Skip to content

Changelog

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

Clear filters

November 202610

AgentFixSolar equipment

The components page no longer marks a string as not connected

A string that produced no energy on one day but energy within the last 30 days is no longer marked as not connected. The not-connected mark now uses the same 30-day energy window as the "probably not connected" badge on the components page. Plants receive this with their next agent update.

mirox-agents 3.2.251 – 3.2.256
AgentFixMajorProduction & yield

The month-to-date yield no longer counts the previous day twice

A solar data logger's month-to-date yield previously counted the previous day's production again on the first day of a new month, inflating the lifetime energy sum. The repeated production is no longer published, and figures already issued keep their value. Plants receive this with their next agent update.

mirox-agents 3.2.244 – 3.2.246
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 202629

AgentImprovements and fixesAlerts & events

An open inverter alarm on the plant's Events page keeps its start time when the on-site agent updates. A self-clearing inverter alarm no longer opens a device fault each night.

  • On the plant's Events page, an open inverter alarm no longer closes and reopens with a reset start time when the on-site agent updates.
  • 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, inverter alarm start times from a data logger that records local time now show in the plant's timezone.
  • A mismatch event between a data logger's counter and its power reading no longer assumes the counter is wrong.
  • A solar data logger's live data no longer stops for minutes while the on-site agent reads its history.
  • On the plant's Events page, a warning event now names an inverter whose data read failed three times in a row.
mirox 2.15.769 – 2.15.777mirox-agents 3.2.232 – 3.2.234
AgentImprovements and fixesThe app itself

Per-string figures no longer fail on plants whose strings are wired directly to the inverter. The on-site agent scans a network device's web UI once, not every hour.

  • A network device's vendor, model and firmware fields no longer take their values from another device.
  • The on-site agent scans a network device's web UI once and only again on a plant scan, instead of every hour.
  • A web-UI scan of a network device leaves a low-priority event in the plant's event list.
  • A device-fault summary for a fault reported at night now holds its notice 30 minutes instead of 5.
mirox 2.15.736 – 2.15.754mirox-agents 3.2.203 – 3.2.212
AgentFixData collection

A data logger's device list is now read whole

A data logger that announced more devices than it delivered previously left the newest entry out of its list, so that device was never polled. The device list is now read whole, and a short list seen while running falls back to the logger's web interface. Plants receive this with their next agent update.

mirox-agents 3.2.194 – 3.2.196
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
AgentFixMajorBattery storage

Battery setpoint no longer reads a flat zero

The battery setpoint figure read a flat zero even while the plant dispatched up to 10 MW. The setpoint figure now matches the plant's dispatch level. Plants receive this with their next agent update.

mirox-agents 3.2.175 – 3.2.176
AgentFixMajorBattery storage

Battery converter's stopped state and fault alarm now read correctly

A battery converter stopped by a protection previously read as unknown, counted as available, and raised no alarm. Its operating state now reads as stopped, its own fault alarm opens five minutes after the stop, and the plant's summary alarm opens fifteen minutes after the stop. Plants receive this with their next agent update.

mirox-agents 3.2.175 – 3.2.176
AgentFixMajorCurtailment & grid limits

Settlement months no longer finalize while satellite days are missing

A curtailment settlement month is no longer finalized while satellite data is still missing. It is rebuilt once more if that data arrives up to 14 days after the month's deadline. Plants receive this with their next agent update.

mirox-agents 3.2.153 – 3.2.157
AgentFixMajorCurtailment & grid limits

Curtailment figures now include the direct-marketer setpoint

Curtailment figures now include the plant controller's power cap and the direct marketer's active-power setpoint. The curtailment figure no longer reads too low where either ran. Plants receive this with their next agent update.

mirox-agents 3.2.153 – 3.2.244
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
AgentImprovements and fixesData collection

A battery storage system and a second generation of a solar data logger can now be added. Adding or updating several components of one plant at once no longer fails.

  • A second generation of a solar data logger can now be added, reading inverters and environment sensors behind it.
  • Adding or updating several components of one plant at once no longer fails for inverters, combiner boxes and strings.
  • Combiner boxes and strings now carry their own loss figures beside the inverter loss.
  • A feed-in meter's data now comes from the meter configured on the plant.
  • A manually added network device now gets one alive check in the network monitor, with an action to run it.
mirox 2.15.632 – 2.15.645mirox-agents 3.2.153 – 3.2.157
AgentFixMajorRevenue & market

Declared outages now reduce the flat-rate curtailment settlement

The plant's outage register is now reported to the direct marketer, and declared maintenance or administrative outages reduce the flat-rate curtailment settlement. Compensation for a period with a declared outage goes down, and figures already issued keep their value. Plants receive this with their next agent update.

mirox 2.15.614 – 2.15.618mirox-agents 3.2.144
AgentFixMajorCurtailment & grid limits

Curtailment settlement and lost energy no longer read too low

Curtailment settlement and lost energy no longer read too low for a period that started after a quiet stretch. The current and previous month are recalculated on the next run, and older months keep their value. Plants receive this with their next agent update.

mirox-agents 3.2.135

September 202625

August 202633

July 202617

June 202620

May 202612

April 20264

March 20261

January 20267