Changelog
Every change to Mirox, grouped by month. Filter by group or by kind of change.
November 20261
October 20262
Stored files with an umlaut, en dash or emoji in the name download again in storage, from a share and in the datasheet view.
The "Reports" page now offers a "Technical Report" template
The "Reports" page now offers a "Technical Report" template with the plant's master data, panel and inverter inventories, a performance ratio analysis by day and month, a metrics chapter, high-priority events and a glossary. The template's title page can be composed in the editor and matches the PDF and document exports.
September 20265
The "Reports" page now shows data readiness before publishing
The "Reports" page now shows data readiness in four rows, monitoring, satellite, settled curtailment and official prices. Publishing a report lists non-final metrics with "Regenerate first" or "Publish anyway", and a recomputed settled month reads "Out of date".
The "Data Export" tab now offers a picker down to battery-cell level
The "Data Export" tab now offers search, a value mode and a picker down to sensor, turbine and battery-cell level. Export templates offer strict or lenient handling of mixed time steps.
A "Reports" page now spans the whole organization
An organization's "Reports" page now has its own entry in the sidebar. Templates can span several plants.
Every plant now has a "Reports" page
Every plant now has a "Reports" page, on which a template and a period are picked and the report generated and downloaded. While a report is built, its cover and language are set, text added, a chapter renamed or hidden, and the report published to keep its files available to download.
Reports and exports can use metrics an organization defines itself
The reports page now has a "Metrics" tab where an organization defines its own figures from the measurements its plants record, for use in reports and exports. A metric is reported as a plant value or per component, at a chosen finest resolution, and the assistant can write and check one inside the editor.
August 20261
Raw data exports stop above 36,000 values in a single column
A raw data export is refused if one column would hold more than 36,000 values — a full year at 15-minute resolution still fits — or if splitting by plant would give more than 50 columns, one per metric and plant. A shorter period, a coarser step, or merged plants keep an export within both limits.
Action required: API users: keep every raw data export within 36,000 values per column — a full year at 15-minute resolution — and, where you split by plant, within 50 columns (metrics × plants). Anything above either limit now fails instead of running. Shorten the time range, choose a coarser step, or merge the plants instead of splitting them.
July 20264
Raw data can now be exported for a single inverter, combiner box or string.
- The raw data tab offers a "Detail level" — park, inverter, combiner box or string — then the components, merged or split into columns.
- The production page now labels the grid line "Feed-In", and the "Production Inv." overlay survives a refresh and a shared link.
- The day power curve now shows expected production from the plant's own irradiation sensor, or from weather data when it has none.
Raw exports now merge plants or keep them apart
For raw data pulled through the API, the setting that combined plants across a portfolio is gone. Several plants are now combined either as one series per measurement or as one series per plant named after it, chosen on the export page with "Merge" or "Split".
Action required: API users: raw data export calls no longer accept aggregation, start_at_zero or delta — these parameters are ignored. Send value=plain, value=start_at_zero or value=use_delta instead of the two booleans, and multi_park_agg=merge or multi_park_agg=split to choose how several plants are combined. For metrics exports, move to park, portfolio and year with quarter, month, week or day; timeframe, period, park_uids and portfolio_uids are still accepted.
Raw data exports through the API now select metrics by id
A raw data export requested through the API now names the raw metrics it wants by id. Query text sent along is no longer run, and anything that is not one of the raw metrics is refused.
Action required: API users: change your raw data export calls to send metric_ids — one to twenty raw metric ids, which you can read from the raw metrics list the API offers. A list of queries is still accepted, but only each entry's id counts and it must be a raw metric id; anything else is refused, and the whole export fails. Query text you send is no longer executed.
A whole portfolio can now be exported, and CSV downloads no longer need a saved template. Each export tab shows the API call behind the current selection.
- On the export page, the raw data tab now takes a portfolio as well as plants.
- Each export tab now shows a "Live URL Preview" of the API call for the current selection, with a button to copy it.
- The metrics picked can now be downloaded as CSV without saving an export template first.
- The raw data tab can now show the change per interval instead of the running total, and the column language can be picked.
- Metrics in a raw export now carry shorter names in the export language, in the picker, the chart and the CSV headers.
- Signing in with two-factor authentication no longer shows an unexpected error before the code is entered.