Announcement

Collapse
No announcement yet.

After migrating to new PC, My Homeseer can no longer connect

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

    After migrating to new PC, My Homeseer can no longer connect

    I migrated to a new PC and everything went rather well. I do have one issue that is driving me mad though. I can no longer connect via my homeseer, which means alexa is dead.

    It shows as 'offline'. I've tried restarting, logging in and out, whatever. How can I get it to realize the install is on another machine now, if that is even the issue? It says "HomeSeer is not running" and "offline"

    #2
    Hi
    Have you checked port forwarding settings for ip addresses?
    It's all I can think of that may have changed.
    I know it's a shot in the dark.

    Comment


      #3
      What OS?
      I have a Hometroller S6 (Windows 7 32-bit), which was delivered with Windows Firewall disabled. Eventually I repaired this idiocy; firewall is now enabled and a few inbound rules established to allow everything to work. I believe the one shown is the one that allows MyHS to work. The complete program pathname is:
      %ProgramFiles%\HomeSeer HS3\HS3.exe

      To test if yours is a firewall issue, try temporarily disabling the firewall and see if that helps.
      Attached Files

      Comment


        #4
        Took the controller back to the original PC and started homeseer. Everything is happy but still have the MY HS issue. It was working fine on this PC, shut down HS, took the stick to the new PC. Got the issue referenced, shut down HS on the new PC, took the stick back to old, started HS and NOW it can't CONNECT.

        I see this in my log:

        Creating connection to MyHS service, there may be a problem with the server or the Internet connection. The connection will be attempted again shortly.

        Pretty frustrating in that nothing changed on this PC. All I did was shutdown, remove the stick and try on another PC. What could that possible have to do with its now inability to connect?

        Comment


          #5
          See if you can login here:

          hxxps://myhs.homeseer.com/

          change the xx to tt above.

          The ZWave stick shouldn't have anything to do with My Homeseer login.
          - Pete

          Auto mator
          Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
          Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
          HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram

          HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
          HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11

          X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant

          Comment


            #6
            What OS, and how is your networking configured. (if its set up as DCHP, the following should all be set up automatically).

            To connect to myhs, the PC needs to be able to (1) translate the name myhs.homeseer.com to an IP address, and (2) needs to know the IP address of the first hop that it can connect to the internet. (1) is called name service; (2) is the default gateway.

            To test (1), enter command (Windows or Linux)
            nslookup myhs.homeseer.com

            Windows response:
            Code:
            nslookup myhs.homeseer.com
            Server:  UnKnown
            Address:  192.168.1.1
            
            Non-authoritative answer:
            Name:    myhs2.homeseer.com
            Address:  54.147.245.0
            Aliases:  myhs.homeseer.com
                      myhs.trafficmanager.net
            Linux response:
            Code:
            Server:         192.168.1.1
            Address:        192.168.1.1#53
            
            Non-authoritative answer:
            myhs.homeseer.com       canonical name = myhs.trafficmanager.net.
            myhs.trafficmanager.net canonical name = myhs2.homeseer.com.
            Name:   myhs2.homeseer.com
            Address: 54.147.245.0
            Both show that the myhs IP address is 54.147.245.0

            To test (2), on Windows: route print -4
            Code:
            IPv4 Route Table
            ===========================================================================
            Active Routes:
            Network Destination        Netmask          Gateway       Interface  Metric
                      0.0.0.0          0.0.0.0      192.168.1.1    192.168.1.124     25
            Linux: route
            Kernel IP routing table
            Code:
            Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
            default         192.168.1.1     0.0.0.0         UG    202    0        0 eth0
            In both cases, shows that the gateway is 192.168.1.1 which is LAN address of my router.

            Comment


              #7
              Thanks for taking a look. With the help of a dynamic dns, I have no issues accessing the PC over the internet. Here are the results from those commands:


              My HS server is 192.168.1.207

              Code:
              Microsoft Windows [Version 10.0.14393]
              (c) 2016 Microsoft Corporation. All rights reserved.
              
              C:\Users\COOP>nslookup myhs.homeseer.com
              Server:  RT-AC68U-CB88
              Address:  192.168.1.1
              
              Non-authoritative answer:
              Name:    myhs2.homeseer.com
              Address:  54.147.245.0
              Aliases:  myhs.homeseer.com
                        myhs.trafficmanager.net
              Code:
                4...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
              ===========================================================================
              
              IPv4 Route Table
              ===========================================================================
              Active Routes:
              Network Destination        Netmask          Gateway       Interface  Metric
                        0.0.0.0          0.0.0.0      192.168.1.1    192.168.1.207    301
                      127.0.0.0        255.0.0.0         On-link         127.0.0.1    331
                      127.0.0.1  255.255.255.255         On-link         127.0.0.1    331
                127.255.255.255  255.255.255.255         On-link         127.0.0.1    331
                    192.168.1.0    255.255.255.0         On-link     192.168.1.207    301
                  192.168.1.207  255.255.255.255         On-link     192.168.1.207    301
                  192.168.1.255  255.255.255.255         On-link     192.168.1.207    301
                      224.0.0.0        240.0.0.0         On-link         127.0.0.1    331
                      224.0.0.0        240.0.0.0         On-link     192.168.1.207    301
                255.255.255.255  255.255.255.255         On-link         127.0.0.1    331
                255.255.255.255  255.255.255.255         On-link     192.168.1.207    301
              ===========================================================================
              Persistent Routes:
                Network Address          Netmask  Gateway Address  Metric
                        0.0.0.0          0.0.0.0      192.168.1.1  Default
              ===========================================================================

              Comment


                #8
                Originally posted by Pete View Post
                See if you can login here:

                hxxps://myhs.homeseer.com/

                change the xx to tt above.

                The ZWave stick shouldn't have anything to do with My Homeseer login.
                No issues with that, however I can't connect after logging in:


                Select System
                HomeSeer is not running.

                73936(Offline)

                Comment


                  #9
                  Just tried logging in today with same result. Will have to investigate when I get home.

                  Comment


                    #10
                    It could be too that your DHCP IP address has changed and your firewall rules were configured to the IP address of the Homeseer server.

                    Are you statically assigning the Homeseer server IP address (whether DHCP or Static?)

                    Here for Homeseer I utilize static IP addressing.

                    Do your firewall rules show the current Homeseer server 192.168.1.207 address?
                    - Pete

                    Auto mator
                    Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
                    Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
                    HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram

                    HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
                    HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11

                    X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant

                    Comment


                      #11
                      Originally posted by shrubby View Post
                      I migrated to a new PC and everything went rather well. I do have one issue that is driving me mad though. I can no longer connect via my homeseer, which means alexa is dead.

                      It shows as 'offline'. I've tried restarting, logging in and out, whatever. How can I get it to realize the install is on another machine now, if that is even the issue? It says "HomeSeer is not running" and "offline"
                      The service was down for most of the night. Does it work now?
                      💁‍♂️ Support & Customer Service 🙋‍♂️ Sales Questions 🛒 Shop HomeSeer Products

                      Comment


                        #12
                        Yeah, other thread reported myHs was down for some.

                        https://forums.homeseer.com/showthread.php?t=190704

                        Comment


                          #13
                          Originally posted by Rupp View Post
                          The service was down for most of the night. Does it work now?
                          Yes, that must have been it. It's curious though. I had left it all day and the last message this morning was that it couldn't connect and that it would try again soon. When I got home, I went to Myhs.homeseer and couldn't connect. So I went to the server and unchecked/rechecked the setting for enabling MyHS service and it connected. I figured, based on the message in the log, it would have done that.

                          Anyway, Alexa works again which is fantastic. I hadn't realized how much I depend on that functionality. Thanks for taking the time to help out. Much appreciated.

                          Comment


                            #14
                            Originally posted by integlikewhoa View Post
                            Yeah, other thread reported myHs was down for some.

                            https://forums.homeseer.com/showthread.php?t=190704
                            Thanks Integlikewhoa

                            Comment

                            Working...
                            X