StatusNotification - Timestamp invalid format

[rustik666]

StatusNotification- Timestamp invalid format

Details

We recieve the next paylod for StatusNotification

[2,"658ae207-02ad-4051-8ecb-51d90e8bbf21","StatusNotification",{"connectorId":2,"errorCode":"NoError","status":"Preparing","timestamp":"2024-04-26T14:35:02+02"}]

2024-04-26T14:35:02+02 isn't valid RFC3339 format which we would expect to receive according to OCPP specification.

[BrianEstrada]

Hey thanks for the report @rustik666 sorry for the long response time, I'll take a look into this now

[BrianEstrada]

@rustik666 I wasn't able to find anywhere in the documentation a mention of RFC3339

I only found this section which mentions ISO 8601 which is what we are following right now

[nick-jones]

Implementations MUST use ISO 8601 date time notation. Message receivers must be able to handle fractional seconds and time zone offsets (another implementation might use them).

Unfortunately this is at odds with the published JSON schema, as the date-time format is specified in many places, and JSON schema requires this to be RFC 3339 - https://json-schema.org/draft-04/draft-fge-json-schema-validation-00#rfc.section.7.3.1

[BrianEstrada]

@nick-jones I'll see if I can reach out to some people at the OCA to see why the discrepancy but in our experience as a CPMS many charge points are sending values to us using Offsets

[nick-jones]

@BrianEstrada That's been our experience too. That said, we've had quite a number of cases where charge points have been non-compliant to the schema in other ways, so I wouldn't necessarily use that as a notion of correctness. The OCPP 2.0.1 and 2.1 draft specs now state:

All time values exchanged between CSMS and Charging Station SHALL be formatted as defined in [RFC3339].

... so I think it's fair to assume this was understood to be an issue and corrected.

This isn't really a hill to die on, but yeah, the main problem with not using RFC 3339 here is that any CSMS that decides to validate payloads against the published schema are going to end up rejecting these messages from the emulator.

I'd be interested to hear what the OCA opinion is on this 👍

[BrianEstrada]

@nick-jones some nice insights thank you for sharing 😃 I think this is enough to convince me to change it in the emulator but I'll still bring it up at the OCA and report back here

[Trevodorax]

Hi ! Any news on this ?

I am facing this issue right now, and it also happens in the StartTransaction request.

I could offer a fix, if I did would it get accepted ?