You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the ESP32C3 does not work (yet). I keep trying to use a vanilla ESP32 (NodeMCU with WROOM32 Board) but I don't get a reliable control via home assistant. No matter how close I place the ESP32 to the lamp, the device constantly becomes unavailable and available.
I currently have 2 EGLO RGBW lamps installed. The ESP is now sitting 1m below one lamp. The Bluetooth connections seam really good with rssi: -43. The other one is about 6m away but still easily controllable with the EGLO remote from the spot of the ESP.
Here is my config:
esphome:
name: awox-ble-mesh-hub
friendly_name: "AwoX BLE mesh hub"
esp32:
# Match this with the board your using
board: nodemcu-32s
framework:
# Be sure to "Clean Build Files" when switching framework
type: esp-idf
status_led:
# Match this with the board your using
pin: GPIO2
# Enable logging
logger:
#level: VERY_VERBOSE
# debug:
# update_interval: 5s
# text_sensor:
# - platform: debug
# reset_reason:
# name: "Reset Reason"
# sensor:
# - platform: debug
# free:
# name: "Heap Free"
# loop_time:
# name: "Loop Time"
mqtt:
broker: !secret mqtt_host
username: !secret mqtt_user
password: !secret mqtt_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
password: !secret ota_password
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
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:
active: false
awox_mesh:
mesh_name: !secret mesh_name
mesh_password: !secret mesh_password
max_connections: 2 # max 3 connections <--- did not alter the problem
# Optional options
# address_prefix: A4:C1
# min_rssi: -90 # to prevent that the mesh tries to connect to devices that are out of range
# max_connections: 2 # max 3 connections
# You can give a list of mesh_ids that only should be handled by this device
# Example when you want to setup multiple ESP modules to only control a part of the mesh) be sure to also set allowed_mac_addresses option.
# allowed_mesh_ids:
# - 12345
# - 23456
# - 6758
# You can give a list of mac_addresses that are allowed to connect to (to exclude some devices that are often offline or for the allowed_mesh_ids option)
# allowed_mac_addresses:
# - A4:C1:38:8A:BA:11
# - A4:C1:38:65:AD:22
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-RGB-TW
manufacturer: EGLO
- product_id: 0x96
device_type: RGB
name: EGLO RGB+TW
model: EGLO-RGB-TW
manufacturer: EGLO
Did you install it over USB? A fresh install can help (especially by bigger code changes/upgrades) to resolve ble disconnect issues or other unexplainable issues
As the ESP32C3 does not work (yet). I keep trying to use a vanilla ESP32 (NodeMCU with WROOM32 Board) but I don't get a reliable control via home assistant. No matter how close I place the ESP32 to the lamp, the device constantly becomes unavailable and available.
I currently have 2 EGLO RGBW lamps installed. The ESP is now sitting 1m below one lamp. The Bluetooth connections seam really good with
rssi: -43
. The other one is about 6m away but still easily controllable with the EGLO remote from the spot of the ESP.Here is my config:
And Log:
logs_awox-proxy_logs.txt
Hope there is a way to get this reliable, as I purchased a bunch of those lamps.
Thanks in advance!
The text was updated successfully, but these errors were encountered: