Does anyone of you is using this one with z2m? or do all of you using aqara hubs and aqara app?
If z2m: Do you also get this problems related with the external sensor?
The new firmware finally seems to reach the setpoint, but it was necessary to remove the device from the app (the smart schedule stopped working and it no longer accepts manual commands). The problem is that it doesnât switch to night mode - rather, it behaves randomly: sometimes the temperature drops at night, sometimes the daytime temperature is still maintained. At least I no longer have to manually change the temperature settings during the day, because the valve suddenly decided not to open even at 16°C even though it should reach 21°C.
So its happend to me. The same that david3 has. It was good for a few days 2 or so. Now I have these Problems. Few Thermostate Resets, few new binding from W600 to W100, nothing helps. All Firmwares Beta and Regular are Updated. IOS and Android App Version updated. It feels like everything is Stuck.
That drives me Crazy. Is it a Location Problem? I am in Germany. Or a App Problem?
Bin auch in Deutschland
I use my W600s together with Z2M and Versatile Thermostat (VTherm).
VTherm supports external temperature sensor, but Z2M (and thus VTherm) currently only supports offset calibration for the W600 and doesnât yet provide a separate external temperature entity (like the predecessor, the Aqara E1).
There are already some open issues, and I hope external temperature sensor support for the W600 will be added to Z2M soon:
- Aqara W600 external temperature input
- External temperature sensor support would be a fantastic addition
Please feel free to support if you can.
Count me in⌠schedules are failing again! ![]()
Hello, Zigbee mode?
W100 connected to W600(as a remote thermometer)?
Temperature graph (APP) W600=W100?
Found this in the FAQ in the App from the W600.
Smart schedule did not run as scheduled
- First, please verify whether the current holding duration in Manual Mode is set to âUntil the Nextâ. If you have set it to a different time, our temperature will operate normally for the corresponding duration according to your set holding time.
- Please check if your gateway is online normally.
- If the temperature difference between different scenes you set is too small, the device may not be able to execute the corresponding scene configuration. It is recommended that you set the temperature difference between different scenes to be greater than 2 degrees Celsius
Point 3. is interesting
So they acknowledge 3 is a bug and they tell the user to fix it.
Seems, as the âsensationalâ thermostat is still not working as advertised.
And still no comment from aqara itself, what they will correct when. ![]()
And that annoys me.
For months, there are only problems with the thermostats but no improvement in sight. Even the support does not help.
Thatâs a real embarrassment. So users are supposed to adapt to a flawed product instead of the product being designed to meet the needs of users.
That sounds harsh, but unfortunately that seems to be the case.
You all get this rant that I just posted in another thread about the W100. Please donât hate me for it, but I think we all have reached the enough is enough point (maybe with the exception of one very positive âreviewer/moderatorâ)
I like that you use it as a controller instead of a thermostat
. No matter how I have had this thing connected to my (according to a recent âplease send some free products to me, I am soo worthyâ review) âfantasticâ radiator w600 thermostats, it hasnât done what it is supposed to do. Updates gives us about 2 - 5 days of working thermostats and then fails again. The only time I actually had some use of it was when connected to zigbee2mqtt I HA. That is why I am waiting for the new version to be released in public in a few days. A blueprint in Home Assistant gave me the opportunity to program the W100 to be actually useful. Right now the actual promised functions of the W100 in daily use doesnât exist. No matter what the one positive âreviewerâ in here thinks. We do not need to give him screenshots of our temperature or what protocol we are using. We just need Aqara to acknowledge that they have released a product or two that are still not ready for public use and that we have paid d a lot of money to test it for them. That is normally not how it works for test users. They are normally paid for their work. I donât know what you guys think but after months of pulling our remaining hair out, I really think Aqara should reach out to us all to arrange something. Right now we all have products that we cannot return to where we bought them because we only have 14 days to do so in the EU. I donât know about you outside the EU. Aqara canât make a decent working firmware, so we are stuck with a non functional setup that we all have paid for because of false promises from Aqara.
I can only recommend to anyone still facing problems to keep nagging the Aqara support.
In my case they have been very forthcoming, after several updates did not solve the issues I am experiencing with the device.
Why should we?! Youâre absolutely right - with every word.
Itâs outrageous what Aqara has done with this thermostat. The only good thing about it is that itâs quiet.
And with me they donât answer anymore.
I created an own PI controller for my Sonoff TRVZB.
This is how it looks like and this is how the W600 should act like:
Can someone confirm, that the E1 had the same bad behaivor??
E1 works great for me (although my house is cold so it never reaches target temperature anyway and I have my own control system to turn them full on or full off)
Nevertheless, operation and schedule and automation of E1 is reliable for me. I wish you had one so you could make these plots too.

