OcppBridge Changelog
π
2025-03-19
β¨ New Feature
- Trigger
BootNotification
via TriggerMessage- Dynamic Heartbeat control enabled:
TheTriggerMessage
command has been extended to support triggering aBootNotification
message from the charger. This can be used to apply configuration changes such as updates to theHeartbeat
interval. - π Firmware Required: No
- βοΈ Behavior on Older Firmware:
- Fully supported β no update required.
- Dynamic Heartbeat control enabled:
π
2025-02-26
β¨ New Feature
- Trigger
Heartbeat
via TriggerMessage- Extended
TriggerMessage
functionality:
TheTriggerMessage
command now supports triggering aHeartbeat
message from the charger, enabling remote status checks. - π Firmware Required: No
- βοΈ Behavior on Older Firmware:
- Fully supported β no update required.
- Extended
π
2024-12-02
β¨ New Feature
MeterValuesSampledData
in GetConfiguration- Read-only visibility into sampled data configuration:
TheGetConfiguration
command now includes theMeterValuesSampledData
key. This key is marked as read-only and provides insight into the sampling configuration. - π Firmware Required: No
- βοΈ Behavior on Older Firmware:
- Fully supported β no update required.
- Read-only visibility into sampled data configuration:
β¨ New Feature
- Configurable
ConnectionTimeOut
-
Editable timeout configuration with firmware update:
TheConnectionTimeOut
key has been added to bothGetConfiguration
andChangeConfiguration
commands.- With updated firmware, the key is read/write, allowing full configuration.
- Without firmware update, only
GetConfiguration
is available and returns a fixed value of 10 seconds.
-
π Firmware Required: Yes
-
β‘οΈ Minimum Pro Firmware:
>=5.3.0.15
-
βοΈ Behavior on Older Firmware:
- The
ConnectionTimeOut
key is read-only and fixed at 10 seconds.
- The
-
π
2024-10-22
β¨ New Feature
- Public Key via GetConfiguration (Eichrecht Only)
- Expose charger public key for Eichrecht-compliant chargers:
TheGetConfiguration
command now returns the charger's public key using theconfigurationKey
MeterPublicKey1
. This feature is only available on chargers that are Eichrecht compliant. - π Firmware Required: Yes
- β‘οΈ Minimum Pro Firmware:
>=6.0.0.0
- βοΈ Behavior on Older Firmware:
- The public key will not be returned.
- Expose charger public key for Eichrecht-compliant chargers:
π
2024-10-10
β¨ New Feature
- Eichrecht Configuration Keys in GetConfiguration
- Support for advanced signature configuration:
TheGetConfiguration
command now returns six new keys for Eichrecht-compliant chargers:StopTransactionSignatureFormat
,SampledDataSignReadings
,AlignedDataSignReadings
,SampledDataSignStartReadings
,AlignedDataSignUpdatedReadings
, andSampledDataSignUpdatedReadings
. - π Firmware Required: Yes
- β‘οΈ Minimum Pro Firmware:
>=6.0.0.0
- βοΈ Behavior on Older Firmware:
- Not applicable β these keys are only available on supported Eichrecht-compliant chargers.
- Support for advanced signature configuration:
π
2024-08-20
π§ Improvement
- Improved Soft Reset Behavior
- Standards-compliant message handling:
The Soft Reset process has been improved for Pro chargers. OcppBridge now ensures the correct sequence of statuses and messages, fully aligned with the OCPP 1.6 standard. - π Firmware Required: Yes
- β‘οΈ Minimum Pro Firmware:
>=5.3.0.15
- βοΈ Behavior on Older Firmware:
- Statuses and messages may arrive in the wrong order.
- Standards-compliant message handling:
π§ Improvement
- Improved Unlock Functionality
- OCPP-compliant unlock behavior:
Unlock operations now follow the OCPP 1.6 standard, ensuring more reliable and predictable behavior for Pro chargers. - π Firmware Required: Yes
- β‘οΈ Minimum Pro Firmware:
>=5.2.4.3
- βοΈ Behavior on Older Firmware:
- Statuses and messages may arrive in the wrong order.
- OCPP-compliant unlock behavior:
π
2024-08-05
β¨ New Feature
- OCPP TriggerMessage Support
- TriggerMessage Command (OCPP):
You can now remotely trigger specific messages from the charging station to the central system using the OCPPTriggerMessage
command. π Read more with examples
- TriggerMessage Command (OCPP):
π
2024-07-18
β¨ New Feature
- Trigger
MeterValues
via TriggerMessage- Extended
TriggerMessage
support:TheTriggerMessage
command now allows triggering aMeterValues
message from the charger, enabling more flexible data collection. - π Firmware Required: No
- βοΈ Behavior on Older Firmware:
- Fully supported β no update required.
- Extended
π§ Improvement
- Aligned Meter Values Timestamps
- Improved timestamp accuracy in
MeterValues
:OcppBridge now aligns meter values timestamps using the last reading timestamp, ensuring accurate reporting.
Previously, the timestamp used was the last changed timestamp, which could lead to inconsistencies. - π Firmware Required: No
- βοΈ Behavior on Older Firmware:
- Fully supported β no update required.
- Improved timestamp accuracy in
π
2023-09-25
β¨ New Feature
- Charger Identity Support
- Charger Identity via OCPP:
The platform now supports sending charger identity as per OCPP standards. π Details and Zaptec legacy behavior
- Charger Identity via OCPP:
π
2023-06-06
π Bug Fix
- ChangeAvailability Handling
- ChangeAvailability Handling:
Fixed a bug related to how Zaptec OCPP handled theChangeAvailability
command.
- ChangeAvailability Handling:
π
2023-03-01
β¨ New Feature
- Reservation Profile Support
- OCPP Reservation Feature Profile:
Zaptec now supports the Reservation profile in OCPP. π More details
- OCPP Reservation Feature Profile: