When creating an OCPP connection URL for a charging station within the Zaptec Portal, the URL connection must include the charge point identity. This allows the Central Server to associate each WebSocket connection with the correct charge point, in line with the OCPP standard.
Legacy OCPP behaviour
Previously, Zaptec overwritten this logic and instead used the Zaptec DeviceID as the charge point identity sent to the Central Server.
- Example:
Connecting to charger ZAP123XYZ and setting your OCPP server URL as in the old Zaptec Portal would have sent that charger identity as: zap123XYZ
This is referred to as legacy OCPP behavior in the Zaptec Portal and remains the default for installations set up before recent updates.
OCPP 1.6J behaviour
Going forward, we will be configuring new Installations following the OCPP standard.
- Example:
In the OCPP standard, a charger's unique identifier should now follow the format: NewDeviceNameZAP
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 behavior
To switch between this change, navigate to the Zaptec Installation you wish to configure and select the Authentication settings. 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.