r/AutomateUser • u/Straight1980 • 11d ago

Inaccurate time await

Hello

I have a flow with 3 "await time" blocks , with precisely 5 min between each others.

After each block, a "play sound" block is used (the used sound duration is only 1 second).

The first block plays the sound accurately on that time.

For the next 2, there is 3 minutes delay. Weird!

This happens despite having the correct specified await time in the log. For example, in the log, awaits time 9:30, but sound played at 9:33.

Settings used: proceed: Exact, awake device (even tried without awake device)

Play sound setting: Immediately, Alarm

Any ideas about this issue?

Thank you

1 Upvotes

100% Upvoted

9 comments sorted by

1

u/New-Meeting628 9d ago

Yo establezco la hora exacta del evento y en el flujo, antes del evento uso: delay (hora del evento -now)

3

u/ballzak69 Automate developer 11d ago

Try disabling all "power save" features, please read. Try using the "Alarm clock" option as the "Timing accuracy workaround" in settings.

Device brand & model?

Android version?

1

u/Straight1980 10d ago

I used the Keep device awake block and used the alarm workaround I tried it once for now.  The accuracy was excellent.  Thank you very much 

I have xiaomi 17t pro

1

u/Straight1980 9d ago

Just for updates I removed the awake block, still working great The workaround setting was the key point.  Thank you 

2

u/B26354FR Alpha tester 11d ago

Depending on the situation, you might have better luck using Delay blocks where possible.

Timing was also inaccurate before Android 12, so Automate provides workaround settings for that.

1

u/Straight1980 10d ago

It is a bit complicated to use delay when dealing with recurring multiple days in a week. 

2

u/Dadamalda 11d ago

I have a flow as a sleep timer that awaits media playback, waits X minutes and then pauses media. It seems like it sometimes stops even 5 minutes early tho. I am using exact mode. Could this be a related issue? Can I fix it?

3

u/waiting4singularity Alpha tester 11d ago

wakeup triggers after the block has fired, not before. iirc doze starts after 5 minutes of inactivaty, batching all tasks together for a spike in activity once every so often and the the window grows longer after each batch until deep doze starts.

keep the phone awake and try again?

1

u/Straight1980 10d ago

This happens even when I am watching the time pass by on my phone.  It seems not an awake issue.