go-eCharger V3 with 054.7 connecting using OCPP

[stumbaumr]

Describe the bug

Since 054.0ff go-eCharger V3 and Gemini implement OCPP. After successfully playing around with cmd/ocpp and getting a config to work I tried using the go-e with OCPP and failed. There is not even output coming in the trace log.

Steps to reproduce

1. Configure evcc to use OCPP

  - name: go-eCharger
    type: template
#    template: go-e-v3
#    host: 192.168.178.22
    template: ocpp
    meter: false
#    stationid: go-echarger-05XXXX
#    stationid: cp0001
    idtag: 1

2. Configure go-eCharger to use OCPP (-> Internet -> OCPP )
3. Save
4. Look at the output...

Configuration details

chargers:
  - name: go-eCharger
    type: template
#    template: go-e-v3
#    host: 192.168.178.22
    template: ocpp
    meter: false
#    stationid: go-echarger-05XXXX
#    stationid: cp0001
    idtag: 1

Log details

root@raspberrypi:~# ./evcc
[main  ] INFO 2022/11/28 22:22:02 evcc 0.108.2
[main  ] INFO 2022/11/28 22:22:02 using config file: /root/evcc.yaml
[main  ] INFO 2022/11/28 22:22:02 starting ui and api at :7070
[db    ] TRACE 2022/11/28 22:22:02 SELECT count(*) FROM sqlite_master WHERE type='table' AND name="settings" -1 <nil>
[db    ] TRACE 2022/11/28 22:22:02 SELECT sql FROM sqlite_master WHERE type IN ("table","index") AND tbl_name = "settings" AND sql IS NOT NULL order by type = "table" desc 1 <nil>
[db    ] TRACE 2022/11/28 22:22:02 SELECT * FROM `settings` LIMIT 1 -1 <nil>
[db    ] TRACE 2022/11/28 22:22:02 SELECT * FROM `settings` 6 <nil>
[ocpp  ] DEBUG 2022/11/28 22:22:03 waiting for chargepoint: 10m0s

That's it...

I do have a tcpdump...

What type of operating system are you running?

Docker container

Version

evcc version 0.108.2

[stumbaumr]

wireshark.zip

[Sillium007]

This might be completely wrong but:

[ocpp ] DEBUG 2022/11/28 22:22:03 waiting for chargepoint: 10m0s

Did you wait 10 minutes? I don't know how OCPP works but at least this sounds to me like the Charger is supposed to do something and maybe the charger only does this initialization (or whatever it does) every now and then,

edit:
Looking at the code

evcc/charger/ocpp.go

Line 123 in 24f4958

c.log.DEBUG.Printf("waiting for chargepoint: %v", timeout)

It looks like evcc is waiting in the initialization phase for the charger and will only continue after the timeout. Therefore I would recommend to try again with waiting 10 minutes and see what the logs show.

https://pkg.go.dev/time#example-After

[stumbaumr]

Thanks for looking into it, but... ;-)

• This was my first idea as well, so yes, I waited the first time for 10 minutes...
• The tcpdump shows that the charger connects to the evcc and then receives a 404 not found response.

I used evcc's own OCPP test client in ./cmd/ocpp to try out my evcc config and also took a tcpdump from that - there the evcc does not respond with a 404 - but the request from the charger to me looks the same as from the test client...

[andig]

OCPP has various drawbacks over direct support. You should not use it unless forced to.

[stumbaumr]

I read in some OCPP/EEBUS issue/pull request comment here that these open standards should be the way to go and in the long term vendor specific interfaces should go away. evcc is still beta software and prone to changes and interruptions during operational use so trying things out does do no harm to my go-eCharger - therefore I tried their implementation out and discovered that bug. go-e used https://github.com/steve-community/steve to implement and verify their implementation - so I believe the bug is on evcc side. And that is what I reported...

[andig]

I believe the bug is on evcc side

evcc wartet auf den Chargepoint der keine Verbindung aufnimmt. Ich sehe da keinen Bug, bitte keine Verwirrung stiften.

I read in some OCPP/EEBUS issue/pull request comment here that these open standards should be the way to go

Das ist kein Statement vom evcc Team. Ocpp bzgl. Go-E ist nicht hilfreich.

[stumbaumr]

evcc wartet auf den Chargepoint der keine Verbindung aufnimmt. Ich sehe da keinen Bug, bitte keine Verwirrung stiften.

Korrekt. Sorry, das war nicht hilfreich von meiner Seite.

Das ist kein Statement vom evcc Team. Ocpp bzgl. Go-E ist nicht hilfreich.

Bin der Ansicht, das bei diesen Standard-Produkten Wallbox sich Standardschnittstellen über alle Hersteller durchsetzen sollten.
#5122 (reply in thread)

[stumbaumr]

Got it to work :-)... at least it is connecting.

Seems there is a limitation on the length of stationid on the go-eCharger side. After changing the stationid to go-e-05XXXX it suddenly connected...

OCPP Server URL using ws://192.168.178.20:8887/go-e-05XXXX

[RTTTC]

So what is your complete working OCPP charger configuration now ?

[stumbaumr]

Charger config part:

chargers:
  - name: go-eCharger
#    template: go-e-v3
#    host: 192.168.178.22
    type: template
    template: ocpp
    idtag: 1
    meter: false
    stationid: go-e-05XXXX

Log output:

[ocpp  ] DEBUG 2022/11/30 07:25:09 chargepoint connected: go-e-05XXXX
[go-e-05XXXX] TRACE 2022/11/30 07:25:09 *core.BootNotificationRequest: &{ChargeBoxSerialNumber: ChargePointModel:go-eCharger ChargePointSerialNumber:05XXXX ChargePointVendor:go-e FirmwareVersion:054.7 Iccid: Imsi: MeterSerialNumber: MeterType:}
[go-e-05XXXX] TRACE 2022/11/30 07:25:09 ChargeProfileMaxStackLevel (r/o): 20
[go-e-05XXXX] TRACE 2022/11/30 07:25:09 ChargingScheduleAllowedChargingRateUnit (r/o): Current
[go-e-05XXXX] TRACE 2022/11/30 07:25:09 ChargingScheduleMaxPeriods (r/o): 20
[go-e-05XXXX] TRACE 2022/11/30 07:25:09 ClockAlignedDataInterval (r/w): 0
[go-e-05XXXX] TRACE 2022/11/30 07:25:09 ConnectorPhaseRotation (r/o): 0.RST,1.RST
[go-e-05XXXX] TRACE 2022/11/30 07:25:09 ConnectorPhaseRotationMaxLength (r/o): 3
[go-e-05XXXX] TRACE 2022/11/30 07:25:09 ConnectorSwitch3to1PhaseSupported (r/o): true
[go-e-05XXXX] TRACE 2022/11/30 07:25:09 GetConfigurationMaxKeys (r/o): 99
[go-e-05XXXX] TRACE 2022/11/30 07:25:09 HeartbeatInterval (r/w): 60
[go-e-05XXXX] TRACE 2022/11/30 07:25:09 LightIntensity (r/w): 49
[go-e-05XXXX] TRACE 2022/11/30 07:25:09 MaxChargingProfilesInstalled (r/o): 20
[go-e-05XXXX] TRACE 2022/11/30 07:25:09 MeterValueSampleInterval (r/w): 10
[go-e-05XXXX] TRACE 2022/11/30 07:25:09 MeterValuesSampledData (r/o): Current.Import,Current.Offered,Energy.Active.Import.Register,Frequency,Power.Active.Import,Power.Factor,Power.Offered,Temperature,Voltage
[go-e-05XXXX] TRACE 2022/11/30 07:25:09 MeterValuesSampledDataMaxLength (r/o): 10
[go-e-05XXXX] TRACE 2022/11/30 07:25:09 NumberOfConnectors (r/o): 1
[go-e-05XXXX] TRACE 2022/11/30 07:25:09 SupportedFeatureProfiles (r/o): Core,FirmwareManagement,SmartCharging,RemoteTrigger
[go-e-05XXXX] TRACE 2022/11/30 07:25:09 SupportedFeatureProfilesMaxLength (r/o): 6
[go-e-05XXXX] TRACE 2022/11/30 07:25:09 WebSocketPingInterval (r/w): 10
[go-e-05XXXX] DEBUG 2022/11/30 07:25:09 waiting for chargepoint status: 30s
[ocpp  ] ERROR 2022/11/30 07:25:09 TriggerMessage MeterValues for go-e-05XXXX: Rejected
[go-e-05XXXX] TRACE 2022/11/30 07:25:09 *core.StatusNotificationRequest: &{ConnectorId:0 ErrorCode:NoError Info: Status:Available Timestamp:2022-11-30 07:25:09 +0100 CET VendorId: VendorErrorCode:}
[go-e-05XXXX] TRACE 2022/11/30 07:25:10 *core.StatusNotificationRequest: &{ConnectorId:1 ErrorCode:NoError Info: Status:Available Timestamp:2022-11-30 07:25:09 +0100 CET VendorId: VendorErrorCode:}

[Joeknx]

Many thanks for the guid. With the FW 054.11 it did not work for me. It works with the 055.0 Beta!

[andig]

@Joeknx OCPP has various drawbacks. Unless you have to I'd always recommend direct integration.