Measurement Data
On the Measurement Data page you can view your readings as a table and download them as a CSV file. You can also see how reliable your data is.
Measurement data table
The table shows your readings with Meter, Timestamp, Measurement (OBIS code), Value (kWh), and Data Quality. The most recent values appear first by default. The filters above let you narrow down by location, meter, measurement, and data quality.
CSV and XLSX export
Click Export above the measurement data table to download the measurement data for the selected period. The file follows your table filters, so filter by Measurement to export only grid consumption, for example. In the dialog you choose the layout, the resolution and the file format (CSV or XLSX). The timestamp format and timezone, the sort order and, for CSV, the separators are under Advanced. The defaults are timestamps in the Austrian format DD.MM.YYYY HH:mm:ss in Europe/Vienna time, oldest value first, and labels in the language you use the app in. On the night the clocks go back in autumn, the hour 02:00 to 02:59 then appears twice; if every timestamp must be unique, choose ISO 8601 with timezone or the UTC timezone. If you take part in an energy community, Export opens a menu: Standard gives the values per meter, With EC column adds the values per energy community. With the default semicolon delimiter, the CSV file opens directly in Excel, Google Sheets, or your energy management system. Every CSV file starts with a UTF-8 byte order mark (BOM), so Excel shows umlauts correctly. XLSX files show kWh values with three decimals.
If the export covers several meters, you get a ZIP file with one file per meter, named after the metering point number and the meter's label. An export of more than 100,000 rows, such as two years of quarter-hour values for several meters, is prepared in the background. Once the file is ready, you get an email and a notification (bell icon), each with a Download button and the date until which you can download the file. If the export fails, you also get an email and a notification.
File layout
Layout sets how the file's columns are arranged. Scheduled exports offer the same choice under Attachment format. The export dialog defaults to Detailed, scheduled exports to For import.
Detailed writes one row per reading, with meter, location, OBIS code, quality and granularity:
smart_meter;metering_point_number;location;timestamp;obis_code;value;data_quality;granularity;measurement_label;quality_label
"Heat pump";AT0010000000000000000000000123456;"Main Street 1";"15.01.2026 09:00:00";"1-1:1.9.0 P.01";1,250;1;QH;"Grid consumption";Measured
For import also writes one row per reading, in fixed columns with the interval's start and end, the unit and your internal reference, for reading into another system:
metering_point_number;internal_reference;timestamp;timestamp_end;value;unit;obis_code;obis_description;quality
AT0010000000000000000000000123456;K-4711;"15.01.2026 09:00:00";"15.01.2026 09:15:00";1,250;kWh;"1-1:1.9.0 P.01";"Grid consumption";1
Compact writes one row per timestamp, with a value and a quality column for each measurement. The columns follow your Measurement selection (Measurements in scheduled exports) and always appear in the same order, so the files of several meters line up. Every interval in the period gets a row, which for quarter-hour values means every quarter hour. Where a reading is missing, the cells stay empty; they are never filled with 0:
timestamp;consumption_kwh;consumption_quality;feed_in_kwh;feed_in_quality
"2026-01-15 09:00:00";1,250;1;2,000;1
"2026-01-15 09:15:00";;;;
"2026-01-15 09:30:00";0,500;2;;
When a scheduled export combines all meters into one file, Compact puts the metering point number in the first column and sorts the rows by timestamp, then by meter. The With EC column export is only available in the Detailed layout. If a meter delivered only hourly or daily values for an earlier period, those rows stay empty in a finer grid, because such a value fits no single row. We tell you how many readings Compact left out this way: in the notice after the download, in the notification for an export prepared in the background, and in a scheduled export's email. For such periods, choose the Day or Month resolution, or one of the other two layouts. If your filters match no readings at all, the download shows the notice "No readings for these filters" in every layout and creates no file.
Resolution
Resolution decides whether values are exported as measured or summed per hour, day or month. Days and months follow Austrian time, also with timestamps in UTC. For electricity a day starts at midnight, which in UTC is 23:00 on the day before, or 22:00 in summer. Gas is counted in gas days, as on the Gas page: the row for 1 November starts at 06:00 and covers the gas used until 06:00 on 2 November, and a gas month runs from 06:00 on the 1st to 06:00 on the next 1st. A gas export as measured also starts at 06:00 on the first day, so its hours, days and months add up to the same total as the Gas page.
Each sum carries the worst quality level of its values: if a day contains a reliable substitute value, the day shows 2. An extra complete column (<measurement>_complete in Compact) shows 1 when every interval of the period was delivered and 0 otherwise. It counts by the period's real length: the day the clocks go forward in March has 92 quarter hours, the day they go back in October has 100, and a gas day on those weekends has 23 or 25 hours. Missing values make a sum smaller than the real consumption, so check complete before you calculate with a sum. A period with no values at all gets no row in Detailed and For import, and an empty row in Compact.
Meters that already report at the chosen resolution or coarser, such as daily values with an hourly resolution, and meters with irregular intervals are exported as measured. The export dialog therefore only offers resolutions coarser than the finest selected meter. In Detailed the granularity column names the chosen resolution (H, D or M). Whether an export downloads directly or is prepared in the background depends on the number of summed rows.
Data quality
The data-quality chart shows a donut chart of what share of your readings falls into each quality level:

- Measured (L1, green): Actually measured values. This is the normal case. Aim for a share above 95%.
- Reliable substitute value (L2, light green): Substitute values from the grid operator because the measured value could not be transmitted. They are suitable for billing. Individual substitute values are normal and have little effect on the analysis.
- Unreliable substitute value (L3, red): Preliminary values with limited reliability, not suitable for billing. They are replaced by the grid operator with measured values or reliable substitute values within 60 days.
If your share of measured values is consistently below 95%, this may indicate a communication problem with the smart meter. In that case, contact your grid operator.
For experts
The quality levels (L1, L2, L3) follow the OBIS code conventions of the Austrian energy market. The exchange period for L3 values is 16 calendar days for energy communities and 60 days for general data exchange. L3 values must not be used for energy billing. After this period the grid operator replaces L3 values with measured or best-estimated values.
What do the OBIS codes mean?
The Measurement column shows what was measured: for most meters Grid consumption (1-1:1.9.0 P.01) or Grid feed-in (1-1:2.9.0 P.01). Which other codes exist, which one your analyses use, and why G.01 and P.01 must not be added together is explained in Understanding OBIS codes.