System Setting Triggering Twice

[Creeper]

Hello, I'm using the "System Setting Change" Trigger to set a local variable when the variable from the Global table updates a value but it's triggering twice because I have two Global Variables with similar names.

For example, I have two actions (Global) test_variable_switch, test_variable_function

I have set the condition to perform two of these actions at the same time and I have set the System Setting Change to monitor only test_variable_switch but it's still picking up test_variable_function and fires the System Setting Change Trigger twice.

How do I match only test_variable_switch and fire the System Setting Change trigger only once? Thanks!

 

[MacroDroidDev]

Please use report a bug in the troubleshooting section because if you have configured it to fire on one exact match then it should not trigger for the other one.

 

[Creeper]

Please use report a bug in the troubleshooting section because if you have configured it to fire on one exact match then it should not trigger for the other one.

The System Setting Change trigger is configured to match only test_variable_switch, but since both test_variable_switch and test_variable_function is set to perform the action at the same time after the other with test_variable_function being the first action in the same Else IF statement, the System Setting Change triggers twice because it matches test_variable_function too because it has a similar name. If I remove one of them, it works fine and only triggers once.

The same issue seems to be happening with Tasker as well so Idk if it's a bug. I'll report the bug if someone can confirm it.

 

[MacroDroidDev]

If the same is happening with tasker then you can be pretty confident it's because the particular value is just creating two update notifications for whatever reason. As long as the values are the same each time then you can simply use a macro not invoked recently constraint (set to 1 second) on the macro to prevent the duplicate triggering.

 

[Creeper]

If the same is happening with tasker then you can be pretty confident it's because the particular value is just creating two update notifications for whatever reason. As long as the values are the same each time then you can simply use a macro not invoked recently constraint (set to 1 second) on the macro to prevent the duplicate triggering.

This is it. I've just tested it again and the test_variable_function is triggering the test_variable_switch at the same time. And since I have another test_variable_switch set to trigger after the test_variable_function it triggers the System Setting Change twice.

The function variable is new and have it's cons over the switch variable. The function variable shows the notification to turn off the setting in the notification area but turns off every time I lock the screen, the switch doesn't show any notification, doesn't turn off and lasts 7 hours. I used system settings change detector macro to detect which turns on the notification icon and found it was the function variable. I had been using the switch Global variable for so long I didn't test the function variable individually, I just thought it was the variable to show the icon in the notification area. I should have done a bit more testing.

The macro is finally working properly and only triggering once now. Thank you so much