#Can no longer connect to HA Yellow; did I unknowingly factory reset it?

1 messages · Page 1 of 1 (latest)

bronze moth
#

Something happened to my Yellow - I think it was jostled and/or unplugged by someone cleaning around it - and I had to plug it back in. Ever since, I haven't been able to connect to it.

I held down the button on the Yellow, and it seemed (based on the LEDs) to restart, and I now have constant red and flickering yellow. The ethernet port's light is on, and the light on the ethernet port on the router to which it's connected is on and flickering. My router shows it as connected and active. However, My usual methods (using the companion app or connecting directly via browser to http://homeassistant.local:8123) do not connect. Even http://<IP Address>:8123 doesn't work.

I started to try to follow the instructions on this troubleshooting page: https://support.nabucasa.com/hc/en-us/articles/25455199250589-I-can-t-access-the-system-via-http-homeassistant-local-8123. None of them have worked for me.

Did I factory reset the thing (without meaning to)? If so, how do I reconnect to it to go about restoring a backup?

glass mural
#

do you get any response using port :4357?

#

IP address change or was it reserved?

bronze moth
#

Not able to access it at homeassistant.local:4357, <IP address>:4357 or either way with :8123 ... I get ERR_CONNECTION_REFUSED / This site can’t be reached / homeassistant.local refused to connect.

I'm not sure if the IP address changed, to be honest, but it's possible (as it wasn't reserved), but I'm typing it in copied directly from the router (which shows it as connected at that IP address).

magic basin
#

Can you ping it? If yes, does the ping stop when you unplug the cable?

burnt meadow
#

Connect via monitor and keyboard serial and check

ha network info
ha core logs
ha supervisor logs
glass mural
bronze moth
#

Thank you all - happily (in terms of end result) but frustratingly (because I don't know what I did to fix it or even what was wrong), a number of repeated resets and power cycles (like, many - I was getting desperate before writing this machine off as bricked) later, it's now back up, reachable, and working as before. Thank you to everyone who tried to help, and extremely sorry for wasting your time ... I'll mark this as solved ...