For the third time over a few months time, after a power loss, all of my “Z-Wave JS to MQTT”-nodes are unresponsive and ends up in a Status: Unknown. The Interview for ProtocolInfo is stuck with the rotating circle. This means that no Z-Wave nodes are working.
I´ve tried rebooting HA, also with a cold start, nothing helps.
Last time it happened a month ago, I did a Partial snapshot restore of the “Z-Wave JS to MQTT” which brought everything back alive. This time it doesn´t help. Can anyone please help or point me towards a solution?
This is from the system log after a partial restore:
21-07-13 12:35:08 INFO (MainThread) [supervisor.snapshots] Found 5 snapshot files
21-07-13 12:37:15 INFO (MainThread) [supervisor.snapshots] Partial-Restore 89eebaa6 start
21-07-13 12:38:15 INFO (MainThread) [supervisor.jobs] 'SnapshotManager.do_restore_partial' blocked from execution, system is not running - CoreState.FREEZE
21-07-13 12:39:54 INFO (MainThread) [supervisor.snapshots] Restoring 89eebaa6 Docker Config
21-07-13 12:39:54 INFO (MainThread) [supervisor.snapshots] Restoring 89eebaa6 Repositories
21-07-13 12:39:55 INFO (MainThread) [supervisor.store] Loading add-ons from store: 65 all - 0 new - 0 remove
21-07-13 12:39:55 INFO (MainThread) [supervisor.snapshots] Restoring 89eebaa6 old add-ons
21-07-13 12:39:59 INFO (MainThread) [supervisor.addons.addon] Restore config for addon a0d7b954_zwavejs2mqtt
21-07-13 12:39:59 INFO (SyncWorker_0) [supervisor.docker.interface] Stopping addon_a0d7b954_zwavejs2mqtt application
21-07-13 12:40:29 INFO (SyncWorker_0) [supervisor.docker.interface] Cleaning addon_a0d7b954_zwavejs2mqtt application
21-07-13 12:40:29 INFO (MainThread) [supervisor.addons.addon] Restoring data for addon a0d7b954_zwavejs2mqtt
21-07-13 12:40:36 INFO (SyncWorker_6) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/zwavejs2mqtt/aarch64 with version 0.22.0
21-07-13 12:40:36 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
21-07-13 12:40:36 WARNING (MainThread) [supervisor.ingress] Fails Ingress panel for a0d7b954_zwavejs2mqtt with 500
21-07-13 12:40:37 INFO (MainThread) [supervisor.snapshots] Partial-Restore 89eebaa6 done
21-07-13 12:41:23 ERROR (MainThread) [supervisor.api.ingress] Ingress error: 400, message='Invalid response status', url=URL('http://172.30.33.1:8099/socket.io/?EIO=4&transport=websocket&sid=exL-ILsyC41EcWj1AAAA')
21-07-13 12:47:35 ERROR (MainThread) [supervisor.api.ingress] Ingress error: 400, message='Invalid response status', url=URL('http://172.30.33.1:8099/socket.io/?EIO=4&transport=websocket&sid=CWm5t5IdGeyX0IPTAAAC')
I dont know if the CoreState.FREEZE or the Ingress Warning/Errors is related.
I get plenty of these in the Z-Wave JS log:
2021-07-13 12:55:54.110 INFO ZWAVE: Node 76: value updated: 50-0-value-66049 0 => 0
2021-07-13 12:55:55.844 INFO ZWAVE: Node 76: value updated: 50-0-value-66049 0 => 0
2021-07-13 12:55:56.725 INFO ZWAVE: Node 76: value updated: 50-0-value-66049 0 => 0
2021-07-13 12:55:56.912 INFO ZWAVE: Node 76: value updated: 50-0-value-66049 0 => 0
2021-07-13 12:55:56.925 INFO ZWAVE: Node 76: value updated: 50-0-value-66049 0 => 0
2021-07-13 12:56:03.646 INFO APP: GET /health/zwave 200 3.966 ms - 1875
2021-07-13 12:56:13.098 INFO ZWAVE: Node 71: value updated: 50-0-value-66049 0 => 0
2021-07-13 12:56:13.138 INFO ZWAVE: Node 71: value updated: 50-0-value-66049 0 => 0
2021-07-13 12:56:13.163 INFO ZWAVE: Node 71: value updated: 50-0-value-66049 0 => 0
2021-07-13 12:56:14.073 INFO ZWAVE: Node 71: value updated: 50-0-value-66049 0 => 0
However, the node 71 and 76 is also Unknown and doesn´t work together with all the other nodes.