Z-wave JS Working but Devices Show Unavailable

joebrands · May 3, 2022, 4:15pm

Hello, I had a power failure due to the recent tornado and after that everything in HA is fine except all the zwave devices now show unavailable. Its strange because looking ta the log of zwave js, I can see all of their status’s updating fine and the controller is working fine as well. I am not sure where the disconnect is.

I did also update everything to check and see if it was versions of zwave and HA that didn’t play nice but that doesn’t change anything. I even restored a backup from the day before the power fault and same thing.

Startup Log:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing... 
-----------------------------------------------------------
 Add-on: Z-Wave JS to MQTT
 Fully configurable Z-Wave JS to MQTT gateway and control panel; based on Zwavejs2Mqtt
-----------------------------------------------------------
 Add-on version: 0.39.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 7.6  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2022.4.7
 Home Assistant Supervisor: 2022.04.0
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] configuration.sh: executing... 
[cont-init.d] configuration.sh: exited 0.
[cont-init.d] nginx.sh: executing... 
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[11:04:26] INFO: Starting the Z-Wave JS to MQTT...
/bin/sh: git: not found
2022-05-03 11:04:32.090 INFO APP: Version: 6.8.1
2022-05-03 11:04:32.099 INFO APP: Application path:/opt
2022-05-03 11:05:24.056 WARN STORE: scenes.json not found
2022-05-03 11:05:24.127 INFO APP: Listening on port 44920 host 0.0.0.0 protocol HTTP
2022-05-03 11:05:24.198 INFO MQTT: MQTT is disabled
[11:05:24] INFO: Starting NGinx...
2022-05-03 11:05:24.249 INFO ZWAVE: Connecting to /dev/serial/by-id/usb-0658_0200-if00
2022-05-03 11:05:27.306 INFO ZWAVE: Zwave driver is ready
2022-05-03 11:05:27.309 INFO ZWAVE: Controller status: Driver ready
2022-05-03 11:05:27.415 INFO ZWAVE: Scanning network with homeid: 0xd107634d
2022-05-03 11:05:27.420 INFO ZWAVE: Node 1 is alive
2022-05-03 11:05:27.428 INFO ZWAVE: Node 1 ready: Zooz - ZST10 (S2 USB Stick Controller)
2022-05-03 11:05:27.729 INFO ZWAVE-SERVER: ZwaveJS server listening on 0.0.0.0:3000
2022-05-03 11:05:28.117 INFO ZWAVE: Next update scheduled for: Wed May 04 2022 00:00:00 GMT-0500 (Central Daylight Time)
2022-05-03 11:05:28.702 INFO ZWAVE-SERVER: DNS Service Discovery enabled
2022-05-03 11:05:29.219 INFO ZWAVE: Node 23: value added 23-50-0-value-66049 => 0
2022-05-03 11:05:29.221 INFO ZWAVE: Node 23: value updated: 50-0-value-66049 0 => 0
2022-05-03 11:05:29.394 INFO ZWAVE: Node 23: value updated: 50-0-value-66049 0 => 0
2022-05-03 11:05:29.408 INFO ZWAVE: Node 23: value updated: 50-0-value-66049 0 => 0

petro · May 3, 2022, 4:21pm

You’ll have to keep watching the logs for node 19. Looking at the logs, I don’t see the startup fully complete. Your logs only mention that the Node 1 is ready. For what it’s worth, I’ve had devices die after power failures as well.

joebrands · May 3, 2022, 4:25pm

I just cut off the log but all the nodes are correctly reporting status updates

2022-05-03 11:26:11.032 INFO ZWAVE: Node 19: value updated: 50-0-value-66049 1.419 => 1.419

petro · May 3, 2022, 4:29pm

Is there another device using that node without manufacturing information?

joebrands · May 3, 2022, 4:48pm

Under the zwave service, I only see my 9 devices/78 entities and no duplicates if that’s what you’re asking. I did notice though that the entities almost all show a “restored” status next to them but I have no idea if that is relevant or not.

finity · May 3, 2022, 9:06pm

Do they all show up normally/alive/complete in the zwavejs2mqtt web interface?

joebrands · May 4, 2022, 2:25pm

Ya they all look good except status shows unknown but I don’t remember if its always shown that

finity · May 5, 2022, 12:36pm

Then that is not good.

All of mine have known status (no ?)

can you do a re-interview of each node one-by-one as each completes?

petro · May 5, 2022, 12:43pm

Before we get too crazy here, have you restarted the container?

joebrands · May 5, 2022, 2:23pm

Ya I think I can just re-interview them all but I wanted to see if I could solve this without doing that. I only have a few devices on this network but it wouldn’t be as feasible when I have 100 of them.

Yes I have restarted zwave-js as well as the pi. I also updated both zwave and HA

petro · May 5, 2022, 2:26pm

Can you verify that you don’t have a ZwaveJS addon installed?

joebrands · May 5, 2022, 3:21pm

I have the supervisor addon installed and the integration connects to its hostname. Is there a different way I should be doing that?

petro · May 5, 2022, 3:36pm

You should have only 2 aspects of Zwave JS installed.

The ZwaveJS2MQTT addon.
If you have the ZwaveJS addon, remove it.
The ZwaveJS Integration.

joebrands · May 5, 2022, 3:39pm

Ah okay sorry I should be more specific. I have the ZwaveJS2MQTT not ZwaveJS in supervisor. Then I also have the ZwaveJS integration.

petro · May 5, 2022, 3:41pm

Thanks, that clarifies things.

Is it possible to restart the addon and post the entire logs here? Lastly, are these all battery devices or are they hardwired?

petro · May 5, 2022, 4:02pm

Actually, I think you can download the logs from zwavejs2mqtt directly from the UI.

It’s on the 6th tab, find one of the zwavejs_xxxx.log_date files and post it.

joebrands · May 5, 2022, 4:22pm

Yep, here it is. Looks like the nodes are failing to ping and also controller is doing some weird stuff
https://pastebin.com/MNRM1XZ0

firstof9 · May 5, 2022, 4:44pm

Unplug your zwave stick from the USB port and re-insert it, then restart the zwavejs2mqtt addon.
It looks like your stick is “jammed” up, I’ve had it happen once or twice.

joebrands · May 5, 2022, 11:40pm

That actually did the trick, Ill have to remember that next time, thank you guys for the help