drc38

See how you get on with the latest release

See https://github.com/lbbrhzn/ocpp/pull/506 for instructions noting the secure option has not been tested and may not work.

Adding an options flow to achieve this will be quite a bit of work. Personally I don't have the need for it, but happy to review a PR if someone...

Suggest sending the log to the manufacturer and raising a ticket. It is not responding to the Ocpp standard when sent `[2,"f6ee754e-9506-4d5c-a546-4e845c97c9e3","GetConfiguration",{"key":["SupportedFeatureProfiles"]}]`

You can comment out `await self.get_supported_features()` in `post_connect`. You may have to comment out other `get_configuration` lines as well as their response to an unsupported key is not Ocpp compliant.

_If the list of keys in the request PDU is empty or missing (it is optional), the Charge Point SHALL return a list of all configuration settings in GetConfiguration.conf. Otherwise...

You'd need to do some research but I think the ocpp1.6 schema still requires it to be passed in json as a string. Validation of messages is not part of...

They need to be using the official schemas eg for GetConfigurationResponse.json: ``` { "$schema": "http://json-schema.org/draft-04/schema#", "id": "urn:OCPP:1.6:2019:12:GetConfigurationResponse", "title": "GetConfigurationResponse", "type": "object", "properties": { "configurationKey": { "type": "array", "items": { "type":...

It is a websocket standard to respond to a ping with a pong. The fact it does not support WebSocketPingInterval should not matter. Is your wifi connection rssi solid?

See https://www.rfc-editor.org/rfc/rfc6455#section-5.5.2 replying with a pong is not optional. If you want to disable you would need to create a patch for the function `monitor_connection` eg skip pinging if interval...