Add custom command support and Zigbee channel retention#80
Conversation
|
Thanks, looks good and clean. Not sure if we should add a data type parameter. And I am not a big fan of the void pointer parameter but not sure if there is a better alternative. Do you also use #26 ? At the moment I am reworking the action callbacks, because they are not threadsave. I would like to merge that first and then look into this. |
|
Could you provide an example yaml? |
|
Wow, thanks for the pointers. Here's the example hue light i'm vibe coding: |
|
I have pushed my changes. Could you please rebase your work and use the new zigbee_event for handling the commands? |
@mwitkow Can you explain the reasoning and purpose for wanting to add this? Asking as wondering if this type of explicit hardcoding of a Zigbee channel does not violate set standard the Zigbee specification standards? I understand that while a device once joined should retain the Zigbee channel across power cycles, reboots, or network interruptions. I do not not Zigbee channel retention should not be hardcoded as it should be possible for the Zigbee gateway application to tell the Zigbee Coordinator to broadcast a Zigbee change channel request command? For reference see Home Assistant's ZHA integration which allow the user to change the Zigbee channel on an existing network: |
I'm building an esph-ome philips-multicolor light (addressable strip).