MQTT Protocol — Lightweight IoT Messaging | EC.DATA

MQTT Protocol for IoT

Lightweight publish/subscribe messaging for IoT energy monitoring.

MQTT Fundamentals

• Pub/Sub model — decoupled publishers and subscribers via a central broker
• Topic hierarchy — structured paths like building/floor/meter/energy
• QoS levels — QoS 0 (at most once), QoS 1 (at least once), QoS 2 (exactly once)
• Retained messages — last known value stored on broker for new subscribers
• Last Will and Testament — automatic notification when a device disconnects

Energy Monitoring Pattern

EC.Node publishes meter readings to topic ec-data/site-id/meter-id/telemetry at QoS 1. The cloud broker processes messages and writes to the time-series database within 5 seconds.

Mqtt in practice

MQTT 3.1.1 / 5.0 with QoS 1 retained messages is how EC.DATA moves telemetry from the field to the cloud. The EC.Node broker enforces TLS 1.3 mTLS and per-device ACLs so a compromised gateway cannot impersonate a meter.

How EC.DATA operationalises Mqtt

EC.Node — EC.DATA's edge gateway — implements Mqtt as a first-class adapter. Provisioning is point-and-click in EC.IoT: select the protocol, choose the brand from the device library, and the gateway streams normalised tags into EC.EMS within minutes. mTLS, certificate pinning, and per-device ACLs are enforced by default so a compromised gateway cannot impersonate another.

For protocol-level troubleshooting, EC.Node ships a packet capture mode that records Mqtt traffic to a rolling buffer, downloadable from EC.IoT for forensic analysis. Most field teams resolve Mqtt issues with the capture without needing a Wireshark install on a customer LAN.

Common pitfalls when working with Mqtt

Mqtt pitfalls almost always trace back to physical-layer issues, not protocol bugs. A field technician should suspect wiring, termination, and addressing before reaching for a packet capture.

• Bus topology violations (star instead of daisy-chain on RS-485) cause intermittent reads that look like firmware bugs.
• Address collisions on Modbus and BACnet manifest as missing devices rather than errors — the silently lost device is the dangerous one.
• Outbound-only firewall rules from the customer LAN often block return traffic; EC.Node uses outbound-only TLS to avoid this entirely.
• Cellular APN misconfiguration produces a connected modem with no usable data path; always validate IP reachability, not just RSSI.

Where Mqtt connects across EC.DATA

Mqtt touches every layer of the EC.DATA stack: telemetry capture in EC.Node; visualisation and alerting in EC.EMS with EC.Alerts; tariff translation in EC.Bills; savings verification in EC.GAIA; and field-device fleet governance in EC.IoT. Solution work originates in EC.Solution Design Studio; partner and customer training live in EC.Academy.

Frequently asked questions about Mqtt

How does EC.DATA expose Mqtt to partners?

EC.Node implements Mqtt as a built-in adapter; provisioning takes minutes from EC.IoT, no firmware build required.

Do I need a separate license to access Mqtt?

No. Mqtt is part of the core EC.DATA platform; partners get it as part of their standard licence and white-label it under their own brand for their customers.

Where do I learn more about Mqtt on EC.DATA?

Start with the EC.Academy track this page belongs to, then explore the related EC.DATA platform modules linked above. The EC.DATA changelog announces new capabilities and the EC.Academy session catalogue tracks every recorded session.

How EC.DATA applies this in production

The concepts in this lesson are not theoretical — they are operationalised every day inside the EC.DATA platform across deployments in 10+ countries on 3 continents. The module most directly tied to this track is EC.Node, working alongside EC.BMS and EC.IoT to translate the underlying physics, protocols, and methodology into a working production system.

Every reading in EC.DATA flows through the same lifecycle: telemetry is captured at the meter or sensor, normalised by the EC.Node edge gateway (which speaks Modbus RTU/TCP, BACnet, OPC-UA, MQTT and pulse counting natively), buffered locally for offline resilience, then delivered to the cloud where EC.EMS stores it as 1-minute resolution time-series. From there, EC.Bills reconciles metered kWh against the utility invoice, EC.Billing allocates consumption to tenants or cost centres, EC.Alerts watches for anomalies, EC.PQ scrutinises waveform quality, and EC.GAIA applies machine learning for forecasting and root-cause analysis.

That integration is what differentiates EC.DATA from the patchwork of disconnected tools most facilities run today. Because every module shares the same data warehouse and the same role-based permission layer, a finding in one module is immediately actionable in another — a tariff change in EC.Bills can adjust demand-alert thresholds in EC.Alerts, a setpoint override in EC.BMS is automatically measured for energy impact in EC.EMS, and an IPMVP baseline is established once and reused across reports forever.

The team behind EC.DATA — described in more depth on the Who We Are page — combines former Fortune 500 energy consultants, field commissioning engineers, and software developers, with a deliberate hiring policy that requires every senior product role to have prior experience on the customer side of an energy programme. The platform is what we wish had existed when we ran those programmes ourselves; the academy is the public-domain version of the training material we built internally to bring new hires up to speed.

If you want to see the platform in action, the free assessment, the savings calculator, and the Solution Design Studio are open without an account; the partner programme is the route in for ESCOs, facility-management firms, commissioning agents, and utilities that want to deliver EC.DATA under their own brand.