Closed Cervenka closed 4 years ago
I was having the same problem.
First try deleting the OpenZwave message queue in your MQTT instance and restarting (as implied in the log) this used to work for me in the previous version. In this version (0.5.0) I have to add the instance configuration variable and keep alternating between 1 and 2 while always remembering to delete the old queues from the MQTT server when I restart.
I have other problems but those could be self-inflicted so even with the above my system is not working but at least the add-on stays up. I hope that my comments may help those with more knowledge find the problem.
It looks like somehow on unclean shutdown, the bridged MQTT instance inside the OpenZWave addon still has a stale /OpenZWave/1/Status
key. Before that internal MQTT server can sync with the main HASS MQTT server, the startup script dies.
For me, this results in a failure to start the addon after an unclean shutdown, even if I delete the /OpenZWave/1
key in the HASS MQTT server. The only way I've found to recover from this is to uninstall and reinstall the OpenZWave addon (which seems to clear out the local data of the OZW MQTT server).
I'm seeing this error as well running a generic linux install. I actually am getting a segfault message appearing in dmesg when the crash happens:
[65410.180934] ozwadmin[13807]: segfault at 38 ip 00007f6e9083bd83 sp 00007ffed81961f0 error 4 in libqvnc.so[7f6e90837000+15000]
I also have this problem. I'm running OpenZwave as a (supervisor) add-on. Any hints on how to diagnose this?
ozwave is crashing for me after updating it from 0.4 to 0.5