Different stations expose different measurands in MeterValue message despite same configuration

[eric-official]

Hello,
I'm currently testing my custom OCPP websocket server against the SAP OCPP simulator. Hereby, I'm testing different config templates of stations. One thing that caught my attention is the divergent availability of measurands in the MeterValues message despite the same configuration. The two measurands that I always want to include in the MeterValues message are Energy.Active.Import.Register and Current.Import. For example, the Siemens station includes both measurands in the MeterValues message. However, the ABB_ATG box doesn't include Energy.Active.Import.Register, the ABB box doesn't include Current.Import, and the EVLink box reports the Current.Import with a single value instead of one value per phase. My station config templates always look something like that for including the measurands Energy.Active.Import.Register and Current.Import:

{
"idTagsFile": "idtags.json",
"baseName": "DE130E417f68d801",
"fixedName": true,
"chargePointModel": "SIEMENSXX213",
"chargePointVendor": "SIEMENS",
"power": 44160,
"powerUnit": "W",
"numberOfConnectors": 1,
"randomConnectors": false,
"voltageOut": 240,
"Configuration": {
"configurationKey": [
{
"key": "MeterValuesSampledData",
"readonly": false,
"value": "Energy.Active.Import.Register,Current.Import"
},
{
"key": "MeterValueSampleInterval",
"readonly": false,
"value": "30"
},
{
"key": "SupportedFeatureProfiles",
"readonly": true,
"value": "Core,LocalAuthListManagement,Reservation"
},
{
"key": "LocalAuthListEnabled",
"readonly": false,
"value": "false"
},
{
"key": "AuthorizeRemoteTxRequests",
"readonly": false,
"value": "false"
},
{
"key": "WebSocketPingInterval",
"readonly": false,
"value": "60"
},
{
"key": "ReserveConnectorZeroSupported",
"readonly": false,
"value": "false"
}
]
},
"AutomaticTransactionGenerator": {
"enable": false,
"minDuration": 300,
"maxDuration": 900,
"minDelayBetweenTwoTransactions": 15,
"maxDelayBetweenTwoTransactions": 30,
"probabilityOfStart": 1,
"stopAfterHours": 0,
"requireAuthorize": false
},
"Connectors": {
"0": {},
"1": {
"bootStatus": "Available",
"MeterValues": [
{
"unit": "Wh",
"context": "Sample.Periodic",
"measurand": "Energy.Active.Import.Register"
},
{
"context": "Sample.Periodic",
"measurand": "Current.Import",
"unit": "A",
"minimum": 6.0
}
]
}
}
}

Is this behavior expected or a bug? Does anybody else encounter the same behavior?

BR Eric