Closed gpayer closed 1 week ago
Hello @gpayer,
Thank you for the detailled report.
- I turned on using the central preset configuration
- Now all VTherms are in state
heating
I don't understand why you consider it is wrong. If you "turned on using the central preset configuration" ll VTherm are heating. What did you expect ?
Hm? Aren't presets values for "comfort", "eco", etc.? I thought what you describe is central control. If changing the values for comfort, eco, min and max temp etc. are somehow also responsible for setting the mode of a climate then this needs some serious explanation and translation check.
Or did you misunderstand me? I meant "enabled the 'use central preset configuration' feature in the configuration in section 'presets'". I did NOT turn on anything by using the central control. I don't even know where it is.
If it helps you I can take screenshots of what I did or take a screen recording.
Ooooh,
Or did you misunderstand me? I meant "enabled the 'use central preset configuration' feature in the configuration in section 'presets'".
Yes ! If I say it with my words, when to check the "use central preset configuration" on one VTherm, this turn on all VTherm.
If this is true (I will give it a check), this is not normal at all. At just something like that in https://github.com/jmcollin78/versatile_thermostat/releases/tag/6.6.1.beta2. Can you give it a try ?
What I fix was that, when you reconfigure on VTherm, all the others are reloaded. And because, the last state was not always written, this could lead to the bug you describe.
Hey, that' great to hear!
I tested with 6.6.1.beta2 and it seems to fix this bug, I could not reproduce it. And it was very easy to reproduce with 6.6.0. So, I'm looking forward to the 6.6.1 release! :smiley:
That is most quickly fixed bug of my history ! 😄
Version of the custom_component
6.6.0
Configuration
VTherm Wohnzimmer:
VTherm Arbeitszimmer:
Describe the bug
I encountered this bug in my production system, but was able to reproduce it in my test system, where I use climate mockups via mqtt. (I really have to extract them to a new repository, they are great for testing)
I did the following:
off
heating
heating
Reconfiguring while off does not trigger this bug. And it seems to be related to the central configuration in some way, changing nothing or other stuff does not necessarily trigger this bug.
Debug log