【Exclusive Trial】Aqara Radiator Thermostat W600 – Be the First to Try

[phates89]

@UnrealAbyss

Solved
error: Screen rotation doesn’t work.
error: child protection doesn’t work through the Aqara Home app.
What helped:
Update version 1335
hard reset, double-clicking the device, and then holding it for 10 seconds on the third click. After adding the new device, both child lock and screen rotation started working.

I did it and the rotation of display worked, thank you!
Not sure if you can consider it “solved” if you need a reset to apply it though

@UnrealAbyss

Solved
error: Screen rotation doesn’t work.
error: child protection doesn’t work through the Aqara Home app.
What helped:
Update version 1335
In the w600 menu on the right, where you select manual mode, you can set it Forever. And select, for example, the vacation mode and set a low temperature on it.

This is a good workaround (that I already applied yesterday) but if you have an on-off toggle should be honored and not overrided. If I disable the valve heating should stay disabled (like it always have been with e1 valves).

[UnrealAbyss]

I had it working for over 96 hours and had no problems until I started turning on the “Valve Detection Notification”

[PiileLV]

The smart schedule is not working. I’ve set different temperatures, but the valve is not taking the schedule and not lowering or increasing temperature. For now only manual control is working for me.
And yes, i have ebabled smart schedule

Also, the tenoerature controlling is also wrong in my opinion. In the app it says that if the temperature drops the set temperature, then it will activate, but the valve keeps working and draining my money

So im waiting for some updates.

Also the app doesn’t recognise the W600 as a HVAC or what its called, like it recognise E1 valves. So they dont show in the same page as E1 in the app.

[Twoj_stary]

I switched back to E1 yesterday. What a relief

• Connection (temperature reporting) with external sensor lasted for 3-4 days, but eventually it got stuck again.
• Still have no idea if the device actually works in terms of opening and closing the valve. I had multiple situations when temperature dropped below scheduled value, and it stayed closed, and vice versa: continued heating after reaching (or even topping by more then 1 degree) set value. Someone suggested that it is feature, but for me such a big hysteresis makes no sense - I can clearly feel the difference between 21 and 22 degrees. Especially, that there is no such issues with E1.

Still waiting for firmware update which will provide some stability.

On the positive side: W600 schedule view inspired me to simplify my aqara app automation for E1 heating, so I do not relay on E1’s schedule anymore.

[jarenback1]

Sign me up too

a. SWEDEN
b. Compatibility ok

[AaronP]

Finally arrived in the UK
I hope to get it installed over the weekend

[UnrealAbyss]

It’s a bit late.

[gonzolex]

Is it possible for this W600 Thermostat to use an external temperature sensor, like the E1 does?
Can the firmware be updated from HA, or does it have to be connected to the Aqara app?

[pach14]

And again, after a few days W600 does not update the temperature and the controls do not work. The thermostat is in Zigbee mode, connected to the M3 on the latest firmware, and is about 1 m away.

[gafich10]

Hello.
I found the reason. You need to reconfigure the sensitivity of W100. Description on the forum. W100 (Remote Temp Sensor) Association to E1 TRV is Unstable - #5 by gafich10

[pach14]

I use standard battery temperature and moisture sensor, readings from sensors works stable about a year, but W600 stops working without any errors after few days. The readings from W600 stays flat (but connected sensor still loging temperature changes). Only solution to starts working w600 i to remove battery for few seconds, or reset device.

[Twoj_stary]

I know I am repeating myself, but I have exactly same issues. New firmware has just been released, but I will wait for feedback before i will install my w600 on radiator again.

[pach14]

Yep, new firmware version is 0.0.0_1839 for zigbee, a this moment its look like it’s more responsible, we will see if it stops working after few days.
Smart schedule starts to work, even if at night temperature doesn’t drop to setpoint, at day starts immidiently heating after automatically change scene to day mode

[pach14]

And after a day W600 stops to work. Stay closed with error. Need to recalibrate to starts heating, also widget shows only “-”, ehh

[hoppel118]

Hi, maybe I am a bit late to the party.

I installed my Aqara W600 two weeks ago and had a lot of issues with the temperature in the room. The device heated the room, even though it shouldn’t. So I deinstalled it again, because I didn’t have the time for deep dive testing. I didn’t remove the batteries in this two weeks. the W600 stayed to connected to my Thread network without any issue.

In the meantime I read this forum thread and found other guys with the same problem, which was solved by resetting the device, switching the firmware to zigbee and back to thread again. That way it was possible to update the device firmware from 0.1.1.0 to 1.0.0.0

I did that too and now the W600 does what it should. My house is full of EVE Thermos, but I really wanted to test and compare the W600 with the EVE Thermo.

So, I use the Aqara W600 and the EVE Thermo in Matter over Thread mode. Both devices are paired to Home Assistant and Apple Home. All my automations are in Home Assistant, while I use Apple Home as my Frontend.

I have 7 Apple Thread Border Routers and 73 Matter over Thread devices.

• Aqara W600 and EVE Thermo have nearly the same size, overall the W600 is a bit smaller
• Aqara W600 and EVE Thermo both use AA batteries
• Aqara W600 seems to be a bit slower than the EVE Thermo in processing the commands from my Matter fabrics, but it doesn’t seem to eat the batteries as fast, as my EVE Thermo does
• EVE Thermo is significantly louder than Aqara W600, when adjusting the temperature
• Aqara W600 has a much more informative display
• EVE Thermo can be used with the EVE app without having a hub
• Via the EVE app we can control some Matter custom cluster features (calibration, screen rotation, temperature offset, valve protection, temperature unit, child lock and transmit power)
• EVE Thermo can be bound to an EVE Thermo Control (temperature sensor) via a Matter binding, Aqara W600 doesn’t have this capability
• EVE Thermo uses Matter DCL to give us new updates. I really hope Aqara is working on this Matter OTA update feature. I also have a this thread running here in the forum.

Her you see two screenshots from the clusters on Endpoint 1 of both devices:

The EVE Thermo has (as already said) the Binding cluster, that I really miss on the Aqara W600. Therefore the Aqara W600 has a Groups cluster. What can we do with this and how can we make use of it?

The pairing procedure to Home Assistant and sharing from HA to Apple Home was smooth. But 5 hours after the initial pairing the device lost its connection to my Thread network.

This what I see in my Home Assistant log:

2025-11-21 13:25:53.460 (Dummy-2) CHIP_ERROR [chip.native.DMG] Subscription Liveness timeout with SubscriptionID = 0xed01847b, Peer = 01:000000000000016C
2025-11-21 13:25:53.469 (MainThread) INFO [matter_server.server.device_controller] <Node:364> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 0
2025-11-21 13:26:24.472 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2025-11-21 13:26:38.463 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:000000000000016C]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2025-11-21 13:26:38.464 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout'
2025-11-21 13:26:38.467 (MainThread) INFO [matter_server.server.device_controller] <Node:364> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 1
2025-11-21 13:27:15.197 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2025-11-21 13:27:29.192 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:000000000000016C]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2025-11-21 13:27:29.193 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error 'src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout'
2025-11-21 13:27:29.196 (MainThread) INFO [matter_server.server.device_controller] <Node:364> Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 2
2025-11-21 13:27:29.196 (MainThread) INFO [matter_server.server.device_controller] <Node:364> Marked node as unavailable

I already removed the batteries from the W600, waited 5 minutes and reinserted the batteries one hour ago. But the device doesn’t come back on its own. What can I do now (except resetting to factory defaults)?

Maybe this is related to firmware 1.0.0.0. What do you think?

Didn’t have such an issue for a very long time.

Thanks Hoppel

[david3]

I also have problems with the W600. That the schedules do not work, Measured temperature is wrong. Settings are not taken over and the new firmware does not work.

Do the update, will also be ready. The next day it’s gone again. Already tried 3 times.

Yesterday

Today

[ESSCO4355]

Change protocol to Zigbee then update.

[david3]

I have Zigbee

[gonzolex]

Is it possible for this W600 Thermostat to use an external temperature sensor, like the E1 does?

[gafich10]

Yes, W100 …