Skip to content

Releases: ocpp-debugkit/toolkit

v0.4.2

Choose a tag to compare

@github-actions github-actions released this 22 Jul 11:32
b79120c

What's Changed

  • fix(core): track STATUS_TRANSITION_VIOLATION status per connector by @sepehr-safari in #131
  • chore: version packages by @github-actions[bot] in #132

Full Changelog: https://github.com/ocpp-debugkit/toolkit/compare/@ocpp-debugkit/toolkit@0.4.1...v0.4.2

v0.4.1

Choose a tag to compare

@github-actions github-actions released this 22 Jul 10:28
ac73cbb

What's Changed

  • fix(core): scope METER_VALUE_ANOMALY to cumulative energy registers per connector by @sepehr-safari in #129
  • chore: version packages by @github-actions[bot] in #130

Full Changelog: https://github.com/ocpp-debugkit/toolkit/compare/@ocpp-debugkit/toolkit@0.4.0...v0.4.1

@ocpp-debugkit/toolkit@0.4.2

Choose a tag to compare

@github-actions github-actions released this 22 Jul 11:32
b79120c

Patch Changes

  • 713dbfc: Fix STATUS_TRANSITION_VIOLATION false positives (#128). The rule validated connector status transitions against a single previous status shared across all connectors, so on a multi-connector station an interleaved notification from a different connector (for example connector 1 going Available while connector 2 goes Finishing) was reported as an invalid transition. Status is now tracked per connectorId (connectorId 0, the charge point as a whole, forms its own series), and each transition is validated only within one connector's series. Reported by shiv3 from the ocpp-cp-simulator integration.

@ocpp-debugkit/toolkit@0.4.1

Choose a tag to compare

@github-actions github-actions released this 22 Jul 10:28
ac73cbb

Patch Changes

  • e1c65e5: Fix METER_VALUE_ANOMALY false positives (#127). The rule flattened every sampledValue across measurand, phase, unit, location and connector into a single series and asserted monotonicity, but only cumulative Energy.*.Register measurands are monotonic and non-negative per OCPP 1.6 section 7.28, so any charge point reporting more than one measurand per sample, or any multi-connector station, produced warnings on nearly every MeterValues message. Readings are now bucketed by (connectorId, measurand, phase, unit, location) and the monotonic and non-negative checks apply only to cumulative energy registers (an absent measurand defaults to Energy.Active.Import.Register); other measurands are ignored by this rule. Reported by shiv3 from the ocpp-cp-simulator integration.

v0.4.0

Choose a tag to compare

@github-actions github-actions released this 17 Jul 11:54
3cff9b1

What's Changed

  • docs: add v0.4.0 and v0.5.0 milestones to the roadmap by @sepehr-safari in #123
  • feat(core): parse the Open OCPP Trace interchange format by @sepehr-safari in #124
  • feat(core,cli): export traces to the Open OCPP Trace format by @sepehr-safari in #126
  • chore: version packages by @github-actions[bot] in #125

Full Changelog: https://github.com/ocpp-debugkit/toolkit/compare/@ocpp-debugkit/toolkit@0.3.2...v0.4.0

@ocpp-debugkit/toolkit@0.4.0

Choose a tag to compare

@github-actions github-actions released this 17 Jul 11:54
3cff9b1

Minor Changes

  • 0115e85: Write the Open OCPP Trace interchange format. toOpenOcppTraceRecords() / toOpenOcppTraceJsonl() export any parsed trace as v1.1 records, with raw serialized from the stored frame, response action back-filled by messageId correlation, and skip-and-flag warnings for events the format cannot represent. A new ocpp-debugkit convert <file> CLI command emits the JSONL, carrying trace-level metadata over from JSON Object inputs. Every exported record is validated against the specification's published JSON Schema in CI, and round-trip tests prove export-then-reparse preserves the consumer view and the events.
  • 32e48f0: Read the Open OCPP Trace interchange format. parseTrace() auto-detects it and parseOpenOcppTrace() parses it directly, mapping records onto the internal event model with raw-frame precedence, messageId-based action derivation, and unknown-field tolerance. deriveOpenOcppTraceView() exposes the format's consumer view, checked in CI against the specification's 15 conformance fixtures.

v0.3.2

Choose a tag to compare

@github-actions github-actions released this 14 Jul 14:13
f06b711

What's Changed

  • chore: retire apps/web (moved to ocpp-debugkit/website) by @sepehr-safari in #117
  • docs: correct stale detection rule and scenario counts by @sepehr-safari in #119
  • chore: version packages by @github-actions[bot] in #120

Full Changelog: https://github.com/ocpp-debugkit/toolkit/compare/@ocpp-debugkit/toolkit@0.3.1...v0.3.2

@ocpp-debugkit/toolkit@0.3.2

Choose a tag to compare

@github-actions github-actions released this 14 Jul 14:13
f06b711

Patch Changes

  • a6b7d12: Correct the package README, which advertised 10 detection rules and 10 predefined scenarios. The toolkit ships 16 detection rules (4 critical, 10 warning, 2 info) and 15 scenarios.

v0.3.1

Choose a tag to compare

@github-actions github-actions released this 09 Jul 17:44
e210de1

What's Changed

  • docs: post-v0.3.0 milestone boundary audit by @sepehr-safari in #111
  • chore: update repo references after rename to ocpp-debugkit/toolkit by @sepehr-safari in #113
  • feat(core): detect repeated boot notifications by @Develop-KIM in #114
  • chore: version packages by @github-actions[bot] in #115

New Contributors

Full Changelog: https://github.com/ocpp-debugkit/toolkit/compare/@ocpp-debugkit/toolkit@0.3.0...v0.3.1

v0.3.0

Choose a tag to compare

@github-actions github-actions released this 09 Jul 07:48
2224138

What's Changed

Full Changelog: https://github.com/ocpp-debugkit/ocpp-debugkit/compare/@ocpp-debugkit/cli@0.1.1...v0.3.0