Welcome to Smart Home Forum by FIBARO
Dear Guest,
as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.
As a member you can:
- Start new topics and reply to others
- Follow topics and users to get email updates
- Get your own profile page and make new friends
- Send personal messages
- ... and learn a lot about our system!
Regards,
Smart Home Forum by FIBARO Team
Question
Komate 0
Dear Community,
I am experiencing a strange behaviour that I consider a bug.
Environment:
I am using a HC3L for heating including radiator and boiler control. I have a thermometer and a valve actuator in each rooms but no physical thermostats.
I'm using QuickApps as virtual thermostats to store setpoints. Climate schedule sets these virtual thermostats that also can be overridden manually. The heating scene is comparing thermometers' and virtual thermostats' values to control the valves and the boiler.
Expected behaviour:
In the HC system the manual override is always set for a specific duration and it has the highest priority. When I override the climate schedule for a device (a room) I expect that the override will be in action until the duration runs out regardless the setpoints meantime. After that the room's setpoint gets reset to the then actual scheduled value.
Problem:
In practice the manual overrides are always get reset when the schedule reaches a setpoint. Since overrides are set for an exact duration this behaviour seems faulty alone. But the situation is even worse: the overrides are always get reset when any zone's schedule reaches a setpoint! That means if I turn the heat up in the living room for the evening movie time it gets reset in every half an hour, even when the towel dryers stop heating in the bathroom. What makes this bug even worse is that not needed setpoints cannot be disabled in the schedule.
It can be a partial workaround if I modify the schedules to avoid the most of the interference but it's not an ultimate solution. I started to develop this system to make the usage more comfy for my family but this bug makes it harder to use.
I've updated the OS recently to 5.170.16 from a years old beta but I didn't try overriding before so I don't know if it worked correctly with the old OS.
Thank you in advance
Please login or register to see this attachment.
Edited by Komate2 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.