Have you been in contact with the support? Did they whitelist your account for the firmware update?
Ok, so I need to ask support for new firmware, I thought that participating in the beta program, enabling beta updates, using the testersâ Slack, and emailing support would be enough.
Today one of my w600 skipped the temperature automation and did not set the temperature to the planned level. The other one did.
ZigBee 0.0.0_2543
They have both worked flawlessly for a few days, but now that seems to be over.
1 Like
Thanks, added above.
Hi!
I have two W600 via Zigbee2MQTT installed and received 0.0.0_2543 on both yesterday. Zigbee2MQTT was updated to 2.7.2 with the former firmware _1839 already.
Since _2543, the valve position only shows a maximum of 10% or an unrounded percentage. 10% seems to be actually 100% since the radiator is hot.
2 Likes
I just updated 4 of 5 W600, and im receiving now positions like 3.3700000762939455%. The local temperature is 19°C actually on this trv, and the setpoint is 21°C. So 3.37% is pretty false. Did they probably changed the decimal numbers? like 0.1?
That could be the only valid reason.
I experience the same issue. Yesterday, I updated my W600 to version 0.0.0_2543 (Zigbee).
At 8:30am I opened the window to ventilate the room. After closing the window the thermostat opened fully but the valve position was set to (only) 10%.
In my opinion the valve position needs to be multiplied by 10 (since 0.0.0_2543).
Did you noticed a better heatingaccuracy or a better behaivor?
Where did you get the FW infos from? WIth z2m, i cant extract any firmware info.
I was hopeing, that this 2°C deadband is removed in this firmware, isnt it?
Then only the external temp input would be missing.
The latest firmware worked fine for two days. Since then i have a 2 °c difference from wanted temperature to what i actually get. I have tried with the thermostats combined as a group connected to w100 and as individuals where one was connected to w100. Since yesterday they have been individuals with no connected external thermostat. Still not getting the wanted temperature.
I am wondering if it would be better to connect them to zigbee2mqtt and calibrate them with Versatile thermostat plugin in Home Assistant, because the Aqara solution does still not work.
I guess 2°C difference is not acceptable.
If i have 19°C or 21°C in my Bathroom is a big difference.
Aqara said once, there is a hysteresis of 2°C between heating and non heating. Thats unaccaptable. It should be max 0.2°C to have a nice warm non-oscillating feeling.
To get the latest Zigbee firmware version, please see my post here: Questions about Aqara W600: Valve modulation and exposed attributes (#W600 #Zigbee #Matter) - #12 by LikeMike
I already installed the latest with the latest z2m converters. It is a big improvement of the older firmware
Have had the newest update for a few days. And itâs does seem to be better? But in a different way.
It now over heats my rooms by 2C. So iv got it set to 20C and my T1 temp sensor typically is saying itâs 22C. It then turns off and cools down again to a out 19.5C before turning the valve on again.
So the 2C dispersion still seems to be there, but unlike before where it would only heat up to just above 20C then allowing it to drop to say 18C before turning on again itâs doing the same thing but just over heating the room more. I mean this is more comfortable, but doesnât seem like a good solution as do still feel the chill difference between the two temps.
Still having some issues with Zigbee and it not changing to the manually set temp from time to time or it not switching to the pre programmed schedule iv set.
Sorry for my not helpful comment. ButâŚ
Why is it so complicated to do it right? And why is such a product released when it is obviously not ready for prime time?
3 Likes
Update! This evening the pop-up about previous settings appeared again and I pressed yes. Now it suddenly seems like they are working as expected again. But letâs give them a day to prove itâŚ
I checked them since yesterday. At all it looked abit better. But still dont understand the algoryhtm:
You can see the current Temp is 4°C above the target, and the valve position wasnt fully closed and it even opened afew percent more. without any interaction or changing setpoints.
I dont know if its maybe related because of the local measurement and the local calibration. Maybe with an external sensor input it would be better⌠I dont know.
I guess @AqaraOfficial should still improve the algorythm and even enable the external input!
An addition to the TRVs behaivor. I think this is unacceptable. thats around 4hours of graph shown in the screenshot.
What do you guys think about this one? Ive submitted a support ticket because of this.
1 Like
I have similar experience after updating to 0.0.0_2543 (Zigbee). Situation improved little bit, but problems still persist:
- overheating and temperature fluctuation is still present (typically -2/+2 degrees, sometimes even more)
- zigbee connection is pretty unstable. Valve is loosing connection with gateway/router many times per day for hours (5 hours of downtime is no exception)
Aqara support contacted me back because of my ticket. This was their answer:
I told them im using 0.0.0_2543 already. Hopefully this will be a newer firmware then 2543.
