Logical flaw?

[FrameXX]

So I have been helping micheluzzo with his problem and making an example macro for him, but I noticed one thing with this macro. It should work like when you turn screen on and then if you shake anytime in the first 10 seconds MacroDroids vibrates mobile. This works, but for no appearant reason MacroDroid also vibrates when variables allowing shake trigger to fire changes to false. System log just says that variable chnaged to false and action vibrate happened with no trigger. This "flaw" only works if you shake at least once in 10 seconds timeout before variable changes to false.

I didn't wanted to bother Jamie via troubleshooting section so I am calling you to import macro (from file I attached) and try the macro if it's same for you, or you can tell me that I am an idiot and missed something important.

Macro itself of course makes no practical sense, but still should work.

 

[Elenkhos]

This setting could explain the behavior you're seeing so check it's disabled:

 

[FrameXX]

This setting could explain the behavior you're seeing so check it's disabled:

View attachment 283

It was enabled, but I turned it off and it's still same. It's not caused by this.

 

[SuperDaniel]

May be a Bug, looks like that after wait the triggers fire again?

You could move the shake actions before screen on or use macro cancel after you set the variable back to false

 

[Elenkhos]

Yep, seems like a bug with multiple triggers and if clauses based on the triggers. If the vibrate on shake option is enabled, it shouldn't be visible in the system log, so it was a long shot.

 

[MacroDroidDev]

I think the issue is that the last trigger invoked is being set to shake so by the time it gets to this clause it think the trigger was actually a vibrate when it clearly wasn't. A workaround to solve is to use an IF/ELSE condition. I will add this to my list of things to investigate but I suspect it may not be a trivial fix so I will have to see.