kattkaries

I'm having the same issue. Also using the Yale Access integration on a NUC. I actually have two bluetooth adapters active (the built in one and a USB one), since...

I don’t know how to check the manufacturer ID, but I have a hard time believing all those different products use the same ID. Like for Nicxe, there’s no way...

So you actually removed the BT hardware from a NUC? I thought it was soldered/hardwired to the MB. Care to point a finger to what to remove in there?

> > I don’t know how to check the manufacturer ID > > Enable debug logging for `homeassistant.components.bluetooth`. You'll see all the advertisements. If I had to guess, it looks...

So, here's another one being detected after enabling BT debug logging.  Turns out the there is a 465 nestled in the manufacturer ID: 2022-09-12 15:51:42.095 DEBUG (MainThread) [homeassistant.components.bluetooth.manager] hci0:...

> https://github.com/hbldh/bleak/blob/aa24332a39952880005705155629df423fbad1aa/bleak/backends/_manufacturers.py#L471 > > `>>> hex(465) '0x1d1' ` > > It sure looks like something is getting confused at the driver level as it shouldn't have 465 in there as...

> > https://github.com/hbldh/bleak/blob/aa24332a39952880005705155629df423fbad1aa/bleak/backends/_manufacturers.py#L471 > > `>>> hex(465) '0x1d1' ` > > It sure looks like something is getting confused at the driver level as it shouldn't have 465 in there...