Modbus ⇄ MQTT gateway

Publish your Modbus registers over MQTT to the cloud — and receive commands back.

The problem

Your PLCs, inverters, drives and meters speak Modbus (RTU over RS485 or TCP/IP) and stay confined to the local bus. IoT platforms, dashboards and the cloud consume MQTT / JSON. Without a bridge, this data never leaves the installation.

How the WBox does it

The WBox publishes Modbus registers as JSON over MQTT to the cloud

The WBox gateway reads Modbus registers (RTU/TCP, master or slave) and publishes them as JSON messages over MQTT to the broker of your choice — private or public cloud. A transformation (scaling, unit, type) prepares the value before publication.

The bridge is bidirectional: an inbound MQTT message can write a Modbus register (command, setpoint). The WBox acts as an MQTT broker or client. Publication frequency, hysteresis and a consistency check keep the network from being flooded.

What you need

The same principle applies: the upload can target Azure, AWS or Google Cloud, and Modbus meters can also be pushed to the cloud.

Try the live demo → See inter-protocol routing → Documentation (wiki) →