Skip to content

Changelog

Every change to Mirox, grouped by month. Filter by group or by kind of change.

Clear filters

November 20265

AgentImprovements and fixesAlerts & events

False offline and unreachable alerts, false fault events and false data holds no longer fire on loggers, inverters and battery historians. An inverter fault that re-raises after its first raise now opens its fault event again.

  • A plant no longer reads offline after a brief network link drop.
  • A data logger's month-to-date yield no longer opens a false mismatch on a late step.
  • A data logger is no longer alerted unreachable while the plant's network link is pending.
  • A data logger outage is now reported once per episode.
  • A battery historian's cell voltages are no longer withheld as "not fed".
mirox-agents 3.2.244 – 3.2.246
AgentImprovements and fixesAlerts & events

In a plant's event list, DC measurement-defect, tracker and battery events no longer repeat. In an export, frozen lifetime-energy totals are not shown.

  • In a plant's event list, DC measurement-defect descriptions now name the faulty DC reading.
  • In a plant's event list, tracker silence and fault-stop events no longer repeat at night.
  • In a plant's event list, a battery unit at rest no longer posts a state change every night.
  • A data logger whose device list could not be read no longer reports its inverters as missing.
  • In an export, a lifetime-energy total frozen at its maximum value is no longer shown.
mirox-agents 3.2.235 – 3.2.238mirox 2.15.778 – 2.15.779

October 20265

AgentImprovements and fixesAlerts & events

Self-clearing inverter alarms no longer fill the plant's Events page. A failed inverter data read now raises an event.

  • A self-clearing inverter alarm no longer opens a device fault each night on the plant's Events page.
  • On the plant's Events page, a warning event now names an inverter whose data read failed three times in a row.
  • A solar data logger's live data no longer stops for minutes while the on-site agent reads its history.
  • A mismatch event between a data logger's counter and its power reading no longer assumes the counter is wrong.
  • The data state on the components page no longer marks a day as unservable when the component's data logger was never asked to read it.
  • A turbine or battery storage that is not communicating no longer joins the plant's outage summary.
mirox 2.15.769 – 2.15.777mirox-agents 3.2.232 – 3.2.234
AgentFixAlerts & events

A curtailed segment no longer marks its inverters as degraded

While a curtailment segment of a plant sat at a zero setpoint, the plant monitor previously marked its inverters as degraded. The inverters no longer open a degraded event. Plants receive this with their next agent update.

mirox-agents 3.2.194 – 3.2.196
AgentFixAlerts & events

A faulted inverter's outage now opens at once

A faulted inverter's outage now opens at once, instead of five minutes after the inverter stopped, and closes once the inverter produces again. The plant's outage summary names the inverters still down and counts the ones producing again. Plants receive this with their next agent update.

mirox 2.15.632 – 2.15.652mirox-agents 3.2.153 – 3.2.161

September 20268

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
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

August 202610

July 20263