ESP32 BLE iBeacon: alias for UID and not MAC based

[Eisbahn]

Dear Tasmota team,

I'm trying to create some simple presence detection for my home based on BLE and therefore using an ESP32 with latest Tasmota BLE 14.4.1 from 2024-12-15T13:32:56
As goal I would like to track my Android devices (tablet, mobile...) and have installed BeaconScope on them as I couldn't find a way to see them with just the stock BT turned on in Android settings in Tasmota BLE menue. As long as the BeaconScope App is on, an iBeacon is send.
After the commands
SetOption115 1 IBEACON 1 BLEAddrFilter 3 BLEMaxAge 120
I also see my created iBeacon in the console and also under configuration -> BLE in Tasmota
14:30:40.376 RSL: SENSOR = {"Time":"2025-02-16T14:30:40","IBEACON":{"UID":"2F234454CF6D4A0FADF2F4911BA9FFA1","MAJOR":"0001","MINOR":"0001","MAC":"79AACC89A2A5","RSSI":-38,"STATE":"ON","PERSEC":0}}
Sadly it seems there are lots of devices, hence I would like to limit the tracking to my known ones. Is there any chance to limit the MQTT forwarding based on the UID? Background: the MAC is changing and therefore useless for filtering...
Is there maybe another/better way to track Android devices?

Any help would be great

[sfromis]

What I do on my Android devices (even without using them as beacons) is to config them to use device MAC instead of the impractical dynamically generated one.

[Eisbahn]

That would help me and would solve my problem, as an alias would work if the MAC would be static. But how do I set that in Android?
For Ehternet I'm using already a static MAC (WiFi -> SSID -> options -> more -> address type), also seen in dev menu (random MAC slider is off) long time ago due to some WiFi rules. But for BT and/or BLE I couldn't find any option in the settings (tablet and mobile are both Samsung ones). Also google just pointed me to the WiFi settings...

[sfromis]

Well ok, I've not checked details with Bluetooth, my main interest is Wifi where it usually should be easy to find. And my rural house is free from "congestion" with my devices being the only ones in range. But it does indeed look like MAC randomization is not optional on Android either, maybe up to what distro you use or developer options.

You can still create Berry code to react to the "usual suspects", ignoring other devices popping in

Of course, running a beacon app defeats the whole anti-tracking purpose of randomizing the MAC.

[Eisbahn]

Hmmm, have tried it without success, as I'm new to BerryCode and have never used it before. Could you maybe have an example or some proper docs?
And yes, tracking individual devices is possible afterwards.
However: I (by accident) closed the BeaconScope app on my Android and no more tracking is possible. As I quite often use the close all tabs button on my devices, I'll propably go with HW tags/beacons which, hopefully they do have a static MAC.

[sfromis]

https://tasmota.github.io/docs/Berry/#rules

tasmota.add_rule('IBEACON#UID=2F234454CF6D4A0FADF2F4911BA9FFA1',
  def (value, trigger, payload, bin)
    print('RSSI',payload['RSSI'])
  end)

This rudimentary example is not meant to be practical, merely to illustrate how things can be picked up from the MQTT-oriented payloads (even when not connected).

And of course, starting a phone app does have the risk that it will not remain started. It is not even unusual for phone makers to include features to kill background apps.

[Eisbahn]

thanks a lot, quite powerful those rules/script language. Never used it before