That’s great news. I hope we can get the same behavior with the Thread firmware soon.
Could you share a screenshot of what it looks like when the target temperature changes (e.g. from 18°C to 22°C)?
2 Likes
Sorry
after the W600’s scheduling function failed again, I have decided to part ways with all 96 of my Aqara products.
Sorry, the reason for the scheduler crash has been found. If it appears, DO NOT click “Cancel”. This is a UX design issue. Aqara will soon optimize the interaction: when a preset smart schedule is detected, this pop-up window will be removed, and the preset schedule will be enabled by default.
I am not sure if it is so much better
Today I had get access to this firmware and instaled it in the morning. We will see if in another days make some difference.
Hi, are you using the W600 built-in thermometer?
Both of mine failed with automation today. We have very cold weather and wind, so I did a little manual preheating in the early hours. The valves are set to continue automation when the next period starts but that didn’t happen today. I have pressed yes to the pop-up and I use a W100 as thermometer and the valves are combined as a group with this. The one that failed yesterday keeps saying “abnormal temperature”.
Firmware is latest Zigbee beta
Hello, I would recommend that you, for the period of bug fixing (I understand that this should not be the case), dissolve the W600 group and bind one W100 to two thermostats (separately).
1 Like
No, external, I will check if internal temperature sensor make some difference, but if there is option for external so it should work also.
Yeah these things are going back, even on the latest beta there is just no controlling them. Currently have 2 rooms set to low temperature (17c) and the radiators are blasting away. The connected room temp sensors show 20c.
Other times when a schedule is set open them up they don’t and the room is freezing.
Shame because the size and quiet operation is a bonus over the E1s but if they can’t do the basics they are useless.