MiroxMirox
  • Platform

    • Philosophy
    • Platform Overview
    • Platform Resources
  • Mirox-Cloud

    • Cloud Overview
    • Connected Microservices
  • Mirox-Agent

    • Agent Overview
    • Deployment Options
    • Data Scraper
    • Digital Twin
  • Technical Details

    • Metric Collection
  • Information

    • Supported Plants
  • Plant Types

    • Solar Plants
    • Wind Plants
    • Battery Storage
    • Alarm System
  • Monitoring & Visualization

    • Real-time Monitoring
    • Digital Twin
    • Component States
    • Inverter Status Codes
    • Inverter Events
    • Loss Detection
    • Power Limits & Curtailment
    • Efficiency Detection
    • KPI Dashboard
  • Data Management

    • Events
    • Tickets
    • Forecasts
    • Reports
    • Metrics
  • Integration & Sharing

    • Cooperations
    • API Tokens
    • VPN
    • VPN Address Conflicts
    • Proxy
  • AI

    • AI Assistant & Wizards
    • Agentic Access (MCP)
  • Billing

    • Market & Tariffs
    • Accounting & Billing
  • Collaboration

    • Invitations
  • Security

    • Authentication
    • Account Lockout
    • Permission System
    • Network Segmentation
    • Cooperation Restrictions
    • Access Audit Logging
    • Activity & Audit Trail
  • Nodes

    • mrxnode
  • Application

    • Door Control
    • Generic Relay
  • Edge Cluster

    • Orchestration
  • Getting Started

    • Onboarding
    • Setup
  • Personal

    • Using the VPN
    • Using the Proxy
    • Two-Factor Authentication
    • Sessions
    • API Tokens
    • Notifications
    • Connect Microsoft Teams
  • Per Park

    • Contacts
    • Network Devices
    • Data Loggers
    • Components
    • Direct VPN (per Agent)
    • Data Volume
    • History Import
  • Organization

    • Member Permissions
    • Cooperations
    • File Storage
    • VPN Services
    • Working with Reports
  • Data Export

    • Metric Export
    • Metric Export API
    • Migrating to the Metric Export
    • Legacy Export API
    • External Report Generation
    • Grafana
    • Grafana Dashboards
    • API Overview
    • MiroxQL Formulas (API)
  • Support

    • Request an Integration
  • mrxnode

    • Overview
    • How-To Guide
    • Container Deployment
    • Command Cheatsheet
    • Troubleshooting
  • Reporting

    • External Report Generator
    • Metric Export for Excel
  • Remote Access
  • AI in Mirox
  • History Import
  • Reports
  • Data Export
  • English
  • Deutsch
  • Español
  • Français
  • Português
  • Italiano
  • English
  • Platform

    • Philosophy
    • Platform Overview
    • Platform Resources
  • Mirox-Cloud

    • Cloud Overview
    • Connected Microservices
  • Mirox-Agent

    • Agent Overview
    • Deployment Options
    • Data Scraper
    • Digital Twin
  • Technical Details

    • Metric Collection
  • Information

    • Supported Plants
  • Plant Types

    • Solar Plants
    • Wind Plants
    • Battery Storage
    • Alarm System
  • Monitoring & Visualization

    • Real-time Monitoring
    • Digital Twin
    • Component States
    • Inverter Status Codes
    • Inverter Events
    • Loss Detection
    • Power Limits & Curtailment
    • Efficiency Detection
    • KPI Dashboard
  • Data Management

    • Events
    • Tickets
    • Forecasts
    • Reports
    • Metrics
  • Integration & Sharing

    • Cooperations
    • API Tokens
    • VPN
    • VPN Address Conflicts
    • Proxy
  • AI

    • AI Assistant & Wizards
    • Agentic Access (MCP)
  • Billing

    • Market & Tariffs
    • Accounting & Billing
  • Collaboration

    • Invitations
  • Security

    • Authentication
    • Account Lockout
    • Permission System
    • Network Segmentation
    • Cooperation Restrictions
    • Access Audit Logging
    • Activity & Audit Trail
  • Nodes

    • mrxnode
  • Application

    • Door Control
    • Generic Relay
  • Edge Cluster

    • Orchestration
  • Getting Started

    • Onboarding
    • Setup
  • Personal

    • Using the VPN
    • Using the Proxy
    • Two-Factor Authentication
    • Sessions
    • API Tokens
    • Notifications
    • Connect Microsoft Teams
  • Per Park

    • Contacts
    • Network Devices
    • Data Loggers
    • Components
    • Direct VPN (per Agent)
    • Data Volume
    • History Import
  • Organization

    • Member Permissions
    • Cooperations
    • File Storage
    • VPN Services
    • Working with Reports
  • Data Export

    • Metric Export
    • Metric Export API
    • Migrating to the Metric Export
    • Legacy Export API
    • External Report Generation
    • Grafana
    • Grafana Dashboards
    • API Overview
    • MiroxQL Formulas (API)
  • Support

    • Request an Integration
  • mrxnode

    • Overview
    • How-To Guide
    • Container Deployment
    • Command Cheatsheet
    • Troubleshooting
  • Reporting

    • External Report Generator
    • Metric Export for Excel
  • Remote Access
  • AI in Mirox
  • History Import
  • Reports
  • Data Export
  • English
  • Deutsch
  • Español
  • Français
  • Português
  • Italiano
  • English
  • FAQ

    • Remote Access — Frequently Asked Questions
    • AI in Mirox — Frequently Asked Questions
    • History Import — Frequently Asked Questions
    • Reports — Frequently Asked Questions
    • Data Export — Frequently Asked Questions

Data Export — Frequently Asked Questions

The questions people ask when they export data from Mirox. For how the export works, see Metric Export; for the parameters of the export links, see the Metric Export API.

1. Can I export my metrics as a time series?

Yes. The Data Export page and the reports read the same metric collection, which includes the metrics your organization defined under Metrics. Open Data Export, click Add metrics and choose them under My Metrics. A metric can be exported from its Finest resolution up to a year, but never finer than 15 minutes. A metric marked Not validated cannot be exported until its expression validates. See Exporting a metric.

2. Which data can I export?

Every metric of the collection: plant values such as feed-in, irradiation, availability, losses and curtailment, and the values of single inverters, combiner boxes, strings, wind turbines, sensors, meters and battery containers, racks, modules, cells and power converters, plus weather, market prices and money values. The picker on the Metrics tab lists them by level, and Explanations offers the whole list as a glossary file. See Available metrics.

3. Can I export each irradiance sensor on its own?

Yes. Add the metric Irradiance per sensor or Irradiation per sensor. Each sensor becomes a column of its own, without averaging. The system template Irradiance Sensors exports all sensors at 15 minutes over yesterday. See Choose components.

4. Why is per interval only offered for energy?

Per interval means the amount within each interval, and only a counted quantity has an amount. A power, a temperature or a ratio is a state at a moment: it is exported As measured, as the average or the last value of the interval. Other counted quantities, such as sun hours or precipitation, offer As measured and Running total. See Values.

5. Why do I get a warning at 1 or 5 minutes?

A meter counts energy in whole steps, often 1 kWh. Within a minute a plant seldom produces a whole step, so an energy per interval at 1 or 5 minutes jumps between zero and one step instead of drawing a curve. For a curve use the matching power metric; for energy use 15 minutes or longer. You can also keep the selection if the meter steps are what you want to see. See The warning below 15 minutes.

6. Why is power not offered per hour or per day?

Power is offered at 15 minutes or finer. An average power over a day hides what happened during the day and is rarely the figure that is meant. For hourly, daily or monthly figures use the energy metric, for example Grid feed-in instead of Grid feed-in power. See Steps and their limits.

7. Why is there a UTC offset column?

Rows follow the local time of the plant. On the day the clocks go back, the hour between 2 and 3 o'clock occurs twice. The UTC offset column tells the two apart and lets any program convert a row to UTC. It appears only at steps shorter than a day and can be switched off in the link with offset_column=false. See Plant local time and UTC.

8. Why is my export in UTC although I chose plant local time?

Because the selected plants lie in different time zones. One file has one time column, so such an export is always in UTC, and a note says so. Export the plants of each time zone separately to get local time.

9. Why is a cell empty instead of zero?

An empty cell means that there is no value for this interval. Zero means that the value was measured and is zero. The previous template export wrote 0 in both cases. If a program needs a number in every cell, add empty=zero to the link.

10. Do my old Excel links still work?

Yes. Every link of the previous exports keeps working and keeps delivering the same columns. They are marked legacy and have no removal date. Bookmarks of the previous Raw Data tab open the Metrics tab with the same selection. See the Legacy Export API and the migration guide.

11. What is a Legacy template?

A template that was created before the Metric Export. It is built on the previous metric set, and its link keeps working unchanged. Convert to new template creates a new template on the metric collection from it and leaves the legacy template as it is. New templates are always built on the metric collection. See Legacy templates and conversion.

12. Why do the numbers differ slightly from my previous export?

Mostly because a day is now the local day of the plant, where the previous export used UTC days. Energy is in kWh throughout, where the previous raw export used Wh. Some metrics are read in a better way than before, for example the battery state of charge weighted by the capacity of the containers. The migration guide marks these metrics as approximate and names the difference.

13. Why do columns of my previous export carry values that were empty before?

Two groups of columns of the previous raw data export were corrected: the availability columns (raw_availability_…) and the wind curtailment columns (raw_curtailment_…_nacelle, _windref and _windfixed). They were empty and carry values now. In an availability column, each row is the availability over a period as long as the exported range, ending at that row. See Corrections.

14. Why is my export refused as too large?

An export is answered within one request, so it is bounded: 50 plants, 20 metrics, 400 columns, 180 000 values per column and 1.8 million values in total. The message names a coarser step or a shorter range that fits. To get more, split the export by time, by plant or by metric. Metrics that Mirox works out from several sources, such as the resolved production, cost more than a plain meter reading. See When an export is too large.

15. Which API token do I need for Excel or a script?

A token of the group Metric Export. It reads every export link, the previous ones included, and cannot change anything. The group was called Reporting before; tokens of that group keep working. In Excel Power Query the token goes into the Authorization header, and the connection is set to Anonymous. See Excel with Power Query.

16. Where did the formula editor go?

The editor for MiroxQL formulas was retired from the app. Existing formulas keep being evaluated in legacy templates, and formulas can still be managed through the API. For a figure you define yourself, use Metrics on the Reports page: a metric works on the 15-minute values, appears in reports and can be exported. See MiroxQL Formulas.

17. What is the difference between Data Export and the Full data export of a report?

Full data export delivers the tables of one published report, exactly as the report froze them. Data Export delivers any metric as a time series for any plants and any time range, read at the moment you ask, and also as a link for Excel or a script. Both read the same metric collection. See Downloads.

18. Who can export data?

Everyone who may read the measurements of a plant: the job roles Operator, Technical Manager, Asset Manager and Viewer. Money values additionally need the accounting permission, which Operator and Asset Manager have. Templates are created, changed and deleted by the organization role Admin; everyone in the organization can use them. See Who can export what.

19. Can I export a raw MetricsQL query?

Yes. On the Metrics tab, MetricsQL under the metrics opens a query field: Enter runs the query, Tab takes what the field proposes. Mirox adds the plant to every selector, so the query never names a plant or an organization. Every series the query answers becomes a column headed MetricsQL and the query, and the link carries it as expr. One export holds up to 5 queries with at most 500 series per plant; queries are not saved in templates. See MetricsQL queries.

20. Why does a column have values only on some rows?

Because the metric has a coarser step than the file, for example a daily performance ratio in a 15-minute file. Its value stands on the first row of each of its intervals, the rows between stay empty, and the chart draws it as points. The orange note above the preview names these metrics and offers Export separately, one link per step. A link written by hand gets the same with mismatch=sparse. See Metrics with different steps.

21. Why does the chart show a coarser resolution than I chose?

A long range at a fine step has more points than a browser can draw. The chart then shows a coarser step, or combines several rows into one point, and says so in an orange note. Only the chart changes: the table, the download and the link keep the step you chose. See Check the preview and download.

Prev
Reports — Frequently Asked Questions
© 2026 Mirox Verwaltungs GmbH. All rights reserved. | Privacy Policy