Shell (NewMotion / 50five / Enovates) Home Advanced 3.0 does not connect to evcc with Modbus or OCCP

[sebastian-graf]

I have a Home Advanced 3.0, originally from Shell Recharge, now 50five. OEM seems to be Enovates. I saw in the docs, that these chargers are now supported, so I set modbus.tcp.ems.enabled and modbus.tcp.enabled to true, but the charger does not accept any connection on port 502, even after manually configuring the port.

So I went down the OCCP route. I configured the OCCP endpoint to evcc and it seems that there was some initial communication, as the stadionID was discovered by evcc. However when starting the check or trying to add it, it shows network error.

evcc is running on a docker host in the same IP Subnet as the charger. It seems that there is communication:

[ocpp ] INFO 2026/08/11 10:26:07 unknown charge point connected: 17XXXXXX
[17XXXXXX-1] DEBUG 2026/08/11 10:26:12 waiting for chargepoint: 5m0s
[17XXXXXX-1] DEBUG 2026/08/11 10:26:17 proactively triggering BootNotification
[17XXXXXX-1] DEBUG 2026/08/11 10:26:19 overriding default idTag with Alfen-specific value:
[ocpp ] DEBUG 2026/08/11 10:26:42 charge point disconnected: 17XXXXXX
[17XXXXXX-1] DEBUG 2026/08/11 10:26:56 waiting for chargepoint: 5m0s
[17XXXXXX-1] DEBUG 2026/08/11 10:27:01 proactively triggering BootNotification
[17XXXXXX-1] ERROR 2026/08/11 10:27:01 failed to trigger BootNotification: cannot send request 2477143805, no client 17XXXXXX exists
[17XXXXXX-1] DEBUG 2026/08/11 10:27:56 boot notification timeout, proceeding
[ocpp ] DEBUG 2026/08/11 10:28:46 charge point connected: 17XXXXXX

Has anybody used this combination?

evcc 0.313.2
Wallbox 1.13.0.1

[sebastian-graf]

I had a look at the packet dump, especially the web socket connection between evcc and the Wallbox. EVCC requests several messages and the wallbox answers with "accepted" until evcc requests:

[2,"3381975070","ChangeConfiguration",{"key":"MeterValuesSampledData","value":"Power.Offered"}]

which is rejected by the wallbox:

[3,"3381975070",{"status":"Rejected"}]

Same for this request from evcc:

[2,"425926062","ChangeConfiguration",{"key":"MeterValuesSampledData","value":"SoC"}]

answered by wallbox:

[3,"425926062",{"status":"Rejected"}]

Afterwards there are further parameters which are accepted

[mfuchs1984]

That shouldn't be an issue. The logged disconnections are most likely causing the failure. You could try to use "Trotzdem speichern" and restart evcc and then look into the ocpp trace log.

[sebastian-graf]

If a click on "trotzdem speichern" the Wallbox returns back to the state where I can select "prüfen" or "Überprüfen und speichern". It does not save the config of the wallbox