Announcement

Collapse
No announcement yet.

Anyone successfully running Homeseer in a virtual machine on a Mac?

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

  • Anyone successfully running Homeseer in a virtual machine on a Mac?

    The reason I'm asking is that I have been able to set it um, starting the VM headless at startup of my Mac etc., but there is one issue that I'm not able to overcome and that is that the web/myHS service seems to disconnect.

    I keep on getting these errors:

    Code:
    Oct-17 20:19:46 Info System connected to MyHS Service successfully with license ID .....
    Oct-17 20:19:46 Info System connected to MyHS Service, waiting for acknowledge...
    Oct-17 20:19:35 Warning Have not heard from MyHS in over 3 minutes, disconnecting for re-connection.
    and this messes up myHS and webacces to Homeseer...



  • #2
    Here run an Oracle VB of Windows 7 lite pro or Windows 7 embedded on my Ubuntu 18.04 HS3 pro box. Over the years have switched it from a NAT'd IP address to a bridged IP with it's own MAC address. Note this is using Oracle Virtual box VM's. IE: so the main Ubuntu build is seen as one static IP with iOS computer and the VB is seen as another static IP with MAC. Not sure if this will help you relating to the iOS computer.
    - Pete

    Auto mator
    Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.4X
    Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.4X

    X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

    Comment


    • #3
      I would have to agree with Pete. This sounds like a network related issue. Can you describe how the Network interface is shared to the VM?


      Sent from my iPhone using Tapatalk

      Comment


      • #4
        It is bridged, using the en0: Ethernet.

        I've also tested this using both vmWare and VirtualBox and I have the same issues on both machines. So I guess it is something that MacOS is doing...

        Comment


        • #5
          Originally posted by widert View Post
          It is bridged, using the en0: Ethernet.

          I've also tested this using both vmWare and VirtualBox and I have the same issues on both machines. So I guess it is something that MacOS is doing...
          Can you confirm whether or not you are getting an IPv4/6 address, and if that can route to the outside world?
          Ifconfig
          Ping 8.8.8.8


          Sent from my iPhone using Tapatalk

          Comment


          • #6
            Yes, confirmed. I have a Ā«staticĀ» ip assigned by my router.

            Ifconfig
            enp0s3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
            inet 192.168.50.200 netmask 255.255.255.0 broadcast 192.168.50.255
            inet6 fe80::a00:27ff:fe59:7cf8 prefixlen 64 scopeid 0x20<link>
            ether 08:00:27:59:7c:f8 txqueuelen 1000 (Ethernet)
            RX packets 57229 bytes 32950483 (32.9 MB)
            RX errors 0 dropped 4811 overruns 0 frame 0
            TX packets 55028 bytes 43604084 (43.6 MB)
            TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

            Comment


            • #7
              Ok, would you do me a favor and try pinging something on the public Internet (8.8.8.8) from the host OS. If it works from the host then try from the Guest VM OS.

              Also, have you considered turning off IPv6 on the guest VM?


              Sent from my iPhone using Tapatalk

              Comment


              • #8
                Strangely, the VM has now been ok for the last 3-4 days.

                There has been an update both to MacOS as well as VirtualBox, might be that this has solved the issue.

                Ping is ok from both machines, ref below.

                Thanks for the help.

                Virtual Machine:
                Code:
                tom@userver:~$ ping 8.8.8.8
                PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
                64 bytes from 8.8.8.8: icmp_seq=1 ttl=55 time=9.68 ms
                64 bytes from 8.8.8.8: icmp_seq=2 ttl=55 time=9.61 ms
                64 bytes from 8.8.8.8: icmp_seq=3 ttl=55 time=9.94 ms
                Mac:
                Code:
                tom@wideMac ~ % ping 8.8.8.8
                PING 8.8.8.8 (8.8.8.8): 56 data bytes
                64 bytes from 8.8.8.8: icmp_seq=0 ttl=55 time=9.480 ms
                64 bytes from 8.8.8.8: icmp_seq=1 ttl=55 time=10.265 ms
                64 bytes from 8.8.8.8: icmp_seq=2 ttl=55 time=10.101 ms
                64 bytes from 8.8.8.8: icmp_seq=3 ttl=55 time=9.820 ms

                Comment

                Working...
                X