PHLocation V2 Discussion

[MNB]

Paul, tried to download your latest v 3.0.0.47 Jan 21st 2019 but all I get is a white screen.... Tried it on Edge and FoxPro browsers with the same resolve, Mike

[sparkman]

Paul, tried to download your latest v 3.0.0.47 Jan 21st 2019 but all I get is a white screen.... Tried it on Edge and FoxPro browsers with the same resolve, Mike

Worked fine for me in Chrome.

EDIT. It did earlier, but not anymore.

[randy]

Paul may have pulled it. There is a problem with the executable not shutting doen properly which prevents installation of new versions. He will likely post another update shortly.

[randy]

Worked fine for me in Chrome.

Al;

I installed .45 last night and .46 this morning and both worked fine. When I tried to update to .47 from the full package this morning, I found the .exe was not shutting down properly. This was probably introduced with .46. .47 will likely install properly, but it may be difficult to apply future updates without shutting down HomeSeer.

[MNB]

Thanxs Randy, I even tried reboot my PC to ensure that it wasn't on my end since Al indicated that he was able to download it. Mike

[The Profit]

Al;

I installed .45 last night and .46 this morning and both worked fine. When I tried to update to .47 from the full package this morning, I found the .exe was not shutting down properly. This was probably introduced with .46. .47 will likely install properly, but it may be difficult to apply future updates without shutting down HomeSeer.

Guess I was too quick to update....I’ve installed .47 so if there is anyway to get instructions on the best way to install future versions?


Sent from my iPad using Tapatalk

[sooty]

There is an issue with .47 so I've pulled the download until I resolve it.

Actually the issue was introduced in a previous version (not sure exactly which one yet) but I'm pretty sure it was after .43 so hopefully not many have it.

The issue is that the plug-in does not shut down properly so won't allow installation of a new version because HS3 still thinks it's still running.

I've identified where the issue is and will have a fix soon.

Paul..

[The Profit]

There is an issue with .47 so I've pulled the download until I resolve it.

Actually the issue was introduced in a previous version (not sure exactly which one yet) but I'm pretty sure it was after .43 so hopefully not many have it.

The issue is that the plug-in does not shut down properly so won't allow installation of a new version because HS3 still thinks it's still running.

I've identified where the issue is and will have a fix soon.

Paul..

What would be a good update process for those of us who have already updated to .47?

Disable plugin, install new version, shutdown HS3 then enable the new version?


Sent from my iPad using Tapatalk

[randy]

Guess I was too quick to update....I’ve installed .47 so if there is anyway to get instructions on the best way to install future versions?


Sent from my iPad using Tapatalk

If you have a problem when the next update comes out:

• Disable PHL and shutdown HomeSeer
• Delete HSPI_PHLocation2.exe from the HS3 root directory
• Restart HomeSeer
• Drop updater_override.txt into the HS root directory
• Drop the .zip file into Updates3/Zips
• Goto Manage Plug-ins and install the local update
• enable PHLocation2
• Enjoy!

Remember that HomeSeer automatically deletes all files in Updates3/Zips at startup and it deletes the updater_override.txt file, so they must be copied when HS is running. If .47 is in and running, don't do anything unless you have a problem with a future update.

[MNB]

As I stated in the two quotes you included in the post, it is up to you. I think that 100 meters (328 feet) is the tightest a fence can be to be reliable. I set mine to .1 mile (528 feet) and it never false triggers, if you have false triggers at .1 try .2. It is just a matter of balance. I cannot imagine a situation where a fence of even 1000 feet would cause a problem unless you are walking. Chances are if you are within 1000 feet you are home and if greater than 1000 you are not. At neighborhood speeds you travel at 37 feet per second, so 1000 feet is only 30 seconds away.

With regard to maximum accuracy I stated that I use 100 meters. I came up with that number by looking at history. Any real readings from my phone are within that number for accuracy. When my phone looses GPS in the basement, it goes to WiFi for position, but Apple reports the accuracy as 65 meters. Looking at the actual positions reported that number seems to be correct. It is a matter of tuning your system to balance speed, accuracy and limiting bad reports.

Randy, its been a few days since our discussion above and I have say I'm now working properly (no false alarms with moving Inside > Outside > Inside my GeoFency inner perimeters when the phone hasn't been moved) after fixing my "iCloud Device" iPhone > to reflect; "General options" > with my "Minimum Distance to Move" = 0.1 mile and my "Maximum Accuracy" = 100 Meters.

I readjusted my GeoFency perimeters to a inner perimeter = 100 meters (328 feet) and a outer perimeter = 1700 meters (~1.02 mi) which works well with my various events (with help from your good self) so I feel like I'm finally up and running (PHL2 wise) many thanxs in this continued learning experience(s), Mike

[sooty]

If you've already installed .47, then I don't think it will cause anything catrosophic to happen. Basically when the plug-in is shut down it doesn't make a clean break from HS3 so HS3 still has a hold on the plug-in's exe file therefore it can't be overwritten whilst HS3 is running.

I need to confirm for sure tomorrow (its 11pm here in the UK) but initial testing seems to suggest that the issue is caused by the way the plug-in is storing the data from the previous location update. This was added to fix the issue with triggers on overlapping known locations.

Currently this is stored as a custom object in the PED (PlugExtraData) of the user root device and whilst the reading and writing of data to this PED object is working fine, for some reason if any plug-in device has such an object in it's PED collection then HS3 won't let go of the plug-in's exe.

I'll get onto it in the morning.

Paul..

[mjolsen]

Randy, its been a few days since our discussion above and I have say I'm now working properly (no false alarms with moving Inside > Outside > Inside my GeoFency inner perimeters when the phone hasn't been moved) after fixing my "iCloud Device" iPhone > to reflect; "General options" > with my "Minimum Distance to Move" = 0.1 mile and my "Maximum Accuracy" = 100 Meters.

I readjusted my GeoFency perimeters to a inner perimeter = 100 meters (328 feet) and a outer perimeter = 1700 meters (~1.02 mi) which works well with my various events (with help from your good self) so I feel like I'm finally up and running (PHL2 wise) many thanxs in this continued learning experience(s), Mike

Hey Mike--
I'm curious how you are using your inner and outer with Geofency.. mind sharing an event and geofency snapshot?

[sooty]

I've uploaded version 3.0.0.48 and reinstated the download link in the release notes page.

See the notes (in red) on the release notes page if you have already installed versions 3.0.0.45 to 3.0.0.47.

Paul..

[zimmer62]

There is a typo in the FMIP Alert Action text.. I currently says "Play altert sound:" extra T in there.

[sooty]

There is a typo in the FMIP Alert Action text.. I currently says "Play altert sound:" extra T in there.

Fixed in .49 or later.

Paul..