SAD TUBA - upgraded 45.1 to recent. Connection refused

Hassbian. Followed steps from site directly, and now I am dead. I was very concerned with upgrading, all was working well. Where can I start to determine why I have lost connection?

Do you normally access the pi’s configuration.yaml and home-assistant.log from a windows pc network connection? If so, check your log file to see what happened. If you don’t use a windows network connection to access your homeassistant setup or if the connection isn’t working. Try checking the home-assistant.log via logging in with PuTTY: Access the Pi with PuTTY (IP shoud be 192.168.1.129 , or you can check your router’s connected devices area to find its IP – maybe its IP changed and that’s the problem? <-- in this case, you can reserve a local static IP for the Pi in your router settings), then log in, then type sudo nano /home/homeassistant/.homeassistant/home-assistant.log to look for error messages (CTRL-X to escape).

Are you working in “headless mode” (ie: no monitor plugged into the Pi?). If you can’t access the Pi at all, I would highly recommend plugging in a monitor and keyboard to see what’s going on. One time I found kernel panics on boot up and realized my power cable/supply to the Pi was underpowered for the Pi’s amp needs.

This may not help right now, but just wanted to share that it is possible to create ‘disk images’ of the Pi’s entire SD card via win32diskimager, so that you can clone your SD card as a backup file on a separate PC, then use the backup file to completely restore a previous installation at a later date.

Thank you for the response, I honestly don’t know what happened. I walked away for 30 min and poof…I connected. I do always keep an image back up of my last good operating system…CYA

The first boot after an update often takes a while before the UI is available. Subsequent reboots will be much faster.