Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handling of heater control device connectivity issues - Heater controller stays on #196

Open
papadi opened this issue Jan 6, 2024 · 2 comments

Comments

@papadi
Copy link

papadi commented Jan 6, 2024

I have the feeling that when the thermostat attempts to turn off the heater when it is unavailable (e.g. because of a connection issue) then it will leave it on forever. Is there a way, or perhaps shouldn't there be a way for the thermostat to ensure that the heating controller is at the correct on/off state periodically?

I noticed this problem recently when I moved my WiFi router and my heating controller (Sonoff 4CHPRO) connection became unreliable. Of course, this is a problem I have fixed already. However, I remember that my heating controller stayed on for hours two or three times in the past as well.

@semxx
Copy link

semxx commented Mar 15, 2024

I have the same problem. When the switch has been unavailable for some time, thermostat will stay ON and state will no change when temp set target bellow threshold. It's abnormal any way. When I try to turn off my switch manual then HAS thermostat service set turned on thermostat after few seconds (triggered by service Home Assistant Core Integration: Generic turn on)

UPD
The problem has been solved after apply clear integral value:

service: smart_thermostat.clear_integral
target:
  entity_id: climate.smart_thermostat_ilia
  

Btw the problem is present. If device (switch) lost connectivity, PID collect in DB incorrect value and apply it for a long time... After that thermostat stay in ON mode. I think in some cases it may be dangerous.

@Chupaka
Copy link
Contributor

Chupaka commented Mar 15, 2024

Did you try to debug using pid_N sensors? I suspect that can be because of control_output is stuck at 100% like I described in #151. When you cleared pid_i, that decreased control_output, so pid_i can now change again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants