The good thing is that you can cover different use cases, but OMG there must be soo much churn & duplication! I hope there are also synergies, like I learned from Z2M how to OTA "manually" via ZHA.
Next task: look around if anyone's made a chart comparing the different options.
@fm_volker A mess? Maybe. However, for me it's a sign of Freedom. Anybody can code whatever (s)he wants, and publish it. Why should I moan?
My current understanding is:
deconz is proprietary, works only with a dongle from one company
z2m is the thing to use if you want Zigbee. If something doesn't work, don't post a toot, but create a bug report and help the devs recreate the problem. z2m works with msny dongle brands.
ZHA is the new kid on the block. It's currently inferior to z2m. It works with many dongle brands, too. Where it shines is (only!) for devs and early adopters. One of the many supported dongles, the SkyConnect, allows for different firmwares. Besides Zigbee it will allow you to use "Thread over Matter" with it. So ZHA is used mostly to get Homeassistant into the "Thread over Ethernet", "Thread over Wifi" and "Thread over Matter" world. But: almost everything here is a work in progress.
@fm_volker Don't do deconz. It's not as powerful or reliable as z2m or ZHA. I've migrated from deconz to z2m (which allowed me to consolidate it on one device as well) which works great.
ZHA is also looking better and better, but when I switched z2m was significantly more mature. That might change.
@larsmb I wanted to go with ZHA — again, after switching to a new RPi4. But surprisingly, this time in HAOS, ZHA falls over the Raspbee 2 TTY, whereas the DECONZ-add on (also a container) has absolutely no issues.
Add comment