I ran the update this evening and now HASS no longer works. Not sure what happened.
Looks like my formatting wasn’t up to par and when I did the update it broke the front end.
Happened to me as well, my config.yaml was trowing an error and thus hass was not working. I have it daemonized on a raspberry so it took me a while to realize I needed to look at the log. Would be nice to have a message on the front end or something telling you that your config is bad.
I ran into the same issue. I just backed up my files and uninstalled and reinstall HA. I wanted to do that anyway to get it installed as --user instead of having to sudo.
After that I manually launched hass from /home/%user%/.local/bin so it would create some directories and files.
Then I added back to my yaml what I had backed up.
Then launched with hass --open-ui and I had my front end back. Had I not wanted to get away from having to sudo everything, I probably would have been more interested in troubleshooting but this just gave me an excuse.
Do you guys have Plex running in a home server? For me I’ve had to install plexapi from pip3 and all is well. Perhaps if you could show us home-assistant.log maybe we can help.
We no longer will start up if we find invalid YAML because you know, it’s invalid 
Means that we also can’t show it in the frontend. I have on my to do list to make a hass --validate command to give feedback on your config.
One thing I just noticed is that there are no times under an item. It use to say when something was last updated underneath the item. Did this change with the most recent update?