Help with BT Near not triggering

1,077 views
Skip to first unread message

Justin Stroud

unread,
May 25, 2016, 12:50:53 PM5/25/16
to Tasker

I have a Android Headunit in my vehicle, with a BT name of "Jeep Commander" and a OBDII device with the name "OBDII". Both become active when I turn on the key. I want to use either one of these with the BT Near function on my phone.  I have a Nexus 6P with Tasker, and a pair of LG Tones that I use when not in the vehicle.


What I'd like to happen is, once I turn the key and start the vehicle, I'd like for it to disconnect my LG Tones and connect to the headset. I've set these up using BT Near (using both the name and Mac of the headunit and the OBDII) and they run manually, but I cannot get BT Near to trigger. I'll post screenshots of how I have it setup. What am I doing wrong? Thank you much!



Screenshot_20160525-122604.png
Screenshot_20160525-122611.png
Screenshot_20160525-122625.png

-Marsh-

unread,
May 26, 2016, 2:19:40 AM5/26/16
to Tasker
BT Near is not working for me either on my Note 5 running Android Marshmallow.
It doesn't seem to be able to access connected/paired devices unless the Bluetooth settings window is open (phone settings not tasker settings)

If you get into your car, and launch the Bluetooth settings on your Nexus 6P, does the Tasker Profile activate?

Pent

unread,
May 26, 2016, 2:26:43 AM5/26/16
to Tasker
Do you have some form of location enabled in Android settings ?

Google is getting touchy about 'locating' oneself with BT or Wifi.

Pent

Justin Stroud

unread,
May 26, 2016, 10:22:52 AM5/26/16
to Tasker
I do have location services on. I'm going to concede defeat and run it like this. All that's required from me is to switch off my headset before I turn the key. Was hoping for 100% automation, but this works as well. 

http://m.imgur.com/a/tqcul

Pent

unread,
May 27, 2016, 3:04:06 AM5/27/16
to Tasker
Well, if you want to keep trying the next step is to remove the specifications you've made in BT Near
to check if it's an ID problem.

Pent

-Marsh-

unread,
May 27, 2016, 4:11:00 AM5/27/16
to Tasker
You keep deleting or locking my help request... your suggestionsite here (or in my post you deleted does nothing to fix the issue)

Not good support for people that paid for this app...

Pent

unread,
May 27, 2016, 4:55:40 AM5/27/16
to Tasker


You keep deleting or locking my help request... your suggestionsite here (or in my post you deleted does nothing to fix the issue)

You posted the same issue on multiple threads, that gets messy.
 

Not good support for people that paid for this app...

 
Not good forum usage to multi-post because then the answers get split over
several threads.

So... you've enabled location and removed any specification of address or name
in the BT Near state and still no activation ?

Pent

-Marsh-

unread,
May 27, 2016, 11:07:59 AM5/27/16
to Tasker
I only posted on here that I was having a somewhat similar the issue with BT near also, and suggested to Justin something to try...

I did not want to "thread" steal so I created my OWN post with my own issues, and example of what I was experiencing...

That is correct, Location service is on, and there is nothing in the name or address and type is set to ANY.
Only option changes was "Standard" from unchecked to checked. I then get a pop up that says it will never activate because no currently paired device matches the context.
I wait 3 min after creating the task, with the screen on... and it never activates. I've waited up to 5min.

Only way it "activates" is if I open the Bluetooth settings window on my phone and my phone starts scanning.

Justin Stroud

unread,
May 27, 2016, 11:26:11 AM5/27/16
to Tasker
I ended up having to totally do away with BT Near. I could not get it to trigger at all. I ended up changing it up and getting it to work 100% hands free, and I couldn't be happier. 

http://imgur.com/a/m7ccf

Pent

unread,
May 27, 2016, 11:28:25 AM5/27/16
to Tasker

That is correct, Location service is on, and there is nothing in the name or address and type is set to ANY.
Only option changes was "Standard" from unchecked to checked. I then get a pop up that says it will never activate because no currently paired device matches the context.
I wait 3 min after creating the task, with the screen on... and it never activates. I've waited up to 5min.

And the BT device is definitely not a 4.0+ BT version ?

BT is turned on I assume ?

Pent

-Marsh-

unread,
May 27, 2016, 11:45:38 AM5/27/16
to Tasker
Which Device are you asking about? My phone? It's a Galaxy Note 5
The are server BT devices sitting within 10ft of me; FitBit, Beats Studio Wireless, Surface Pro 4, Samsung Level U, x2 Raspberry Pi BT hats, Samsung Gear S2, and a couple others.
No idea if they are BT4.0+ version, I never looked into it... but I'm sure one is bound to be, and one is not.


Why is it when I click the magnifying glass next to Name or Address, they are listed as connected... but if I select one of them then try to exit the profile it tells me it will never activate because
no currently pair devices match... even though it was selected from a list of pair devices... (separate issue)

Pent

unread,
May 29, 2016, 3:49:27 AM5/29/16
to Tasker

Which Device are you asking about? My phone? It's a Galaxy Note 5

The BT device.
 
The are server BT devices sitting within 10ft of me; FitBit, Beats Studio Wireless, Surface Pro 4, Samsung Level U, x2 Raspberry Pi BT hats, Samsung Gear S2, and a couple others.
No idea if they are BT4.0+ version, I never looked into it... but I'm sure one is bound to be, and one is not.


Why is it when I click the magnifying glass next to Name or Address, they are listed as connected... but if I select one of them then try to exit the profile it tells me it will never activate because
no currently pair devices match... even though it was selected from a list of pair devices... (separate issue)

The list shows you paired devices. Maybe you selected a BT LE device from the list and selected 'Standard Devices' only further down, for instance.

If you only clicked Standard and you get the error that no paired device can match, that implies they're all BT LE.

Pent

-Marsh-

unread,
May 29, 2016, 10:43:26 AM5/29/16
to Tasker
I've tried all combinations. I've given up on the creating this profile in tasker. The BT Near does not function properly for me in Tasker.
I switched to the Automate app which works fine. So I'll just use that.
Reply all
Reply to author
Forward
0 new messages