Add support for NTP configuration via DHCP (fixes #689)#1798
Add support for NTP configuration via DHCP (fixes #689)#1798agners merged 2 commits intohome-assistant:devfrom
Conversation
|
Hi @redgryphon, It seems you haven't yet signed a CLA. Please do so here. Once you do that we will be able to review and accept this pull request. Thanks! |
There was a problem hiding this comment.
Ideally we'd like to have also an option to set the NTP server from the user interface (Supervisor). However, for that systemd-temesyncd would need a D-Bus property to set the NTP server via D-Bus. That is currently not available 😞
However, this is independent, and for now we can set NTP server via config file as your PR suggests.
Oh, that would be the end goal for everyone I suppose.
Is it because there is something to be done in Home Assistant or because systemd-timesyncd lacks the support for it? |
Because systemd-timesyncd lacks the support for it. It has already a D-Bus interface, so I think it should be fairly straight forward to add it. |
If I ever got time in the near future that could be something I'd like to tinker with. We'll see. |
|
This has been merged in the latest beta - question is, how can we check what's the currently active NTP server set in the system? |
|
There is no built-in way in Supervisor or CLI to get the NTP server, currently. Similar to editing NTP server it would need D-Bus support (see #1798 (review)). If you have enabled SSH access to the OS, you can check the logs to see what server has been used (using |
If I'll find some time I am able to create another PR for this information to be available at least in the CLI. |
…me-assistant#1933)" This reverts commit 0c9cfde.
…ant#689) (home-assistant#1798)" This reverts commit f62fee2.
I managed to create a working solution that fixes #689. It works in my lab but I think it is pretty straightforward to be understood and to be reproduced as well.