Dashboard
Live status — auto-refreshes every 30s
--
Charging
--
Stopped
--
Idle
--
Available
--
Fault
--
Total Power
--
Best Plug to Connect
--
--
Charging Details
Live plug status — auto-refreshes every 30s
Stopped Vehicles 0
| Plug ⇅ | SoC ⇅ | Time ⇅ | Action |
|---|---|---|---|
| No stopped vehicles | |||
Idle Vehicles 0
| Plug ⇅ | SoC ⇅ | Power ⇅ | Time ⇅ | Action | |
|---|---|---|---|---|---|
| No idle vehicles | |||||
Charging Vehicles 0
| Plug ⇅ | SoC ⇅ | Power ⇅ | Time ⇅ |
|---|---|---|---|
| No active sessions | |||
Available Plugs 0
No available plugs
Malfunctioning / Offline 0
| Plug ⇅ | Reason |
|---|---|
| No faults detected | |
Connect your bus to
--
--
Alternative
--
--
Priority Details
Optimal plug selection for arriving buses
⚠ Shunt Alert — Buses at 100% SoC are blocking plugs. Move vehicles to free capacity.
Hours Left
--
Charging
--
Blocked 100%
--
Free Plugs
--
Buses Remaining
--
Energy Capacity
--
Energy Needed
--
Status
--
| Rank | Plug | Load % | Headroom kW | Energy Deliverable | Score |
|---|---|---|---|---|---|
| Click Renew to calculate | |||||
System Logs
Automation cycle history
Loading...
Settings
Schedule, priority parameters, email alerts
Charging Schedule
Define Stop-when-charged periods — the times when the fleet is actively charging and the system should remotely stop sessions when each bus reaches the SoC threshold.
Plugs are automatically set Operative (and optionally remote-started) when a slot ends. Overnight slots are supported — set From later than To (e.g. 23:00 → 06:00).
Plugs are automatically set Operative (and optionally remote-started) when a slot ends. Overnight slots are supported — set From later than To (e.g. 23:00 → 06:00).
Automation Enabled
Disable to pause all automatic stop/restore actions
Priority Parameters
Vehicles at 100% SoC below this power → Idle section
Trigger power-limit step at this SoC. Use 98% to avoid plug-lock issues on Irizar buses.
Restore Settings
When a charging slot ends, the system automatically sets stopped plugs back to Operative.
If vehicles do not resume via Autocharge, enable explicit remote Start below.
Optional BMS reset: if chargers need an Inoperative → Operative cycle mid-sleep to clear stuck states, set a maintenance reset time below. This is separate from the slot schedule.
Optional BMS reset: if chargers need an Inoperative → Operative cycle mid-sleep to clear stuck states, set a maintenance reset time below. This is separate from the slot schedule.
Leave at default (04:30) if no mid-sleep BMS reset is needed. This only fires during an active slot.
How early before reset time to send Inoperative (default 5 min)
Explicit Start After Slot End
Send a remote Start command 5s after restoring Operative. Disable if vehicles resume via Autocharge — enable only if Autocharge is not active.
Kiosk Display Settings
Shown on all kiosk screens
Displayed on tablet when driver taps INFO on an available plug
Users
Manage accounts and permissions
| Name | Username | Role | Actions |
|---|
OCPP Bridge
Virtual charger settings — connects Kempower cabinets to external CSMS (Ampeco)
Unknown
ⓘ
Saving any changes automatically restarts the bridge to apply them. The restart takes about 5 seconds — the status pill will update when the bridge is back online. Use Stop Bridge / Start Bridge only for manual control.
Live Cabinet Status
Auto-refreshes every 15s
Loading...
CSMS Connection
The base URL provided by Ampeco (or your test backend). Do not include the chargepoint ID — it is appended automatically per cabinet.
The idTag sent for depot autocharge sessions (no driver app). Must be registered as a valid token in your CSMS. Use the same value in Ampeco/CitrineOS authorization settings.
Cabinets & Exported Connectors
Each row is one Kempower cabinet. Set the Charge Point ID exactly as registered in Ampeco.
Under Exported Connectors, type the connector IDs you want Ampeco to see, separated by commas — leave blank to export all plugs.
Click Discover to auto-fill connector IDs from live Kempower data.
Account
Change your password
Kiosk Screens
Tablet displays (1–4 plugs) — each screen gets its own permanent URL
LED Strips
ESP32 LED stripe controllers — 1 plug per strip, JSON endpoint