Loadpoint: rename chargeCurrent to offeredCurrent (BC)

[premultiply]

The name chargeCurrent at the loadpoint is confusing because, unlike chargeCurrents and chargePower, it is not a measured value but the setpoint value that is sent to the charger.

This PR therefore changes its name to offeredCurrent.

For the API exports, the old export name will also remain for the time being, but will be considered deprecated.

/cc @andig @naltatis @mfuchs1984

TODO

• rename in UI/App (@naltatis)
• align log messages with new naming @premultiply
• OPTION: redefine and publish lp.chargeCurrent as "max(lp.chargeCurrents[])": maximum measured charge current for better API compatibility (non-BC)

Out of scope

• fix circuits (Circuits: review and validate logic from #20183 #20365)

[andig]

Wenn wir das machen dann sollte es komplett sein. Keine doppelten Namen.

[naltatis]

Der UI Change ist überschaubar, soll ich den hier mit rein machen damit wirs sauber haben?

[andig]

Ja bitte- ganz oder gar nicht.

[andig]

Auch das Logging muss mit angepasst werden.

[andig]

@premultiply wozu brauchen wir

2. redefine and publish lp.chargeCurrent as "max(lp.chargeCurrents[])": maximum measured charge current

[naltatis]

fyi @marq24

[naltatis]

UI ist angepasst und das publishing des alten Wert (chargeCurrent) entfernt (BC)

[marq24]

so chargeCurrent will be renamed, but the array chargeCurrents will stay... this will generate some issues in HA... but I must check, if and how this can be handled....

I just 'invent' key_alias - so now I can get the value by two different keys - in HA the name will be still the old one...

[premultiply]

The option is to remap the name chargeCurrent to the content of max(chargeCurrents[]) and keep publishing it in addition and next to the new published value offeredCurrent.

So the name would stay but the meaning would slightly differ from before. I think this would not break anything in most cases as it would show correctly what was just suggested before.

[naltatis]

So the name would stay but the meaning would slightly differ from before.

I’d rather remove the existing key and accept the breaking change.

[marq24]

So the name would stay but the meaning would slightly differ from before.

I’d rather remove the existing key and accept the breaking change.

I am totally fine with that: your project -> your rules :-D

[premultiply]

LGTM?