YOUR CHARGING NETWORK
Charger routing
Keep your endpoints. Choose your CMS.
Your chargers 0
Mappings apply when a charger next connects.
A stable address for every charger. Remapping keeps existing connections on their current CMS. Schedule reconnection after charging sessions finish.
Add the exact OCPP endpoint supplied by your CMS provider. Use {chargerId} where the CMS charger ID should be inserted.
Configuration history
The latest 50 changes to your network.
Add your CMS destination
Get the OCPP URL and credentials from Pulse Energy or your CMS provider. Save the endpoint under CMS destinations.
wss://your-cms.example/ocpp/{chargerId}Illustrative format. Your provider supplies the real URL.
Register your charger
Add its ID, OCPP version and CMS mapping. Use the CMS charger ID field if the upstream provider knows it by a different ID.
Choose whether Pulse receives the charger’s credentials, separate CMS credentials, or no Basic authentication.
Configure the charger once
Copy its gateway URL into the charger’s OCPP server setting. Configure the charger ID as its Basic authentication username and use the password shown when you register it.
Some chargers append their ID automatically. In that case enter only the gateway base URL ending in /ocpp.
Remap when you’re ready
Edit a charger to select another CMS. Wait until it is idle, then arrange reconnection through your current CMS or charger management tools.
Pausing blocks new connections. Existing sessions continue on their current connection. Historical transactions and billing data require a separate migration.
This gateway supports OCPP 1.6J and 2.0.1 over secure WebSockets with Basic authentication. SOAP and charger/client certificate authentication are not implemented. Confirm compatibility with your hardware and Pulse before fleet rollout. For a permanent production endpoint, attach a domain you own in Cloudflare.