BT near: "No currently paired device matches this context so it can never activate"

161 views
Skip to first unread message

Jochen Pinnekamp

unread,
Sep 4, 2015, 4:13:50 PM9/4/15
to Tasker
Hi all,

I'm trying to set up tasker to enable BT when I'm in my car. The Phone and Car are already paired.
I chose the device directly through tasker, set any device class and standard and LE devices as well as toggle BT.
When I exit the configuration the warning in the title appears.
(Also, it does seem to never activate.)

Am I misunderstanding the configuration?
From my point of view, anything that tasker offers as a choice for the device should be paired, therefore it must be able to match it.

Any ideas, what could be wrong?

Thanks and Regards
Jochen

Brad Minion

unread,
Sep 5, 2015, 10:02:54 AM9/5/15
to tas...@googlegroups.com
In my experience I find it best to select as few qualifiers as needed. I would try locating the BT device by clicking on the magnifying glass (you probably already did that) and then any device class, check standard devices (not also LE) and toggle bluetooth. The car's probably not an LE device. The other thing to consider is how your car "looks" for a device to connect with. Some cars might only look when first turned on. Some might look every so often or continuously. Then there's how often BT near looks. I think the default is every 5 minutes when the screen is off. Whatever the timing of these "look" periods, your car and phone would have to be looking for each other at the same moment. That seems somewhat hit and miss to me. But, to be honest, I've never used BT near. I leave BT on 24/7. I have used Wifi near though so I think they probably work similarly as far as the timing goes. Maybe someone else has done this and can help.

--
You received this message because you are subscribed to the Google Groups "Tasker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.
Visit this group at http://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.

Rich D

unread,
Sep 5, 2015, 8:18:49 PM9/5/15
to Tasker Google Groups Post


> I chose the device directly through tasker,
set any device class

Ok.

and standard and LE devices as well

This might be  the issue... from the userguide...

Standard/Low-Energy Devices: if you're only interested in a particular type of device, select only "ONE" of these to reduce power usage.

Jochen Pinnekamp

unread,
Sep 8, 2015, 1:18:16 PM9/8/15
to Tasker
At least when leaving the screen, i get the same message. But I'll Grey iff it detects it anyway.

Thanks for the advice.

Jochen Pinnekamp

unread,
Sep 8, 2015, 1:21:00 PM9/8/15
to Tasker
Mmh, i guess that is possible. I just assumed it was a configuration issue because of the message that tasker gives.

But if i cannot get it to run I'll keep bt on permanently.

Thanks.

Reply all
Reply to author
Forward
0 new messages