If the VOOL mobile app shows "Configuration issue detected", the app has noticed that something in the site's setup is not right — most often the load management configuration. It is a notification, not a fault code, and it does not mean the charger is broken.
This notification was introduced in VOOL mobile app version 3.19.0. Its purpose is to tell you early that a setting needs attention, so it can be fixed before it starts interrupting your charging.
If you are the charger's user
Configuration is set during installation, and changing it needs the installer or admin role. So the action here is short:
Contact the company that installed your charger, or your site administrator, and tell them the app is reporting a configuration issue.
If charging is also being interrupted, mention that — it helps them prioritise.
You can keep using the charger in the meantime. Immediate charging usually still works even when load management is misconfigured, which is exactly why the notification exists: without it, the problem stays invisible until a scheduled or price-based session fails.
If you are an installer, admin or owner
Use Health Status in the VOOL Portal to find out which configuration issue the app is referring to. Open the site and click Health Status.
Health Status identifies:
Outdated firmware
Load management configuration issues
Weak connections
Front panel malfunctions
Under- and over-voltage alarms
Three things worth knowing about the check
It runs when you open it, not continuously. The check polls every device on the site at the moment you ask for it. So after you change a setting, run it again — it will not clear on its own in the background.
Only errors raise the notification. Health Status reports warnings as well as errors, but the app notification is triggered by error-level notices only. A site can show warnings without anyone being notified.
Members cannot see Health Status. If someone says they cannot find it, check their role — it is available to owners, admins and installers.
Finding the actual fix
Health Status names the category rather than the exact fix. Once you know the category, these articles cover the usual causes:
Load management — check the charger's OCPP source first. If the charger has no internet connection of its own but the LMC does, the source must be LMC; if the charger has its own connection, it must be Internal. See Charger's OCPP Source.
Load management, continued — if the LMC and charger disagree about which control channel to use, the charger will reject load management even though both devices look online. This is the commonest error class behind this notification. See Charger–LMC communication: CAN, LAN and control channels.
Weak connections — a charger or LMC on marginal Wi-Fi or a flaky Ethernet run will drop in and out. Assign static IP addresses so a router reassignment does not silently break the link.
Front panel — almost always a contact problem rather than a failed panel. Check that the bottom edge of the panel sits flush against the housing before replacing anything. See Front Panel LED Light Troubleshooting.
If you need to report it to us
Send us the serial number of the charger and of the LMC, what Health Status reports, and whether charging is being interrupted or only the notification is showing. Those three things let us look at the right device straight away instead of asking you to check things onsite.