OCPP 1.7.4
about 1 year ago by Valeriia Morozova
- Improved resource management for WebSocket connections by disposing a connection before creating a new one. (2023-11-06)
- Improved the transaction retry mechanism by removing duplicate checks and by starting timeout count down after message is sent via WebSocket. Previously, transactional messages timed-out and retried after a fixed period of 2 minutes. Then, the value of
TransactionMessageRetryInterval
from configuration was used to determine timeout. With this improvement, only the values ofTransactionMessageRetryInterval
andTransactionMessageAttempts
are used for retries. (2023-11-06) - Added retry mechanism to offline transactions. (2023-11-06)
- Removed bounce back delay on chargers going online. Charger will be displayed as online within few minutes upon establishing successful WebSocket connection. Previously, there was a delay of 15 minutes or more. (2024-03-05)
- Added additional internal error codes to StatusNotification VendorErrorCode property. If you get these, please contact our partner integration team to get explanation. (2024-06-05)
- Added support for chargers running on local ocpp, so that operator can use both cloud and local solutions under the same registration. (2024-06-05)
- Added support for Charge Max, which as a MID compliant charging device signs charging sessions and submits the signatures for end user verification. The signature is included in StopTransaction request message as additional MeterValue item in transactionData property (2024-09-18)