Skip to content
Energy · Component

IoT Metering Gateway

Meter readings arrive from different devices, at different times and in different formats. IoT Metering Gateway validates, deduplicates and buffers that data before handing normalized records to settlement, billing and analytics.

EV & PV readyDeterministic validationBack-pressure & retry

Protocols & integrations

Start with the interfaces already present at your sites: meters, sensors, PV equipment, home controllers and EV chargers.

Modbus TCP/RTUMQTT (brokers & bridges)HTTP/REST & WebhooksWebSocketsOCPP 1.6/2.0 for EV chargersOCPI 2.2 for roaming/back‑officeVendor SDKs (Fronius, Huawei, Sungrow, ABB)Smart‑home gateways (Grenton, Home Assistant)Time‑series & column storesS3‑compatible object storage

Prepare each reading for downstream use

Collection ends with a record another system can use. Validation rules, queues and normalized payloads define what happens before that handoff.

Protocol adaptors

DLMS/COSEM, Modbus and MQTT with pluggable SDK to onboard additional sources.

Validation & quality

Schema checks, deduplication, late/missing read handling and outlier rules.

Back-pressure & buffering

Queueing, retries and dead-letter channels keep data flowing without overload.

Normalized records

Unified payloads for settlement/billing, portals and analytics (time-series + columnar).

Observability

SLIs/SLOs, tracing and dashboards for throughput, latency and quality.

Exposure & APIs

Events/webhooks, query APIs and batch exports for settlement and BI.

Devices we connect

From field devices to back‑office systems - mapped to a clean, normalized model.

Smart meters

Electricity & heat meters with pulse/serial gateways

Sensors

Temperature, humidity, pressure and custom telemetry

Inverters & PV

String & hybrid inverters, production & status

Home controllers

Grenton & other gateways (scenes, relays, inputs)

EV chargers

OCPP‑enabled wallboxes and DC chargers

Sub‑metering

Modbus RTU/TCP slave networks in buildings

Define the boundary between collection and billing

The gateway owns collection and preparation of the reading in a Kubernetes-native pipeline. Settlement, billing and forecasting consume its output and apply their own business rules. Agree the interfaces at those boundaries.

Agree the source contract

For each metering source, define the protocol, reading identifiers and timestamps. The adaptor connection uses the supported transport and access controls.

Define the exception path

Decide how invalid, late or missing readings reach review and reprocessing. Queues and dead-letter handling keep those cases visible before the record is used downstream.

Name the receiving system

Choose the normalized payload, northbound API, mapper or batch export consumed by settlement, billing or analytics. That receiving system owns the calculation or decision that follows.

Common deployments

Different deployments consume the same prepared readings for different operational purposes.

AMI → Settlement

Smart meters feed validated reads into the settlement engine and billing.

DER telemetry

PV/storage telemetry normalized for analytics, alerts and cost allocation.

Municipal portals

Meter/household data exposed to self-service portals and BI dashboards.

Security & operations

Operate the collection boundary with transport security, controlled access and an auditable exception process.

Zero‑trust transport

TLS/mTLS, rotated certificates, cipher policy

Identity & access

OIDC/OAuth2, scoped tokens and per‑tenant quotas

Data protection

Encryption at rest, WORM retention and legal hold

Observability

Structured logs, traces and SLO dashboards

Resilience

Queueing, back‑pressure, retries and dead‑letter review

Compliance hooks

Audit trail and export for regulators

References

Selected deployments and partnerships.

GreenCell
Grenton

Request a demo

Trace a sample reading through its validation result, exception handling and downstream payload.

Talk to an expert

AI Energy Analytics

Explainable forecasts and anomaly detection on normalized data.

See analytics

FAQ

Which devices and protocols are supported?▾

DLMS/COSEM, Modbus TCP/RTU and MQTT brokers out of the box. The adaptor SDK supports integration of additional sources.

How do you ensure data quality?▾

Validation and deduplication at ingress, rules for late/missing reads and outliers, reprocessing flows with audit lineage.

Contact us