Skip to content

Conversation

@FreeMasen
Copy link
Owner

No description provided.

@FreeMasen
Copy link
Owner Author

Here is the driver logs for on boarding a new button, I've added lines beginning with -- as comments for the device events I generated by interacting with the device, they are above the print statement output from the MoveToLevelWithOnOff cluster handler

onboarding.log

@FreeMasen FreeMasen changed the title very close to working Add Lutron Aurora driver Sep 21, 2023
address_header = addrh,
body = message_body,
})
device:send(tx)
Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was hoping that doing this would allow the device itself to send an accurate state, instead of treating it like a stateless dimmer where events are either < or > 3. I am now seeing this go out and maybe get acknowledged but not change in the device.

# received read request
< ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xF298, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0xFF, profile: 0x0104, cluster: Level >, lqi: 0xC4, rssi: -61, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x10, seqno: 0x75, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
# sent response
< ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xF298, dest_endpoint: 0x01, profile: 0x0104, cluster: Level >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || attr_id: 0x0000, ZclStatus: SUCCESS, DataType: Uint8, data: 0xE5 > > > >
# Level
< ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xF298, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0xFF, profile: 0x0104, cluster: Level >, lqi: 0xD4, rssi: -64, body_length: 0x0006, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x11, seqno: 0x77, ZCLCommandId: 0x04 >, < MoveToLevelWithOnOff || level: 0x02, transition_time: 0x0002 > > >
# ack?
< ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xF298, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Level >, lqi: 0xD6, rssi: -64, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x14, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x01, ZclStatus: SUCCESS > > >

It seems odd that we get the MoveToLevel event before the ack (assuming that it is an ack?)

Comment on lines 19 to 23
if not self.environment_info.hub_zigbee_eui then
return self:call_with_delay(1, function()
do_configure(self, device)
end)
end
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

were you running into this happening during testing?

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not really, just when I was trying to get some already onboarded devices reconfigured so I was calling this from added

capabilities:
- id: button
version: 1
- id: switchLevel
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

did you also want to emulate "switch"?

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is sort of up in the air, this is currently setup to just be a button and a dimmer but it could be a switch instead

@FreeMasen FreeMasen force-pushed the feat/phillips-aurora branch from 24ecf70 to 7fe5f5d Compare December 12, 2023 17:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants