Hass virtual box IP address issues

Configuration
1

Hi All

I’ve recently moved over to hass on virtualbox. I had it running also side my pi environment for a while to test before switching my hassbian pi off.

Setup
NUC pc running Windows 10
Virtualbox running the latest hass - bridged network
Pfsense leases a dhcp address via vm mac of 192.168.5.235

Now everything seemed to be ok above ip reachable and if I login to the vm hass terminal I can ping all of my devices on the 192.168.5.0 subnet.
I briefly turned on discovery to configure my axis cameras 192.168.5.74 & 5.199. When discovery found them they were listed on a 169.254.x.x address (local loopback)

Now even though pfsense has leased the ip of 5.235 to my vm hass, what’s happening in the vm when I do ifconfig I get what is like a natted address 172.x.x.x

All seems very strange and I’ve never experienced this with other virtual box machines.

Any ideas would be appreciated

Thanks folks

2

One other thing to note. The axis cameras will only work when configured manually. Even though they are reachable on either the 169 or 192 addresses hass constantly changes the acces token ID

3

Have you fixed this yet?

I just want to confirm your configuration so I have it clear.

PFSense LAN: 192.168.5.0/24
Camera: 192.168.5.74
Camera: 192.168.5.199

HASS VM: 192.168.5.235 (DHCP)
How is HASS installed, is it Docker. or straight up Linux or Windows or Other?

I’ve personally never used Virtual Box, but I do run PFSense and I do run Hass.IO in docker on a NUC running Ubuntu Server. So I can assist where possible.

4

Yea I think so :grimacing:.

Dopey me realised the ip is the docker host that hassio is in (only just changed over from hassbian).

As for the cameras I’ve sorted them by manually adding again rather than use auto configure. I’ve not resolved the token id changing all the time but I think that’s an appdaemon issue doing it. As I get illegal login attempt failed from my tablet running the hadash front end.

In the last hour I’ve put a response on another post relating to similar issue.

Have you got same problem?

5

My LAN is split in to multiple VLAN with all IOT on an Isolated subnet with strict rules only allowing specific devices hassio and out to the WAN.

I use NEST for cameras so I’m not sure I get this issue, however I have a friend who had an issue similar to what you have described and he managed to resolve it. I’ll send him a message for the resolution.

6

Not sure if this help or if its the same issue, but this is the config he is using.

camera:
  - platform: ffmpeg
    input: -rtsp_transport tcp -i rtsp://192.168.5.199/unicast
    name: LivingRoom