Issue with iBeacons from UUID in Passive BLE Monitor Integration

[praguevara]

Hello,

I've been working on integrating a few iBeacon devices into the Passive BLE Monitor within Home Assistant, using UUIDs for identification. However, I noticed an issue where these devices only function correctly when the discovery mode is enabled.

Upon further investigation, I suspect this issue is related to the ble_gateway component primarily filtering on MAC addresses. Hence, the UUID-based iBeacons do not seem to automatically update as expected.

I believe this behavior might not be immediately clear for other users as well, especially those who are working with iBeacons or other BLE devices identified by UUID. Therefore, I suggest that the documentation could benefit from an update to provide clarity on this specific behavior.

Moreover, I'd like to propose a feature request: Would it be possible to enhance the ble_gateway component to allow automatic updates for UUID-based devices in the same manner as it does for MAC-based devices? This feature could significantly improve the usability and versatility of the Passive BLE Monitor integration.

[myhomeiot]

Hello, please check #4 it's has a example how to filter beacons by UUID. At the time of #4 Passive BLE Monitor doesn't support UUIDs, but you right, today it's can be useful to have it on BLE Gateway. Just for my understanding, today Home Assistant and ESPHome has Bluetooth Proxy support, why you use Passive BLE Monitor?