Model evidence at a glance
Public manufacturer evidence documents OCPP 1.6J support. AmpNexus has not yet assigned a Sentinel evidence level to this model and firmware scope.
Manufacturer documented means public protocol evidence is available. It does not mean the model is onboarded, supported or AmpNexus verified, and it is not electrical safety certification.
Hardware evidence scorecard
Zaptec Zaptec Pro
Certification, integration and observable signals are assessed separately.
- OCPP certificationNot evidenced
- AmpNexus integrationDocumented
- Operational stateNot evidenced
- ConnectivityNot evidenced
- Charging sessionsNot evidenced
- EnergyNot evidenced
- VoltageNot evidenced
- CurrentNot evidenced
- PowerNot evidenced
- TemperatureNot evidenced
- RCD diagnosticsNot evidenced
- Contactor feedbackNot evidenced
- Fault / reset evidenceNot evidenced
- Vendor APINot evidenced
- Sentinel assurance
- Assessment pending
- Observability coverage
- 0 / 12
Coverage counts signal areas with published verified or partial evidence. It is not a charger health score.
Evidence flow
From charger to Sentinel
Charger
Zaptec
Zaptec Pro
Published evidence lanes
- Meaning
- Timestamps
- Provenance
- Limitations
Scope
- Model
- Zaptec Pro
- Variant or configuration
- Direct and Zaptec Cloud OCPP routes have different control and load-management boundaries that must be assessed separately.
- Firmware
- Zaptec documents OCPP compliance from firmware 7.5.4.0+ for applicable Pro variants from serial ZPR080000 and ZPG.
- Geography or network context
- UK and European variants where the linked documentation applies
- Evidence last reviewed
- 2026-08-09
- Mapping and integration scope
- 1 integration record
Integration paths
OCPP
OCPP 1.6J
Publicly documented protocol capability only; installed firmware, configuration, access and message coverage require integration review.
- Mapping version
- Not recorded
- Last verified
- Not verified
Integration limitations
- A public OCPP statement does not establish which optional profiles, messages, fields or vendor extensions are enabled on an installed unit.
- No AmpNexus model and firmware mapping has been published for this profile yet.
Capability evidence
- Reported, not yet verified
Integration documentation
OCPP 1.6J interface
- Integration source
- zaptec-pro-documented-ocpp
- Availability conditions
- Subject to the documented model, firmware, configuration, credentials and backend access route.
- Units or meaning
- Public protocol support; not an AmpNexus-verified Sentinel capability mapping.
- Freshness or cadence
- Not yet verified by AmpNexus
- Evidence source
- Zaptec OCPP 1.6J developer documentation; Zaptec OCPP firmware and configuration guide
- Last verified
- Not verified
Protocol compatibility is the start of an integration assessment, not evidence that every Sentinel signal is available.
Evidence boundary
What is not yet evidenced
- Sentinel operational capability and data quality have not yet been verified for the stated model and firmware scope.
- Optional OCPP profiles, message coverage, security configuration and vendor-specific fields remain to be mapped.
- Thermal, contactor, CP/PP and protection evidence must not be inferred from protocol compatibility alone.
How to improve this profile
Expose and verify more evidence
- Connect a representative unit to the AmpNexus integration test path.
- Verify boot, status, transaction, metering, fault and firmware evidence against the applicable firmware.
- Work with the manufacturer to document vendor-specific telemetry and known limitations.