Unexpected BT device connected trigger behaviour

Pseudocyclic

Well-known member
I just merged two macros.

One had the trigger 'Bluetooth event - device connected - any' and the other had the trigger 'Bluetooth event - device connected - headset'.

When headset connected, both of the 'old' macros were triggered.

I presumed that now, when headset connected, the 'new' macro would be triggered twice.

But it isn't. The 'Bluetooth event - device connected - any' trigger fires but the 'Bluetooth event - device connected - headset' trigger does not.

I didn't expect this. Am I missing something obvious?
 

dhj49er

Well-known member
I just merged two macros.

One had the trigger 'Bluetooth event - device connected - any' and the other had the trigger 'Bluetooth event - device connected - headset'.

When headset connected, both of the 'old' macros were triggered.

I presumed that now, when headset connected, the 'new' macro would be triggered twice.

But it isn't. The 'Bluetooth event - device connected - any' trigger fires but the 'Bluetooth event - device connected - headset' trigger does not.

I didn't expect this. Am I missing something obvious?
I wouldn't expect your merged macro to run twice, as that would require 2 triggers and there is only 1.

However, the 2 macros, albeit with slightly different triggers, will each run on when the headset connects. The event is the trigger for each macro.
 

Pseudocyclic

Well-known member
I wouldn't expect your merged macro to run twice, as that would require 2 triggers and there is only 1.

However, the 2 macros, albeit with slightly different triggers, will each run on when the headset connects. The event is the trigger for each macro.
Merged macro DOES have TWO triggers - one trigger from each of the two macros that I merged, ie 'Bluetooth event - device connected - any' AND 'Bluetooth event - device connected - headset'.
 

dhj49er

Well-known member
Yes...the merged macro has 2 triggers, but there is only 1 event.

MD will run the macro on the first match of the event to the triggers.

There is no 2nd event to trigger the macro again.

That's my understanding on how MD works.
 

Pseudocyclic

Well-known member
Thanks for that, I've got it now.

I tested again, then switched the positions of the triggers, and then re-tested.

Whichever trigger is in the first position is the one that fires.

Thanks again!
 
Top