Michael Geers
Michael Geers
Yes, we currently don't have a process for UI-configured tariffs since they use raw yaml. Option 1: We could reuse the `evcc.yaml` redactor for yaml-response config endpoints. This would have...
I'd say auto-gen on activate through user. Not sure if we really need a manual upload or cert entry. Can still be done via CLI really necessary.
Yes, I'd say we can migrate yaml based configurations. Only auto-gen if user wants to activate and no certain is found in config.
\cc @marq24
@Maschga ui change looks good 🎊. I only introduced a couple of computeds to eliminate redundant checks.
@andig what do you mean with `structure: decide totals sub key`? Moving `battery.[soc,power,capacity]` to `battery.totals.[soc,power,capacity]`? I'd see why this would make sense symmetry-wise, but I'd keep this structure as-is right...
> decide name/title handling to avoid empty @andig You mean adding a `name` field to the `Measurement` entry? If this is technically possible we should add it and use it...
> I don't see the green button: Ok is see. I think I have to level up the demo auth service to make a reliable test for this szenario.
@andig Did this happen in "Create vehicle" dialogue or did you open the auth modal from navigation?
Kontext? Experimental Config UI? Auf der Dokuseite steht dieser Text ja.  Glaube aber auch, dass wir den Satz an sich noch mal überarbeiten,bzw. ausführlicher...