Zaptec legacy OCPP behaviour



When creating an OCPP connection URL for a charging station within the Zaptec Portal, according to the OCPP standard, the connection URL needs to contain the charge point identity so that the Central Server knows which charge point a WebSocket connection belongs to.

Zaptec had previously overwritten this logic and instead used the Zaptec DeviceID as the identity for the Central Server.

Example: Connecting to charger ZAP123XYZ and setting your OCPP server URL as  in the old Zaptec Portal would have sent that chargers identity as


This is referred to in the Zaptec Portal as legacy OCPP behaviour. Any installations set up previously will have this behaviour as standard.


OCPP 1.6J behaviour

Going forward, we will be configuring up new Installations following the OCPP standard.

In the OCPP standard, this charge points unique identifier should be 


With the latest changes in the Zaptec Portal, we now allow the option for switching between Zaptec legacy OCPP behaviour and the OCPP standard behaviour.



Activating and deactivating legacy behaviour

To switch between this change, navigate to the Zaptec Installation you wish to configure and select the Authentication settings.

Screenshot 2023-09-04 at 13.13.47.png

You will now see a toggle for 'Use legacy OCPP behaviour' - this should remain disabled if you wish to follow the OCPP 1.6 J standard. 


Was this article helpful?
0 out of 0 found this helpful