Skip to content

July 2026

Changes released in July 2026.

Open in the full timeline

Web appFeatureMajorAlerts & events

Notifications now go to Slack, Teams, Discord or an HTTPS address

The profile's "Notifications" tab has a new "Third-Party Notifications" card with up to five destinations — a Slack, Microsoft Teams or Discord channel, or an HTTPS address — each receiving the notices chosen per plant and subject. They arrive the moment the event happens, whether or not anyone is online.

mirox 2.15.73 – 2.15.79
Read more in the documentationNotifications
Web appFeatureAlerts & events

An email now arrives only if the phone notification goes unopened

While a phone can show Mirox notifications, the email for a notification waits five minutes and is sent only if the notification has not been opened on the phone. The "Email Notifications" card on the profile's "Notifications" tab explains this.

mirox 2.15.64 – 2.15.72
Read more in the documentationNotifications
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
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
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
Web appFeatureAlerts & events

An inverter that stops producing in daylight now raises an event

An inverter that reports no production for about 15 minutes while irradiation is at least 50 W/m² now opens a "Component production outage" event on the "Activity" page, and the event closes on its own once production resumes. Times with snow, frost, fog or an active curtailment do not count.

mirox 2.14.177 – 2.14.184
Read more in the documentationActivity
Web appFeatureMajorAlerts & events

A "Tickets" page lists the tickets of every plant

A new "Tickets" page lists the tickets of every reachable plant. A ticket describes a problem, is assigned to a colleague and discussed in comments, with people mentioned by @ and the components and events it concerns linked.

mirox 2.14.168
Web appFeatureMajorAlerts & events

An "Activity" page gathers the events of every plant

A new "Activity" page gathers the events of every reachable plant: what happened, who or what caused it, and when. A grid of the last 30 days shows which days were busy, and the feed filters by day, priority or type.

mirox 2.14.168
Read more in the documentationActivity