Most energy meters measure. Very few of them communicate in a way a modern cloud dashboard actually wants. The gap between a traditional industrial meter (RS485, polled once every 15 minutes by a local gateway) and an IoT energy meter (WiFi or Ethernet to the cloud, publishing via MQTT at an interval you configure) is wider than it sounds. It's the difference between every facility running its own polling server, and many facilities reporting to a single web dashboard with alerts.
What is an IoT energy meter?
An IoT energy meter is a smart energy meter with built-in internet connectivity — WiFi, Ethernet, or cellular — that publishes energy data to cloud platforms in real time without requiring a separate gateway, data concentrator, or polling server. Unlike traditional meters that only support local protocols (Modbus RTU over RS485) and rely on external infrastructure to reach the internet, an IoT energy meter is internet-native: it carries its own TCP/IP stack, supports modern protocols like MQTT and HTTPS, and can be commissioned directly from a smartphone.
A true IoT energy meter ships with:
- IP connectivity built in — WiFi, Ethernet, or both. No gateway hardware.
- MQTT or HTTPS publishing — data flows out to any broker or cloud API directly.
- On-device logging — when internet drops, the meter keeps recording and syncs on reconnect.
- OTA firmware updates — no site visits required to patch or upgrade.
- Configuration over the network — remote commissioning, not a laptop and a USB cable.
Not every meter marketed as “IoT” does all five. Some are traditional Modbus meters with a bolted-on WiFi module and no edge intelligence — functionally identical to a gateway. When evaluating, check all five items explicitly.
IoT energy meter vs. traditional meter + gateway
The traditional deployment model in Indian factories for the last 20 years has been energy meters chained on RS485, polled by a central gateway that pushes data to a BMS, SCADA, or cloud server. This stack works, but has real disadvantages:
- Polling latency. A 15-minute polling cycle means any event shorter than 15 minutes is missed or smoothed into an average.
- Single point of failure. If the gateway crashes, every meter downstream goes offline.
- Commissioning overhead. Each meter's Modbus address has to be set and the gateway polling schedule configured and maintained.
- Extra hardware. The gateway is one more device to buy, power, license where applicable, and maintain.
- Physical wiring. RS485 cable has to be pulled from each meter to the gateway.
The IoT energy meter model replaces this stack with meters that connect directly to the facility WiFi or LAN, publish data to a cloud MQTT broker or an API, and need no gateway. The benefits are data at the interval you choose rather than the gateway's polling cycle, distributed resilience (one meter down doesn't take others with it), and simpler commissioning.
When comparing the two, cost the whole stack, not just the meters: gateway hardware, any software licences, wiring, and the maintenance of the extra device. And check what data granularity each design gives you — a gateway's polling cycle sets the floor on how finely you can see events.
How MQTT and WiFi enable real-time monitoring
MQTT (Message Queuing Telemetry Transport) is a publish-subscribe protocol designed specifically for low-bandwidth, high-latency, and constrained-device scenarios. Three elements matter for IoT energy metering: the meter publishes on its own schedule rather than waiting to be polled; hierarchical topics that let dashboards subscribe to exactly the data they need; and QoS levels that support reliable delivery with local buffering during outages.
WiFi as the transport layer has one key advantage for Indian factories: it's often already installed. Where a building has WiFi coverage, adding another IoT energy meter needs little or no new network infrastructure. For sub-panels deep inside switchgear rooms where WiFi coverage is weak, Ethernet is the fallback.
Deployment patterns
- Factory sub-metering. Feeder- and machine-level meters on facility WiFi or Ethernet, with no gateway to configure.
- Multi-site industrial portfolio. 5+ sites aggregated into a single portfolio dashboard without site-by-site gateway provisioning.
- Commercial building tenant sub-billing. One meter per tenant; monthly billing reports generate from cloud data.
- OEM integration. Machine builders embed IoT energy meters into their products to offer energy-as-a-feature.
- EV charging infrastructure. Class 0.5S IoT meters on the AC feed to chargers. See our EV charging metering solution.
- Remote / unmanned sites. Telecom towers, pump stations, retail stores — meter joins a mobile hotspot or existing Ethernet.
Security considerations
Adding internet connectivity to a meter creates attack surface. Good IoT energy meters address this explicitly: TLS-encrypted transport, signed firmware updates, role-based access, and the option to disable services you don't use. For regulated industries, an air-gapped configuration with an on-premises MQTT broker inside the facility network — rather than a public cloud — is often preferred. Good IoT energy meters support both deployment models with the same hardware.
Where Titan fits
Titan is a Class 0.5S (IEC 62053-22) 3-phase IoT energy meter with WiFi, Ethernet and RS485 built in. It publishes over MQTT (to your own broker, or directly to AWS IoT Core or Azure IoT Hub) or HTTP/HTTPS push at a configurable interval, answers Modbus TCP and BACnet/IP on the network, and uses its RS485 port for either Modbus RTU or BACnet MS/TP (one at a time, selected at set-up). Modbus and MQTT run simultaneously. It also has an on-device REST API for provisioning, OTA firmware updates, and relay and pulse outputs. The register map and MQTT topics are published in our open titan-integration repository; for a walkthrough, see how to get energy meter data into your software.
Designed and manufactured in-house at our 7.5-acre facility. For sizing a deployment, use our energy meter sizing calculator. For the end-to-end monitoring stack, see the IoT energy meter solution.