CLI not starting after update to 14.2 / core 2025.1.4 - "login" not helping

Hello everyone,

this is my first post here, so first of all thanks for all the effort you put into this community, helped me a lot of times already!
My name is Patrick and i am more or less a beginner with home assistant.

System Info:
About the System
Core2025.1.4
Supervisor2024.12.3
Operating System14.2
Frontend20250109.2
wired LAN connection
running in VM installed on windows10

possible outcomes:

  1. fixing the problems, “repairing” my HA instance
  2. help me backup my solar data history and i completly start over again. Since I did not have a lot of custom made sensors and templates, this is no big pain.

Problem
After the update to core 2025.1.4 and OS 14.2 i ran into some problems:

  • many of my integrations do not work properly anymore
  • booting HA shows error messages don’t know how to deal with

Integrations not working anymore:
Viessmann ViCare, Tesla WallConnector, Twinkly, Google Calendar, Blink, Forecast Solar

MQTT is not working as well…
It can be fixed, but the entities do not work after fixing, so the fix is not really a fix :slight_smile:

After searching the internet for solutions, I found a thread where typing “login” in the console was mentioned as a possible solution… did not work for me.
Console after typing “login”
Console 2 after login

As mentioned I am a beginner, so if you need any logs please give me some hints where to find them. Looking forward to your feedback!

Thanks + br
Patrick

Have you tried rebooting the host computer?

Yes tried it several times.
Rebooting Host machine, VM, HA,… does not work

Posting the error messages would be helpful.

You might want to consider installing a fresh copy of the previous working version of the Home Assistant OS and restoring a backup. Then checking the logs to make sure everything is working as expected before upgrading.

backup brings back old data, but does not solve the problem

The logs can be found in home-assistant.log and home-assistant.log.1

Home-assistant.log is the current log file and the log.1 file is an archived log.

A best practice is to create a backup before upgrading. This allows the entire system to be recovered. The problem may have existed prior to the upgrade or there may have been a breaking change in the release notes that you should have fixed prior to upgrading.