OCPI & Roaming

Q: How do I connect to roaming partners like Hubject?
A: Set up credentials and roles in the OCPI dashboard. Ensure /versions, /credentials, and /locations endpoints are active.

Q: Why is the MSP shown as 'Unknown' in roaming sessions?
A: This indicates missing or invalid party_id in the OCPI payload. Verify credential exchange and mappings.

Q: How does fallback work when real-time RFID auth fails?
A: eMabler checks the driver database, then custom real-time auth (if enabled), and finally OCPI. For proper fallback, ensure real-time integrations don’t suppress this behavior.

Q: What does “Split EVSE by Socket” do?
A: It changes how charging sockets are represented in OCPI. When enabled, each socket is treated as its own EVSE with a unique ID. For example, if a charger has ID XXXX and two sockets, partners will see them as XXXX01 and XXXX02. If disabled, all sockets share the same EVSE ID (XXXX). For chargers with only one socket, there is no practical difference. For chargers with multiple sockets, this is required for them to work properly in OCPI. This field should be set before adding the charger to the integration, because changing it afterwards would change the socket identity for the OCPI partner.