How to track charge point communications
Keeping track of a charge point’s communications can be invaluable for managing your operations. By filtering specific commands, such as authorisation messages or start transaction messages, you can quickly find the information you need. This ensures clarity and efficiency in your charging station management.
How to filter charge point communications
Select the charge point you want to review.
Go to the commands section.
Click on filters to open the filtering options.
Choose the method you want to search for and click apply.
You will now see all the selected commands associated with that charge point.
Commonly used OCPP methods
ChangeConfigurations
Sent from the Central System → Charger. Used to update a configuration key/value on the charging station (e.g. changing heartbeat interval, enabling smart charging, setting a metering interval). The charger responds with
Accepted,Rejected, orRebootRequired(if the change only takes effect after a reboot).
StatusNotifications
Sent from the Charger → Central System. The charger reports its current status for a connector (e.g.
Available,Charging,SuspendedEV,Faulted,Unavailable). This is how the backend knows what's happening at the charger in real time — it's purely informational, no response action is expected beyond acknowledgment.
GetConfiguration
Sent from the Central System → Charger. Used to read one or more configuration keys from the charger. If you send it without specifying a key, the charger returns all its configuration values. Useful for diagnostics — e.g. checking what firmware settings are active.
Authorize
Sent from the Charger → Central System. When a driver presents an RFID card, the charger asks the backend: "Is this card allowed to charge here?" The backend responds with
Accepted,Blocked,Expired, orInvalid. This is the core of access control — and where Access Group whitelisting comes into play.
StartTransaction
Sent from the Charger → Central System. Notifies the backend that a charging session has begun. Contains the RFID token, connector ID, meter value at start, and a timestamp. The backend responds with a transaction ID and an authorization status. This is what creates the session record in the platform.
StopTransaction
Sent from the Charger → Central System. Notifies the backend that a session has ended (either by the driver unplugging, stopping via app, or a remote stop command). Contains the final meter value, transaction ID, and reason for stopping. This is what closes the session and triggers billing.