BUG - bluetooth constraint blocking trigger from working

chaoscreater

Active member
I've noticed that in the latest MacroDroid version, one of my macros (which I haven't modified for months) suddenly stopped working.

This particular macro is really simple. It just has "Bluetooth Enabled" as trigger and "Bluetooth Disabled" as constraint. When my Bluetooth is off and I turn it on, it should trigger the macro to run, but it doesn't. It used to work fine, but I think it broke either in the last MacroDroid update or the current one. If I remove the "Bluetooth Disable" constraint, then it works fine.

I'm not sure if it's because of the recent fix from here that broke it?

I've tested and confirmed the issue on 2 different phones, both running Android 11.
 
Last edited:

Dm114

Well-known member
I've noticed that in the latest MacroDroid version, one of my macros (which I haven't modified for months) suddenly stopped working.

This particular macro is really simple. It just has "Bluetooth Enabled" as trigger and "Bluetooth Disabled" as constraint. When my Bluetooth is off and I turn it on, it should trigger the macro to run, but it doesn't. It used to work fine, but I think it broke either in the last MacroDroid update or the current one. If I remove the "Bluetooth Disable" constraint, then it works fine.

I'm not sure if it's because of the recent fix from here that broke it?

I've tested and confirmed the issue on 2 different phones, both running Android 11.
I was about to suggest you to delete the 'BT Disabled' constraint because if the trigger 'BT Enabled' fires the disabled constraint isn't true anymore.
 

chaoscreater

Active member
I was about to suggest you to delete the 'BT Disabled' constraint because if the trigger 'BT Enabled' fires the disabled constraint isn't true anymore.
It's not just that particular bluetooth constraint that is not working. It's all bluetooth constraints that are not working, including "Device Connected" or "Device Not Connected".

So for example, if I have a trigger for "Device Disconnected" and I only want this trigger to run when the bluetooth constraint "Device Not Connected to XYZ Device" is true - well too bad because the constraint is broken in the latest MacroDroid version....

The point is, this worked fine before and now it doesn't and on multiple devices. It's a BUG.
 

Dm114

Well-known member
It's not just that particular bluetooth constraint that is not working. It's all bluetooth constraints that are not working, including "Device Connected" or "Device Not Connected".

So for example, if I have a trigger for "Device Disconnected" and I only want this trigger to run when the bluetooth constraint "Device Not Connected to XYZ Device" is true - well too bad because the constraint is broken in the latest MacroDroid version....

The point is, this worked fine before and now it doesn't and on multiple devices. It's a BUG.
I agree with you for the example with XYZ device: it should work. You're probably right, it might be a bug. You should report it in the Report a Bug section in the main menu.
 
Top