docs: EV charger bench commissioning, reset and local OCPP guide

[HuggeK]

Bench notes for the EV chargers on the Sourceful test rig — how to get into each
unit, how to point it at a local OCPP 1.6J central system, and how to factory
reset one when an installer login is in the way.

No driver or manifest changes yet. This is the groundwork that decides which
drivers are worth writing and in what order.

Bench inventory

Device	Local path	Existing driver
Charge Amps Dawn (22 kW 3P)	OCPP 1.6J	none
Charge Amps Luna (22 kW 3P)	OCPP 1.6J	none
Charge Amps, silver RFID unit	OCPP 1.6J	none
Zaptec (Go / Go 2 / Pro)	OCPP 1.6J, cloud-gated	zaptec (HTTP, read-only)
Easee Charge Up	native OCPP 1.6J, beta	easee (Modbus), easee_cloud (HTTP)
Ambibox V2G / InterControl ambiCHARGE 11 kW	MQTT	ambibox_v2x ✅

Findings that shape the work

There is no Charge Amps driver at all. Three of the six bench units are
Charge Amps, and every current model speaks OCPP 1.6J since the migration off
the proprietary CAPI protocol. This is the largest gap and the best argument for
a local central system.

Zaptec cannot be unlocked from the bench. Box-level OCPP needs the
Allow OCPP 1.6J user-group permission plus partner access granted through the
Zaptec cloud portal. There is no installer-app or on-device path, so without a
partner account it stays on the read-only HTTP driver.

Easee native OCPP moves the cloud dependency rather than removing it. The
charger does talk straight to a local 1.6J server at runtime, but the switch is
provisioned through Easee's cloud API, needs firmware ≥ 328, and is beta.

Operational gotchas worth knowing before touching hardware

• Charge Amps Bluetooth pairing only works in the first 10 minutes after
  power-up. If a unit has been energised longer, cut the fuse and re-energise
  before searching. This is the most common reason a bench unit "will not
  connect".
• Charge Amps RFID locks must be activated via my.charge.space before the
  OCPP switch, not after.
• Cloud and local are mutually exclusive on Charge Amps — a unit on a local
  central system disappears from the Charge Amps app.
• Charge Amps factory reset is itself behind the password. Reset lives in the
  local interface under System, and no hardware reset button is documented, so a
  second-hand unit with no password letter needs Charge Amps support.
• Zaptec appends the serial to the OCPP URL automatically — do not include it
  yourself.
• Charge Amps remote stop is unreliable in other OCPP integrations; the
  control path that works is current-based (0 A to stop). A driver should model
  stop as a charging profile at 0 A rather than RemoteStopTransaction.

Why this points at a local OCPP server

A local central system unlocks the three Charge Amps units and Easee natively,
and would unlock Zaptec if partner access appears.

FTW had exactly this and deleted it: go/internal/ocpp/ held a 1.6J central
system (config.go, handlers.go, server.go plus tests, on
github.com/lorenzodonini/ocpp-go), retired as unused in srcfl/ftw#578. The
starting point for that work is that commit, not a blank page.

🤖 Generated with Claude Code

[HuggeK]

Moved to a discussion: srcfl/ftw#747 — EV charger bench: commissioning, factory reset and local OCPP

This is operator knowledge about hardware, not driver source, so a discussion is a better home than a doc file in this repo. Two things pushed it across:

• Most of these chargers need no driver at all. They speak OCPP, and FTW now serves OCPP 1.6J and 2.0.1 directly in core — see feat(ocpp): OCPP 1.6J + 2.0.1 support — chargers connect with no driver ftw#732. Only the Ambibox / InterControl ambiCHARGE still needs one, and ambibox_v2x already covers it.
• Discussions are disabled on this repo, so it lives on srcfl/ftw next to the OCPP work.

Closing unmerged; nothing here is lost.