I’ve took the plunge last weekend and removed all devices from ZHA and re-added them using Deconz. After renaming them all my automations etc work again and the past five days have been really great; not a single light that stayed on when it wasn’t supposed to, or the other way around. I was dreading this transition because I wasn’t sure if deCONZ was going to be an improvement for me, but for now I’m very glad that I did.
A few takeaways:
- While the Phoscon and deCONZ bundle is a bit weird, deCONZ is very advanced. In ZHA I never managed to be able to rewrite cluster attributes for my Aqara curtains, in deCONZ those attributes all have readable names and values (instead of hexadecimals) and a form-based interface. I needed this to change the direction of one of my curtains, since HA always thought it was open when it was closed. That saves me a template cover!
- Another benefit for my curtains; their exact position is available in the entity itself. With ZHA I had to use a database sensor to read a value.
- The most problems I’ve experienced in ZHA were with lights that have to turn on with a specific brightness / color temperature. 9 times out of 10, these light would just turn on on a very low brightness, regardless of the desired state. This works perfectly with deCONZ.
- Zigbee light groups work very good for me; consistently switching all the devices in the group on or off and reporting the correct status.
- Automations and scripts feel ‘snappier’. During my last week with ZHA I had some devices randomly losing connection overnight, causing a lot of timeout errors in the logs. These errors also halted the execution of the actions in those automations, or really slowed them down at times that ZHA did work. My guess is that HA waits for each individual ZHA action to complete before continuing to the next action. The deCONZ integration does not seem to do that, or does it much faster, since especially large automations (scripts that turn off all the devices in my home for example), are completed much faster.