Hi everyone,
Setup:
- 2× W600 in one room, both on firmware 0.0.0_2848, Zigbee
- Hub M2
- Climate Sensor W100 as the external temperature source
- An automation sets 18 °C at night and 20 °C during the day
- Solid fuel boiler with 60–70 °C supply water; Grundfos Alpha2 pump running 24/7 in proportional pressure mode (about 7 W)
Problem:
Both thermostats run an automatic valve calibration 3–5 times a day, with no action from me. Each time the log shows the same three entries in the same minute:
- Valve calibration successful
- Turn on heating
- Set temperature: XX °C (the same value that was already set)
This looks like a device restart. Both units do it at the same minute or within a few minutes of each other, for example:
- Nov 16: 02:34 (both units)
- Nov 18: 02:52, 07:38 and 13:46 (both units)
- Nov 19: 00:34 (both units), 08:15/08:16, 11:21 (both units) and 16:05/16:10
During each calibration the valve opens fully, so the hot water heats the room. The W100 graph shows clear temperature steps right after the calibrations. The room stays at 23–24 °C while the setpoint is 18–20 °C, and the app shows “Temperature control abnormal”.
What I’ve ruled out:
- Batteries: replaced them in one unit. No change, and the synchronized timing rules them out anyway.
- Hub: moved the Hub M2 next to the router and unplugged it three times. No calibration was triggered.
- W100 link: switched one unit to its internal sensor. Both still recalibrated almost together (16:05 and 16:10).
- Hydraulics: the pump runs constantly at the same low power, so there are no pressure spikes.
- Manual calibration: done several times on both valves.
- Firmware: no update is available.
Questions:
- Is this a known issue with firmware 2848? Is a fix planned?
- What makes both units restart and recalibrate at the same time if it isn’t the hub or the W100?
I’ve also contacted support through the app and I’m happy to share device logs.
Thanks!
2 Likes
Hi there, it looks like you’re experiencing a support-related issue. We’ve automatically created a support ticket for you and will reach out via the forum email within the next two business days.
If other members have any suggestions or insights on this topic, feel free to share!
1 Like
Welcome to the forum, @pawel_st! That is a very well documented first post, with times, the log entries and everything you have already ruled out. It makes it easy to compare.
So I went through the logs of my four W600. All are on 0.0.0_2848, three on a Hub M3 and one on a Hub E1.
| Room |
Hub |
Calibrations in the log |
| Linus |
M3 |
Nov 13 at 22:38 and Nov 17 at 07:06, both without any action from me |
| Dining room |
M3 |
Two on Nov 13, both started by me |
| Doll room |
M3 |
None, although the setpoint changed many times |
| Party cellar |
E1 |
None, the log is completely empty |
Two things I take from this.
1. There may be a way to tell automatic from manual. When I started a calibration myself, the log shows two entries: first the start of the calibration, then “Valve calibration successful” about two minutes later. The two entries in the room Linus only show “Valve calibration successful”, with no start entry before it. My app is in German, so the exact English wording of the start entry may differ. Can you check whether yours look the same? If your 3 to 5 per day all come without a start entry, we are looking at the same thing.
2. It happens here too, but far less often and not in sync. Two automatic calibrations in one week, on one unit out of four. The other units did nothing at those times, even the ones on the same hub. So in my setup it looks like something the single device does, not something the hub triggers for all of them.
That makes your case stand out in two ways: the frequency, and the fact that both units do it in the same minute. Whatever causes it seems to reach both of your valves at once. Is there anything the two share that the rest of your Aqara devices don’t, apart from the room?
I did not see overheating after my two events, but with only two of them I would not read much into that.
2 Likes
Thanks a lot, Frank, that’s really helpful!
1. Start entry: No, there is no start entry in my logs. Every automatic calibration appears as three entries in the same minute:
- Valve calibration successful
- Turn on heating
- Set temperature: XX °C (the value that was already set)
So it looks the same as your Linus case. The extra “Turn on heating” and “Set temperature” lines suggest to me that the device restarts and restores its state. Do your two automatic events in Linus also have these two lines after them?
2. What the two units share:
- The same hub: a Hub M2. You’re on M3 and E1, so this could be a key difference. These are the only Aqara thermostats on my M2.
- The same W100 as the temperature source. Switching one unit to its internal sensor didn’t stop the synced calibrations, though.
- Window Detection set to “Door/window sensor detection” with a linked Aqara door/window sensor. I checked the sensor logs, and no open or close event matches the calibration times.
- The same automations: every setpoint change is sent to both units at the same moment. The calibrations also happen at times when no automation runs, e.g. 11:21 and 16:05.
Restarting the hub doesn’t trigger a calibration; I unplugged it three times.
Aqara support has asked for log access, which I’ve granted, so hopefully they’ll find something. I’ll post an update here.