Every deployed smart meter today transmits data in this format. The data arrives at the utility head-end, gets translated through middleware, stored in a proprietary database, and sits there. The institutions that could act on it — banks, insurers, grid planners, AI systems — cannot access it without another translation layer that rarely gets built.
What EdgeMeter does differently
EdgeMeter devices transmit every event as structured JSON over MQTTS. No proprietary encoding. No middleware translation. Every consumption event, every payment, every tamper alert arrives as a natively structured data asset — directly compatible with ML pipelines, time-series databases, and stream processors.
The protocol choice is the product decision. MQTTS provides lightweight, secure, publish-subscribe messaging designed for constrained networks. The TLS layer ensures integrity without HTTPS overhead. The JSON payload is self-describing. The data is immediately useful to any modern system.
The leapfrog
Utility procurement specifications worldwide embed IEC 62055/62056 — which mandates DLMS/COSEM and STS. EdgeMeter's dual-stack architecture satisfies every line item while delivering capabilities the spec does not know to ask for. The cost to manufacture dual-stack is the same. The unit economics are the same. But the output is fundamentally different.
A DLMS meter produces binary blobs. An MQTTS meter produces structured data assets. The difference is not a feature. It is a generation.