OCPP parameter reference

OCPP parameter table

Parameter overview for OCPP 1.6 on Charge Controller, including Config UI mappings, scopes, defaults, and vendor extensions

OCPP parameter catalog

Parameter overview for OCPP 1.6 on Charge Controller, including Config UI mappings, scopes, defaults, and vendor extensions

1. OCPP-related configuration parameters

Category	Parameter	Purpose	Info
# General Connectivity	Connection Type	Physical connection method for OCPP Backend communication	Defines the preferred connection method. If both Ethernet and GSM are active, Ethernet is always used automatically. If no Backend is configured, no OCPP communication occurs.
	Backend Communication Type	Select communication protocol (e.g. OCPP 1.6)	Defines the backend communication protocol and version. Required to enable OCPP communication.
	Backend Host	Backend host address (domain/IP)	Base endpoint for all backend requests. Must be reachable via selected connection type. Use domain names where possible (see More).
	Backend Port	Backend port for OCPP connection	Usually 80/443 or the backend's custom port. Ensure firewall rules allow outbound connections.
	OCPP Protocol	Select protocol: ws:// or wss://	Use wss:// for TLS. For strict TLS verification, ensure hostnames match certificates. For testing, allow non-strict verification (see More).
	Backend Host Path	Path segment appended to OCPP URL	Used to match backend routing conventions (e.g. /ocpp16). Must match backend expectations.
	OCPP ChargeBoxIdentity (ChargePointID)	Identifier used to register the station with the backend	Must be unique. Often used in backend provisioning. Used in WebSocket URL and backend authentication flows.
	Backend Communication Timeout	Timeout for backend communication attempts	If too low, could cause frequent disconnects on unstable networks. If too high, may delay failure detection. Use with watchdog settings (see More).
	TCP Watchdog Timeout	Detect TCP-level inactivity	Helps detect "dead" connections even when TCP stays open. Too low may cause false positives, too high delays detection. See More.
	OCPP Keep-alive Interval	Interval for backend keep-alive checks (e.g. WebSocket ping)	Used to keep connections stable and detect stalls. Impacts reconnect behavior (see More).
# OCPP Traffic	Queue Size	Maximum OCPP message queue size	If full, additional messages are dropped and the connection may reset depending on implementation. See More.
	OCPP Transaction Message Retry Count	Retry count for Start/StopTransaction (and related)	Controls resilience during backend outages. Too low risks lost transactions. Too high may spam backend. See More.
	Number of Eichrecht transaction message attempts	Retry attempts for Eichrecht-protected transaction messages	Eichrecht mode may enforce additional attempts and/or blocking logic. See More.
# StatusNotification	Send informative StatusNotifications	Send additional informative status notifications	Useful for backend monitoring/diagnostics but may be noisy. See More.
	Send error StatusNotifications	Send error status notifications	Enables more detailed error reporting through OCPP. See More.
	Send USB error StatusNotifications	Report USB-specific errors via StatusNotification	Useful when USB metering or attached devices fail. See More.
# Meter Values	Retransmit MeterValues	Retransmit MeterValues on backend reconnect	Helps backends receive missed meter values after disconnects. See More.