Does MacroDroid support Exit Tasks or do I need two Macros?

[Kelemvor]

Coming from Tasker, it has Tasks that run when a profile is activated, and you can have an Exit Task that runs when the profile is no longer active. Does MacroDroid support that or do I need two separate items?

E.g. I have a profile that runs when my Bluetooth connects to my car. Then I have an Exit Task that runs when I'm no longer connected to my car.

In MD, do I need to setup one Macro with a BT Connected trigger and a separate one with a BT Not Connected trigger?

Thanks.

 

[RSF]

MacroDroid doesn't have the exact same concept, but you can add a second trigger to a macro to handle an exit condition. Sometimes having both a trigger and an exit trigger in the same macro is useful, since they can share the same local variables (and you have one vs. two macros to deal with).

Put both triggers in the macro (e.g. Bluetooth connected, and Bluetooth disconnected), and add an IF statement with a Condition to test for which trigger was triggered using MacroDroid's "Trigger Fired" condition.

 

[JosefHamel]

MacroDroid doesn't have the exact same concept, but you can add a second trigger to a macro to handle an exit condition. Sometimes having both a trigger and an exit trigger in the same macro is useful, since they can share the same local variables (and you have one vs. two macros to deal with).

Put both triggers in the macro (e.g. Bluetooth connected, and Bluetooth disconnected), and add an IF statement with a Condition to test for which trigger was triggered using MacroDroid's "Trigger Fired" condition.

For a slightly more compact version, use constraints instead of IF statements for single instructions.