Skip to content

April 2026

Changes released in April 2026.

Open in the full timeline

Web appFeatureMajor

Check what changes before you edit a plant's VPN subnets

Before you confirm adding or removing a subnet, you see what it affects: how many of the plant's devices sit inside a subnet you are removing, and that the plant's on-site agent restarts with the new settings. You are also warned if a subnet overlaps another plant's subnet on the same VPN, or the plant's own direct connection.

mirox 2.13.149 – 2.13.150
Web appFeature

Compare metric series in the export

"Compare series" adds a table under the export's metrics preview. It gives each selected metric's total, mean and standard deviation, and measures every further metric against the first one you picked.

mirox 2.13.149 – 2.13.150
Read more in the documentationMetrics export API
Web appFeature

Network scans run on their own and show live progress

A plant's network is now scanned on a schedule: hourly for small networks, daily for larger ones, and not automatically when the network is too large. While a scan runs, the plant's Networking page shows its stage, the share of addresses checked and how many devices have been found so far.

mirox 2.13.149 – 2.13.150
Web appFixMajor

Daily figures cover exactly the day, not 25 hours

Your figures for past days change slightly, with energy coming out a little lower. Until now a day's energy, losses, shutdowns, battery charge and discharge, irradiation and weather averages were worked out over 25 hours, so every day carried an extra hour. Exports, dashboards and reports now show the corrected values for past days too.

mirox 2.13.145 – 2.13.146
Read more in the documentationMetrics export API
Web appSecurity

Network devices are managed only by the plant's own organization

A plant you reach through a cooperation no longer lets you add, edit or delete its network devices, start a discovery scan or change their web access; the plant's own organization does that. You still see the devices and their availability.

mirox 2.13.145 – 2.13.146
Web appFeatureMajor

Open a network device's web interface from the device list

On a plant's Dataflow page, a device found on the plant network opens its own web interface through Mirox when you click its address. Switch the access off per device with "Web UI Proxy", store the login the device needs, and add further web addresses for one device.

mirox 2.13.128 – 2.13.143
Web appFeatureMajor

Network monitoring for the devices on a plant's network

Each plant now has its own "Networking" page listing the devices on its network, with availability, ping latency and packet loss over the last hour, 24 hours or 30 days. Devices the on-site agent finds appear on their own. "Discover" starts a scan, and "Add Device" adds one by IP address.

mirox 2.13.122 – 2.13.146
Web appFeatureMajor

Charts and live readings on the Battery page

A plant's Battery page opens on an "Overview" with state of charge, energy stored and usable capacity, and a graph of charge and discharge power for the chosen day, week, month or year. Click a bar to step into that period. Boxes, storages, modules and cells show their current readings.

mirox 2.13.118
Web appFeatureMajor

Battery storage health and components down to cell level

A plant's Battery page now shows the storage system's health and key figures and lists its components on the Box, Storage, Module and Cell tabs. Components appear automatically once the on-site agent reports them.

mirox 2.13.117
Web appImprovements and fixes

The day power curve reads correctly again, a plant's VPN assignment takes several subnets, and pages no longer stall while logging.

  • The day power curve's forecast no longer detaches from the production line, and its last 15 minutes no longer jump between meter and inverter values.
  • Assigning a plant to a VPN service takes several subnets: add or remove rows in the dialog, and duplicates are rejected.
  • The plants table's VPN dialog preselects the VPN service that plant is assigned to, instead of the first service with plants.
  • Pages no longer stall while the app records its troubleshooting log in your browser; that log is now kept in a compact form.
mirox 2.13.114 – 2.13.117
Web appBreaking changeMajor

Battery measurements for exports and reports are replaced

Plants with battery storage are measured with a new set of values covering the whole storage system down to module and cell level. The previous battery charge, discharge, level, capacity and temperature measurements are no longer offered for exports, reports and dashboards; daily battery figures now come from the new whole-system counters.

Action required: API users, and anyone who built exports, reports or dashboards on battery values: switch them to the new battery measurements. The previous battery charge, discharge, level, capacity and temperature measurements are no longer offered, so an export or dashboard built on them returns nothing. Figures collected under the previous measurements stay in your plant's history.

mirox 2.13.116
Read more in the documentationMetrics export API
Web appBreaking changeMajor

Emails about unhealthy data sources are switched off

Mirox no longer sends an email when a plant's data sources stop delivering, and no longer sends the recovery email when they deliver again. The connections overview in the app still shows which plants, loggers and devices are offline.

Action required: Plant operators and technical operations: you are no longer told by email when a plant's data source stops delivering or recovers. Watch the connections overview in the app, which lists the plants, data loggers and devices that are currently offline, and their availability over the chosen period.

mirox 2.13.112
Web appImprovements and fixes

Cooperations get their own tab, the plants table lists each plant's components, and VPN services are restricted to organization admins and moderators.

  • The plants table shows each plant's feed-in meters, inverters, combiner boxes, strings and sensors, with a legend for how their data is collected.
  • Cooperations moved to their own tab on the organization page, with separate lists for outgoing and incoming cooperations, each searchable and paged.
  • Members no longer see the VPN services on the organization page; only organization admins and moderators do.
  • A VPN service with plants assigned can be deleted; the confirmation names the plants removed, and the plants table's VPN dialog can remove a plant.
  • Adding a VPN service asks for its client address; editing one lets you upload a new WireGuard configuration file or replace its keys.
  • Adding or editing a VPN service or a direct VPN rejects 0.0.0.0/0 and warns when a network overlaps another connection of the plant.
  • Adding or editing a plant's direct VPN connection no longer asks for a gateway address; the connection is set up and checked without one.
  • Opening a device that has not yet reported a status no longer fails.
mirox 2.13.83 – 2.13.112
Web appFeatureMajor

Connections page for VPN services, plants and data loggers

The new "Connections" entry in the main menu lists your organization's VPN services, plants and data loggers with their availability. Its "Live" tab shows everything that has been offline for more than 15 minutes, and which plants, loggers and components are affected.

mirox 2.13.107 – 2.13.109
Web appFeature

Data loggers and remote access move to a plant's Dataflow page

A plant's menu has a new "Dataflow" page with the tabs "Data Loggers", "Remote Access" and "Agent Config". The three moved off the components page, which now shows only the plant's components. The page header carries agent health, logger health and traffic for the chosen period.

mirox 2.13.107 – 2.13.109