Connect your CSMS
Chargeflux.io connects to your CSMS from its cloud runtime while the simulator UI runs in your browser. Connecting to a CSMS requires free magic-link sign-in; Demo Mode works without an account. This guide explains what your endpoint needs to accept.
Endpoint requirements
- The endpoint must use
wss://(secure WebSocket). Plainws://is only permitted forlocalhostduring local development. - It must accept the
ocpp1.6orocpp2.0.1WebSocket subprotocol during the handshake. - It must be reachable from Chargeflux's hosted runtime. Private or internal-only endpoints need a future private runner or a public test endpoint.
- The station identity must match what the CSMS expects, typically as the last path segment of the URL.
Browser limitations
The OCPP WebSocket is not opened by the browser tab. Browser-only constraints such as mixed content blocking, immutable Origin headers and client-certificate prompts do not apply to the hosted connection path.
Supported authentication
The current free simulator focuses on common station identity and URL-based setup:
- No authentication.
- Station identity in the URL path.
- A token in the query string.
Putting a token in a URL can expose it through browser history, CSMS logs or copied screenshots. The simulator warns you when a URL contains a token.
Still limited in the proof of concept
The hosted simulator is not a private network runner or a fleet-scale load-testing tool. Private runner work is tracked on the roadmap for endpoints that require:
- Private network access or a source-IP allowlist.
Pro supports always-on stations and CI/CD automation through the REST API and MCP server.
If a connection fails, see troubleshooting WebSocket connections.
Next: run a real OCPP 1.6 path
Once the endpoint accepts the handshake, walk BootNotification and a short session on the OCPP 1.6 simulator. For dual-stack backends, also cover the OCPP 2.0.1 simulator. First UI steps: getting started.
Last reviewed August 2026 · Chargeflux.io