Odroid N2+ loss of USB devices after upgrading to OS 6.0 - "Ignore device ... failes to initialize by udev"

Hi everyone. Earlier today I upgraded to OS 6.0 and afterwards discovered my Zigbee devices (deconz Conbee II, using a usb extension) were all unavailable, as was my NUT UPS connection.

Looking at the Hardware list, the USB devices weren’t listed. Unplugging - replugging the USBs, I’m getting this error (just the once) in the Supervisor log:

21-06-21 21:31:00 WARNING (MainThread) [supervisor.hardware.monitor] Ignore device /sys/devices/platform/soc/ffe09000.usb/ff500000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.1 / failes to initialize by udev
21-06-21 21:31:00 WARNING (MainThread) [supervisor.hardware.monitor] Ignore device /sys/devices/platform/soc/ffe09000.usb/ff500000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.1 / failes to initialize by udev
21-06-21 21:31:00 WARNING (MainThread) [supervisor.hardware.monitor] Ignore device /sys/devices/platform/soc/ffe09000.usb/ff500000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.1/1-1.1:1.0/0003:051D:0002.0002/hidraw/hidraw0 / failes to initialize by udev

Looking in the Host log, the UPS connection is briefly detected but then disconnects.

[   19.073923] usb 1-1: new high-speed USB device number 5 using xhci-hcd
[   19.261670] hub 1-1:1.0: USB hub found
[   19.262159] hub 1-1:1.0: 4 ports detected
[   19.350050] usb 2-1: new SuperSpeed Gen 1 USB device number 5 using xhci-hcd
[   19.405913] hub 2-1:1.0: USB hub found
[   19.406222] hub 2-1:1.0: 4 ports detected
[   19.617919] usb 1-1.2: new full-speed USB device number 6 using xhci-hcd
[   19.779538] hid-generic 0003:051D:0002.0001: hidraw0: USB HID v1.00 Device [American Power Conversion Back-UPS ES 850G2 FW:938.a2 .I USB FW:a2 ] on usb-xhci-hcd.4.auto-1.2/input0
[   20.799369] usb 1-1.2: USB disconnect, device number 6

No named mention of the Conbee II stick.

I’ve tried several restarts, different ports, even rolling back to OS 5.13 (but that then caused an issue with PulseAudio so went back to 6). Anyone have any ideas?

Not had this issue (I don’t have anything plugged into my n2+) but thought I’d mention that given home assistant blue is an Odroid N2+, I’d have expected to see many more people flagging this. Could it be specific to your install? Clean etch and config restore solve it?

Thanks, Andy. I did consider that it would’ve been more widespread, but no harm in asking around. Using a Pi as an external deconz host as a workaround until I have more time to investigate a fix. Can’t re-etch right now as I don’t have an eMMC adapter, but will consider in future.

I’m not sure if you need a dedicated etcher.

Doesn’t the odroid n2+ have an SPI mode that lets you flash it over usb?

Does it? Even better! I bought it as a pre-installed unit so didn’t have to worry about that. Will definitely consider reflashing it then… if the USB works :wink: Thanks for the pointers!

1 Like

Common Tasks - Operating System - Home Assistant gives the instructions, I believe.