Thanks for your answer. i have testet it but it´s the same error in my system
Greatings
Title: RD200 V3 Firmware 3.0.1 – ESP_GATT_CONN_FAIL_ESTABLISH with ESPHome Bluetooth Proxy (ESP32 rev3.1)
Device:
RadonEye RD200 V3, Firmware 3.0.1
Serial: FR:JK12RE001423
MAC: 88:57:21:A2:91:8A
Setup:
Home Assistant 2026.7.4
ESPHome 2026.7.3, ESP32 rev3.1 (classic, not S3)
Bluetooth Proxy: Active, 3 connection slots, RSSI -68 dBm
rd200v2 HACS v4.8 (also tested v5.03)
Ecosense app fully closed, phone rebooted
Error (HACS integration):
Failed to connect after 9 attempt(s): Error ESP_GATT_CONN_FAIL_ESTABLISH
ESPHome direct (radon_eye_rd200 component) log:
[esp32_ble_client]: [88:57:21:A2:91:8A] 0x00 Connecting
[BTU_TASK]: hcif disc complete: hdl 0x0, rsn 0x3e (x10)
[esp32_ble_client]: ESP_GATTC_DISCONNECT_EVT, reason 0x3e
[radon_eye_rd200]: Disconnected!
[esp32_ble_client]: ESP_GATTC_OPEN_EVT in DISCONNECTING state (status=133)
[esp32_ble_client]: Connection open error, status=133
What I tried:
rd200v2 v4.8 and v5.03
esp-idf and arduino framework
scan_parameters adjusted (interval 320ms, window 30ms)
on_boot TX power lambda removed
radon_eye_rd200 ESPHome component directly (no proxy)
Phone rebooted, app closed
RadonEye power cycled
HA restarted multiple times
Key observation: Device is visible and advertising (RSSI -68, connectable). ESP32 finds it and initiates connect, but RadonEye sends rsn 0x3e (Connection Failed to Establish) repeatedly at HCI level before GATT even starts. connect_completed_total: 0 – never once connected.
Issue #53 confirms V3.0.1 should work. Could this be a classic ESP32 rev3.1 incompatibility with RD200 V3? Would ESP32-S3 help?
Thanks for your answer. i have testet it but it´s the same error in my system
Greatings
Title: RD200 V3 Firmware 3.0.1 – ESP_GATT_CONN_FAIL_ESTABLISH with ESPHome Bluetooth Proxy (ESP32 rev3.1)
Device:
RadonEye RD200 V3, Firmware 3.0.1
Serial: FR:JK12RE001423
MAC: 88:57:21:A2:91:8A
Setup:
Home Assistant 2026.7.4
ESPHome 2026.7.3, ESP32 rev3.1 (classic, not S3)
Bluetooth Proxy: Active, 3 connection slots, RSSI -68 dBm
rd200v2 HACS v4.8 (also tested v5.03)
Ecosense app fully closed, phone rebooted
Error (HACS integration):
Failed to connect after 9 attempt(s): Error ESP_GATT_CONN_FAIL_ESTABLISH
ESPHome direct (radon_eye_rd200 component) log:
[esp32_ble_client]: [88:57:21:A2:91:8A] 0x00 Connecting
[BTU_TASK]: hcif disc complete: hdl 0x0, rsn 0x3e (x10)
[esp32_ble_client]: ESP_GATTC_DISCONNECT_EVT, reason 0x3e
[radon_eye_rd200]: Disconnected!
[esp32_ble_client]: ESP_GATTC_OPEN_EVT in DISCONNECTING state (status=133)
[esp32_ble_client]: Connection open error, status=133
What I tried:
rd200v2 v4.8 and v5.03
esp-idf and arduino framework
scan_parameters adjusted (interval 320ms, window 30ms)
on_boot TX power lambda removed
radon_eye_rd200 ESPHome component directly (no proxy)
Phone rebooted, app closed
RadonEye power cycled
HA restarted multiple times
Key observation: Device is visible and advertising (RSSI -68, connectable). ESP32 finds it and initiates connect, but RadonEye sends rsn 0x3e (Connection Failed to Establish) repeatedly at HCI level before GATT even starts. connect_completed_total: 0 – never once connected.
Issue #53 confirms V3.0.1 should work. Could this be a classic ESP32 rev3.1 incompatibility with RD200 V3? Would ESP32-S3 help?