Weird behaviour with "Minimum Activation"? #1914
Unanswered
homerojleal
asked this question in
Q&A
Replies: 4 comments 3 replies
-
|
Hello, Can you give me your custom attributes of the the VTherm ? (Dev Tools / State). |
Beta Was this translation helpful? Give feedback.
1 reply
-
Beta Was this translation helpful? Give feedback.
2 replies
-
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hello, I transform this discussion into an issue because it seems there is an issue. Thank you for the report. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment




Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
My TPI settings are as follows:

I'm using version 9.3.0 and only setting I have "outside the "UI" and in the configuration.yml is as follows:
versatile_thermostat:
max_on_percent: 0.7
Looking at the graphs...I believe the "Minimum Activation" is not working as expected.
Even though I have the value = 1600s, it seems to turn off the switch even before reach 1600s of on_percent/time.
And I also verify that temperature does not rise above upper threshold (20.8 set point + 0.3 high-TPI threshold).
Is there something I'm might be miss understanding in regards to the expected behaviour?
Is there an open-known issue related to this "possible problem"?
Beta Was this translation helpful? Give feedback.
All reactions