Michael Geers

@andig hier passt noch was nicht ``` go run main.go --config /Volumes/data/evcc/evcc.yaml meter sungrow_battery -b charge [main ] INFO 2024/07/21 11:49:40 evcc 0.0.0 [main ] INFO 2024/07/21 11:49:40 using config...

Hier mit mehr Logging. ``` go run main.go --config /Volumes/data/evcc/evcc.yaml meter sungrow_battery -b charge [main ] INFO 2024/07/21 15:05:23 evcc 0.0.0 [main ] INFO 2024/07/21 15:05:23 using config file: /Volumes/data/evcc/evcc.yaml...

Meine lokalen Tests waren jetzt alle erfolgreich. Charge Mode lädt jetzt wie gewünscht mit voller Leistung aus dem Netz.

> This might be linked to https://github.com/evcc-io/evcc/issues/19765 and https://github.com/evcc-io/evcc/issues/19650 It's a little related, but we'll keep the `priority` setting separate. What you're talking about here is more of a visual...

@andig implement by adding an `order: [int]` field to loadpoint (evcc.yaml & config api) which is is used on boot to sort all loadpoints? We'll also need this for vehicles...

@detlefheese priorization is handled in this issue https://github.com/evcc-io/evcc/issues/19650

> If we need this everywhere lets do it line title/icon and keep it outside the loadpoint api? Would make it easier. But we'd still have the above described issue...

@pvmil please leave it open. This is something we should implement. I see the priority as not very high right now, but if it's open people can refer to it...

The UI currently assumes that prices only change every hour. Cheap grid charging, cost calculations and afaik also the planning algorithm are not limited to fixed time intervals. What would...

> In terms of U.I. , I would imagine that if possible, it would be fantastic to actually derive the interval duration from the API request Yes, this sounds like...