Zwave JS issue please help

Configuration Z-Wave
1

Hi HA,
I have a weird one I hope you can help me with a sanity check. I’ve been happily converting from Hubitat. I’ve been migrating all my zwave devices with the latest, greatest JS UI. The process has been going great for weeks until today. I’ve migrated about 80 devices so far without issue. Now, using the same process, I can include new devices, they work 100% in the JS UI but in HA the device is unavailable, and the funny this is I get proper activity updates in the device page’s activity section (so the JS ↔ HA connection appears fine). All the logs indicate a good connection. I’ve restarted HA, unplugged the HA Zwave antenna, restarted JS. What finally worked was doing a full reboot on my HA server. Has this happened to anyone else or is it just an anomoly that can happen from time to time? Thanks

2

Make sure ZwaveJS is not installed and not running at the same time…

3

Thanks, and yes, I read about the confusing naming of the integration. I followed the instructions religiously to make sure only 1 Zwave solution was installed. What was really odd is that in addition to them working 100% through the UI, they were also updating within the ‘Activity’ window on the device page. i.e. the Activity box would show something like ‘scene 001 event triggered by…’. But the device and entities on the same page had literally nothing next to them (no ‘unavailable’, no slide control, no values, nothing) clicking on the actual device to bring up the details window popped up a box that just read Unavailable with a yellow alert icon. It’s like it was halfway connected to HA.

4

it’s likely a browser caching issue. Refresh the page next time using CTRL+F5 (if on windows)

1 Like
5

Huh, for all the debugging things I did, I didn’t try this one. I do for dashboard issues but this didn’t occur to me to try. Hopefully it doesn’t happen again but if it does then I’ll give it a try.
Thanks

6

HA’s UI is a browser, it has all the pitfalls a browser UI has, which is cached and or stale data and code depending on the circumstances. Always CTRL+F5 when things in the UI are acting funky.