Automation run later 3 minutes about core HOT 16 CLOSED

Still broken in last version. No reaction here?

from core.

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

from core.

Still broken

from core.

What are you running HA in?

from core.

HA OS as virtual machine in ESXI.

from core.

You have an issue with your VM getting time from ESXI. Verify that your time sync is working properly. I.e. this is not an issue with HA, but an issue with your VM setup.

from core.

I don't understand and i thinkyou are wrong. HA OS have some time. I hope HA has ONE and only single time value. This time may be right may be wrong, may be different against "real" time. But read again what i wrote.

I did NOT wrote "automation run 3 minutes later after REAL TIME (checking some atom clock)".

What i am saying is "Automation should run every half hour (/30 setting) but it runs at 10:03, 10:33, 11:03 of HA time not real time".

Look again on this:

I think it is total irrrelevant what "real" time is. My HU runs automation on wrong his internal time.

from core.

I think it is total irrrelevant what "real" time is. My HU runs automation on wrong his internal time.

HA in a VM on ESXI get's it's time from ESXI. There's nothing else to it.

Start here:
https://knowledge.broadcom.com/external/article/312204/troubleshooting-ntp-on-esx-and-esxi-6x.html

from core.

Euh, it works on everyone else's machine, so it's likely not a bug in HA but in your setup

from core.

@Petro31
Ok. Again. ESXI machine has 10:03 time. Real atom world ultimate clock time is 10:00. ESXI don't know it is 10:00. You wrote "HA in a VM on ESXI get's it's time from ESXI". So one and only time HA knows is that same as on ESXI. So this SHOULD happen in this config:

• real world time 9:57 (but ESXI nor HA don't know this)
• ESXI = HA time 10:00
• automation is triggered at 10:00
• automation detail should show starting time 10:00
• automation should say "it is 10:00"

Again - please explain how THIS is possible:

Only explanation is HA has samehow TWO times inside and in some case get "time 1" and in other cases takes "time 2".

Your explanation with unsynced NTP time is nonsense sorry.

from core.

Well, based on your attitude, I'm just not going to reply anymore. I don't have time for negativity.

from core.

I am very positive. I contribute to HA when i post bugs and i hope for better HA and less buggy HA. But when someone say "this is not bug" he has to have good arguments. So "I'm just not going to reply anymore" will not resolve this bug. Please read again my posts, i didn't say "you are dumb" but i try to explain bug in detail.

And @joostlek "it works for everyone" is not proof there is no bug in HA sorry..

from core.

Okay so why are we having a discussion about if this is a bug or not. You should just not have different time settings and it will be fine. I don't see this as a bug because the software is not intended to be run like this.

from core.

Sorry but you still don't understand problem. You wrote "just not have different time settings". Different from WHAT? @Petro31 wrote "HA in a VM on ESXI get's it's time from ESXI." So only ONE time value exists - time on ESXI machine and that very same time on HA. Where is that "second" time? There is no second time, there is no "different" time. Maybe there is bug right inside that "HA in a VM on ESXI get's it's time from ESXI" algorithm.

I think best way could be implement NTP into HA. But "HA in a VM on ESXI get's it's time from ESXI" is blackbox and maybe buggy blackbox. But rather than solve problem you closed it. Sorry not good attitude.

from core.

Don't forget that your browser also has a time which can be used with for example date inputs. I do agree that your attitude is very out of line. You keep explaining that it's our problem, but if that was the case, we would have at least a thousand issues about this. And we don't so this is an issue for 1 person on about a million users. That means its likely your problem, and not a HA one.

from core.

Don't forget that your browser also has a time which can be used with for example date inputs.

This can easily be confirmed by looking at the automation trace. I'd be willing to bet that the automation shows that it's firing at 10am local time translated to UTC, but because his UTC is set 3 minute in the past and his browser is not, the browser shows 10:03.

Download the trace and show us it's json.

from core.