I’ve just setup HA today but not had time to set much up yet.
Suddenly the browser (Edge, Explorer and Chrome) will not connect via http://homeassistant.local:8123 which has previously been working a treat. The app keeps having connection issues.
It’s installed on a Pi4, which is on Wifi. I originally planned to run with an ethernet but no matter what I did, the install crashed. This happened a handful of times but the first time setting up with Wifi credentials, it work first time. So at some point I want to switch to ethernet.
I don’t normally have Wifi issues and I’ve checked the speed etc and everything seems to be running as expected. It was working fine this afternoon, as I installed ESPhome and an ESP8266 module.
homeassistant.local is mDNS, which means “multicast DNS”. It relies on whoever is going to use it to be able to receive 1-hop multicast messages from the device.
This can be affected by sooo many factors. Well, just a few…but still. Wifi router configuration, wifi isolation (wired, 2.4 ghz, 5ghz), windows vs iOS vs linux (bonjour vs Avahi for handling mDNS), etc.
So I wouldn’t worry about that part too much. Just use the ip address which should always work if it’s running and stable.
Are you saying there are still issues after using the ip address? Can you just ping the rpi in a cmd and leave it running for a while?
Hello, thank for the advice. It all started loading again through the browser, using the IP.
But following your advice and using cmd to ping the Pi, all I get is unable to find host. If I ping homeassistant I get the same. I’ve used the Fing app to find the IP but nothing works.
I installed Home Assistant onto the SD card, via the instructions on the main page, so Fing does not see the Pi but HomeAssistant. Bit odd really, not sure where to go from here.
Log into your router (if you have access) and see if it shows up as an attached device.
Or connect the pi to a monitor and access it directly to do an ifconfig to see the ip address. Might even have errors.
My guess (only because this exact thing happened to me) is the power supply isn’t big enough and it’s either rebooting, kernel panicing and freezing, etc. Or it’s a bad SD card and you should write the image to a new one (also happened to me).
Windows saying unable to find host means it has a route to it IF, but it’s either not on, or not at the address you specified, or not connected to the network at all. So your clues are going to live on the pi itself at this point.
I have pinged it prior to using HA, running Raspbian. I’m new to Pi and coding so it’s all new, as you can probably tell.
There is no Raspbian image installed on the SD, just the HA image, which is why I’m wondering the Pi does not show up but Home Assistant does, with an IP.
The PSU is an official Pi one, so I’d rule that out. Although it could be a duff one.
I’ll check the router
EDIT: I checked via the router and the IP address which I have is correct and the Pi is not showing but Home Assistant is.
The HA image is its own OS. Home Assistant Core runs on Raspbian Lite. Home Assistant image is a custom OS (HassOS…based on buildroot)
I don’t use this image (I use Home Assistant Core), but keep in mind when you get access via console (username root, no password). There should be an on-screen instruction for how to exit the HassOS to get to the root filesystem so you can do normal linux commands.
I did set it up with Raspbian Lite but I started again and installed the image mentioned. Not sure which is the better option. Possibly should have stuck with the Rasbian Lite. Any thought on that?
Depends on what you want really. Home Assistant Core doesn’t have the add-on capabilities. All custom integrations you want have to be manually installed. I’ve only ever used Core, so I can’t say which I prefer. Keep in mind, it seems like nearly everyone else uses HassOS, so when you’re searching for help, tutorials, etc…most of them are only for HassOS and using the built-in addons.