Real-Time Monitoring

Mirox actively retrieves data from your plants instead of waiting for them to report in, so you always have near-real-time visibility into every installation — and you notice a silent logger the moment it stops responding, not hours later.

Active Data Collection

Real-time monitoring is built on an active collection model. A dedicated edge agent (the Data Scraper) runs for each plant and continuously reaches out to the local devices to pull their latest readings.

Active Retrieval: Mirox connects to your loggers, inverters, meters and storage systems and reads them on a schedule — it never depends on the device choosing to push data
Continuous Operation: Collection runs around the clock to keep your dashboards close to live
Failure Visibility: Because Mirox initiates every read, a device that goes quiet is detected immediately and surfaces as a data-collection issue

This approach gives you current information even from equipment that has no ability to report on its own.

How Mirox Connects to Your Devices

Plants in the field run a wide mix of hardware, so Mirox connects to each device family through a purpose-built adapter rather than a single generic protocol. Each adapter understands one vendor's specific interface — its login flow, its data format and its quirks — and translates the readings into the common Mirox metric vocabulary.

Adapters already exist for many common device families, including:

Data loggers such as Bluelog, Huawei SmartLogger and Sungrow loggers
Inverter controllers such as SMA Sunny Central and SMA Power Manager
Power-quality meters such as Janitza
Controllers and PLCs such as Phoenix Contact and Dexcon
Battery storage systems such as FREQCON BESS
On-site historians and monitoring servers, including SQL Server based historians and PRTG
File and object stores holding exported readings (S3-compatible storage and local files)
Weather and irradiance sources that supplement on-site measurements

We can adapt to your hardware

If your plant uses a device family that is not yet covered, we can build a new adapter for it on request. The adapter library grows with the equipment our customers run — you are not limited to a fixed protocol list.

Not every logger is plug-and-play

A dozen device families support fully automated, zero-configuration onboarding today — including Janitza, Huawei SmartLogger, Fronius and Solar-Log — and the set keeps growing. Generic loggers are onboarded through an interactive mapping setup with the relevant connection details. Mirox does not auto-discover arbitrary loggers without configuration.

What Mirox Measures

Mirox normalizes everything it reads into one consistent metric catalog covering generation, storage, environment and infrastructure — currently well over 370 distinct measurements spanning grid and AC output, inverter and combiner-box (GAK) values, string-level readings, battery box/module/cell values, weather inputs and agent health. Component-level labels (per inverter, per string, per battery module) let you drill from a whole-plant figure down to an individual device.

Components are auto-discovered: as readings arrive, Mirox infers the plant's inverters, combiner boxes, strings and battery hierarchy from the data stream and builds the component tree for you, without manual entry.

Data Processing Pipeline

Once a reading is collected, it passes through a consistent set of steps before it reaches your dashboards:

Validation: Readings are range-checked, energy counters are confirmed to only ever increase, and frozen or stuck values are flagged
Normalization: Values are converted to standard units (for example kW to W) and a common format
Enrichment: Mirox derives values that are not read directly — such as energy integrated from power, combiner-box aggregates and clear-sky baselines
Storage: The result is recorded in the time-series database for analysis and visualization

This pipeline means data from a Sungrow logger and data from an SQL historian end up indistinguishable to you — same units, same names, same quality checks.

Real-Time Advantages

The active collection model delivers several concrete benefits:

Reduced Latency: You see system changes and events almost as they happen
Higher Reliability: Monitoring does not depend on device-initiated reports that may silently fail
Comprehensive Coverage: Mirox can read devices that have no ability to push data at all
Proactive Monitoring: A communication or device failure is detected the moment a scheduled read does not return the expected data

Monitor Overview

The Monitor page lists every plant you can access in one table — solar, wind and battery side by side — so you can see at a glance which site needs attention. Three columns carry the verdict.

Park State

The first column gives each plant one state, decided in this order — the first that applies wins:

State	When
Inactive	Monitoring is not activated yet — a logger integration, onboarding data or payment information is missing.
Disconnected	The VPN tunnel is offline, the plant network is unreachable, or most of its network devices went down together. It outranks everything below, because a dead link silences every unit behind it.
Alert	A safety alarm is open on a wind turbine or a battery unit, or 30 % or more of the inverters, turbines or battery units are down — in outage, stopped by a fault, or (inverters) with heavily reduced output.
Communication issue	30 % or more of the inverters, turbines or battery units are not communicating.
Warning	More than 5 % of a unit family is down, or no working irradiance sensor is left.
Unknown	Mirox cannot vouch for the plant: no data has arrived yet.
Check	Connected, and nothing open changes the state.

Shares are counted per unit family and weighted by rated power where it is configured, so a large unit counts more than a small one; the worst family decides. Stops that are status rather than faults — a remote pause, environmental or marketer curtailment, a service stop — never count as down.

Each state has its own icon in the column; hover one to read the state and its rule:

Inactive — a grey pause circle
Disconnected — a purple crossed-out Wi-Fi symbol
Alert — a red octagon with an exclamation mark
Communication issue — an amber unplugged plug
Warning — an orange triangle
Unknown — a grey question mark
Check — a green check mark

The column header's filter narrows the table to the states you pick.

Events Column

The Events column answers one question: is anything open on this plant that someone should look at? It shows a number — how many events are open — next to small grey icons for the kinds of event involved (up to six). Click the number to open the list; every row in it leads to the place where that event is handled. An empty cell means nothing is open.

What is counted. Every open event of the plant at level Normal or above (Normal, High, Very high and Critical — see the alarm levels). Safety alarms, device faults, sensor defects and alarm-system events are therefore always included. Events you or a colleague have hidden, and events on components that are hidden, are not counted.

What is left out, and why. The table should state each fact once, and this column should only light up for something that needs attention:

Left out	Why
A unit's own outage, fault stop or lost communication (inverters, turbines, battery units)	The Equipment column right next to it already shows exactly these, with their count.
Park-wide network events — VPN offline, plant network unreachable, many network devices down at once	That is what the Disconnected state says.
String-level findings	They are evaluated per string on the analysis page; on the overview, dozens of strings would drown every other event.
Settlement bookkeeping (redispatch and marketer settlements)	These stay open for weeks by design while a billing period runs — they are accounting, not alarms, and would keep the column lit on every plant.
Curtailment episodes	The Live column's setpoints and the production graph already show an active curtailment.
The manufacturer's raw alarm and warning lists	Mirox counts what it concluded from them — a device fault, a fault stop, a safety alarm — instead of every raw code.
Events below Normal (Low, Very low)	These are observations worth watching, not problems.

Tickets. Below the number, a ticket badge shows the plant's open tickets with the icons of their categories; hover it to see them.

Events column and notifications. The column shows the open events of the plant regardless of your notification settings — everyone looking at the Monitor sees the same number. Notifications are a separate, personal choice: an event reaches you only if its category is switched on for a channel and its level is at or above the minimum level you chose for that category (many roles start at High). So the column can show events that never notified you — for example a Normal device fault — and you can be notified about events the column leaves out because another column shows them, such as an inverter outage or a lost VPN. On your Profile ▸ Notifications page, each category shows how many events of each level occurred on your plants in the last 30 days, which helps you choose a minimum level. What each level means is listed in Alarm Levels.

Equipment Column

The Equipment column shows the health of a plant's units as compact badges — one badge per kind of unit, stacked where a plant has more than one kind (for example a solar plant with a battery storage system):

the icon says which units are counted: a circuit-board chip for inverters, a wind turbine for wind turbines, a battery for battery storage units (a power converter where the plant has them, otherwise a battery container);
the fraction says how many of them are healthy, for example 11/12. A dash means no unit of that kind has been observed yet.

It is a health figure, not a production figure: an inverter idle at night, a turbine standing still in low wind or paused on purpose, a battery waiting for its next cycle all count as healthy.

When units have a problem, small coloured badges appear inside the unit badge — an icon and how many units are affected:

Safety alarm — a red siren: fire, smoke or gas, thermal runaway, a released suppression or an arc. It puts the plant in Alert.
Outage or fault stop — a red crossed-out lightning bolt: the unit is not producing, or stopped because of a fault. Ordered, weather and market stops are status, not faults.
Reduced output (inverters) — a red falling arrow: still producing, but far below its own model.
No communication — an amber plug with a cross: no data from the unit for longer than its threshold, or cut off by a network outage.

A grey pause badge counts the wind turbines and battery units standing still on purpose — held by an environmental module (bat or shadow protection), the direct marketer, the grid operator or service; hover it to see why. It is status, not a fault: it never notifies, never changes the plant's state, and those units stay in the healthy fraction.

Each unit is counted once, so the badges and the fraction never add up to more units than the plant has. No communication wins: while we cannot hear a unit, we cannot know its real state either, so it is counted only as No communication — an outage or fault stop that was still open when the connection dropped is not counted on top (it stays listed with the unit when you open the badge). Of the units we can hear, an outage or fault stop comes before reduced output.

Hover a badge to read what it means; click a coloured badge to see the affected units and the events behind them. The same icons are listed in the column header's ⓘ.

Connection Status and Topology

Because Mirox initiates every connection, it can show you the full path from the cloud all the way down to each logger. You can see whether the cloud is reaching the plant's agent, whether the agent can reach your network infrastructure and devices, and whether each individual logger is responding — so when something breaks, you know exactly where in the chain to look. The on-site network discovery and device health checks are covered in the Local Network Inspector.

Security Considerations

Active collection is designed to strengthen, not weaken, your plant's security posture:

Read-Only Operation: Collection reads device values and does not write to or control your equipment
Encrypted Connections: Data retrieval uses encrypted transport wherever the device supports it
Access Control: All collection activity is authenticated and authorized
Network Isolation: The plant's agent operates within secure network boundaries and reaches the plant only through its own VPN tunnel

Data Scraper — the edge agent and the full list of supported device adapters
Digital Twin — physics-based modeling built on the collected data
KPI Dashboard — the headline metrics derived from real-time monitoring
Local Network Inspector — on-site discovery and connection health for your plant network
Events — automatic detection of issues from the live data feed
Alarm Levels — which events notify, at which level and how fast
Forecasts — weather-based production outlook on top of historical readings