Cannot access Hassio.local:8123

In the instruction (7) to installing hass.io

Blockquote
The Raspberry Pi will now boot up, connect to the Internet and download the latest version of Home Assistant. This will take about 20 minutes.

Blockquote
My mistake I stated update, i was meaning the above.

Itā€™s NOT connected to the Internet to do ANYTHING

Or to put it another way, it cannot connect to the internet unless it can get an IP address (from a dhcp server) and have a route to the internet. Home assistant is clever, but not clever to conjure up a connection to the internet where none exists.

1 Like

Once you plugged your RBpi in your router, wait about half an hour. Then it should be up and running.

Thanks to Francis, nickrout, and David.
I got another ip address 192.168.1.4 and now I got the HA connect @ http:// hassio.local:8123

1 Like

And please stop using ā€œblockquotesā€ and/or ā€œcodeblocksā€ for all of your posts. It makes it very difficult to read and thatā€™s why your screen shots werenā€™t showing.

1 Like

Iā€™m having periodic problems with local access. Figured this looked like a good post to glom onto.

I have a duckdns account, but my home computer is typically connect via hassio.local:8123. Sometimes it doesnā€™t work. I also have the Samba Share and SSH add-ons installed so I can access the config files and appdaemon from a local computer. When hassio.local quits connecting, so does everything else locally (samba share, SSH access, and the mariadb frontend HeidiSQL to query the hass mariadb). Interestingly, I can still access my hass.io lovelace frontend by going through the duckdns server route.

The local IP is 192.168.1.9 and shows up in the list of items attached to the router. All my automations still work fine. Itā€™s just that I canā€™t connect through hassio.local through either a browser, Samba Share, SSH, or any other way that uses either hassio.local or the actual local IP address. Iā€™m pretty sure if I restart hassio, everything will work again (it didnā€™t!). But after robooting the RPi3, it did work again - I have local access back.

Any ideas? Itā€™s kind of annoying to lose that capability every now and then.

Iā€™m running 0.101.3 (getting ready to upgrade to 0.102, but havenā€™t yet - pretty sure thatā€™s not the issue).

Thanks for any advice!

when hassio.local stops resolving, does the IP address work?

If so it is a mDNS problem.

Thanks for the quick response, @nickrout. I tried that and it does not work either.

I didnā€™t have to reboot my router to get it to work (not sure that matters in troubleshooting). The only thing that brought it back was rebooting the RPi that runs hass.io. Restarting HA didnā€™t do the trick.

Does ping work to either address?

Hey Everyone. New here, just installed on a Rpi3b+. Ive been watching your convo and thought i would jump in too, as im having pretty much the same issue as far as not being able to connect either wireless or wired. when i pull my IP addresses, i have 2 for hassio but i cannot seem to get to the GUI. My command screen is giving me a login option.what am i missing?

Dang - didnā€™t try that, and now Iā€™ve rebooted so it works. Should ping work to hassio.local?

What is the command screen? Id it a monitor connected to your Pi? You have to load the network info onto a USB stick when you first install so hass.io knows how to connect. That goofed me up when i first installed it. Iā€™ll find where thatā€™s described and repost.
Assuming youā€™re installing hass.io?

EDIT: hereā€™s the link that describes the wifi config file - Getting started - Home Assistant It seems pretty picky about following the instructions exactly. I seem to recall having to do this a couple of timesā€¦

The fact that you have two IPs might be because you have both a wifi and direct internet connection if you have it plugged in, too (?). I also set a static IP address for hassio to keep it from changing.

Hope this gets you going!

Yes it should work pinging by name.

I just lost local access - I tried pinging both the IP and hassio.local - neither worked (timed out). Going through duckdns does work, but I canā€™t access any of the files through samba share or sshā€¦

EDIT: I upgraded to the latest release (0.102). Once it restarted I still didnā€™t have access to hassio.local through any means (samba, ssh, Chrome). I cycled power to the RPi and then I had access. Is it possible the hassio internal DNS server is getting messed up somehow?

Hi, Iā€™m new and trying to get some help. I just got HomeAssistant up on my Rpi3b+ by flashing a 32GB SD card using etcher. I used the 64bit image (hassos_rpi3-64-3.12.img.gz). I have it connected by an ethernet cable. I tried connecting to Hassio.local:8123 but was unable to but came across an article which recommended trying to connect to the IP address directlyā€¦ (X.X.X.x:8123) which I was able to determine from a new device named ā€œhomeassistantā€ which showed up in the list of wired devices on my router. This worked and I got into HomeAssistant created an account , even connected to my Sonos speaker and I was able to make it play a song then a couple minutes later it says connection lost and I have been unable to connect since.

Through the console Iā€™m able to login. I ran ā€œhardware infoā€ and I see a list of audio, disk,gpio, input and serial devices but nothing about network devices. Any help on some basic troubleshooting I could do from the console would be greatly appreciated. I just keep seeing this message repeated:

IPv6 ADDRCONF(NETDEV_UP) wlan0: link is not ready

I donā€™t see network devices either when running ā€˜ha hardware infoā€™

@HAtest:~# ha hardware info
audio: {}
disk:
- /dev/mmcblk0p2
- /dev/mmcblk0p1
- /dev/mmcblk0
gpio:
- gpiochip0
input: []
serial: []

@HomeAssistant:~# ha hardware info
audio: {}
disk:
- /dev/mmcblk0
- /dev/mmcblk0p1
- /dev/mmcblk0p2
gpio:
- gpiochip0
input: []
serial:
- /dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0
- /dev/ttyUSB0

If you look at the console from a attached monitor, it is normal to see that message. Why do you think that is a problem ?

Did you ever find a solution?
Have you tried a different browser? Some default security options are very restrictive.

I know itā€™s been over a year but I suspect some folks looking for help are still finding this question.

BillP