Connecting a charging station (OCPP)
How to connect an OCPP-compatible charging station to Optimaatti. Supported versions: OCPP 1.6J and 2.0.1 — the protocol version is negotiated automatically, no manual selection needed on the station.
Prerequisites
- A charging station supporting OCPP 1.6J or 2.0.1 (WebSocket / OCPP-J).
- Network access from the station to the internet (cloud) or to the same LAN as an EvEdge server.
- Access to the station's own management panel (usually a web UI at the station's IP).
- An Optimaatti account and a household to attach the station to.
Pairing details from Optimaatti
Open Optimaatti → Charge points → Add charge point. The service gives three values to enter on the station:
- Station ID (identity): enter it in the station's "Charge point ID" field.
- Connection address: in the form wss://<host>/ocpp/<id> → the station's "Central system URL". If it won't connect, try the address without the ID path segment.
- Pairing token: the station's "AuthorizationKey" / Basic Auth password. Copy it immediately — shown only once. You can rotate it if needed.
Station OCPP settings (recommended)
The most important settings on a typical OCPP 1.6 station. Names match the standard OCPP keys; your station may show a subset.
- OcppSecurityProfile: use 1 (ws) or 2 (wss, recommended). Do not use 0 on a public network.
- HeartbeatInterval 240, WebSocketPingInterval 10: keeps the connection alive through NAT/firewalls.
- MeterValuesSampledData = Energy.Active.Import.Register, MeterValueSampleInterval 60: required for consumption and savings tracking — without it the energy counter won't grow.
- SupportedFeatureProfiles includes SmartCharging: required for power control (solar, spot and load management).
- AuthorizeRemoteTxRequests False: remote start from Optimaatti works without an extra authorization round.
- FreeModeActive: True = charging without an RFID tag (simplest for home use), False = RFID in use.
- Station's own load management (Master/Slave, Modbus TCP): set to Off when Optimaatti controls charging — two overlapping controllers fight each other.
OCPP 2.0.1 stations
Same three pairing values. Differences:
- The station offers ocpp2.0.1 in the handshake and the server prefers it automatically (2.0.1 > 1.6).
- Settings are configured as Device Model variables (the station vendor's UI handles this): heartbeat, metering interval and measurands as above.
- Optimaatti detects smart charging support automatically after the first connection.
- The charge point list shows an OCPP 2.0.1 badge once negotiation succeeds.
Commissioning checklist
- Station on the network and has an IP address.
- Charge point created in Optimaatti; ID, URL and token saved.
- URL, ID and AuthorizationKey entered on the station, saved and the station rebooted.
- Optimaatti shows the station as Online.
- Test charge: transaction visible in Optimaatti and the energy counter grows.
- Power control test: "Smart charging OK" turns green after the first accepted command.
Troubleshooting
No connection at all
Check the address scheme (ws vs wss), port (443 for wss), DNS and firewall.
Immediate disconnect (401)
Wrong token, or the ID doesn't match the URL path segment. Rotate the token and re-enter both.
Immediate disconnect (400)
The station offers only a subprotocol the server doesn't support. Select OCPP 1.6J or 2.0.1.
Transaction visible but energy = 0
MeterValuesSampledData doesn't include the Energy.Active.Import.Register measurand, or the sampling interval is 0.
"Smart charging not supported"
SmartCharging is missing from the station's SupportedFeatureProfiles, or the station rejects the profile. Check firmware support.
The same guide is available directly in the app: Charge points → Setup guide. There it adapts to your server and pairing details.