-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
Calibrating and finding overshoot value times out waiting for heating system to start on v4 #77
Comments
Maybe we need to look again at the new OPV calibration process. Meanwhile you can test the manual OPV calculation method #36. |
For reference, these are the logs on v3:
While this also logs a similar message for a while, it does after some minutes return with a calculation in the config low, allowing me to finish setup of the device. |
On v3 I get a OPV of ~31c after about 3 minutes, should I not trust this value and rather calculate it myself? |
Yes, better not to trust this value. What’s your boiler brand? |
Remeha Avanta |
Just started my journey with SAT, after realising this winter that the Ideal weather compensation system does not work if you plug in an opentherm thermostat over an on/off one, it becomes a glorified outdoor temp sensor and expects the thermostat to do all the work. Anyway same problem for me Ideal Vouge Max C40, autotune doesn't finish and timesout and just sits there, so for not done a quick manual calc and got a value of 44 not idea if this is close :) |
Yes, this value looks fine. |
On v3 I can configure SAT with automatic gains calculation, on v4 this times out after 10 minutes without ever having started anything it seems:
Upgrading to v4 afterwards does work and I seem to be able to control the gateway without issues after initial setup and then upgrade.
I am using a nodo shop opentherm utp gateway connected to a Rehema Avanta c28 boiler and a Nest v3 OpenTherm thermostat. SAT is connected to the opentherm gateway through serial over tcp. Please let me know what I can do to troubleshoot this or if there are any other logs I can provide you with.
The text was updated successfully, but these errors were encountered: