You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One thermostat (Comet DECT) sets a wrong temperature, mostly at night.
The FRITZ!Box monitors the temperature. At around 10 PM, I used the "good night" scene which sets the temperature to 16° C. Instead, you can see the temperature rising. At 5 AM, it starts to rise again with all of us sleeping and no automation. In the morning, the thermostat shows a set point of 25° C. There is neither an automation in the home app, nor in the FRITZ!Box
I have had the exact same issue with the kitchen thermostat about one year ago, and since I could not find any solution, I replaced one thermostat with a new one. The new one is in another room and the Comet DECT from there was moved to the kitchen. Now it is the same issue.
We're using the updated HomeKit architecture on iOS 16.4.1, homebridge is running on v1.6.0, the Fritz Platform plugin is on v6.0.19.
Has anyone any idea why this happens?
The text was updated successfully, but these errors were encountered:
One thermostat (Comet DECT) sets a wrong temperature, mostly at night.
The FRITZ!Box monitors the temperature. At around 10 PM, I used the "good night" scene which sets the temperature to 16° C. Instead, you can see the temperature rising. At 5 AM, it starts to rise again with all of us sleeping and no automation. In the morning, the thermostat shows a set point of 25° C. There is neither an automation in the home app, nor in the FRITZ!Box
I have had the exact same issue with the kitchen thermostat about one year ago, and since I could not find any solution, I replaced one thermostat with a new one. The new one is in another room and the Comet DECT from there was moved to the kitchen. Now it is the same issue.
We're using the updated HomeKit architecture on iOS 16.4.1, homebridge is running on v1.6.0, the Fritz Platform plugin is on v6.0.19.
Has anyone any idea why this happens?
The text was updated successfully, but these errors were encountered: