Thanks to @gekjan the valve position has been fixed (already available on the dev branch of Zigbee2MQTT) and will be available with the next release of Zigbee2MQTT on 1st February 2026.
1 Like
Futher update using Zigbee latest beta update. smart schedules on some of my TVRâs just fail to run half the time. 2 of my 7 W600âs their schedules seem to work no issues what so ever. The others are completely hit and miss.
How is this possible? The when in the app when you try and change them manually they do not update in the app and will not change temp. Itâs as if they are locked up and frozen and you have to come back in 10 or 20 mins and try again.
I am also facing various problems with my smart heating devices, even on latest firmware.
W100:
When I change the frequency of updating the temperature to âHighâ, it resets to âStandardâ every time when I look again.
âConnect thermostatâ stays at âNot associatedâ all the time, even if I have connected my valve group.
W600:
I have created a group of 4 W600. When I change the temperature of the group, e.g. from 18 to 20 degrees, this is saved and displayed correctly. But the temperature of the devices itself will stay at 18 degrees.
I have linked my W100 to the group of 4 W600 and have set the W100 as temperature source for each device. I have set the temperature for the group to 18 degrees. However, the temperature in the room wonât go beyond 17,4 degrees (measured at the W100). The valves itself display even lower temperatures (around 15-16 degrees). This is strange because 1. they are linked to the W100 and 2. If they display the temperature based on their own sensor, the temperature directly at the valve should be higher than the temperature at the W100, as the W100 is placed at some distance to the radiators.
I do not want to use Schedule Management. But even if I turn it off, the setting switches to âEnableâ again after some time.
W500:
If I change the Temperature Range Buffer, this will be reset to the default value of ± 0,5 degrees afterwards.
I have turned off the device and try to turn on again, but this doesnât work. If I go to the device page again, it is offline again.
All devices are connected to a hub M200 using Zigbee.
Firmware versions:
Hub: 4.5.20_0021 / Zigbee 0017
W100: 0.0.0_1539
W600: 0.0.0_2543
W500: 0.0.0_1030
This is very interesting.
The valve position should not be constant for an hour if the temperature is above target. The jump of the valve position without a change in current or set temperature suggests there is a fundamental problem with the control algorithm.
There might be a bug in the implementation of the integrator of the controller or it might be a problem with the sampling rate, but thatâs just guessing.
Unfortunately, I donât see the valve position with the Thread firmware, so I canât perform any meaningful tests myself.
Yes, i think the whole PID algorhytm is broken. They need to find a better solution for it.
The support told me they are whitelisting accounts for a new test firmware, but they didnt respond to my reply after this message.
Probably (hopefully) they doesnt mean 0.0.0_2543 (Zigbee). This is still not working.
I think at all this TRV is one of the best ive tested yet, but there are 2 things left to fix:
- External Temperature Input
- The still totally broken PID controller
if they fix it, i will probably buy another 10 pieces. Now im running 5 already
1 Like
I absolutely agree. The hardware is great, the software not so much (at least not the controller part).
In theory a PI controller is the right solution for this use case. However, the current behavior of the TRVs does not really match what I would expect from that kind of controller.
1 Like
Yes. Well⊠We will see what will happen next. I just can suggest to open tickets at aqara, so they will get pressure to do something.
If there are only a few tickets, they probably wont do anything
I can see nobody care about Matter user here, but I would ask anyway. I had two W600 connected to Aeotec hub and then to SmartThings. I read here that some of you update via app without hub. If I would also do that, did it change something for Matter? Did Matter is only proxy for underlying logic? Can somebody answer me?
Hi @cr4zybaran,
as far as I know it is currently not possible to update the Matter firmware without a hub like the M100. This is currently only possible for Zigbee with Zigbee2MQTT.
Iâm using the W600 with Matter myself and I did see some changes with the recent updates. I donât know whether the control algorithm is exactly the same for both Zigbee and Matter, though.
I contacted the aqara support again and and they told me they are still working on the optimization:
Do you have any E1 TRVs? Iâve got 4 and they all seem to function well*. It would be interesting to see if you graph the raw values for the E1 if itâs control algorithm is as retarded as the W600?
Note* My house is under heated to nothing ever reaches target temperature anyway, which is why I want to be able to control the valve position manually. But this is a separate issue I asked Aqara about.
1 Like
One more âminor issueâ I found, I do not see any battery status via Z2M in my Home assistant⊠
1 Like
There is a new Firmware for W600.
ZigBee 0.0.0_2644
5 Likes
Nice! Did you install it already?
I need to wait till someone get it and uploads it zo z2mâŠ
Yes installed on 3 Devices, lets try out
Sounds good, I hope they will also update the Thread firmware.
New firmware, and the first thing happening⊠the pop-up asking about existing configuration data. Shouldnât that have been fixed?
1 Like
Hi all! New Aqara owner here. I donât see new firmware for the W600 thermostat within the app. I am using it over zigbee. Could it be location based?
Thank you very much!