Announcement

Collapse
No announcement yet.

No Remote Access Into Linux HS3 Install

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

    No Remote Access Into Linux HS3 Install

    Fairly new to Homeseer, coming from not-so-SmartThings.

    Migrating from Samsung, most of my devices are z-wave GE & Leviton wall switches / dimmers, Honeywell Z-wave T-stats & Google Home for voice access. I'm running HS3 on an AMD PC / Raspberry pi.

    Ran HS3Pro trial for 30 days with mixed results as follows:
    Installed Ubuntu Mate 16.04. Installed Mono following instructions found on the forums (mono-complete, mono-vbnc, and mono-xsp4).

    When installed on AMD A10 APU PC running Ubuntu Mate 16.04, was able to connect and operate devices when on my LAN, however could not access from outside (via myhs.Homeseer.com or HSTouch app) and couldn't get google home to work (I'm thinking google home integration relies on having outside access). I even tried messing around with different versions of Mono with same results (latest and greatest, 5.01, 4).
    After about 2 weeks I was fed up and installed on a Windows 7 PC. EVERYTHING worked perfect. Local access as well as remote access. Even messed around with HSTouch designer and was happy with that as well.
    Fast forward to about a week ago. I made the plunge and purchased the license for HS3Pro (@ 50% off, awesome deal!!!!). I also snagged a Raspberry Pi 3 B+, installed Raspbian lite, and installed HS3 Linux, again following instructions on the forum.
    I'm back where I started with only having access locally. Is there something simple I'm missing with HS3 on Linux?
    I've verified remote access is enabled from the web interface.
    Any help would be appreciated.
    Thanks.

    #2
    Welcome to the Homeseer forum Scott.

    Here doing Homeseer 3 (lite) and Homeseer 3 Pro on Ubuntu Linux 64 bit. (tinkering still with Smartthings).

    The in and out from the internet rules (ports) are the same on Linux as Windows.

    Even a bit easier as typically the RPi or Linux stuff is run without a windows gui or console headless.

    There are many RPi / Linux users today remotely connecting to their Homeseer at home from the internet (smart phone or office or whatever).

    Personally here have gone to using VPN over the years to access my home stuff such that I do not open ports up on my firewall. That is me though.

    Baby steps. Other Homeseer users will chime in shortly.
    - 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


      #3
      For the HS3 web browser GUI you open up the port utilized:

      80 - is the default port

      I would change it to something else like 7777 maybe.

      You would then open the firewall for port 7777.

      For HSTouch / MyHomeseer dot com you would open up port:

      10200
      - 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


        #4
        Thanks for the info, Pete. I'll try messing with the ports and post my results.

        I'm also curious if there's specific versions of software people have had success with under Ubuntu 16.04.
        The Linux how-to link from the Homeseer website does list some of these versions, but appears to be outdated. Or maybe there's some additional software needed to run than just HS3 and Mono for the web interface to work?

        I'm nowhere near an expert with Linux, but have toyed around with it for years. I recently built a plex server running Ubuntu Mate 16.04, which is why I wanted to attempt HS3 on Linux. RPi just seemed like the ideal solution for efficiency.

        Comment


          #5
          Originally posted by Gauss View Post
          Thanks for the info, Pete. I'll try messing with the ports and post my results.

          I'm also curious if there's specific versions of software people have had success with under Ubuntu 16.04.
          The Linux how-to link from the Homeseer website does list some of these versions, but appears to be outdated. Or maybe there's some additional software needed to run than just HS3 and Mono for the web interface to work?

          I'm nowhere near an expert with Linux, but have toyed around with it for years. I recently built a plex server running Ubuntu Mate 16.04, which is why I wanted to attempt HS3 on Linux. RPi just seemed like the ideal solution for efficiency.
          Gauss,

          Can you provide a bit more details around your install setup. Specifically to these questions:

          Is HS3 starting?
          What port is the web server listening on?
          How are you starting HS3?
          Are you starting the service as Root? Through sudo or directly?

          Can you provide some command line examples or screenshots?

          Comment


            #6
            I'm also curious if there's specific versions of software people have had success with under Ubuntu 16.04.

            Just about all of the Homeseer plugins posted should run in Linux Mono.

            Basically it just a couple of changes to the plugin such that the same plugin runs in Windows or Linux.

            There are a few Windows Plugins that utilize specific Windows kernal calls that will not run on Linux.

            Personally way back when testing plugins I would specifically ask or request that the plugin run in Linux and help the PI author testing the plugin in Linux.

            The Linux how-to link from the Homeseer website does list some of these versions, but appears to be outdated.

            Or maybe there's some additional software needed to run than just HS3 and Mono for the web interface to work?


            Linux is Linux and mono is mono.

            Homeseer 3 will run on any Linux with Mono (mono-complete and mono-vbnc) installed on any CPU these days (ARM, AMD or Intel).

            There is nothing really special in Linux to run Homeseer 3.

            Personally Homeseer 3 runs better in Linux than Windows. That is my personal opinion.

            I have though played with computers since the 1970's.
            - 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


              #7
              Pete:
              I tried opening ports 80, 10200 & 10400 on my router to no success. I also tried changing the default port from the web interface to 7777 and also opened that port as well on my router, but still no success.
              Now when I had HS3 running on my windows 7 PC, I didn't have to open any ports at all on my router which is why I'm thinking something is setup differently in linux than in windows.

              jeubanks:
              Is HS3 starting?
              Yes, HS3 is starting, and I'm able to access the web interface from different devices within my LAN.

              What port is the web server listening on?
              I've tried 80 as well as 7777 for my server port.

              How are you starting HS3?
              Are you starting the service as Root? Through sudo or directly?

              I start HS3 from the command line (Raspbian lite install). I've tried './go' and I've also tried 'sudo ./go', both locally (keyboard & monitor connected directly to RPi) and also via putty on windows 7 machine. I login into Raspbian with the 'pi' user.

              Can you provide some command line examples or screenshots?
              Here's the complete log when I start HS3:


              login as: pi
              pi@192.168.1.38's password:
              Linux piHomeSeer 4.14.34-v7+ #1110 SMP Mon Apr 16 15:18:51 BST 2018 armv7l

              The programs included with the Debian GNU/Linux system are free software;
              the exact distribution terms for each program are described in the
              individual files in /usr/share/doc/*/copyright.

              Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
              permitted by applicable law.
              Last login: Sat May 19 19:57:13 2018 from 192.168.1.49

              Wi-Fi is disabled because the country is not set.
              Use raspi-config to set the country before use.

              pi@piHomeSeer:~ $ cd HomeSeer/
              pi@piHomeSeer:~/HomeSeer $ sudo ./go
              HomeSeer Linux starting...
              08:06:12:3550:[Database]->Opening (Mode=Read Only) up HomeSeer LOG database /hom e/pi/HomeSeer/Logs/HomeSeerLog.hsd
              08:06:12:5888:[Startup]->Loading Settings
              08:06:12:7818:[Startup]->Settings Loaded.
              08:06:16:7776:[Startup]->
              08:06:16:7789:[Startup]->******************************************************* *************************
              08:06:16:7823:[Startup]-> HomeSeer version 3.0.0.435 Edition: HS3 Pro Starting Now
              08:06:16:7839:[Startup]->******************************************************* *************************
              08:06:16:7855:[Startup]->
              08:06:16:8634:[Startup]->Creating Class Objects...
              08:06:16:8675:[Startup]->COM port classes started.
              08:06:16:8751:[Startup]->Application interface class started.
              08:06:16:8857:[Startup]->Web server class started.
              08:06:16:8886:[Startup]->E-Mail SEND class started.
              08:06:16:8909:[Startup]->E-Mail RECEIVE class started.
              08:06:16:8975:[Startup]->Plug-In Interface class started.
              08:06:16:9017:[Startup]->Local voice recognition class started.
              08:06:16:9081:[Startup]->Database SAVE process started.
              08:06:16:9096:[Startup]->Loading configuration file ...
              08:06:16:9396:[Database]->Opening (Mode=Read Only) up HomeSeer database /home/pi /HomeSeer/Data/HomeSeerData.hsd
              08:06:17:2626:[Database]->Loading Devices...
              08:06:17:2677:[Load Config]->16 total devices loaded.
              08:06:17:2736:[Load Config]->Loading Event Groups...
              08:06:17:2875:[Load Config]->Loading Events...
              08:06:17:2954:[Load Config]->0 total events loaded.
              08:06:17:2965:[Load Config]->Loading COUNTERS...
              08:06:17:3093:[Load Config]->Loading TIMERS...
              08:06:17:3451:[Startup]->HomeSeer version is: 3.0.0.435
              08:06:17:3474:[Startup]->Creating Speaker Client Interface Object...
              08:06:17:3540:[Startup]->This version of HomeSeer is registered as a HS3PRO vers ion.
              08:06:17:4395:[Info]->Remote plug-in API interface started on port 10400
              08:06:17:4409:[Startup]->Checking for available plug-ins
              08:06:18:9176:[Plug-In]->Found plug-in: Z-Wave, version: 3.0.1.190
              08:06:18:9206:[Startup]->Initializing Plug-Ins
              Queuing plugin Z-Wave to load...
              08:06:18:9653:[Plug-In]->Finished initializing plug-in Z-Wave
              08:06:19:0143:[HSTouch Server]->Server started on port 10200
              08:06:19:0255:[Startup]->HStouch server started, waiting for clients to connect.
              08:06:19:0648:[Web Server]->Local IP address is: 192.168.1.38
              08:06:19:0735:[Web Server]->Web Server started on port 80
              Connecting to server at 127.0.0.1...
              08:06:19:1231:[Startup]->Start automation engine...
              08:06:19:1301:[Startup]->Initializing Speaker Client Interface
              08:06:19:1465:[Speech]->Listening for remote speaker connections on port 10401
              08:06:19:1697:[Database]->Opening (Mode=Read/Write) up HomeSeer Energy database /home/pi/HomeSeer/Data/Energy/Energy.hsd
              08:06:19:2371:[Web Server]->Web Server authorized local login successful from: 1 92.168.1.49 User: default
              08:06:19:3346:[Startup]->Updater services starting...
              08:06:19:3406:[Startup]->Starting Find service...
              08:06:19:3692:[Startup]->Running the startup script Startup.vb
              08:06:20:2743:[Info]->Plugin Z-Wave has connected. IP:127.0.0.1:35970
              Connected, waiting to be initialized...
              08:06:20:3348:[Starting Plug-In]->Initializing plugin Z-Wave ...
              08:06:20:3548:[Z-Wave]->InitIO called, plug-in version 3.0.1.190 is being initia lized...
              Z-Wave Plugin: OS Type is Linux
              08:06:22:8402:[Z-Wave]->Database: Opening (Mode=Read Only) up HomeSeer database /home/pi/HomeSeer/Data/Z-Wave/Z-Wave2.db
              08:06:23:3355:[Z-Wave]->Loading Z-Wave Network Objects...
              08:06:23:3675:[Z-Wave]->1 total Z-Wave Network Objects loaded.
              08:06:23:5758:[Z-Wave]->Loading Z-Wave Data Objects...
              08:06:23:5808:[Z-Wave]->1 Networks were restored from the data in the database.. . Building data connections.
              08:06:23:5844:[Z-Wave]->Network FCE5FD47 has 16 device data elements.
              08:06:23:6297:[Z-Wave]->16 total Z-Wave Data Objects loaded.
              08:06:23:9622:[Startup]->Starting Event Scheduler...
              08:06:23:9667:[Startup]->Starting HSSentry watchdog.
              Sentry path: /home/pi/HomeSeer/HS3Sentry.exe
              08:06:24:0105:[Startup]->Scripting is OK and is now running Startup.vb
              08:06:24:0544:[TTS]->Speak ():Welcome to Home-Seer
              /home/pi/HomeSeer/./speak.sh: 3: /home/pi/HomeSeer/./speak.sh: pico2wave: not fo und
              Playing WAVE 'temp.wav' : Signed 16 bit Little Endian, Rate 16000 Hz, Mono
              08:06:24:2518:[Startup]->Starting the HS3 Sentry EXE
              08:06:24:2596:[Startup]->Start up complete.
              Type 'shutdown' to shutdown HomeSeer

              > 08:06:24:5502:[Info]->System connected to MyHS Service, waiting for acknowledg e...
              08:06:24:7438:[Info]->System connected to MyHS Service successfully with license ID XXXXX.
              08:06:25:4214:[Starting Plug-In]->Plugin Z-Wave started successfully in 5086 mil liseconds
              08:06:25:4640:[Z-Wave]->0 event actions were loaded from HomeSeer.
              08:06:25:4657:[Z-Wave]->0 event triggers were loaded from HomeSeer.
              08:06:25:5276:[Z-Wave]->465 Simple AV Control Command Class Control Commands hav e been loaded successfully.
              08:06:25:7969:[Z-Wave]->Z-NETv2: =============================================== =======================
              08:06:25:8003:[Z-Wave]->Z-NETv2: ----------------------------------------------- -----------------------
              08:06:25:8058:[Z-Wave]->Initializing Z-Wave interface Z-NETv2 (HomeSeer Z-NET Et hernet) at 192.168.1.102, port 2001
              08:06:25:8092:[Z-Wave]->Z-NETv2: ----------------------------------------------- -----------------------
              08:06:25:8204:[Z-Wave]->Z-NETv2: The Z-Wave Command Execution Thread was Started or Restarted.
              08:06:25:8492:[Z-Wave]->Z-NETv2: Z-Wave Ethernet at IP 192.168.1.102, connected to interface ok.
              08:06:26:1194:[Z-Wave]->Z-NETv2: The Z-Wave API Execution Thread was Started or Restarted.
              08:06:26:1550:[Z-Wave]->Z-NETv2: Getting node information from controller...
              08:06:28:4176:[Z-Wave]->Z-NETv2: Controller Manufacturer: Express Controls, ID=0 x2, Type=0x5
              08:06:28:4217:[Z-Wave]->Z-NETv2: Controller firmware version: 4.32
              08:06:28:5862:[Z-Wave]->Z-NETv2: Z-Wave services for the SECURITY COMMAND CLASS were successfully started.
              08:06:28:5896:[Z-Wave]->Z-NETv2: Z-Wave Serial API version: 5
              08:06:28:5928:[Z-Wave]->Z-NETv2: Z-Wave interface node ID: 1, Home ID: FCE5FD47
              08:06:28:5976:[Z-Wave]->Z-NETv2: Found 5 Z-Wave nodes in interface node ID 1 (Z- NETv2)
              08:06:28:7083:[Z-Wave]->The interface's security support has been set.
              08:06:28:7325:[Z-Wave]->Z-NETv2 Controller chip type is ZW050x.
              08:06:28:7356:[Z-Wave]->Z-NETv2 Controller is static lib.
              08:06:28:7397:[Z-Wave]->Z-NETv2 There is a SUC/SIS in the network.
              08:06:28:7428:[Z-Wave]->Z-NETv2 is the SIS for the network.
              08:06:28:7537:[Z-Wave]->Z-NETv2: ............................................... .......................
              08:06:28:7569:[Z-Wave]->Z-NETv2: .............................. FINISHED ....... .......................
              08:06:28:7604:[Z-Wave]->Z-NETv2: ............................................... .......................
              08:06:30:2338:[Z-Wave]->******************************************************** ***********************
              08:06:30:2369:[Z-Wave]-> STARTUP COMPLETE: All configured interfaces were succ essfully initialized.
              08:06:30:2401:[Z-Wave]->******************************************************** ***********************
              08:06:55:8724:[Z-Wave]->Starting Z-Wave Polling for Network FCE5FD47...
              Last edited by Gauss; May 19, 2018, 06:19 PM.

              Comment


                #8
                Does/do your system(s) show up when searching from https://find.homeseer.com/ ?

                You don't need to touch your router at all for MyHS access. It doesn't require any ports opened. Your success from Windows is proof of that.

                First thing I'd check is the networking setup. Is the system able to communicate outside the LAN at all? Try

                ping www.homeseer.com

                Comment


                  #9
                  zwolfpack:

                  Does/do your system(s) show up when searching from https://find.homeseer.com/ ?
                  Yes, my HS3 RPi and zNET devices show up using find.homeseer.com

                  You don't need to touch your router at all for MyHS access. It doesn't require any ports opened. Your success from Windows is proof of that.
                  My thoughts exactly. That's why I believe it's something not setup correctly in linux.

                  First thing I'd check is the networking setup. Is the system able to communicate outside the LAN at all? Try

                  ping www.homeseer.com


                  Yes, this pings successfully.

                  Comment


                    #10
                    @Scott,

                    For the web interface here on my machines always change the default port 80 to port XXXX just out of habit as my Linux boxes are LAMP servers running Apache.

                    Try logging manually via the browser on your Homeseer 3 box to myhomeseer dot com.

                    Also make sure the checkbox is enabled. Well it must be because you are seeing your devices. Log in to myhomeseer dot com with same credentials you have configured on your Windows box and configured on your Linux box (or check these).

                    Here I do not utilize myhomeseer dot com and option is disabled and I used to use open ports on the firewall for direct access to the HS3 browser and for Homeseer 3 touch and today utilize VPN.
                    - 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
                      Good, that confirms basic networking is correct. From your transcript I see

                      08:06:24:5502:[Info]->System connected to MyHS Service, waiting for acknowledg e...
                      08:06:24:7438:[Info]->System connected to MyHS Service successfully with license ID xxxxxxx.


                      Which indicates its connected properly to the MyHS service. This should be shown as a connection to 'foreign' port 10300 via command

                      netstat -t

                      What happens when you try to login to https://myhs.homeseer.com from within the LAN?

                      What error indications do you get when trying to login remotely?
                      Last edited by zwolfpack; May 19, 2018, 04:56 PM.

                      Comment


                        #12
                        You should blank out your license ID above.
                        - 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


                          #13
                          Pete:
                          Thanks. I updated my log above.


                          zwolfpack:
                          Which indicates its connected properly to the MyHS service. This should be shown as a connection to 'foreign' port 10300 via command

                          netstat -t

                          Is this a setting maybe I don't have turned on properly?

                          What happens when you try to login to https://myhs.homeseer.com from within the LAN?
                          Works great. When I click 'Access System' it loads up my HS3 web interface.

                          What error indications do you get when trying to login remotely?
                          After I click 'Access System' it hangs, like it's not going anywhere. If I click on 'Access System' again, I receive a "Server Error in '/' Application" (image attached).
                          Attached Files

                          Comment


                            #14
                            netstat -t

                            is a Linux command. Output looks like this:

                            Code:
                            $ netstat -t
                            Active Internet connections (w/o servers)
                            Proto Recv-Q Send-Q Local Address           Foreign Address         State
                            tcp        0      0 192.168.1.105:ssh       192.168.1.129:61459     ESTABLISHED
                            tcp        0      0 192.168.1.105:53330     hometroller:3551        TIME_WAIT
                            tcp6       0      0 192.168.1.105:2001      hometroller:52490       ESTABLISHED
                            I'm running HS3 on Windows so can't show the connection to MyHS service on a Linux system. But on Windows it looks like this:
                            Code:
                            TCP    192.168.1.103:52492    45.76.21.192:10300     ESTABLISHED
                            which is interpreted to mean that my local system 192.168.1.103 has a client port opened to remote server 45.76.21.192 port 10300. 45.76.21.192 is the address for connected2.homeseer.com and server port 10300 is the MyHS service port. [The client port number (52492 in this case) is an arbitrary number an isn't important].

                            When you login to myhs.homeseer.com and press 'Access System', you probably notice that the address in the URL bar switches to a local IP address. In my case its http://192.168.1.103. I believe this is done via some sleight of hand using the data shown on find.homeseer.com.

                            If I login to myhs.homeseer.com but instead press 'Manange Account', then from that page press 'Access System', the sleight of hand isn't done. Now the address in the URL is https://connected2.homeseer.com, but the page displayed is the same. In this case the page is fetched thru the connected2.homeseer.com proxy, which in turn fetches the page thru the back channel connection described above.

                            The fact that your log indicates a successful connection to MyHS service would seem to indicate that your back channel is active; however I'm wondering if perhaps something in the mono TLS (security) setup on your raspi isn't up to snuff. Unfortunately since I'm not running HS3 on a raspi, I'm probably not able to help much in that department. You may want to contact tech support as they may be able to check more behind the scenes.
                            Last edited by zwolfpack; May 19, 2018, 10:10 PM.

                            Comment


                              #15
                              Hi Gauss, did you ever figure this out? I have exactly the same issue and until now have been using a VPN from my phone to SonicWall firewall to work around the issue but now I want to use GoogleHome etc which needs myHS working it seems.

                              I'm running Ubuntu 16.0.4.4 LTS as a VM on ESXi6.5.

                              Homeseer is in a non root users /home folder and I have a cronjob setup from the root account to run the following:

                              "@Reboot sleep 60 && exec sh /home/mark/HomeSeer/autostart_hs #Homeseer 3"

                              autostart_hs:
                              #!/bin/sh
                              export LANG=en_US.UTF-8
                              cd /home/mark/HomeSeer
                              mono HSConsole.exe

                              I see entry's in the logs for MyHS connecting but also see its not heard from it:
                              Nov-09 23:04:26 Info System connected to MyHS Service successfully with license ID xxxxx.
                              Nov-09 23:04:26 Info System connected to MyHS Service, waiting for acknowledge...
                              Nov-09 23:04:08 Warning Have not heard from MyHS in over 3 minutes, disconnecting for re-connection.
                              netstat -t on the server does show a connection:
                              .....
                              tcp 0 0 172.30.1.17:39688 45.76.21.192.vult:10300 ESTABLISHED

                              I too have used this before in a windows VM before in testing before I moved to my production Ubuntu server.

                              Comment

                              Working...
                              X