Skip to content

OCPP GARO Entity Pro charger creation fails from 0.312.0 #33296

Closed

Description

@munterkalmsteiner

Describe the bug

I am using a GARO Entity Pro charger via OCPP 1.6J.

The charger can be configured and used successfully with evcc 0.311.1. With evcc 0.312.0 and newer versions tested, adding/testing the same charger through the UI fails.

The GARO charger establishes an OCPP connection to evcc and responds to OCPP requests. During charger creation, however, evcc does not complete the charger initialization.

I reproduced the behavior after deleting the existing charger configuration and creating it again from scratch.

Tested versions:

0.311.1: works
0.312.0: fails
0.314.5: fails

The GARO Entity Balance was initially also connected to evcc via OCPP. I additionally tested with only the Entity Pro connected, and the problem remained.

Steps to reproduce

  1. Run evcc 0.312.0 or 0.314.5.
  2. Configure a GARO Entity Pro to use evcc as its OCPP 1.6J backend.
  3. In the evcc UI, add an OCPP 1.6J compatible charger.
  4. Test or save the charger.
  5. The UI eventually reports a failure, for example network error or create failed: missing charger instance.

Repeating the same procedure with evcc 0.311.1 succeeds.

Configuration details

Equivalent YAML configuration:

chargers:
  - name: garo
    type: template
    template: ocpp
    stationid: GaroCS-49152E2A66280
    connector: 1

Charger:

Manufacturer: GARO
Model: Entity Pro
Firmware: 4.10.3

Log details

The charger connects successfully:

[ocpp  ] INFO unknown charge point connected: GaroCS-49152E2A66280

When testing the charger, evcc waits for the charge point and sends a TriggerMessage requesting a BootNotification:


[GaroCS-49152E2A66280-1] DEBUG waiting for chargepoint: 5m0s
[GaroCS-49152E2A66280-1] DEBUG proactively triggering BootNotification
[ocpp  ] TRACE send GaroCS-49152E2A66280: [2,"3878677571","TriggerMessage",{"requestedMessage":"BootNotification"}]
[ocpp  ] TRACE recv GaroCS-49152E2A66280: [3,"3878677571",{"status":"Accepted"}]


The charger subsequently sends a BootNotification:


[ocpp  ] TRACE recv GaroCS-49152E2A66280: [2,"tkWmUy6/Se6YK+4LuhFn+w","BootNotification",{"chargePointModel":"EntityPro","chargePointVendor":"Garo","chargeBoxSerialNumber":"4C3B6C016F70","chargePointSerialNumber":"49152E2A66280","firmwareVersion":"4.10.3","meterSerialNumber":"4c3b6c016f70","meterType":"Embedded"}]


evcc replies with Pending:


[ocpp  ] TRACE send GaroCS-49152E2A66280: [3,"tkWmUy6/Se6YK+4LuhFn+w",{"currentTime":"2026-08-30T00:03:22Z","interval":60,"status":"Pending"}]


and later:


[GaroCS-49152E2A66280-1] DEBUG boot notification timeout, proceeding


Depending on the version, the UI subsequently reports:

create failed: missing charger instance (0.314.5)

or 

network error (0.312.0)

What type of operating system or environment does evcc run on?

Linux

External automation

  • I have made sure that no external automation like HomeAssistant or Node-RED is active or accessing any of the mentioned devices when this issue occurs.

Nightly build

  • I have verified that the issue is reproducible with the latest nightly build

Version

No response

Activity

  1. github-actions commented on Aug 30, 2026

    @github-actions
    Contributor

    Thanks for the detailed logs — they pinpoint this well.

    Root cause: the charger-creation/test HTTP handler wraps device instantiation in a hard 10s context timeout (startDeviceTimeout in server/http_config_helper.go). For OCPP, the boot handshake needs: WebSocket connect → 5s built-in delay before evcc proactively sends TriggerMessage (TriggerBootDelay in charger/ocpp/const.go) → charger processing/round-trip → actual BootNotification. On real hardware like the GARO Entity Pro this can take longer than the remaining time budget.

    Since #31652 (OCPP: clear failed charge point registration on init error, merged 2026-07-10, first released in 0.312.0), when the outer context is cancelled by that 10s timeout, RegisterChargepoint (charger/ocpp/cs.go) now clears the in-flight charge point registration (reg.cp = nil) instead of keeping it cached. That means the charger's BootNotification, which is still in flight and arrives shortly after the timeout, lands with no registered charge point (cs.ChargepointByID fails), so evcc answers Pending and never calls cp.OnBootNotification/cp.connect(true) for it — the boot result is discarded. The next Test/Save attempt starts a brand-new charge point object and repeats the same race, so the charger config ends up saved without ever gaining a valid instance, producing missing charger instance (core/loadpoint.go:271, since dev.Instance() is nil).

    Before #31652, the same 10s timeout also caused the request to fail, but the registered charge point object was kept around, so the boot handshake could complete in the background and a subsequent retry picked up the already-initialized instance — explaining why 0.311.1 worked despite the same tight timeout.

    This looks fixable, but the fix needs some care: #31652 intentionally fixed a real bug (permanently caching a charge point that never completes setup), so simply reverting it would reopen that issue. A better fix likely needs to distinguish "outer request timed out while the boot handshake is still legitimately in progress" from "the charge point failed to respond at all", or decouple the OCPP registration/boot-wait from the UI request timeout so a slow-but-working handshake can finish in the background and be reused by the next Test/Save.

    cc @andig

    🤖 Generated with Claude Code

    🤖 Links updated with OpenCode

  2. added
    devicesSpecific device support
    and removed
    bugSomething isn't working
    on Aug 30, 2026
  3. munterkalmsteiner commented on Sep 6, 2026

    @munterkalmsteiner
    SponsorAuthor

    Is there any other information I can provide? I'm also happy to test any fix if that would help.

  4. andig commented on Sep 7, 2026

    @andig
    Member

    Could you please try current release? The timeout has since been extended to 15s which might already help.

  5. andig commented on Sep 7, 2026

    @andig
    Member

    It it still fails can you please provide timestamped debug/OCPP trace covering a fresh Test/Save attempt through the boot timeout?

  6. munterkalmsteiner commented on Sep 7, 2026

    @munterkalmsteiner
    SponsorAuthor

    Tested with 0.315.0, but unfortunately, no success...

    [GaroCS-49152E2A66280-1] DEBUG 2026/09/07 23:10:23 waiting for chargepoint: 5m0s
    [GaroCS-49152E2A66280-1] DEBUG 2026/09/07 23:10:28 proactively triggering BootNotification
    [ocpp  ] TRACE 2026/09/07 23:10:28 send GaroCS-49152E2A66280: [2,"3825946","TriggerMessage",{"requestedMessage":"BootNotification"}]
    [ocpp  ] TRACE 2026/09/07 23:10:28 recv GaroCS-49152E2A66280: [3,"3825946",{"status":"Accepted"}]
    [ocpp  ] TRACE 2026/09/07 23:10:35 recv GaroCS-49152E2A66280: [2,"FW0IM0IJQ5S+BGr26g09EA","BootNotification",{"chargePointModel":"EntityPro","chargePointVendor":"Garo","chargeBoxSerialNumber":"***redacted***","chargePointSerialNumber":"***redacted***","firmwareVersion":"4.10.3","iccid":"***redacted***","imsi":"***redacted***","meterSerialNumber":"***redacted***","meterType":"Embedded"}]
    [ocpp  ] TRACE 2026/09/07 23:10:35 send GaroCS-49152E2A66280: [3,"FW0IM0IJQ5S+BGr26g09EA",{"currentTime":"2026-09-07T21:10:35Z","interval":60,"status":"Pending"}]
    [GaroCS-49152E2A66280-1] DEBUG 2026/09/07 23:10:42 boot notification timeout, proceeding
    
  7. andig commented on Sep 8, 2026

    @andig
    Member

    Thanks, this trace helps. I checked the release source: 0.315.0 still has the 10-second timeout. The increase to 15 seconds merged the following day in #33118, so my recommendation to try the current release was premature. Could you test the current nightly after restarting evcc and include the log through the final Test/Save result? Your BootNotification arrives after 12 seconds, which explains why 0.315.0 still responds Pending.

  8. munterkalmsteiner commented on Sep 9, 2026

    @munterkalmsteiner
    SponsorAuthor

    The nightly build, 0.316.0-dev, worked. The charger is now validating and connected. Thanks! Will wait for the release, switch and test.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

devicesSpecific device support

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions