Mischpreis can no longer be chosen under a contract's "Revenue model". A contract still set to it is valued at "Marktwert (as-if-produced)", and compensation for curtailment ordered by the marketer follows that model from this release, while figures already issued keep their value.
Action required: Plant and portfolio managers: open the market configuration of every plant whose direct-marketing contract was settled on the Mischpreis model, and confirm that "Marktwert (as-if-produced)" or "Fixed value" is the right revenue model for that contract. Marketer-curtailment compensation is calculated on the chosen model from this release; support helps you with an affected contract.
mirox 2.15.310 – 2.15.329
Web appBreaking changeMajorNetwork & remote access
The "VPN auto-heal" wizard can no longer be started, while a run started earlier still opens. A plant's VPN connection is now diagnosed from "Inspect VPN connection" on the plant, where "Start AI diagnosis" takes the router on site and what is needed and lets the assistant read the configuration and the logs itself.
Action required: Anyone who used the "VPN auto-heal" wizard: start the diagnosis from the plant instead. Open the plant's networking page, choose "Inspect VPN connection" on the VPN, go to its diagnosis step, name the router on site and what you need, and carry on with the assistant in the tab it opens. Starting a new auto-heal run is refused from this release; runs you started before it stay readable.
mirox 2.15.253 – 2.15.260
Web appBreaking changeMajorReports, exports & files
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.
A plant's revenue page and its contracts are no longer open to technical managers and members, while organization admins, moderators and commercial managers keep them together with every change to tariffs, EEG values and PPA terms. A plant's "Market" settings stay readable for everyone, and figures already issued keep their value.
Action required: Organization admins: go through who needs revenue on each plant. A technical manager or a member who used to open a plant's revenue page, or edit its tariff, EEG or PPA terms, can no longer do so — give that person the commercial manager role on the plant if they still need it. Admins and moderators of the owning organization keep both.
For organization admins and moderators, notices about production faults, the availability of data sources and sensor defects no longer arrive unless the topic is switched on under "What Notifies Me" in the profile's "Notifications" tab. Technical managers keep them, and a choice already made for these topics stands.
Action required: Organization admins and moderators: open your profile's "Notifications" tab and, under "What Notifies Me", switch on every topic you still want to hear about — production faults, the availability of your data sources and sensor defects are no longer selected for you. If you had already chosen these topics yourself, your choice stands and there is nothing to do.
A negative-price rule set on a PPA contract is no longer read. "Negative-price rule (§51)" is now set on each EEG value in a plant's core data, under "Market", and until it is set a plant's grid-curtailment compensation is shown without the suspension.
Action required: Asset and portfolio managers: open each plant's core data, go to "Market" and set "Negative-price rule (§51)" on every EEG value that needs one. The threshold that used to sit on the PPA contract is ignored from this release, and until you set the rule again that plant's compensation figures are shown unmasked. While you are there, check every direct-marketing contract: one settled at a fixed value now needs its "Settlement price (€/MWh)".
In the profile's "Notifications" tab, every topic now has its own choice of app, email or both, and the single switch that kept all email off is gone. "Working hours" now holds back emails only, while app notifications arrive at once.
Action required: All members: open your profile's "Notifications" tab and go through the topics. Email is now chosen per topic, so the one switch that used to keep every email away no longer holds — switch email off on the topics you do not want in your inbox. And make sure every topic you want to see in your bell has the app or email selected: a topic with neither selected reaches you nowhere.
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.
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 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.
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.
A plant's devices can now be reached through a personal VPN only with "Operator" on that plant, or as an admin or moderator of the organization that owns it. With "Technical Manager" or below, access to that plant's devices is lost.
Action required: Organization admins: give any member who must reach a plant's networks over the VPN the "Operator" job on that plant, and any member who must open a device's web page at least "Technical Manager". Ask them to download their VPN connection file again once you have changed it.