Skip to main content

Modbus integration

Modbus remains the workhorse for power meters, VFDs, and packaged plant. Open IoT Hub ingests holding and input registers into the same point model used by BACnet and MQTT.

Transports

  • Modbus TCP — one TCP connection per device or serial gateway; default port 502
  • Modbus RTU — RS-485 through a gateway; configure baud, parity, and response timeout

Register mapping

Import a CSV with columns device_id, function, address, length, data_type, scale, and unit. Supported data types include UINT16, INT16, UINT32, FLOAT32 (with explicit endianness).

# Validate TCP reachability from the compose host
docker-compose exec web sh -c 'nc -zv meter.local 502'

Polling discipline

Group registers into blocks to minimise round trips. Respect vendor maximum request sizes — many meters allow only 12–20 registers per read. Stagger devices to avoid RS-485 collisions on multi-drop RTU buses.

Energy use cases

Typical integrations include main incomer kWh, sub-meter feeds for tenant rebilling, and VFD power for fan-coil diagnostics. Pair Modbus trends with dashboard templates in the gallery and review licensing if you redistribute analytics to clients.

Safety

  • Disable coil writes unless the integrator owns the safety narrative.
  • Log raw frames at debug level only — disable in production.
  • Use read-only service accounts on shared serial buses.

Next steps

Explore a running stack, review the open source repositories, estimate ROI for a deployment, or talk with the CONTEXUS team about integration and licensing.

Module licensing details are summarised on /licensing. Browse reference dashboards in the gallery.