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

[Feature] Master clock capability #107

Closed
m4rky-m4rk opened this issue Jan 10, 2022 · 3 comments
Closed

[Feature] Master clock capability #107

m4rky-m4rk opened this issue Jan 10, 2022 · 3 comments

Comments

@m4rky-m4rk
Copy link

m4rky-m4rk commented Jan 10, 2022

Would it be possible for the binding to act as a master clock for openwebnet?

I see regular time and date frames on the BUS using the own client. I assume the BUS master clock sends this frame and the slave clocks use it.

Problem:
MH202 and Screen10 do not use an NTP server. After resuming from a power outage the BUS clocks are no longer correct. Also, daylight saving has to be done manually.

Solution:
The openHAB system clock is always correct, it syncs with ntp severs, has automatic daylight saving change, and its easier to use an UPS to avoid power interupts. So, the openHAB binding would be the better choice for the BUS master clock with other BUS clocks acting as slaves (this is an optional setting in the config for MH202, Screen10)

https://community.openhab.org/t/openwebnet-bticino-openhab3/128305/27?u=m4rk

If not possible then maybe something could be done via rules and generic command already requested:
#52

@mvalla
Copy link
Owner

mvalla commented Jan 11, 2022

@m4rky-m4rk please move this issue/feature to openhab/openhab-addons repository

@m4rky-m4rk
Copy link
Author

m4rky-m4rk commented Jan 11, 2022

Done

openhab#12018

@mvalla
Copy link
Owner

mvalla commented Jan 16, 2022

closing this as it has been moved to openhab/openhab-addons repository

@mvalla mvalla closed this as completed Jan 16, 2022
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

2 participants