I broke my geofence
Steve Blethen
ssblethen59 at gmail.com
Mon Feb 28 19:56:12 EST 2022
Hi All,
This problem has been solved. It turnes out the GPS coordinates of the entry/exit of the geofence WAS a feature a few years ago. Since then the author of Locative eliminated this “feature” as it put excessive pressure on iPhone batteries and caused delays acquiring this data and subsequent transmission of the entry/exit notification. They didn’t make a big deal about eliminating this feature as it wasn’t being used. I guess I’m the only guy who ever thought up a reason to try to integrate this information into his HA system.
-Steve
> On Feb 23, 2022, at 9:29 AM, James Sentman <james at sentman.com> wrote:
>
> I’m sitting waiting on new tires for my wifes car right now, but I’ll experiment with this when I get home. I am fairly sure I am using the /locative link for my own but I’ll not know for sure till I get home. If they have changed things I’ll get that sorted out. I know that they did something that required some reconfig but I can’t remember right now what they changed. i think it was just they no longer supported the default and you had to specifically set up the links for every link? I’ll check it soon.
>
> The /locative link assumed that the data about which geofence name was being entered or existed would come in as a form element from their servers by default. If you change the layout or whats included in this then it will not parse it properly and give the kind of errors you’re seeing. I would turn debug mode on for the JSON/HTML server and record some of the data that is actually being sent. The individual hits will end up in a folder on the desktop as separate files for ease of sorting through them when there can potentially be a lot of traffic to filter through. At a minimum it needs to send the name of the geofence point as you setup and whether you are entering or exiting. I can find my examples and saved off code bits when I get home later but you’ll need to at least send the same data that it sends by default, after that you can add anything else new that you need which should be able to be passed through to the script of the unit but again I’ll verify that too later on.
>
>
>
>> On Feb 20, 2022, at 5:50 PM, Steve Blethen <ssblethen59 at gmail.com <mailto:ssblethen59 at gmail.com>> wrote:
>>
>> I was using the /locative option. Never had any problems with it until I paid for the custom web hook option. I’ll give your suggestion a try. Fixing geofence problems can be a drag as I’ve got to make the changes and then go for a ride to trigger locative. The “test” option will prove the server works but otherwise it doesn’t help me confirm things actually work.
>>
>> I’m still gonna need the GPS info because of where I’m located in relation to the main road.
>>
>
> Thanks,
> James
>
>
> James Sentman http://www.PlanetaryGear.org <http://www.planetarygear.org/> http://MacHomeAutomation.com <http://machomeautomation.com/>
>
>
>
>
> _______________________________________________
> XTensionList mailing list
> XTensionList at machomeautomation.com
> http://mail.machomeautomation.com/mailman/listinfo/xtensionlist
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.machomeautomation.com/pipermail/xtensionlist/attachments/20220228/dd47d02c/attachment.html>
More information about the XTensionList
mailing list