Skip to content

August 2026

Changes released in August 2026.

Open in the full timeline

Web appFixMajorCurtailment & grid limits

Curtailment figures at battery plants no longer read too high

At plants with battery storage, curtailed energy and the compensation shown against it now come from what the inverters produced, and fall where they read too high. The feed-in meter sits behind the battery, so quarter-hours spent charging looked like no production at all and were claimed in full.

mirox 2.15.376 – 2.15.393
AgentFixProduction & yield

The performance ratio now comes from the inverters' own output

Wherever every inverter a plant expects has reported, the performance ratio now comes from what those inverters produced, not from the feed-in meter. Losses in the meter and the lines no longer count against it. Plants receive this with their next agent update.

mirox 2.15.376 – 2.15.393mirox-agents 3.1.435 – 3.1.442
Web appImprovements and fixesAlerts & events

A component's status now shows what was detected and since when. Alarm codes from inverters now read in the user's own language.

  • A component's status on the analysis or components page now opens what was detected, since when, and how often each code was raised.
  • A feed-in meter now shows "Energy partly estimated" and an inverter with a frozen lifetime counter "Counter frozen", each opening the event behind it.
  • When strings are added, "Select all" now covers every inverter of the plant and no longer stops at the first 100.
  • A Huawei battery container no longer shows a warning for low coolant, nor a status number that appears in no Huawei document.
  • Creating a remote-access server for both IPv4 and IPv6 on a plant that already has remote access works again.
  • A file dragged into an assistant conversation is attached, and an image in a ticket opens full size when clicked.
mirox 2.15.376 – 2.15.393
Read more in the documentationEventsInverter status codesDirect VPN
AgentImprovements and fixesAlerts & events

Solar plants no longer raise an alert every night that a device stopped sending. A curtailed inverter no longer reads as an outage.

  • Inverters going quiet after dark no longer raise an alert at a solar plant, while a device that cannot be reached still alarms.
  • An inverter held down to zero by the direct marketer no longer counts as an outage while its own status says it is limited.
  • Huawei 33KTL-A and 36KTL inverters now show their real operating status and model instead of a wrong status code and their firmware.
  • Inverters are no longer flagged as measuring wrongly when one stray reading invents energy on a quiet string.
mirox-agents 3.1.435 – 3.1.442
Read more in the documentationInverter status codes
Web appFixMajorCurtailment & grid limits

A limit matching the grid connection no longer counts as curtailment

Curtailed energy and the compensation shown against it now fall at plants whose grid connection is smaller than their inverters. A limit from the direct marketer that merely restates full output was counted as curtailment all day long and is now judged against the smallest of panel peak, inverter rating and grid connection.

mirox 2.15.367 – 2.15.375
AgentFixProduction & yield

A failed grid meter no longer hides curtailed minutes

The performance ratio is no longer flattered at a plant whose grid meter cannot be reached. Minutes the plant spent held down at the grid operator's limit are now left out, even without a reading from that meter, instead of counting as clean production. Plants receive this with their next agent update.

mirox-agents 3.1.422 – 3.1.433
Web appImprovements and fixesThe app itself

A hybrid plant's power graph now shows its battery. Lists across the app can be filtered from their column headers.

  • A hybrid plant's day power graph now draws its battery's power.
  • Power curves no longer double an inverter's output after its data logger has been renamed.
  • The dashboard can now be filtered from its column headers.
  • Searching or excluding a portfolio on the dashboard now narrows its KPI cards.
  • A plant's production page now opens with a summary of every component type.
  • Identifiers in tables can now be copied by clicking them.
mirox 2.15.367 – 2.15.375
AgentImprovements and fixesAlerts & events

Reduced-output flags open and clear on firmer ground, and device-reported faults confirm and update during the day.

  • The "Reduced output" flag no longer stays on a recovered component.
  • A device-reported thermal or insulation fault now confirms its event within 15 minutes, and a changed alarm count appears on the event within 30 minutes.
  • A string behind a data logger now reports its negative current when it back-feeds.
  • That quarter-hour's feed-in energy no longer drops from the Marktprämie after a restart inside a quarter-hour.
mirox-agents 3.1.422 – 3.1.433
AgentImprovements and fixesCurtailment & grid limits

Phoenix Contact Power Control Unit 4.0 controllers now report their limits, and a curtailed plant no longer raises underperformance alerts.

  • A Phoenix Contact Power Control Unit 4.0 now reports the grid operator's and direct marketer's limits and the setpoints given to the battery.
  • Inverters at a plant held down by the grid operator or the direct marketer are no longer reported as producing far below expectation.
  • A day on which half of a plant's components fall below expectation no longer raises an underperformance event on each of them.
  • A Phoenix Contact controller whose web interface has no login can now be added without one.
mirox-agents 3.1.416 – 3.1.417mirox 2.15.361 – 2.15.366
Read more in the documentationData loggers
Web appImprovements and fixesThe app itself

Whether a device is online is now answered the same on every page, instead of differently on each.

  • A stopped on-site agent no longer shows green for fifteen minutes, a short restart gap shows amber, and a device never seen shows grey.
  • Battery converters and containers now show the state they report about themselves, for NR Electric converters and Linyang containers.
  • The AC/DC switch beside a converter's graph now works, and a separate DC entry in the list of values is no longer needed.
  • The visibility and shared note of several ticked combiner boxes can now be changed in one go, per inverter, data logger or whole plant.
  • The assistant can now hide the components on one data logger, showing what would change and applying it only after confirmation.
mirox 2.15.340 – 2.15.352
Read more in the documentationComponentsAI assistant
Web appFixMajorRevenue & market

Marktprämie figures per band are corrected and show their energy

The revenue tables now show an "Energy (§ 51 applied)" column: the energy each band's Marktprämie is actually paid on. Each band's premium is now worked out from that energy instead of being shared across the bands by capacity.

mirox 2.15.330 – 2.15.339
Web appImprovements and fixesNetwork & remote access

Remote-access connections a plant dials out to now show as much as the ones it accepts.

  • A remote-access connection the plant dials out to now shows its remote site under the name it was given, with a throughput chart.
  • When a VPN is added, an IPsec configuration file can now be uploaded and its values filled in.
  • A plant's OpenVPN remote access offered over IPv6 now accepts connections from IPv6 clients.
  • Connected clients on a plant's VPN tab are now named after their protocol, instead of a guess at the device at the far end.
  • Long lines in a VPN log now scroll sideways inside the window instead of running off the edge.
mirox 2.15.330 – 2.15.339
Read more in the documentationDirect VPN
Web appFixMajorRevenue & market

The revenue comparison now comes from the monthly settlement

The comparison of settlement methods on the revenue page now uses the figures from the monthly settlement. A month that has not been settled yet reads as unavailable instead of showing a number.

mirox 2.15.310 – 2.15.329
Web appFixMajorCurtailment & grid limits

Flat-rate compensation is now measured against the last valid period

For plants settled on the flat-rate method, a curtailment is now measured against the power in the last valid period before it, rather than the highest power found earlier. Curtailed energy and compensation fall wherever the old rule lifted them, while figures already issued keep their value until a month is rebuilt.

mirox 2.15.310 – 2.15.329
Web appImprovements and fixesThe app itself

Inverters now show the operating status they report about themselves. Lists, pickers and live graphs that misbehaved work again.

  • The analysis and components pages now have a "Status code" column showing what a Huawei, SMA or Fronius inverter reports about itself.
  • A site connected over IPsec again shows its address under "Live status" instead of a dash.
  • The inverter picker in a plant's segment dialog no longer opens empty when the dialog is opened a second time.
  • Members whose plant access comes through a shared portfolio can pick those plants in the site switcher again.
  • Paging through a long list no longer shows one row twice and leaves another one out.
  • A live graph on a plant's networking page follows the clock again, instead of standing still while it keeps loading.
mirox 2.15.310 – 2.15.329
Read more in the documentationInverter status codesDirect VPN
Web appFixMajorCurtailment & grid limits

Curtailment rows no longer show a figure from another calculation

Where the data a plant's settlement method needs has not been published yet, lost energy and compensation worked out a different way were shown as the plant's own. The row and its dialog now read "Satellite data not yet available" instead, or "No usable measurement data" where the gap is permanent.

mirox 2.15.296 – 2.15.309
Web appFixMajorRevenue & market

Curtailment excluded by § 51 no longer shows a euro amount

A quarter-hour excluded from remuneration by § 51 EEG no longer shows a euro amount. The amount disappears when the month is recalculated, while the excluded energy stays in kWh.

mirox 2.15.296 – 2.15.309
Web appImprovements and fixesThe app itself

Analysis graphs now show voltage and current for inverters, combiner boxes and strings. Dashboard bars now leave out a day whose energy counter jumped to an impossible value and mark it with a warning.

  • The analysis switch is now "Show connected components", breaking a component into its parts when on.
  • The analysis now adds a component to the comparison when a row checkbox is ticked in compare mode.
  • A VPN connection Mirox hosts now has an "IP version" setting: IPv4, IPv6 or both.
  • A WireGuard connection Mirox hosts now has a "Reconnect port" on which the site router re-dials.
mirox 2.15.296 – 2.15.309
Read more in the documentationDirect VPN
AgentImprovements and fixesData collection

Production curves for each component now follow the day in 15-minute steps instead of filling in hour by hour. Curtailment figures now appear for plants that previously had none.

  • Curtailment figures now appear for plants without irradiation data and for five plants whose nameplate power could not be read.
  • An inverter now reports its active-power setpoint.
  • An outage on a dead inverter no longer closes and re-opens through the morning.
  • A component producing far below expectation no longer reads healthy after a stretch where it sent nothing.
  • Voltages from a data logger now read as phase-to-neutral under the new phase names.
mirox-agents 3.1.361 – 3.1.373
Web appImprovements and fixesNetwork & remote access

Remote access to a plant now survives a move of its on-site agent. For connections Mirox hosts, OpenVPN is now suggested instead of WireGuard.

  • Remote access to a plant survives a move of its on-site agent: the address stays the same and the agent reconnects by itself.
  • For plants whose remote access Mirox hosts, OpenVPN is now suggested instead of WireGuard, and each option explains the reason.
  • A half-finished VPN wizard is now kept as a draft and restored when it reopens for the same plant.
  • A site connection can now be given its own name when it is added or edited, instead of the suggested one.
mirox 2.15.279 – 2.15.290
Read more in the documentationDirect VPN
Web appFixMajorCurtailment & grid limits

Curtailment figures no longer count night-time quarter-hours

Curtailment running into the night no longer counts energy from the irradiation sensor's night-time reading, a quarter-hour below 5 W/m² now counting as zero. Curtailed energy and the compensation shown against it fall at plants settled from measured irradiation, for instructions reaching into the evening or early morning.

mirox 2.15.274 – 2.15.278
Web appImprovements and fixesUsers & access

A portfolio shared by a partner organization opens its plants' connection status, tickets, events and graphs again. A "Security Officer" share is now passed on only as that role.

  • A portfolio shared by a partner organization now opens its plants' connection status, tickets, events and graphs.
  • A "Security Officer" share is now passed on only as that role, never with fewer rights.
  • A "Security Officer" can open a VPN connection's "Live status" and logs, while "Debug" stays closed.
  • A plant's "Production" page now shows its panel peak, inverter peak, DC/AC ratio and grid limit under the title.
  • The web pages of a plant's devices open again for a "Security Officer".
mirox 2.15.274 – 2.15.278
Read more in the documentationPermission systemDirect VPN
AgentImprovements and fixesData collection

A device's web page that answers only over HTTPS opens again. It is no longer noted as plain HTTP.

  • A device's web page that answers only over HTTPS is no longer noted as plain HTTP.
  • A device just found in a scan now opens its web page at once.
  • Curtailment episodes on a plant's "Activity" page show their current status again after the month's settlement has run.
mirox-agents 3.1.346 – 3.1.349mirox 2.15.274 – 2.15.278
Read more in the documentationNetwork devices
Web appFixMajorRevenue & market

Curtailment compensation is no longer shown before 23 December 2025

Compensation for curtailed energy is now shown only for quarter-hours from 23 December 2025 on, the day that rule took effect. A compensation figure for a delivery month lying wholly before that date disappears the next time that month is settled.

mirox 2.15.261 – 2.15.273
Web appImprovements and fixesThe app itself

A plant's day graph no longer turns red for hours after a brief drop in its remote connection.

  • Components now flag two more problems: producing far below what is expected of them, and sending no measurements at all.
  • A plant's network devices can now be searched by what is opened on them, and filtered by device type across the whole list.
  • Buttons on a plant's networking and core-data pages now match what the role may actually do.
  • The API now accepts a lowercase id, a spaced id list and an out-of-range page or limit instead of refusing them.
mirox 2.15.261 – 2.15.273
Read more in the documentationNetwork devicesDirect VPN
AgentImprovements and fixesAlerts & events

The plant analysis no longer writes off strings or inverters on the strength of a day when the plant was dark or partly out.

  • Strings are no longer marked as not connected after a day the plant was dark or hardly reporting.
  • A string marked that way earlier clears itself once it measures again, instead of waiting to be cleared by hand.
  • An inverter that was out for part of the day is no longer reported as producing far below what is expected of it.
  • An event closed on an inverter no longer re-opens by itself on a day that inverter recovered.
  • Configured strings that have never produced now count in the expected values and can raise events.
  • An alert about a data source that came back while the on-site agent restarted no longer stays open.
mirox-agents 3.1.337 – 3.1.345mirox 2.15.261 – 2.15.273
Web appFixMajorCurtailment & grid limits

Curtailed energy and compensation before mid-May 2026 rise

Curtailed energy and the compensation shown against it rise for periods before mid-May 2026: quarter-hours that carried no measurement now count, worked out from the plant's own irradiation sensors and feed-in meters. Plants settled on the flat-rate method get figures there for the first time.

mirox 2.15.253 – 2.15.260
Web appImprovements and fixesBattery storage

Files of up to 200 MB can now be put into a plant's storage. Each battery container shows its racks, modules and cells, and each of those can be followed with its own curves.

  • Files of up to 200 MB can now be uploaded into a plant's storage.
  • A file over 50 MB is stored but not analysed automatically and reads "Too large to analyse (over 50 MB)".
  • Each battery container now shows how many racks, modules and cells sit below it, and how many of its cells are healthy.
  • A converter, rack, module or cell on a battery plant can now be picked and its own curves followed as a graph, heatmap or table.
  • A plant's contact list sorts and filters again when it holds entries with no personal name, such as the grid operator.
  • A battery component can no longer be marked as verified or given a note, as its details come from the battery system itself.
mirox 2.15.253 – 2.15.260
Read more in the documentationFile storage
Web appFixMajorCurtailment & grid limits

Excluded curtailments now stay out of the settlement

A curtailment episode excluded with "Exclude from settlement" is now left out of the month's curtailed energy and compensation. Until this release the exclusion was recorded, but the month was settled as though nothing had been excluded.

mirox 2.15.243 – 2.15.252
Web appImprovements and fixesData collection

Adding a Phoenix Contact or Huawei data logger works again, instead of being refused the moment it is saved. A device's web page opened through remote access no longer loops endlessly or arrives as a file download.

  • Adding a Phoenix Contact or Huawei data logger no longer fails the moment it is saved.
  • A device's web page opened through remote access no longer loops endlessly or arrives as a file download.
  • The assistant now says when web search or document reading is unavailable, instead of answering from memory.
  • The name "MCP Server Authentication" is reserved for the assistant's own token and is refused when an access token is created.
  • The "Battery storage present" switch in a plant's master data now shows in the user's language.
mirox 2.15.243 – 2.15.252
Read more in the documentationData loggersProxy
AgentImprovements and fixesAlerts & events

An inverter that sends nothing now reads as "Inverter not communicating" rather than as an outage. The alert for failed components now follows them as they drop out and come back, with a notification at the start and on recovery.

  • An inverter that sends nothing, and the combiner boxes behind it, now read as "Inverter not communicating" rather than as an outage.
  • The alert for failed components now follows them as they drop out and come back, with a notification at the start and on recovery.
  • On a plant's "Activity" page, an inverter or combiner box that keeps producing far below its expected model now gets its own event.
  • A battery with a power converter now delivers its data to the plant's battery views.
mirox-agents 3.1.322 – 3.1.333mirox 2.15.243 – 2.15.252
Web appFixMajorCurtailment & grid limits

Curtailment figures no longer count a limit near full power

A limit from the grid operator or the direct marketer left between 85 % and full power no longer counts as a curtailment, even where it does curtail. Curtailed energy and the compensation shown against it drop at plants whose limit sat in that band, at some for a whole month.

mirox 2.15.235 – 2.15.242
AgentImprovements and fixesSolar equipment

The string analysis now runs by itself, once a week and every night through a plant's first 30 days.

  • An alert for a device that stopped sending data now closes once the device is back.
  • Expected values now come from a flat-mounted irradiation sensor where a plant has one, and per inverter orientation where a plant faces several directions.
  • At plants with many strings, the string analysis again measures a full 30 days, so a string that sent nothing reads as having no data.
mirox 2.15.235 – 2.15.242mirox-agents 3.1.314 – 3.1.320
Web appImprovements and fixesAssistant

The assistant keeps writing its answer while another page of the app is open.

  • An answer the assistant is writing keeps going when the chat is left, a tab switched or the connection lost, and is waiting on return.
  • The chat reopens on the last conversation when opened again within 15 minutes, instead of an empty one.
  • The assistant can be asked whether strings are built as configured and names any whose measured orientation, tilt or panel count differs.
  • The assistant can be asked what a plant is producing right now, or what it is expected to produce over the next five days.
  • Asked why a plant is unreachable, the assistant tells whether the plant's own router or its internet line stopped answering.
  • The assistant no longer hands out a colleague's phone number or email, while contacts stored for a plant are still answered.
mirox 2.15.228 – 2.15.234
Web appImprovements and fixesAlerts & events

The assistant can now say what an event cost in lost energy.

  • Asked about an event, the assistant estimates the lost energy and names the components and tickets linked to it.
  • The activity list now opens on events of high priority and above, and can still be filtered to any priority level.
  • Notification rules can no longer be set to the two lowest priority levels, and a rule already set to one keeps it.
mirox 2.15.225 – 2.15.227
AgentImprovements and fixesAlerts & events

A component that has gone quiet is now reported on the same day, instead of the day after.

  • A component is reported roughly an hour after it stops sending data in daylight, instead of a day later.
  • An inverter whose strings were entered by hand and confirmed is now watched for outages, which it was not before.
  • A quiet stretch never counts towards an outage while the plant's irradiation is unknown, at night for example.
mirox-agents 3.1.305 – 3.1.306
Web appFixMajorProduction & yield

A feed-in meter's own reading is used again on bright days

A feed-in meter's own reading is used again on bright days, and the day counts as "measured" instead of "integrated". Before, a high reading was thrown out as impossible and replaced by the total added up from the inverters, or by zero where there was no substitute.

mirox 2.15.214 – 2.15.224
Web appImprovements and fixesAlerts & events

Open events and connection outages are now counted without double counting, and every event carries a name in the user's language.

  • A plant's open-event count no longer adds the grouping alert on top of the dead components themselves: twelve dead inverters read as twelve.
  • Every event in a plant's activity list, dialogs and tickets now shows its name in the user's language instead of an untranslated one.
  • The month chart no longer marks a day as a connection outage when the plant produced right through a brief drop, or before monitoring began.
  • A Solar-Log logger can now be stopped, under its settings, from reporting a feed-in meter another source already reads, which counted grid power twice.
  • In the API, the site list can be narrowed by portfolio and type, both comma-separated, with the total and the paging following the filter.
mirox 2.15.214 – 2.15.224
Read more in the documentationData loggers
AgentImprovements and fixesData collection

A device a data logger lists but has never measured now appears among the plant's components. Where a Solar-Log logger's daily totals are unreadable, daily energy is recovered from the devices' own readings.

  • A Solar-Log feed-in meter now appears in the plant's components even while it is still holding back its energy readings.
  • The single alert for components that stopped producing now arrives after 30 minutes instead of an hour.
mirox-agents 3.1.298 – 3.1.304
Read more in the documentationComponents
AgentFixMajorProduction & yield

Expected production at capped plants no longer reads too low

The expected-production curve read too low at plants whose output is capped, sitting well below the cap on bright days. It now follows the cap itself, and expected production on a bright day matches what the plant is allowed to deliver. Plants receive this with their next agent update.

mirox-agents 3.1.278 – 3.1.296mirox 2.15.198 – 2.15.213
Web appImprovements and fixesAlerts & events

The monitor list no longer counts an inverter idle at night as missing.

  • "Reachable subnets" now shows where two plants' networks overlap, not only where they are identical, and lets the plant serving the shared addresses be chosen.
  • On a per-Wp day graph, the reference curve now follows the selected components, so an east-west plant shows both of its peaks.
  • The sign-in page now states how long the pause after repeated failed sign-ins lasts, and that changing the password does not end it early.
  • Third-party components received security updates.
mirox 2.15.198 – 2.15.213
Read more in the documentationAccount lockoutVPN
Web appFixMajorRevenue & market

Compensation no longer counts a curtailed quarter-hour twice

Where two sources sent readings for the same minutes — after a restart, for example — a plant's curtailed energy for that quarter-hour was counted twice, and the compensation shown read too high. Such a quarter-hour is now left out of the settlement, and figures already issued keep their value.

mirox 2.15.190 – 2.15.197
Web appImprovements and fixesAlerts & events

A data logger that has gone silent no longer counts as healthy in a plant's tally.

  • Graph tooltips now mark each curve with the events running at that moment, and a click pins the tooltip so those events can be opened.
  • Where a plant already has a Mirox-hosted remote access server, another router or network can now be added to it instead of a second server.
  • A plant's coordinates can now be entered as degrees, minutes and seconds or as decimal minutes, chosen under "Coordinate format".
  • Each connected site in a plant's remote-access list now opens its own "Live status", and its tunnel address can be copied with one click.
  • The edit dialog of a network device no longer shows the values of the device edited before it.
  • A plant can now be given a build date in the future when it is created.
mirox 2.15.190 – 2.15.197
Read more in the documentationDirect VPN
AgentImprovements and fixesProduction & yield

An inverter whose energy counter stalls no longer lowers a Fronius plant's energy, and editing a data logger no longer splits other loggers' inverter history.

  • At Fronius plants, an inverter whose lifetime energy total stops advancing no longer lowers the plant's energy, its production being worked out from its power.
  • Adding or editing a data logger no longer causes another logger's Huawei or Sungrow inverters to appear as new components with their history split.
mirox 2.15.190 – 2.15.197mirox-agents 3.1.259 – 3.1.276
AgentFixMajorSolar equipment

The string analysis now gives a result for nearly every string

The string analysis now gives nearly every string a result, measured on the plant's clearest days, instead of only a handful. Strings on combiner boxes that measure current per input are no longer reported as unmeasurable, and plants receive this with their next agent update.

mirox-agents 3.1.257
Web appImprovements and fixesAlerts & events

Open events now appear on the components list, on the components they concern.

  • The components list marks each inverter, combiner box and string with its open events, and selecting a mark opens that event.
  • A combiner box shows how many of its strings send no measurement data, and lists them when the number is selected.
  • A plant's string and inverter lists open again instead of failing with an error.
  • Opening a device's own web page through remote access no longer returns to the Mirox sign-in page.
  • A partner organization given a technical role can now edit a plant's network devices and add or remove devices.
  • IP addresses now sort by number in device lists and access logs, so .2 comes before .101.
mirox 2.15.185 – 2.15.189
Web appFixMajorProduction & yield

Expected yield now allows for panel ageing since the plant was built

A plant's expected monthly yield now allows for panel ageing counted from the day the plant was built, not from the day Mirox started collecting its data. Expected figures fall where the plant is older than its data, and no ageing is applied where no build date is recorded.

mirox 2.15.176 – 2.15.184
Web appImprovements and fixesData collection

Each value read from a data logger can now be given its own factor and limits.

  • Under "Advanced settings", a factor and a high and low limit can be set for each value read from a data logger.
  • Inverters, combiner boxes and strings that have never sent a measurement are now counted separately, no longer as producing.
  • An inverter, combiner box, irradiation sensor or feed-in meter added by hand can now be deleted from its table, after a confirmation.
mirox 2.15.176 – 2.15.184
Read more in the documentationData loggers
AgentImprovements and fixesSolar equipment

String analysis is available again at plants that run under a standing power limit.

  • At plants on sloping ground, the direction strings face is now worked out correctly instead of reading too far east.
  • At plants under a standing grid or marketer power limit, string analysis is available again instead of a whole day counted as curtailed.
mirox 2.15.176 – 2.15.184mirox-agents 3.1.250 – 3.1.256
AgentFixData collection

Unreachable Huawei inverters no longer report zero production

Huawei plants no longer show production dropping to zero when the data logger cannot reach an inverter. An unreachable inverter is now left out instead of being recorded as zero, and the plant's power is worked out from the inverters that did answer.

mirox-agents 3.1.233 – 3.1.237
AgentImprovements and fixesSolar equipment

The string analysis now runs in more situations: without a panel datasheet, on cloudy days, and where a string's orientation cannot be measured.

  • Without a panel datasheet the analysis still finds each string's wiring, connections and orientation, and only the peak power is missing.
  • A string whose own orientation cannot be measured now takes the orientation of its inverter, instead of being left out.
  • When there are too few clear days, cloudy days now help work out orientation, counting for less than a clear day.
  • A day when the plant stopped sending for an hour is still measured, instead of being set aside as overcast.
  • If no strings are set up for the inverters, the analysis now says so instead of failing with an error.
  • Expected production now follows the configured strings even when some lack a peak power or an orientation, instead of the plant's peak power alone.
mirox-agents 3.1.233 – 3.1.237
Web appFixMajorProduction & yield

Component details no longer show energy a thousand times too high

An inverter, a string or a combiner box opened from the analysis page showed its produced, expected and lost energy a thousand times too high — kWh labelled as MWh — and the battery overview showed DC power the same way. Both read correctly again.

mirox 2.15.166 – 2.15.172
Web appImprovements and fixesNetwork & remote access

The personal VPN now follows the technical role held on each plant. Plants with no AC limit configured now get a 5-day forecast.

  • Every plant on which a technical role is held now appears under "Reachable subnets" in the profile, including one shared by a partner.
  • An "Asset Manager (Commercial)" no longer reaches plant equipment: no subnets on their VPN, and no changes to a device's "Web Targets".
  • A meter's own reading now counts for today and for a plant's first days, instead of looking like a data logger fault.
  • Plants with no AC limit configured now get a 5-day forecast and expected values — uncapped estimates, flagged as such under "Expectation comparison".
  • Editing a network device from its details no longer leaves the page unclickable until it is reloaded.
  • The creator or assignee of a ticket now receives its notifications even while the plant is muted, unless the ticket itself is muted.
mirox 2.15.166 – 2.15.172
Read more in the documentationVPNProxyNotifications
AgentImprovements and fixesData collection

Combiner boxes, irradiation sensors and feed-in meters now name the data logger they are read from. An older device reached through remote access no longer asks for a login over and over.

  • Combiner boxes, irradiation sensors and feed-in meters now show the data logger they are read from.
  • An older device's own web page, reached through remote access, no longer asks for a login over and over.
  • Adding a data logger now reports when its test read keeps failing — a missing login, for example — instead of showing nothing.
mirox-agents 3.1.227 – 3.1.232mirox 2.15.166 – 2.15.172
Web appImprovements and fixesUsers & access

Renaming an organization no longer fails when no contact email is stored for it.

  • A field cleared in an organization or contact dialog now saves as empty, and an unchanged dialog saves nothing.
  • Through the API, /v1/sites now lists the reachable plants without health figures, and /v1/sites/status returns health for the plants named in the call.
  • A remote-access route whose subnet contains the reserved address 10.112.0.1 is now flagged, and only that single address stays unreachable inside the plant.
mirox 2.15.160 – 2.15.165
AgentImprovements and fixesSolar equipment

Huawei inverters now report their insulation resistance.

  • A combiner box now shows the serial number the on-site agent read from it.
  • The satellite irradiation figures in settlement events, which had stopped at 2026-07-31, update again on their own.
mirox-agents 3.1.220 – 3.1.226
Read more in the documentationMarket
AgentFixMajorCurtailment & grid limits

Flat-rate settlement now deducts the direct marketer's share

In a "Redispatch settlement" event, the lost energy worked out by the flat-rate (pauschal) method previously counted quarter-hours the direct marketer had curtailed at the same time. For months from July 2026 the figure is net of that share and decreases where the two overlapped, while earlier months keep the gross figure. Plants receive this with their next agent update.

mirox 2.15.144 – 2.15.151mirox-agents 3.1.214
Read more in the documentationMarket
AgentFixMajorProduction & yield

Curtailed minutes no longer count against the performance ratio

The performance ratio read too low at plants that were curtailed, and the expected production scaled from it was too low as well. Both are correct from this release, which plants receive with their next agent update. Plants receive this with their next agent update.

mirox-agents 3.1.214
Web appImprovements and fixesProduction & yield

The monitor chart now shows what a plant should have produced while it was offline. The week, month and year charts gain the same expected-production curve as the day chart.

  • The monitor chart now shows what a plant should have produced while it sent nothing, marked "Expected (no connection)".
  • Reference curves now break where the plant sent nothing, instead of drawing a straight line across the gap.
  • On the export page, "Try it out" now provides ready-made terminal commands, a Python script and an AI prompt, with a reporting-only access token.
  • A plant's components can now be searched and attached to a ticket while it is still being written.
  • Large exports covering many plants now arrive faster.
  • Every date range picker now offers "Last year", meaning the whole of the previous calendar year.
mirox 2.15.144 – 2.15.151
Read more in the documentationMetrics export APIRaw data excel exportAPI tokens
AgentFixAlerts & events

A plant going offline now raises a single event

A plant that goes offline now raises one alert instead of two or none, and the alert closes only once the whole plant is reachable again. Alerts for devices that drop out in the same moment are held back, and plants receive this with their next agent update.

mirox-agents 3.1.208 – 3.1.212
Web appImprovements and fixesThe app itself

Hovering a person in tickets and support shows their profile, activity links open the right plant again, and a plant's remote access asks before restarting.

  • In tickets and support, hovering a person shows their profile: organization, role, email, phone and their job in the plant.
  • Links in the activity list open the right plant again and lead straight to where the event can be acted on.
  • A reaction to a message now appears in the support and ticket lists as the newest activity, with who reacted and to which message.
  • In a plant's remote-access settings the networks are listed in the order they are routed, and a network can be renamed in place.
  • Restarting a plant's remote access now asks for confirmation and states how many connected sites the restart affects.
  • Third-party components received security updates.
mirox 2.15.134 – 2.15.143
Read more in the documentationDirect VPN
AgentImprovements and fixesData collection

Grid meter readings taken through a Phoenix Contact controller no longer arrive with the feed-in direction reversed.

  • A Phoenix Contact controller now works out by itself which direction the grid meter counts, and shows no grid values until it is sure.
  • "Grid sign convention" in the controller's settings sets the direction by hand when the automatic check cannot decide.
  • Settlement events now also carry the lost energy worked out by the flat-rate (pauschal) method, beside the figures from each irradiation source.
  • Curtailments back to January 2025 are now settled, the reference day for months before July 2026 being the last suitable day before the curtailment.
  • A settlement event now names an irradiation source left out and why, and a morning gap in its readings no longer leaves the afternoon unsettled.
  • Expected production now follows each string's own orientation and size when the plant's components state them all, instead of one plant-wide orientation.
mirox-agents 3.1.203 – 3.1.207mirox 2.15.130 – 2.15.133
Read more in the documentationMarket