Sigenergy ACEV charger - identifying controls

[alexeiw123]

Hi All,

The sigenergy ACEV charger was launched with OCPP support, but no ability to assign an OCPP server address.

The sig dev team have configured my HA OCPP server address remotely prior to giving (other) end users access to assign their own server.

My charger is successfully connected but having never dived in to the world of OCPP, I'm seeking some advice on how to explore and test functionality. I've been able to start charge sessions. A few times it let me top the session but mostly that doesn't work. I tried to use the actions to change the charge current, but I probably stuffed up the syntax somehow.

Really just looking for a hand so that we can work out what level of functionality is accessible and get it added as a supported device.

E.g. - the charger has the capability to switch between 1ph and 3ph, but not sure if that is exposed to OCPP.

https://www.sigenergy.com/au/products/ac-charger

[alexeiw123]

e.g. I am able to start charging but can't stop it. From my logs:

ocpp.exceptions.TypeConstraintViolationError: TypeConstraintViolationError: Payload for Action is syntactically correct but at least one of the fields violates data type constraints (e.g. “somestring”: 12), {'cause': "'MBEPHQRN1V9B99XXIMZ5-' is too long", 'ocpp_message': <Call - unique_id=429, action=StopTransaction, payload={'meterStop': 1093780, 'timestamp': '2025-08-19T11:45:29Z', 'transactionId': 1755603896, 'idTag': 'MBEPHQRN1V9B99XXIMZ5-'}>}

[drc38]

Looks like there maybe an issue with your charger firmware, it is appending "-" to the id_tag of "MBEPHQRN1V9B99XXIMZ5" causing the violation.

The docs explaining how ocpp works are here: https://github.com/mobilityhouse/ocpp/tree/master/docs/v16

[drc38]

As a workaround you could change this line to a range of 19

ocpp/custom_components/ocpp/chargepoint.py

Line 199 in e4d587c

self._remote_id_tag = "".join(secrets.choice(alphabet) for i in range(20))

[alexeiw123]

As a workaround you could change this line to a range of 19

Thankyou - I tried this and still saw the same behaviour. With limited time to debug and understand this, I reverted the change for now.

Sigen just released the OCPP option to public yesterday, so I assume others will assist and also provide Sigen with feedback where they need to update support.

[anthrox]

Hello I also have this charger EVAC 22 4G T2 WH i get a lot of data from the OCPP but the SoC sensor doesnt seem to be working currently

i have found this document from September 2025 that outlines there current supported features ill email sigenergy see if they have a update document

Technical Note - OCPP Connection Configuration (note this is a direct link to the vendor PDF file)
this document outlines there support on there AC and DC chargers
https://www.sigenergy.com/en/support/files/2253

[alexeiw123]

Great to hear someone else using this - after the above I've left mine in the sig mode until I get some time to properly investigate controlling with OCPP. Unfortunately when I looked prior starting and stopping charging was very unreliable and proper implementation is a bit beyond my skillset without investing a lot of time.

The issue for me is that sigs PV surplus charging is really really bad in winter, but in summer, I have an energy surplus, so it hasn't been an issue. I expect this will become important again come winter!

How are you finding it other than lock of SoC information? I assume that would require the vehicle to provide SoC as well as the sig charger to be compliant for reporting it via OCPP?