Charge battery (from Grid) Cutoff Soc missing

[qbushome]

Hi

Am I right when I say that I'm missing this Configuration parameter?

number.al700xxxxxxxxx_bathighcap returns 100%

I don't think this referes to the same information.
In the App I set "Charging Cutoff SOC [%]" to 65%.

The only place where I can find my "65%" is in sensor.al700xxxxxxxxx_charging_range, which gives me "Charging Range
99.0% - 65.0%".

Thanks for looking into this.

Regards

[Poshy163]

Heya @qbushome,

The charging_range sensor reflects the charge/discharge SOC boundaries configured for your battery, its represents the range within which the battery is allowed to charge and discharge.

you can find these settings within the alpha app within the settings > charging/discharging settings. you may need to enable the charge/discharge toggles within the app to see it (this wont automatically charge/discharge unless you set time bounds)

[qbushome]

Hi

I know I can find it in the app., but...

Take the action alphaess.setbatterycharge (and it's brother setbattery discharge).
There is a parameter: chargestopsoc and dischargecutoffsoc

To change this parameter you have to call the action complete with all other parameters.
So just to change the cutoff for (dis)charging, I have to call an action

        data:
          enabled: "{{ (states('input_boolean.alphaess_grid_discharging')) }}"
          cp1start: "{{ (today_at(states('input_datetime.alphaess_start_discharging_1'))).strftime('%H:%M')}}"
          cp1end: "{{ (today_at(states('input_datetime.alphaess_stop_discharging_1'))).strftime('%H:%M')}}"
          cp2start: "{{ (today_at(states('input_datetime.alphaess_start_discharging_2'))).strftime('%H:%M')}}"
          cp2end: "{{ (today_at(states('input_datetime.alphaess_stop_discharging_2'))).strftime('%H:%M')}}"
          chargestopsoc: "{{ (states('input_number.alphaess_stop_discharging_soc')) }}"
          serial: "AL7001xxxxxxxxxx"

It would be great to have a "number.al7001Xxxxxx_chargingcutoffsoc" that I can change and it does the job.

I hope you understand what I mean.

[Poshy163]

Ahhh, now i get you, this already exists, as batHighCap and batUseCap (which is the names the openAPI documentation uses)

these numbers once adjusted, send an updated call to the API with all the other values contained within either the charge or discharge (aka the 2 charge/discharge slot times)

[qbushome]

Ah, ok, but that was confusing because these numbers don't update when I change these values in the App/Website or with the action alphaess.setbattery(dis)charge.

So when I set discharge cutoff to 15% (website), batUseCap (HA) remains 10% (in your exampke above).
When I change batUseCap to 20%, and I take a look at the website, I see it has actually changed to 20%.

Because of that, I did not realise these numbers above are the same as the (dis)chargestopsoc-values in the action.

Edit:
Seems not to be the case for Charge and Discharge Start+End-time. When I change these on the website, the entities in HA change after a few seconds.

So it's only batUseCap and batHighCap not updating after changing these online.

Edit2:
I stopped using the actions and just use the entities (number and switch) to do the changes, working perfectly.
/me happy