8jmm3
commented
8 months ago If it's of any use to anyone analyzing the behaviour, here is some pseudocode showing how the v2 units responds to a GetConfiguration message:
void handle_ocpp_get_configuration_req_msg(void *pJSON)
{
void* pItem;
int nItemCount = 0;
if (cJSON_HasObjectItem(pJSON, "key"))
{
pItem = cJSON_GetObjectItem(pJSON, "key");
nItemCount = cJSON_GetArraySize(pItem);
}
char szConfigKey[];
szConfigKey[0] = '\0';
sprintf(szConfigKey, "\"configurationKey\":[");
char szUnknownKey[];
szUnknownKey[0] = '\0';
sprintf(szUnknownKey, "\"unknownKey\":[");
char szPayloadItem[];
int nValidItemCount = 0;
for (int i = 0; i < nItemCount; ++i)
{
char* pszValue = cJSON_GetStringValue(cJSON_GetArrayItem(pItem, i));
nValidItemCount++;
if (strcmp(pszValue, "MaxCurrent") == 0)
{
sprintf(szPayloadItem, "{\"key\":\"MaxCurrent\",\"readonly\":true,\"value\":%d},", get_evse_max_current());
strcat(szConfigKey, szPayloadItem);
}
else if (strcmp(pszValue, "MinCurrent") == 0)
{
...
}
else if (strcmp(pszValue, "SetCurrent") == 0)
{
...
}
else if (strcmp(pszValue, "StartChargingAfterConnect") == 0)
{
sprintf(szPayloadItem, "{\"key\":\"StartChargingAfterConnect\",\"readonly\":false,\"value\":\"%s\"},", chargeAfterConnectFlag ? "true" : "false");
strcat(szConfigKey, szPayloadItem);
}
else if (strcmp(pszValue, "AuthorizeRemoteTxRequests") == 0)
{
sprintf(szPayloadItem, "{\"key\":\"AuthorizeRemoteTxRequests\",\"readonly\":false,\"value\":\"%s\"},", authorizeRemoteTxRequestFlag ? "true" : "false");
strcat(szConfigKey, szPayloadItem);
}
else if (strcmp(pszValue, "ConnectorPhaseRotation") == 0)
{
sprintf(szPayloadItem, "{\"key\":\"ConnectorPhaseRotation\",\"readonly\":true,\"value\":\"NotApplicable\"},");
strcat(szConfigKey, szPayloadItem);
}
else if (strcmp(pszValue, "HeartbeatInterval") == 0)
{
sprintf(szPayloadItem, "{\"key\":\"HeartbeatInterval\",\"readonly\":false,\"value\":\"%d\"},", heartbeatInterval);
strcat(szConfigKey, szPayloadItem);
}
else if (strcmp(pszValue, "LocalAuthorizeOffline") == 0)
{
...
}
else if (strcmp(pszValue, "LocalPreAuthorize") == 0)
{
...
}
else if (strcmp(pszValue, "MeterValueSampleInterval") == 0)
{
...
}
else if (strcmp(pszValue, "NumberOfConnectors") == 0)
{
...
}
else if (strcmp(pszValue, "ResetRetries") == 0)
{
sprintf(szPayloadItem, "{\"key\":\"ResetRetries\",\"readonly\":true,\"value\":\"1\"},");
strcat(szConfigKey, szPayloadItem);
}
else if (strcmp(pszValue, "StopTransactionOnInvalid") == 0)
{
...
}
else if (strcmp(pszValue, "SupportedFeatureProfiles") == 0)
{
sprintf(szPayloadItem, "{\"key\":\"SupportedFeatureProfiles\",\"readonly\":true,\"value\":\"Core,FirmwareManagement\"},");
strcat(szConfigKey, szPayloadItem);
}
else if (strcmp(pszValue, "UnlockConnectorOnEVSideDisconnect") == 0)
{
...
}
else if (strcmp(pszValue, "StationPassword") == 0)
{
sprintf(szPayloadItem, "{\"key\":\"StationPassword\",\"readonly\":false,\"value\":\"%s\"},", get_station_password());
strcat(szConfigKey, szPayloadItem);
}
else if (strcmp(pszValue, "ServerUrl") == 0)
{
sprintf(szPayloadItem, "{\"key\":\"ServerUrl\",\"readonly\":false,\"value\":\"%s\"},", get_ocpp_server_url());
strcat(szConfigKey, szPayloadItem);
}
else
{
sprintf(szPayloadItem, "\"%s\"", pszValue);
strcat(szUnknownKey, szPayloadItem);
nValidItemCount--;
}
}
strcat(szConfigKey, "]");
strcat(szUnknownKey, "]");
char szJSONPayload[];
if (nValidItemCount == nItemCount)
{
sprintf(szJSONPayload, "{%s}", szConfigKey);
}
else
{
sprintf(szJSONPayload, "{%s,%s}", szConfigKey, szUnknownKey);
}
send_ocpp_response("GetConfiguration", szJSONPayload);
}
emlynmac
djiesr
github-actions[bot]
Describe the bug
Grizzl-e Smart v2 does not work with the OCPP integration version 0.4.40
Firmware WiFi Module: GWM-07.013-03
Firmware Power Board: GCW-10.18-05.7
To Reproduce
Upon configuring the Grizzl-e, it connects and has the following errors in the HA logs:
Additional context
With websockets debug added.