I’ve got a W100 associated with an E1 TRV and an automation which fires the boiler when the E1 requests heat.
Based on the heating traces the W100 looks to have had a bug and not communicated with the E1 for more than a day, which caused the boiler to turn on for the whole day and waste a heap of energy.
Hello, glad to hear. I don’t know what the reason is, but this problem is solved when you set W100 to manual mode with a polling period of 10 minutes. The problem completely disappears.
If you analyze it, then I need to raise this problem with the developers more persistently. It has become something massive. Tutorial - Troubleshooting Aqara W100 whit Aqara Valve E1
Currently, after a month-long test, I have not encountered any disconnect problems. Please note that the data transfer mode, temperature, and humidity are set to standard or high. This always tends to preserve battery life. This can be bypassed with the custom mode.
I I set this parameter from the very beginning, the W100 sensor has never fallen off. By the way, I turn off the humidity altogether, it is updated ~once an hour. I save battery.
One minute in the upper field is the update rate of the W100 dial. If you set the period, it becomes 10 minutes in total, by the way, this reduces unnecessary signals for E1 adjustment.
I forgot to say. I have W600 and E1 and W100 connected Zigbee directly to the gateway. To eliminate possible disconnections due to repeater problems.
In Ukraine, the industrial network often disappears now (you know why), and such a Zigbee connection is very reliable for operational work without a repeater.
Understood. In this case both devices are within 2m of the hub, in the same room (central hallway). The hub also has battery backup and never loses power. This can only be a software bug and not a communication issue unfortunately.