GeoFency No Longer Communicates with PHLocation2

[cmdrcrank]

iPhone 7 running latest iOS. PHLocation2 plug-in version 3.0.0.64. HomeSeer 3 Pro (latest version). GeoFency URL: https://connected2.homeseer.com/phl2api?dtype=GF

This worked great for a very long time, but recently stopped working. When I use the Test Entry button in GeoFency, it says "Failed - canceled"

[randy]

That means GeFency is not connecting with the HomeSeer web server. How are you connecting? Posting through a DDNS with port forwarding, MyHS or other?

[Bigstevep]

If you are connecting through MyHS on HS4 you need to go into GeoFency and change the Webhook to your new user name and password. Since I've done that it's been working for days including today.

[cmdrcrank]

Geofency stopped working again with HS4. When I check my Geofency app on my iPhone, it says connection successful, but there is no corresponding log entry in HS4. I am using MyHS.com to access the server with my HS4 credentials.

[trevor-austin]

Mine is working fine.

[cmdrcrank]

I tried everything and finally found HSBuddy. It works perfectly and is far easier to configure.

[MNB]

That means GeFency is not connecting with the HomeSeer web server. How are you connecting? Posting through a DDNS with port forwarding, MyHS or other?

randy, Not that I changed anything other than converting from HS3 to HS4 but it appears that something has changed re Geofency and/or PHLocation2

I'm currently using within the GeoFency app:

URL Settings: Entered for both Entry and Exit as: https://connected2.homeseer.com/phl2api?dtype=GF which implies MyHS posting
Authentication: MyHS credentials
HTTP Method: POST

Have I captured them properly to work with HS4?

because when I test either Entry or Exit, I get a message "Successful timeout from host, source IP 1.1.1.1" but I never see anything within the HS4 Log. do you per chance have any other suggestions?

Update: I tried the URL command within my browser and got prompted for my MyHS credentials which it took, but quickly received a similar message "timeout from host, source IP 1.1.1.1" I guess the question is whom on the HS4 side is responding?

[randy]

The posting through MyHS doesn’t need to change from HS3 to HS4, but you do need to make sure your HS4 instance is registered with MyHS.HomeSeer.com. Mine is still reliable with HS4.

[MNB]

Firstly thanxs for the comeback, trust your doing better? I don't fully understand your comment "make sure your HS4 instance is registered with MyHS.HomeSeer.com"? I assumed that when I login in to MyHS that I'm logging into HS4 or is there something more or a way to verify?

Update: I tried to log on both locally and via the MyHS route and simply use the "Ip address/phl2api?dtype=GF" within the browser and got the following responses within the browser and HS4 log “Error! Fence data check type [F] failed.” which suggests that it's getting to HS4 but did not have proper GF data. So is there something else outstanding, I see that Geo Fency app got update just recently (setting changes?)

[randy]

If you can access your system remotely through MyHS then your system is properly linked.

There are two requirements

1. post to: https://connected2.homeseer.com/phl2api?dtype=GF
2. Make sure your credentials (username/password) are correct as they are set on MyHS

You can also do it locally using <HomeSeer IP>/phl2api?dtype=GF. You still need to use valid credentials in GeoFency account settings. For local it can be any HomeSeer user with admin rights, for MyHS it has to be the username and password for MyHS

[MNB]

You can also do it locally using <HomeSeer IP>/phl2api?dtype=GF. You still need to use valid credentials in GeoFency account settings. For local it can be any HomeSeer user with admin rights, for MyHS it has to be the username and password for MyHS

Randy, I did the local route <HomeSeer IPort>/phl2api?dtype=GF and got the following responses within the browser and HS4 Log, can you confirm if you get the same?

Browser response: Error! Fence data check type [F] failed.
HS4 Log:

11/11/2021 7:25:54 PM Legacy-Plugin/Script PHLocation2 Error (phlapi) GET Error: Error! Fence data check type [F] failed.
11/11/2021 7:25:54 PM Legacy-Plugin/Script PHLocation2 Error (ProcHttpFenceData) DataCheck Error. Did: Fid: Fname: Ftyp:F Fdir:-1 Fpv:17

I also confirm the same result if I post via MyHS <https://connected2.homeseer.com/phl2api?dtype=GF> route. I guess the question is should I be getting something different?

[randy]

If you enter that address in a browser, that is the correct response because you are not sending the GeoFency payload. You will also get the same response with your browser through MyHS, but it should prompt you for a username and password.

If those are true, then you really need to look at the username and password for the webhook in GeoFency. Also note that the url and credentials need to be set for every fence and iBeacon you set up on every client running GeoFency. If you change the password for MyHS, you have to change it for every fence and iBeacon on every client

[MNB]

So I decided to change the URL on Geofency app for the "Entry" to <https://<local ip & Port>/phl2api?dtype=GF> and got the same result as before, but I then changed "from https to http" and wala my local resulted in the Succesful ["CTime"'"11/11/2021..."] message along with a HS4 log entry "11/11/2021 8:40:15 PM Legacy-Plugin/Script PHLocation2 Warning (ProcessFenceUpdate) Fence data received from unknown device ID [XXXXXXX-7F93-4AF1-A82C-XXXXXXXX]!" small miracle!

So I tried to do the same with the MyHS side <http://connected2.homeseer.com/phl2api?dtype=GF> but I did not get the same (note my cell strength was only 1 bar) but could that be the issue/difference? graphing at straws..

[randy]

That would indicate that your GeoFency device ID has changed on your phone. You just need to copy the ID from the HomeSeer log and paste it into the GeoFency root device’s device ID. This I’d changes when you change phones or reinstall GeoFency in the phone. Yes, the local will not be https. This ID problem will affect local and MyHS

[MNB]

Well, if all else fails you, then remove the offending app and re install "GeoFency"! when I did that, I initially couldn't get it reinstall so something was not well with my previous installed GeoFency app. So once I got reinstalled, I had to recreate all of my GeoFency Devices (2x) and iBeacons (4x) so not a big deal (just a little relearning pains) but I now have a working GeoFency/PHlocation2 solution.

So as always, many thanxs randy for your expertise and suggestions. The one recommendation I noted during this process is that for those of you who have low Phone signal strength you might want to initially use your local Wi-Fi (<http://<HomeSeer IP>:<port>/phl2api?dtype=GF> as the Geofency Entry/Exit URL to establish your GeoFency devices and verify that they work. Once you're done with your setup/testing, then change your URL back to the <https://connected2.homeseer.com/phl2api?dtype=GF> and "Bobs you Uncle!".