-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LYWSD03MMC cannot reconnect to repeater #142
Comments
not sure how it can help? Maybe I explained the problem a bit unclear. Binding was ok and device is working and it do reconnect after battery jerking. However it should reconnect to network automatically without any manual work like other devices do. |
This behavior is not observed with a normal Zigbee coordinator.
|
Okay, thank you. All other devices do not have such issue, that's why I thought something could be tweaked/fixed in firmware. |
When testing the coordinator shutdown for more than a day, the Zigbee Xiaomi aqara sensors always fell off. Others did not.
Tell me what needs to be fixed if everything works as it should. In the year since the installation of the autonomous ZigBee router, not a single device has dropped out of the network. And once again - the Zigbee network is not designed to work without a coordinator. Devices begin to search for the network chaotically. And if they come across a crooked router from Tuya, then anything can happen. The same applies to Zigbee coordinators. If the program does not work correctly or does not allow re-join and re-binding at all, then all Zigbee 3.0 devices are disconnected. Tuya and Xiaomi devices do not comply with Zigbee 3.0 standards and require special programs on the Zigbee coordinator side. |
Have LYWSD03MMC with 04 Sep firmware. It works fine until repeater got down (e.g. electricity outage). After this device do not automatically reconnect to repeater. Do reconnect after reboot (remove and insert battery). Other devices (soil moisture sensors) connected to the same repeater works fine with no reconnect issue.
The text was updated successfully, but these errors were encountered: