Not sure what has happened all my nodes are all of a sudden gone (empty list), in the zwave-js UI it states connected, but “no data available”, “no nodes” in HA integration it states failed setup, but has all my 24 nodes are listed there. Sadly I am not at the house, remote reboot/restart (linux + docker) doesn’t help…hoping it just needs a hard boot as zwave-js is unable to read the my aeotec 700 stick. Anyone experienced this? When access the list in the control panel it states in red “Error while calling getProvisioningEntries: Z-Wave client not connected”
That’s the expected behavior when. JsUI can’t see the stick. I’d do a host restart and see if it comes back.
Definitely don’t start making configuration changes until you fix the comms issue.
Cool, will see if I can track someone down to hard boot the device (reboots don’t do anything). It does list the device "lrwxrwxrwx 1 root root 13 Aug 2 00:42 usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_989d61548974ec1193afa95019c2d21c-if00-port0 -> ../../ttyUSB0" or is this different?
That’s indeed a silicon labs cp210 device. (most likely your stick)
Many reasons it could not be ‘talking’. Could be interference, the stick could have just locked up. Too early to know… most of these issues clear with a hard reboot. Start there. Also consider installing something to be able to remotely, reliably power cycle the box on demand if you’re running headless and remote.
Two comments…
(1) Yesterday one of my Zwave devices seemed disconnected and a ping did not work. I restored the latest backup and that resolved it.
(2) I put my HA Yellow Box on a Kasa Wifi switch. If I have HA issues and need to restart the box while away from home, then I do that with the ON-OFF Kasa switch in the Kasa App on my phone.
Planning to configure wake-on-lan, so I can sent a shutdown (properly bring it up) and hard boot the device by waking it remotely. Anyways had the neighbor switch it back on after shutting it down and everything popped back up…phew!!!
2 Likes
fixed…neighbor switched host back on after I remotely shut it down…everything back in order!!! Thanks!!
1 Like
Issue came back last night (lost connection to controller), however fixed it by enabling “soft reset” option in the zwave control panel…basically after I enabled it all devices directly popped up…somewhat confused by this as it reads disabled causes issues with some controller and it seems with me having it disabled caused issues! Now I believe there was a recent update I pulled to zwave-js (latest) and never had this issue prior, so wondering if its related. Anyways been stable since last night!
Soft reset is a potential problem for 500-series controllers being used in VMs. 700-series aren’t usually affected.
gotcha, however the odd thing was switching it on actually fixed my issue…and never had an issue with zwave-js (docker-compose) not seeing the controller and now twice in 2 days, well the info on the controller as it actually said it was connected!! Again wondering if something got updated think I might have pulled a newer version of zwave-js
You might just need to reseat the stick in the USB port, they’re pretty heavy and especially with vertical ports the connection sometimes gets a bit unreliable.
1 Like
For anyone that missed it, a recent update caused an issue with the soft reset option causing the stick to lock up. Looks like it’s fixed in the next Z-Wave JS UI release and the workaround is to disable the soft reset option from settings.
1 Like