Use this forum to discuss possible implementation of a new feature before opening a ticket.
A developer shall edit the topic title with "[xxx]" where xxx is the id of the accompanying tracker id.
Duplicate posts about the same id. +1 posts are not allowed.
"This provides a standard interface for downstream applications (e.g. ZHA and zigpy-cli) to manage network settings independent of the radio hardware. It also removes the need to separately maintain identical network formation code in each radio library."
Thé zigpy developper want to stick close to the Home assistant side.
I have approached them to do some enhancements in order to have a smooth integration with DomoticZ and got a clear no.
Jeedom's Zigbee plugin developers posted two great blog articles which indirectly explain to users why they choose to base their implementation on zigpy:
Might read a bit pessimistic or realistic as a reference to why supporting different Zigbee devices, in general, is very hard and complicated to implement.
Hello @gamester17 we have reshape the project on Domoticz-Zigate to use zigpy low layers and we are progressing. I have a good feeling on what can be achieve because we will remain at the zigbee layer using raw mode provided by the different devices.
Currently the approach is to use the Domoticz-Zigate in its current state to process all messages, and we will be using zigpy-<radio modules> just to abstract the zigbee controller.
Today our focus is Zigate via the zigpy-zigate module and TI CCxxx (ZNP) via the zigpy-znp module
At the end, we should expect a smooth transition if someone wants to move from one brand to the other, as it will be only to re-pair the device, but all existing plugin database and domoticz database will remains
Renber wrote: ↑Sunday 02 January 2022 16:38
Good news ! I am looking forward to the module for xbee. Thank you
fell free to join the team , we don't have any xbee module, and we are currently focussing on TI, but if you have xbee, we can definitiveley help you in integrating it
As stated, we focus mainly on ZNP the TI Z Stack because we have been equipped with the zzh coordinator from Electro Lama.
Any volunteers to join us to work on deconz, Silabs Xbee ... please just let us know, we have made the think quiet simple and we have somehow a template which need to be duplicated for each new HW coordinator
We have made a good step in the Silicon Labs integration. If there is anybody willing to participate in our tests, we have now a plugin version starting to work with Eelabs keys.
we are making now a new step with the support of dresden electronik and have started the integration of ConBee II and Raspbee.
If any willing to beta test it, just let me know in MP