Home April 2026 2026 Nov1 Oct2 Sep5 Aug1 Jul4 Jun1 May2 Apr4 Jan3 Open in the full timeline
Wed, Apr 22 Web app Improvements and fixes Reports, exports & files
Export templates now show their metrics in the row, and the list offers a search, copying a template's ID and a confirmation before deleting. In the export, metrics are always listed in the same category order, with energy and power first. The export now offers "Curtailment Losses" and "Technical Loss Energy" in place of the two earlier energy loss entries. Opening a device's web interface no longer sends the browser to an address outside Mirox. mirox 2.13.169 – 2.13.177
Sun, Apr 19 Web app Feature Reports, exports & files
"Compare series" adds a table under the metrics preview in the export. It gives each selected metric's total, average and how much it varies, and measures every further metric against the first one picked.
mirox 2.13.149 – 2.13.150
Web app Improvements and fixes Reports, exports & files
In the export's metrics view, whole portfolios can now be picked, and every accessible plant inside them is included. Weekly, monthly, quarterly and yearly resolutions are offered wherever the chosen period allows them. Hovering a chart in the export now shows the metric's name instead of a code. The year list in the export no longer offers years after the current one. mirox 2.13.149 – 2.13.150
Sat, Apr 18 Web app Improvements and fixes Reports, exports & files
With "Full weeks" turned on, the first and last week of the selected period are filled out to all seven days. The preview marks weeks that fall only partly inside the selected range with * and explains the mark. Weekly points in the preview chart now read CW12, and daily points show only the day of the month. A whole month can now be exported as a single row. Choosing the tab character as separator now gives a tab-separated file, and the preview shows values containing quotes or the separator correctly. mirox 2.13.148
January 2026May 2026 Jump to month
These release notes are generated automatically from our engineering changes and may contain mistakes. For anything critical, ask us directly: support@mirox.io