Bermuda BLE Trilateration

Configuration - Home Assistant Core: 2026.6.4 - Home Assistant OS: 18.0 - Supervisor: 2026.06.2 - Bermuda: 0.8.5 - HomeKit Controller is installed and has active devices. ## Describe the bug Bermuda's `device_registry_updated` callback assumes every device identifier contains exactly two elements: [code] HomeKit Controller devices can have three-element identifiers. When one of these device registry entries is updated, Bermuda raises `ValueError: too many values to unpack (expected 2, got 3)` and aborts the callback. This occurred once on June 22, 2026 immediately after Home Assistant startup …

Excerpt saved from GitHub on 2026-10-23.

… its no problem that the answer tooks a little bit longer, i`m happy about getting an answer :) If i take a look to the data sheet of my ESP i have an ESP32 (not S3 or C3). My ESP32s are the following ones: diymore ESP32 Mini Development Board ESP32 NodeMCU WiFi Bluetooth ESP32 CH9102F Chip Typ C The first time commissioning and flashing was via USB and the esp ready-made Project. After that i did an firmwareupdate via OTA to all of the ESPs. Your named content of the section i couldn`T find in my yamls. My have the following Content. Proxy 1 ``` substitutions: name: …

Excerpt saved from GitHub on 2026-10-23.

Hi, I use a USB Bluetooth dongle connected directly to the mini PC running Home Assistant. The integration doesn't work; no devices or scanners are detected. This dongle works with iBeacon integration, but maybe it doesn't work with Bermuda integration? This is the error in the registry ``` Registratore: homeassistant.config_entries Fonte: config_entries.py:762 Prima occorrenza: 21:44:02 (4 occorrenze) Ultimo accesso: 21:47:01 Error setting up entry Bermuda BLE Trilateration for bermuda Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/config_entries.py", line 762, …

Excerpt saved from GitHub on 2026-10-23.

… on: #816, Original Author: https://github.com/daviddelahoz Added improvements requested by Bermuda repo owner. As per original author: Discover enabled rolling-key devices from the FindMy integration. Create one stable Bermuda metadevice per FindMy accessory while following its confirmed rolling Bluetooth address. Accept only locally detected addresses with a recent, timezone-aware detection timestamp. Link Bermuda entities to the originating FindMy device-registry identifier so area, distance, current MAC, and presence remain on one device. Add focused tests for fresh/stale source handling …

Excerpt saved from GitHub on 2026-10-23.