Skip to content

September 2026

Changes released in September 2026.

Open in the full timeline

AgentImprovements and fixesBattery storage

The direct marketer's battery setpoint is read from one more plant controller layout. A battery converter's voltages now read in volts, and the first data collection cycle at a battery plant finishes in seconds.

  • A battery storage power converter that reports voltages with no declared unit now reads them in volts.
  • The first data collection cycle at a battery plant no longer reads the cell tabs, so it finishes in seconds instead of a minute.
mirox-agents 3.2.128 – 3.2.130
AgentFeatureMajorData collection

A plant controller can now be added as a data logger

A plant controller can now be added as a data logger, reading the grid operator's active-power setpoint as a percentage of installed capacity or the plant's irradiance sensor. Plants receive this with their next agent update.

mirox-agents 3.2.120 – 3.2.123mirox 2.15.570 – 2.15.571
AgentFixMajorCurtailment & grid limits

A direct marketer's limit now reads against the plant's own setpoint

The limit a direct marketer states was shown twice, once against the plant controller's own rating. It is now a single figure against the plant's own setpoint, and the plant's curtailed energy is corrected. Plants receive this with their next agent update.

mirox-agents 3.2.102 – 3.2.112
AgentFixMajorCurtailment & grid limits

Close-to-live curtailment no longer shows impossible values

Curtailment and compensation shown close to live no longer show impossible values. A plant whose reference days all fail the plausibility check shows no close-to-live figure, and issued figures keep their value. Plants receive this with their next agent update.

mirox-agents 3.2.102 – 3.2.112
AgentFixSolar equipment

A dead voltage sense line now reads as missing, not zero production

A combiner box behind a data logger previously showed a measured 0 W while its strings carried real current. A missing channel now shows nothing, and an explicit zero still reads as zero. Plants receive this with their next agent update.

mirox-agents 3.2.102 – 3.2.112
AgentImprovements and fixesAlerts & events

Plant outages, device faults and event times now read as the devices ran. Outages no longer open from a zero combiner box reading, and event times no longer carry the timezone offset.

  • A combiner box that reports zero power against its own live readings no longer opens an outage.
  • A silent inverter now opens a plant alarm after 12 hours.
  • Two data loggers can now be added, reading combiner boxes, strings, the grid meter, irradiation and temperature sensors, and curtailment limits.
  • A plant-wide grid trip is no longer recorded as a device fault.
  • Event times from the data logger are no longer off by the timezone offset.
mirox 2.15.539 – 2.15.552mirox-agents 3.2.102 – 3.2.112
AgentFixAlerts & events

A closed outage lists every component that was down

A closed outage previously named only the components that recovered last — 7 of 17 silent inverters — and now lists the whole incident. A device fault no longer reopens once the device has withdrawn every fault code, and no longer reads "Live" after an outage takes it over. Plants receive this with their next agent update.

mirox 2.15.536 – 2.15.538mirox-agents 3.2.97
AgentFeatureMajorData collection

A Meier-NT ADL-MX data logger can now be added

A Meier-NT ADL-MXmini or ADL-MXSpro data logger can now be added and reads the Power-One / ABB Aurora inverters and Si irradiance sensor behind it: power, voltages, currents, temperatures, irradiation, wind speed, daily and total energy, and each inverter's reported operating state. Plants receive this with their next agent update.

mirox 2.15.497 – 2.15.503mirox-agents 3.2.87 – 3.2.91
Read more in the documentationData loggersInverter status codes
AgentFixMajorWind turbines

Weather wind speed no longer reads 3.6 times too high

Wind speed and wind gusts from the weather service were previously recorded in km/h under an m/s label, so the values shown read about 3.6 times too high. They are now recorded in m/s, and values recorded earlier keep the old figure.

mirox-agents 3.2.85
AgentFeatureMajorData collection

Bachmann SPPC and mtu EnergyPack now serve as data loggers

A Bachmann SPPC park controller and an mtu EnergyPack battery can now be added as data loggers, the SPPC reading the grid connection point and the grid operator's and direct marketer's limits, the EnergyPack its state of charge, health, stored energy and power limits, with the next agent update.

mirox 2.15.486 – 2.15.493mirox-agents 3.2.76 – 3.2.82
Read more in the documentationData loggers
AgentFeatureData collection

Each Janitza meter can now be assigned what it reads

At a plant with a battery behind its grid connection point, each Janitza meter can now be assigned what it reads: the grid connection point, the PV feeder or the battery feeder. PV and battery readings then stay separate from the plant's grid figures, with the next agent update.

mirox 2.15.486 – 2.15.493mirox-agents 3.2.76 – 3.2.82
Read more in the documentationData loggers
AgentImprovements and fixesData collection

A wind plant without a feed-in meter now gets its production from the turbines' lifetime energy counters. It no longer raises a fault for the missing meter.

  • A battery's control signal now reads zero on its chart while the direct marketer is connected and asking for nothing.
  • A battery plant's settlement no longer drops quarter-hours after each restart of the on-site data collection.
mirox 2.15.468 – 2.15.483mirox-agents 3.2.67 – 3.2.72
Read more in the documentationData loggers
AgentFeatureMajorBattery storage

A battery storage can now be added as a data logger

A battery storage can now be added as a data logger, and its converters, battery skids, and racks are then read with power, charge and discharge limits, state of charge, and the grid operator's limits on both charging and feed-in. Plants receive this with their next agent update.

mirox-agents 3.2.53 – 3.2.66mirox 2.15.457 – 2.15.467
Read more in the documentationData loggers
AgentImprovements and fixesAlerts & events

An alarm or fault reported by an inverter now stays open until the inverter itself withdraws it. It no longer disappears from the list on its own.

  • An alarm raised by an inverter no longer closes just because part of its alarm list could not be read.
  • A fault reported by an inverter no longer closes on its own after the on-site data collection restarts.
  • A low-insulation warning no longer stays shown as active after the inverter has withdrawn it.
  • A battery unit read by a second data logger no longer keeps the make and model of the previous one.
  • The grid operator's ceilings on a battery storage's charging and discharging now appear on the plant's "Control Units" tab.
  • Wind and battery plants now receive the site's weather data — temperature, wind, precipitation, snow and irradiation.
mirox-agents 3.2.53 – 3.2.66mirox 2.15.457 – 2.15.467
AgentFixMajorCurtailment & grid limits

Close-to-live curtailment at battery plants no longer reads too high

Curtailment and compensation shown before the settlement at plants with battery storage now come from what the inverters produced, not from the feed-in meter behind the battery. They fall wherever the plant was charging or discharging while a limit was in force, and plants receive this with their next agent update. Plants receive this with their next agent update.

mirox-agents 3.2.50 – 3.2.51
AgentFixAlerts & events

An inverter the data logger cannot read is no longer called faulty

A plant no longer opens an "Inverter device fault" when its data logger reports it cannot read an inverter and no readings arrive. A low-priority "Logger cannot reach inverter" entry opens instead and becomes "Inverter not communicating" after an hour of daylight, and plants receive this with their next agent update.

mirox 2.15.447 – 2.15.456mirox-agents 3.2.50 – 3.2.51
Read more in the documentationInverter events
AgentImprovements and fixesData collection

Inverters behind a data logger are read again after a missed reply. Wind turbines and battery modules no longer read as offline for most of the day.

  • An inverter behind a data logger is read again after a missed reply, instead of dropping out of the data.
  • Wind turbines and battery modules no longer read as offline for most of the day while their connection is checked every 30 minutes.
  • A plant's mean irradiation no longer includes a reading higher than the sun can deliver.
mirox-agents 3.2.50 – 3.2.51
AgentFixMajorProduction & yield

Wind and battery plants are no longer measured as solar plants

A plant set up as a wind plant or a standalone battery plant is no longer measured as if it had panels: it no longer shows an expected-production curve, a clear-sky reference, a performance ratio or curtailment figures. Solar plants are unchanged, and plants receive this with their next agent update.

mirox 2.15.428 – 2.15.442mirox-agents 3.2.32 – 3.2.41
AgentFeatureMajorData collection

Vestas wind turbines are now read through VestasOnline

A Vestas VestasOnline SCADA server can now be added as a data logger, and every turbine behind it is read — power, wind and its lifetime energy counter — and listed on the wind plant's "Turbines" page. Plants receive this with their next agent update.

mirox 2.15.428 – 2.15.442mirox-agents 3.2.32 – 3.2.41
Read more in the documentationData loggers
AgentFixMajorCurtailment & grid limits

Lost energy no longer counts a pause in data collection as zero

Curtailment losses previously read too high for any quarter-hour in which the on-site data collection paused: those minutes counted as zero production. Those minutes now count at the rate the measured minutes around them show, and lost energy and compensation fall for such quarter-hours.

mirox-agents 3.2.14 – 3.2.23
AgentImprovements and fixesAlerts & events

A faulty irradiation sensor no longer triggers false inverter outages, and a plant's total feed-in energy is no longer missing after an inverter replacement or a restart of the on-site data collection.

  • A daylight reading an irradiation sensor cannot physically deliver is now refused, and inverters are no longer declared in outage against it.
  • A plant's total feed-in energy is published again after an inverter has been replaced, or after the on-site data collection restarted.
mirox-agents 3.2.14 – 3.2.23
AgentImprovements and fixesAlerts & events

Alarms reported by inverters now open, close and are counted the way their maker intends.

  • An emergency stop, a device fault or a latched arc fault no longer clears itself while the inverter is still reporting it.
  • Sungrow fan messages now appear as warnings rather than faults, as Sungrow itself rates them.
  • Measurements taken while the plant cannot reach Mirox are now stored and sent on once the connection returns.
  • An inverter that keeps falling back into the same reported state keeps one open entry, and every recurrence is counted.
  • An alarm an inverter first reported as a warning and then as a fault now shows the more serious of the two.
mirox 2.15.407 – 2.15.419mirox-agents 3.2.4 – 3.2.12
Read more in the documentationInverter status codes
AgentImprovements and fixesData collection

Linyang battery alarms name their condition, Phoenix Contact WebVisit park controllers report their limits and setpoints, and blue'Log loggers stay connected at plants with many strings and sensors.

  • Alarms from Linyang containers now name the condition, such as a charge over-temperature, instead of only an alarm level.
  • A Phoenix Contact park controller with a WebVisit interface now reports grid and marketer limits, and the setpoints applied.
  • blue'Log loggers no longer drop in and out at plants with many strings and sensors.
mirox 2.15.397 – 2.15.406mirox-agents 3.1.449 – 3.1.454
Read more in the documentationData loggers
AgentFixAlerts & events

A curtailed plant now reads as producing, not as shut down

A plant held at its grid operator's or direct marketer's limit now reads as producing, not "Grid Shutdown" or "External Shutdown". One long curtailment no longer fills the event list with dozens of entries.

mirox-agents 3.1.445 – 3.1.446
AgentImprovements and fixesData collection

Expected power is worked out again through stretches where irradiation readings were lost, and Huawei inverters now report model, firmware and rated power.

  • Irradiation sensors are no longer reported as sending nothing for hours at a time, and expected power and performance ratio are worked out again.
  • Huawei inverters now report their manufacturer, model, firmware version and rated power in their component details.
mirox-agents 3.1.445 – 3.1.446
Read more in the documentationComponents