Announcement

Collapse
No announcement yet.

PHLocation V2 Discussion

Collapse
This is a sticky topic.
X
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • MNB
    replied
    Paul, I've noticed that my "Home Direction" device takes ~ 5 Mins to change state from approaching to Stopped which obviously affect ones event timing (I believe you made mention in an earlier post about 5 minutes) is there any way of getting a quicker response like <1 minute? Mike

    Leave a comment:


  • MNB
    replied
    Paul, I noticed when I downloaded v.61 I got v.63, was I faster than you updating your text description? Mike

    Leave a comment:


  • sooty
    replied
    Originally posted by mwaite View Post

    Very interesting. I can see how this can get convoluted fast. I understand the thresholds you described, but I'm not sure that's what is happening. I have min. distance to move set to 0.2 miles, the phone has not moved more than 50 feet or so for the past 8 hours. Best 'not moving' time has been only about 15 minutes (all day long I've been monitoring). Some logic is definitely different than PHLocation(V1), as I didn't have this issue, it seemed like the min. distance would really have to be exceeded to trigger a new location event. In my case I've lost some functionality. It's a fantastic program though, and my donation is on the way.
    There may well be something that I missed. If it's broken I will endeavour to fix it once I know what the cause is.

    It's getting late here now so I'll look at it in more detail tomorrow but from memory, the only times it would generate a new location trigger and reset the time at location are:
    1. You have (or it thinks you have) moved more than the min dist.
    2. The "Force update of position devices" option in config>other is ON.
    3. It detects a "User has Stopped" event.

    If you've not moved for a few hours and it's only holding the time at location for 15 minutes, then something isn't right.
    Assuming you're not going to be moving for the next hour or so, go to the plug-in general config page and set debug to file ON. Leave it on until you observe a couple of resets of the time at location device (with no actual device movement) then switch OFF the debugging and email me the log file.

    paul dot huddlestone at gmail dot com

    I'll look over it in the morning.

    Paul..

    Leave a comment:


  • mwaite
    replied
    Originally posted by sooty View Post

    Things should work more or less as you describe in that the time at location should only be reset when a new location trigger occurs.

    I'll look over the code now but I think I know what may cause the extra triggers without a corresponding history entry.

    I'll try and explain.....
    The numbers are irrelevant but as an example, consider a min dist to move setting of 0.5 miles and you're travelling home with a 5 minute iCloud polling interval.
    The plug-in polls iCloud and gets the location of your device which at that time happens to be 0.4 miles from home and is also more than 0.5 miles since the last recorded location so a new location is recorded to history and the time at location device is reset.
    5 minutes later iCloud is polled again and this time you are at home and have stopped moving for the day.
    This presents a problem because you have not moved more than 0.5 miles since that last update, so the plug-in won't update your location and will show you still at the previous location of 0.4 miles away.

    To try and overcome this issue, the plug-in has a mechanism to detect if the user has stopped. I'll not try to explain how this is done here as it will take forever but what it does if it detects that the user has stopped is replace the last stored history record with the current location rather than adding a new record. This will also cause a new location trigger and reset the time at location device.

    Does that sound like it would cause the behaviour you're seeing?

    I can't just remember why it was done this way as opposed to just adding another history record but there must have been some method in my madness at the time
    Either way it would still generate a new location trigger / time at location reset.

    Another situation (discussed here recently) that could cause a new location trigger is that if the max accuracy setting > min dist to move. If this were the case, then you would see it in the history records.

    I don't use actual device location here any more (have no real use for it), but when I did I would use geofencing to control the polling. When I entered the home geofence for example I would have it:

    1. Stop polling.
    2. Wait 5 minutes.
    3. Single poll for current location.

    Polling was then resumed when exiting the geofence.

    Paul..
    Very interesting. I can see how this can get convoluted fast. I understand the thresholds you described, but I'm not sure that's what is happening. I have min. distance to move set to 0.2 miles, the phone has not moved more than 50 feet or so for the past 8 hours. Best 'not moving' time has been only about 15 minutes (all day long I've been monitoring). Some logic is definitely different than PHLocation(V1), as I didn't have this issue, it seemed like the min. distance would really have to be exceeded to trigger a new location event. In my case I've lost some functionality. It's a fantastic program though, and my donation is on the way.

    Leave a comment:


  • MattL0
    replied
    works great thanks

    Leave a comment:


  • sooty
    replied
    Originally posted by MattL0 View Post
    I am getting theses error when i try v.61. And avery time i restart the plugin

    no error on .60
    Feb-18 16:45:01 PHLocation2 (Startup) Finished at 16:45:01.353
    Feb-18 16:45:01 PHLocation2 Error (Startup) Error count is 1 Plug-In functions disabled.
    Feb-18 16:45:01 PHLocation2 (Startup) Plug-In is registered.
    Feb-18 16:45:01 PHLocation2 (Startup) 0 known locations loaded.
    Feb-18 16:45:01 PHLocation2 (InitHomeLocation) Home Location set. Lat:45.43977 Lon:-73.48173 Rad:0.5 Msg:False
    Feb-18 16:45:01 PHLocation2 (LoadConfigSettings) Distance data provider is set to Pri:None Alt:None
    Feb-18 16:45:01 PHLocation2 (LoadConfigSettings) Static map provider is set to None
    Feb-18 16:45:01 PHLocation2 (LoadConfigSettings) Dynamic map provider is set to None
    Feb-18 16:45:01 PHLocation2 (LoadConfigSettings) Links map provider is set to None
    Feb-18 16:45:01 PHLocation2 (LoadConfigSettings) Elevation Data provider is set to Pri:None Alt:None
    Feb-18 16:45:01 PHLocation2 (LoadConfigSettings) Reverse Geocode provider is set to Pri:OSM Alt:None
    Feb-18 16:45:01 PHLocation2 (LoadConfigSettings) plug-in is working in Metric units.
    Feb-18 16:45:01 PHLocation2 Error (UpgradeDb) Error! No of updates Req doesn't match No of updates done. Not updating DB version.
    Feb-18 16:45:01 PHLocation2 (UpgradeDb) Version 8 update initiated.
    Feb-18 16:45:01 PHLocation2 (BackupDb) Database backed up to BK_20190218164501.db3
    Feb-18 16:45:01 PHLocation2 (UpgradeDb) Called. From v7 To v8
    Feb-18 16:45:01 PHLocation2 Warning (Startup) Database version update required
    Sorry. Should be fixed in .62 just uploaded.

    Paul..

    Leave a comment:


  • sooty
    replied
    Originally posted by mwaite View Post
    I'm trying to figure out what constitutes a reset of the "Time @ Location" device, and 'New Location' event trigger . This is an iPhone device.

    Here's my problem:
    I have configured "Minimum Distance to Move" set to 0.2 miles, yet my 'time @ location" device is resetting well within this 0.2 miles range. The History Viewer does not show these unless the minimum distance is exceeded. This all came to light when I set an event that triggers on "New Location". New Location is triggering as the 'time @ location' resets (which makes sense), however I don't want the 'time @ location' to reset (nor the New Location trigger) if the 'Minimum Distance to Move' is not reached.

    Am I missing how this is supposed to work?
    Things should work more or less as you describe in that the time at location should only be reset when a new location trigger occurs.

    I'll look over the code now but I think I know what may cause the extra triggers without a corresponding history entry.

    I'll try and explain.....
    The numbers are irrelevant but as an example, consider a min dist to move setting of 0.5 miles and you're travelling home with a 5 minute iCloud polling interval.
    The plug-in polls iCloud and gets the location of your device which at that time happens to be 0.4 miles from home and is also more than 0.5 miles since the last recorded location so a new location is recorded to history and the time at location device is reset.
    5 minutes later iCloud is polled again and this time you are at home and have stopped moving for the day.
    This presents a problem because you have not moved more than 0.5 miles since that last update, so the plug-in won't update your location and will show you still at the previous location of 0.4 miles away.

    To try and overcome this issue, the plug-in has a mechanism to detect if the user has stopped. I'll not try to explain how this is done here as it will take forever but what it does if it detects that the user has stopped is replace the last stored history record with the current location rather than adding a new record. This will also cause a new location trigger and reset the time at location device.

    Does that sound like it would cause the behaviour you're seeing?

    I can't just remember why it was done this way as opposed to just adding another history record but there must have been some method in my madness at the time
    Either way it would still generate a new location trigger / time at location reset.

    Another situation (discussed here recently) that could cause a new location trigger is that if the max accuracy setting > min dist to move. If this were the case, then you would see it in the history records.

    I don't use actual device location here any more (have no real use for it), but when I did I would use geofencing to control the polling. When I entered the home geofence for example I would have it:

    1. Stop polling.
    2. Wait 5 minutes.
    3. Single poll for current location.

    Polling was then resumed when exiting the geofence.

    Paul..

    Leave a comment:


  • MattL0
    replied
    I am getting theses error when i try v.61. And avery time i restart the plugin

    no error on .60
    Feb-18 16:45:01 PHLocation2 (Startup) Finished at 16:45:01.353
    Feb-18 16:45:01 PHLocation2 Error (Startup) Error count is 1 Plug-In functions disabled.
    Feb-18 16:45:01 PHLocation2 (Startup) Plug-In is registered.
    Feb-18 16:45:01 PHLocation2 (Startup) 0 known locations loaded.
    Feb-18 16:45:01 PHLocation2 (InitHomeLocation) Home Location set. Lat:45.43977 Lon:-73.48173 Rad:0.5 Msg:False
    Feb-18 16:45:01 PHLocation2 (LoadConfigSettings) Distance data provider is set to Pri:None Alt:None
    Feb-18 16:45:01 PHLocation2 (LoadConfigSettings) Static map provider is set to None
    Feb-18 16:45:01 PHLocation2 (LoadConfigSettings) Dynamic map provider is set to None
    Feb-18 16:45:01 PHLocation2 (LoadConfigSettings) Links map provider is set to None
    Feb-18 16:45:01 PHLocation2 (LoadConfigSettings) Elevation Data provider is set to Pri:None Alt:None
    Feb-18 16:45:01 PHLocation2 (LoadConfigSettings) Reverse Geocode provider is set to Pri:OSM Alt:None
    Feb-18 16:45:01 PHLocation2 (LoadConfigSettings) plug-in is working in Metric units.
    Feb-18 16:45:01 PHLocation2 Error (UpgradeDb) Error! No of updates Req doesn't match No of updates done. Not updating DB version.
    Feb-18 16:45:01 PHLocation2 (UpgradeDb) Version 8 update initiated.
    Feb-18 16:45:01 PHLocation2 (BackupDb) Database backed up to BK_20190218164501.db3
    Feb-18 16:45:01 PHLocation2 (UpgradeDb) Called. From v7 To v8
    Feb-18 16:45:01 PHLocation2 Warning (Startup) Database version update required

    Leave a comment:


  • sooty
    replied
    Originally posted by teladog01 View Post

    Just found this thread, looks like maybe the registration server is down.
    The issue with not being able to register should be resolved now.

    Paul..

    Leave a comment:


  • MNB
    replied
    Steve, HS v.511 is available for downloading which I have just done will be experimenting with EasyTrigger to see if problem is resolved. I did noticed that my Virtual Device no longer has On/Off control selection so far good... Will advise later, Mike

    Leave a comment:


  • mwaite
    replied
    I'm trying to figure out what constitutes a reset of the "Time @ Location" device, and 'New Location' event trigger . This is an iPhone device.

    Here's my problem:
    I have configured "Minimum Distance to Move" set to 0.2 miles, yet my 'time @ location" device is resetting well within this 0.2 miles range. The History Viewer does not show these unless the minimum distance is exceeded. This all came to light when I set an event that triggers on "New Location". New Location is triggering as the 'time @ location' resets (which makes sense), however I don't want the 'time @ location' to reset (nor the New Location trigger) if the 'Minimum Distance to Move' is not reached.

    Am I missing how this is supposed to work?

    Leave a comment:


  • teladog01
    replied
    Originally posted by teladog01 View Post
    I've not read all 38 pages of this thread, and a search of the thread turned up no relevant results, so apologies if this has been reported and discussed already....

    Decided to try out PHLv2 tonight. When I enter my email and click the Register button on the General Settings tab of the plugin config page, nothing happens except for this error in the log:

    Code:
    Feb-17 9:50:35 PM PHLocation2 Error (RequestRegKey) WE:The operation has timed out
    The License Status still says "Trial with 30 days remaining".

    Is this a known issue? Not a biggie, guess I've got 30 days to get it resolved
    Just found this thread, looks like maybe the registration server is down.

    Leave a comment:


  • teladog01
    replied
    I've not read all 38 pages of this thread, and a search of the thread turned up no relevant results, so apologies if this has been reported and discussed already....

    Decided to try out PHLv2 tonight. When I enter my email and click the Register button on the General Settings tab of the plugin config page, nothing happens except for this error in the log:

    Code:
    Feb-17 9:50:35 PM           PHLocation2 Error     (RequestRegKey) WE:The operation has timed out
    The License Status still says "Trial with 30 days remaining".

    Is this a known issue? Not a biggie, guess I've got 30 days to get it resolved

    Leave a comment:


  • slbuck
    replied
    Originally posted by MNB View Post
    Steve, I've left the two "Execute immediate script" on and am waiting with baited breath for the way forward, Mike
    If Spud says it's possible to copy the status only devices, I'll go that route with easy trigger. For now, I've set the previous location to status only and doing the script commands. It seems to be the most reliable way to update the device.

    Leave a comment:


  • MattL0
    replied
    Originally posted by slbuck View Post

    UPDATE: Setting things back to Both resolved the issue. There's something wrong with the download for v 507 so we'll have to wait on that. Reading the fixes for that release, I don't think we'll be able to hide the controls. I've reached out to Spud to see if he can allow a status only device to be copied to another status only device.

    Mike,

    It looks like I'm still having problems updating the Previous location device with anything set to Status for the Status-Controls. I'm going to set them all back to "Both" and see if that resolves the issue.
    Feb-17 10:29:30 EasyTrigger ERROR SetDeviceValue: Cannot find control value 4 for device 2826
    Feb-17 10:29:30 Event Event Trigger "PHLocation 2 PHL - Steve - Update Previous Location"

    see this thread.
    https://forums.homeseer.com/forum/ul...ue#post1283834

    Leave a comment:

Working...
X