Timer starts with extra seconds

jaswalters · May 10, 2022, 11:36pm

How come an HA “timer” seems to always start with added seconds?

Capture

BebeMischa · May 10, 2022, 11:42pm

I see this behavior also

jaswalters · May 10, 2022, 11:44pm

I’ve seen others with the same issue but I have found no solution as I have seen it add 5 seconds and I have seen it add 10 seconds.

tom_l · May 11, 2022, 1:35am

Either the device running the web browser or the system time is incorrect.

github.com/home-assistant/core

Timer starts with 52sec already on the counter

opened 03:57AM - 17 Apr 20 UTC

closed 02:49PM - 17 Apr 20 UTC

RomRider

integration: timer

## The problem  When I start a timer entity, the entity.last_updated gets a date that is 52 seconds behind now, which means the display is off by 52 seconds (didn't check if the `timer.finished` event happens really after 10min or 9.52min in my case or not) and on cancel, the last_updated is 52 sec ago also (you have to be fast to see it 😊). You can see it below: ![Apr-17-2020 05-51-43](https://user-images.githubusercontent.com/21064206/79530574-f4805e00-806f-11ea-9170-9eb584b8b082.gif) ## Environment  - Home Assistant Core release with the issue: 108.4 - Last working Home Assistant Core release (if known): unknown - Operating environment (Home Assistant/Supervised/Docker/venv): Docker - Integration causing this issue: timer - Link to integration documentation on our website: ## Problem-relevant `configuration.yaml`  ```yaml timer: bedroom_nebulizer_timer: ``` ## Traceback/Error logs  ```txt ``` ## Additional information

jaswalters · May 11, 2022, 4:47am

Yeppers, updated my list of NTP servers and it resolved the issue.