iBeacon keeps generating new devices for the same pixel watch

[upper lance]

all of those duplicate entries come from my one watch and whenever a new one appears, the old one stops working, and i don't know what the deal is or how to fix this. frankly i dont even know how to configure things like transmit power in the HA wearos app

[ornate tusk]

The beacon rotates so you cant be tracked by it. You need to get the IRK then add it as a private IRK, that way home assistant can decode the beacon and detect the device as it rotates.

Getting the IRK is the next battle... Do you have a spare esp32 by any chance?

[upper lance]

Oh I've literally done that before, I've got a rooted android phone it's hilariously easy

Just didn't know that affected ibeacons

[upper lance]

So I add a private ble device or do I add it to the ibeacon thing somehow?

[ornate tusk]

Once you have the irk you add it via the Private BLE Device integration.

[upper lance]

I see, and then I just use the ibeacon integration as normal after that?

Or do I use the ble for tracking

[ornate tusk]

You ignore the ibeacon stuff once you have the IRK, you use the device created in the private ble devices integration.

I also recommend installing Bermuda from HACS. gives you some nice extra stuff.

[upper lance]

-# i do have this actually

i had a lot of this configured and i deleted half of it cause it was buggy and inconsistent

but i didnt fully get everything

i didnt realize you needed ibeacon on anyways to do ble for phones and stuff, and yet that you shouldnt use the ibeacon integration for that

[ornate tusk]

The ibeacon is the ping but you need to be able to decode it to track. Which is a good thing really. otherwise it would be super easy to track any device.

[upper lance]

fair enough