andig
@naltatis ich glaube das funktioniert noch nicht wie gewünscht weil der YAML Error jetzt eine ganz andere Struktur bekommt und damit die line/column Information verliert. Mir ist noch nichts Schlaues...
Ja, wie gehabt: wenn yaml error (ob mit Class oder ohne) dann keine DB. Ebenso wenn DB Class error.
Oder: wir machen das Wrapping fürs Config file anders, analog: ```go func jsonError(w http.ResponseWriter, status int, err error) { w.WriteHeader(status) res := struct { Error string `json:"error"` Line int `json:"line,omitempty"`...
@naltatis nochmal angehübscht falls etwas Unvorhergesehenes passiert. Kann rein?
> What I wouldn't give for immutable byte slices... Cloning the bytes will be quite expensive Isn't the purpose here to use these for other purposes like exporting them to...
@wimaha I guess that's because `getMaxCurrent` gets evaluated at every single cycle. Only option I see is rolling back this addition?
/cc @ScumbagSteve @darkenbula @Dirk77777 @gaetancollaud @wimaha we can either accept the battery drain or remove the interface. Or somebody has a batter idea- it's up to you ;)
In loadpoint.go `syncCharger` the current is always validated when the charger is in `enabled` state. We don't check charging. Wondering why- in the issue here- the charger would be enabled?...
I understood this issue is about `tesla-ble`? So that's the charger considered `enabled`. It is enabled when vehicle is allowed to charge and visible in the logfile.
We only look at the Status, meter is irrelevant.