W600 thermostat: Collection of infos and open issues

Since there are quite a few threads about the W600, I thought it would be a good idea to collect all the open issues and relevant information in one topic.

I plan to keep this updated for new firmware updates.

Current firmware versions

Zigbee: 0.0.0_2543
Thread: 1.0.0.8

Note

These firmware versions are still in beta phase, your Aqara account needs to be whitelisted by the Aqara support to receive the update. (Activating beta firmware updates in the Aqara Home app does not seem to be sufficient)

Alternative: Zigbee2MQTT supports OTA updates for the W600 when using the dev branch as mentioned in this post.

Important info about firmware update mechanism

Known Issues

General

Zigbee only

Thread only

List of W600 Issue Threads

Outdated firmware versions

Zigbee: 0.0.0_1839, 0.0.0_2442
Thread: 1.0.0.0, 1.0.0.6

23 Likes

Thank you so much for your dedication.
Since I follow all of the mentioned threads, Iā€˜m happy that you consolated all of them into one single post.

Looking forward to the Aqara team to get all the remaining issues fixed soon.

7 Likes

Good work. I will post upcoming problems here.

For now I can not yet get the 2442 firmware (Beta updates is enabled) so my problems still are there. But will monitor it and will report back here.

3 Likes

How can I be whitelisted to receive latest update?

4 Likes

Please read the complete post carefully.

[…] your Aqara account needs to be whitelisted by the Aqara support to receive the update.

3 Likes

I added a link to create a ticket to the post.

4 Likes

Hi, so the new firmware version seems to be okay. So far, the valves are working as expected with a small temperature offset, though the firmware has only been running for a day.

​I still need to link them with the W100 sensors. If anyone has experience with the connection and stability, let me know. Previously, my W100s disconnected a few times and changed their sampling frequency on their own. This might have been caused by the older W600 firmware. I had it configured according to the values posted here on the forum.

1 Like

Hi everyone, could someone help me with an automation for when a window is closed? Currently, I have it set up so that closing the window triggers the valve to turn on and switch to ā€œautoā€ temperature regulation.

​The problem is that the radiator gets hot immediately and takes a long time to cool down, causing the room to overheat for about 2 hours. I’m thinking about changing the logic: when the window closes, set the temp to 14°C, wait 10 minutes, and only then switch to auto mode.

​Do you think this will work? Or how do you have your heating automations configured to prevent this?

2 Likes

Hi, thanks for the feedback. You are talking about the _2543 Zigbee firmware, right?

1 Like

Yes. _2543 Zigbee

2 Likes

I am assuming it requires an Aqara hub as well?
I was hoping to upgrade the firmware through the Aqara Home app, so I factory reset the device to unpair with Z2M. However, after choosing protocol in the app, I seem to be stuck as it is prompting me for which Aqara hub I have.

Yes, adding a device to the app requires an Aqara hub. I’ll clarify that above.

But it is already listed as an issue and I hope Aqara will enable more firmware update mechanisms in the future.

Personally I hope to be able to update my devices via Home Assistant and Matter.

Same but I would love to update via Home Assistant and Zigbee. Unfortunately, it is not possible as confirmed by the Aqara Technical Support. I hope Aqara will change it.

ā€žRegarding your question about updating the Zigbee firmware without an Aqara hub, unfortunately, firmware updates for the W600 in Zigbee mode require an Aqara Zigbee 3.0 gateway (with version 4.3.8 or higher). The protocol switching (between Zigbee and Thread) does not trigger a firmware update.ā€œ

2 Likes

In my opinion this is outrageous. Aqara advertise that w600 would be work with Matter, but without updates, this product is crippled on that platform. I am very disappointed and I think strongly about return whole order of aqara devices.

3 Likes

good to know. thanks for quoting this. I mean matter and zigbee are be design vendor independent. so it should not be necessary to buy special hub. one for aqara, one for switchbot, one for… just to speak a vendor independent protocol.

that’s not what i expect when i buy such a product!

me too!

3 Likes

How to get newest firmware, as a early tester I still have 0.0.0_1839, beta updates enabled, and still outdated firmware. Hardware was released and known issues remained, and testers have no option to check if new firmware resolves issue or if there is new ones.

Your account has to be whitelisted by Aqara Support. Check the link in the note section from the post.

Could you please mention in the post to which region your account is connected to?
I only get 0.0.0_2442 beta and the support told me it depends on the server region. Unfortunately they don’t mentioned the right region to get the latest version :frowning:

Európa - Slovakia

As someone actively testing Aqara devices, I’m wondering how I can effectively validate current functionality or bug fixes when the latest firmware available to me—for both the W600 valve and the M3 hub—hasn’t been updated since mid-November.
I even checked recently to see if anything had hung up in this process and switched between Zigbee–Matter–Zigbee, but I still have an archaic firmware version. I’m managing with workarounds, but that’s not really the point

BTW today I’ve received update for aqara app to 6.0.9 till then I was stuck on 6.0.7