ZWave needs to handle interface failure or disconnection more gracefully.
I recently had a z-wave interface suddenly unable to initialize its UART (it had been up for 16 days):
[cp210x ttyUSB0: cp210x_open - Unable to enable UART 1597473.446697 cp210x ttyUSB0: cp210x_open - Unable to enable UART [cp210x ttyUSB0: cp210x_open - Unable to enable UART 1597483.448871 cp210x ttyUSB0: cp210x_open - Unable to enable UART [cp210x ttyUSB0: cp210x_open - Unable to enable UART
Upon unplugging and re-plugging in the device, it was able to properly initialize again:
1597945.579260 cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [cp210x 2-1.1:1.0: device disconnected 1597952.778096 usb 2-1.1: new full-speed USB device number 5 using ehci-pci [usb 2-1.1: New USB device found, idVendor=10c4, idProduct=ea60 1597952.872358 usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [usb 2-1.1: Product: CP2102 USB to UART Bridge Controller 1597952.872364 usb 2-1.1: Manufacturer: Silicon Labs [usb 2-1.1: SerialNumber: 0001 1597952.873283 cp210x 2-1.1:1.0: cp210x converter detected [usb 2-1.1: reset full-speed USB device number 5 using ehci-pci 1597953.039125 usb 2-1.1: cp210x converter now attached to ttyUSB0
Once this was done, however, I had to Reset the device from the web admin (or killall ZWave) for it to bring the interface back up.
How can we better handle this situation?
-Thom