Autel MaxiCharger - Can't modify the amp value

[Nidrachp]

Describe the bug
Type charger : Autel Maxicharger
OCPP information:
Security profile: WS
URL : homeassistant.local
Server path: /ws/webSocket?=sn
Server port: 9000

I can connect my home assistant to the charger. It is possible to switch the charger ON/OFF. Not possible to edit the amp value

I have the message: [547608280000] PropertyConstraintViolationError: When chargingProfilePurpose =ChargingStationMaxProfile, chargingProfileKind SHALL NOT be Relative, {}

Logs:

Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/commands.py:238
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 16:44:32 (2 occurrences)
Last logged: 18:02:50

[547608280000] PropertyConstraintViolationError: When chargingProfilePurpose =ChargingStationMaxProfile, chargingProfileKind SHALL NOT be Relative, {}
[547371048768] PropertyConstraintViolationError: When chargingProfilePurpose =ChargingStationMaxProfile, chargingProfileKind SHALL NOT be Relative, {}
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 238, in handle_call_service
response = await hass.services.async_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2067, in async_call
response_data = await coro
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2104, in _execute_service
return await target(service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 272, in handle_service
return await service.entity_service_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 878, in entity_service_call
single_response = await _handle_entity_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 948, in _handle_entity_call
result = await task
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/number/init.py", line 106, in async_set_value
await entity.async_set_native_value(native_value)
File "/config/custom_components/ocpp/number.py", line 127, in async_set_native_value
resp = await self.central_system.set_max_charge_rate_amps(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/ocpp/api.py", line 287, in set_max_charge_rate_amps
return await self.charge_points[cp_id].set_charge_rate(limit_amps=value)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/ocpp/api.py", line 639, in set_charge_rate
resp = await self.call(req)
^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/ocpp/charge_point.py", line 313, in call
response = await self._get_specific_response(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/ocpp/api.py", line 894, in _get_specific_response
raise resp.to_exception()
ocpp.exceptions.PropertyConstraintViolationError: PropertyConstraintViolationError: When chargingProfilePurpose =ChargingStationMaxProfile, chargingProfileKind SHALL NOT be Relative, {}

Thank you for your help.

[github-actions]

Stale issue message

[david-j-duran]

I have the same issue

[shauncraill]

Hi, is there any way to re-open this issue and see if we can resolve it? I can assist by any means, I have a charger available and set up to get the current adjustment working

[shauncraill]

I'm still busy with a lot of back and forth emails with Autel, it seems like the issue is they aren't complying to OCPP 100%. They now want to send me a custom OCPP profile for the specific charge current I want to charge with, then I need to apply a different profile each time I want to adjust charge current.

Obviously updating firmware each time you want to adjust current does not make any sense. I will keep this thread updated in the next week about a possible solution. Otherwise I am returning the Autec and installing a Wallox Pulsar

[PeterMikeSmooth]

Hi there,

I'm getting the same issue on my Autel MaxiCharger :
Failed to perform the action number/set_value. PropertyConstraintViolationError: When chargingProfilePurpose =ChargingStationMaxProfile, chargingProfileKind SHALL NOT be Relative, {}

@lbbrhzn would it possible that Autel MaxiCharger just does not support "Relative" chargingProfileKind ?
I would like to try with "Absolute" chargingProfileKind but I don't see that definition anywhere in the HA OCPP code :

~/projects/HA/ocpp$ grep -ri ChargingProfileKindType custom_components/ocpp/ocppv16.py: ChargingProfileKindType, custom_components/ocpp/ocppv16.py: om.charging_profile_kind.value: ChargingProfileKindType.relative.value, custom_components/ocpp/ocppv16.py: om.charging_profile_kind.value: ChargingProfileKindType.relative.value, custom_components/ocpp/ocppv201.py: ChargingProfileKindType, custom_components/ocpp/ocppv201.py: "charging_profile_kind": ChargingProfileKindType.relative.value, tests/test_charge_point_v201.py: ChargingProfileKindType, tests/test_charge_point_v201.py: "charging_profile_kind": ChargingProfileKindType.relative.value, tests/test_charge_point_v201.py: "charging_profile_kind": ChargingProfileKindType.relative.value, tests/test_charge_point_v201.py: "charging_profile_kind": ChargingProfileKindType.relative.value, tests/test_charge_point_v201.py: "charging_profile_kind": ChargingProfileKindType.relative.value,

Any recommandation to make a test with "Absolute" ?

Thank you !

[shauncraill]

So I have spoken to some important people in South Africa. Autel doesn't look like they intend to add OCPP compatibility fully. They just don't care about it!

However, the Autel range supports ModbusTCP. I've started with the integration, still busy to get it all running, should have it done in the next while.

[PeterMikeSmooth]

However, the Autel range supports ModbusTCP.

I tried ModbusTCP, MaxiCharger does answer to just a few registers ...

`:mbpoll -m tcp -r 1 -c 5 192.168.1.33
[1]: 0
[2]: 1
[3]: 100
[4]: 1
[5]: 1

mbpoll -m tcp -r 20001 -c 10 192.168.1.33
[20001]: 0
[20002]: 22000
[20003]: 0
[20004]: 3200
[20005]: 0
[20006]: 22000
[20007]: 0
[20008]: 3200
[20009]: 0
[20010]: 0

mbpoll -m tcp -r 21001 -c 10 192.168.1.33
[21001]: 0
[21002]: 22000
[21003]: 0
[21004]: 3200
[21005]: 0
[21006]: 22000
[21007]: 0
[21008]: 3200
[21009]: 0
[21010]: 0`

And not the one to tune max charging amps. Let us know if you succeed doing something ...