IRK Sensor/Onboarding for Private BLE

[margau]

Describe the problem you have/What new integration you would like
Let esphome provide the IRK (Identity Resolving Key) for devices to be used in the Home Assistant Private BLE integration.

Please describe your use case for this integration and alternatives you've tried:

Private BLE needs the IRK of a device, which apparently can be determined by peering a (e.g, android) device using bluetooth. With private BLE, esphome often is already present as bluetooth proxy, so the "onboarding" of a new device might be useful here also.

espresense as alternative firmware already does this (https://www.home-assistant.io/integrations/private_ble_device/#espresense), but needing another esp just to read out the IRK, while the remaining parts of the presence tracking are done by Private BLE/esphome bluetooth proxy (instead of espresense) is not straightforward.

[margau]

This is somewhat related to #2285, but not identical. 2285 is about handling IRK inside the tracking itself, while this is about initially determining the IRK (mainly for the existing private ble integration)

[agittins]

It looks a lot like someone has already written a component to do this: https://github.com/dgrnbrg/appdaemon-configs/tree/a5780a16e15b8b10f6dd1cdad20250adc13a9451/custom_components/irk_enrollment

It looks like it will require some updating to get it working with current esphome, but it looks like all the heavy lifting has been done already.

It would be great to have a component to do this, especially if it could be turned on and off as required (assuming it might have an impact on proxy performance). Likewise if it could be hooked into the Private BLE Device integration, to give a seamless enrolment into HA.

[dgrnbrg]

I updated my component so that it builds again, but I haven't tested it. I'd be happy to help fixing/testing when I can, but I have a very large amount of other ESPHome development I'm doing, and I won't be able to focus on the entire lifecycle of this until late summer or fall.

[myhomeiot]

You can use small fix

[dgrnbrg]

I've merged @myhomeiot's fix. Thank you!