Yes, running on 20GB of RAM, this should not be the bottleneck.
@boheme61 For sure, I can just start over. But honestly, this is not my demand here. This installation is really without any bigger value… But I want to really understand what went wrong and get used to narrowing down errors to their root cause I can fix.
Just imagine I’d be one year ahead, with hours and hours invested in my setup and then facing a comparable error… Then my go-to-solution will definitely NOT be to start over, without restoring any backups. I think it is important to not only follow the happy path. This is the only thing I’m pointing to here… If this is not your approach, ok for me. But maybe there’s someone else out there who might help me out with some hints on identifying and fixing such issues.
What I did in the meantime: Deactivated FiatChamp and removed the device from MQTT. Put debug on startup entries as descibed in “Integration blocking startup” in 2024.5+: Tracking down instability issues caused by integrations - Community Guides - Home Assistant Community (home-assistant.io), but this did not really provide valuable insights.
Nevertheless, I still see random errors such as error when changing vscode addon configuration (sidebar switch). The only things I see in the home-assistant.log at that time is an error because there was a timeout. That is it. But for identifying the timeouts cause, I’d need to know which process or integration eats up resources…