Announcement

Collapse
No announcement yet.

Can no longer log in to HomeSeer using lan up address

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

  • Can no longer log in to HomeSeer using lan up address

    Hi folks,

    i can still use myhs.homeseer.com but since upgrading to .500 I can no longer hit the local up address directly.

    Anyone else have this problem? I don’t know why it says up address is 127.0.0.1. Not sure if that’s related.

    From the about page:

    Current Date/Time: 2/13/2019 1:46:24 PM
    HomeSeer Version: HS3 Standard Edition 3.0.0.500
    Operating System: Microsoft Windows 10 Pro - Work Station
    System Uptime: 1 Day 4 Hours 27 Minutes 24 Seconds
    IP Address: 127.0.0.1
    Number of Devices: 337
    Number of Events: 108
    Available Threads: 799
    HSTouch Enabled: True
    Event Threads: 0
    Event Trigger Eval Queue: 0
    Event Trigger Priority Eval Queue: 0
    Device Exec Queue: 0
    HSTouch Event Queue: 0
    Email Send Queue: 0
    Anti Virus Installed: Windows Defender
    In Virtual Machine: No MFG: dell inc.
    Enabled Plug-Ins
    2.0.28.0: BLOccupied
    3.0.0.56: EasyTrigger
    3.0.0.104: LutronCaseta
    3.0.0.31: Nest
    0.0.0.45: Pushover 3P
    1.0.0.7: Restart
    3.0.1.252: Z-Wave

  • #2
    127.0.0.1 is the loopback address of the HS server. What is the private (LAN) address?

    Comment


    • #3
      did your ip address change? 127.0.0.1 is a special ip address call the loopback or localhost address. i see my real local ip address when connect locally or remotely through myHS.

      HS3 SEL running Pro Edition 3.0.0.531 on Ubuntu 18.04, mono 5.20, 656 devices, 209 events.
      Plug-Ins: Chromecast, Device History, EasyTrigger, Ecobee, JowiHue, LutronCaseta, MeiUnifi, PHLocation2, Pushover 3P, SDJ-Health, Sonos, WeatherFlow, weatherXML
      Scripts: SparkMan's Lock Event, 5 of Jon00 scripts.

      Comment


      • #4
        I did not change it. It should be 192.168.1.13. Why is HomeSeer confused?

        Comment


        • #5
          My outdated .435 shows a LAN IP Address: Do you see this?
          HS3PRO 3.0.0.500 as a Fire Daemon service, Windows 2016 Server Std Intel Core i5 PC HTPC Slim SFF 4GB, 120GB SSD drive, WLG800, RFXCom, TI103,NetCam, UltraNetcam3, BLBackup, CurrentCost 3P Rain8Net, MCsSprinker, HSTouch, Ademco Security plugin/AD2USB, JowiHue, various Oregon Scientific temp/humidity sensors, Z-Net, Zsmoke, Aeron Labs micro switches, Amazon Echo Dots, WS+, WD+ ... on and on.

          Comment


          • #6
            Are you running a firewall that may need to be updated? You can turn off the W10 firewall and test.
            -Rupp
            sigpic

            Comment


            • #7
              I think the issue is with having FireDaemon run HS3 as a service. When I start HS3 manually on the desktop, it runs correctly.

              Comment


              • #8
                So when I run HS3 from the desktop icon, it starts up correctly and knows it's own IP Address. Now I need to figure out what is different about starting it like that.

                Current Date/Time: 2/13/2019 5:06:30 PM
                HomeSeer Version: HS3 Standard Edition 3.0.0.500
                Operating System: Microsoft Windows 10 Pro - Work Station
                System Uptime: 0 Days 0 Hours 1 Minute 35 Seconds
                IP Address: 192.168.1.13
                Number of Devices: 337
                Number of Events: 108
                Available Threads: 800
                HSTouch Enabled: True
                Event Threads: 0
                Event Trigger Eval Queue: 0
                Event Trigger Priority Eval Queue: 0
                Device Exec Queue: 0
                HSTouch Event Queue: 0
                Email Send Queue: 0
                Anti Virus Installed: Windows Defender
                In Virtual Machine: No MFG: dell inc.
                Enabled Plug-Ins
                2.0.28.0: BLOccupied
                3.0.0.56: EasyTrigger
                3.0.0.104: LutronCaseta
                3.0.0.31: Nest
                0.0.0.45: Pushover 3P
                1.0.0.7: Restart
                3.0.1.252: Z-Wave

                Comment


                • #9
                  *SOLVED*

                  I don't know why but I had the setting "Bind Server to IP Address" set to the IP Address of the computer.

                  Once I turned that off, HS3 went back to working via FireDaemon.

                  It still doesn't have the right IP Address in the settings, but it doesn't seem to matter.

                  Comment


                  • #10
                    How can I get to the About page you displayed?

                    My about page doesn't show the information you show in post #1

                    Comment


                    • #11
                      That is on the Tools / Help page
                      HS3 SEL running Pro Edition 3.0.0.531 on Ubuntu 18.04, mono 5.20, 656 devices, 209 events.
                      Plug-Ins: Chromecast, Device History, EasyTrigger, Ecobee, JowiHue, LutronCaseta, MeiUnifi, PHLocation2, Pushover 3P, SDJ-Health, Sonos, WeatherFlow, weatherXML
                      Scripts: SparkMan's Lock Event, 5 of Jon00 scripts.

                      Comment

                      Working...
                      X