Skip to content

September 2026

Changes released in September 2026.

Open in the full timeline

Web appFixAlerts & events

An inverter fault now opens its outage under curtailment

An inverter that reports a fault no longer opens its outage only after a curtailment cap or low light has lifted. The event dialog shows which condition it overrode, with the maker's status and text.

mirox 2.15.553 – 2.15.564
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
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
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 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
Web appImprovements and fixesAlerts & events

A brief network glitch at a plant no longer reads as an internal problem. Battery racks, modules and cells list in position order, and the battery power graph marks AC and DC readings.

  • The plant connection view now reads "Agent restarting or reconnecting" for five minutes before it calls the problem "Internal service issue".
  • A device that went down during an outage on that path reads "Reconnecting" for three minutes after the connection returns.
  • The details panel on that view no longer closes when a date range is picked.
  • Battery racks, modules and cells now list in position order, instead of Cell 1, Cell 10, Cell 100.
  • The battery power graph now marks a reading "AC · converters" or "DC · racks", and containers and racks measure DC only.
mirox 2.15.397 – 2.15.406
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