Initial Setup Home Assistant Green - Troubleshoot PLEASE HELP!

Installation
1

Hello All - I just purchased a brand new Home Assistant Green. Everything I have read about HA is what I have been looking for. An all in one solution for all of my smart home devices.

I unboxed and connected my HA Green to my COX Panoramic Modem and Router. After multiple reboots of both my HA and Cox Modem, I am still unable to even connect via the HA app. The HA app is unable to locate any servers. I am novice when it comes to setting up home networks and connecting a server such as HA. I tried port forwarding as a bypass but still no luck. I am unsure of what else to try to get HA Green to connect. Any help would be greatly appreciated!

HA Snapshot
HA Snapshot695×859 88.5 KB

2

Try specifying this server address: http://192.168.0.51:8123 in the app or visiting it in a web browser on your local network.

If it works you need to reserve that address (or another one if you prefer) in your router’s DHCP server so it never changes.

3

Hi Tom - thanks for the quick reply. When I enter the specific server address, I get a NSURLErrorDomain - 1004. Failed to connect. Any ideas as to what else to try? I’ve searched solutions with no luck.

4

What do you get with homeassistant.local:8123? when in the phone’s browser?

5

I tried a couple times and it says the server stopped responding.

6

Are you getting positive results from a PC?

7

Still doesn’t work entering a URL on my PC.

8

Open CMD on your PC and enter ping homeassistant.local and post what you get.

9

It doesn’t really do anything. Snippet below.

image
image993×382 21.1 KB

10

Your gateway addresses are different

image

image
image862×40 6.75 KB

11

Indeed, seems like 2 different networks.

12

That’s strange. I just tried pinging home assistant again and got the below.

image
image1402×406 24.2 KB

13

Forget about pinging homeassistant.local for now and focus on LiQuid_cOOled’s post above.

Your HA is telling you that it’s sitting on 192.168.0.51, but somehow your router (or something) is trying to reach it on 192.168.68.53.

Let’s start from the basics:
What’s the IP address of your router? Is is 192.168.0.1 or 192.168.68.53?
Do you have another router in the house which might be handing out IP addresses?

14

I had another deco wifi router but I have now disconnected it.

Below is a screenshot of my COX wifi network.

image
image430×617 11.4 KB

15

Ok, now we’re getting somewhere. Your deco was handing out IPs on a separate subnet, so needs to be set to bridge mode if you ever want to use it again.

Try accessing http://192.168.0.51:8123 now. It should go through the cox router and connect.
If not, check that number of clients connected page on the router and see if HA shows up there

16

Ok I entered that address but it says it can’t be reached. When I go to manage my COX devices connected, it lists the HA as connected. Below are the details on the connection.
image

17

And what is the IP of the device you are trying this on ?

1 Like
18

Below is the computer IP

image

19

The address showing in your screen shot is your IPv6 address so when you ping you can eliminate that by using:

ping homeassistant.local -4 in CMD

I should have been more specific.

20

169.254 is an indication the device is not connected to the network.

If for some reason you lose the connection to the network, then of course your system will not be able to find a DHCP server to get an IP address automatically. So, in this situation, Windows will automatically assign an IP address to itself starting with 169.254. This procedure is called Automatic Private Internet Protocol Addressing (APIPA).

To be clear you have a Cox modem/router and had another router connected, is that correct?

Are you running a VPN?