OCPP 1.6 compliance

[pit]

Hi.

Teltocharge device is not fully compliant with the OCPP 1.6 protocol.

According to OCPP 1.6 Specification, Part 2, Section 6.10, the field chargingRateUnit in ChargingSchedule type has cardinality 1..1 (Mandatory). Your device response to GetCompositeSchedule is missing this field, causing schema validation errors in strict OCPP backends. Please fix this.

Sample log file from evcc:

[ocpp ] ERROR 2026/02/03 13:47:02 ocpp message (123276127): OccurenceConstraintViolation - Field CallResult.Payload.ChargingSchedule.ChargingRateUnit required but not found for feature GetCompositeSchedule ([3,"123276127",{"status":"Accepted","connectorId":1,"scheduleStart":"2026-02-03T12:47:01Z","chargingSchedule":{"duration":60,"startSchedule":"2026-02-03T12:47:01Z","chargingSchedulePeriod":[{"startPeriod":0,"limit":0,"numberPhases":3}]}}])

[Dominic]

@pit

[ocpp ] ERROR 2026/02/03 13:47:02 ocpp message (123276127): OccurenceConstraintViolation - Field CallResult.Payload.ChargingSchedule.ChargingRateUnit required but not found for feature GetCompositeSchedule ([3,"123276127",{"status":"Accepted","connectorId":1,"scheduleStart":"2026-02-03T12:47:01Z","chargingSchedule":{"duration":60,"startSchedule":"2026-02-03T12:47:01Z","chargingSchedulePeriod":[{"startPeriod":0,"limit":0,"numberPhases":3}]}}])

Hello,

Thank you for reaching out to us. I created internal ticket to our engineer to continue from here. I will get back to you with more information as soon as I get updated on this inquiry. Also, my apologies about the issue that you experienced with our system.

Sincerely,

Dominic