Mesh

[cristideca]

Hello,

The hub is seeing the bulb, but does not find a mesh to connect. Log:
[09:24:05][D][awox.mesh:119]: scan end
[09:24:06][D][awox.mesh:236]: Total devices: 1
[09:24:06][D][awox.mesh:238]: Available device A4:C1:38:E5:5B:28 [0] => rssi: -62
[09:24:06][D][awox.mesh:261]: Currently 0 mesh devices reachable through active connections (0 currently known and 0 fully recognized)
[09:24:06][D][awox.mesh:270]: Try to connecty to device A4:C1:38:E5:5B:28 no mesh id known yet

---

My config:

esphome:
name: awox-ble-mesh-hub-etaj
friendly_name: "AwoX BLE mesh hub etaj"

esp32:
board: esp32dev
framework:
type: esp-idf

status_led:

Match this with the board your using

pin: GPIO2

Enable logging

logger:
#level: VERY_VERBOSE

mqtt:
broker: "homeassistant.local"
username: ""
password: ""

Disable retained discovery messages until you are got the config correct

discovery_retain: True

Disable Home Assistant API to prevent frequent MQTT disconnections

#api:

ota:

• platform: esphome

wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
manual_ip:
static_ip: ***
gateway: ***
subnet: 255.255.255.0

external_components:

• source:
  type: git
  url: https://github.com/fsaris/EspHome-AwoX-BLE-mesh-hub
  ref: main

ref: dev

- source:

type: local

path: components

esp32_ble_tracker:
scan_parameters:
interval: 1100ms
window: 1100ms
active: true

Enable Home Assistant API

#api:

#bluetooth_proxy:

active: False

awox_mesh:
mesh_name: !secret mesh_name
mesh_password: !secret mesh_password

device_info:
# Example device type, see device info in HomeAssistant or MQTT message to find the 'product_id'
- product_id: 0x96
device_type: RGB
name: EGLO RGB+TW
model: EGLO-RBB-TW
manufacturer: EGLO
icon: mdi:wall-sconce-flat

- product_id: 0x30
  device_type: RGB
  name: EGLOPanel 30x120
  model: EPanel_120
  manufacturer: EGLO
  icon: mdi:wall-sconce-flat

[fsaris]

What are the next log lines? Do you see a failing login attempt?

[cristideca]

08:38:06][D][awox.mesh:236]: Total devices: 3
[08:38:06][D][awox.mesh:238]: Available device A4:C1:38:E6:C8:2D [0] => rssi: -58
[08:38:06][D][awox.mesh:238]: Available device A4:C1:38:E5:5B:28 [0] => rssi: -9999
[08:38:06][D][awox.mesh:238]: Available device A4:C1:38:B2:6E:5F [0] => rssi: -84
[08:38:06][D][awox.mesh:261]: Currently 0 mesh devices reachable through active connections (0 currently known and 0 fully recognized)
[08:38:06][D][awox.mesh:270]: Try to connecty to device A4:C1:38:B2:6E:5F no mesh id known yet
[08:38:06][I][awox.mesh:143]: Try to connect A4:C1:38:B2:6E:5F => rssi: -84
[08:38:06][I][awox.connection:150]: [4] set_state SEARCHING
[08:38:06][D][esp32_ble_client:110]: [4] [A4:C1:38:B2:6E:5F] Found device
[08:38:06][D][esp32_ble_tracker:677]: Found device A4:C1:38:B2:6E:5F RSSI=-82
[08:38:06][D][esp32_ble_tracker:698]: Address Type: PUBLIC
[08:38:06][D][esp32_ble_tracker:700]: Name: 'JSlEvrsJ'
[08:38:06][I][awox.connection:150]: [4] set_state DISCOVERED
[08:38:06][W][component:237]: Component awox_mesh took a long time for an operation (66 ms).
[08:38:06][W][component:238]: Components should block for at most 30 ms.
[08:38:08][D][esp-idf:000][BTU_TASK]: W (48399) BT_HCI: hcif disc complete: hdl 0x0, rsn 0x3e

[08:38:08][D][esp-idf:000][BTU_TASK]: W (49152) BT_APPL: gattc_conn_cb: if=3 st=0 id=3 rsn=0x3e

[08:38:08][D][esp-idf:000][BTU_TASK]: W (49156) BT_APPL: gattc_conn_cb: if=4 st=0 id=4 rsn=0x3e

[08:38:08][D][esp-idf:000][BTU_TASK]: W (49163) BT_APPL: gattc_conn_cb: if=5 st=0 id=5 rsn=0x3e

[08:38:08][D][esp-idf:000][BTU_TASK]: W (49168) BT_APPL: gattc_conn_cb: if=6 st=0 id=6 rsn=0x3e

[08:38:08][D][esp-idf:000][BTU_TASK]: W (49177) BT_APPL: gattc_conn_cb: if=7 st=0 id=7 rsn=0x3e

[08:38:08][D][esp-idf:000][BTU_TASK]: W (49189) BT_HCI: hcif disc complete: hdl 0x0, rsn 0x3e

[fsaris]

And then it stops?

What device are you using?

Did you do a wired install?

[cristideca]

It loops. I did a wired install on a esp32 wroom 30 pins with esp home

[fsaris]

Do you see a reboot between the circles?

Can you test if installing Bluetooth proxy works, or just trying to use it as a Bluetooth tracker?
There are more reports of devices that just don't work for some unknown reason. My personal experience is that a full fresh build (so also in esp home builder clean build files) and do a wired install.

[cristideca]

My last logs are with bluetooth proxy on. Maybe the boards i bought are defective?

[fsaris]

That could be the case. Or maybe wrong board configured?

Easiest is to get a new board and check of that works

[cristideca]

Did a clean install and here are the logs
logs_esphome-web-45dfc4_logs.txt

[cristideca]

Got different boards. Now when i install (wired) it works. I can control the lights. After I unplug and plug again the board, i get:
INFO Connected to MQTT broker! [12:57:58][D][awox.mesh:133]: No devices found to connect to [12:58:00][D][awox.mesh:236]: Total devices: 2 [12:58:00][D][awox.mesh:238]: Available device A4:C1:38:E5:5B:28 [0] => rssi: -9999 [12:58:00][D][awox.mesh:238]: Available device A4:C1:38:B2:6E:5F [0] => rssi: -9999 [12:58:00][D][awox.mesh:261]: Currently 0 mesh devices reachable through active connections (0 currently known and 0 fully recognized)

[cristideca]

@fsaris any idea why this is happening?
This log is after i reset the board:
logs_esphome-web-bad340_logs.txt

[fsaris]

Did you do a install/flash using a wired serial connection?

When you see errors like

[23:16:28][D][esp-idf:000][BTU_TASK]: W (15203) BT_HCI: hcif disc complete: hdl 0x0, rsn 0x3e
[23:16:28][D][esp-idf:000][BTU_TASK]: W (15593) BT_HCI: hcif disc complete: hdl 0x0, rsn 0x3e
[23:16:29][D][esp-idf:000][BTU_TASK]: W (16496) BT_HCI: hcif disc complete: hdl 0x0, rsn 0x3e
[23:16:29][D][esp-idf:000][BTU_TASK]: W (16852) BT_APPL: gattc_conn_cb: if=3 st=0 id=3 rsn=0x3e
[23:16:29][D][esp-idf:000][BTU_TASK]: W (16856) BT_APPL: gattc_conn_cb: if=4 st=0 id=4 rsn=0x3e
[23:16:29][D][esp-idf:000][BTU_TASK]: W (16859) BT_HCI: hcif disc complete: hdl 0x0, rsn 0x3e

that result in a ESP_GATTC_DISCONNECT_EVT, reason 62 it often means the bluetooth stack crashes. If you search for this error it's often caused by one of the next things:

• bigger framework change that need a wired re-install (bigger update or switch of framework arduino vs esp-idf) see warning on https://esphome.io/components/bluetooth_proxy.html#bluetooth-proxy
• wrong board selected
• dependencies issues in cached libraries (clear buld data and try again, preferably using a wired connection)