Skip to content

August 2026

Changes released in August 2026.

Open in the full timeline

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 appFeatureMajorAlerts & events

Inverters now show when switched off, tripped or reporting a fault

Inverters now show what they report about themselves: "Stopped by command" when one was switched off, "Protective stop" when its protection tripped, and "Device fault" when the machine reports a fault the measurements cannot show. The maker's own wording and how often it was raised are shown alongside.

mirox 2.15.367 – 2.15.375
Read more in the documentationInverter status codesEvents
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
Web appFeatureAlerts & events

Inverter status codes now open events for stops and self-derating

The status code an inverter reports about itself now opens an event when the device was stopped by command, tripped on its protection, raised a safety alarm or is throttling itself back. The health column shows "Stopped by command" and "Protective stop", and every code one inverter reports is held in a single event.

mirox 2.15.361 – 2.15.366
Read more in the documentationInverter status codes
AgentFeatureAlerts & events

Battery alarms now appear in a plant's event list

Alarms that NR Electric converters and Linyang battery containers raise about themselves now appear in the plant's event list, and an alarm closes again as soon as the device clears it. Each alarm shows how serious it is, and a Linyang alarm names the racks affected. Plants receive this with their next agent update.

mirox-agents 3.1.416 – 3.1.417mirox 2.15.361 – 2.15.366
Web appFeatureMajorAlerts & events

Inverters that need a service visit are now flagged while producing

An inverter at full output but showing wear is now flagged with "Elevated temperature", "Insulation weakening", "Phase imbalance" or "Efficiency declining". Each problem is marked on the component and listed separately.

mirox 2.15.296 – 2.15.309
Read more in the documentationEvents
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
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 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 appFeatureAlerts & events

The connection list now shows why an inverter has gone silent

Each inverter in the monitor's connection list now leads with the reason it cannot be reached: an open outage on the network device its data logger sits behind, naming that logger. Such an inverter counts as a connection issue at once, instead of only after an hour without a signal.

mirox 2.15.214 – 2.15.224
Read more in the documentationNetwork devices
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
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 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
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
AgentFeatureAlerts & events

An irradiation sensor that stops measuring is now reported

An irradiation sensor is now flagged when it reads zero while a neighbouring sensor or the plant's own production shows the sun is up. A confirmed defect also sends a notification.

mirox-agents 3.1.227 – 3.1.232mirox 2.15.166 – 2.15.172
Web appFeatureMajorAlerts & events

The monitor page now shows each plant's open events

A "Status" column on the monitor page shows a green checkmark when all is well, otherwise how many problems are open and how serious they are. Selecting it opens "Active events": everything still going on at that plant, grouped by type, each row linking to the part it concerns.

mirox 2.15.152 – 2.15.159
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