Closed jmcollin78 closed 10 months ago
To use it just add into your configuration.yaml the following configuration:
versatile_thermostat:
...
safety_mode:
check_outdoor_sensor: false
I understand this new setting completely ignores the external sensor failure. But when it fails (no new value for a while), it means that we no longer know/trust the outside temperature, so maybe the calculated power could be completely wrong. What would happen if the external coefficient was just temporarily set to 0 (zero) when sensor failure is detected, until it is sending values again? Wouldn't the resulting power calculation give a better value than using a constant preset value? For example, when at 60%, it would drop to 50% instead of 10%, maybe? And if the temperature continues to rise in the room, it would eventually drop to zero.
You have the choice to not ignore and then have a constant instead of the power (this is the current behavior) and ignore it and then the power is wrong as you said but because the coef_ext is generally very low (0.03) this is not a real problem.
You have the choice.
When the outdoor temperature sensor is in failure, the safety mode is triggered.
Because the outdoor temperature has a limited influence on percent calculation, it should be possible to deactivate it if the user think it is acceptable.
To avoid adding more configuration parameters, an global option in expert mode (so in the configuration.yaml is the prefered way). This option is not activated by default (the outdoor temperature can trigger the safety mode).