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.
"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.
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.
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.
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.
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.
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.
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.
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.
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 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.
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.
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.