Describe the bug

evcc 0.209.1 in docker on ubuntu 24 lts

i use mostly the db-mode and have only my solar inverters in my evcc.yaml. the rest of my configuration has been build in ui. In generell I like the behaviour of evcc to only show things that are relevant in the current context. ie. only show circuits in charger configuration when these are configured.

I changed my hardware configuration and needed to remove my grid meter and replaced it with a new one. that leads to bricked evcc. because my removing the grid meter, the grid as base for circuits was missing. no chance to remove the association between circuit and chargers, because circuit cant come up, because of the missing grid meter. I ended up, removing all my chargers and created new ones without relation to circuits.

** solution i like to see**
if evcc is not able to start a specific part that does not work anymore, do not remove all related settings from the ui, instead leave them there, to enable the user to remove the relations and keep the configuration as stable as possible.

maybe the vision of those settings can be toggled, by adding a debug flag, that show the setting, even if they are not consistent with the current configuration and runtime environment.

** alternative solution **
give a warning, that the related item is not accessable and the desired functionalty will not work until the related item is working. that need to include a db-id change that may or may not automatically is replaced if only one related item, like the grid is referenced.

Steps to reproduce

1. create charger
2. create grid meter
3. create circuit
4. associate charger with circuit
5. remove grid meter

Configuration details

this is only related to db settings!

Log details

nothing to add here

What type of operating system or environment does evcc run on?

Docker container

External automation

• I have made sure that no external automation like HomeAssistant or Node-RED is active or accessing any of the mentioned devices when this issue occurs.

Nightly build

• I have verified that the issue is reproducible with the latest nightly build

Version

evcc version 0.209.1