Frequently asked questions
What is an OCPP test server?
An OCPP central system you point your charger at to see whether it speaks the protocol correctly before connecting it to a real platform. This one answers everything with sensible values (start accepted, card accepted…), so you can run a full charging session, and it explains what would fail in production.
What does it check?
- That the URL has the right shape, without the identity repeated at the end.
- Whether it connects encrypted (wss://) or unencrypted (ws://), and which subprotocol it asks for.
- Whether it sends a username and password, and in what form (without showing the password).
- That every message matches the official OCPP 1.6J or 2.0.1 schema.
- That meter values include the energy register, needed to bill per kWh.
- How often it sends meter values while charging, and whether its clock is right.
- That it closes the session before saying “Available”: some chargers do it the other way round and the session gets lost.
I got a warning. How do I fix it?
We have a guide for each common error: won't connect, BootNotification Rejected, keeps disconnecting, 0 kWh sessions or won't start remotely.
Do I need to sign up?
No. The page gives you a URL with your own code. Only whoever has that code sees the charger's log and can send it commands.
What is stored about my charger?
Nothing on disk. Messages live in memory and are deleted after two hours without activity.
It works here. Will it work on askacharge.com?
That's the idea: the test server checks the charger's handshake with the same code askacharge.com uses. The difference is that there the password must be the one the panel gives you and cards must be registered. The brand-by-brand guides to changing the OCPP URL show where each setting lives.
Can I use it as a free OCPP server for my chargers for good?
No, and we would rather say so up front: it is for testing. Each connection lasts at most 30 minutes and codes expire after two hours without activity. To run chargers every day (sessions, cards, tariffs, billing) you need a full central system (CSMS) such as askacharge.com: 30 days free, no card, and the same URL shape you used here. Your own chargers at home? We're preparing askacharge.com/casa, the first one free: not open yet, but you can join the waiting list.
Does it support OCPP 2.0.1?
Yes. The same URL accepts OCPP 1.6J and 2.0.1: the charger picks the version with the WebSocket subprotocol it asks for (ocpp1.6 or ocpp2.0.1), and the page shows which one it used.