Open jbytheway opened 2 months ago
Hello,
I have the same issue since the August upgrades:
Conbee II controller not recognized when performing OS reboot, so Zigbee add-on does not start + External Bluetooth USB controller not recognized when performing OS reboot, so defaulting to the default RPI one (range too low so some devices not recognized)
However after rebooting HA only they are detected again, it seems only OS reboot is causing the issue. In the meantime, after OS reboot, I have to reboot core manually, then start manually zigbee addon, then reconfigure bluetooth integration manually to select the correct controller.
Hello,
Same here, with RPI4 and HA OS 13 (or 13.1)
Today, i restart (electric) the RPI without USB. When HA is ok, i plug USB, and it work ... (Teleinfo and Zigbee)
An update to my symptoms: I've since had to reboot (remaining on 12.2), and when I did so the USB was not detected again. I had to reboot twice before it worked once more.
So perhaps the success or failure is just random, and I got more unlucky with versions later than 12.2.
I did try booting 13.1 four times before giving up. I guess I should try more, but it's rather time consuming so I'm not enthused to.
This got annoying enough that I gave up on trying to fix it and instead migrated my Home Assistant installation to a new device.
But in the process of migrating, I was able to confirm that it wasn't just this USB device that was failing to appear. All USB devices I tried to connect (including a USB keyboard) did not work. So this definitely feels like it was an issue at the kernel or hardware level.
Facing same issues with Home assistant blue. All usb's devices are not reachable. tried to reboot. Tried to downgrade and rebooted many times but no access anymore. Very annoying.
I ran into this issue as well and it turns out that there might be a known hardware issue with the Blue device.
Check these links:
lsusb shows the in built hub, just not the USB stick.
I'm going to go buy a USB hub and see if the the USB ports are dead or if they just can't push any power.
I wound up finding a "USB on the go" hub with power supply in a drawer from another unrelated project with a Pi Zero. Moving my USB stick to that and plugging it into the MicroUSB other side of the HA Blue device got me back up and running.
Which strongly suggests we are victim to the bum hardware in the ODroid. Which is disappointing but at least explains the issue.
Describe the issue you are experiencing
(Previously discussed in the comments of #3347 but I think my issue is different enough that I should open a new one)
When I first upgraded to 12.4 in June my Zigbee controller was not recognized by the kernel. No
/dev/ttyUSB
device appeared, so Zigbee didn't work. I fixed by downgrading to 12.2 (although, strangely, it's necessary to reboot again after downgrading to fix the issue).This weekend I tried upgrading to 13.1 in the hope that this might have been fixed in the interim. But the symptoms remain the same as on 12.4.
I don't see any errors in the host logs. The first relevant log message that appears in the success case but not the failure case is
usbcore: registered new interface driver ch341
It seems like the failure case simply never notices the USB Serial device and registers the driver.
I tried connecting my USB device to a different port; it didn't affect the results.
What operating system image do you use?
odroid-n2 (Hardkernel ODROID-N2/N2+)
What version of Home Assistant Operating System is installed?
13.1
Did the problem occur after upgrading the Operating System?
Yes
Hardware details
Steps to reproduce the issue
/dev
.Anything in the Supervisor logs that might be useful for us?
Anything in the Host logs that might be useful for us?
I've gathered host logs for three different scenarios:
I'll attach the full logs below, but here are some extracted highlights, after running those full logs through
sed -r 's/^([^ ]* ){3}//' | grep -iE 'usb|hub|ch341'
:13.1 failure:
12.2 failure:
12.2 success:
There's not much difference before the USB serial messages, but here are some things I noticed:
System information
No response
Additional information
Full host logs for the three scenarios discussed above:
logs-13.1-failed.txt logs-12.2-failed.txt logs-12.2-success.txt