v0.17.0
Pre-release
Pre-release
Additions and improvements
v1.6
- Added the
IsConnectedgetter to charge point instances
v2.0.1
- Added the
IsConnectedgetter to charging station instances SampleValue.Valuefield is not required anymore- Added the missing
CertificateHashDataChainoptional field in GetInstalledCertificateIds response - Added the missing
V2GCertificateChainCertificateUse enum value - Added the missing
ISO15693andMacAddressenum values of IdTokenType
Websocket
- The default subprotocol is now set correctly during initial negotiation and may be enforced via the
SetRequestedSubProtocolon the websocket client - The server now supports adding additional HTTP handlers, via an underlying router
Generic
- Upgraded lib to min Go version 1.16
- Upgraded some dependencies
- Message callbacks are now invoked within dedicated goroutines to prevent the called from being blocked
- Added debug logs for outgoing/incoming raw JSON messages
- Added support for HTML escaping
- Added the
SetNewChargingStationValidationHandleron server endpoints for checking incoming connections before the websocket upgrade takes place - Improved error handling when sending responses/errors
- Added optional
SetInvalidMessageHookhandler to intercept and handle invalid messages on ocppj layer
Bugfixes
v1.6
stopTimeparameter in GetDiagnosticsRequest is now named correctlyChargingProfileStatusNotSupportedvalue in SetChargingProfile messageClearChargingProfileStatusvalidation in ClearChargingProfile confirmationConfigurationKeyvalidation in GetConfiguration message- Several validation keys are not overwritten by the v2.0.1 package anymore due to name duplication
v2.0.1
idTokentype- Removed incorrect validation for
idTokenin RequestTransaction request AttributeStatusvalidation in SetVariables responsemessagesInQueuejson field in GetTransactionStatus responsecertificateTypefield in GetInstalledCertificateIds request- Update
FormatViolationocpp-j error type SerialNumberupdated to max length 40 in CertificateHashData and OCSPRequestDataType
Generic
- Incoming ocpp-j errors with empty details field are now parsed correctly
- Invalid ocpp-j message types are now parsed and handled correctly
- Fixed deadlock caused by double invocation on
client.Stop