Download the plug-in and user guide here
NOTE:
There was an issue in versions 3.0.0.57 and 3.0.0.58 where on each start the plug-in could create an additional message panel HS3 device.
If you have installed one of these versions then install version 3.0.0.59 or later then use the HS3 device management page and search for all instances of Device Type "Message Panel" then delete all but one of the devices and re-start the plug-in.
v 3.0.0.64 Nov 12th 2019
Fixed - removed registration requirements, until a new registration method is established
v 3.0.0.63 Feb 18th 2019
Fixed - New installations of any version between 3.0.0.57 and 3.0.0.60 would throw a database SQL error when trying to add a known location.
v 3.0.0.60 Feb 12th 2019
Added - Any location can be specified in Enter/Exit location trigger.
Changed - Message panel will now show a single message containing all transitioned known locations for a single update.
v 3.0.0.59 Feb 11th 2019
Fixed - Plug-in would create multiple message panel devices under some circumstances.
v 3.0.0.58 Feb 10th 2019
Fixed - Plug-in could fail to start on first run for systems where decimal separator is not dot.
v 3.0.0.57 Feb 10th 2019
Added - Message Panel device.
v 3.0.0.56 Feb 6th 2019
Fixed - Polling of service accounts freezing after first poll on some systems.
Fixed - Dynamic history maps would fail to display if a known location name contained an apostrophe and was included on the map.
v 3.0.0.55 Feb 4th 2019
Fixed - Further fixes to API settings on config page.
Fixed - Driving distance / time lookups failing on systems with "," as decimal separator.
Fixed - Various typo's and other small bug fixes.
v 3.0.0.54 Feb 2nd 2019
Fixed - API preferences on plug-in config page not saving correctly.
v 3.0.0.53 Feb 1st 2019
Fixed - Custom path & file name not working for static maps.
v 3.0.0.52 Feb 1st 2019
Added - Static maps functionality similar to how it was in PHLocation V1. Works with Google and Mapquest.
Fixed - Backitude speed value incorrectly reported.
Fixed - A new Known Location could be saved more than once resulting in duplicate records.
Fixed - Known Locations with an apostrophe in the name were not saved.
v 3.0.0.49 Jan 27th 2019
Change - Typo on FMIP alert message event action.
Change - Functions that use decimal values changed to prevent issues where system decimal separator is not dot.
Change - Beacon statuses changed to In Range and Not In Range.
Change - Added user guide link to plug-in menu.
Other minor bug fixes.
v 3.0.0.48 Jan 22nd 2019
Fixed - If elevation data was not included in a GET/POST and the user had set an elevation provider then it wasn't being looked up.
Fixed - Plug-in event actions were not kept intact for copied events.
Added - Custom position data now accepts device state and charge state parameters.
Fixed - Course child device value / graphic pair range was set 0-180 instead of 0-360
Fixed - Service account polling could be disabled under certain circumstances.
Fixed - Entry / Exit triggers wouldn't fire if there were multiple overlapping known locations and the user was within more than 1 location.
Added - New known locations can be added via phl2api.
Fixed - Home location direction device was not showing correct status.
Fixed - Issue causing the plug-in not to fully shut down (introduced in 3.0.0.47)
Other minor bug fixes.
NOTE:
There is an issue in versions .45, .46 and .47 that prevents the plug-in from fully shutting down. This will prevent a new version being installed as it can't overwrite the plug-in's exe file.
If you are installing .48 or later over one of these versions then you will need to:
1. Disable the plug-in from the HS3 manage plug-ins page.
2. Stop and re-start HS3 with the plug-in disabled.
3. Install new plug-in version through the HS3 installer.
4. Enable plug-in in the HS3 manage plug-ins page.
If the plug-in still fails to install, then it will be necessary to stop HS3 and manually delete the file \HS3\HSPI_PHLocation2.exe then re-start HS3 and run the install again.
v 3.0.0.43 Jan 17th 2019
Added - Plug-In action to send Find My iPhone Alert messages.
Added - Child device for position type users to show Approaching or Leaving home location.
v 3.0.0.42 Jan 15th 2019
Added - New user type "Monitored Position". External HS3 devices can be specified as the source for lat, lon and accuracy of a position type user.
Added - Extra debug logging added to procedure that writes fence data to db to enable better error tracking.
v 3.0.0.41 Jan 13th 2019
Fixed - Copied events containing a plug-in trigger could not be modified without totally rebuilding the event trigger.
Fixed - Other minor bug fixes.
v 3.0.0.40 Jan 12th 2019
Fixed - FollowMee devices were not being updated.
Fixed - Setting a polling interval > 2h on service accounts wasn't working.
NOTE:
There was an issue in versions 3.0.0.57 and 3.0.0.58 where on each start the plug-in could create an additional message panel HS3 device.
If you have installed one of these versions then install version 3.0.0.59 or later then use the HS3 device management page and search for all instances of Device Type "Message Panel" then delete all but one of the devices and re-start the plug-in.
v 3.0.0.64 Nov 12th 2019
Fixed - removed registration requirements, until a new registration method is established
v 3.0.0.63 Feb 18th 2019
Fixed - New installations of any version between 3.0.0.57 and 3.0.0.60 would throw a database SQL error when trying to add a known location.
v 3.0.0.60 Feb 12th 2019
Added - Any location can be specified in Enter/Exit location trigger.
Changed - Message panel will now show a single message containing all transitioned known locations for a single update.
v 3.0.0.59 Feb 11th 2019
Fixed - Plug-in would create multiple message panel devices under some circumstances.
v 3.0.0.58 Feb 10th 2019
Fixed - Plug-in could fail to start on first run for systems where decimal separator is not dot.
v 3.0.0.57 Feb 10th 2019
Added - Message Panel device.
v 3.0.0.56 Feb 6th 2019
Fixed - Polling of service accounts freezing after first poll on some systems.
Fixed - Dynamic history maps would fail to display if a known location name contained an apostrophe and was included on the map.
v 3.0.0.55 Feb 4th 2019
Fixed - Further fixes to API settings on config page.
Fixed - Driving distance / time lookups failing on systems with "," as decimal separator.
Fixed - Various typo's and other small bug fixes.
v 3.0.0.54 Feb 2nd 2019
Fixed - API preferences on plug-in config page not saving correctly.
v 3.0.0.53 Feb 1st 2019
Fixed - Custom path & file name not working for static maps.
v 3.0.0.52 Feb 1st 2019
Added - Static maps functionality similar to how it was in PHLocation V1. Works with Google and Mapquest.
Fixed - Backitude speed value incorrectly reported.
Fixed - A new Known Location could be saved more than once resulting in duplicate records.
Fixed - Known Locations with an apostrophe in the name were not saved.
v 3.0.0.49 Jan 27th 2019
Change - Typo on FMIP alert message event action.
Change - Functions that use decimal values changed to prevent issues where system decimal separator is not dot.
Change - Beacon statuses changed to In Range and Not In Range.
Change - Added user guide link to plug-in menu.
Other minor bug fixes.
v 3.0.0.48 Jan 22nd 2019
Fixed - If elevation data was not included in a GET/POST and the user had set an elevation provider then it wasn't being looked up.
Fixed - Plug-in event actions were not kept intact for copied events.
Added - Custom position data now accepts device state and charge state parameters.
Fixed - Course child device value / graphic pair range was set 0-180 instead of 0-360
Fixed - Service account polling could be disabled under certain circumstances.
Fixed - Entry / Exit triggers wouldn't fire if there were multiple overlapping known locations and the user was within more than 1 location.
Added - New known locations can be added via phl2api.
Fixed - Home location direction device was not showing correct status.
Fixed - Issue causing the plug-in not to fully shut down (introduced in 3.0.0.47)
Other minor bug fixes.
NOTE:
There is an issue in versions .45, .46 and .47 that prevents the plug-in from fully shutting down. This will prevent a new version being installed as it can't overwrite the plug-in's exe file.
If you are installing .48 or later over one of these versions then you will need to:
1. Disable the plug-in from the HS3 manage plug-ins page.
2. Stop and re-start HS3 with the plug-in disabled.
3. Install new plug-in version through the HS3 installer.
4. Enable plug-in in the HS3 manage plug-ins page.
If the plug-in still fails to install, then it will be necessary to stop HS3 and manually delete the file \HS3\HSPI_PHLocation2.exe then re-start HS3 and run the install again.
v 3.0.0.43 Jan 17th 2019
Added - Plug-In action to send Find My iPhone Alert messages.
Added - Child device for position type users to show Approaching or Leaving home location.
v 3.0.0.42 Jan 15th 2019
Added - New user type "Monitored Position". External HS3 devices can be specified as the source for lat, lon and accuracy of a position type user.
Added - Extra debug logging added to procedure that writes fence data to db to enable better error tracking.
v 3.0.0.41 Jan 13th 2019
Fixed - Copied events containing a plug-in trigger could not be modified without totally rebuilding the event trigger.
Fixed - Other minor bug fixes.
v 3.0.0.40 Jan 12th 2019
Fixed - FollowMee devices were not being updated.
Fixed - Setting a polling interval > 2h on service accounts wasn't working.