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
    Again, thanxs Paul, I'm now feeling empowered PHL2 wise which might be just a false sense of security!

    Leave a comment:


  • sooty
    replied
    Originally posted by MNB View Post
    Paul, thanxs for the explanation it does provide insight into the confusion…

    1) According to your overview "History" with device ID (96_history.html) is created during Map Viewer page, however we can also get a history if we use a event to build a dynamic Map with Map type of History.

    2) Where does the static device Id (96_current.png) map get created from?

    3) The iCloud device>PHLocation2 tab Dynamic Mapping Options is a dynamic map for current mapping (when location changes) which doesn't have history associated with it, whilst Static Mapping Option is a static map for current mapping (when location changes) and doesn't have history associated with it by nature of a png file. Other than file type both basically produce similar results (have I missed something?)
    Thanxs in advance not trying to be difficult only trying to make sure I understand, Mike
    1. If the path and file name are not overridden then all dynamic maps generated from an event, regardless if history or current will be named (dynamic_map_from_action.html). The same applies to static maps although the file name will be (static_map_from_action.png).

    2. That should be coming from the "Build a new map when location changes" option within static map settings on the PHL2 tab of the user with device ref 96.

    3. You summary is exactly right.
    Dynamic maps are more suited to viewing with a browser where you can pan and zoom the map etc and are designed to be used in an iFrame which may be embedded in another web page.
    Static maps are just that, a fixed "static" image that cannot be panned or zoomed. This was initially done in PHL V1 so users could display the map images in HSTouch.
    Wasn't going to put this in V2 but a few folks asked for it so I added it.

    Paul..

    Leave a comment:


  • MNB
    replied
    Paul, thanxs for the explanation it does provide insight into the confusion…

    1) According to your overview "History" with device ID (96_history.html) is created during Map Viewer page, however we can also get a history if we use a event to build a dynamic Map with Map type of History.

    2) Where does the static device Id (96_current.png) map get created from?

    3) The iCloud device>PHLocation2 tab Dynamic Mapping Options is a dynamic map for current mapping (when location changes) which doesn't have history associated with it, whilst Static Mapping Option is a static map for current mapping (when location changes) and doesn't have history associated with it by nature of a png file. Other than file type both basically produce similar results (have I missed something?)
    Thanxs in advance not trying to be difficult only trying to make sure I understand, Mike

    Leave a comment:


  • sooty
    replied
    Originally posted by MNB View Post
    Paul, Map(s) question; which tab is controlling the two maps below (I was assuming the Configuration>Mapping but I do not believe that's totally correct?
    • Dynamic Map (Built-in Viewer)
    • Auto Generate (All Users) Dynamic Map settings
    • Auto Generate (All Users) Static Image Settings
    1. (Device Id)_history.HTML
    2. (Device ID)_current.PNG
    3. alluserscurrent.HTML
    Confusing I know. I'm confused and I wrote it
    I'll try and change / rearrange some of the descriptions and tooltips to better describe what each setting does.

    The built in-dynamic map viewer creates HTML files whenever it's used. The file names are fixed and are really not that relevant to the end user because they are only used internally.

    Settings for the built in dynamic map viewer are on the Mapping tab of the plug-in config.
    The first section (Dynamic Map (General) Settings) applies to all dynamic maps regardless of how they are created / viewed.
    The (Dynamic Map (Built-In Viewer) Settings) apply only to the built-in viewer.

    Within each position type user, there is the option to automatically generate both static and / or dynamic "All Users" maps.
    Map generation is triggered whenever a user with that option switched ON changes location. It will then grab all other users with the option switched ON and generate a map.
    The settings for "All Users" map types are a little confusing because they are split between the Config>Mapping and each individual user.
    The general parameters for "All Users" maps like map size, type and file name override etc are done in Config>Mapping.
    Within each user's PHL2 tab the marker character and marker pin colour apply to both All Users and Single User maps. The rest of the settings are "Single User" only.

    So, if you don't override any file names the defaults below will be used: F=Fixed File Name O=Overridable File Name
    F (alluserscurrent.html) Created / updated when the "All Users" button is clicked on the Map Viewer page.
    F (deviceId_history.html) Created / updated when the "History" button is clicked on the Map Viewer page.
    O (all_users_current.html) Created / updated when an "All Users" dynamic map is automatically generated.
    O (deviceId_current.html) Created / updated when a "Single User" dynamic map is automatically generated.
    O (dynamic_map_from_action.html) Created / updated when a dynamic map is generated from an event action.
    O (all_users_current.png) Created / updated when an "All Users" static map is automatically generated.
    O (deviceId_current.png) Created / updated when a "Single User" static map is automatically generated.
    O (static_map_from_action.png) Created / updated when a static map is generated from an event action.

    Think that's it.

    Paul..

    Leave a comment:


  • slbuck
    replied
    Originally posted by MNB View Post
    Randy, slow question.. "Known Location for his home is 0 and "The Vortex" is 4." where does value get set or inferred for home and Vortex contains 0 vs 4? are there other devices that have value of 1-3 or 5> Mike

    Update: I believe that the slot number for Known places within PHL2 e.g. 0 for home and in the case for Steve 4 for vortex.

    Steve, out of curiously what makes up your vortex known place?
    I was actually guessing the value for the Vortex to be 4 since it was the 4th location I had added. 0 is always Home and then 1-99999999 are for user added locations. I now have 10 known locations and they are alphabetized so I've lost track of which value is assigned to each known location. I've reached out to Paul to see if he might include the value for each location under the known locations tab.

    The vortex known place is just a regular location (my in-laws actually) and so I handle entry/exit to this location separately from all other locations.

    Leave a comment:


  • slbuck
    replied
    Originally posted by MNB View Post
    Stephen, thanxs for sharing, I agree with you PHL2 has significantly improved the Location/Maping capabilities. I noticed that your using Group Conditions I thought I had read some where or was advised that Group conditions aren't reliable in how they execute has something changed with the recent HS3 upgrades.

    2)How does the "range" trigger work I see [0,0] and [4,4] thanxs in advance
    3)Where does "Any" when using the PHL2 command "User: Steve phone exits known location: Any." come from?
    I'm only checking the group conditions to make sure they are all true, I'm not doing any group actions. So far, it seems to be working ok. I need to test to make sure things are working when party mode is set or when occupancy status is Away.

    For the range triggers, as Randy pointed out, my original intent was to verify that I wasn't at Home nor the Vortex after exiting a known location. This actually didn't work since the Current Location value was updated to None (value of -1) and so was always not home (value of 0) or the vortex (value of 4). I updated my post above to show the new logic that I'm using and I'll test this out for a couple of days to see if it works.

    Leave a comment:


  • MNB
    replied
    Paul, Map(s) question; which tab is controlling the two maps below (I was assuming the Configuration>Mapping but I do not believe that's totally correct?
    • Dynamic Map (Built-in Viewer)
    • Auto Generate (All Users) Dynamic Map settings
    • Auto Generate (All Users) Static Image Settings
    1. (Device Id)_history.HTML
    2. (Device ID)_current.PNG
    3. alluserscurrent.HTML

    Leave a comment:


  • MNB
    replied
    Paul, thanxs for the clarification. So just that I'm clear in my understanding the other Known location(s) (not Home) are sequential numbering based on how they were inputted e.g. 2nd inputted Known Location =1 followed by the 3rd being =2 and ect?

    Update: Somehow I don't believe my statement is correct because the Known Locations are in alpha numeric sequence which would put device number is flux...

    Leave a comment:


  • sooty
    replied
    Originally posted by MNB View Post
    Randy, slow question.. "Known Location for his home is 0 and "The Vortex" is 4." where does value get set or inferred for home and Vortex contains 0 vs 4? are there other devices that have value of 1-3 or 5> Mike

    Update: I believe that the slot number for Known places within PHL2 e.g. 0 for home and in the case for Steve 4 for vortex.

    Steve, out of curiously what makes up your vortex known place?
    Don't read too much into the device value (slot number) used in the current location device as this may not always provide the correct info.

    As far as known locations are concerned, ID 0 is always assigned to the Home Location and ID's >0 are assigned to any additional known locations.

    WRT the current location device the device values are not always as they seem:
    If the user is not within any known location then the value is -1.
    If the user is ONLY within the Home Location and NOT also within any other known location then the value is 0.
    If the user is ONLY within ONE other known location (that is NOT the home location) then the value will be >0 where the number represents the ID of the known location.
    If the user is within MULTIPLE (i.e. overlapping known locations) locations then the value will be -2.

    In summary:
    It is fine to use the device value if you don't have overlapping known locations.

    Paul..

    Leave a comment:


  • bjwanvik
    replied
    Thank you!
    I should have seen that myself... After some struggling with my tasker string, I'm finally in with the Android (tasker) device as well - then everything should be ready to take advantage of this fantastic plug-in

    Leave a comment:


  • sooty
    replied
    Originally posted by bjwanvik View Post
    I just installed PHLocation 2, and got the iCloud up and running pretty fast.
    Tasker didn't work out so well for me
    I just copied the old tasker task from PHLocation (1) and modified the url, but I'm getting this error:
    (ProcPositionData) Invalid Interface Name for user [4918] of PHLocation2!

    Any idea what that could be? 4918 is the device for tasker device in PHLocation 2. I realized that if I change the string in tasker, for instance change from 4918 to 4917, that's reflected in the log - also tried to change to the user, and tried to rename device 4918 to different names without that helping.
    Apologies, the user guide is incorrect for Tasker configuration

    The "(ProcPositionData) Invalid Interface Name for user [4918] of PHLocation2!" message is coming from PHLocation V1 because device ref 4918 belongs to PHLocation V2.
    Change the URL in your Tasker post from /phlapi?dtype=CD to /phl2api?dtype=CD

    Paul..

    Leave a comment:


  • bjwanvik
    replied
    I just installed PHLocation 2, and got the iCloud up and running pretty fast.
    Tasker didn't work out so well for me
    I just copied the old tasker task from PHLocation (1) and modified the url, but I'm getting this error:
    (ProcPositionData) Invalid Interface Name for user [4918] of PHLocation2!

    Any idea what that could be? 4918 is the device for tasker device in PHLocation 2. I realized that if I change the string in tasker, for instance change from 4918 to 4917, that's reflected in the log - also tried to change to the user, and tried to rename device 4918 to different names without that helping.

    Leave a comment:


  • MNB
    replied
    Randy, slow question.. "Known Location for his home is 0 and "The Vortex" is 4." where does value get set or inferred for home and Vortex contains 0 vs 4? are there other devices that have value of 1-3 or 5> Mike

    Update: I believe that the slot number for Known places within PHL2 e.g. 0 for home and in the case for Steve 4 for vortex.

    Steve, out of curiously what makes up your vortex known place?

    Leave a comment:


  • MNB
    replied
    Thanxs Randy for taking the time to explain on both Group conditions and Easy trigger conditons. As I have mention before examples are great learning tools so if one doesn't quite grasp what's going on this forum always has subject matter experts.

    Well I guess I must of not kept up with the "Jones" and updated to the latest... Thanxs Mike

    Leave a comment:


  • rprade
    replied
    Originally posted by MNB View Post
    Stephen, thanxs for sharing, I agree with you PHL2 has significantly improved the Location/Maping capabilities. I noticed that your using Group Conditions I thought I had read some where or was advised that Group conditions aren't reliable in how they execute has something changed with the recent HS3 upgrades.

    2)How does the "range" trigger work I see [0,0] and [4,4] thanxs in advance
    3)Where does "Any" when using the PHL2 command "User: Steve phone exits known location: Any." come from?

    Group conditions work fine, There is some ambiguity on one of the options as explained here.

    Known Location for his home is 0 and "The Vortex" is 4. Those are Conditions not Triggers. A range of [0,0] means equal to 0 and a range of [4,4] is equal to 4. Together, the event will run only if he has been away from Home (0) or The Vortex (4) for at leas 10 seconds. As he wrote, he handles entry and exit of those two locations separately.

    "Any" was added to the latest beta - 3.0.0.60 yesterday.

    Leave a comment:

Working...
X