@Aaron: Did you watch the video in the play store from AutoLocation? It’s a pretty nice example of how to set it up. Was your geofences service running?
Keen to switch vswitch directly from within tasker - makes most sense. understand you links - thank you for those. no joy though? trying it in a browser first and I get an “ok” response - but no action takes place?
Did you take the correct MIOS-Seerver as described in the other thread? Very strange if you get an OK but no action. Did you adjust the link in order to switch a virtual switch?
Hi there,
Got it working - think I may have suffered from a slow vera as after some restarting and f5’ing I got results working in browser, locally / remotely, and via Tasker remotely using:
https://MYSERVER/MYUSERNAME/MYPASSWORD/MYUNITNUMBER/data_request?id=action&output_format=xml&DeviceNum=IDNUMBER&serviceId=urn:upnp-org:serviceId:SwitchPower1&action=SetTarget&newTargetValue=1Who knows - working now though - thanks again. I am just finalising my final PLEG logic and will test over the coming days but after initial tests expecting good results - lets hope so 
I am using Llama (with its cell based location) instead of Tasker and AutoLocation. It is simpler, but free and works for me very nice. It can’t do the request directly, but you can use a shortcut to almost any Home Automation app, I use HomeBuddy.
AutHomation should work with out any issue with Llama. It should also be able to use the tasker plugins that AutHomation contains to make adding an action simpler.
- Garrett
do you mean the one with the Store (large & small) example? I tried a few things and it was not working properly for me yet. Do you have 2 separate Profiles for inside & outside the fence, or are you using entry & exit Tasks in the single Profile?
No, I only have one profile per geoefence. Each profile has one entry and one exit task. Did you make sure the link you are using to switch the virtual switch on the vera is working correclty in a browser?
Hi all, mine working well, also one geofence per desired area as this is most battery efficient and works well. The faq on the auto location site is a good break down of the functions also. I tested my tasker and auto location by having it turn my phone to silent. Once this worked well I then swapped the turning phone to silent mode to the Vera task instead. So far it workig well and I am working on gd PLEG logic to make things work well specifocaly for my needs. Would not use this for locks but great for upancy states etc.
Sent from my HTC HD2 using Tapatalk 2
Yup… when I use my previously used Profile using Tasker’s Network Location (one profile, entry & exit tasks defined) it works fine using the same ‘tasks’ as I’m trying to use with AutoLocation.
[quote=“garrettwp, post:26, topic:178980”]AutHomation should work with out any issue with Llama. It should also be able to use the tasker plugins that AutHomation contains to make adding an action simpler.
- Garrett[/quote]
Thanks Garret, I am using Llama and I found an HTTP Post plugin for locale that works with Llama, it works great since it can update the status in Vera without the need of any other app.
Another alternative that has worked for me without the need to ever touch a phone (because the wife doesn’t like me to be installing and testing things in her phone, its hers!), it just involves ping, but has worked very nice for me:
[ol][li]First, via the router, assign a static IP to the phones MAC address, leaving the phone in DHCP.[/li]
[li]Create a Ping device in Vera for that device.[/li]
[li]Set ping count to 3 (or whatever you think it would work, I selected that because 1 and 2 failed very often and 4 was a lot), the time Period doesn’t matter because it will be controlled with PLEG.[/li]
[li]Create a self-retrigger timer for each device that will give time to failsafe, I set 2.5 mins, could be less, could be more, depends on your experience. This time is the one that will let the phone be disconnected without triggering anything.[/li]
[li]Create the conditions to trigger the timers and set the period to a lower value so it pings more often the phone if it comes back, I have it in 15 seconds.[/li]
[li]Finally create the conditions that really do something when Vera is “sure” that the phone is out. Of course this has a little delay when you really leave the house (in my case, because of my timer and period set, up to 2:30 plus 15 seconds, total 2:45 at most. In this action, set the period back to something more wide, I set 120 seconds so it is not pinging so often when the phone is not home.[/li]
[li]If you like, in the comeback condition for each device, you can set an intermediate period, I have 90. So I have finally three periods. (1) 90 when I am at home, (2) 15 when my wifi disconects or ping fails and (3) 120 when I am out of home.[/li][/ol]
I am attaching my status.
PS. My turn_off_all_empty_home condition looks complicated because it is a workaround for PLEG 5.5 before the off timestamp where implemented, I have not updated yet, but the new syntax should be this which has the same effect but with less code:
fusam_left_home AND fudan_left_home AND !fusam_leaves AND !fudan_leaves AND (fusam_left_home;!fusam_leaves) AND (fudan_left_home;!fudan_leaves)for those that use autolocation and followed the video example, if you reboot your phone, does the autolocation rerun its “scenes”? Mine does. what do i need to do to fix this?
I found that AutoLocation has been very, very, very bad for me. It triggers sometimes when I’m 10 miles away.
Tasker’s native Network Location has been 1000x better.
But to answer your question… YES, IT WILL retrigger upon a reboot unless you use Tasker to set variable that live across reboots.
[quote=“Aaron, post:34, topic:178980”]I found that AutoLocation has been very, very, very bad for me. It triggers sometimes when I’m 10 miles away.
Tasker’s native Network Location has been 1000x better.[/quote]
I have to agree with this. AutoLocation was regularly reporting me to be over 100 miles from where I actually was. And it was butchering my battery. I uninstalled it. While the regular location stuff in Tasker is better it still is absolutely in no way whatsoever, in any way at all, remotely accurate and reliable. Many times a day does it report me being nowhere near where I really am.
I’ve had good luck with Tasker native. Usually updates in a minute or so
Sent from my SAMSUNG-SGH-I747 using Tapatalk
i think i’ll just skip the geofence and use nfc instead. Thanks for the input.
Ping Sensor?
Ping Sensor?[/quote]
I will do this when i can get my wireless network overhauled. I don’t have the distance needed to make it work from my driveway.
keith,
try Tasker’s native Network Location. I have mine set to 100m from my home and usually when I’m about 150 feet from it my Tasker triggers to tell Vera I’m home (using AuthomationHD integration). The most delay is usually leaving the location… sometimes that takes about a minute or two to trigger the Away task. Thus, seems more accurate/sensitive entering the location vs exiting. This is fine for me as I also have my Ping sensor which PLEG watches to set my alarm to AWAY after 2 minutes of failed Pings. This redundancy has worked almost flawlessly.