Aqara W600 thermostatic valves – major reliability and usability issues

Hello,

I’m a long-time Aqara user and overall I’ve been satisfied with your products so far. That’s why I’m quite disappointed to write this message today.

I recently bought 10 Aqara W600 thermostatic radiator valves to upgrade my heating system. Eight of them are paired with Aqara W100 temperature sensors, all connected via Zigbee to an Aqara M3 hub. All devices are running the latest firmware (W600 version 0.0.0_1839).

After a few days of use, I have to say that I’m honestly surprised, worried and unhappy. To be very clear: in its current state, the system is unusable.

Pairing was already extremely painful. More than half of the devices (7 out of 10) failed during the first pairing attempt. In some cases the process gets stuck when switching from Thread to Zigbee, in others it blocks during hub pairing, and in several cases the valve remains stuck in calibration mode. When that happens, there is no way to recover, even after rebooting or removing the internal battery. The only solution is a factory reset and starting over. In practice, installing 10 valves took almost half a day.

Configuration through the app is also very unreliable. Changes made in the app are often not applied to the valve, and conversely, temperature changes made directly on the valve are not always reflected in the app. The interface itself is not intuitive. The smart schedule time slider is badly designed: after selecting a time range, you must wait around two seconds before validating, otherwise the wrong value is saved. Copying a day schedule to other days works randomly. Most importantly, smart schedules are never applied correctly. All my valves have the exact same schedule, with the same temperatures and time ranges, yet at a given moment they often end up in different states. For several days I manually forced a return to the smart schedule by setting a manual temperature and cancelling it. Eventually I gave up and set all valves to permanent manual mode, which obviously defeats the purpose of buying connected valves. I also had three valves where smart schedules were never saved at all, requiring a factory reset. Child lock is completely unreliable as well: I enabled it on all valves via the app, but in practice it disables itself on all of them after a few hours. Temperature source selection is also broken. Even when I explicitly select an external W100 sensor, the valve often continues using its internal sensor.

Actual heating behavior is just as bad. Some rooms have multiple radiators, all equipped with Aqara valves, same configuration, same W100 temperature source. Despite this, some radiators are fully closed while others are fully open. This looks like a badly tuned PID with strong overshoot and undershoot. In practice, it is very rare to see a valve in an intermediate position; they are almost always either fully open or fully closed. I tried everything to fix this: recalibration, forcing temperature updates from the W100 sensors every 10 minutes, nothing helps. The valves always diverge.

Right now, while it is –3°C outside, the house is under-heated in the morning. Beyond comfort issues, I am also worried about the impact on my heating system itself. When several valves randomly decide to close, the boiler keeps running with little or no effective load. I deliberately kept two radiators with manual valves, and those two now receive an abnormally high flow, clearly showing that the installation is becoming unbalanced. This behavior is not only inefficient but potentially harmful for the long-term health of the system.

I’ve seen on various forums that many users are experiencing similar issues, and that Aqara support mentions ongoing efforts to improve the situation. I sincerely hope a permanent and reliable solution will arrive soon. In my case, this represents close to 1000 euros invested in valves, temperature sensors, hub, Zigbee relays and accessories, which are currently almost completely useless.

Thank you for reading, and I hope this feedback will be taken seriously.

6 Likes

Hello, welcome to the forum. Sorry for the inconvenience you experienced. The new firmware has fixed some of the problems you described. Check in the app whether you have the new W600 firmware. If there is no new firmware, I recommend contacting support. Also, you can enable beta versions of firmware in the app (so that you receive beta firmware). Personally, my W600 operation has stabilized, the PID regulator has started working normally.

Merry Christmas to you!
:h5ldfuv37rmmla1gamylun_109:

2 Likes

Could you give me your Aqara account? I’ll push the new Zigbee firmware to you.

5 Likes

Hi, could yoy push update to me please I have exactly the same issue

1 Like

Hello, welcome to the forum, Merry Christmas to you!
:h5ldfuv37rmmla1gamylun_109:

Write in private @XianTangHE your Aqara Home account.

1 Like

Hello,

I have four W600 thermostats, all with external temperature sensors.

I have to say, with the 2442 update, it’s much, much better.

However, I do have one point of criticism. For example, if I manually change the temperature in the app for two hours, the thermostat sometimes doesn’t return to the correct schedule. This is especially true if there was already a change in the schedule during those two hours.

I hope I’ve explained it clearly.

Best regards and Merry Christmas to everyone!

2 Likes

Not sure how to send a private message

1 Like

Hello, Merry Christmas to you. I showed you how in the screenshots.

Bonjour,

J’ai le même probleme.
Je suis passé des thermostats E1 au W600 et plus rien ne fonctionne.

1 Like

Hello,

Following my previous message, I was contacted by Aqara support and asked to provide my Aqara account number. After that, a firmware update identified as version 2442 became available in the application. I have now installed this update on all my valves.

After this update, some of the issues I was experiencing have been fixed. Most importantly, the major problem where valves were diverging toward fully open or fully closed states appears to be resolved. Since installing the update, I have not encountered this behavior again.

Not all issues are fixed yet. In particular, the configuration interface still has some problems. For example, at regular intervals, the app asks me to set up smart schedules even though they are already active. That said, smart schedules now seem to activate correctly and behave much more consistently.

Regarding temperature regulation, I still sometimes notice valves remaining open even when the setpoint has already been reached or slightly exceeded. I also observe occasional overshoot of up to about 1°C, which I find relatively high. This seems to happen mainly in rooms equipped with multiple radiators. It is not a major issue, but I do hope there will be further improvements in this area.

In any case, I would like to thank the support team and the technical teams for their responsiveness. I hope the product will continue to improve over time.

2 Likes

Hello, thank you for your feedback on the new update.
The Aqara team continues to fix the shortcomings identified by users.

Can you also do this for my account? No update for me, still sitting at 1839 with all the issues others have here :melting_face:

Hello.
Write in private @XianTangHE your Aqara Home account.

Sadly I dont have the message button :sweat_smile:

You need to reach trust level „Basic“ in this forum: Understanding Discourse Trust Levels

You are still on trust level „New“ and are not allowed to send PMs yet.

Wow thank you, so I cant even use my products before this, ookaaaay :sweat_smile:

Hello,

After a few more days of usage on firmware version 2442, I would like to share additional feedback.

Even though smart schedules are already set up, the application regularly displays the message “Existing configuration data has been detected for the smart schedule. Do you want to apply it?”. This happens frequently and becomes quite annoying over time.

Smart schedules themselves are still very unreliable. Time ranges and target temperatures are rarely respected. My current workaround is to manually iterate over all my thermostatic valves twice a day (morning and evening), change the temperature to force manual mode, then immediately cancel manual mode in order to force the smart schedule to apply. This should obviously not be necessary.

Most of my valves are paired with a W100 temperature sensor. However, the temperature displayed by the W100 and the temperature actually used by the thermostatic valve do not always match, even though they should be identical (aside from a possible small time delta). For reference, my W100 sensors are configured to send temperature updates every 10 minutes. Even worse, in some rooms multiple valves are associated with the same W100 sensor. Not only do the valve temperatures differ from the W100 reading, but the temperatures reported by the different valves also differ from each other. These differences can reach almost 2°C and, in my opinion, directly cause uneven heating between radiators that should otherwise behave identically.

Child mode is still unreliable and systematically disables itself after some time.

It is also very common to observe temperature overshoot of 1 to 1.5°C above the setpoint. The target temperature is already reached, yet the radiator still receives water at a significant flow rate. I have re-run calibration on all Aqara valves to rule that out, without any improvement. All my thermostatic valves are brand new, so I can reasonably exclude any mechanical issue such as a stuck valve.

I hope the support and engineering teams can take note of these points, as they currently make the overall experience quite frustrating.

3 Likes

As far as I understood, the external sensor problem is still a known issue:

I hope the Aqara team will solve all the issues very soon since the reviews of the W600 are getting worse and worse and customers still complain a lot (see Amazon reviews and many topics on this forum).

1 Like

I created a topic to provide an overview of the current state of the W600. Feedback welcome.

1 Like