MQTT Integration
Publish energy data to any MQTT broker with TLS encryption. The lightweight messaging protocol built for IoT.
Why MQTT for Energy Data?
MQTT (Message Queuing Telemetry Transport) is the de facto standard for IoT messaging. Designed for constrained networks and low-bandwidth environments, it uses a publish-subscribe model that decouples data producers from consumers. This makes it ideal for energy monitoring deployments where hundreds of data points need to flow reliably from meters to cloud platforms, databases, or analytics engines.
Unlike polling-based protocols, MQTT pushes data the instant it is available, giving you real-time visibility into energy consumption across your entire estate.
How It Works with EpiSensor
EpiSensor wireless sensors communicate over ZigBee to the ZGW-10 Gateway, which acts as the central data hub. The gateway's built-in MQTT client publishes structured JSON payloads to your chosen MQTT broker on configurable topics. Each sensor and measurement type can be mapped to its own topic hierarchy, making downstream filtering and routing straightforward.
The gateway supports MQTT v3.1.1 and v5.0, with TLS 1.2/1.3 encryption and certificate-based authentication. You can connect to cloud-hosted brokers such as HiveMQ, EMQX, or Mosquitto, or to the native MQTT endpoints on AWS IoT Core, Azure IoT Hub, and Google Cloud IoT. Quality of Service levels 0, 1, and 2 are fully supported, with local message buffering to handle intermittent connectivity.
Key Features
TLS Encryption
Secure all data in transit with TLS 1.2/1.3 and mutual certificate authentication. Upload custom CA certificates directly through the gateway interface.
Flexible Topic Mapping
Define custom topic hierarchies per sensor, per measurement type, or per site. Use template variables for dynamic topic generation across large deployments.
QoS 0, 1, and 2
Choose the quality of service level that matches your requirements, from fire-and-forget to guaranteed exactly-once delivery.
Local Buffering
If the network drops, the gateway buffers messages locally and publishes them when connectivity is restored. No data is lost.
JSON Payloads
Data is published in clean, structured JSON format with timestamps, unit labels, and sensor metadata, ready for direct ingestion by any platform.
Multiple Broker Support
Publish to multiple MQTT brokers simultaneously. Send data to both your local SCADA system and a cloud analytics platform from a single gateway.
Use Cases
Real-Time Energy Dashboards
Stream live consumption data to Grafana, Kibana, or custom dashboards via an MQTT broker. Visualise power, voltage, and current across hundreds of circuits with sub-minute latency.
Cloud Data Pipelines
Feed energy data into cloud-native ingestion services like AWS IoT Core or Azure Event Hubs using their native MQTT endpoints. Build serverless processing pipelines without custom middleware.
Multi-Site Aggregation
Collect data from gateways across dozens of sites into a single MQTT broker. Use topic-based routing to organise data by region, building, or tenant for portfolio-level analytics.
Getting Started
Configuring MQTT on the EpiSensor gateway takes just a few steps. From the gateway's web interface or via the Core management platform, enter your broker address, port, and credentials. Upload TLS certificates if required. Select the sensors and measurement types you want to publish, define your topic structure, and choose a QoS level. The gateway begins publishing immediately once the connection is established.
For advanced use cases, the Edge visual programming environment lets you transform, filter, or enrich data before it reaches the broker. Add calculated fields, aggregate readings, or apply threshold-based logic -- all without writing code.
Ready to Connect via MQTT?
Talk to our team about integrating EpiSensor with your MQTT infrastructure.