Skip to content

June 2026

Changes released in June 2026.

Open in the full timeline

Web appFeatureRevenue & market

A PPA contract can now be assigned to a plant segment

On a plant's "Market" tab, a PPA contract can now be assigned to the segment it covers instead of being given a typed power value. The contract takes that segment's panel peak power, a contract covering the whole plant stays on "Whole park", and the tab shows the total capacity assigned.

mirox 2.14.148 – 2.14.151
Web appImprovements and fixesSolar equipment

An analysis now fills in while it runs, instead of only once each of its days is finished.

  • While an analysis runs, the day being processed shows how many strings already have a result, not only once that day is finished.
  • The analysis summary now lists strings whose orientation could only partly be confirmed as a group of their own, apart from fitted and unassessable strings.
  • Pages and downloads from a device opened through remote access no longer stop part-way once the remote-access configuration is downloaded again.
  • Grey stretches now appear between a data logger's readings only where the logger really stopped reporting.
mirox 2.14.144 – 2.14.147
Read more in the documentationComponentsVPNData loggers
Web appImprovements and fixesProduction & yield

Two more values can now be recorded in a plant's settings.

  • A plant's "Grid Transmission Limit" can now be entered in its settings, and its "Yearly Degradation" in percent beside the monthly PR targets.
  • A data logger now opens on a "Mapped metrics" overview, where one click removes a mapped reading and the change is saved straight away.
mirox 2.14.142 – 2.14.143
Read more in the documentationData loggers
Web appFixMajorProduction & yield

Production now covers days the feed-in meter did not report

Days when the feed-in meter did not report, or reported an implausible value, no longer drop out of production figures. Production for those days is taken from the inverters instead.

mirox 2.14.137 – 2.14.141
Web appFixCurtailment & grid limits

Curtailment by settlement method is compared alike in the revenue API

The comparison of curtailment energy by settlement method in the API's revenue response previously depended on the data-quality filter and the plant's clipping setting. It now counts each method's booked curtailment energy alike, with inverter clipping considered.

mirox 2.14.137 – 2.14.141
Web appFeatureMajorSolar equipment

A plant's inverters can now be grouped into segments

The "Segments" tab of a plant's components page now groups its inverters into blocks, roofs or sub-parks, each with a name of its own. Each segment adds up the panel and inverter peak power of its inverters, unless a value is set by hand instead.

mirox 2.14.137 – 2.14.141
Web appImprovements and fixesNetwork & remote access

The status dots of data loggers and network devices now follow the live readings. A device that went down no longer shows green.

  • When a device's web page cannot be opened through remote access, a Mirox page names the reason instead of a raw error.
  • Each of a device's web pages can be given its own login, separate from the device login.
  • Devices that block unfamiliar addresses, such as a FRITZ!Box with rebind protection, can now be opened as well.
  • On a plant's "Market" tab, "Accounting country" can now be set to "None" for a plant without EEG accounting, which hides the EEG values.
  • A QReader data logger's value mapping now offers "By External (W)", a power limit set by external control in watts, optionally tied to a segment.
mirox 2.14.137 – 2.14.141
Read more in the documentationProxyData loggers
Web appFeatureRevenue & market

A running estimate of the Mischpreis is now calculated

Until the official quarterly value is published, a running estimate of the Mischpreis (mixed price) used for settlement is calculated from the reBAP and AEP forecasts, covering about 1 month. The official value is recorded once it is published.

mirox 2.14.133 – 2.14.136
Web appImprovements and fixesData collection

A data logger's value mapping can now be corrected after setup through "Edit metrics". Strings on several selected inverters can now be edited in one step on a plant's components page.

  • Newly detected components show "Collecting data…" for their first two hours.
  • A plant's pages no longer show the on-site agent as not responding right after a configuration change restarts it.
  • A plant's solar analysis page no longer shows a clear-day count larger than the days its inverters have been reporting.
  • The mapping of an irradiation sensor on a data logger now records whether it measures horizontal or module-level.
mirox 2.14.133 – 2.14.136
Read more in the documentationData loggersComponents
Web appFeatureMajorBattery storage

A plant's battery storage now has a page of its own

Battery storage now has its own page in the plant, showing state of charge, stored energy, usable capacity and the component count as figures, a time-series graph, and a real-time table of the battery components.

mirox 2.14.124 – 2.14.131
Web appFeatureReports, exports & files

A report's metrics and resolution can now be chosen

In a plant's report, the metrics can now be selected, and the resolution can be switched between daily, weekly and monthly. The report's table and bar chart show the selected metrics at the chosen resolution.

mirox 2.14.124 – 2.14.131
Web appImprovements and fixesThe app itself

A plant's production charts now fill the hours a remote-access outage left without data with expected production. The "Forecast" page now lists the hours of today and tomorrow with a negative day-ahead price.

  • A plant's ticket list can now be filtered, sorted and paged.
  • A plant's networking page shows each device's type, address and online status.
  • A contact's SEPA direct-debit mandate can now be signed from the contact's actions.
  • A plant's component table now marks offline devices.
  • A plant's day power chart now marks snow periods.
mirox 2.14.124 – 2.14.131
Web appSecurityUsers & access

Tickets, tariffs and devices can be changed only if the role allows

Changing a ticket comment, a plant's tariffs, its contracts or its devices now works only where the member's role allows it, while read-only access still opens them. Remote-access connections are listed only where the member's access covers them.

mirox 2.14.77 – 2.14.84
Web appBreaking changeMajorNetwork & remote access

A connected site's tunnel address is now assigned automatically

A connected site added to a plant's remote access no longer asks for a tunnel address, which is now assigned. Connected sites that already exist keep their current address.

Action required: Organization admins and technicians who set up remote access: when you add a connected site, take its tunnel address from the configuration you download instead of choosing one, and use that address when you configure the remote router. Connected sites that already exist are untouched and keep their current address, so nothing has to be changed on routers that are already connected.

mirox 2.14.75 – 2.14.76
Read more in the documentationVPN
Web appImprovements and fixesThe app itself

A combiner box's figures open again. Deleting a plant's remote access now asks for its name to be typed first.

  • Deleting a remote-access server or a connected site now asks for its name, and the warning states that its keys are gone for good.
  • A combiner box's figures open again instead of failing with an error.
  • A connected site that has been deleted no longer counts in the plant's remote-access status.
  • When plant documents are uploaded, the suggested installed capacity now covers every construction phase, and the grid operator and planning company are recognised more reliably.
  • A subnet typed but not added to the list now triggers a warning instead of the connected site being saved without it.
  • Times from late yesterday no longer show as today, and dates written in words now follow the calendar day.
mirox 2.14.75 – 2.14.76
Read more in the documentationVPNRemote accessComponents
Web appFixMajorCurtailment & grid limits

Saving a market option no longer switches off inverter clipping

Saving any option in a plant's market settings no longer sets inverter clipping to be ignored. Since 1 June, plants where that happened showed too much curtailment energy and a compensation calculated from it that was too high as well.

mirox 2.14.71 – 2.14.74
Web appBreaking changeMajorThe app itself

Portfolios with plants and plants with loggers cannot be deleted

A portfolio can no longer be deleted while plants are still assigned to it. A plant can now be deleted while it is running, but only once every data logger has been removed from it.

Action required: Organization admins: to delete a portfolio, first move its plants to another portfolio or delete the plants you no longer need, then delete the empty portfolio. To delete a single plant, remove its data loggers first; deactivating the plant is no longer required.

mirox 2.14.68 – 2.14.70
Web appFixMajorCurtailment & grid limits

Curtailment now counts the production the imposed limit forbids

Curtailment on the dashboard and on a plant's production page is now the production the imposed limit forbids, attributed to the grid operator or the direct marketer and shown per settlement method. Figures from 1 June are calculated this way, while earlier periods keep the figures of the previous calculation and are marked "Legacy Data".

mirox 2.14.68 – 2.14.70
Web appFeatureMajorProduction & yield

The "Forecast" page shows a five-day forecast for every plant

A "Forecast" page now lists a five-day production forecast for every visible plant, filtered by portfolio, searched by name and paged through as a list. Each day shows weather, temperature, wind and an energy figure, plus a power curve under the clear-sky ceiling.

mirox 2.14.68 – 2.14.70
Web appImprovements and fixesProduction & yield

A plant's production page is rebuilt around the performance ratio. Remote access now reaches several connected sites at once.

  • Several connected sites can now be reached through one plant's remote access, with each site's subnets, keys and status managed on the "Peers" tab.
  • The production page is rebuilt: performance ratio per source, an inverter table, site specifications, and a day curve with the clear-sky ceiling and expected production.
  • Stretches where the plant could not be reached are now filled with the energy the weather model expects, shown as "Expected (no connection)".
  • The API now returns a plant's revenue and EEG compensation per month or year through GET /v1/park/{uid}/revenue, with Marktwert, Marktprämie and curtailment per settlement method.
  • The dashboard button again opens on the whole selected day, instead of on an empty range.
  • A plant's address is saved again when it is changed in the plant's details.
mirox 2.14.68 – 2.14.70
Read more in the documentationVPNRemote access
Web appImprovements and fixesNetwork & remote access

Strings added by hand can now be deleted, and a network scan that finds nothing says why.

  • Strings added by hand can be selected on the components page and deleted after a confirmation prompt, while detected strings stay.
  • A network scan that finds nothing now says whether it could not reach the plant network or the scanned range held no devices.
  • All address ranges of a direct remote-access connection are edited in one list and saved together; ranges already used on the plant are flagged.
  • A plant's on-site agent keeps running when the plant is removed from an organization's remote access or that remote access is deleted.
mirox 2.14.57 – 2.14.67
Read more in the documentationComponentsVPNRemote access
Web appFeatureMajorSolar equipment

Deep analysis picks its own days and runs in one press

"Deep Analysis" on a plant's components page now runs without a date or analysis mode to choose. It looks back over the last 90 days of weather, picks up to seven mostly clear days, and works out orientation, tilt and panel count for every string from them.

mirox 2.14.56
Read more in the documentationComponents
Web appImprovements and fixesNetwork & remote access

The day power chart now marks only connection losses that really happened and names the remote access connection that dropped. The record of remote access activity opens on the most recent weeks.

  • On a plant without remote access, the day power chart no longer marks the whole day as a lost connection.
  • Where a connection really dropped, the chart now names the remote access connections affected, or states that their state is unknown.
  • The record of remote access activity opens on the most recent weeks, and the weekday labels stay in place while scrolling.
mirox 2.14.55
Web appFeatureSolar equipment

The string list now flags only the strings that need review

The string list now flags only the strings that need review: ones where neither configuration nor measurement says what is installed, ones where measurement contradicts configuration, and ones found disconnected. "Review" shows configured and measured values side by side, and "Mark as reviewed" clears a flag until the next analysis finds it again.

mirox 2.14.49 – 2.14.54
Read more in the documentationComponents
Web appImprovements and fixesSolar equipment

Strings can now be added to many inverters or combiner boxes in one step instead of one device at a time.

  • Strings can be added to several inverters or combiner boxes in one step, with all of a plant's inverters selected at once.
  • Editing a single string now opens with that string's current values already filled in.
  • If the connection to a data logger drops during its setup, "Reconnect" resumes it and keeps the step, credentials and value mapping.
  • On plants without combiner boxes, adding a string no longer asks where to attach it.
mirox 2.14.49 – 2.14.54
Read more in the documentationComponentsData loggers
Web appFeatureSolar equipment

Inverters can be edited in bulk and a component's datasheet opened

On a plant's components page, several inverters — or all inverters of the plant — can now be selected to assign their model datasheet or show hidden ones in one step. Where a datasheet is attached, the model name in the inverter, string and battery tables opens it.

mirox 2.14.38 – 2.14.48
Web appSecurityUsers & access

File, accounting and AI access now follows the manager's role

Plant and organization storage now opens files of every category to technical and commercial managers, while accounting and contracts stay with commercial managers. Technical managers no longer reach the organization's AI overview or clearing its chat history, and members with view-only access no longer open a plant's files.

mirox 2.14.26 – 2.14.37
Web appFeatureNetwork & remote access

WireGuard remote access can now use a pre-shared key

A WireGuard remote-access server created on a plant now has "Require a pre-shared key" on by default, and the connected site receives an extra generated key alongside its keypair, shown once right after creation. For an existing connection, "Include a pre-shared key" adds, renews or removes the key when its configuration is regenerated.

mirox 2.14.26 – 2.14.37
Web appFeatureNetwork & remote access

Network scans now take a range and show devices as found

Starting a network scan on a plant's networking page now opens a dialog where "Scan range (optional)" limits the scan to part of the network and "Overwrite existing names" replaces device names with the latest analysis. Found devices appear in the table while the scan runs, filling in as they are identified.

mirox 2.14.26 – 2.14.37
Web appImprovements and fixesData collection

Agent-started wizard runs can be stopped, unresponsive runs end as failed after 30 minutes, and the agent configuration tab leaves the data-flow page.

  • A wizard run started by the on-site agent can be stopped by anyone who can see it.
  • A run that stops responding no longer sits on waiting and is marked failed after 30 minutes.
  • The plant's data-flow page no longer shows the agent configuration tab to organization admins and moderators.
mirox 2.14.26 – 2.14.37
Web appFeatureData collection

QReader data loggers can now be set up by mapping their values

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.

mirox 2.14.18 – 2.14.25
Read more in the documentationData loggers
Web appFeatureSolar equipment

Deep analysis shows its progress and can be aborted

A running deep analysis now shows each step, from production and weather data through strings, combiner boxes, inverters and feed-in meters, with the estimated time left. "Abort" stops it and keeps the results found so far, and at the start a "Clean re-analysis" can be chosen instead of the saved configuration.

mirox 2.14.18 – 2.14.25
Web appImprovements and fixesThe app itself

A network scan can now be limited to a subnet inside the plant's networks, and the monthly production chart keeps a slot for every day.

  • The monthly production chart now keeps a bar slot for every day of the selected range, leaving days without data empty.
  • A "Network scan" dialog now limits a scan to a subnet inside the plant's networks, and a device's type is picked from a fixed list.
  • A changed peak power, self-consumption, location or commissioning date now reaches a plant's on-site agent by itself, and the "Core Data" page shows the update.
  • The device search on a plant's "Networking" page now matches name, vendor, type, description, serial number, OS and MAC address as well as IP address.
  • The plant image is now shown in 4:3, and the upload dialog previews exactly how it will be cropped.
  • Adding an inverter or module type by hand no longer fails with an unexpected error.
mirox 2.14.18 – 2.14.25