hass-ember-mug-component: Bluetooth proxies are not working

Thank you so much for your hard work and dedication to making this issue work for those of us that only have proxies.

Excited to try.

Ok, I’ve done a lot of testing with the single Proxy I have, but as far as I can tell, there doesn’t seem to be anything I can do from the point of the integration.

The ESPHome Proxy seems to automatically disconnect from any device that hasn’t sent out a broadcast even if it is still actively connected and sending signals. This is probably just to ensure the three active spots are freed up. Sadly, the mug only does this in pairing mode.

Perhaps they will add an option to prevent this in future for active devices, but for now, the only options for proxies seem to be: A. Briefly enter pairing mode to reconnect when you want it to connect. B. Leave the device in pairing mode all the time and it will stay connected.

I will keep looking around for other options too. Maybe we can force it somehow. However, for now I will put this in the readme as current way to use it with proxies.

If anyone has any ideas please let me know though. I do want to make this work better.

I have the same problem with BT proxies. The mug worked fine when near to the adapter in the Pi, but was out of range in the kitchen. I have an ESP32-POE-ISO-EA which seems to be working fine, updated through ESPhome to latest firmware. I have updated to the beta Ember integration and not noticed much difference.

Some log info, from ESPhome: [13:54:14][D][esp32_ble_tracker:264]: Starting scan... [13:54:15][D][esp32_ble_client:039]: [0] [fa:71:15:24:9f:85] Found device [13:54:15][I][esp32_ble_client:054]: [0] [fa:71:15:24:9f:85] Attempting BLE connection [13:54:15][W][esp32_ble_client:106]: [0] [] Connection failed, status=133 [13:54:15][D][esp32_ble_tracker:264]: Starting scan... [13:54:16][D][esp32_ble_client:039]: [0] [fa:71:15:24:9f:85] Found device [13:54:16][I][esp32_ble_client:054]: [0] [fa:71:15:24:9f:85] Attempting BLE connection [13:54:16][W][esp32_ble_client:106]: [0] [] Connection failed, status=133 [13:54:16][D][esp32_ble_tracker:264]: Starting scan... [13:54:17][D][esp32_ble_client:039]: [0] [fa:71:15:24:9f:85] Found device [13:54:17][I][esp32_ble_client:054]: [0] [fa:71:15:24:9f:85] Attempting BLE connection [13:54:18][W][esp32_ble_client:106]: [0] [] Connection failed, status=133 [13:54:18][D][esp32_ble_tracker:264]: Starting scan... [13:54:19][D][esp32_ble_client:039]: [0] [fa:71:15:24:9f:85] Found device [13:54:19][I][esp32_ble_client:054]: [0] [fa:71:15:24:9f:85] Attempting BLE connection [13:54:19][W][esp32_ble_client:106]: [0] [] Connection failed, status=133 [13:54:19][D][esp32_ble_tracker:264]: Starting scan... [13:54:20][D][esp32_ble_client:039]: [0] [fa:71:15:24:9f:85] Found device [13:54:20][I][esp32_ble_client:054]: [0] [fa:71:15:24:9f:85] Attempting BLE connection [13:54:20][W][esp32_ble_client:106]: [0] [] Connection failed, status=133 [13:54:20][D][esp32_ble_tracker:264]: Starting scan...

Log from HA: `Logger: custom_components.ember_mug.coordinator Source: custom_components/ember_mug/coordinator.py:88 Integration: Ember Mug (documentation, issues) First occurred: 13:48:55 (7 occurrences) Last logged: 13:54:21

(FA:71:15:24:9F:85) - FA:71:15:24:9F:85 -> /org/bluez/hci1: Failed to connect: (FA:71:15:24:9F:85) - FA:71:15:24:9F:85 -> esp32-bluetooth-proxy-0464bc: Failed to connect: Error ESP_GATT_CONN_FAIL_ESTABLISH while connecting: Connection failed to establish: Interference/range; External Bluetooth adapter w/extension may help; Extension cables reduce USB 3 port interference`

What I see in the HA UI for the integration when the mug ISNT in pairing mode: Retrying setup: An error occurred updating mug: e=BleakAbortedError(’ (FA:71:15:24:9F:85) - FA:71:15:24:9F:85 -> esp32-bluetooth-proxy-0464bc: Failed to connect: Error

I see this in the logs when the mug IS in pairing mode: “Bluetooth GATT Error address=FA:71:15:24:9F:85 handle=36 error=5 description=Insufficient authentication”

In the proxy/ESP32 logs when the mug IS in pairing mode, I see this: `INFO Reading configuration /config/esphome/esp32-bluetooth-proxy-0464bc.yaml… INFO Starting log output from esp32-bluetooth-proxy-0464bc.local using esphome API INFO Successfully connected to esp32-bluetooth-proxy-0464bc.local [14:15:19][I][app:102]: ESPHome version 2022.11.4 compiled on Dec 5 2022, 13:17:22 [14:15:19][I][app:104]: Project esphome.bluetooth-proxy version 1.0

[14:15:20][C][logger:293]: Logger: [14:15:20][C][logger:294]: Level: DEBUG [14:15:20][C][logger:295]: Log Baud Rate: 115200 [14:15:20][C][logger:296]: Hardware UART: UART0 [14:15:20][C][bluetooth_proxy:051]: Bluetooth Proxy: [14:15:20][C][bluetooth_proxy:052]: Active: YES [14:15:20][C][safe_mode.button:022]: Safe Mode Button ‘Safe Mode Boot’ [14:15:20][C][safe_mode.button:022]: Icon: ‘mdi:restart-alert’ [14:15:20][C][esp32_ble_tracker:796]: BLE Tracker: [14:15:20][C][esp32_ble_tracker:797]: Scan Duration: 300 s [14:15:20][C][esp32_ble_tracker:798]: Scan Interval: 1100.0 ms [14:15:20][C][esp32_ble_tracker:799]: Scan Window: 1100.0 ms [14:15:20][C][esp32_ble_tracker:800]: Scan Type: ACTIVE [14:15:20][C][esp32_ble_tracker:801]: Continuous Scanning: True [14:15:20][C][captive_portal:088]: Captive Portal: [14:15:20][C][mdns:103]: mDNS: [14:15:20][C][mdns:104]: Hostname: esp32-bluetooth-proxy-0464bc [14:15:20][C][ota:093]: Over-The-Air Updates: [14:15:20][C][ota:094]: Address: esp32-bluetooth-proxy-0464bc.local:3232FA9-944A [14:15:20][C][api:138]: API Server: [14:15:20][C][api:139]: Address: esp32-bluetooth-proxy-0464bc.local:6053 [14:15:20][C][api:143]: Using noise encryption: NO [14:15:20][C][improv_serial:032]: Improv Serial: [14:16:06][I][esp32_ble_client:066]: [0] [fa:71:15:24:9f:85] Disconnecting. [14:16:06][D][esp32_ble_client:039]: [0] [fa:71:15:24:9f:85] Found device [14:16:06][I][esp32_ble_client:054]: [0] [fa:71:15:24:9f:85] Attempting BLE connection [14:16:07][W][esp32_ble_client:106]: [0] [] Connection failed, status=133 [14:16:07][D][esp32_ble_tracker:264]: Starting scan… [14:16:07][D][esp32_ble_client:039]: [0] [fa:71:15:24:9f:85] Found device [14:16:07][I][esp32_ble_client:054]: [0] [fa:71:15:24:9f:85] Attempting BLE connection [14:16:09][I][esp32_ble_client:154]: [0] [fa:71:15:24:9f:85] Service UUID: 0x1800 [14:16:09][I][esp32_ble_client:156]: [0] [fa:71:15:24:9f:85] start_handle: 0x1 end_handle: 0x7 [14:16:09][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic 0x2A00, handle 0x3, properties 0xa [14:16:09][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic 0x2A01, handle 0x5, properties 0x2 [14:16:09][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic 0x2A04, handle 0x7, properties 0x2 [14:16:09][I][esp32_ble_client:154]: [0] [fa:71:15:24:9f:85] Service UUID: 0x1801 [14:16:09][I][esp32_ble_client:156]: [0] [fa:71:15:24:9f:85] start_handle: 0x8 end_handle: 0xb [14:16:09][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic 0x2A05, handle 0xa, properties 0x20 [14:16:09][I][esp32_ble_client:154]: [0] [fa:71:15:24:9f:85] Service UUID: FC543622-236C-4C94-8FA9-944A3E5353FA [14:16:09][I][esp32_ble_client:156]: [0] [fa:71:15:24:9f:85] start_handle: 0xc end_handle: 0x33 [14:16:09][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic FC540001-236C-4C94-8FA9-944A3E5353FA, handle 0xe, properties 0xa [14:16:09][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic FC540002-236C-4C94-8FA9-944A3E5353FA, handle 0x10, properties 0x2 [14:16:09][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic FC540003-236C-4C94-8FA9-944A3E5353FA, handle 0x12, properties 0xa [14:16:09][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic FC540004-236C-4C94-8FA9-944A3E5353FA, handle 0x14, properties 0xa [14:16:09][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic FC540005-236C-4C94-83E5353FA, handle 0x16, properties 0x2 [14:16:09][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic FC540006-236C-4C94-8FA9-944A3E5353FA, handle 0x18, properties 0xa [14:16:09][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic FC540007-236C-4C94-8FA9-944A3E5353FA, handle 0x1a, properties 0x2 [14:16:09][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic FC540008-236C-4C94-8FA9-944A3E5353FA, handle 0x1c, properties 0x2 [14:16:09][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic FC54000A-236C-4C94-8FA9-944A3E5353FA, handle 0x1e, properties 0x8 [14:16:09][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic FC54000C-236C-4C94-8FA9-944A3E5353FA, handle 0x20, properties 0x2 [14:16:09][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic FC54000D-236C-4C94-8FA9-944A3E5353FA, handle 0x22, properties 0x2 [14:16:09][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic FC54000E-236C-4C94-8FA9-944A3E5353FA, handle 0x24, properties 0x2 [14:16:09][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic FC54000F-236C-4C94-8FA9-944A3E5353FA, handle 0x26, properties 0xa [14:16:09][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic FC540010-236C-4C94-8FA9-944A3E5353FA, handle 0x28, properties 0xa [14:16:09][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic FC540011-236C-4C94-8FA9-944A3E5353FA, handle 0x2a, properties 0xa [14:16:09][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic FC540012-236C-4C94-8FA9-944A3E5353FA, handle 0x2d, properties 0x10 [14:16:09][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic FC540014-236C-4C94-8FA9-944A3E5353FA, handle 0x30, properties 0xa [14:16:09][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic FC540013-236C-4C94-8FA9-944A3E5353FA, handle 0x32, properties 0x10 [14:16:09][I][esp32_ble_client:154]: [0] [fa:71:15:24:9f:85] Service UUID: 00001530-1212-EFDE-1523-785FEABCD123 [14:16:09][I][esp32_ble_client:156]: [0] [fa:71:15:24:9f:85] start_handle: 0x34 end_handle: 0xffff [14:16:09][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic 00001532-1212-EFDE-1523-785FEABCD123, handle 0x36, properties 0x4 [14:16:09][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic 00001531-1212-EFDE-1523-785FEABCD123, handle 0x38, properties 0x18 [14:16:09][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic 00001534-1212-EFDE-1523-785FEABCD123, handle 0x3b, properties 0x2 [14:16:09][D][esp32_ble_tracker:264]: Starting scan… [14:16:58][I][esp32_ble_client:066]: [0] [fa:71:15:24:9f:85] Disconnecting. [14:16:58][D][esp32_ble_client:039]: [0] [fa:71:15:24:9f:85] Found device [14:16:58][I][esp32_ble_client:054]: [0] [fa:71:15:24:9f:85] Attempting BLE connection [14:16:58][W][esp32_ble_client:106]: [0] [] Connection failed, status=133 [14:16:58][D][esp32_ble_tracker:264]: Starting scan… [14:16:59][D][esp32_ble_client:039]: [0] [fa:71:15:24:9f:85] Found device [14:16:59][I][esp32_ble_client:054]: [0] [fa:71:15:24:9f:85] Attempting BLE connection [14:17:01][I][esp32_ble_client:154]: [0] [fa:71:15:24:9f:85] Service UUID: 0x1800 [14:17:01][I][esp32_ble_client:156]: [0] [fa:71:15:24:9f:85] start_handle: 0x1 end_handle: 0x7 [14:17:01][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic 0x2A00, handle 0x3, properties 0xa [14:17:01][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic 0x2A01, handle 0x5, properties 0x2 [14:17:01][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic 0x2A04, handle 0x7, properties 0x2 [14:17:01][I][esp32_ble_client:154]: [0] [fa:71:15:24:9f:85] Service UUID: 0x1801 [14:17:01][I][esp32_ble_client:156]: [0] [fa:71:15:24:9f:85] start_handle: 0x8 end_handle: 0xb [14:17:01][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic 0x2A05, handle 0xa, properties 0x20 [14:17:01][I][esp32_ble_client:154]: [0] [fa:71:15:24:9f:85] Service UUID: FC543622-236C-4C94-8FA9-944A3E5353FA [14:17:01][I][esp32_ble_client:156]: [0] [fa:71:15:24:9f:85] start_handle: 0xc end_handle: 0x33 [14:17:01][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic FC540001-236C-4C94-8FA9-944A3E5353FA, handle 0xe, properties 0xa [14:17:01][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic FC540002-236C-4C94-8FA9-944A3E5353FA, handle 0x10, properties 0x2 [14:17:01][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic FC540003-236C-4C94-8FA9-944A3E5353FA, handle 0x12, properties 0xa [14:17:01][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic FC540004-236C-4C94-8FA9-944A3E5353FA, handle 0x14, properties 0xa [14:17:01][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic FC540005-236C-4C94-8FA9-944A3E5353FA, handle 0x16, properties 0x2 [14:17:01][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic FC540006-236C-4C94-8FA9-944A3E5353FA, handle 0x18, properties 0xa [14:17:01][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic FC540007-236C-4C94-8FA9-944A3E5353FA, handle 0x1a, properties 0x2 [14:17:01][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic FC540008-236C-4C94-8FA9-944A3E5353FA, handle 0x1c, properties 0x2 [14:17:01][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic FC54000A-236C-4C94-8FA9-944A3E5353FA, handle 0x1e, properties 0x8 [14:17:01][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic FC54000C-236C-4C94-8FA9-944A3E5353FA, handle 0x20, properties 0x2 [14:17:01][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic FC54000D-236C-4C94-8FA9-944A3E5353FA, handle 0x22, properties 0x2 [14:17:01][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic FC54000E-236C-4C94-8FA9-944A3E5353FA, handle 0x24, properties 0x2 [14:17:01][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic FC54000F-236C-4C94-8FA9-944A3E5353FA, handle 0x26, properties 0xa [14:17:01][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic FC540010-236C-4C94-8FA9-944A3E5353FA, handle 0x28, properties 0xa [14:17:01][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic FC540011-236C-4C94-8FA9-944A3E5353FA, handle 0x2a, properties 0xa [14:17:01][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic FC540012-236C-4C94-8FA9-944A3E5353FA, handle 0x2d, properties 0x10 [14:17:01][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic FC540014-236C-4C94-8FA9-944A3E5353FA, handle 0x30, properties 0xa [14:17:01][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic FC540013-236C-4C94-8FA9-944A3E5353FA, handle 0x32, properties 0x10 [14:17:01][I][esp32_ble_client:154]: [0] [fa:71:15:24:9f:85] Service UUID: 00001530-1212-EFDE-1523-785FEABCD123 [14:17:01][I][esp32_ble_client:156]: [0] [fa:71:15:24:9f:85] start_handle: 0x34 end_handle: 0xffff [14:17:01][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic 00001532-1212-EFDE-1523-785FEABCD123, handle 0x36, properties 0x4 [14:17:01][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic 00001531-1212-EFDE-1523-785FEABCD123, handle 0x38, properties 0x18 [14:17:01][I][esp32_ble_client:059]: [0] [fa:71:15:24:9f:85] characteristic 00001534-1212-EFDE-1523-785FEABCD123, handle 0x3b, properties 0x2 [14:17:01][D][esp32_ble_tracker:264]: Starting scan… [14:17:02][W][bluetooth_proxy.connection:054]: [0] [fa:71:15:24:9f:85] Error reading char/descriptor at handle 0x24, status=5 `

The BT proxy is in the same room and I have tried 0.5m away and 4m away from the mug with same results. and the proxy is on a table away from any interference.

I did try untrusting the mug from the adapter settings via VNC in the Pi bluez GUI in case is was conflicting, but that didnt help.

Is there a way to ‘pair’ the mug on another adapter and it still work when then brought into the range of the proxy?. Like I mentioned it was working previously close to the other adapte,r but was out of range where it is normally located. I added the proxy and located it nearby but it never connected (no available slot errors, thats why I untrusted it from the other adapter in case it was trying to make 2 connections etc).

I did try taking the mug back to the BT adapter connected to the Pi/HA and it was redetected perfectly straight away. But then moving it back near the proxy adapter i just see the connection errors in the logs like: [13:54:20][D][esp32_ble_client:039]: [0] [fa:71:15:24:9f:85] Found device [13:54:20][I][esp32_ble_client:054]: [0] [fa:71:15:24:9f:85] Attempting BLE connection [13:54:20][W][esp32_ble_client:106]: [0] [] Connection failed, status=133]

And of course then the entities for the mug just stop updating,

I’m happy to try anything to get it working 😃