OCPP 1.7.4
12 months 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 (2024-09-18)
Refresh Token Handling
about 1 year ago by Leon Mwazange
To cover a potential security issue, we are updating our authentication/authorization services to correctly handle refresh tokens.
This change, will likely cause issues with integrations that have cached refresh tokens.
Because this is an area that can be exploited we urge any integration operator/partner using our APIs to use standard practice and request a new refresh token, and implement fall back logic if they fail to obtain valid tokens.
OCPP 1.5
about 3 years ago by Maryam Farzad
OCPP version 1.5 requires firmware ≥276 to function properly
Free charging requires firmware ≥300