Skip to main content

Charger's OCPP Source

J
Written by Juhan Harm

In the VOOL charger’s configuration panel, you can set the OCPP source. This setting determines whether the charger connects directly to the VOOL OCPP server or through the LMC.

Guidelines:

  • If the charger doesn't have its own internet connection but the LMC does, the OCPP source should be set to "LMC."

  • On the other hand, if the charger has its own internet connection (LAN, Wi-Fi or 4G), the OCPP source should be set to "Internal."

Access the Configuration panel on the charger detail view:

Then, check the Settings module:

Change the parameter value:

If the OCPP source is set wrong

An incorrect OCPP source usually shows up as one of these:

  • The charger sits in Suspended by charger and never starts a scheduled or price-based session.

  • The portal reports error_charger_lmc_communication_not_ok.

  • Immediate charging still works — which is what makes this easy to misread as a smart-charging problem rather than a connectivity one.

Two things to check when the source is set to LMC but the charger still cannot reach it:

  • Same network segment. The charger finds the LMC over mDNS, which does not cross subnets or VLANs. Both devices have to sit on the same segment.

  • Static addresses. Give the charger and the LMC static IP addresses. If the router reassigns an address, the link drops and the charger falls back to the symptoms above.

The exact notices you will see

When a charger is reaching the OCPP server directly but its OCPP source is still set to LMC, the portal shows:

The charger is directly connected to the OCPP server, but the OCPP source is set to LMC.

That combination is invalid. Either set the OCPP source to Internal, because the charger has its own internet connection, or fix the connection so it genuinely goes through the LMC. This notice was worded differently before March 2026, so an installer quoting slightly different words is describing the same thing.

A second notice, OCPP connection issue, is raised when a second OCPP connection is attempted for the same charger, or when the OCPP version does not match the charger's OCPP source.

Who can see these notices: they appear to installers, to VOOL administrators, and in the Partner Portal. Workspace owners and admins do not see them — which is why a customer often cannot find the message support is describing to them.

Did this answer your question?