No ZWave devices showing after zwave JS update

I fell victim to the ZWave JS UI update that broke things but this has since been fixed in Zwave JS UI 1.15.5.

However, even after I upgraded to 1.15.5, I’m still having issues with no devices showing up:

Zwave JS UI

It shows it as connected
image

Showing failed setup:

Tapping on the configure button:

My “connection method” settings are this:

In Addons, i only have Z-Wave JS UI installed:

The log from that addon shows this:

2023-08-17 13:50:07.404 INFO APP: GET /health/zwave 200 0.295 ms - 2140
2023-08-17 13:50:37.881 INFO APP: GET /health/zwave 200 0.292 ms - 2140
2023-08-17 13:51:08.352 INFO APP: GET /health/zwave 200 0.783 ms - 2140
2023-08-17 13:51:38.862 INFO APP: GET /health/zwave 200 0.332 ms - 2140
2023-08-17 13:52:09.298 INFO APP: GET /health/zwave 200 0.283 ms - 2140
2023-08-17 13:52:39.816 INFO APP: GET /health/zwave 200 0.396 ms - 2140
2023-08-17 13:53:10.247 INFO APP: GET /health/zwave 200 0.370 ms - 2140
2023-08-17 13:53:40.715 INFO APP: GET /health/zwave 200 0.285 ms - 2140
2023-08-17 13:54:11.153 INFO APP: GET /health/zwave 200 0.285 ms - 2140
2023-08-17 13:54:41.761 INFO APP: GET /health/zwave 200 0.300 ms - 2140
2023-08-17 13:55:12.453 INFO APP: GET /health/zwave 200 0.335 ms - 2140
2023-08-17 13:55:43.162 INFO APP: GET /health/zwave 200 0.291 ms - 2140
2023-08-17 13:56:13.700 INFO APP: GET /health/zwave 200 0.275 ms - 2140
2023-08-17 13:56:44.200 INFO APP: GET /health/zwave 200 0.280 ms - 2140
2023-08-17 13:57:14.647 INFO APP: GET /health/zwave 200 0.290 ms - 2140
2023-08-17 13:57:45.069 INFO APP: GET /health/zwave 200 0.331 ms - 2140
2023-08-17 13:58:15.706 INFO APP: GET /health/zwave 200 0.299 ms - 2140
2023-08-17 13:58:46.403 INFO APP: GET /health/zwave 200 0.277 ms - 2140
2023-08-17 13:59:17.009 INFO APP: GET /health/zwave 200 0.305 ms - 2140
2023-08-17 13:59:47.593 INFO APP: GET /health/zwave 200 0.282 ms - 2140
2023-08-17 14:00:18.044 INFO APP: GET /health/zwave 200 0.315 ms - 2140
2023-08-17 14:00:48.456 INFO APP: GET /health/zwave 200 0.504 ms - 2140
2023-08-17 14:01:18.903 INFO APP: GET /health/zwave 200 0.302 ms - 2140
2023-08-17 14:01:49.355 INFO APP: GET /health/zwave 200 0.325 ms - 2140
2023-08-17 14:02:19.758 INFO APP: GET /health/zwave 200 0.295 ms - 2140
2023-08-17 14:02:38.707 INFO APP: GET / 200 88.798 ms - 2140
2023-08-17 14:02:38.801 INFO APP: GET /static/js/126.7b8e034044b622d70d63.js 200 33.788 ms - 44167
2023-08-17 14:02:38.870 INFO APP: GET /static/css/app.83a89bf35f19c04e42df.css 200 48.645 ms - 920456
2023-08-17 14:02:38.885 INFO APP: GET /static/js/app.c8ececd4b4407683c2ba.js 200 33.437 ms - 2370482
2023-08-17 14:02:39.153 INFO APP: GET /api/auth-enabled 200 8.899 ms - 29
2023-08-17 14:02:39.167 INFO APP: GET /static/favicons/favicon-32x32.png 200 12.721 ms - 1670
2023-08-17 14:02:39.291 INFO APP: GET /static/logo.png 200 76.238 ms - 26171
2023-08-17 14:02:39.295 DEBUG SOCKET: New connection Iny3Exk60SWZFyNxAAAN
2023-08-17 14:02:39.381 INFO Z-WAVE: Setting user callbacks
2023-08-17 14:02:39.414 DEBUG SOCKET: Event INITED emitted to Iny3Exk60SWZFyNxAAAN
2023-08-17 14:02:39.440 INFO APP: GET //static/fonts/MaterialIcons-Regular.2d80174.woff2 200 29.262 ms - 125116
2023-08-17 14:02:40.530 INFO APP: GET /api/settings 200 1313.697 ms - 13613
2023-08-17 14:02:40.538 INFO APP: GET /api/auth-enabled 304 0.770 ms - -
2023-08-17 14:02:50.202 INFO APP: GET /health/zwave 200 0.336 ms - 2140
2023-08-17 14:03:11.927 DEBUG SOCKET: User disconnected from Iny3Exk60SWZFyNxAAAN: transport close
2023-08-17 14:03:11.928 INFO Z-WAVE: Removing user callbacks
2023-08-17 14:03:20.649 INFO APP: GET /health/zwave 200 0.359 ms - 2140
2023-08-17 14:03:51.100 INFO APP: GET /health/zwave 200 0.312 ms - 2140
2023-08-17 14:04:21.516 INFO APP: GET /health/zwave 200 0.321 ms - 2140

Help?

have you tried a power cycle of your Rpi, Yellow Box, or whatever box you use ?

I’m running HA in a VM but don’t think I’ve restarted it. I’ll try that now.

Did this and no change. Exactly same situation as I originally described.

Try to remove Zwave dongle and put back.

This did the trick along with powering down the VM and powering it back up. Thank you!

1 Like