Energy

Anything that exposes its readings over a standard interface. LoRaWAN energy meters, current clamps and pulse counters arrive through The Things Stack, ChirpStack or LORIOT, and the Thinger.io Marketplace already has plugins with payload decoders for several of them. Wi-Fi and cellular devices speak MQTT or HTTP directly.

Wired equipment is read at the edge. A small gateway running the Node-RED plugin or the Thinger.io Linux client polls Modbus RTU or TCP registers on meters, PV inverters, battery systems and EV chargers, and M-Bus converters bring heat, gas and water meters in with them. The device keeps working as before; the platform simply starts reading it.

The utility meter tells you how much the whole site used. Sub-meters on floors, production lines, tenants or large machines tell you where it went. That breakdown is the basis of any energy management system, including ISO 50001: you cannot improve a significant energy use you cannot see.

Sub-metering also turns energy into a cost each department or tenant can own. When the bill is split by measured use instead of square metres, consumption drops on its own. For tenant billing, pick meters with MID approval; for internal allocation and efficiency work, a well installed current clamp is often enough.

Many electricity tariffs measure demand as the average power over a short integration period, commonly 15 minutes in Europe, and charge extra when it exceeds the contracted power. The peak is set by a few minutes of coincident loads, such as compressors, ovens, HVAC and EV chargers starting together.

With readings every few seconds, the platform projects the current quarter hour, compares it with the contracted power and raises an alarm while there is still time to act. A rule or an operator can then defer non-critical loads, for example throttling chargers or pausing water heaters, so the peak never lands on the invoice.

Yes. Most PV inverters expose AC power, daily yield, string voltages and currents and fault codes over Modbus TCP, many following the SunSpec register maps, and hybrid inverters and battery systems add state of charge and charge or discharge power. A meter at the grid connection point completes the picture with import and export.

With those three flows in one data bucket, dashboards show self-consumption (the share of PV used on site), self-sufficiency (the share of demand covered by PV) and the yield of each string, so an underperforming string or a tripped inverter shows up the same day instead of at the annual review.

Yes, as a monitoring layer. In a secondary substation, an RTU or gateway reads the top oil temperature probe, the transformer load through current transformers, LV feeder meters and door or fault contacts, and reports over 4G or the utility's own network. The platform stores the history, draws load and temperature trends and raises alarms on overloads, hot transformers or lost communications.

Protection stays where it belongs, in the relays and switchgear on site. Thinger.io adds visibility across many substations, so maintenance can be planned on measured load and temperature instead of fixed rounds.

Yes, and most projects do. Thinger.io exposes every stored reading through a REST API, pushes events through webhooks and exports data buckets to CSV, so measured data can feed an existing SCADA historian, energy management system, BMS or billing platform. The built-in Node-RED plugin bridges industrial protocols such as Modbus and OPC UA in both directions, so the platform adds the sites and meters your current tools do not reach without replacing them.

Both are common. Cloud instances start fast and need no server administration, which suits pilots, ESCOs and multi-site portfolios. Private cloud or fully on premise deployments keep metering data inside your own infrastructure, which some utilities and critical infrastructure policies require. Thinger.io runs identically in every mode, with EU data residency and managed backups available.

Thinger.io is an ISO 27001 certified company. Devices connect over authenticated, encrypted channels, with per-device certificates over mutual TLS where the hardware supports it, and users sign in with MFA or single sign-on (OIDC). White label branding lets an energy service company run the platform under its own name, with each customer's sites kept separate.

It depends on the number of sites and meters, the hardware already installed and the integration work, so most projects are quoted individually. Existing meters with Modbus or M-Bus outputs usually only need a gateway, which keeps the hardware cost low. On the platform side, our Private Cloud plans are published on the pricing page and start at 49 euros per month for a dedicated instance, which is usually enough to run a first pilot. Enterprise and on premise deployments are sized per project.