Home Assistant issue - "Invalid Server Details"

to clarify... what is the IP address of the machine you are using to PING from?
to clarify... what is the IP address of the Blue Iris machine?
if they are on different IP schemes (example 192.168.100.50 and 192.168.200.50), you will not be able to ping them. One or the other have to be on the same IP scheme (192.168.100.2 and 192.168.100.3, for example).
Well....you will not be able to ping or see machines on a different IP scheme without the help of firewall rules. But that comes later :)
lastly...the 5 things that are important when it comes to IP info is:
1.) network device IP address (example: 192.168.1.50)
2.) subnet mask (example: 255.255.255.0)
3.) gateway (usually ends with a .1 example: 192.168.1.1)
4.) primary DNS (example to google DNS: 8.8.8.8)
5.) secondary DNS (example to good DNS again: 8.8.4.4)
for some reason...when you use different IP schemes (192.168.1.50 and 172.20.1.30)...people call that using different subnets. Which has nothing to do with the subnet mask.
Just wait til you get into VLANS :)
 
Last edited:
Vettester said:
It might help if you post a screenshot shot of the ipconfig command from your laptop.
Click to expand...

As requested (the second ping is a fictional IP to demonstrate the different error message of a not found host).

1644078447998.png

Holbs said:
to clarify... what is the IP address of the machine you are using to PING from?
to clarify... what is the IP address of the Blue Iris machine? The IP of the actual computer is
if they are on different IP schemes (example 192.168.100.50 and 192.168.200.50), you will not be able to ping them. One or the other have to be on the same IP scheme (192.168.100.2 and 192.168.100.3, for example).
Well....you will not be able to ping or see machines on a different IP scheme without the help of firewall rules. But that comes later :)
Click to expand...

IP of FROM machine: 192.168.1.23
IP of BI machine: There are 3 IPs on that machine. 1 is the IP of the actual PC, 1 is the IP for VirtualBox VM that runs Home Assistant, and 1 is for the BI server (I think). Screenshot below. IP address of the PC itself is 192.168.1.20, and the IP address of the BI server is 172.24.144.1 (I did not set this manually or anything, it is what was created by BI). The middle one (Ethernet 5) is the the IP of the Home Assistant VM.

What you are saying about being on the same IP scheme makes sense intuitively to me, but I am puzzled why BI would default to a 172.X--> network address if that's the case.
1644078301246.png
 
this is beyond me. Never dabbled with trying to configure 3 different ethernet adapters in one machine :)

Most I have ever done was to have 2 NIC cards in my blue iris machine: one NIC card connected to my regular network (192.168.1.xxx). other NIC card connected to the different IP scheme (example: 192.168.2.xxx) dedicated dumb 16 port POE switch which all my cameras connected to.
 
if you are struggling to understand IP schemes and subnet topology...it might be better (though less secure) to have all your machines land on the same IP scheme (example: PC 192.168.1.20, HA 192.168.1.21, BI 192.168.1.22
For temporary purposes. then all 3 machines will see each other and work. can later start moving things around to different ip schemes when you are comfortable with more advanced setups.
 
Holbs said:
this is beyond me. Never dabbled with trying to configure 3 different ethernet adapters in one machine :)

Most I have ever done was to have 2 NIC cards in my blue iris machine: one NIC card connected to my regular network (192.168.1.xxx). other NIC card connected to the different IP scheme (example: 192.168.2.xxx) dedicated dumb 16 port POE switch which all my cameras connected to.
Click to expand...

Haha me either. The reality is that BI and Home Assistant are BOTH on the same machine, yet they can't talk to each other! It's making me crazy.
 
out of curiousity, who initially setup your network?
 
i have no skillz for virtual stuff. good luck :)
I opted to have a dedicated Blue Iris machine that only does Blue Iris stuff and a dedicated i3 NUC for Home Assistant for home automation stuff.
I initially was going to put Home Assistant on a Rasperry Pi 3 but a week later, snagged a working i3 NUC for free. I delagated the rasberry pi to do Octoprint/3D printer duty
 
It looks like when you setup the VM in VB it looks like you used the default IP scheme.

Here's the default adapter settings.

Screen Shot 2022-02-05 at 10.04.08 AM.png

You should have changed the IP address to something within the IP scheme you are using.

This link should give you some insight on how to change your VM IP address.

Editing a VM hostname or primary IP address | Skytap help and documentation

Change the hostname or primary IP address of a VM.
help.skytap.com help.skytap.com
 
Vettester said:
It looks like when you setup the VM in VB it looks like you used the default IP scheme.

Here's the default adapter settings.

View attachment 117824

You should have changed the IP address to something within the IP scheme you are using.

This link should give you some insight on how to change your VM IP address.

Editing a VM hostname or primary IP address | Skytap help and documentation

Change the hostname or primary IP address of a VM.
help.skytap.com help.skytap.com
Click to expand...
OK. So let me clarify- should I change the VirtualBox adapter (HA) to the same as the BI one? Ex. 172.X-->?

EDIT: I just tried that, changed the address in VirtualBox to the exact same as the BI server except I changed the last digit from "1" to "12", then tried adding in HA again but it's still not working :/. Let me know if I misunderstood.
 
Last edited:
thompssc said:
OK. So let me clarify- should I change the VirtualBox adapter (HA) to the same as the BI one? Ex. 172.X-->?
Click to expand...
No, it needs to be 192.168.1.x. It's kind of confusing but the 172.x ip address is the virtual network used by HA.
 
Last edited:
You must log in or register to reply here.
Top Bottom