Nach Update auf evcc 0.310.0 - Fehler "[main ] FATAL vehicle cannot create vehicle 'db:11': cannot create vehicle type 'template': invalid key: climaterdisabled"

[rca1234-lab]

Hallo zusammen,

nach Update auf Version 0.310.0 startet evcc nicht mehr mit Fehler "FATAL vehicle cannot create vehicle 'db:11': cannot create vehicle type 'template': invalid key: climaterdisabled"

Offensichtlich wurde der Key entfernt. Da ich DB-only Konfiguration habe sind unsere vier Fahrzeuge in der Oberfläche alle nicht mehr sichtbar und ich komme nicht ran.

Gibt es eine Möglichkeit das zu fixen oder muß ich alles zurücksetzen und komplett neu konfigurieren?

Grüße, Ralf

[rjkoning]

same here: Fout tijdens opstarten. Controleer de configuratie en start opnieuw.
vehicle: cannot create vehicle 'db:7': cannot create vehicle type 'template': invalid key: climaterdisabled

[mfuchs1984]

Konfiguration sollte dennoch erreichbar sein.

[mfuchs1984]

Welches vehicle ist denn db:11?

[rca1234-lab]

Die Konfiguration ist erreichbar, der Bereich "Fahrzeuge" ist aber komplett leer.
Ich habe 4 Fahrzeuge hinterlegt, weiß nicht welches db:11 ist leider. Kann ich das separat aus der db löschen oder manuell ändern?

[andig]

@claude find root cause in recent PRs

[andig]

@kaindl

[kaindl]

@rca1234-lab, @rjkoning are you using offline- or iso15118-vehicles? For those I can reproduce it.

@andig if we remove a parameter from a template, there is no way to fix it for the user, it will not be included in the yaml, you can create in the "Need help" -> "Report a problem" page and also in the log there is only the invalid key, not the whole config of this vehicle.

I think, we should think about some way to handle such problems better.

prepared a PR fixing this for offline- and iso15118-vehicles (#31297)

[rjkoning]

@kaindl I added one from Home Assistant. the other was Offline

[rca1234-lab]

Thanks a lot for your swift replies, much appreciated!

To your questions: I use all four vehicles as "Generic [no API]" and all four vehicles disappeared.

My workaround I found one our ago was to roll back to version 309.2 . It works fine. I think I should not yet upgrade to a new version of evcc yet.

Follow-up question: would you suggest me to create yaml-files with the config and remove the vehicles from the db then?

[kaindl]

#31297 is already merged, so you should be able to upgrade to anything >310.0 safely :)

and no, no need to move your config to yaml. IMHO this needs to get more robust in the code.

[rca1234-lab]

Thanks a lot - will wait for the current charge to finish, then update again to 310.0 - happy to report here it if works.

Just to mention: it cannot be valued enough that there is a hotfix on a Sunday; thanks again!

[kaindl]

0.310.0 is unchanged, as soon as there is an 0.310.1 you can update :)

[nissty81]

Wann kommt die 0.310.1?

Ich komme nicht mehr vor und zurück.
Fehler bei 0.310.1: vehicle: cannot create vehicle 'db:53': cannot create vehicle type 'template': invalid key: climaterdisabled
Fehler bei 0.309.2: vehicle: cannot create vehicle 'db:54': cannot create vehicle type 'template': invalid key: autodetectdisabled
loadpoint: [db:20] decoding failed due to the following error(s): 'core.Loadpoint' has invalid keys: ui

[kaindl]

@andig

[WhyMe2025]

Same problem here: vehicle cannot create vehicle 'db:65': cannot create vehicle type 'template': invalid key: climaterdisabled

Please fix.

[VolkerK62]

what kind of vehicle is it?

My hyundai is working fine

[WhyMe2025]

ID.4 and Renault 5 Electric

[WhyMe2025]

EVCC doenst work anymore because of this error messages. EVCC asks tot check the setup, but no vehicles are visible anymore. Restart doesnt fix the problem of totally not working anymore just as adding the cars again.

[nilleholger]

Same here

[WhyMe2025]

I rolled back to the virtual machine backup of last week, now everything is working fine on the old version. Will wait before upgrading until this problem is resolved.

[kaindl]

I created #31306 to address this problem in general for the future.

[rjkoning]

THX! @kaindl that did the job!

[Timer2000]

Has the bug been fixed in the new 0.310.2

[ChristopheHD]

Tested in 0.310.1 and bug is corrected.