Sevr X2 - charge power over-reporting

Smart Chargers
1

Hi,

I had a Sevr X2 EVSE installed last week, which is advertised as being OCCP 1.6J compliant.

I know that it’s not officially supported, so I first connected it to the ChargeHQ test server and ran the tests and all seemed to work.

It’s working well insofar as control goes, but something is going awry between the EVSE and ChargeHQ in terms of reporting the active power.

My car supports up to 11 kW 3-phase charging and, after inversion losses, shows 9.8 or 9.9 kW flowing to the battery.

At the same time ChargeHQ thinks that the X2 is pushing about a megawatt to the car, with almost all of that drawn from the grid.

It’s no issue when I charge at full power (I have a schedule set for the 3 hours a day when I have free power from the grid), but it’s then not working when it’s meant to be tracking my solar, even when I have ample generation.

My PV generation and consumption data appears to be coming across correctly.

IMG_1133
IMG_11331179×2556 168 KB

Has anyone come across this sort of issue before?

If this forum is monitored by ChargeHQ staff, is there anyone who can look at the OCPP logs to see where it’s going wrong?

Thanks.

2

Hi. The logs show that the charger is misreporting the power value. Notice the massive Power.Active.Import value:

{
   "connectorId":1,
   "transactionId":1753951830,
   "meterValue":[
      {
         "timestamp":"2025-08-05T03:50:13Z",
         "sampledValue":[
            {
               "measurand":"Voltage",
               "context":"Sample.Periodic",
               "phase":"L1",
               "unit":"V",
               "value":"245.07"
            },
            {
               "measurand":"Voltage",
               "context":"Sample.Periodic",
               "phase":"L2",
               "unit":"V",
               "value":"242.53"
            },
            {
               "measurand":"Voltage",
               "context":"Sample.Periodic",
               "phase":"L3",
               "unit":"V",
               "value":"243.92"
            },
            {
               "measurand":"Current.Import",
               "context":"Sample.Periodic",
               "phase":"L1",
               "unit":"A",
               "value":"13.91"
            },
            {
               "measurand":"Current.Import",
               "context":"Sample.Periodic",
               "phase":"L2",
               "unit":"A",
               "value":"14.18"
            },
            {
               "measurand":"Current.Import",
               "context":"Sample.Periodic",
               "phase":"L3",
               "unit":"A",
               "value":"14.08"
            },
            {
               "measurand":"Power.Active.Import",
               "context":"Sample.Periodic",
               "unit":"W",
               "value":"1028803"
            },
            {
               "measurand":"Energy.Active.Import.Register",
               "context":"Sample.Periodic",
               "unit":"Wh",
               "value":"38"
            },
            {
               "measurand":"Current.Offered",
               "context":"Sample.Periodic",
               "unit":"A",
               "value":"32"
            }
         ]
      }
   ]
}
3

Thank you. I wonder where it comes up with that figure.

I note that the voltage and current figures for each phase appear to be correct.

As an end user, I obviously have no way of altering the firmware on the EVSE. I’m pretty sure that Sevr just buys the unit as a white-label item from Joint Tech in China, and haven’t found any firmware updates online.

Would it be possible on ChargeHQ’s end to ignore that ridiculous value and just calculate the sum of of the three phases’ voltage * current values?

It appears that your system also relies on this value to calculate the grid import, rather than relying on the data from the PV system.

I’d be happy to help with coding if that’s a possibility. I’m a barrister these days, but was a software engineer in a past life.

4

Hi @prv2b57d42. Thanks for the offer to assist. In general we don’t add special case code to work around bugs in particular chargers, except in rare circumstances where it is justified.

I’m afraid your best option is probably to contact the distributer of the charger, who may have contacts with the OEM who writes the software. You could supply the example MeterValues to demonstrate the issue.

Cheers,
Jay.

5

Thanks, again.

That’s an entirely reasonable position.

In great news, despite not having it available on any website, Sevr got onto it quickly and sourced a firmware update from the OEM. It’s now reporting the power correctly.

I’m not across your policies on listing EVSEs as supported, but it appears that with the firmware shown in the attached screenshot, the Sevr X2 works with ChargeHQ.

IMG_1190
IMG_11901179×2556 251 KB