The VOOL LMC exposes a Modbus TCP interface for local integrations — reading site measurements into a home-automation system such as Home Assistant, or into a building management system. This is separate from the charger's own Modbus interface, which is documented in the Charger Modbus manual.
Enabling it
Modbus TCP on the LMC is disabled by default. Three settings control it:
Enable — turns the interface on.
Port — the TCP port it listens on.
Write enable — separate from reading, so you can allow monitoring without allowing control.
The interface binds to the local network only; it is not reachable from the internet. It is available on recent LMC firmware, so if you cannot find the settings, check that the LMC is up to date.
If you would rather not configure it yourself, send us the LMC serial number at [email protected] and we can enable it remotely, usually within a working day. Tell us whether you need read-only access or read and write.
Modbus has no authentication. Anything on the same network can read the interface, and if writes are enabled, control charging through it. Only enable it on a network you trust, and leave writes off unless you actually need them.
Register documentation
The LMC register map is not published here yet. Ask us and we will send it — tell us what you are building and we can point you at the right registers.
If a working integration stops responding
Check the device's current IP address first. After a firmware update or a router change, the LMC's local IP can change. The current address is visible in the web portal.
Set a static IP — or a DHCP reservation in the router — for the LMC and the chargers. This is worth doing regardless: it also prevents the LMC losing sight of its chargers.
Confirm the polling machine is on the same subnet. Modbus does not cross subnets or VLANs.
Other integration routes
Modbus and OCPP are the documented integration paths. Third-party Home Assistant integrations exist but are not built or maintained by VOOL, and some do not work with the LMC without adjustment. For partner or developer API questions, email us with your questions numbered.