After weeks of successful use, unable to connect to HA Green after Reset

Windows 11, Edge and Chrome Browser
I have been working with HA successfully for several weeks now. Fortunately, I have backups. I screwed up the YAML file and needed to do a reset: hold down button during power up, waiting for solid yellow LED. Lots of LED activity, then a heart-beat yellow LED.

The only change is the reset of my HA Green. Nothing else in the network or my PC changed. HA is definitely on the same network as my PC. My HA Android App is also not connecting.

I cannot connect with the address I have been using (http://)
homeassistant.local:8123/lovelace/0, or homeassistant.local:8123. The IP address for HA OS, 192.168.87.46 hasn’t changed, and I can Ping this address successfully from my PC. 192.168.87.46:8123 also does not work. “Hmmm… Can’t reach this page.”

I struggled mightily with this same problem when the system was new and I can’t remember what finally worked. I believe it was simply adding the /lovelace/0 to the address.

How do you know? Do you have a monitor on the Green? Ethernet?

I have never seen a Green, but this is what I found:

  • Press and hold the button on the back of the device.
  • While holding the button, reconnect the power cable.
  • Keep holding the button until the yellow LED turns solid.
  • Once the yellow LED is solid, release the button. The system will begin downloading and reinstalling the latest version of Home Assistant Core and Supervisor.

“Home Assistant OS” is an “Idle” device listed in my router configuration, at the same IP Adress as it was before the reset. Both my PC and my HA Green are connected to the router via Ethernet cables. I performed the Green reset exactly how you show it… more than once.

Under my router’s “Port Management”
Home Assistant
192.168.87.46
20:f8:3b:01:57:e7
8123->8123 (TCP)

What is the IP of the router and your PC?
What do you get when you ping homeassistant.local? If all you get is an IPV6 address, ping homeassistant.local /4

ASUS RT-N16 10.0.0.3
LAN port on ASUS to WAN port on Google WiFi 10.0.0.241
All ethernet devices on my network (30 devices) are downstream of the Google Wifi LAN port, so they share the same network as Wireless.
PC is 192.168.87.241

For troubleshooting purposes, I connected the PC and HA Green to the ASUS Router. Both devices were assigned new IP addresses. I used the new HA IP address and still got no HA browser connection.

With HA Green and PC connected to ASUS Router, I successfully ping the HA Green.

Correction: The 30 Devices on my network are a mix of Wireless and Wired devices.

Pinging homeassistant.local [fe80::36f9:a8d7:4571:8a78%19] with 32 bytes of data:
Reply from fe80::36f9:a8d7:4571:8a78%19: time<1ms
Reply from fe80::36f9:a8d7:4571:8a78%19: time<1ms
Reply from fe80::36f9:a8d7:4571:8a78%19: time<1ms
Reply from fe80::36f9:a8d7:4571:8a78%19: time=1ms

Ping statistics for fe80::36f9:a8d7:4571:8a78%19:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms

I moved my PC and HA Green back onto the Google WIFI LAN, where it was working before. Here is the ping after that move:

C:\Users\geofc>ping homeassistant.local /4

Pinging homeassistant.local [192.168.87.46] with 32 bytes of data:
Reply from 192.168.87.46: bytes=32 time<1ms TTL=64
Reply from 192.168.87.46: bytes=32 time<1ms TTL=64
Reply from 192.168.87.46: bytes=32 time<1ms TTL=64
Reply from 192.168.87.46: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.87.46:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Home Assistant Observer works fine 192.168.87.46:4357 Connected, Supported, Healthy

I could be wrong, but this sounds like core did not start. Can yo get the command line using the terminal and keyboard on the host computer? Try ha core restart

By “host computer” do you mean the HA Green? Sounds like it’s time for me to hook up a keyboard and monitor to the Green.

Hooked up monitor and keyboard. Entered “Core Restart” Got “Unknown error, see supervisor” Says the ha is not necessary.

Says “Waiting for Supervisor to startup…”

Here’s the log from the failed core restart.

run

ha supervisor repair
ha core rebuild

I’m back. I got suspended for 19 hours for having too many Replies for a new member. I executed the two commands last night. The only change in behavior was that when I reattached the monitor tonight, there was no output from the HA Green HDMI. I had to do a reset. Original issue remains.

supervisor repair: Command completed successfully
core rebuild: Unknown error, see supervisor

Supervisor Log after the above commands:

Here are the Core Logs after a clean Reset.

Home Assistant OS 14.2
Home Assistant Core: 2025.3.1

And here is the Supervisor Log after the clean reset.

SUCCESS!
Restoring HA by holding down the button until solid yellow led, while powering up was the root cause of my problem. Restoring using the SD card method succeeded Resetting the device using an SD card – Home Assistant Green