Esp32 bluetooth proxy difficultiy .. going down

I am having some difficulty getting ESP32 bluetooth proxy to work.
I managed to configure everything, it recognizes and discovers the devices I have in the area, but after a few minutes it crashes, it doesn’t receive bluetooth signals anymore. I have to unplug and replug the module manually to reboot it.

No symptoms, simply no longer receiving signals.

Then sometimes it resumes independently, sometimes I turn it off and on again.

Is my gateway defective?
Any suggestions?

regards
Stefano

If I push the Safe Mode Boot, then it will come back alive for other 4-5 minutes.
The gateway it will stay pingable, but dosen’t detect any bluetooth event anymore.

It’s really annoying and unusable this gateway.

Is i a normal behavior of this gateway or is mine defective?

Because then it is unusable

Definitely not normal. Can you post your YAML? Without that, all we would have is guesses.

2 Likes
substitutions:
  name: esp32-bluetooth-proxy-8513ac
  friendly_name: Bluetooth Proxy 8513ac
packages:
  esphome.bluetooth-proxy: github://esphome/bluetooth-proxies/esp32-generic.yaml@main
esphome:
  name: ${name}
  name_add_mac_suffix: false
  friendly_name: ${friendly_name}
  
api:
  encryption:
    key: bbbbbbbbbbbbb-key-bbbbb
    
wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

2023-06-21 08_52_15-Home Assistant

then I have to press “Safe Mode Boot” to reactivate them

so it is unusable, I would like to know how to tell if HW is defective

I can’t understand, it says it is offline but the logs show everything ok:

INFO ESPHome 2023.5.5
INFO Reading configuration /config/esphome/esp32-bluetooth-proxy-8513ac.yaml...
INFO Starting log output from esp32-bluetooth-proxy-8513ac.local using esphome API
INFO Successfully connected to esp32-bluetooth-proxy-8513ac.local
[10:21:04][I][app:102]: ESPHome version 2023.5.5 compiled on Jun 20 2023, 12:40:58
[10:21:04][I][app:104]: Project esphome.bluetooth-proxy version 1.0
[10:21:04][C][wifi:505]: WiFi:
[10:21:04][C][wifi:363]:   Local MAC: D4:D4:DA:85:13:AC
[10:21:04][C][wifi:364]:   SSID: [redacted]
[10:21:04][C][wifi:365]:   IP Address: 172.16.8.126
[10:21:04][C][wifi:367]:   BSSID: [redacted]
[10:21:04][C][wifi:368]:   Hostname: 'esp32-bluetooth-proxy-8513ac'
[10:21:04][C][wifi:370]:   Signal strength: -46 dB ▂▄▆█
[10:21:04][C][wifi:374]:   Channel: 8
[10:21:04][C][wifi:375]:   Subnet: 255.255.255.0
[10:21:04][C][wifi:376]:   Gateway: 172.16.8.1
[10:21:04][C][wifi:377]:   DNS1: 172.16.8.31
[10:21:04][C][wifi:378]:   DNS2: 172.16.8.31
[10:21:04][C][logger:301]: Logger:
[10:21:04][C][logger:302]:   Level: DEBUG
[10:21:04][C][logger:303]:   Log Baud Rate: 115200
[10:21:04][C][logger:305]:   Hardware UART: UART0
[10:21:04][C][bluetooth_proxy:065]: Bluetooth Proxy:
[10:21:04][C][bluetooth_proxy:066]:   Active: YES
[10:21:04][C][safe_mode.button:022]: Safe Mode Button 'Safe Mode Boot'
[10:21:04][C][safe_mode.button:022]:   Icon: 'mdi:restart-alert'
[10:21:04][C][esp32_ble:238]: ESP32 BLE:
[10:21:04][C][esp32_ble:240]:   MAC address: D4:D4:DA:85:13:AE
[10:21:04][C][esp32_ble:241]:   IO Capability: none
[10:21:04][C][esp32_ble_tracker:591]: BLE Tracker:
[10:21:04][C][esp32_ble_tracker:592]:   Scan Duration: 300 s
[10:21:04][C][esp32_ble_tracker:593]:   Scan Interval: 320.0 ms
[10:21:04][C][esp32_ble_tracker:594]:   Scan Window: 30.0 ms
[10:21:04][C][esp32_ble_tracker:595]:   Scan Type: ACTIVE
[10:21:04][C][esp32_ble_tracker:596]:   Continuous Scanning: True
[10:21:04][C][mdns:108]: mDNS:
[10:21:04][C][mdns:109]:   Hostname: esp32-bluetooth-proxy-8513ac
[10:21:04][C][ota:093]: Over-The-Air Updates:
[10:21:04][C][ota:094]:   Address: esp32-bluetooth-proxy-8513ac.local:3232
[10:21:04][C][api:138]: API Server:
[10:21:04][C][api:139]:   Address: esp32-bluetooth-proxy-8513ac.local:6053
[10:21:04][C][api:141]:   Using noise encryption: YES
[10:21:04][C][improv_serial:032]: Improv Serial:

I have never seen a product work so poorly.
What a disappointment

I just tried another Hardware, yes I bought a new one, but the problem persists.

So it must be a software problem.

Can someone kindly help me or post a working configuration?

Actually like this it is unusable, after a few minutes it turns off and does NOT work.

THANKS
Stefano

What specific hardware are you using? I’ve never used the method you’re using for a BT Proxy exclusive device, I’ve just added it to several devices I already made for other uses.

I would maybe start with creating a base YAML for your device just to get it to connect to HA and make sure that works as it should. Then add the BT Proxy components and see if that works as well.

I’m using M5Stack ATOM Lite.
The config used is the default I got durring the installation.

I will try to follow the instruction on the link

I’ve noticed my bluetooth proxy is no longer working after hitting the install button in ESPHome after flashing it from the proxy site, somethings up with the new ESPHome update i think

What ESPHome version are you using? There was an issue in a recent one, but the current version (ESPHome 2023.6.5) fixed that.