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, clarification in regards to maps; I see that I can input both static and dynamic maps particulars within a) the Configuration>Mapping tab and b) the same within Users / Devices>iPhone device>PHLocation2 tab. My question is what is the difference between the two and how should I use them as I'm assuming that my iPhone is being used in both examples? Mike

    Leave a comment:


  • The Profit
    replied
    Hello sooty I'm wondering if I have set something up incorrectly. I've noticed that the "Time at Location" device will keep resetting back to 0 at random times. I have had my phone sitting on my night stand (at Home) when sleeping and when I wake up in the morning the "Time at Location" device will show that it's been 8 minutes at that location (Home).

    When I set up the Home and Work Known Location I used the full Lat/Lon from the Lat/Lon devices on my phone from the plugin. I have set the iCloud Device (iPhone) - Minimum Distance to Move: 0.5 mi and the Home Known Location Radius to 0.5 mi. I understand that my GPS position will float around a little but a half mile is a big difference. Is there something that you can suggest I change in settings that might help?

    Leave a comment:


  • usLEDsupply
    replied
    Originally posted by sooty View Post

    After reading the log you PM'd me, I think the issue is a badly formatted tracking url in the EGI app.

    There was a small error in the user guide relating to EGI tracking which I've now corrected.

    Assuming you're using the MyHS service, in the URL for Tracking enter the following:
    Code:
    https://connected2.homeseer.com/phl2api?dtype=ET&androidid=${androidId}&lat=${realLatitude}&lon=${realLongitude}&acc=${accuracy}&date=${localLocationDate}&phlid=656
    and see if it then works.

    Paul..
    That did the trick no errors and the location is updating again:-)

    Leave a comment:


  • will40
    replied
    Thanks slbuck. I was running an old version of PHL V2. Paul straightened me out. Thanks for the tip on the altitude, I see that now.

    Leave a comment:


  • slbuck
    replied
    Originally posted by will40 View Post
    I changed my PHL V1 backtiude parameters to meet new PHL V2 with new device REF, success code, URL, etc and have successful messages on my device. Unfortunately my devices are not updating and my HS3. log is rejecting the data. I double checked device ID. Am I missing something? Thanks

    Click image for larger version

Name:	PHL v2 BK log.JPG
Views:	18
Size:	29.4 KB
ID:	1281673
    I'm using Backitude and recently made the switch to PHL 2 and it's working great here.

    Make sure your server URL is set to "https://connected2.homeseer.com/phl2api?dtype=BK"

    I originally missed the updated API name which changed to phl2api and had a similar error that you did.

    The following are things I had to change on Backitude under the custom server settings:

    1) Server URL to https://connected2.homeseer.com/phl2api?dtype=BK

    2) Custom Field 1 - updated with new device id for PHL2 backitude user

    3) Clear the altitude field - Backitude was not sending correct data. Make sure you set an API provider in the PHL2 API configuration page for elevation. You can use the free ElevationAPI f you don't have one of the other supported providers.

    Leave a comment:


  • usLEDsupply
    replied
    first test no error so ill go for a drive and see if it works

    Leave a comment:


  • sooty
    replied
    Originally posted by usLEDsupply View Post
    i keep getting this error (since updating from .31) i don't think i changed anything else?
    Feb-03 1:47:33 AM PHLocation2 Error (phlapi) GET Error: Invalid accuracy value. Data rejected.
    Feb-03 1:47:33 AM PHLocation2 Error (ProcEgiTrackingData) Data rejected for DeviceId: 656. Invalid accuracy value: -1
    using
    EgiGeoZone
    PH 3.0.0.54
    HS3 .500
    Win 7 64bit
    After reading the log you PM'd me, I think the issue is a badly formatted tracking url in the EGI app.

    There was a small error in the user guide relating to EGI tracking which I've now corrected.

    Assuming you're using the MyHS service, in the URL for Tracking enter the following:
    Code:
    https://connected2.homeseer.com/phl2api?dtype=ET&androidid=${androidId}&lat=${realLatitude}&lon=${realLongitude}&acc=${accuracy}&date=${localLocationDate}&phlid=656
    and see if it then works.

    Paul..

    Leave a comment:


  • sooty
    replied
    Originally posted by racerfern View Post
    While you're making some changes, here's a typo... Orphans
    Click image for larger version

Name:	Screen Shot 02-03-19 at 07.29 AM.PNG
Views:	12
Size:	14.5 KB
ID:	1281897
    Thanks for pointing it out. This is fixed in versions >= 3.0.0.55.

    Paul..

    Leave a comment:


  • sooty
    replied
    Originally posted by usLEDsupply View Post
    i keep getting this error (since updating from .31) i don't think i changed anything else?
    Feb-03 1:47:33 AM PHLocation2 Error (phlapi) GET Error: Invalid accuracy value. Data rejected.
    Feb-03 1:47:33 AM PHLocation2 Error (ProcEgiTrackingData) Data rejected for DeviceId: 656. Invalid accuracy value: -1
    using
    EgiGeoZone
    PH 3.0.0.54
    HS3 .500
    Win 7 64bit
    The accuracy value is expected to be >=0. It would appear that EGI is:
    1. Not sending an accuracy value or
    2. The value is < 0 or
    3. The plug-in is not able to parse the value being sent.

    Can you:
    Set debug to file ON from the plug-in config page
    Send a test from the EGI app (glasses icon)
    Switch OFF debug to file.
    Email or PM me the log file.

    Paul..

    Leave a comment:


  • racerfern
    replied
    While you're making some changes, here's a typo... Orphans
    Click image for larger version

Name:	Screen Shot 02-03-19 at 07.29 AM.PNG
Views:	12
Size:	14.5 KB
ID:	1281897

    Leave a comment:


  • usLEDsupply
    replied
    i keep getting this error (since updating from .31) i don't think i changed anything else?
    Feb-03 1:47:33 AM PHLocation2 Error (phlapi) GET Error: Invalid accuracy value. Data rejected.
    Feb-03 1:47:33 AM PHLocation2 Error (ProcEgiTrackingData) Data rejected for DeviceId: 656. Invalid accuracy value: -1
    using
    EgiGeoZone
    PH 3.0.0.54
    HS3 .500
    Win 7 64bit

    Leave a comment:


  • will40
    replied
    Originally posted by sooty View Post

    Can you disable then re-enable the plug-in from the HS3 manage plug-ins page, then email or PM me all the log entries from the plug-in start-up. There will be 2 entries (Startup) Begins at.... and (Startup) Finished at.... to help identify the entries I need to see.

    Paul..
    PM Sent

    Leave a comment:


  • sooty
    replied
    Originally posted by racerfern View Post
    I use Android exclusively and have never set anything of iCloud. Why are the following lines in the startup routine?
    Feb-02 16:44:14 PHLocation2 (LoadConfigSettings) Using stored iCloud client ID: 68604395-C983-424C-8478-735065A58ECE
    Feb-02 16:44:14 PHLocation2 (LoadConfigSettings) iCloud retry time 5000 ms.
    Feb-02 16:44:14 PHLocation2 (LoadPiSettings) iCloud give up after 5 tries.
    Feb-02 16:44:14 PHLocation2 (LoadPiSettings) iCloud max retries set to 6
    These settings are present in all installations regardless if iCloud is used or not on the premise that it might be used.

    You're not the first to ask that question so I'll remove those entries from the start up logging.

    Paul..

    Leave a comment:


  • sooty
    replied
    Originally posted by will40 View Post
    I changed my PHL V1 backtiude parameters to meet new PHL V2 with new device REF, success code, URL, etc and have successful messages on my device. Unfortunately my devices are not updating and my HS3. log is rejecting the data. I double checked device ID. Am I missing something? Thanks

    Click image for larger version

Name:	PHL v2 BK log.JPG
Views:	18
Size:	29.4 KB
ID:	1281673
    Can you disable then re-enable the plug-in from the HS3 manage plug-ins page, then email or PM me all the log entries from the plug-in start-up. There will be 2 entries (Startup) Begins at.... and (Startup) Finished at.... to help identify the entries I need to see.

    Paul..

    Leave a comment:


  • racerfern
    replied
    I use Android exclusively and have never set anything of iCloud. Why are the following lines in the startup routine?
    Feb-02 16:44:14 PHLocation2 (LoadConfigSettings) Using stored iCloud client ID: 68604395-C983-424C-8478-735065A58ECE
    Feb-02 16:44:14 PHLocation2 (LoadConfigSettings) iCloud retry time 5000 ms.
    Feb-02 16:44:14 PHLocation2 (LoadPiSettings) iCloud give up after 5 tries.
    Feb-02 16:44:14 PHLocation2 (LoadPiSettings) iCloud max retries set to 6

    Leave a comment:

Working...
X