Skip to content

July 2026

Changes released in July 2026.

Open in the full timeline

AgentFeatureCurtailment & grid limits

A plant now records a "Redispatch settlement" event per curtailment

For each grid-operator curtailment of a solar plant, the lost energy is now worked out under the binding BilAReM method and recorded as a "Redispatch settlement" event on the plant's "Activity" page, with the reference day chosen and the lost energy per irradiation source. Plants receive this with their next agent update.

mirox-agents 3.1.184 – 3.1.197mirox 2.15.111 – 2.15.125
Read more in the documentationMarket
AgentImprovements and fixesData collection

A Phoenix Contact controller now delivers a plant's feed-in readings. Expected production and the satellite performance ratio no longer read too low on days with a gap in the satellite reading.

  • A plant no longer appears offline while it catches up on a large backlog of older values.
  • With "Also monitor grid connection point" switched on, a Phoenix Contact controller now delivers the plant's feed-in power, reactive power and energy totals.
mirox-agents 3.1.184 – 3.1.197
AgentImprovements and fixesData collection

Values that plants were dropping now come through: on the largest plants, around sparse irradiation readings, and from Phoenix Contact controllers.

  • Plants with thousands of strings no longer stop delivering their string and combiner box values.
  • On plants that report sparsely, the figures worked out from irradiation readings no longer have gaps.
  • Plants with a Phoenix Contact controller now report their grid-operator and direct-marketer power limits, whichever integrator built the control cabinet.
  • An inverter whose peak power is entered as one figure is read again instead of being skipped.
mirox 2.15.80 – 2.15.88mirox-agents 3.1.151 – 3.1.153
AgentImprovements and fixesAlerts & events

Plants no longer report a working network connection as offline.

  • An event about a plant's connection now says in words why it opened and what ended it.
  • On large plants, expected production no longer stalls or counts energy twice after the on-site agent restarts.
mirox-agents 3.1.145 – 3.1.147mirox 2.15.73 – 2.15.79
Read more in the documentationActivity
AgentFixMajorProduction & yield

Performance ratio returns on plants that report less often

The performance ratio measured against weather and satellite data shows again on plants where inverters, the feed-in meter or the irradiation sensor report only every few minutes. On those plants the figure had been missing since 2026-06-08. Plants receive this with their next agent update.

mirox-agents 3.1.143
AgentFeatureNetwork & remote access

Plants now report a lost network connection

When a plant's network, its remote access or one of its network devices stops answering, the plant's "Activity" page now shows "Park network offline", "Network device offline", or "Network device mass outage" when many go at once. Each clears itself when the connection returns. Plants receive this with their next agent update.

mirox 2.15.48 – 2.15.63mirox-agents 3.1.142
Read more in the documentationActivity
AgentImprovements and fixesAlerts & events

The on-site analysis now reports a string as defective, not an outage. Open string investigations now close after three days without usable data.

  • In the on-site analysis, a producing string below its neighbours on three sunny days is reported as defective.
  • A stuck reading no longer raises a "Measurement conflict" in the on-site analysis.
  • An event for a defective string names the inverter, combiner box and string it concerns.
  • A gradually failing meter no longer appears as an outage in the on-site analysis.
mirox-agents 3.1.140mirox 2.15.32 – 2.15.35
Read more in the documentationComponents
AgentFeatureAlerts & events

A component that measures wrong no longer shows as an outage

Once a day, an inverter's energy is compared with the sum of its combiner boxes, and a combiner box's with the sum of its strings. A component that reads zero while the comparison shows it produced now shows "Measurement conflict" instead of "Outage". Plants receive this with their next agent update.

mirox-agents 3.1.135 – 3.1.138mirox 2.15.21 – 2.15.31
AgentFixMajorCurtailment & grid limits

Live curtailment losses on large plants no longer drop to zero

On plants with many strings and combiner boxes, the live figure for energy lost to a grid curtailment dropped to zero during a curtailment, reporting lost energy too low. It holds the measured value again. Plants receive this with their next agent update.

mirox-agents 3.1.130
AgentFeatureAlerts & events

Strings that stopped producing are told apart from shaded strings

A string that produces nothing now raises a notice of its own. While the cause is still open it shows as "Investigation" and still counts as producing, becoming an "Outage" once the evidence confirms it or closing when shading explains it. Plants receive this with their next agent update.

mirox 2.14.224 – 2.14.228mirox-agents 3.1.130
AgentFixMajorCurtailment & grid limits

Lost energy no longer counts for both the marketer and the grid

When a direct marketer curtailed only part of a plant, lost energy was counted twice, against the marketer and the grid operator. It now counts once, from that part's share of expected production, and the grid operator's figure drops. Plants receive this with their next agent update.

mirox-agents 3.1.127
AgentFeatureAlerts & events

Plants now report an inverter that has stopped producing

The on-site agent now raises a "Component production outage" event on the "Activity" page when an inverter stops producing. The event appears after three five-minute windows with no output, only in daylight when snow, fog or curtailment does not explain it, and closes once production resumes. Plants receive this with their next agent update.

mirox 2.14.185 – 2.14.194mirox-agents 3.1.124
Read more in the documentationActivity
AgentFixMajorCurtailment & grid limits

Flat-rate curtailment now counts only the BDEW clock windows

Flat-rate (pauschal) curtailment energy now counts only in the BDEW windows: 06:00–19:00 CET (07:00–20:00 in summer time) March to October, 09:00–16:45 CET November to February. Compensation changes with those figures. Plants receive this with their next agent update.

mirox 2.14.174 – 2.14.176mirox-agents 3.1.122
AgentFixMajorData collection

Huawei SmartLogger now reports every string of its inverters

Larger SUN2000 inverters on a Huawei SmartLogger reported only their first 12 or 18 strings, leaving the rest without voltage or current. Every wired string is now monitored, whatever the model. Plants receive this with their next agent update.

mirox-agents 3.1.122
AgentImprovements and fixesSolar equipment

The on-site analysis now reports strings missing from a plant. Strings now get results on days with late or partial readings.

  • The on-site analysis now reports inverters taking in more DC power than their listed strings account for, and roughly how many strings are missing.
  • Strings on a day whose data starts late now get a performance ratio, counted only over the hours with readings.
  • Strings now get a panel count on days with readings only around midday, as the brightest readings now count too.
  • The panel count entered for a string no longer overwrites the one the analysis measured, and both are kept.
mirox-agents 3.1.122
Read more in the documentationComponents