Mihai Ambrosie
Mihai Ambrosie
The issue is still present.
The issue is still present.
I set up an automation which starts the Add-On if it's not running for 1 minute and 10 seconds. Nonetheless, I hope this bug will be fixed eventually. ```yaml alias:...
An alternative is to modify the Add-On configuration. But I do agree that a real fix is needed. ```yaml base_topic: zigbee2mqtt server: mqtt://192.168.45.201:1883 user: xxxxxxx password: xxxxxxxxxxxx include_device_information: true ```
Just to add that if I add the same AP as an AiMesh Node, the additional device "AiMesh None (None)" doesn't get created and neither does the additional sensor "AiMesh...
It looks like the issue happens only with older devices which don't have AiMesh support. In this case the device causing the issue is an RT-AC87U on 384.13_10 or 3.0.0.4_382_52545-ga0245cc.
Nothing to be sorry about. Thanks a lot for your great work on this integration. 😊
I've tried the PR and it is causing tens of errors in HA like the below, even without the packets sent over by the ESPHome BLE gateway. ```Logger: homeassistant Source:...
@myhomeiot I had replaced __init__.py and const.py in my HA ble_monitor custom component with your proposed changes. After restarting HA it gets flooded with the error mentioned previously. I guess...
Would it be possible to add local mode also for zhimi.toilet.sa1? The specs are 100% the same in home.miot-spec.com (https://home.miot-spec.com/spec/zhimi.toilet.sa1). I'm currently on the latest release v0.7.17. Thanks in advance.