[APP][Pro] Blueriiot Blue Connect Local

Hello guys,

This topic can be used for support questions, feature suggestions and bug reports related to the Blueriiot Blue Connect Local app.

In contrary to the other community app, this app does not make use of the Blueriiot API, rather it uses local connectivity. This offers a number of benefits: you are no longer depending on the cloud for your measurements and you can take as many measurements as you want on the times you want.

In the current version the app supports direct BLE connectivity from Homey, as well as the use of an ESPHome Bluetooth Proxy.

The app itself can be found in the Homey store on the following locations:

I’ve developed this app in a full open-source mindset, the source code is available under a GPL-license, meaning that everyone is allowed to use it provided that they release their source code under a GPL-compliant license. You can find the source code of the application in my GitLab repository at:

Any issues which are found in the app, or features which I’m still considering to be adopted, can be found in the GitLab issue tracker at:

Anyone is free to contribute towards the app, you can simply fork the repository on GitLab and create a merge request with your changes, I’ll review them and most likely include them as part of the app.

If you want, you can buy me a beer, or send me a donation using:

I really hope you enjoy the app, and any feedback is always welcome! I try to respond to all requests as soon as possible, but be aware that I have a regular job too, which might imply that sometimes it takes a bit longer then on other times.

Kind regards,

great App.
Very usefull, thanx for your work

Hi, I’m having problems using BlueConnect Local through an ESPHome Bluetooth Proxy.

Setup:

  • Homey Pro Early 2023
  • Blueriiot BlueConnect Local
  • Blue Connect sensor MAC: 00:A0:50:D8:D4:9A
  • ESP32-WROOM / NodeMCU style ESP32
  • ESPHome proxy using the YAML from the project repository
  • ESPHome API encryption enabled
  • ESP32 proxy IP: 192.168.1.91

What works:

  • Direct BLE mode works when the Blue Connect is close to Homey
  • ESPHome proxy connects to Homey successfully
  • Homey discovers the Blue Connect through the ESPHome proxy
  • The device can be added in Homey

What fails:

  • Take a measurement does not populate temperature, pH, ORP or battery
  • All capabilities remain empty/null in Homey
  • ESPHome sees the Blue Connect and attempts to connect, but the BLE/GATT connection fails

Relevant ESPHome log:

Connecting v3 without cache
Timeout waiting for teardown
OPEN_EVT in unexpected state
Connection open failed, status=133
Disconnected, reason=0x08 / 0x85

I first tested ESPHome 2026.9.1, then downgraded to 2026.7.2, but the behavior is the same.

The ESP32 is placed very close to the Blue Connect, so this does not appear to be a range issue.

Is there a known issue with ESPHome proxy mode, or is there a specific ESPHome version / ESP-IDF version / ESP32 board that is known to work reliably? https://www.amazon.se/dp/B0D9BTQRYT

Additional log detail:
@2colors/esphome-native-api 1.3 connects successfully, but ESPHome reports:
using outdated API 0.0, update to 1.14+

BLE still fails with:
ESP_GATTC_OPEN_EVT in DISCONNECTING state (status=133)
Connection open error, status=133

Hey @henqo

I might have found something that could fix your issues. Unsure though that it will work.

Could you try with v0.2.6 which is published towards test and is available from Blueriiot BlueConnect Local | Homey

Thanks!

Thanks! I tested v0.2.6, but unfortunately I still get the same BLE/GATT failure through the ESPHome proxy.

Homey connects to the ESPHome proxy successfully and the Blue Connect is discovered, but the connection still fails with:

ESP_GATTC_OPEN_EVT in DISCONNECTING state (status=133)
Connection open error, status=133

The device MAC is still 00:A0:50:D8:D4:9A.

The log also still shows:

@2colors/esphome-native-api 1.3 using outdated API 0.0, update to 1.14+

Direct BLE from Homey works when the Blue Connect is close enough, so the sensor itself seems OK.

Hey @henqo

I’ll have a deeper look during the next days, it should work as I’ve been using it all summer with ESPHome as BLE Proxy, but have to fire up the setup again as my pool is currently closed for winter.

Kind regards,

Thanks, no problem at all.

I’ll leave my setup unchanged for now so we have a stable reference when you get a chance to test it again.

Let me know if you want any additional logs or configuration details from my setup.

Hey,

For me it still looks to work - the message you get is barely a warning, it should not block the reading.

Is there any other output on the ESPHome device? Maybe a complete log could help me to dig deeper into this.

Kind regards,

Thanks — I managed to capture a complete DEBUG log now.

After removing and re-adding the Blue Connect device in Homey, the ESPHome proxy is again receiving the BLE connection requests.

The important part is that I can reproduce the issue consistently. There are several separate connection attempts to:

00:A0:50:D8:D4:9A

Each attempt starts normally with:

Connecting v3 without cache
Stopping scan to make connection
Promoting client to connect
Connecting

but eventually ends with:

ESP_GATTC_DISCONNECT_EVT, reason 0x100
ESP_GATTC_OPEN_EVT in DISCONNECTING state (status=133)
Connection open error, status=133

I also notice that the Homey ESPHome client at 192.168.1.172 disconnects/reconnects around some of these attempts, and the log still shows:

@2colors/esphome-native-api 1.3 using outdated API 0.0, update to 1.14+

Full log:
[08:43:00.503][C][api:269]: Server:
[08:43:00.503][C][api:269]: Address: bleproxy.local:6053
[08:43:00.503][C][api:269]: Listen backlog: 2
[08:43:00.503][C][api:269]: Max connections: 6
[08:43:00.504][C][api:276]: Noise encryption: YES
[08:43:00.577][C][mdns:259]: mDNS:
[08:43:00.577][C][mdns:259]: Hostname: bleproxy
[08:46:54.877][D][wifi:2474]: Roam scan (-53 dBm, attempt 1/3)
[08:47:37.393][D][api:253]: Accept 192.168.1.172
[08:47:37.490][W][api.connection:1751]: ‘@2colors/esphome-native-api 1.3’ using outdated API 0.0, update to 1.14+
[08:47:37.576][D][api.connection:2526]: @2colors/esphome-native-api 1.3 (192.168.1.172): connected
[08:47:47.312][D][api.connection:2526]: @2colors/esphome-native-api 1.3 (192.168.1.172): disconnected
[08:47:47.407][W][api.connection:2532]: @2colors/esphome-native-api 1.3 (192.168.1.172): Reading failed CONNECTION_CLOSED errno=128
[08:47:52.743][D][api:253]: Accept 192.168.1.172
[08:47:52.848][W][api.connection:1751]: ‘@2colors/esphome-native-api 1.3’ using outdated API 0.0, update to 1.14+
[08:47:52.849][D][api.connection:2526]: @2colors/esphome-native-api 1.3 (192.168.1.172): connected
[08:47:53.773][I][bluetooth_proxy:059]: [0] [00:A0:50:D8:D4:9A] Connecting v3 without cache
[08:47:53.789][D][esp32_ble_tracker:169]: connecting: 0, discovered: 1, disconnecting: 0, active: 0
[08:47:53.789][D][esp32_ble_tracker:909]: Stopping scan to make connection
[08:47:53.790][D][esp32_ble_tracker:917]: Promoting client to connect
[08:47:53.802][D][esp32_ble_tracker:953]: Setting coexistence to Bluetooth to make connection.
[08:47:53.803][I][esp32_ble_client:126]: [0] [00:A0:50:D8:D4:9A] 0x00 Connecting
[08:47:53.803][D][esp32_ble_client:232]: [0] [00:A0:50:D8:D4:9A] fast conn params
[08:47:53.851][D][esp32_ble_tracker:169]: connecting: 1, discovered: 0, disconnecting: 0, active: 0
[08:48:03.302][D][esp-idf:000][BTU_TASK]: W (382407) BT_HCI: hcif disc complete: hdl 0x0, rsn 0x3e dev_find 1
[08:48:03.803][D][esp32_ble_client:157]: [0] [00:A0:50:D8:D4:9A] Disconnect before connected, disconnect scheduled
[08:48:05.831][D][esp-idf:000][BTU_TASK]: W (384926) BT_HCI: hcif disc complete: hdl 0x0, rsn 0x3e dev_find 1
[08:48:07.082][D][esp-idf:000][BTU_TASK]: W (386187) BT_HCI: hcif disc complete: hdl 0x0, rsn 0x3e dev_find 1
[08:48:08.330][D][esp-idf:000][BTU_TASK]: W (387436) BT_HCI: hcif disc complete: hdl 0x0, rsn 0x3e dev_find 1
[08:48:08.823][D][esp32_ble_client:157]: [0] [00:A0:50:D8:D4:9A] Disconnect before connected, disconnect scheduled
[08:48:09.621][D][esp-idf:000][BTU_TASK]: W (388686) BT_HCI: hcif disc complete: hdl 0x0, rsn 0x3e dev_find 1
[08:48:10.849][D][esp-idf:000][BTU_TASK]: W (389936) BT_HCI: hcif disc complete: hdl 0x0, rsn 0x3e dev_find 1
[08:48:12.097][D][esp-idf:000][BTU_TASK]: W (391196) BT_HCI: hcif disc complete: hdl 0x0, rsn 0x3e dev_find 1
[08:48:13.111][D][esp32_ble_client:380]: [0] [00:A0:50:D8:D4:9A] ESP_GATTC_DISCONNECT_EVT, reason 0x100
[08:48:13.111][D][bluetooth_proxy.connection:383]: [0] [00:A0:50:D8:D4:9A] Disconnect, reason=0x100
[08:48:13.114][D][esp32_ble_client:212]: [0] [00:A0:50:D8:D4:9A] ESP_GATTC_OPEN_EVT
[08:48:13.115][E][esp32_ble_client:325]: [0] [00:A0:50:D8:D4:9A] ESP_GATTC_OPEN_EVT in DISCONNECTING state (status=133)
[08:48:13.115][W][esp32_ble_client:224]: [0] [00:A0:50:D8:D4:9A] Connection open error, status=133
[08:48:13.115][D][esp32_ble_tracker:169]: connecting: 0, discovered: 0, disconnecting: 0, active: 0
[08:48:13.116][D][esp32_ble_tracker:957]: Setting coexistence preference to balanced.
[08:48:13.228][W][api.connection:2532]: @2colors/esphome-native-api 1.3 (): Packet write failed SOCKET_WRITE_FAILED errno=128
[08:48:13.228][D][api:253]: Accept 192.168.1.172
[08:48:13.332][W][api.connection:1751]: ‘@2colors/esphome-native-api 1.3’ using outdated API 0.0, update to 1.14+
[08:48:13.336][D][api.connection:2526]: @2colors/esphome-native-api 1.3 (192.168.1.172): connected
[08:48:14.148][I][bluetooth_proxy:059]: [0] [00:A0:50:D8:D4:9A] Connecting v3 without cache
[08:48:14.163][D][esp32_ble_tracker:169]: connecting: 0, discovered: 1, disconnecting: 0, active: 0
[08:48:14.163][D][esp32_ble_tracker:909]: Stopping scan to make connection
[08:48:14.163][D][esp32_ble_tracker:917]: Promoting client to connect
[08:48:14.175][D][esp32_ble_tracker:953]: Setting coexistence to Bluetooth to make connection.
[08:48:14.237][I][esp32_ble_client:126]: [0] [00:A0:50:D8:D4:9A] 0x00 Connecting
[08:48:14.238][D][esp32_ble_client:232]: [0] [00:A0:50:D8:D4:9A] fast conn params
[08:48:14.241][D][esp32_ble_tracker:169]: connecting: 1, discovered: 0, disconnecting: 0, active: 0
[08:48:24.182][D][esp32_ble_client:157]: [0] [00:A0:50:D8:D4:9A] Disconnect before connected, disconnect scheduled
[08:48:27.162][D][esp-idf:000][BTU_TASK]: W (406267) BT_HCI: hcif disc complete: hdl 0x0, rsn 0x3e dev_find 1
[08:48:29.198][D][esp32_ble_client:157]: [0] [00:A0:50:D8:D4:9A] Disconnect before connected, disconnect scheduled
[08:48:34.197][D][esp32_ble_client:380]: [0] [00:A0:50:D8:D4:9A] ESP_GATTC_DISCONNECT_EVT, reason 0x100
[08:48:34.197][D][bluetooth_proxy.connection:383]: [0] [00:A0:50:D8:D4:9A] Disconnect, reason=0x100
[08:48:34.200][D][esp32_ble_client:212]: [0] [00:A0:50:D8:D4:9A] ESP_GATTC_OPEN_EVT
[08:48:34.200][E][esp32_ble_client:325]: [0] [00:A0:50:D8:D4:9A] ESP_GATTC_OPEN_EVT in DISCONNECTING state (status=133)
[08:48:34.200][W][esp32_ble_client:224]: [0] [00:A0:50:D8:D4:9A] Connection open error, status=133
[08:48:34.215][D][esp32_ble_tracker:169]: connecting: 0, discovered: 0, disconnecting: 0, active: 0
[08:48:34.215][D][esp32_ble_tracker:957]: Setting coexistence preference to balanced.
[08:48:35.036][W][api.connection:2532]: ESPHome Logs 2026.7.2 (): Reading failed SOCKET_READ_FAILED errno=128
[08:50:32.927][D][api.connection:2526]: @2colors/esphome-native-api 1.3 (192.168.1.172): disconnected
[08:50:33.010][W][api.connection:2532]: @2colors/esphome-native-api 1.3 (192.168.1.172): Reading failed CONNECTION_CLOSED errno=128
[08:50:33.010][D][api:253]: Accept 192.168.1.172
[08:50:33.108][W][api.connection:1751]: ‘@2colors/esphome-native-api 1.3’ using outdated API 0.0, update to 1.14+
[08:50:33.194][D][api.connection:2526]: @2colors/esphome-native-api 1.3 (192.168.1.172): connected
[08:50:34.029][I][bluetooth_proxy:059]: [0] [00:A0:50:D8:D4:9A] Connecting v3 without cache
[08:50:34.040][D][esp32_ble_tracker:169]: connecting: 0, discovered: 1, disconnecting: 0, active: 0
[08:50:34.040][D][esp32_ble_tracker:909]: Stopping scan to make connection
[08:50:34.047][D][esp32_ble_tracker:917]: Promoting client to connect
[08:50:34.048][D][esp32_ble_tracker:953]: Setting coexistence to Bluetooth to make connection.
[08:50:34.048][I][esp32_ble_client:126]: [0] [00:A0:50:D8:D4:9A] 0x00 Connecting
[08:50:34.048][D][esp32_ble_client:232]: [0] [00:A0:50:D8:D4:9A] fast conn params
[08:50:34.149][D][esp32_ble_tracker:169]: connecting: 1, discovered: 0, disconnecting: 0, active: 0
[08:50:39.033][D][esp-idf:000][BTU_TASK]: W (538038) BT_HCI: hcif disc complete: hdl 0x0, rsn 0x3e dev_find 1
[08:50:40.191][D][esp-idf:000][BTU_TASK]: W (539297) BT_HCI: hcif disc complete: hdl 0x0, rsn 0x3e dev_find 1
[08:50:41.492][D][esp-idf:000][BTU_TASK]: W (540547) BT_HCI: hcif disc complete: hdl 0x0, rsn 0x3e dev_find 1
[08:50:42.720][D][esp-idf:000][BTU_TASK]: W (541797) BT_HCI: hcif disc complete: hdl 0x0, rsn 0x3e dev_find 1
[08:50:45.200][D][esp-idf:000][BTU_TASK]: W (544307) BT_HCI: hcif disc complete: hdl 0x0, rsn 0x3e dev_find 1
[08:50:47.736][D][esp-idf:000][BTU_TASK]: W (546817) BT_HCI: hcif disc complete: hdl 0x0, rsn 0x3e dev_find 1
[08:50:48.965][D][esp-idf:000][BTU_TASK]: W (548067) BT_HCI: hcif disc complete: hdl 0x0, rsn 0x3e dev_find 1
[08:50:50.220][D][esp-idf:000][BTU_TASK]: W (549328) BT_HCI: hcif disc complete: hdl 0x0, rsn 0x3e dev_find 1
[08:50:51.526][D][esp-idf:000][BTU_TASK]: W (550577) BT_HCI: hcif disc complete: hdl 0x0, rsn 0x3e dev_find 1
[08:50:52.757][D][esp-idf:000][BTU_TASK]: W (551837) BT_HCI: hcif disc complete: hdl 0x0, rsn 0x3e dev_find 1
[08:50:53.780][D][esp32_ble_client:380]: [0] [00:A0:50:D8:D4:9A] ESP_GATTC_DISCONNECT_EVT, reason 0x100
[08:50:53.780][D][bluetooth_proxy.connection:383]: [0] [00:A0:50:D8:D4:9A] Disconnect, reason=0x100
[08:50:53.784][D][esp32_ble_client:212]: [0] [00:A0:50:D8:D4:9A] ESP_GATTC_OPEN_EVT
[08:50:53.785][E][esp32_ble_client:325]: [0] [00:A0:50:D8:D4:9A] ESP_GATTC_OPEN_EVT in DISCONNECTING state (status=133)
[08:50:53.785][W][esp32_ble_client:224]: [0] [00:A0:50:D8:D4:9A] Connection open error, status=133
[08:50:53.792][D][esp32_ble_tracker:169]: connecting: 0, discovered: 0, disconnecting: 0, active: 0
[08:50:53.793][D][esp32_ble_tracker:957]: Setting coexistence preference to balanced.

Hey @henqo

At first sight, I don’t get much wiser from the ESPHome log, but after some discussions with AI I came a bit further.

The following suggestions came out of the AI prompts:

  1. The Blue Connect is connected to something else. A phone with the Blue Riot app, or a second proxy, will make it ignore other centrals. The user should force-close the app and turn off Bluetooth on nearby phones.
  2. The sensor is asleep or too far away. The Blue Connect only advertises briefly and has weak radio output. The ESP saw it advertise (discovered: 1) but couldn’t hold a link, which suggests marginal signal. The proxy should sit within a few metres of the sensor, ideally with line of sight.

I’ve also made some further stability improvements to the app in v0.2.7 for ESPHome.

Kind regards,

Hi Kenny,

Thanks again for your continued help!

I’ve now done some additional testing, including trying a completely different ESP32 board.

Here’s what I’ve tested so far:

  • Updated the Blueriiot BlueConnect Local app to v0.2.7.

  • Turned off Bluetooth on nearby phones and closed the Blueriiot app.

  • Placed the ESP32 proxy very close to the Blue Connect sensor.

  • Tested two separate ESP32-WROOM-32 boards, using the same ESPHome Bluetooth Proxy configuration.

  • Made sure only one ESP32 was powered on during each test.

Unfortunately, both boards produce exactly the same connection errors.

The new ESP32 successfully connects to Wi-Fi and Homey, discovers the Blue Connect sensor, and attempts a BLE connection. However, it never manages to establish a connection.

Here’s an example from the latest log:

11:21:01 Connecting v3 without cache
11:21:07 BT_HCI: hcif disc complete: rsn 0x3e
11:21:11 Disconnect before connected
11:21:16 Homey ESPHome API client disconnected
11:21:22 ESP_GATTC_OPEN_EVT in DISCONNECTING state (status=133)
11:21:22 Connection open error, status=133

I also consistently see this warning:

@2colors/esphome-native-api 1.3
using outdated API 0.0, update to 1.14+

Could this outdated API implementation, the connection timeout, or the handling of BLE connection attempts be contributing to the problem?

One more question regarding the hardware:

Both ESP32 boards I’m testing are the same model, purchased here:

Could you share a link to the exact ESP32 board you’ve successfully tested with Blue Connect?

I’d be happy to try a different model if you have one that you know works reliably.

Thanks again for all your efforts and the continued improvements to the app. I really appreciate it!

Kind regards,
Hendrik

Hey @henqo

I have an ESP WROOM32 as well, I don’t recall anymore where I bought it exactly though.

The connection log shows with me:

[12:20:18][D][api.connection:1383]: @2colors/esphome-native-api 1.3.6 (192.168.0.70) connected
[12:20:19][I][bluetooth_proxy:054]: [0] [00:A0:50:B8:5B:DD] Connecting v3 without cache
[12:20:19][D][esp32_ble_tracker:131]: connecting: 0, discovered: 1, disconnecting: 0
[12:20:19][D][esp32_ble_tracker:779]: Stopping scan to make connection
[12:20:19][D][esp32_ble_tracker:787]: Promoting client to connect
[12:20:19][D][esp32_ble_tracker:821]: Setting coexistence to Bluetooth to make connection.
[12:20:19][I][esp32_ble_client:111]: [0] [00:A0:50:B8:5B:DD] 0x01 Connecting
[12:20:19][D][esp32_ble_client:212]: [0] [00:A0:50:B8:5B:DD] fast conn params
[12:20:20][D][esp32_ble_tracker:741]: Scan stop complete, set scanner state to IDLE.
[12:20:20][D][esp32_ble_tracker:131]: connecting: 1, discovered: 0, disconnecting: 0
[12:20:20][D][esp32_ble_client:199]: [0] [00:A0:50:B8:5B:DD] ESP_GATTC_CONNECT_EVT
[12:20:20][D][esp32_ble_client:199]: [0] [00:A0:50:B8:5B:DD] ESP_GATTC_OPEN_EVT
[12:20:20][I][esp32_ble_client:321]: [0] [00:A0:50:B8:5B:DD] Connection open
[12:20:20][D][esp32_ble_client:195]: [0] [00:A0:50:B8:5B:DD] Searching for services
[12:20:20][D][esp32_ble_client:199]: [0] [00:A0:50:B8:5B:DD] ESP_GATTC_SEARCH_CMPL_EVT
[12:20:20][D][esp32_ble_client:212]: [0] [00:A0:50:B8:5B:DD] medium conn params
[12:20:20][I][esp32_ble_client:425]: [0] [00:A0:50:B8:5B:DD] Service discovery complete
[12:20:20][D][esp32_ble_tracker:131]: connecting: 0, discovered: 0, disconnecting: 0
[12:20:20][D][esp32_ble_tracker:825]: Setting coexistence preference to balanced.
[12:20:21][D][esp32_ble_tracker:207]: Starting scan, set scanner state to STARTING.
[12:20:21][D][esp32_ble_client:374]: [0] [00:A0:50:B8:5B:DD] cfg_mtu status 0, mtu 23
[12:20:21][D][esp32_ble_client:199]: [0] [00:A0:50:B8:5B:DD] ESP_GATTC_REG_FOR_NOTIFY_EVT
[12:20:21][D][esp32_ble_client:199]: [0] [00:A0:50:B8:5B:DD] ESP_GATTC_WRITE_CHAR_EVT

I don’t get the message about the API version, although I don’t suspect issues with that, based on feedback I gathered online. Nevertheless, there is not a lot I can do about it, as I’m already using the latest version of the library.

I flashed my ESPHome end of 2025, the bootlog shows this:

[12:15:28]I (29) boot: ESP-IDF 5.4.2 2nd stage bootloader
[12:15:28]I (29) boot: compile time Dec 29 2025 12:09:11
[12:15:28]I (29) boot: Multicore bootloader
[12:15:28]I (31) boot: chip revision: v3.1

My ESPHome device yaml is as follows:

#
# Device Settings
#
esphome:
    name: bleproxy
    friendly_name: BLE Proxy
    min_version: 2025.1.0
    name_add_mac_suffix: false

esp32:
    variant: esp32
    framework:
        type: esp-idf

web_server:
    port: 80

api:
    port: 6053
    batch_delay: 50ms  # Reduce latency for real-time applications
    listen_backlog: 2  # Allow 2 pending connections in queue
    max_connections: 6  # Allow up to 6 simultaneous connections
    max_send_queue: 10  # Maximum queued messages per connection before disconnect
    encryption:
        key: !secret encryption_key
    reboot_timeout: 30min

logger:
    level: DEBUG

# Allow Over-The-Air updates
ota:
    - platform: esphome

wifi:
    ssid: !secret wifi_ssid
    password: !secret wifi_password

    ap:
        ssid: "Bluetooth Proxy"
        password: !secret wifi_ap_password

captive_portal:

bluetooth_proxy:
    active: true

esp32_ble_tracker:
    scan_parameters:
        active: true
        interval: 1000ms
        window: 700ms

Maybe this gives a bit info?

Thanks again for checking this.

I did a few more tests and managed to get much closer to your setup:

  • ESP WROOM32

  • ESPHome 2025.8.2

  • ESP-IDF 5.4.2

  • same BLE proxy configuration

  • Blue Connect placed close to the ESP32

  • removed and re-added the device in Homey

The result is still the same: the proxy discovers the Blue Connect and starts connecting, but it never reaches ESP_GATTC_CONNECT_EVT.

I repeatedly get:

Disconnect before connected

followed by either:

ESP_GATTC_DISCONNECT_EVT, reason=0x3e

or sometimes:

reason=0x100

and then:

ESP_GATTC_OPEN_EVT ... status=133

I also sometimes see the Homey ESPHome API connection close around the same time:

Reading failed CONNECTION_CLOSED errno=128

One difference I noticed compared to your working log is that yours shows:

0x01 Connecting

while mine shows:

0x00 Connecting

Do you think the address type difference could be relevant?

At this point I’m running out of ideas, so if nothing stands out to you I may just leave it for now.

Hey,

To be honest, i start running out of ideas myself as well :slight_smile: .

If you use the BLE device inside the app, without the ESP, it works correctly right? If so, it must be something different in the BLE stack, just wondering what.

Which Blue Connect device do you have?

Kind regards,