Announcement

Collapse
No announcement yet.

EgiGeoZone GR02 error - with test

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    EgiGeoZone GR02 error - with test

    Setting up for the first time... always get error GR02 (timeout establishing a session with PHLocation).

    HS3 on Win10
    Win 10 FW set to allow HS3 both Private & Public, ANY port, both TCP & UDP (2 separate rules in control panel)
    Internet router FW TCP & UDP open with internal & external set to same port #s - same as in PHLocation, of course.

    I have 15 other port forwarding rules in my FW, those all work so I don't think my FW is blocking.

    thx for the help!

    #2
    From a web browser on another machine within the same LAN as your HS3 machine, try the following url

    Code:
    http://yourhs3server:phlocationport/phlegigeozone
    Are you prompted for credentials or does the page timeout?

    Paul..

    Comment


      #3
      Originally posted by sooty View Post
      From a web browser on another machine within the same LAN as your HS3 machine, try the following url

      Code:
      http://yourhs3server:phlocationport/phlegigeozone
      Are you prompted for credentials or does the page timeout?

      Paul..
      times out.

      PHlocation startup from HS3 log..
      May-29 1:29:22 PM PHLocation (Startup) Finished at 01:29:22.469
      May-29 1:29:22 PM PHLocation (StartDQThreads) Fence DQ thread started OK.
      May-29 1:29:22 PM PHLocation (StartDQThreads) Pos DQ thread started OK.
      May-29 1:29:22 PM PHLocation (CreateDeviceLists) Finished.
      May-29 1:29:22 PM PHLocation (CreateDeviceLists) There are no active custom user devices. Setting monitoring to OFF.
      May-29 1:29:22 PM PHLocation (CreateDeviceLists) No AppLv Timer devices found. Don't start AppLv Timer.
      May-29 1:29:22 PM PHLocation (CreateDeviceLists) Loc Timer type devices found. Start LocTimer.
      May-29 1:29:22 PM PHLocation (CreateDeviceLists) No FM User type devices added to poll list. Don't do polling.
      May-29 1:29:22 PM PHLocation (http) Server thread started OK on port 6001
      May-29 1:29:22 PM PHLocation (CreateDeviceLists) Total PI devices found = 17
      May-29 1:29:22 PM PHLocation (CreateDeviceLists) Other type device PHLCSU[225]BK added to PI main dev list.
      May-29 1:29:22 PM PHLocation (CreateDeviceLists) Other type device PHLCFN[224]EG added to PI main dev list.
      May-29 1:29:22 PM PHLocation (CreateDeviceLists) Active GF/EG User device PHLCUS[223]EG with ID: [223] added to GF/EG list.
      May-29 1:29:22 PM PHLocation (CreateDeviceLists) Active User type device PHLCUS[223]EG added to usertypes list.
      May-29 1:29:22 PM PHLocation (CreateDeviceLists) Active User type device PHLCUS[223]EG added to users list.
      May-29 1:29:22 PM PHLocation (CreateDeviceLists) User type device PHLCUS[223]EG added to PI main dev list.
      May-29 1:29:22 PM PHLocation (CreateDeviceLists) Found plug-in User type device PHLCUS[223]EG
      May-29 1:29:22 PM PHLocation (CreateDeviceLists) Other type device PHLCCS[222]BK added to PI main dev list.
      May-29 1:29:22 PM PHLocation (CreateDeviceLists) Other type device PHLCAL[221]BK added to PI main dev list.
      May-29 1:29:22 PM PHLocation (CreateDeviceLists) Other type device PHLCNK[220]BK added to PI main dev list.
      May-29 1:29:22 PM PHLocation (CreateDeviceLists) Other type device PHLCSP[219]BK added to PI main dev list.
      May-29 1:29:22 PM PHLocation (CreateDeviceLists) Other type device PHLCAC[218]BK added to PI main dev list.
      May-29 1:29:22 PM PHLocation (CreateDeviceLists) Loc Timer type device PHLCTM[217]BK added to Timer list.
      May-29 1:29:22 PM PHLocation (CreateDeviceLists) Loc Timer type device PHLCTM[217]BK added to PI main dev list.
      May-29 1:29:22 PM PHLocation (CreateDeviceLists) Other type device PHLCLO[216]BK added to PI main dev list.
      May-29 1:29:22 PM PHLocation (CreateDeviceLists) Other type device PHLCLA[215]BK added to PI main dev list.
      May-29 1:29:22 PM PHLocation (CreateDeviceLists) Other type device PHLCZC[214]BK added to PI main dev list.
      May-29 1:29:22 PM PHLocation (CreateDeviceLists) Other type device PHLCCN[213]BK added to PI main dev list.
      May-29 1:29:22 PM PHLocation (CreateDeviceLists) Other type device PHLCTN[212]BK added to PI main dev list.
      May-29 1:29:22 PM PHLocation (CreateDeviceLists) Other type device PHLCSU[211]BK added to PI main dev list.
      May-29 1:29:22 PM PHLocation (CreateDeviceLists) Other type device PHLCSA[210]BK added to PI main dev list.
      May-29 1:29:22 PM PHLocation (CreateDeviceLists) Active User type device PHLCUS[209]BK added to usertypes list.
      May-29 1:29:22 PM PHLocation (CreateDeviceLists) Active User type device PHLCUS[209]BK added to users list.
      May-29 1:29:22 PM PHLocation (CreateDeviceLists) User type device PHLCUS[209]BK added to PI main dev list.
      May-29 1:29:22 PM PHLocation (CreateDeviceLists) Found plug-in User type device PHLCUS[209]BK
      May-29 1:29:22 PM PHLocation (CreateDeviceLists) Started.
      May-29 1:29:22 PM PHLocation (Startup) Plug-In is licensed.
      May-29 1:29:22 PM PHLocation (Startup) License state returned 0
      May-29 1:29:22 PM PHLocation GetLicenseState Called
      May-29 1:29:22 PM PHLocation (Startup) Database structure update not required.
      May-29 1:29:22 PM PHLocation (Startup) Database version is: 9
      May-29 1:29:22 PM PHLocation (Startup) Plug-in version is: 3.0.1.90
      May-29 1:29:22 PM PHLocation (LoadPiSettings) UTC offset secs: -21600
      May-29 1:29:22 PM PHLocation (LoadPiSettings) Using stored iCloud client ID: EC1A51D0-F621-4B00-BEEF-FE69A15C2ABD
      May-29 1:29:22 PM PHLocation (LoadPiSettings) iCloud retry time 5000 ms.
      May-29 1:29:22 PM PHLocation (LoadPiSettings) iCloud give up after 5 tries.
      May-29 1:29:22 PM PHLocation (LoadPiSettings) iCloud max retries set to 6
      May-29 1:29:22 PM PHLocation (LoadPiSettings) Logging of http requests to file is ON.
      May-29 1:29:22 PM PHLocation (LoadPiSettings) BinPath = C:\Program Files (x86)\HomeSeer HS3\Data\PHLocation\
      May-29 1:29:22 PM PHLocation (LoadPiSettings) DataPath = C:\Program Files (x86)\HomeSeer HS3\Data\PHLocation\PHLocation.phd
      May-29 1:29:22 PM PHLocation (LoadPiSettings) MapPath = html\PHLocation\Maps\
      May-29 1:29:22 PM PHLocation (LoadPiSettings) ImagePath = images\PHLocation\
      May-29 1:29:22 PM PHLocation (LoadPiSettings) LogPath = html\PHLocation\Logs\
      May-29 1:29:22 PM PHLocation (LoadPiSettings) HSAppPath = C:\Program Files (x86)\HomeSeer HS3
      May-29 1:29:22 PM PHLocation (Startup) System decimal separator used is [.]
      May-29 1:29:22 PM PHLocation (Startup) Detected OS is Windows version 6.2.9200.0
      May-29 1:29:22 PM PHLocation (Startup) Begins at 01:29:22.035
      May-29 1:29:22 PM Plug-In Finished initializing plug-in PHLocation
      Last edited by Ltek; May 29, 2017, 02:47 PM.

      Comment


        #4
        Originally posted by Ltek View Post
        Win 10 FW set to allow HS3 both Private & Public, ANY port, both TCP & UDP
        Need a rule to to allow to HSPI_PHLocation.exe, not just HS3.exe.

        Comment


          #5
          You actually need to create a Windows Firewall rule for the port that the plug-in is listening on.

          To confirm that it is a firewall issue, you can try temporarily disabling the Windows Firewall and see if that url then works OK.

          Paul..

          Comment


            #6
            I figured out the Firewall

            ONLY thing that works...
            Firewall Rule that opens the Port you are using, with under Programs = ALL programs that meet the criteria

            DOES NOT WORK...
            FW rule for HSPI_PHLocation.exe - no matter if ALL or Specific port.

            ... this REALLY needs documentation - the Wiki does not have any of the info I've had issues with
            Last edited by Ltek; May 29, 2017, 04:18 PM.

            Comment


              #7
              Originally posted by Ltek View Post
              I figured out the Firewall

              ONLY thing that works...
              Firewall Rule that opens the Port you are using, with under Programs = ALL programs that meet the criteria

              DOES NOT WORK...
              FW rule for HSPI_PHLocation.exe - no matter if ALL or Specific port.

              ... this REALLY needs documentation - the Wiki does not have any of the info I've had issues with
              Although not fully documented step by step, there is some basic info here:

              http issues

              and

              obtaining the device ID

              Paul..

              Comment


                #8
                Originally posted by sooty View Post
                Although not fully documented step by step, there is some basic info here:

                http issues

                and

                obtaining the device ID

                Paul..
                I Highly recommend putting in the Firewall info I have above.

                I made thousands of Firewall rules over the years ... PHlocation didnt work with FW like other EXEs typically do.

                The only rule that worked opens that port for ALL apps... that is not normally needed. Its not needed with HS3 or any other app I use - the norm is that you specific the EXE, then allow all ports or specify a port.

                thx for the help

                Comment


                  #9
                  Originally posted by Ltek View Post
                  I Highly recommend putting in the Firewall info I have above.

                  I made thousands of Firewall rules over the years ... PHlocation didnt work with FW like other EXEs typically do.

                  The only rule that worked opens that port for ALL apps... that is not normally needed. Its not needed with HS3 or any other app I use - the norm is that you specific the EXE, then allow all ports or specify a port.

                  thx for the help
                  The reason that the firewall needs to be port as opposed to exe based is that the plug-in uses httplistener and not tcplistener. Changing this has been on my todo list for quite a while but for some reason I haven't gotten round to it.

                  The next release will be able to use HS3's built in web server to receive the data so will work via MyHS with HTTPS, removing the need for open ports.

                  I will also make the change so that it becomes exe based for those that don't want to go down the MyHS route.

                  Paul..

                  Comment


                    #10
                    Originally posted by sooty View Post
                    The reason that the firewall needs to be port as opposed to exe based is that the plug-in uses httplistener and not tcplistener. Changing this has been on my todo list for quite a while but for some reason I haven't gotten round to it.

                    The next release will be able to use HS3's built in web server to receive the data so will work via MyHS with HTTPS, removing the need for open ports.

                    I will also make the change so that it becomes exe based for those that don't want to go down the MyHS route.

                    Paul..
                    excellent news!

                    Comment


                      #11
                      Originally posted by sooty View Post
                      ... I will also make the change so that it becomes exe based for those that don't want to go down the MyHS route.

                      Paul..
                      Please do (save us from MyHS). The last thing I want is 'another' middle man that, from my opinion and usage, brings no solid added value.

                      Comment


                        #12
                        Originally posted by sooty View Post
                        The reason that the firewall needs to be port as opposed to exe based is that the plug-in uses httplistener and not tcplistener. Changing this has been on my todo list for quite a while but for some reason I haven't gotten round to it.

                        The next release will be able to use HS3's built in web server to receive the data so will work via MyHS with HTTPS, removing the need for open ports.

                        I will also make the change so that it becomes exe based for those that don't want to go down the MyHS route.

                        Paul..
                        @Sooty
                        Just checking if this was done?

                        So can we now use the same port for PHlocation (under PHlocation settings) as we do for HS3's web?

                        thx

                        Comment

                        Working...
                        X