Bluetooth proxy not proxying

ESPHome
1

in order to connect a InkBird IBS-TH2 sensor to homeassistant I have set up an ESP32-WROOM-32 board with the package from the ready-made page.

After detection I have “adopted” the board.

Problem is, the InkBird sensor is not detected. No bluetooth devices at all show up In the default ESP-Log.

After increasing the log level to extra-verbose I can see that messages from various devices are received. The InkBird sensor (recognizable by its adress (49:23:04:08:0A:2E) which I got from the Engbird-App), and my Jabra Headset among them.

[19:58:21][V][esp32_ble:314]: (BLE) gap_event_handler - 3
[19:58:21][VV][esp32_ble_tracker:423]: Parse Result:
[19:58:21][VV][esp32_ble_tracker:440]:   Address: 5B:2D:BB:ED:84:12 (RANDOM)
[19:58:21][VV][esp32_ble_tracker:442]:   RSSI: -95
[19:58:21][VV][esp32_ble_tracker:443]:   Name: 'Jabra Evolve2 65'
[19:58:21][VV][esp32_ble_tracker:451]:   Ad Flag: 26
[19:58:21][VV][esp32_ble_tracker:454]:   Service UUID: 0x180F
[19:58:21][VV][esp32_ble_tracker:454]:   Service UUID: 0x180A
[19:58:21][VV][esp32_ble_tracker:454]:   Service UUID: 0xFEFF
[19:58:21][VV][esp32_ble_tracker:473]: Adv data: 02.01.1A.07.03.0F.18.0A.18.FF.FE.11.09.4A.61.62.72.61.20.45.76.6F.6C.76.65.32.20.36.35 (29)
[19:58:59][V][esp32_ble:314]: (BLE) gap_event_handler - 3
[19:58:59][VV][esp32_ble_tracker:423]: Parse Result:
[19:58:59][VV][esp32_ble_tracker:440]:   Address: 49:23:04:08:0A:2E (PUBLIC)
[19:58:59][VV][esp32_ble_tracker:442]:   RSSI: -39
[19:58:59][VV][esp32_ble_tracker:443]:   Name: 'TST'
[19:58:59][VV][esp32_ble_tracker:451]:   Ad Flag: 6
[19:58:59][VV][esp32_ble_tracker:454]:   Service UUID: 0xFFF0
[19:58:59][VV][esp32_ble_tracker:457]:   Manufacturer data: 93.14.00.FC.B7.64.08 (7)
[19:58:59][VV][esp32_ble_tracker:473]: Adv data: 02.01.06.03.02.F0.FF.04.09.54.53.54.0A.FF.2B.09.93.14.00.FC.B7.64.08 (23)
[19:59:00][V][esp32_ble:314]: (BLE) gap_event_handler - 3
[19:59:00][VV][esp32_ble_tracker:423]: Parse Result:
[19:59:00][VV][esp32_ble_tracker:440]:   Address: 49:23:04:08:0A:2E (PUBLIC)
[19:59:00][VV][esp32_ble_tracker:442]:   RSSI: -40
[19:59:00][VV][esp32_ble_tracker:443]:   Name: 'sps'
[19:59:00][VV][esp32_ble_tracker:451]:   Ad Flag: 6
[19:59:00][VV][esp32_ble_tracker:454]:   Service UUID: 0xFFF0
[19:59:00][VV][esp32_ble_tracker:457]:   Manufacturer data: 93.14.00.FC.B7.64.08 (7)
[19:59:00][VV][esp32_ble_tracker:473]: Adv data: 02.01.06.03.02.F0.FF.04.09.73.70.73.0A.FF.2B.09.93.14.00.FC.B7.64.08 (23)
[19:59:00][V][esp32_ble:314]: (BLE) gap_event_handler - 3
[19:59:00][VV][esp32_ble_tracker:423]: Parse Result:
[19:59:00][VV][esp32_ble_tracker:440]:   Address: 49:23:04:08:0A:2E (PUBLIC)
[19:59:00][VV][esp32_ble_tracker:442]:   RSSI: -38
[19:59:00][VV][esp32_ble_tracker:443]:   Name: 'sps'
[19:59:00][VV][esp32_ble_tracker:451]:   Ad Flag: 6
[19:59:00][VV][esp32_ble_tracker:454]:   Service UUID: 0xFFF0
[19:59:00][VV][esp32_ble_tracker:457]:   Manufacturer data: 93.14.00.FC.B7.64.08 (7)
[19:59:00][VV][esp32_ble_tracker:473]: Adv data: 02.01.06.03.02.F0.FF.04.09.73.70.73.0A.FF.2B.09.93.14.00.FC.B7.64.08 (23)
[19:59:04][V][esp32_ble:314]: (BLE) gap_event_handler - 3

Any ideas whats going wrong here?

2

The device (“sps”) should be detected by HA, not ESPHome

3

yes, “should be” is correct :sunglasses:

but there are no “Proxying packet from” packets in the log
so there might be nothing for HA to detect

4

I have updated my Bluetooth proxies to 2023.12.7 and the vast majority of my Bluetooth temperature sensors are now mostly unavailable.

Prior to this on a 2023.11.X version sensors were very occasionally unavailable.

New version:

image
image739×607 21.8 KB

And here is a longer graph, you can clearly see when I installed the latest updates to the Bluetooth proxies yesterday.

image
image1852×762 52.8 KB

The proxies have not been moved, and the temperature sensors have not been moved. This is purely a software issue.

5

it gets more interessting: I’ve setup a second, identical esp32 board (from the same delivery). With this board the proxy works flawlessly.