Hi folks,
I have a problem with my zwave devices dropping off the network and it requires a restart of Z-Wave JS to get things working again. I run Home Assistant OS 5.12 (download and burn the image to SD, boom your up and running) along with a HUSBZB-1 Hub setup with 2 zwave devices (Motion sensor and tilt sensor) and a bunch of zigbee bulbs along with a few Zigbee outlets. A Raspberry Pi 3 B+ is the host.
My problem is that numerous times throughout the day the triggers from the zwave devices stop being seen by HA. In the logs I found “usb_serial_generic_read_bulk_callback - urb stopped: -32” for both USB0 and USB1. (visible with dmesg|grep usb) The zigbee devices still work fine and I suspect that is because I send commands to them vs the zwave ones which I rely on them to send state updates to HA. Pulling up Supervisor -> Z-Wave JS and selecting “Restart” from the control panel gets the devices working again.
I’ve been having these entries pop up probably up to a dozen times a day. Sometimes I’ll go for a day with no issues and then the next day may bring on 1 entry for me to reset the plugin with no problems the rest of the day or sometimes it’s almost constant. I’ve even removed the usb extension cable with no real change apparent. It’s been irritating to say the least.
Googling the “urb stopped” entries show that it seems to have been an minor issue on the Pi’s for a few years for some people now with no real fix. Some believe it to be a hardware issue while others lean toward a disappearing file handle being the culprit. At this point I’d be happy just to implement a cron job to automate a restart of Z-Wave JS periodically and be done with it but have not been able to figure out how to go about calling a restart from the “Terminal & SSH” addon or from anywhere else outside the Z-Wave JS console for that matter.
If someone could share how to restart Z-Wave JS from command line I would be a very happy camper indeed. As I’m not a programmer an ELI5 rendition would be best.
Thanks!