Skip to content
This repository has been archived by the owner. It is now read-only.

Flow with timed action doesn't start at time XX:XX #290

Closed
Arjanvde opened this issue Mar 2, 2016 · 17 comments

Comments

Projects
None yet
5 participants
@Arjanvde
Copy link

commented Mar 2, 2016

What is your Homey version (Settings → System)?

0.8.20

What did you try to achieve?

I'm trying to achieve that Homey switches it's LED ring to brightness 0 when the times 21:49. I've waited until the time was 21:49 and no action, looking at the geek log i did see it switched at 21:49:58.

schermafbeelding 2016-03-02 om 21 50 06

What was the result?
I was impatiently waiting on an action at 21:49 and nothing happend. When i cam e back with a cup of tea i saw that the LED ring was off and was surprised it was off and it needed a few attempts to find out that it was switched on at 21:49:58. I seriously thought that i did something wrong at my first attempts.

What did you expect as result?
The light ring to turn to brightness 0 at exactly 21:49:00. It would be wishful that it would be switched on at the exact time as that could be easily checked with the computer time.

@Arjanvde Arjanvde changed the title Flows with timed actions act Flow with a timed actions don't start at time XX:XX Mar 2, 2016

@Arjanvde Arjanvde changed the title Flow with a timed actions don't start at time XX:XX Flow with timed action doesn't start at time XX:XX Mar 2, 2016

@KroontjesPen

This comment has been minimized.

Copy link

commented Mar 3, 2016

Conformation on this behavior.
If you are testing and for a 2 minutes window is this too much.
Let well, the switch time can be xx:xx:02.

Delay now 26 sec.

@KroontjesPen

This comment has been minimized.

Copy link

commented Mar 3, 2016

For the record.
It is the flow time and not the voice time that is good.

Delay now 29 sec.

@WeeJeWel

This comment has been minimized.

Copy link
Contributor

commented Mar 3, 2016

Is your system time correct?

@WeeJeWel WeeJeWel self-assigned this Mar 3, 2016

@Arjanvde

This comment has been minimized.

Copy link
Author

commented Mar 3, 2016

At the "Stuff for geeks" screen the system time is one hour behind (Currently showing 11:45). Even though it is one hour behind when i set the timer in a flow in 12:45 it activates the flow somewhere at 12:45.

It would be preferable to have it switched at 12:45:00 exactly, not somewhere within the 12:45 minute range.

@KroontjesPen

This comment has been minimized.

Copy link

commented Mar 3, 2016

System time is synchronized every hour and there are no strange noticed in the log there.

Delay now 46 sec,

@KroontjesPen

This comment has been minimized.

Copy link

commented Mar 3, 2016

With some practice I could Homey say the time on xx:xx:58, xx:xx:59 and xx:xx:00 and it was the right one.

Delay now 48 sec,

@bvdbos

This comment has been minimized.

Copy link

commented Mar 4, 2016

same for me...

@WeeJeWel

This comment has been minimized.

Copy link
Contributor

commented Nov 1, 2016

Does this still occur on Homey v0.10.7?

@bvdbos

This comment has been minimized.

Copy link

commented Nov 1, 2016

For me it doesn't. Always firing within a few seconds of the exact time....

@WeeJeWel

This comment has been minimized.

Copy link
Contributor

commented Nov 1, 2016

Alright great! I'll close this issue until someone still experiences problems.

@WeeJeWel WeeJeWel closed this Nov 1, 2016

@Arjanvde

This comment has been minimized.

Copy link
Author

commented Nov 1, 2016

Just created a test flow which whould fire on 12:42 it did fire on 12:42:24. See also my screenshot for a flow which should fire on 12:45 (I expect it to fire on exactly e 12:45:00)

flow 1

flow 2

So the issue still persists.

Could be that it is by Homey's nature that it starts somewhere in the 45 range?

@bvdbos

This comment has been minimized.

Copy link

commented Feb 6, 2017

@Arjanvde does this still happen for you?

@Arjanvde

This comment has been minimized.

Copy link
Author

commented Feb 6, 2017

@bvdbos Jup still triggers somewhere within the set minute.

@bvdbos

This comment has been minimized.

Copy link

commented Feb 24, 2017

24-2-2017 07:00:50.748 Speech-output Speech {"text":"het is 06:59 ","type":"say","session":"homey"} with this flow:
schermafdruk_2017-02-24_07-02-32
but to be honest, the flow doesn't declare the time has to be told at the exact hour... As for the time it's saying, that's #1315

@Arjanvde

This comment has been minimized.

Copy link
Author

commented May 2, 2017

Did some research myself.

The issue is that Homey's Cron is rolling and it only is able to trigger a flow around 40 times at exactly 09:00:00. From there on, it triggers the flow on 09:00:01 for around 40 times etc. In the attached file I did some monitoring and it has 41 triggers between 09:56:45 and 10:37:45, and has 38 triggers between 10:38:46 and 11:18:46.

A flow with a timed action starts when Homey's cron has passed. This also applies for Sunset/Sunrise, this does start somewhere within the minute.

@WeeJeWel can you say whether this is able to be resolved or is this Homey's behaviour.

Rolling.txt

@WeeJeWel

This comment has been minimized.

Copy link
Contributor

commented Aug 14, 2017

I've changed some behavior in the upcoming 1.5.0-rc.6 release. Please let me know whether this issue still persist.

@Arjanvde

This comment has been minimized.

Copy link
Author

commented Aug 18, 2017

Did some tests (today and yesterday) and it looks like this is solved correctly. Thanks!

@Arjanvde Arjanvde closed this Aug 18, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.