Wallbox Pulsar Plus

[kimbo1st]

Recently started to use OCPP on my Wallbox Pulsar Plus. Via a Node Red steering, I charge the car dynamically depanding on the PV. What I notice, since I started to use it, that the current stops following after some time and becomes stale.

Checking the logs I see the following:

Logger: custom_components.ocpp
Bron: custom_components/ocpp/number.py:240
integratie: Open Charge Point Protocol (OCPP) (documentatie, problemen)
Eerst voorgekomen: 11:41:41 (1 gebeurtenis)
Laatst gelogd: 11:41:41
Set current limit rejected by CP (kept optimistic UI at 13.0 A).

Logger: ocpp
Bron: custom_components/ocpp/chargepoint.py:466
integratie: Open Charge Point Protocol (OCPP) (documentatie, problemen)
Eerst voorgekomen: 11:53:00 (6 gebeurtenissen)
Laatst gelogd: 12:08:17
Ignoring response with unknown unique id: <CallResult - unique_id=a00a3102-52e2-4a59-a2db-2d6519688b37, action=None, payload={'status': 'Accepted'}>
Ignoring response with unknown unique id: <CallResult - unique_id=61d6fc3b-372b-4ed3-bc8c-1ad562be7a00, action=None, payload={'unknownKey': [], 'configurationKey': [{'readonly': True, 'key': 'ChargeProfileMaxStackLevel', 'value': '10'}]}>
Ignoring response with unknown unique id: <CallResult - unique_id=bc0614ed-cda5-4ace-940b-0606518eff6f, action=None, payload={'status': 'Accepted'}>
Ignoring response with unknown unique id: <CallResult - unique_id=12a2d1c7-d1dd-481e-86b8-bb93fc6bcf3e, action=None, payload={'status': 'Accepted'}>
Ignoring response with unknown unique id: <CallResult - unique_id=6ff67ea4-e42c-4846-b986-503eecd64344, action=None, payload={'unknownKey': [], 'configurationKey': [{'readonly': True, 'key': 'ChargingScheduleAllowedChargingRateUnit', 'value': 'Current'}]}>

Logger: custom_components.ocpp
Bron: custom_components/ocpp/number.py:245
integratie: Open Charge Point Protocol (OCPP) (documentatie, problemen)
Eerst voorgekomen: 11:40:20 (20 gebeurtenissen)
Laatst gelogd: 12:10:54
Set current limit failed: Waited 10s for response on [2,"cc8643d8-f65e-4861-a96f-989cf4065c9c","GetConfiguration",{"key":["ChargingScheduleAllowedChargingRateUnit"]}]. (kept optimistic UI at 9.0 A).
Set current limit failed: Waited 10s for response on [2,"33a0d800-bc70-4364-b4ed-8e46329f8ccc","GetConfiguration",{"key":["ChargingScheduleAllowedChargingRateUnit"]}]. (kept optimistic UI at 12.0 A).
Set current limit failed: Waited 10s for response on [2,"cb271927-711c-4a42-8312-b3bfea32b672","GetConfiguration",{"key":["ChargingScheduleAllowedChargingRateUnit"]}]. (kept optimistic UI at 13.0 A).
Set current limit failed: Waited 10s for response on [2,"6ff67ea4-e42c-4846-b986-503eecd64344","GetConfiguration",{"key":["ChargingScheduleAllowedChargingRateUnit"]}]. (kept optimistic UI at 15.0 A).
Set current limit failed: Waited 10s for response on [2,"ee515d98-b4b2-4395-90eb-a06186e12f70","GetConfiguration",{"key":["ChargingScheduleAllowedChargingRateUnit"]}]. (kept optimistic UI at 15.0 A).

When I change the current limit in the Wallbox portal, it reflects right away in HA... so communication seems to be working fine.

Is this the way the system has been designed that you set a max current once in a session and then it stays like that?
Although it increased from 9 - 16A in the beginning of the session without any issue.

Hope this can be solved because otherwise I need to find out an other solution to sear dynamically.