I setup Openzwave and setup all my devices. It seems to work well. However, when I reboot HA all the zwave entities are unavailable (many are hardwired inovelli switches), even after 10 minutes. The Openzwave addon is running, and the integration says the network available.
The only way to get the zwave nodes back is to restart the OZW addon. I’m on HA 0.115, OZW addon 0.5.2, and a HUSBZB-1 stick.
Having same trouble here… it was all working perfectly. I was able to restart hassio from configuration menu and the openzwave would continue running.
However after trying to pair/include a new motion sensor it started getting hickups. And after a reboot all devices became unavailable. At first i thought it might be updating to latest hassio and OpenZWave but rolling back on my snapshot didn’t solve the problem.
I tried doing mqtt.dump without solving it. I tried restarted the openzwave add-on. I tried restarting hassio from configuration. Right now nothing is working still
Hard to tell whether the root causes are the same or not. In my case, a HASS restart will often render all Z-Wave entities unavailable until (a) I manually interact with them (and that only works some of the time) or (b) an ozwdaemon restart.
Common thread here seems to be the mqtt addon.
The standalone docker container and standalone mqtt containers don’t seem to have this issue, as far as I can tell.
I’m using the standalone ozwdaemon Docker image and a standalone MQTT broker (VerneMQ in Docker) – nothing hass.io-related – and I’m experiencing it every time I restart HASS.