Sudden disconnections and it takes so long to connect

[marcRod8]

I've been looking for solutions and trying different configurations for my YAML, but without success.

I would like to start with the fact that it takes so long to connect to the BLE devices. It was something that I noticed during the initial installation, but I didn't pay much attention to it because I thought that once the connection was established, it would not cause any more issues.
Here I leave a piece of the log that repeats during the initial connection (and I don't know why):

    [20:09:21][D][awox.mesh:119]: scan end
    [20:09:24][D][awox.mesh:236]: Total devices: 10
    [20:09:24][D][awox.mesh:239]: Available device A4:C1:38:16:8E:DD [3805] => rssi: -54
    [20:09:24][D][awox.mesh:239]: Available device A4:C1:38:BE:63:8B [25483] => rssi: -56
    [20:09:24][D][awox.mesh:239]: Available device A4:C1:38:BE:95:8D [5517] => rssi: -59
    [20:09:24][D][awox.mesh:239]: Available device A4:C1:38:9C:6A:14 [27156] => rssi: -60
    [20:09:24][D][awox.mesh:239]: Available device A4:C1:38:E6:DE:27 [24103] => rssi: -61
    [20:09:24][D][awox.mesh:239]: Available device A4:C1:38:3E:D7:31 [22321] => rssi: -62
    [20:09:24][D][awox.mesh:239]: Available device A4:C1:38:BE:33:8F [13199] => rssi: -62
    [20:09:24][D][awox.mesh:239]: Available device A4:C1:38:A8:A1:95 [8597] => rssi: -63
    [20:09:24][D][awox.mesh:239]: Available device A4:C1:38:14:B3:81 [13185] => rssi: -66
    [20:09:24][D][awox.mesh:239]: Available device A4:C1:38:E8:85:BE [1470] => rssi: -70
    [20:09:24][D][awox.mesh:264]: Currently 10 mesh devices reachable through active connections (10 currently known and 10 fully recognized)
    [20:09:24][D][awox.mesh:133]: No devices found to connect to
    [20:09:24][W][component:239]: Component awox_mesh took a long time for an operation (102 ms).
    [20:09:24][W][component:240]: Components should block for at most 30 ms.

The other issue is that after a few hours, the system randomly disconnects, and the connection process starts again.
If the connection were quicker or my system more stable, it wouldn't be a problem.
Does anyone know how I can solve these two problems?
I'll also leave my YAML here in case anyone has suggestions to improve it.

      esphome:
        name: esp32controller-casa
        friendly_name: "ESP32Controller_Casa"
        platformio_options:
           board_build.partitions: no_ota.csv
           board_build.flash_size: 4MB
      
      esp32:
        board: esp32dev
        framework:
          type: arduino
      
      status_led:
        pin: GPIO2
      
      logger:
      
      
      
      mqtt:
        broker: 
        port: 1883
        username: "MQTTUser"
        password: !secret mqtt_password
      
      
      ota:
        platform: esphome
        password: !secret ota_password
        
      wifi:
        ssid: !secret wifi_ssid
        password: !secret wifi_password
      
        ap:
          ssid: !secret ap_ssid
          password: !secret ap_password
      
      external_components:
        - source:
            type: git
            url: https://github.com/fsaris/EspHome-AwoX-BLE-mesh-hub
            ref: main
      
      esp32_ble_tracker:
        scan_parameters:
          active: False
      
      awox_mesh:
        mesh_name: !secret mesh_name
        mesh_password: !secret mesh_password

Thanks.

[michalpulda]

Hi!

You can try to whitelist only MAC addresses of your AWOX devices. That should make establishing connection much faster, because the device will not try to connect to all the devices it sees around. I have 7 devices in total, so I have listed them in the config:

...
awox_mesh:
  mesh_name: !secret mesh_name
  mesh_password: !secret mesh_password
  
  allowed_mac_addresses:
    - A4:C1:38:xx:xx:xx
    - A4:C1:38:xx:xx:xx
    - ...
...

To find a MAC address of your light just go to HA Settings --> Devices --> MQTT --> select your device --> MQTT Info --> click on Payload --> and among identifiers: there should be the MAC address you are looking for.

Let me know if it helps!

[marcRod8]

Hi, thanks for your response. It seems to be a little improvement, but the problem is not solved yet.
Could the queued commands be realted with the connection problem?
I see repeadtly this line:
[11:33:11][I][awox.connection:122]: 15 queued commands (debounce timer: -161, next command DD, for dest: 5517)

Anyone know how can I clean all these queue commands on the connection begining?
Thanks

[fsaris]

The queued commands do not slow down the setup of a new connection. It could only slow down processing a command you send.

Can you show some more logging because the logs you show in your first post doesn't show anything related to the (dis)connections. It only shows the found devices.

Is there a disconnect due to a restart of de esp? Or is one of your devices offline?

You could also play with the minimal rssi setting so it only tries to connect devices that are in "close range". If there is a "poor" connection it's also slower to setup a connection.

[marcRod8]

I've been playing with the lights and forcing the esp32 and it seems that the problem is that the esp32 restarts suddenly. This long down is just before playing with the lights.
[12:45:49][I][awox.connection:115]: still 4 queued commands
[12:45:49][D][esp32_ble_client:191]: [0] [A4:C1:38:3E:D7:31] ESP_GATTC_WRITE_CHAR_EVT
[12:45:49][I][awox.connection:122]: 4 queued commands (debounce timer: -160, next command D0, for dest: 13199)
[12:45:49][I][awox.connection:122]: 4 queued commands (debounce timer: -147, next command D0, for dest: 13199)
[12:45:49][I][awox.connection:122]: 4 queued commands (debounce timer: -131, next command D0, for dest: 13199)
[12:45:49][I][awox.connection:122]: 4 queued commands (debounce timer: -119, next command D0, for dest: 13199)
[12:46:02][W][component:172]: Component mqtt cleared Warning flag
[12:46:02][I][mqtt:291]: MQTT Connected!
[12:46:03][I][app:062]: setup() finished successfully!
[12:46:03][I][app:100]: ESPHome version 2025.4.1 compiled on May 4 2025, 11:47:09

Any suggestion?
Thanks

[fsaris]

Try esp-idf instead of arduino that is a lot better with memory use etc #71

framework:
    # Be sure to "Clean Build Files" when switching framework
    type: esp-idf

[marcRod8]

Thanks, it was really helpful!
I also had to create the no_ota.csv
And now my system is much more stable.
I'll like to suggest you to make a note in the git mentioning the importance of providing with a good electrical supply the esp32 (I really noticed an improvement with the new power transformer)