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

FR100 - thermostat time correction from ntp #536

Closed
odelcourt opened this issue Jun 2, 2022 · 8 comments
Closed

FR100 - thermostat time correction from ntp #536

odelcourt opened this issue Jun 2, 2022 · 8 comments
Labels
bug Something isn't working

Comments

@odelcourt
Copy link

Since update to v3.4.1 (coming from 3.3.1), every second I have this message in console:
000+00:54:48.710 I 2158: [thermostat] thermostat time correction from ntp

screenshot1

it seems to "overwhelm" the thermostat because it respond much slower to command from MQTT (changing mode, tuning one wwonetime,...). I have deactivated the NTP sync on the EMS and I have no more the message in the console and the thermostat react to command "as usual" (fast). It seems that the "thermostat time correction from ntp" occupies the EMS bus.

My Thermostat is a BOSCH/JUNKERS FR100 . Do you need other information(s) ? Can I actually do something else than deactivate the NTP sync ?

screenshot2

@odelcourt odelcourt added the bug Something isn't working label Jun 2, 2022
@MichaelDvP
Copy link
Contributor

Can I actually do something else than deactivate the NTP sync ?

That's one option, second is to set the clock correctly, than it needs no correction. Third is, that is seems the clock for FR100 is not writable, so we have to disable the clock-setting command for this thermostat. I'll make a PR to dev build.

MichaelDvP added a commit to MichaelDvP/EMS-ESP32 that referenced this issue Jun 2, 2022
@odelcourt
Copy link
Author

That's one option, second is to set the clock correctly, than it needs no correction.

I have checked / tried that with no success :-(
I had not that problem before, is it something that has been changed with the version 3.4.x ?

@MichaelDvP
Copy link
Contributor

v3.4 checks the clock and if thermostat clock differs much from NTP it writes the corrected time to the clock, see #386. But for some thermostats the clock is not writeable via ems-bus. Sad that this was not detected in beta tests.

@odelcourt
Copy link
Author

v3.4 checks the clock and if thermostat clock differs much from NTP it writes the corrected time to the clock, see #386.

OK, this explains this.

But for some thermostats the clock is not writeable via ems-bus. Sad that this was not detected in beta tests.

Bah. You can't test all with all hardware.... and the workaround was easy. Thank you for the follow of the tickets.

proddy added a commit that referenced this issue Jun 3, 2022
fix #536 and uart task priority
@proddy
Copy link
Contributor

proddy commented Jun 7, 2022

Can we close this?

@odelcourt
Copy link
Author

Can we close this?

How can I test this ? I guess I have to install a dev version? But mine EMS-ESP32 is used in "production", thus have you a dev build "safe" ? Otherwise, yes you can close this but I will only be able to test it with the next official release. Many thanks for your support and development.

MichaelDvP added a commit to MichaelDvP/EMS-ESP32 that referenced this issue Jun 8, 2022
@MichaelDvP
Copy link
Contributor

I've made a test branch based on main build and only add this patch. You can check here, source here, and after test you can also go back to previous builds.

@odelcourt
Copy link
Author

I've made a test branch based on main build and only add this patch. You can check here, source here, and after test you can also go back to previous builds.

Tested successfully. I'll keep that version running for now. Many thanks !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants