E1 thermostat sleeping/faulty

[jkibs111]

I am having problems with my aqara thermostat e1. It is like they are sleeping and do not open the radiator valve when the temperature falls below the setpoint. However if I just increase the setpoint by 0.5C and thus “wakes” thermostat it reacts and opens the valve correctly. The problem is there both when I use an external temperature sensor and when I’m not.
Picture1 shows the problem. I placed a linked sensor close to a window where it is colder than the 22C setpoint. The temperature drops to below 20C but the thermostat does nothing… It is dormant for 10hours until I actively “wake” it from the app by changing the setpoint. This time I activate by actually decreasing the setpoint by 0.5C – it just needs to be woken up… However, it goes back to its dormant mode after reaching the setpoint. I have been in contact with aqara support and they say the thermostat may be faulty but don’t want to do anything since the thermostats are three years old…
Now two days ago, my second thermostat also started behaving weirdly. It had given a low battery warning, so I changed the batteries, but after it is much worse at regulating the temperature – see picture2. After the battery change and valve recalibration it basically behaved like the other thermostat and did not heat until at woke it up by changing the setpoint (big temperature dip in picture).
Has anybody experienced similar issues with the e1 thermostat and possible fixes? Or do they simply have about a three year lifetime

[cezary806]

I don’t, but I think E1 thermostat partly relies on the cloud to function (you can see that automations with the E1 have the “cloud” tag instead of “local” tag). So maybe there’s a problem with connection to the cloud or with the cloud?
You may also try contacting the support and posting the solution here for future reference.

[gafich10]

Hi, this problem has appeared recently. Re-bind the external thermometer. If you have a W100, give a sampling period of 10 minutes.

W100 Explanation of the temperature sampling setting для то

I think many users are confused by the settings in the W100 sensor. I want to make a short description of this setting. To find this setting, you need to select it in the W100 splash screen. [IMG_20250729_184830] [IMG_20250729_184848] We will leave the settings for later, after the explanation this question will disappear. After selecting manual settings, the following selection window appears. The “Samnling period” setting is responsible for the speed of data update on the physical, I em…

[jkibs111]

Thanks - I am only using the small Temperature and Humidity Sensors, but I will try to re-bind them.

[jkibs111]

Thanks. I am actually using them in automations with a window sensor but mine says “local”.

[cezary806]

Interesting, when I use “Temperature is below a set temperature” then the automation is “cloud”, but when I add another local condition (like if temperature is below 17°C on W100), then it says “local”.

And @gafich10, thanks for the heads up. I actually used this fix a while ago and forgot about it. The E1 will automatically change to internal sensor after a few hours because some sensors will stop updating the temperature if it’s somewhat constant. And then the E1 sees it as if the sensor was offline.

[gafich10]

@cezary806

Interesting, when I use “Temperature is below a set temperature” then the automation is “cloud”, but when I add another local condition (like if temperature is below 17°C on W100), then it says “local”.

Hello, unfortunately “more installed” and “less installed” are CLOUD. And when it says Local automation, it’s not necessarily local. Read the local explanatory note when viewing automation. It says “will be local if there are no cloud services” . And what I said above is CLOUD.

Note: to check LOCALITY, temporarily disconnect the internet from the gateway (option on the router) and check the performance. I put a temporary button press in the WHEN condition (to quickly check). I think you understood what I wrote about WHEN.