An organization's VPN row now has a "Move to another host" action. Before the move is confirmed, it shows where the VPN would land, how many plants restart on site and lose data briefly, which plants get a new VPN address, and which routers keep the old one and stay disconnected until restarted.
Inverters now show what they report about themselves: "Stopped by command" when one was switched off, "Protective stop" when its protection tripped, and "Device fault" when the machine reports a fault the measurements cannot show. The maker's own wording and how often it was raised are shown alongside.
The status code an inverter reports about itself now opens an event when the device was stopped by command, tripped on its protection, raised a safety alarm or is throttling itself back. The health column shows "Stopped by command" and "Protective stop", and every code one inverter reports is held in a single event.
A swapped inverter, listed twice because the data logger gave the new unit a new address, is now spotted as a pair and offered for confirmation on the components page. Once confirmed, the new inverter takes over the old one's configuration, the old unit is retired, and the graphs keep the earlier history.
Each remote-access connection on a plant's VPN tab now shows whether it is really working, rechecked while the tab is open. One that is set up but not running is marked red, with the next step to take, and one that is running while the remote site has not connected is marked amber.
An inverter at full output but showing wear is now flagged with "Elevated temperature", "Insulation weakening", "Phase imbalance" or "Efficiency declining". Each problem is marked on the component and listed separately.
Remote access over IPsec (IKEv2), for site routers that speak nothing else, now shows whether the remote site is connected, with its availability and traffic, instead of an unknown state. A site set up but never connected stays in the list, and "Add peer" attaches a second router.
The assistant now answers where a setting or page is with a link to it, and explains what a type of event means or how a measurement is worked out. It also lists what a plant measures, draws the curve for a component or a whole plant, and points out stretches with no data.
A "Curtailments" section on a plant's "Production" page now lists every settled curtailment and every live detection in the period shown, each with its window, its Ausfallarbeit, how it was settled and the compensation. The graphs now draw the same figures, so the last days of a period stay empty until the settlement has run.
The "Add a VPN connection" wizard now offers "IPsec (IKEv2)" beside WireGuard and OpenVPN, for industrial routers that speak nothing else. Mirox can host the tunnel for the plant or connect to a router that hosts it, with a pre-shared key that is generated or pasted.
Every network of a plant can now be tagged by what it carries — "Plant control", "Network infrastructure", "Cameras" or "Security systems" — when it is added, edited or opened for remote access. The new "Security Officer" role reaches only the networking, camera and security networks, never production, revenue or plant control.
A new "Control Units" tab on a plant's components page now lists the signals the plant is regulated by: the cap from the grid operator, the cap from the direct marketer, and the setpoint the plant controller applies. Each signal names the data logger reporting it and can be renamed, hidden or given a note.
The components page now has a tab for each battery level — "PCS", "Box", "Storage", "Module" and "Cell" — with a checkbox on every row. "Edit Components" then sets or clears the datasheet for the ticked rows, for everything below the filtered parent, or for every component of that type.
An organization's own Anthropic, OpenAI or self-hosted account can now be added by an administrator or moderator under "AI providers" in the organization's AI settings. The models members may use are picked from it and one marked as the default, after which members choose a model per conversation.
Battery plants now have an "Energy flow" page. It shows live power through the converters and racks, state of charge, the voltage and temperature spread of the cells, a heatmap of every cell in a rack, and the same curves over a chosen period.
With "Group string names by MPPT" switched on under a solar plant's "Component Naming" settings, its strings read "MPPT 2 – String 1" in the components list, a string's details, the analysis tables and tickets. Strings whose inverter does not report how many inputs each MPPT has keep their plain numbering.
The assistant now answers what a plant earned in a month or a year: production revenue, the compensation for grid and marketer curtailment, and the market value behind them. Several plants are compared side by side and against the yield the plan expected, and months not yet settled are named as provisional.
A model can no longer be chosen for the assistant, which always answers on the model Mirox provides. A model an organization had chosen earlier is cleared the next time the AI settings open.
A dropdown beside the chat's input bar sets how much reasoning the assistant does before it answers: "Deep", "Medium", "Low" or "Off". Every conversation opened or switched to starts on "Medium".
Each inverter in the monitor's connection list now leads with the reason it cannot be reached: an open outage on the network device its data logger sits behind, naming that logger. Such an inverter counts as a connection issue at once, instead of only after an hour without a signal.
The monitor list now has a "Live" column showing the power each plant is feeding into the grid, refreshed every 10 seconds. Below it stand the plant's two power limits, from the grid operator and from the direct marketer, each coloured only while it is holding the plant back.
Curtailment episodes detected at a plant now appear in the plant's events as their own entries, with the limit that applied and the period covered. "Exclude from settlement" on an entry leaves it out of that month's curtailment figures, and "Re-include in settlement" puts it back.
The "Edit logger" dialog now has a "Configuration" tab. There, the options a data logger offers and the "Serial / metric id prefix" its components are identified by can be changed without deleting and re-adding the logger, and "Apply changes" sends them to the plant.
A solar plant without a feed-in meter can now be given a virtual one with "Add Virtual Meter" on the plant's "Feed-in Meters" tab. The on-site agent then reports the plant's grid power and total grid energy as the sum of its inverters, as estimates rather than measured readings.
A "Status" column on the monitor page shows a green checkmark when all is well, otherwise how many problems are open and how serious they are. Selecting it opens "Active events": everything still going on at that plant, grouped by type, each row linking to the part it concerns.
The "Sites" tab now lists, under "Shared with your organization", the plants and portfolios other organizations share, below the organization's own. Each row names who shared it, the role given, the portfolio a plant comes through, and reads "visible only — no data access" when it cannot be opened.
The assistant now answers a question about a plant's remote access with every connection: its role, protocol, the sites it connects, the networks it routes, and each one's last known status. Where something looks wrong, it names a likely cause.
Three tabs beside the logs — "Live status", "Diagnose" and "Debug" — show whether a plant's remote access is working. "Live status" shows each connection's address, throughput and how long ago it last checked in, updated once a second.