connecting

[drowsy kestrel]

I bought a new Home Assistant Green, plugged in the power and Ethernet, but I can't get it to connect. I've tried http://192.168.1.1:8123/ and homeassistant.local:8123 and used the companion app as well. I've restarted HA, I've restarted the router, and changed laptops, yet nothing seems to work. It would be great if someone could help me out. Thanks!

[grave wind]

Connect a keyboard and monitor and check ha supervisor logs and ha core logs. Also check ha network info.

[brazen karma]

if you do not have a keyboard / monitor handy, start by logging into the router web ui and seeing what it shows for connected devices - if you tell us the router make and model we might be able to give some directiona as to where exactly to look.

You should see an entry that looks like the Home Assistant Green with the IP Address assigned to it bey the router. Use that IP address in your browser on the laptop instead of 192.168.1.1

[drowsy kestrel]

I am using TP Link Archer AX12. I can see home assistant connect via wired access. The IP given to it is 192.168.0.198. When I enter that in the browser I get the same error "This site can’t be reached
192.168.0.198 refused to connect."
I am using IP Cameras with my router, could that be a possible issue?

[grave wind]

If http://192.168.0.198:8123 doesn't work, can you ping the ip?

[drowsy kestrel]

it works fine when I ping 192.168.1.1

[grave wind]

That's very likely the gateway.

Do ping 192.168.0.198.

[drowsy kestrel]

This works

[grave wind]

Can you reach any of them?

• http://192.168.0.198:8123
• http://192.168.0.198:4357

[drowsy kestrel]

This works

[grave wind]

But 8123 not, okay. To troubleshoot further we really need a CLI. You can try if a reboot fixes it on its own but that's about it.

[drowsy kestrel]

I'm not sure what a CLI is

I tried rebooting a few times but it didnt work

[grave wind]

The command line interface. You need to connect a keyboard and monitor.

[drowsy kestrel]

okay let me do that

would I need a mouse as well?

[grave wind]

No.

An alternative would be to reset the device: https://support.nabucasa.com/hc/en-us/sections/25139705229725-Troubleshooting
I'm curious to check what's wrong though.

[brazen karma]

I'm also curious - but if yu do not have a micro-hdmi to hdmi then you may want to try the reset.

[drowsy kestrel]

okay what now

how do I reset using the command line?

[grave wind]

Check the commands I gave you earlier: #1410641562819498079 message
Right now it seems like it has no IPv4. Please go closer for the following pictures.
The reset procedure is explained in the link above. You can also use ha os datadisk wipe but let's troubleshoot first.

[drowsy kestrel]

so I followed the links you sent earlier and I reset HA. However, now its giving this error

[grave wind]

You can use this to check the supervisor logs

journalctl -fu hassos-supervisor.service

[grave wind]

Press q to get out, then check ip a and journalctl -r. You can scroll with arrow keys.

[drowsy kestrel]

is that the letter Q

[grave wind]

Yep.

[drowsy kestrel]

nothing happens when I press q and enter

[grave wind]

Whenever a CLI tool is "stuck" in some way you usually use CTRL+C or Q to close it depending on what it is.

[drowsy kestrel]

I'm rebooting

[grave wind]

Q was just to get out of the log following tool.

[drowsy kestrel]

okay I did this, what am I looking for here?

or would you want me to send a screenshot

[grave wind]

Yes. I want to check the network settings and look for errors. This could log anything so I can't tell you what to look for.

[drowsy kestrel]

I used the arrow keys to scroll down but I have no idea what I am looking at to be honest

[grave wind]

I need the ip a output too. My guess is that it has no network connectivity.

Also evident by the missing ip

[drowsy kestrel]

the eternet cable is working fine cause I use the same one for my desktop

[grave wind]

Yeah the network interface is down and has no carrier (no link). Make sure to check that both ends of the cable are connected properly. One should be in the router's LAN port. You can run journalctl -f while plugging it in to see if anything is logged by doing that.

To reset the networking settings use this

rm -r /mnt/overlay/etc/NetworkManager/system-connections
reboot

I don't think this will solve it though. You can also try ifup -v end0.

[grave wind]

You need to get out of the log following first via q. Otherwise the commands are just put into the void.

[drowsy kestrel]

q doesnt seem to work

maybe I am missing something

[grave wind]

Or CTRL+C.

[drowsy kestrel]

nothing happens with that either

[grave wind]

This should work.

Maybe it's CMD+C on your keyboard.

[drowsy kestrel]

its a standard windows keyboard

[grave wind]

When you see the # you're out of the log following.

[drowsy kestrel]

oh, I didnt know that

ill use this

rm -r /mnt/overlay/etc/NetworkManager/system-connections
reboot

[grave wind]

That will reset the networking to default settings. The issue right now seems to be a physical one which is why I wanted to check the logs while re-plugging the network cable first.

[drowsy kestrel]

what command do you want me to write?

[grave wind]

Same thing. journalctl -f, then re-plug the cable and see if anything new is logged when connecting it.

Another way would be watch -n1 ip a and concentrate on end0 while doing the same re-plugging.

[grave wind]

I feared there would be too many logs. journalctl -kf might be a bit more quiet as it only shows kernel logs.

[brazen karma]

I'd try a different network cabl;e

[drowsy kestrel]

okay, let me try that

[grave wind]

That looks much better. What does ip a say now?

[drowsy kestrel]

ive pluged it directly into the main router now. Before it was going through a network switch

[grave wind]

Looks good. NIC is up and has a carrier and ip.

[drowsy kestrel]

what next

[grave wind]

What kind of switch is it?

[drowsy kestrel]

tp link switch

[grave wind]

Do you have a model number?

[drowsy kestrel]

I can put the HA green here as well. I just need it to work for now

The CLI isnt working

[grave wind]

At this point I'd do ha supervisor repair; sleep 30; ha host reboot. Then give it 20 minutes or so.

I noticed something. Your subnet is different. Earlier it was 192.168.0.X and now it's 192.168.1.X.
Try if you can reach http://192.168.1.10:8123.

[drowsy kestrel]

stil cant reach

[grave wind]

If your device is in the 192.168.0.X subnet you might not be able to reach it. I'm not sure how your network is set up. Might be double NAT situation here.

[drowsy kestrel]

this is another router that I am connected to now

[brazen karma]

'Supervisor Image missing'

[grave wind]

Note that the log is in reverse.

[drowsy kestrel]

getting this error

[grave wind]

:<

Network issues can really mess the system up.
You can try this: https://gist.github.com/Impact123/e9a4a07b184eb393d2ff762e3b1b0a05#repair-supervisor

[drowsy kestrel]

can I try a factory reset?

if that would be easier

[drowsy kestrel]

cause I am not sure what I am supposed to do here

[grave wind]

Depends on you. Just run all the commands one by one.

I'm still a little bit concerned about your networking situation though.

I have to go for now.

[drowsy kestrel]

okay, well thanks for your help

[brazen karma]

just confirm, you used a different cable to plug to direct to the router you are connected to?

[drowsy kestrel]

currently I am plugged directly into the main router using the default cable that comes with HA green. Before I was using another cable and connected to another router which is connected to this one via a TP Link switch

[brazen karma]

ok, so it is a different cable (I think your problem was the cable). However, it somewhat worked and then the system got corrupted as it started doing updates

type

docker ps -a
``` and send the photo

that command lists all the docker containers

[drowsy kestrel]

I did another factory reset and now I can see cli

[brazen karma]

ok, then it should work is you use a laptop connected to the same router and go to http://192.168.1.10:8123

that photo looks good

[drowsy kestrel]

ITS ALIVE!!!!!!

[brazen karma]

I think I was right about it being the cable

[drowsy kestrel]

Thank you so much guys. I'd been looking forward to HA for so long and I thought I'd get the easiest solution which is HA green but then when I plugged everything I was like.... I dont think ill be able to use it

[drowsy kestrel]

yup

well, I think it was because of a couple of additional connections in the middle like the switch and the other router

this time its working with the main router

[brazen karma]

a switch direct to a router shouldn't make too much difference. But going from router to router will make a difference (double NAT as Impact mentioned)

Hopefully you don't need to move it

[drowsy kestrel]

So I need to same wifi as the one my home assistant green is plugged into right? I have other routers connected to my main routers as access points but I am guessing it won't work on those wifis

[grave wind]

Routers often have a AP mode.

[drowsy kestrel]

What is an AP mode?

[grave wind]

Access Point mode where it acts kinda like a repeater.

[drowsy kestrel]

Oh right, well I'll try it out. Thanks again for all your help!

[brazen karma]

Yes, but if you want do a wick diagram of the hardware and wired between them showing the make and model.

We can then give you suggestions on how to configure.

[drowsy kestrel]

Here is the network diagram. When I plug Home Assistant into the company router, it works. When I plug it into the mesh right next to it, it doesn't. The reason I'd like to plug it into the mesh is that all my smart devices are connected to it. I can do the smart life integration, but for the WLED integration, I need Home Assistant and the WLED device to be on the same network. I control most of the lighting through WLED.
When we did the troubleshooting before, there was a break in the wire between the Switch and HA. After we set up HA directly with the company router, I plugged it into the Xiaomo AX3000, but it stopped working again.
Could you suggest how I can get Home Assistant to work with the mesh?

[brazen karma]

Ok, first thing is what are the Tenda and TP-Link Archer routers doing?

I also think you are running the Xiaomi Mesh in a default configuration. You should change this by setting them to 'Repeater Mode'.

You should wire one Xiaomi to each switch. So you will have one on the Roof, one on First Floor and one on Ground floor that are wired to the switch. Place the fourth unit you have half way to a spot where you have the weakest signal.

Disable WiFi on the Internet Company Router as this is being provided by the Mesh

Having most of the Xiaomi units wired means they will use the wire for backhaul and would provide better connectivity- especially as they are only Dual-Band and not Tri-Band.

By putting them in 'Repeater Mode' you are making them into just access points and all Network Configuration will be handled at the Internet Router

[drowsy kestrel]

The wifi signals don't reach the roof so I got a cheap router for that. The TP Link router is for 5G cause for some reason my phone doesnt pick up the 5GHZ bandwith from the xiaomi router.
When I connect the Xiaomi routers through ethernet then they become stand alone routers and the "mesh" functionality doesnt work.
The Xiaomi router next to the main internet device is connected to ethernet and when I run a cable from that Xiaomi router to HA, I am unable to access HA.

[brazen karma]

This is because the Xiaomi is in it's default mode and not 'Repeater Mode' which is creating a separate subnet and introducing Double NAT

[brazen karma]

In access point mode with a wire, you don't really need them to be in MESH - Devices that connect to the WiFi will use whichever gives them a good connection.

If all those routers have there wifi turned on you will have interference since only 3 non-overlapping channels are available (1, 6, and 11)

You could put the Tenda and TP-Link into access point mode as well.

I'd add that due to the fact that the Xiaomi is dual-band having them running in AP wired will give more bandwidth to connected devices than having them in MESH. In MESH the Xiaomi will use one of the bands to send data back to the main unit - this means a device connected to that band will share the bandwidth.

Using all the routers / wifi units in Access Point mode will flatten your network and simplify it. Basically everything will be on 192.168.0.x at the moment you have a lot of things that are probably introducing new subnets and giving you Double NAT.

[drowsy kestrel]

I can turn all the other routers off for now so that the bandwidth clears up. Also, do you want me to send you the CLI image after plugging HA into Xiaomi main router?

[brazen karma]

set Xiaomi main router to Access Point mode and turn off wifi on the Internet Provider router. Then you should be able to plug your HA Green into any switch or Xiaomi lan port - note that if you are not plugging the Xiaomi to a switch then do not use a lan port for HA Green

With the Xiaomi in AP mode the HA Green should be on http://192.168.1.10:8123 (same as when you plugged it direct to ISP router). All other devices connected to the Xiaomi's will also switch to 192.168.1.X

[drowsy kestrel]

I am still getting the error

what do I write on the cli to check if HA has internet access

[drowsy kestrel]

when I write this in cli it says "unknown command"

[brazen karma]

ha network info

what os is on your laptop?

[drowsy kestrel]

macos

[brazen karma]

so the IP of your Home Assistant is still http://192.168.1.10:8123

you can check you laptop ip - I'm not sure about the UI way as I don't use MacOS however, open terminal and type ifconfig should give the details

[grave wind]

You can't use this in the HA CLI. You need to enter login first. It's when the # shows.

[drowsy kestrel]

This is what ipconfig shows

I can try with a windows laptop

[grave wind]

ip a or ifconfig might work.

[drowsy kestrel]

this is ifconfig

[grave wind]

Also see: https://apple.stackexchange.com/questions/20547/how-do-i-find-my-ip-address-from-the-command-line

So you have 192.168.31.x/24 in your case. Totally different subnet than HAOS.

[drowsy kestrel]

switched to windows

[grave wind]

Same here.

[brazen karma]

Which WiFi are those connected to?

[drowsy kestrel]

HA and the laptop are both currently connected to the Xiaomi router

[brazen karma]

HA is plugged in to the Xiaomi? and the laptop wireless?

[drowsy kestrel]

Yes

[brazen karma]

Is the Xiaomi in 'repeater mode'?

[drowsy kestrel]

let me confirm

I dont know how to put it on repeater mode

[brazen karma]

tap internet connection mode settings

[drowsy kestrel]

okay its on repeater mode now

HA shows up like this on the router

[tight pond]

too much dhcp going on?

[brazen karma]

Now that Xiaomi is in repeater mode, restart HA Green and Laptop.

Run 'ha network info' on HA Green to show us IP
Run 'ifconfig' on Mac Laptop to show IP
Run 'ipconfig' on Windows Laptop to show IP

All IP's should be in range 192.168.1.X

[brazen karma]

Yes, lots of DHCP and Double NAT - hence trying to flatten the network.

[drowsy kestrel]

So it turns out that I had to reboot all the routers after putting the mesh on repeater mode. Once I did that, HA started to work. Just to confirm, the problem was that the mesh was not on repeater mode?

[tight pond]

use a hammer..