Help centre

Nine times out of ten it is the OCPP identity or the endpoint URL, entered with a typo or the wrong case. After that, check that the site’s firewall permits outbound WebSocket upgrades on 443 — many host networks allow HTTPS but block the upgrade. If both are correct, the charger’s message log will show whether it is reaching us at all.

Check the payment status on the session. The usual causes are a pre-authorisation that expired before capture, a gateway decline after the session completed, or a free or promotional tariff. All three are distinguishable in the session record, and the first two are recoverable through follow-up.

This is almost always meter value configuration. Confirm the charger reports Energy.Active.Import.Register in MeterValuesSampledData and that a sample interval is set. A unit that reports no energy register cannot be billed correctly, and the fix is a configuration change rather than a refund policy.

Create the partner, link their stations, and send an invite. They set their own password and see only their own stations, sessions, uptime and settlements. The scoping is applied in the data layer, so it also holds for their exports.

Create a station group containing those sites and assign the staff member to it with the permission level you want — view, operate or manage. Owners always retain full visibility, so nobody can accidentally lock themselves out.

No. The resolved tariff is snapshotted onto each session when it starts, so a price change applies to sessions that begin after it. Past invoices are never rewritten.

Read back the composite schedule from the charger. Some models accept SetChargingProfile and then ignore it — the response and the composite schedule will show which. Also confirm the profile was re-applied after the charger’s last boot.

Through CSV export in the console, or programmatically through the API — sessions, meter values, drivers, payments, invoices and settlements. There is no request process and no delay.