Announcement

Collapse
No announcement yet.

HS Connection: Not Set

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #16
    Here are my log files. Couple of notes:

    1. When clearing the settings in sage, it caused my extender to crash. When it restarted, the settings were cleared (this is in this log).

    2. Since I cleared the settings, I only get as far as the not set issue which is where I stopped. I did not manually edit the properties files to get to the HS login. So I suspect that the login issue will still be there but I thought you would want to fix the not set issue first or maybe they are related.

    Thanks
    Attached Files

    Comment


      #17
      Heatvent,

      I believe I may have found the problem. Before InControl sends an acknowledgement back to Sage, it does a Ping to make sure it is available. The ping appears to fail.

      Please confirm your Sage Server's IP address is 192.168.0.100. If so, from your HomeSeer server, can you start up a Command Prompt and enter "Ping 192.168.0.100".

      If you do not get a reply, then that is the issue. You can look through your firewall options on the Sage server to see if you can "Allow ICMP echo". In any case I will add a feature to the next version to Not Ping.

      If that is not the issue, let me know and I will keep looking through the logs.


      Thanks!
      Michael



      Originally posted by heatvent View Post
      Here are my log files. Couple of notes:

      1. When clearing the settings in sage, it caused my extender to crash. When it restarted, the settings were cleared (this is in this log).

      2. Since I cleared the settings, I only get as far as the not set issue which is where I stopped. I did not manually edit the properties files to get to the HS login. So I suspect that the login issue will still be there but I thought you would want to fix the not set issue first or maybe they are related.

      Thanks

      Comment


        #18
        192.168.0.100 is the address sage server. I did the ping and got a reply.

        Comment


          #19
          Heatvent,

          Sorry we have still not been able to get your issue resolved. From the log file, it is failing at the ping, so not sure where the issue. Let's try this:

          - Download the InControl update from the HomeSeer Updater (version 1.4.3)
          - Go to the InControl settings (http://<HomeSeer Server>/InControl_Sage_config)
          - Make sure the Log Level is on 3
          - Check the "Disable Sage Server Ping Verification" box
          - Click "Save Settings"
          - Restart your Sage server and try again.

          If you have the same issue, please send the updated InControlHS.Log file from your main HomeSeer directory.

          Thanks!

          Originally posted by heatvent View Post
          192.168.0.100 is the address sage server. I did the ping and got a reply.

          Comment


            #20
            My son is watching Toy Story at the moment so I will try later when he's done.

            Comment


              #21
              Good news! That did the trick. In fact, seems to connect quicker/easier than ever before.

              Comment


                #22
                Attached, please find log files after updating to version 1.4.3 and disabling the sage server ping verification box.

                Good news - I'm now able to proceed to next step and log in successfully through the sage client.

                Bad news - When clicking on control within sage, I do not see any of the devices where allow control has been checked within homeseer. When clicking on refresh (below options) within sage control, the connection between sage and homeseer gets lost. To reconnect to homeseer, a reboot is required.

                Comment


                  #23
                  Great news, thanks for the update!!


                  Originally posted by heatvent View Post
                  Good news! That did the trick. In fact, seems to connect quicker/easier than ever before.

                  Comment


                    #24
                    Dwalters,

                    It does not appear that the log files were attached to your post. Can you repost them? Thanks!


                    Originally posted by dwalters View Post
                    Attached, please find log files after updating to version 1.4.3 and disabling the sage server ping verification box.

                    Good news - I'm now able to proceed to next step and log in successfully through the sage client.

                    Bad news - When clicking on control within sage, I do not see any of the devices where allow control has been checked within homeseer. When clicking on refresh (below options) within sage control, the connection between sage and homeseer gets lost. To reconnect to homeseer, a reboot is required.

                    Comment


                      #25
                      Mike - Logs should now be posted.

                      Also, a couple additional observations:

                      1. The incontrol settings links within homeseer/InControl_Sage is broken.
                      2. When unchecking the sage server ping verification box, I'm no longer able to log in. The check box needs to be checked to receive log in valid.
                      Attached Files

                      Comment


                        #26
                        dwalters,

                        For #1, can you give me the URL (what is listed after the server name) of the page you are on immediatly prior to getting the Page Not Found?

                        Do you have an InControl.Log.1 file in your Sage Directory?

                        Next, can you shut down Sage and then HomeSeer and edit the hspi_incontrol.ini? I would like you to delete the [Servers] and [Context] sections (delete the section header and all lines until you reach the next section header) and replace it with the below settings. If you would like, you can also post your hspi_InControl.ini and I can make the changes directly. Then restart HomeSeer and then Sage and see if this works.

                        Code:
                        [Servers]
                        0_ID=1005
                        Count=1
                        NextID=1006
                        1005_IP=192.168.76.100
                        1005_Desc=Server
                        1005_Port=10992
                        
                        [Contexts]
                        0_1_ButtonCommand=Play
                        0_1_ButtonLabel=Play
                        0_2_ButtonCommand=Stop
                        0_2_ButtonLabel=Stop
                        0_3_ButtonCommand=
                        0_3_ButtonLabel=
                        0_ButtonCount=2
                        0_Client=NO
                        0_Context=1005_SAGETV_PROCESS_LOCAL_UI
                        0_ContextOnly=SAGETV_PROCESS_LOCAL_UI
                        0_Desc=Server
                        0_HSDevice=YES
                        0_IncludeTitle=NO
                        0_MediaPlayerIP=192.168.76.103
                        0_Ref=4882
                        0_RemoteUI=NO
                        0_SageID=1005
                        0_ServerUI=YES
                        0_Type=Local
                        1_1_ButtonCommand=Play
                        1_1_ButtonLabel=Play
                        1_2_ButtonCommand=Stop
                        1_2_ButtonLabel=Stop
                        1_ButtonCount=2
                        1_Client=NO
                        1_Context=1005_001d6a5caa09
                        1_ContextOnly=001d6a5caa09
                        1_Desc=Family Room
                        1_HSDevice=YES
                        1_IncludeTitle=YES
                        1_MediaPlayerIP=192.168.76.106
                        1_Ref=4247
                        1_RemoteUI=YES
                        1_SageID=1005
                        1_ServerUI=NO
                        1_Type=HD Media Player
                        ContextCount=2
                        Originally posted by dwalters View Post
                        Mike - Logs should now be posted.

                        Also, a couple additional observations:

                        1. The incontrol settings links within homeseer/InControl_Sage is broken.
                        2. When unchecking the sage server ping verification box, I'm no longer able to log in. The check box needs to be checked to receive log in valid.

                        Comment


                          #27
                          Mike,

                          Please use the attached files for reference.

                          1. URL - Screenshot1 indicates the specific link and screenshot2 is the returned page when you click on the link.

                          2. InControl.Log.1 - Included a file called InControl.log.1.lck. This is the only file referencing InControl.Log.1.

                          3. hspi_incontrol.ini - Included a before and after and latest.


                          After rebooting homeseer and sage,

                          1. Logged into sage and reentered user name and password as the device ID was changed. I can now see the devices within sage, however, not able to change for example (on/off).

                          2. The connection between homeseer and sage continues to have a lost connection when logging into sage via control. A reboot is required to reestablish connection within homeseer.

                          3. Finally, device ID 1004 appears within /InControl_Sage...see screenshot3. It seems this device should have been removed when making changes to the hspi_incontrol.ini file?
                          Attached Files

                          Comment

                          Working...
                          X