Message Detail
Inject Command
Click an action or type one, then click Builder for guided fields
Charging Profile
Schedule Visualization
Add schedule periods below
Schedule Periods
| # | Start (s) | Limit | Phases |
|---|
Presets
Clear matches:
unchecked = clear the profile id on every connector / stack level
Applied envelope (read-back)
GetCompositeSchedule is what the station says it will actually deliver, after stacking every installed profile — the answer to “which limit is really in force?”.
Alpitronic HYC: the factory profile ships ChargePointMaxProfileEnabled=false, so station-wide load management is off and the composite may be empty even when a TxDefaultProfile is installed. An empty result is an answer, not a failure.
Uses the Connector ID, Duration and Rate Unit above.
No composite schedule read yet
| From | Until | Limit | Phases |
|---|
Scenarios
| Name | Version | Messages | Source |
|---|
Diagnostics pull — one-time upload
Mints a single-use upload link, sends
GetDiagnostics (1.6) / GetLog (2.0.1) to the charger, and collects the file here for download.Uploaded files
Collect & correlate
Pulls the charger's logs (
GetDiagnostics / GetLog), unpacks the HYC diagnostic files, and lines their events up against this proxy's OCPP traffic — matched by OCPP messageId, with the site's time-zone offset auto-derived. Runs on demand or daily.Correlation results
Payments …
Tap → pre-auth → RemoteStart → charge → settle. Requires
payments.enabled + a terminal linked to the charger.Active payments
History
| Time | Charger | Card | Energy | Amount | State |
|---|
ID-Tag Access Control
Gate OCPP Authorize / StartTransaction by the presented ID — RFID card, Plug&Charge VID, autocharge MAC, etc. Applies in standalone (mini-CSMS) mode.
Loading…
Reservations
Reserve for an ID (RFID card or Plug&Charge / AutoCharge VID) until it expires. Sends ReserveNow; the charger holds it until that ID authorizes. 1.6 reserves a connector; 2.0.1 reserves an EVSE (which holds all its connectors) and can constrain by connector type.
Reservations
Charger Control
Send OCPP commands to a connected charger. Each is injected and the charger's response is shown inline. Version-aware (1.6 & 2.0.1).
Trigger Message
Ask the charger to (re)send a message now — handy to coax a status or boot out of a quiet unit.
Availability
Take a connector (or the whole charger — connector 0 / blank) in or out of service.
ChangeAvailability.Unlock Connector
Release the cable lock.
UnlockConnector. 1.6 takes a connector id; 2.0.1 takes an EVSE id plus a connector index within that EVSE — a dual-outlet HYC is EVSE 1/conn 1 and EVSE 2/conn 1. A station with a transaction running answers OngoingAuthorizedTransaction (2.0.1) or UnlockFailed.Display Message — OCPP 2.0.1
Put text on the station's screen.
SetDisplayMessage / GetDisplayMessages / ClearDisplayMessage. OCPP 1.6 has no DisplayMessage feature — these controls are disabled on a 1.6 charger. Alpitronic HYC: gated by the factory key DisplayMessageEnabled, which is false by default.Firmware Update
Upload an image here and the proxy serves it at an unguessable
/fw/<token>/<name> URL; UpdateFirmware then points the charger at it — no external web server. Progress arrives as FirmwareStatusNotification. Alpitronic HYC: an unsigned image needs AllowNonSecureFirmwareUpdates=true (the factory default). Set firmwareHostBaseUrl in settings to a host the charger can actually reach.Local Authorization List
Push the Access-tab whitelist (exact IDs only) to the charger so it can authorize the same cards while offline.
SendLocalList / GetLocalListVersion.Plug & Charge (ISO 15118)
Contract-certificate relay to an ISO 15118 certificate pool. The CSMS never parses or generates EXI and is not a CA — it forwards the EV's blob and hands the answer back.
Off by default: with the relay disabled the proxy keeps answering the honest refusals (
UnknownVendorId / Failed), which is what stops a PnC station tearing its session down. Enable it in Settings → config.json (pnc.enabled).
Loading…
Reset
Reboot the charger. Soft = graceful (finish/queue), Hard = immediate. Interrupts any active session. Two-click to confirm.
Monitoring & Events
What the charger reports on its own: 2.0.1 NotifyEvent device events (the replacement for the 1.6 StatusNotification.errorCode channel) and SecurityEventNotification. Below that, the variable-monitoring composers that make a station push a NotifyEvent when a value crosses a threshold.
Device events NotifyEvent
Faults and threshold trips the station pushed, newest first. A
Cleared row is the return-to-normal half and is never counted as a fault.| Time | Component | Variable | Code / trigger | Detail |
|---|
Security events SecurityEventNotification
1.6 security whitepaper + 2.0.1. Alpitronic HYC: the factory key
SendOcppSecurityNotifications is false by default — flip it (Control → config push, or the charger UI) or this list stays empty. Many of these are benign (SettingSystemTime), so they are never counted as faults.| Time | Charger | Type | techInfo |
|---|
Variable monitoring — OCPP 2.0.1
SetVariableMonitoring asks the station to watch a device-model variable and push a NotifyEvent when it trips. GetMonitoringReport asks what monitors it already has — the answer arrives as NotifyMonitoringReport and is collected below. 1.6 has no monitoring feature. Alpitronic HYC: the 302-key factory profile advertises no MonitoringCtrlr keys, so a real HYC may answer Rejected/NotSupported — that answer is the test result.