Installed HA on X-86 by Etching the image directly on the SSD. Have it hooked to a monitor and keyboard to watch first boot. After several tries, it will only boot to the “Home Assistant Command Line” (“ha >_” on the X-86) and does not appear on “https://homeassistant.local:8123/” (on my Windows Computer). Not sure what to do. Any advice or help?
Have you tried using the IP instead of homeassistant.local?
Tried " http://192.168.178.19:8123/". The HA computer is only showing the command line. Is that what it shows while operating?
Yes. And can you see a line saying that Home Assistant is now avalable at http://xxxxx:8123 or something like that? The HA command line is ok i believe
It shows:
Home assistant URL: http://homeassistant.local:8123
Observer URL: http://homeassistant.local:4357
Neither seem to work. Would it be a firewall problem? I thought not since this is local.
So, HA is up and running. What does the Chrome says when you hit the URL using de IP?
You can also try to ping the IP address and/or the alias “homeassistant.local” in the command line to check that you can reach the server
One more… try using homeassistant.local:8123 without the http// in Chrome
FYI, I have the X-86 hooked up with ethernet which worked fine with Win11 before I etched HA, so I think the connection is good.
Chrome says:
This site can’t be reached
homeassistant.local refused to connect.
Try:
Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_REFUSED
Just in case… Is 192.168.178.19 the IP address of the x-86 HA or the Win11 instead? You should use the x-86 IP address.
If that is what you are using you will have to check what is causing the connnection failure between x-86 and Win11… Looks like a software related issue (firewall, antivirus, etc) in win11 machine
The IP was one listed online as an alternative. I’m not sure how to get the X86 IP address as it no longer boots in Win after the etching. I would like to try that. I looked in Fing and tried all the connected ips as http://xx.xx.xx.xx:8123. Is there something else I should try.
I really appreciate your assisting this 70+ retiree with this. I already have a bit of automation to connect to it.
Is http:\xx.xx.xx.xx:8123 the right format?
No, the right format for a url is
http://xx.xx.xx.xx:8123/
On the screen of the HA machine, it should show the IP address that the computer got when it booted. If it doesn’t say so, maybe it didn’t get an IP address.
Another option - at the ha> commandline, type
network info
Tell us what it says.
The usual startup message should show something like this
| | | | /\ (_) | | | |
| |__| | ___ _ __ ___ ___ / \ ___ ___ _ ___| |_ __ _ _ __ | |_
| __ |/ _ \| '_ \ _ \ / _ \ / /\ \ / __/ __| / __| __/ _\ | '_ \| __|
| | | | (_) | | | | | | __/ / ____ \\__ \__ \ \__ \ || (_| | | | | |_
|_| |_|\___/|_| |_| |_|\___| /_/ \_\___/___/_|___/\__\__,_|_| |_|\__|
Welcome to the Home Assistant command line.
System information
IPv4 addresses for enp2s0: 192.168.20.254/24
IPv6 addresses for enp2s0: fe80::8528:35de:etc/64
OS Version: Debian GNU/Linux 11 (bullseye)
Home Assistant Core: 2023.8.0b2
Home Assistant URL: http://hass.local:8123
Observer URL: http://hass.local:4357
Just below system information it gives your ipv4 address.
Thank you for the info. That is the message I got on startup, but I don’t recall any ip address. I will be back at my computer in about half an hour and I will try to retrieve the ip address and get it working then.
After a “network info” I received:
docker:
address: xxx.xx.xx.x/xx
dns: xxx.xx.xx.x
gateway: xxx.xx.xx.x
interface: hassio
host_internet: true
…
I tried these IP addresses in my browser with the proper format (as described) and none seemed to work.
What image did you flash to the SSD? I always use the Generic x86-64 - Home Assistant and I don’t see anything about Docker in the HA console.
What happens when you ping homeassistant.local? If MDNS is working you will see the IPV4 address:
C:\Users\steve>ping homeassistant.local /4
Pinging homeassistant [192.168.1.57] with 32 bytes of data:
Reply from 192.168.1.57: bytes=32 time<1ms TTL=64
Reply from 192.168.1.57: bytes=32 time<1ms TTL=64
Reply from 192.168.1.57: bytes=32 time<1ms TTL=64
Reply from 192.168.1.57: bytes=32 time<1ms TTL=64
I personally don’t trust MDNS, so I use http://192.168.1.57:8123 to get into the Home Assistant GUI.
I flashed:
haos_generic-x86-64-10.3.img
As for pinging:
C:\Users\louis>ping homeassistant.local
Pinging homeassistant.local [fe80::adb2:fe48:d26e:b89e%12] with 32 bytes of data:
Reply from fe80::adb2:fe48:d26e:b89e%12: time<1ms
Reply from fe80::adb2:fe48:d26e:b89e%12: time<1ms
Reply from fe80::adb2:fe48:d26e:b89e%12: time<1ms
Reply from fe80::adb2:fe48:d26e:b89e%12: time<1ms
So does this mean it is a setting in my router? Been having trouble with the login and password to the router. Is http://192.168.1.57:8123 an IP I could try, or is that specific to you?
I read yours again. So I didn’t get an IP back, so MDNS isn’t working? What’s my next step?
There is a bug open for IPV6 issues - maybe that’s the cause.
You got an IP address back - just an IPV6 one… If you have any need for IPV6 internally you can turn it off in your router.
How would I know if I have a need for IPV6? If I turn it off, will that fix my problem? (Notwithstanding the fact that I am having trouble getting the login for my router.). Apparently I have reached the limit for the number of replies for a new user in a day. This is in reply to the reply below. I did disable IPV6 on Windows and a ping did receive a normal looking local IP, but it did not work to bring up the Home Assistant GUI. I assume that means I must disable it on the router, which I can’t find the password to right now. Maybe tomorrow. I appreciate the help and I may reply more after my 18 hours ban.