Generation against load
Inverter output, building consumption and grid import appear on one timeline in the same units.
Solution
Energy and Solar
Inverters, sub-meters and the incoming supply all speak Modbus or MQTT with different register layouts. IoTServa normalizes them so energy balances can be read, not rebuilt.
- Modbus
- MQTT
The Problem on Site
Solar output, building load and grid import are measured by different devices with different units and timestamps. Reconciling them by hand each month hides losses and faults between the meters.
Typical Equipment
- Solar inverters and data loggers
- Three-phase and clamp energy meters
- Battery and generator controllers
- Weather and irradiance sensors
- Grid-side protection meters
What You Get to See
Faults found early
An inverter reading low against its neighbours shows up in the data before the monthly report.
Clean sub-metering
Tenant and department consumption is attributed from the same history that drives dashboards.
Export for reporting
Interval data leaves as CSV or through the API for billing and sustainability reports.
Protocols in This Setup
Each one is read natively and joins the same tag model.
Where We Suggest the Pilot Starts
Start with the main incomer, the inverters and two sub-meters. Add irradiance if you want to compare output against expectation.
Questions for This Setup
Does IoTServa produce billing-grade data?
IoTServa records what the meters report. Billing-grade accuracy depends on the meters and your tariff process, not on the platform.
Can it read different inverter brands?
Yes, through one device profile per model. Brands that expose Modbus or MQTT can share the same tag names.
Show Us the Energy and Solar Equipment. We Will Scope the Pilot.
Tell us which protocols are on site. We will scope a pilot that reads your real devices.