WTH why ZHA not option to run it addon/docker so Zigbee network does die on reboot? I would love to use ZHA instead of Zigbee2MQTT, the only reason I run Zigbee2MQTT is so my Zigbee network doesn’t die on reboot. I don’t really use MQTT side of that app.
Why do you reboot the host so much? That’s a very rare event for me personally.
I don’t reboot the host that offend, but isn’t ZHA apart for core, and that get reboot more often then the host?
Oh. Well I mean it doesn’t die with an HA restart, the coordinator is still active. It’ll miss state changes but it gets the current state once it starts again. Which isn’t any different then Z2M (HA misses all state changes while down and catches up when back online).
Maybe you can clarify what is breaking for you as opposed to Z2M or what specifically you want to happen differently?
The zha integration would need to become an addon. It was in the works but stopped due to the issues of migrating from an integration to an addon seamlessly and avoiding the issues that occured with the zwave integration migrations to zwavejs from openzwave I think it was.