May 2026
Changes released in May 2026.
The web app is now in Spanish, French, Portuguese and Italian
The web app is now available in Spanish, French, Portuguese and Italian, alongside English and German. An invitation email is now sent in a language chosen when the invitation is made.
An organization's documents can now be kept in folders
An organization's own documents can now be kept in Mirox, not only a plant's. A "Storage" tab on the organization page holds folders, uploaded files, a search, and the download of a selection as one ZIP file.
A member can now be given technical or commercial asset-manager authority without being made a moderator.
- An organization can give a member the "Asset Manager (Technical)" or "Asset Manager (Commercial)" role, between Moderator and Member.
- A moderator now holds the same permissions on a plant as an organization admin, including deleting a plant or a portfolio.
- When a new version is out, "A new version of Mirox is available" offers "Refresh", and the page refreshes itself after 120 seconds.
- A contact's street, ZIP code and city can now be recorded on a plant's "Core Data" page.
- "Edit Park" on a plant's "Core Data" page appears only to members who may change that plant's data.
- Opening a file without permission no longer fails with an unexpected error, and a message says permission is lacking.
A plant's "Core Data" page now records EEG values and contracts
A plant's "Core Data" page has a new "Market" tab. Under "Configure" it records the plant's EEG values with the peak power and period each one covers, its grid operator and its PPA / direct marketing contracts, and shows the weighted anzulegender Wert and how much of the installed peak power the EEG values cover.
Huawei SUN2000 inverters now report phase-to-neutral voltages
AC voltages of Huawei SUN2000 inverters of the 60KTL, 185KTL and 215KTL families read through a Huawei SmartLogger no longer show line-to-line values under the phase names. The values now shown are the phase-to-neutral voltages, which are lower than the figures shown before. Plants receive this with their next agent update.
Huawei SmartLoggers can now be set up as data loggers
A Huawei SmartLogger 1000, 3000 or 4000 on a plant's network now appears under "Possible loggers" on the "Dataflow" page and reads the inverters, strings and sensors behind it. Plants receive this with their next agent update.
A plant's "Core Data" page holds more contacts and gives each peak power figure its own place. The dashboards of a newly created plant or portfolio are ready right away.
- A plant's "Core Data" page now links a grid operator and a project company, and an "Other" contact takes a label of its own.
- A plant now lists only the contacts assigned to it, no longer those assigned to its portfolio.
- Park type, site and inverter peak power and the DC/AC ratio now each have their own place on the "Core Data" page.
- An inverter, string or combiner box that is delivering data no longer shows the "No data for 1 year" badge in the component lists.
- For API users, GET /v1/park/{uid}/forecast now returns five days of daily forecast and cloudless-sky reference energy plus hourly forecast power for a plant.
Phoenix Contact PLCnext controllers now serve as data loggers
A Phoenix Contact PLCnext controller found on a plant's network can now be set up as a data logger under "Possible loggers" on the "Dataflow" page, reporting the active-power limits from the grid operator and the direct marketer every 30 seconds, in percent. Plants receive this with their next agent update.
A Janitza meter can now be entered as a data logger by hand. This year's Jahresmarktprämie now appears on the "Market" page as a running estimate per technology.
- On a plant's "Dataflow" page, "Add Logger" now accepts a Janitza meter entered by hand, without waiting for a network scan to find it.
- This year's Jahresmarktprämie now appears on the "Market" page as a running estimate for each technology, updated with every price update.
A network device's own web page at a plant opens again, including over slow connections and on older equipment.
- A device's web page now loads properly even when it pulls in many pieces at once, including on older equipment.
- A device on a slow connection now gets 30 seconds to answer instead of 10 before the page gives up.
The username and password saved for a network device can be shown
On a plant's "Networking" page, a device's "Authentication" tab now shows the username and password saved for it, with the password hidden until it is revealed. Only members with an administrator or technical role can see them, and anyone else is asked to contact a teammate who can.
Day-ahead prices, Marktwert and Jahresmarktprämie have their own page
A "Market" page in the main menu now shows day-ahead electricity prices for Germany (DE-LU) for any chosen day, with tomorrow's prices appearing once the auction has closed. The same page shows the monthly Marktwert and the Jahresmarktprämie per technology.
Data loggers added by the organization can now be edited or removed
A data logger added by the organization itself can now be changed or removed through the actions menu of each logger in a plant's "Dataflow" list. "Edit logger" changes its display name, how often it collects, and notes, and "Remove logger" stops collecting from it and puts the device back under "Possible loggers".
During a guided logger setup, a device that stays silent now comes with the reason it did not answer.
- During a guided logger setup, the reason a device did not answer is now shown, and "Reconnect" tries it once more.
- A plant's "Dataflow" page now also counts data from the sites connected through the plant's own VPN server.
A Janitza meter set up through the guided logger setup now reports feed-in in the right direction, whichever way its current transformers are wired.
A plant's "Networking" page now offers "Abort scan" for a running network scan and "Regenerate peer config" for a WireGuard site's connection file. Availability figures for a plant's VPN connections no longer show gaps.
- A running network scan can now be stopped on a plant's "Networking" page with "Abort scan", keeping the devices already found.
- A device deleted on a plant's "Networking" page stays deleted after the on-site agent next reports what it found.
- Availability figures for a plant's VPN connections no longer show gaps after the on-site agent restarted or a connection switched between WireGuard and OpenVPN.
- A WireGuard site's connection file can now be rebuilt with "Regenerate peer config", keeping its name, subnets and address while the on-site agent restarts once.
Devices found on a plant's network can now become data loggers
A plant's "Dataflow" page now lists the devices found on its network that Mirox can already read, under "Possible loggers". A guided setup starts from one of them, shows a test read with the device's raw values next to the readings Mirox would publish, and collects nothing until the changes are applied.
A power cap of 85 % or more no longer counts as curtailment
A plant held at a power cap of 85 % or higher previously counted as curtailed all day, which showed curtailment losses that did not exist and skewed its performance ratio. Only a cap below 85 % now counts as curtailment. Plants receive this with their next agent update.
Plants without an irradiation sensor now get a performance ratio
The performance ratio of a plant that uses weather data instead of an on-site irradiation sensor now shows a figure where it showed none before, as the gaps between its 15-minute weather readings no longer count as missing data. Each plant receives this with its next on-site agent update. Plants receive this with their next agent update.
A data source that was unreachable when the on-site agent started now delivers its readings as soon as it answers again. A restart of the agent is no longer needed.
A new solar plant is now set up step by step
The plant list now shows how far each solar plant's setup has come. A plant, active from the moment it is created, opens on its setup steps: uploading documents, completing the plant's data, setting up the VPN, checking the network devices found and mapping the data loggers.
A plant's "Wizard runs" list now shows a member's own runs and those started by a device at the plant. Other members' runs no longer appear in it.
The "Core Data" page now stores a plant's documents in folders
The "Storage" tab of a plant's "Core Data" page now opens a file explorer for organization admins and moderators. Files of any type up to 50 MB can be uploaded, sorted into folders, moved, renamed or deleted.
Changing a plant's VPN settings and issuing a fresh certificate is now one step instead of two.
- On a VPN connection, "Apply changes & rotate certificate" applies the waiting settings and issues a fresh certificate in one step.
- An OpenVPN option on a plant's VPN connection set back to its default value is now saved instead of being lost.
- Opening the web app while still signed in now goes straight in instead of showing the sign-in page.
- The API history can now be narrowed to the calls that changed something with "Non-GET".
A plant's hosted OpenVPN server now offers a choice of key type
An OpenVPN server hosted by Mirox for a plant now has a "PKI key algorithm": "RSA-2048 (industrial standard)", which nearly every router accepts, or "ECDSA-P256 (modern)". On an existing server, "Rotate CA certificate" issues a new authority and new certificates for everyone connecting.
A cloudless-sky reference now shows what a plant would produce
A plant's production can now be compared, for every day, with the power and energy it would reach under a completely cloudless sky, in 15-minute steps, with and without the inverter peak cap. The same reference is rebuilt daily as a six-day outlook. Plants receive this with their next agent update.
Deleting a plant's VPN connection now shows what is lost before the deletion is confirmed.
- Before a plant's VPN connection is deleted, the confirmation shows how many network devices lose their route, and some of their addresses.
- A personal VPN certificate from the profile page now also reaches the networks of sites connected to a VPN hosted by a plant.
- "Reachable subnets" on the profile page's "VPN" tab now updates on its own after a plant's subnets change.
- On the "Topology" tab, a device whose address lies outside every configured subnet of its plant is now listed in a separate group.
- A request for access to Mirox now receives a confirmation email in the language the request was made in.
- In an organization's plant list, "Manage VPN" now opens that plant's "Networking" page instead of a separate window.
The performance ratio is no longer skewed by an irradiation sensor that freezes during the day while another sensor still sees daylight.
The sign-in page no longer shows an error message when it is opened or after signing out.
On a phone, a page's tabs are now picked from a dropdown. Until now the tab strip ran off the edge of the screen.
Live logs now open for a plant's agent and each VPN connection
On a plant's "Agent Config" tab, "Open live logs" shows what the on-site agent is recording right now, starting with the last 100 lines. On the "Networking" page, each VPN connection's menu now offers "Open Logs" for that connection's own records.
The assistant now diagnoses a plant's VPN connection that is down
While a VPN connection at a plant is down, its menu on the "Networking" page offers "Diagnose", and the assistant reads that connection's recent records and reports what it found. Where it can, it suggests a fix that is put in place with "Apply".
At a brand-new plant, the round device chart on the "Networking" page no longer disappears. Each device stays grey until its first readings arrive.
OpenVPN connections at a plant no longer look offline while they are in fact working. The "Networking" page now shows their real status and how much data they have used.
Device access now depends on the job held on the plant
A plant's devices can now be reached through a personal VPN only with "Operator" on that plant, or as an admin or moderator of the organization that owns it. With "Technical Manager" or below, access to that plant's devices is lost.
Action required: Organization admins: give any member who must reach a plant's networks over the VPN the "Operator" job on that plant, and any member who must open a device's web page at least "Technical Manager". Ask them to download their VPN connection file again once you have changed it.
An older router can now join a plant's OpenVPN
An older router that cannot speak modern OpenVPN can now join a plant's VPN. A "Compatibility preset" — "Modern (2.5+)", "Legacy 2.3 era" or "Legacy 2.2 (Blowfish)" — is chosen when the plant's OpenVPN connection is set up or edited.
A network scan at a plant now shows devices while it is still running.
- On a large plant, the device list fills batch by batch during a scan instead of only when the scan finishes.
- A device that answers only sometimes now turns up in a scan, which probes each address twice and more gently.
- When two-factor sign-in is set up, the authenticator app now saves the entry under "Mirox".
The web interface of an older device that offers only outdated encryption can now be opened.
The "Access Log" now lists sessions on a device's web interface
The plant's "Access Log" tab now lists who opened a device's own web page through Mirox, not just who connected by VPN, with the person, the device and what they did there. Sessions appear once the plant's on-site agent has been updated.
The VPN page on the profile now searches and filters its subnet list and shows details of the certificate, for accounts that can reach many plants.
- The subnet list can be searched and filtered by portfolio and plant, with subnets claimed by two plants listed first.
- The certificate now shows its public key and creation date.
A network device's own web page, opened from a plant, now lands on the page the device actually shows, even when the device redirects to another address.
Larger transfers to devices at a plant no longer stall over a VPN connection. The downloaded connection file now carries the setting that was missing.
Remote connections to a plant's networks are now logged
A plant's "Networking" page now has an "Access Log" tab listing every connection made to the plant's networks from outside, grouped by day. Each connection has its own rows naming the person, when they connected, the network they reached and how much data they moved.
The "Recent connections" list on the profile page now shows more about each of the account's own VPN connections.
- The "Recent connections" list now shows each connection's length, location, IP address and data used, next to its start time.
- Deleting a VPN certificate no longer clears earlier connections, and a new certificate keeps them too.
- The downloaded VPN configuration file is now named after the account's email address instead of a code.
The profile page now issues a VPN certificate for plant networks
The profile page has a new "VPN" tab, where "Issue cert" downloads a WireGuard configuration that reaches the networks of the plants a user has access to. "Reachable subnets" lists what the tunnel reaches, and "Recent connections" shows when it was last used.
Sessions and API tokens now show which browser or tool last used them.
- Each session and API token now names the browser or tool that last used it, or shows "Unknown client".
- After a change is saved on a plant's "Networking" page, a notice states that the on-site agent is applying it and will restart shortly.
The "Networking" page now shows who is connected and their traffic
A "Connection status" and a "Traffic" column on the plant's "Networking" page now show, for every connection and everyone using it, who is connected right now, how much of the chosen period they were connected, and what they received and sent today.
An API token can now get a new secret without being recreated
"Rotate" in a token's menu under "API Tokens" on the profile page now gives an existing token a new secret value, keeping its name, description and permission level with a newly chosen expiry. The old value stops working immediately.
A plant can now host a VPN for other sites and people
A plant can now host its own VPN, with the keys and the port created by Mirox. On the plant's "Networking" page, other sites are added on the "Site VPN" tab and individual people on the "User VPN" tab.
Network devices now show their current status on the Connections page and on a plant's Networking page, instead of a reading from minutes ago.
- On the Connections page, a device no longer shows as offline while its availability reads 100%.
- On a plant's Networking page, a device's name no longer stays marked as offline after the device has come back.