Android Device is Off During Time & Day Triggers

[KeeperCake]

Say you set a trigger to run at 6PM Friday. As it happens, though, your device is powered off at 6PM on Friday. Turn it back on later. The trigger will not somehow fire retroactively. Is that correct and has it always been?

Specifically, I want to enable floating buttons at set times. Thought I'd make this a general help topic, though, so other ideas for actions one might want are welcome.

Obvious workaround: use bootup trigger to run same macro. Figure out specific constraint set so desired actions get run if 6PM on the Friday in question has passed. Could factors other than power being off result in T&D triggers being skipped?

 

[Dm114]

Say you set a trigger to run at 6PM Friday. As it happens, though, your device is powered off at 6PM on Friday. Turn it back on later. The trigger will not somehow fire retroactively. Is that correct and has it always been?

Triggers - MacroDroid Wiki

macrodroidforum.com

 

[KeeperCake]

Triggers - MacroDroid Wiki

macrodroidforum.com

Note that my question is two-fold. Assuming you intended for me to read the second paragraph from your link, that's a yes to the first half but merely an implied yes to the second half. Since the second half of my question is academic, I'll shrug it off.

Benefit of date & time trigger as is: if your macro is, say, a DIY alarm clock, you'll basically be glad it doesn't ring late because the device was off.

Drawback: if a button is supposed to appear at the set time and persist until you tap it, for example. OR if you intended a variable to be set at a certain time, device power being off throws you a curve, etc.

Solution: supplement the macro(s) with the Device Boot trigger. Fine-tune so that the desired actions take effect if the trigger time has passed.

Question I was leading up to: does that solution fully address that drawback, or can anyone think of other triggers that might be necessary?

Related considerations: the system clock remains accurate upon bootup, and MacroDroid stopwatches are found to be running as if the device was never off.

All things considered: is this kind of trigger retroactivity a viable feature request? (i.e. is it feasible and is it potentially useful enough to be worth the devs' effort?)

 

[Jacob L]

It's also possible to use the macro enabled trigger. It's worth reading the help card that tells you how it works

 

[Dm114]

Note that my question is two-fold. Assuming you intended for me to read the second paragraph from your link, that's a yes to the first half but merely an implied yes to the second half. Since the second half of my question is academic, I'll shrug it off.

Benefit of date & time trigger as is: if your macro is, say, a DIY alarm clock, you'll basically be glad it doesn't ring late because the device was off.

Drawback: if a button is supposed to appear at the set time and persist until you tap it, for example. OR if you intended a variable to be set at a certain time, device power being off throws you a curve, etc.

Solution: supplement the macro(s) with the Device Boot trigger. Fine-tune so that the desired actions take effect if the trigger time has passed.

Question I was leading up to: does that solution fully address that drawback, or can anyone think of other triggers that might be necessary?

Related considerations: the system clock remains accurate upon bootup, and MacroDroid stopwatches are found to be running as if the device was never off.

All things considered: is this kind of trigger retroactivity a viable feature request? (i.e. is it feasible and is it potentially useful enough to be worth the devs' effort?)

The simplest way would be to store last system time the macro ran. Then launch it at boot time (2nd trigger or from another macro) and check whether you have to play your alarm (or a notification) or not, according to current time.