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.
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.
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.
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.
The bell in the header now lists what happened on plants, tickets and the organization, and selecting an entry opens it there. The profile's "Notifications" tab sets which kinds of news arrive, from which priority on, and whether they also arrive outside the app.
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.