Pass WIFI Presence from Tasker

#1

1) Give a description of the problem
Looking for the easiest way to use WIFI near to toggle virtual presence sensor. Would also like to do the same with Bluetooth connected (car).

2) What is the expected behaviour?
Example…if near wifi “home” and bluetooth connected to “car” - then open garage door. I suppose in the end I want if presence sensor car = true and presence sensor home = true, then open garage door

3) What is happening/not happening?
Nothing, nothing at all, I am a newb.

4) Post a Green Snapshot of the pistonimage
(UPLOAD YOUR IMAGE HERE)

5) Attach logs after turning logging level to Full
(PASTE YOUR LOGS HERE THEN HIGHLIGHT ALL OF THE LOGS AND CLICK ON THE </> ICON TO FORMAT THEM CORRECTLY)

REMOVE BELOW AFTER READING
If a solution is found for your question then please mark the post as the solution.

#2

I’ve not used it myself as I have an iphone, but if you use android I suspect you will be able to do this with the tasker app.

I know others on here use it for quite a few automatons.

#3

Easy to do in Tasker. (in the “Profile” tab)

Just keep in mind that when your screen is off, “WiFi near” is only checked every X seconds.
(you can adjust it in: Preferences > Monitor)

  • If you make that number too small, your battery will be used up quicker
    (it checks all day, every day)
  • If you make the number too large, it might not “see” you right away.
    (it’ll see you the next time it checks)

To help with this, you can buy the Tasker plugin called AutoLocation. This plugin lets you program to automatically change your location “sensitivity” throughout the day, so you can get precise accuracy when you want it, and battery conservation otherwise.

I’d probably use Tasker to send a HTTP Get to the External URL of a piston that only does one thing:
Opens Garage Door

I would probably drop this logic since your phone already has to be in the car for the earlier “bluetooth connected” to be true…

I would definitely drop this logic since your GPS will likely not show you as home the instant you pull into the driveway.

Basically, it’s only a single line piston here in webCoRE, with 99% of the programming being done in Tasker. (Thankfully, there’s great people on the Tasker forum or in the Tasker group)

At the risk of sounding negative, it’s important to note that with today’s technology, GPS location service will not be as fast as the time it takes you to manually push the garage remote button. I believe this also applies to “WiFi near”. Even if you drain your battery quickly with WiFi checks every 10 seconds, (instead of the default 120s) you may still find yourself waiting for the door to open.

#4

Just to clarify, my last post is with the assumption that you want your doors opening automatically when returning home…

If, on the other hand, you want automation when leaving the garage, may I recommend the Tasker trigger of:

IF MyPhone connects to MyCar's bluetooth  (event > net)  Rare event
Then run Task:
    IF WiFi is near home                  (state > net)  Common state
    Then 
        Send HTTP Get to a webCoRE piston that opens the garage door

(using the piston’s External URL)

This one would work nearly instantly 100% of the time when exiting the house.
(well, about 1 second after your BT connects, that is)

Note though that it will never work when returning home… that is different logic entirely…
(see my previous post for my thoughts on that)

Safety Tip:

If your Bluetooth is typically slow to connect to your car, I would not recommend the above, since the garage door will stay closed until after your BT connects. (with the car potentially running in the meantime)

#5

In a nutshell:

Tasker’s “WiFi near” is great for 100% confirmation, but not for instant responses…
(unless you take a battery hit, or construct a lot more programming in Tasker)