Open-source DevTools for debugging OCPP charging sessions. Parse, analyze, and diagnose traces from a browser tab, your CI pipeline, or a native desktop instrument.
The OCPP DebugKit family is two independent products that share the same trace format, event model, and failure taxonomy. Use one, or both.
TypeScript · npm · CLI · browser
The library and CI brain.
Parse, analyze, and report OCPP traces anywhere JavaScript runs — in the browser inspector, a Node CLI, or your test suite.
Zig · Native SDK · desktop
The instrument on the bench.
A native desktop debugger that sits between a charge point and its backend, decodes every frame live, and flags protocol failures the moment they happen.
| Toolkit | Studio | |
|---|---|---|
| Language | TypeScript | Zig |
| Runs in | Browser, Node, CI | Native desktop (macOS, Linux) |
| Surface | npm library, CLI, web inspector | GUI app + headless CLI |
| Best for | Analysis anywhere, automation, sharing | Live capture, native performance, OS integration |
| Install | npm install -g @ocpp-debugkit/toolkit | One-line macOS installer |
A trace captured in Studio opens in the toolkit's web inspector, and vice versa. The two are independent implementations checked against the same conformance contract in CI — same format, same normalized events, same failure taxonomy.
The toolkit reads and writes the vendor-neutral Open OCPP Trace format, so a trace from a simulator, proxy, or CSMS test suite opens in the inspector, and DebugKit can write the format back out for them. The parser and exporter are checked against the format's conformance fixtures in CI.
Normalize OCPP 1.6J traces into events, sessions, and a timeline you can search and filter.
16 detection rules flag failures — failed auth, connector faults, offline stations, meter gaps, and more.
Semantic diffing of two traces to see exactly what changed between runs.
Export a session analysis as a Markdown or HTML report.
Step forward and back through a session deterministically, at any speed.
Strip station IDs, transaction IDs, and idTags before sharing a trace.
15 built-in scenarios with expected-failure assertions for the analysis engine.
Run scenario checks in CI and fail the build on regressions.
# Install the toolkit CLI
npm install -g @ocpp-debugkit/toolkit
# Inspect a trace
ocpp-debugkit inspect trace.json
# Generate a report
ocpp-debugkit report trace.json --output report.md
# Run a scenario
ocpp-debugkit scenario run failed-authOr try the web inspector — no installation required.