Unique ID problem with BLE Beacons, Device Tracker, and Proximity

Configuration
1

I am struggling with the use of BLE beacons and how these are used to create device trackers with unique ID’s. I get the concept, it’s just that I cannot get around the issue of that the device tracker’s do not seem to have a unique ID.

I’m guessing that the solution is staring at me in the face, but I just cannot see what it is that I am doing incorrectly.

image
image966×320 18.1 KB

I get this message for all the device trackers created from BLE beacons, as seen below.

image
image1374×930 61.9 KB

This is the section on my configuration.yaml in which I define the device trackers.

# Device Trackers
device_tracker:
# BLE
  - platform: bluetooth_le_tracker
    track_new_devices: true
    track_battery: true
    interval_seconds: 5

This is the relevant section of my know_devices.yaml. All the mac addresses are unique and verified using nRF Connect on my Android device.

mobile_trevor:
  name: Trevor's OnePlus Nord2 5G
  mac: BT_D0:49:7C:xx:xx:xx
  icon: mdi:cellphone
  picture:
  track: true

keys_britta:
  name: B's Keys
  mac: BLE_7C:2F:80:xx:xx:xx
  icon: mdi:car-key
  picture:
  track: true

keys_spare:
  name: Spare Keys
  mac: BLE_7C:2F:80:xx:xx:xx
  icon: mdi:key-chain
  picture:
  track: true

keys_cleaner:
  name: Cleaner's Keys
  mac: BLE_7C:2F:80:xx:xx:xx
  icon: mdi:key-chain
  picture:
  track: true

keys_trevor:
  name: T's Keys
  mac: BLE_7C:2F:80:xx:xx:xx
  icon: mdi:car-key
  picture:
  track: true

This is my proximity.yaml which is referenced in configuration.yaml by
proximity: !include proximity.yaml

# Proximity sensors
home:
  devices:
    - device_tracker.keys_britta
    - device_tracker.keys_trevor
    - device_tracker.keys_cleaner
    - device_tracker.keys_spare
    - device_tracker.britta_s_samsung_s9
    - device_tracker.trevor_s_one_nord_5g
  tolerance: 10

britta:
  devices:
    - device_tracker.keys_britta
    - device_tracker.britta_s_samsung_s9
  tolerance: 10

trevor:
  devices:
    - device_tracker.keys_trevor
    - device_tracker.trevor_s_one_nord_5g
  tolerance: 10

cleaner:
  devices:
    - device_tracker.keys_cleaner
  tolerance: 10
  
spare_keys:
  devices:
    - device_tracker.keys_spare
  tolerance: 10

Not surprisingly the proximity entities are also suffering from the unique ID problem.

image
image1370×788 42.4 KB

2

Did you ever find a solution of creating a device_tracker with a unique_id ??

Krs

Mark

3

I’m not familiar with the device tracker integration, but can’t you just use the newer iBeacon Tracker integration to do this?