Dynamic current control on Wallbox Pulsar plus

[jostd]

I have started to use this ocpp integration to control my Wallbox Pulsar Plus chargers about a week ago.
I previously used the cloud API from Wallbox, but that is currently not workable with a multiple charger setup.
My main concern is that there are multiple means of limiting the charge current for dynamic (solar) charging, and I don't know which one I should use.

The oocp integration provides number._maximum_current, which sends a default profile to the charger. There are multiple instances on the web, where people warn, not to use default profiles, because it will wear out non-volatile memory on the charger. One discussion on this (ocpp) github page is here:
discussion 1566
One should rather use a (temporary) TxProfile in order to preserve non-volatile memory. I have tried this out and it works, But it is flying blind, as there is no HA entity/state associated with it. The service call (action) to ocpp.set_charge_rate with a custom profile doesn't appear to return a success state. I suppose one would have to retrieve the profile of that ID to check whether it stuck...

I have also read that the TxProfile being written to volatile memory is only a requirement for ocpp 2.0.1, not 1.6, which the wallbox chargers are running.

There are two additional methods for sending current limit to the integration:

1. The Pulsar Plus has a feature called chargingALimitConn1 which can be set and read via ocpp's configure and get_configuration commands. This also works to limit charging current
2. Occp also provides the limit_amps parameter for the set_charge_rate action (service). This action will send a MaxProfile with max staxk-level (10).

Does anyone know what is best for the Wallbox chargers?

[pemillenaar]

following. I'm in exactly the same boat.
Did you find out anything useful in the meantime? I tried installing the Dynamic OCPP EVSE here on Github but I can't get it installed somehow. Did you consider or use this one?

[jostd]

Hi @pemillenaar
I tried a number of solutions but finally stuck to this lbbrhzn/ocpp integration. It has been reliable for me with the following exception:
When I upgraded the firmware of my Wallbox Pulsar Plus units from 6.6.15 to 6.8.12, using the TxProfile to steer the smart charging became unreliable and I switched to using the set_charge_rate action (service) command of the ocpp integration, which in turn sends the MaxProfile to the charger.

[kimbo1st]

Hi, I am wondering managing the current even works properly. So I have the slider and with node red I change the current depending on the solar power. But after some time it stops reacting, even the slider is on 16A, the current offered stays on 7A and also in the vendor portal it remains stuck on the 7A. This is quiet annoying and unpractical.