I can no longer access HA on my Pi 3. All of my room sensor boards are no longer connected via. MQTT as well.
I have tried re-imaging a brand new micro SD card with all three images with the same result.
After using Etcher re-imaging a new micro SD all goes well. I get the standard splash window that it might take HA up to 20 minutes to update. Eventually, I get the login screen. I’ve tried both my existing login and new login’s with the same result. All I get is the spinning HA logo with connecting. I’ve let it run all night, no difference.
I have three ports forwarded on my router 3218, 1883 and 8123 both port range and local.
I am having the same issue… Basically a stock installation of Hassio that I’m trying to configure. Here is what I noticed::
Yesterday, I couldn’t access via Firefox browser. Not sure why but Chrome works. Didn’t worry too much about it thinking that it was a fluke.
Tonight, I connected to http://hassio.local:8123 using Chrome, rebooted Hassio from the UI and now:
“This site can’t be reached hassio.local refused to connect.”
I’ve tried 4 different browsers and multiple machines. I can ping the Pi’s IP with success AND I can see the SAMBA on my network.
The only thing I’m playing with in the config is setting up MQTT- and that is basic from the Hassio store.
any help is greatly appreciated. Spending too many hours on trying to get the configuration working.
I don’t think that would have an effect if you are only connecting locally.
Being able to ping the pi is a good sign.
Can you connect from another PC/tablet on the network? That would prove or disprove your theory.
If you can get your yaml file you wont have to start from scratch. Can you get the config/home-assistant.log file? Does that shed any light on what is happening?
I have the same problem. I set up duck dns as well. everything was working fine and all of a sudden it stopped. (without me making any changes to the files…
How can I get into the config file? any idea please help…