Time Await not working

[dany...@gmail.com]

Hi Guys,
I created a simple flow which:
- start
- block "time windows" set to "immediate" to see if it's day or night (7.00 - 23.00)
- Yes: --> Time await 23.00 ---> Wi fi off, Data off --> Loop into Time Await 7.00
- No: --> Time await 07.00 --> Wi fi on, Data on --> Loop int Time await 23.00

So it's very simple..
The problema is that time await "doesn't work".
Following your suggestions:
- I set "power save" mode to "off" for Automate
- I don't have programs which may close the app (in fact it's working)
- I set mode to "inexact" to save battery.

If I got mobile in my hands at the "time await" hour, it's ok, if screen is off it doesn't work.

Have you got suggestions (maybe a different way to implement the flow too)
Mobile: Xiaomi Redmi Note 4 rooted
Android version: 7.0 (MIUI 9.0.3)

[Henrik "The Developer" Lindqvist]

You should only need a single Time window block with proceed "Exact", where YES goes Wi-Fi/mobile data off, NO goes on.

As the doc say, "Accurate timing is impossible on Android 6+ due to 'Doze' mode. In worst case, up to 15 minutes inaccurate."

Always use proceed "Exact", and the "Awake device" option enabled.

[dany...@gmail.com]

Hi Henrik,
thank you for answer.
At the beginning I tried to use the "Time Window" block, but I noticed something strange (please confirm me the behavior).
Let's consider a time window block 7.00am --> 16 hours.
It seems to me that if the flow start before 7.00 am, so that it passes before into "yes" state, then in "no" state, it works well.
But if I start the flow at 10.00am, for example, I have to wait 7.00am of the day after for block to work.
It seems that the first block "state" must be "yes".
Have you got suggestions?
Thanks in advance.
Regards,

          Daniele

[ega...@gmail.com]

Hi,

Is anything changed about this beahvior?

Sincerely

четверг, 30 ноября 2017 г., 10:28:32 UTC+3 пользователь dany...@gmail.com написал:

[Henrik "The Developer" Lindqvist]

Use an "Timing accuracy workaround" in Automate settings.

[ega...@gmail.com]

Henrik, thanks for answering.

The real problem for me is not an accuracy, but the "Time window" block behavior when it is entered at the current time which is inside the specified time window. In this case it waits for the beginning of next window (next day) and not for the end of ongoing time window (also see the dany's description below). In my opinion, such behavior is quite illogical.

Sincerely

понедельник, 18 февраля 2019 г., 23:22:30 UTC+3 пользователь Henrik "The Developer" Lindqvist написал:

[Henrik "The Developer" Lindqvist]

To check if time is currently within the window use proceed Immediately.

All decision blocks works the same way, proceed "When changed" will await the next "event", proceed "Immediately" will check the current state.

[ega...@gmail.com]

Yes, I see, but the end of the time window could also be considered as an "event".

OK, never mind, I can use two "Time await" blocks instead of one "Time window" to do what I want. And thanks again for your efforts.

вторник, 19 февраля 2019 г., 0:21:51 UTC+3 пользователь Henrik "The Developer" Lindqvist написал:

[Henrik "The Developer" Lindqvist]

The should also always be an event with proceed When Changed, but only if you revisit the same Time window block.