On the plant's components page, in its sensor and meter tabs, each irradiation sensor and feed-in meter now shows which data logger serves it, its data state and its last data time. A logger filter narrows the table.
The "Import" tab on a plant's "Dataflow" page now takes the ZIP archive from the plant's previous monitoring system and matches its devices to components by serial number or name. The import runs day by day and can be paused, stopped, or have what it wrote deleted.
Devices behind an "SMA Data Manager / Power Manager" or "Sungrow Logger" data logger are now listed and their alarms reach the plant's event list. A blue'Log logger gains a "String monitoring" section.
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 Huawei SmartLogger can now be added without storing its login, since most readings come in over Modbus TCP rather than the web interface. A check then reports whether Modbus worked, is switched off or not permitted, or whether RS485 address conflicts hide inverters, naming the serial numbers it could not reach.
A Meteocontrol blue'Log data logger can now be added to a plant, signed in with the password used on the device. Its devices and channels appear by name, and standard sensor channels come already recognised, needing only "Track this value".
The data logger wizard now sets up Fronius Datamanager and Datalogger devices, reading every inverter and an optional sensor card from the device itself.
A QReader data logger can now be set up by mapping its values. The "Map values" step lists every value the device sends for matching to a known measurement, and the "Dry run" step then shows which measurements the mapping produces before saving.
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".
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.
The Components, Dataflow and Networking pages now show when the plant's on-site agent is being set up, updating, not responding, or not running at all. The note names what that agent handles for the page — collecting data, finding devices or setting them up.
A plant's menu now has a "Dataflow" page with the tabs "Data Loggers", "Remote Access" and "Agent Config". The components page no longer holds them and shows only the plant's components.