JouloDocs
Integrations

KEBA

How a KEBA KeContact connects to Joulo over OCPP, which series can reach a backend, and where MID sits in the article number.

KEBA splits by series, not by brand. Whether your KeContact can reach Joulo depends on the series. Whether it has a MID meter is a separate question, answered by the article number.

At a glance

PropertyValue
RouteOCPP 1.6J, on the supported series below
Endpointwss://ocpp.joulo.nl/{chargePointId}
AuthenticationOCPP basic auth
SyncLive, over the WebSocket
MID detectionCharacter IX of the article number
BackfillSessions from the moment the charger connects

Which series can connect

SeriesReaches a backendMID
P30 a-seriesNo, offline basic modelNo
P30 b-seriesNoNo
P30 c-seriesNo, Modbus TCP and UDP onlyOptional
P30 x-seriesYes, OCPP 1.6JOptional
P40 and P40 ProYes, OCPPOptional

The c-series is the trap. KEBA's own comparison table shows a tick for OCPP on the c-series. There it is a client: up to fifteen c-series units sit behind an x-series that acts as master and OCPP hub. A c-series has no field for a backend URL, so Joulo can never reach it directly. Joulo does not sell that master setup as a route.

MID is a variant, not a series

MID sits in character IX of the article number, directly after the second hyphen:

CharacterMeaning
MMID, under 2014/32/EU
LMID plus Eichrecht
EMeter without MID
0No meter

This holds for the c-series and the x-series alike. "An x-series is always MID" is folklore, and buying one on that assumption is how people end up with a charger they cannot register.

What Joulo reads

Joulo stores start and stop transactions and the energy register samples that arrive during a session. Every frame is archived for support and disputes.

Limitations

  • The c-series cannot reach Joulo on its own. Check your series before you plan a connection.
  • Third-party software that reads the charger over Modbus and forwards it is not a valid measurement source for ERE registration. The certified meter has to be the source.

Next steps