iBeacon tracker + bluetooth proxy issues vs ESPresense

I bought a couple of ESP32 boards to have a play with ESPresense and Bluetooth Proxies and over the last few hours have been running a comparison between the two mechanisms for tracking an Android phone with the companion app BLE transmitter enabled.

This is what ESPresence sees:
Screenshot 2022-11-16 111154

And ESPHome Bluetooth Proxy + iBeacon Tracker intergration:
Screenshot 2022-11-16 111015

There is clearly something wrong with the config of the proxy, but can anyone provide any clues as to what? Here is the config, which I believe is pretty close to the standard one.

esphome:
  name: '${name}'
  name_add_mac_suffix: true
  project:
    name: 'esphome.bluetooth-proxy'
    version: "1.0"

esp32:
  board: nodemcu-32s

# WiFi credentials #
wifi:
  ssid: 'xxx'
  password: 'yyy'
  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: '${device_name}'

web_server:
  port: 80

api:
logger:
ota:
improv_serial:
captive_portal:

dashboard_import:
  package_import_url: 'github://esphome/bluetooth-proxies/esp32-generic.yaml@main'

esp32_ble_tracker:
  scan_parameters:
    interval: 1100ms
    window: 1100ms
    active: true
  
bluetooth_proxy:
  active: true

button:
- platform: safe_mode
  name: Safe Mode Boot
  entity_category: diagnostic

Thanks in advance.

Looks like there are issues with ESPHome and the iBeacon integration. I think I’ll wait for this to be resolved before spending any more time on it: ESPHome with bluetooth proxy and iBeacon integration · Issue #79781 · home-assistant/core · GitHub

2 Likes

Sorry to bring up an old post - did you end up resolving this? Are you sticking to one solution now?