#[Resolved] Coral device stopped working after last update

1 messages · Page 1 of 1 (latest)

mighty sable
#

HI all,

I noticed that after updating to 2025.9.1 my coral device wasn't working and Frigate would crash.

dmesg shows it's detected:
2025-09-10 16:29:58.391 homeassistant kernel: usb 2-1: new SuperSpeed USB device number 2 using xhci-hcd
2025-09-10 16:29:58.407 homeassistant kernel: usb 2-1: New USB device found, idVendor=1a6e, idProduct=089a, bcdDevice= 1.00
2025-09-10 16:29:58.407 homeassistant kernel: usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0

but it seems that lsusb doesn't properly recognize it and I don't think the device drivers are created.

lsusb
Bus 003 Device 001: ID 1d6b:0002 Linux 6.12.34-haos-raspi xhci-hcd xHCI Host Controller
Bus 002 Device 002: ID 1a6e:089a
Bus 001 Device 001: ID 1d6b:0002 Linux 6.12.34-haos-raspi xhci-hcd xHCI Host Controller
Bus 004 Device 001: ID 1d6b:0003 Linux 6.12.34-haos-raspi xhci-hcd xHCI Host Controller
Bus 004 Device 002: ID 0bda:9210 Realtek RTL9210
Bus 002 Device 001: ID 1d6b:0003 Linux 6.12.34-haos-raspi xhci-hcd xHCI Host Controller
Bus 001 Device 003: ID 1b3f:2008 GeneralPlus USB Audio Device
Bus 001 Device 002: ID 14cd:8601 USB Device USB 2.0 Hub

I stuck it on my linux box and it works fine there.

I rolled back to 2025.8.3 with no joy then rolled back the OS from 16.2 to 16.1 and that didn't fix it either. I'm at a loss as what to try next. I'm open to suggestions. I'm running HAOS On an Rpi5.

More documentation in the git issue tracker at https://github.com/home-assistant/operating-system/issues/4294#issuecomment-3282592287

GitHub

Describe the issue you are experiencing I noticed the other day that my Frigate had stopped working. Delving into things a little further I see this in my log: 2025-09-10 16:28:16.691722650 [2025-0...

mighty sable
#

huh, it looks like protection mode was turned on by something in the Frigate config.