Since I rebooted my server, some addon can’t start:
19-07-05 01:41:00 ERROR (SyncWorker_3) [hassio.docker] Can't start addon_a0d7b954_vscode: 500 Server Error: Internal Server Error ("linux runtime spec devices: error gathering device information while adding custom device "/dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0014XXXXXX-if00": no such file or directory")
19-07-05 01:41:01 ERROR (SyncWorker_4) [hassio.docker] Can't start addon_7ad98f9c_zigbee2mqtt: 500 Server Error: Internal Server Error ("linux runtime spec devices: error gathering device information while adding custom device "/dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0014XXXXXX-if00": no such file or directory")
19-07-05 01:41:18 ERROR (SyncWorker_6) [hassio.docker] Can't start addon_a0d7b954_nodered: 500 Server Error: Internal Server Error ("linux runtime spec devices: error gathering device information while adding custom device "/dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0014XXXXXX-if00": no such file or directory")
I think I already had a problem similar to that one and “fixed” it by reinstalling the affected addons. This time this doesn’t work. If I unplug the usb device, I can start the addons excepting the zigbee2mqtt addon.
When I go to Hass.io -> System and click the hardware button, I see that the device /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0014XXXXXX-if00 is correctly detected.
What’s wrong?
I’m running Hass.io on a Proxmox VM (HassOS 2.12, I also had the problem on 2.11)
If I login with ssh on port 22222 (debug), I don’t see the device when doing an ls on /dev/serial/by-id, but I see my zigbee/zwave stick? The device is listed with lsusb though.
in my case, I could “rename” the device in re-programming the USB-chip itself with a different name (without colon’s!).
I guess the other (only?) possible solution is to create links. And you have to take care that these links are re-created after rebooting!