|
"$id": "urn:OCPP:Cp:1.6:2020:3:InstallCertificate.req", |
The backported messages from 2.0.1 to 1.6 seems to have this problem in the JSON Schema validator, any idea why? If we remove the $id and add title like in the other schemas, it works.
Here is a valid message we receive from OCTT official testing (maybe we should create an unit test for it?)
object(SolutionForest\OcppPhp\Ocpp\v16\Calls\GetLog)#2601 (7) {
["messageTypeID"]=>
int(2)
["messageId"]=>
string(10) "2575884193"
["log"]=>
object(stdClass)#2566 (3) {
["remoteLocation"]=>
string(31) "https://example-server.com/logs"
["oldestTimestamp"]=>
string(20) "2026-05-17T18:05:00Z"
["latestTimestamp"]=>
string(20) "2026-06-07T18:05:00Z"
}
["logType"]=>
string(11) "SecurityLog"
["requestId"]=>
int(8)
["retries"]=>
int(1)
["retryInterval"]=>
int(1)
}
ocpp-php/src/Ocpp/v16/Schemas/InstallCertificate.json
Line 3 in 460adab
The backported messages from 2.0.1 to 1.6 seems to have this problem in the JSON Schema validator, any idea why? If we remove the
$idand addtitlelike in the other schemas, it works.Here is a valid message we receive from OCTT official testing (maybe we should create an unit test for it?)