A nice guy created a PR. There you’ll find the URL for manual updating. It’s a shame that Aqara can’t provide the URL itself.
4 Likes
Thanks for that! Still cannot update these lovely thermostats. Devices do not respond to OTA. They are just stuck at -1 Firmware in Z2M… The app route as XT-XianTang mentioned still does not work reliabily. Resetting and readding also does not help.
I am now at the point where I give up and get different thermostats, heck even the old E1’s would be an improvement
2 Likes
How can one see the valve opening percentage? Is it available through the Aqara app or Home Assistant? Thanks.
I can see it in Z2M but for me it is not accurate at all.
Shows 0% - Radiator boiling hot 
2 Likes
Is it known how often does the thermostat refresh with the hub (not on matter)? What I have noticed every morning the radiator is heating, if I press the thermostat it shows the “old” room temperature, only after that it updates to the new one (a difference of about 3-4 degrees).
Is there a new firmware update on the way? The thermostat still has the issue of never reaching target temperature.
Also, does anyone else sometimes have an issue where valve position is no longer updating in Home Assistant with Zigbee2mqtt? Temperature still updates.
1 Like
Yes, has the same issue that valve position is not updated after some time.
Fun fact: if you actively fetch it over Zigbee2MQTT GUI the valve position is reported correctly.
Valve position is not updated with the regular payload anymore.
3 Likes
I have the same problem. After a while, the valve position stops updating. I also noticed that a thermostat was heating for no reason, even though the temperature setpoint was set to 5°C and it was much warmer outside. Removing the batteries and restarting the system resolved the issue and closed the valve.
Sadly, no improvement for a long time.
It seems aqara is not anymore interested in improving their product and communicating this to their users.
This was my last aqara product, that is more complicated than switch or light bulb
I have lost faith in aqara!
5 Likes
True words. I’m really thinking of reverting back to Tados thermostats which worked well out of the box and returning the Aqara’s ones since they do not work as advertised (not even basic functionality, not to mention other features). In EU this can be done within the year of purchase by consumer law, I believe. Any EU users here with experience on that?
2 Likes
I’m also interested in returning my thermostats in Germany and would appreciate hearing about anyone’s experiences.
I estimate that, due to their poor control performance, the thermostats have cost me more in heating bills than I did in previous years with manual valves. The bill is still pending…
3 Likes
I have the E1 as well as the W600. The E1 does its thing very well, except they tend to break mechanical after some time.
I have 2 W600 combined with external temperature sensors WSDCGQ11LM and I’m facing the same problem as addressed in this thread (with firmware 0.0.0_2745)
4 Likes
I should have returned it directly in the first month, where it was possible without problems. But I had hopes…
Depends where you bought them. I used Tink and basically got told, they wont refund me as it was past the 14 Day return window. And the use case that I have, using it via Z2M etc is officially not supported.
I did point out that even with the Aqara Hub, I had the same issues, they would not budge and told me to contact Aqara.
Aqara ignored me pretty much and told me that the team is working on it, but due to Chinese new year etc it could take a while. I now have given up… Heating period is pretty much over and I removed the W600 for now. Even when I had them switched off, they randomly turned on again. 200€ e-waste and a lesson learned.
2 Likes
If you’re in EU it has nothing to do with the manufacturer, you only communicate in written form with the seller.
Under EU consumer protection laws (Legal Guarantee of Conformity), since the defect has become apparent within the first year of delivery, it is presumed to have existed at the time of purchase.
They can offer a new replacement, and when this one does not work as expected as well you can demand the full refund. You can try this immediately, since defects are software related and not fixed, hence replacements won’ work either:
Therefore, I am exercising my right to a remedy under EU law and kindly request a full refund of the purchase price (contract termination due to severe non-conformity).
I have just noticed that smart schedules don’t use the correct time for Events… Maybe wrongly used daylight saving times?
Just another update… one started heating randomly today - room temperature 22 (on the thermostat as well as another temperature sensor), heating set to 20. Radiator hot. @aqara - I think it’s time you solve this random behaviour.
1 Like
There is no reaction from Aqara.
Dubious 
1 Like
Hi all,
I have been following this thread for a while and wanted to share a few findings that might be useful for the community — some from my own testing, some from an active support ticket I have open with Aqara Technical Support.
Factory reset bug (firmware 20260305) — reliable indicator and workaround
Several people have mentioned that the hardware factory reset does not work on firmware 20260305. I can confirm this and want to add a precise indicator to verify whether a reset was actually successful:
Check the Display Flip setting after performing the reset. After a genuine factory reset, this setting returns to its default value. If it remains unchanged, the reset did not complete — the device only left the Zigbee network but did not clear its internal state.
I repeated the standard reset procedure (press twice, hold 10 seconds) multiple times with the same result every time: network leave happens, Display Flip stays unchanged. Full reset never occurred.
The only reliable workaround I found:
- Flash back to Matter firmware via the Aqara app
- Perform factory reset in Matter mode via the Aqara app
- Re-flash to Zigbee firmware
I had to use this workaround again just recently when trying to pair the device to an Aqara Hub M100 for diagnostics — confirming this is a consistent and reproducible regression vs. firmware 20260122, where the hardware button works as documented.
Valve position bug — additional diagnostic detail
Like others here, I have the stale valve position reporting issue on firmware 20260305. One observation that might help Aqara’s engineering team narrow it down:
If you actively fetch the position attribute via the Zigbee2MQTT GUI after the reporting has gone stale, the device returns the correct current value. This means the device tracks valve position internally and correctly — it simply stops proactively reporting it after some time. This is a reporting/attribute-push failure, not a hardware or position-tracking failure.
My three other W600 units on firmware 20260122 on the same coordinator do not exhibit this behavior.
Active Aqara support ticket
I have an open support ticket with Aqara Technical Support (ticket #715768) covering these issues. The interaction so far:
- Aqara has requested device log access via the Aqara Home app (Profile → Message Center → System → Approve), which I have granted via a Hub M100 I bought specifically for this purpose.
- Issues 1 (stale valve position) and 2 (factory reset bug) have been escalated. I have explicitly pushed back on the suggestion that these are third-party platform issues — they are firmware-level regressions that manifest independently of Z2M or any coordinator.
- I have formally requested either a fixed newer firmware or a downgrade path to 20260122.
- I have not yet received a confirmed timeline.
I will update this thread when I have further responses from Aqara.
I hope this is useful. Happy to share more details from the support ticket as the conversation progresses.
6 Likes
we just have to accept, that the w600 are crap and that aqara is not willing or does not have the abillity to fix it.
4 Likes