1
Solved

Bluetooth Connected profiles don't fire when a Name variable is used

Tasker is not firing a Bluetooth Connected event (Profile) if I put a string in the Name variable in the event.

This is a Profile that I've used for years, and it recently stopped working - after Tasker and my Phone both updated, so I'm not sure which one may have caused the bug.

The profile triggers an action to set a sound/volume profile in another app, whenever my truck's bluetooth connects to my phone.  But for testing, I created an even simpler profile and gave it one action: to produce a popup message "BT Connected".

I tested this profile with NO parameters (no name, no address), and it works. The event fires each time I connect any bluetooth device.
Then I tested again, with a known bluetooth device name in the profile Name field. It fails to fire.. I copied the name string directly from the device name in my phone settings.
Then I tested a third time. This time I removed the name string; and I added the bluetooth device's MAC address. This time the Profile fires OK.

I repeated these steps a few times, and used a couple of different devices to be sure of my results.

I also tried changing the device name in my phone settings, to a very simple text string with no numbers or punctuation. This did not help.

Tasker is auto-updated from the Play Store, and it's on version 5.12.22
All tasker permissions are enabled, none are disabled in my phone settings > apps > permissions.

Phone is Pixel XL, fully updated. Android version 11; security update June 5 2021; Google Play system update May 1, 2021, Android build number RQ3A.21605.005

Follow

2 replies

Votes Newest Oldest
KW

Hi Joao,

That worked. (I feel silly, I didn't realize I could do it that way.)
So, it seems that when I rename a device in my phone > bluetooth devices list, my new name/label isn't visible to Tasker.

I am something like 60% confident that it used to work, because (a) I almost always rename my bt devices; and (b) I've always manually entered the names in my Tasker profiles.  But I never paid close attention to this before, so maybe for the one device that I used in this profile, I had never renamed it, and it was always using the factory name, so it just never mattered?

In any event, my immediate problem is solved. Thanks!

Yeah, maybe that was it 😄 Glad it works!

Hi. Can you please try using the magnifying glass in the condition to select the device instead of writing it manually? Thanks

Topic is closed for comments