All topics
On this page

The file comes from the history of the gateway. The history keeps at most one reading per register per minute, even if the gateway reads every second. Anyone who can open the gateway can download, including a team member with read-only access.

Download the file

Loading the walkthrough.

  1. Open the gateway list

    Open Gateways in the menu.

  2. Open the gateway

    Click the gateway whose readings you want.

  3. Open the menu

    Open the menu with the three dots at the top right of the gateway page.

  4. Open the download window

    Choose Download readings. The Download readings window opens.

  5. Choose the period

    In Period, choose how far back you want to go. The choices are Last 7 days, Last 30 days, Last 12 months and Everything. The default is Last 30 days.

  6. Choose the detail

    In Detail, choose how fine the file is. Every reading gives all stored readings. Per 15 minutes, Per hour and Per day summarise the readings per register. The default is Every reading.

  7. Choose the file format

    In File format, choose between CSV for Excel and JSON. The default is CSV for Excel.

  8. Save the file

    Click Download. When the file is ready, the browser saves it and the window closes.

On a phone or in a narrow browser window, the gateway page has no menu with three dots. The download icon (Download readings) in the bar at the top opens the same window there.

Everything includes all stored readings. How long readings are kept is described in Retention periods and exporting your data.

What the file contains

The file name starts with the name of the gateway, or with the serial number if the gateway has no name of its own. Times in a CSV file are in the timezone of your organisation. That is the Timezone under Settings > Organization, by default Europe/Amsterdam (CET/CEST), see Set up your organisation and profile. The timezone in your profile does not count.

Values are included with the scale already applied, as in the portal. A register that reads 2314 with scale 0.1 appears as 231.4. The file uses the scale that is currently set on the register, also for older readings. A status register appears as a number, not as the text the portal shows next to it. Values from the Variables tab are not in the file.

Every reading as CSV

The first column gives the date and time as YYYY-MM-DD HH:MM:SS. After that, each register gets its own column, in order of register address. The header is the name of the register with the unit, for example Voltage L1 (V). The name of the Modbus device is not part of it.

If two Modbus devices of the same type are connected to the gateway, their columns get the same headers. To tell them apart, give the registers of one of them another name, as described in Set up registers. A file per 15 minutes, hour or day does have a column with the name of the Modbus device.

Registers that were read at the same moment share a row. An empty cell means the register has no reading at that time.

Per 15 minutes, hour or day as CSV

The file then has one row per bucket per register. A bucket is a quarter of an hour, an hour or a day. The rows are in order of time and, within a bucket, of register address. The headers are in the language of the portal.

ColumnContents
Start, EndStart and end of the bucket, in the timezone of your organisation
Modbus device, Register, UnitName of the Modbus device, name of the register and the unit
CountNumber of readings in the bucket
Average, Minimum, MaximumOver the readings in the bucket
First, LastFirst and last reading in the bucket
ConsumptionCounters only, the consumption in the bucket
Counter resetyes when the counter dropped in the bucket. Consumption is then empty
Register IDThe id of the register

A counter is a register with the kind Counter, such as a kWh meter reading. The kind is in the Kind column, see Automatic monitoring. The consumption is the last value of the bucket minus the last value of the previous bucket with readings. For the first bucket the last value from the 7 days before counts.

Buckets of 15 minutes and an hour follow the clock. A day runs from midnight to midnight in the timezone of your organisation. The first bucket is always whole, even if the period starts in the middle of it. The last bucket can still be running, such as today with Per day.

JSON

JSON follows the format modbuscloud.readings, version 1. At the top are the details of the export, such as gateway, timezone, resolution, from and to. Then comes registers, with for each register among others id, name, unit, modbus_device, address, scale_factor and counter. Then come the values.

DetailListFields per item
Every readingreadingsts, register_id, value
Per 15 minutes, Per hour, Per daybucketsstart, end, register_id, count, avg, min, max, first, last, delta, delta_reset

Times in JSON are UTC in ISO 8601. register_id refers to id in registers. Values are already converted with the scale, which is why values_scaled is true. delta is the consumption in the bucket and delta_reset is true when the counter dropped, like Consumption and Counter reset in the CSV. For a register that is not a counter, both are null.

Format for Excel

The format of a CSV file follows the language in which you use the portal. The table shows how the file is formatted for each language. JSON is the same in every language.

Portal languageSeparatorDecimal markTime column with Every reading
Nederlands;,Tijdstip
Deutsch;,Zeitpunkt
English,.Time

Excel recognises the file as UTF-8, so characters such as °C and ü display correctly.

Too many readings for one file

A file holds at most 500 000 readings, as CSV and as JSON. A reading is one value of one register. With 20 registers and a polling interval of 300 seconds, you reach that limit after about 87 days. With an interval of 60 seconds or shorter, it is after about 17 days.

If the period holds more, you get the newest readings. The browser still saves the file. The window stays open with the message Too many readings for one file: it holds the latest 500,000. Choose a shorter period for everything.

The first line of such a CSV file states the time from which it is complete. The headers are then on the second line. In JSON, truncated is then true and complete_from gives that time. To get a period in full, choose a shorter period. If even Last 7 days does not fit, or if you want the readings from before that time, use the REST API.

Per 15 minutes, hour or day, the limit applies to the readings the portal reads to calculate the buckets. Per 15 minutes reads all readings in the period, so you reach the limit as quickly as with Every reading. Per hour and Per day use the hourly values the portal has kept since 19 August 2026, without a limit. Only for the time before that does the portal read individual readings, and there the limit does count.

If the portal reads more readings than the limit, the file starts at the first bucket that is complete. The window stays open with the message Too many readings to summarise in one go. The file therefore starts later than requested. Choose a shorter period for everything. The first line of the CSV and complete_from in JSON give the start of that bucket.

Get readings in another way

The table compares the three ways.

WhatDownload readingsCSV on TrendsREST API
RegistersAll registers of the gatewayThe registers in the chartAll registers or a selection
PeriodLast 7 days, Last 30 days, Last 12 months or Everything1h, 6h, 24h, 7d or 30dStart and end of your choice, at most 7 days per request (366 days for a single register)
DetailEvery reading, Per 15 minutes, Per hour or Per dayIndividual readings at 1h and 6h, averages after thatEvery stored reading
FormatCSV for Excel in the language of the portal, or JSONCSV with commas and a decimal pointPages of at most 1000 readings

How the CSV button works is described in View values and charts. For the API you need an API key, as described in REST API and webhooks.

As an owner or administrator you can also export all gateways at once, with the settings, under Settings > Data export. This is described in Exporting your entire account, together with the full structure of the CSV and JSON files.

Updated on 15 October 2026

Still stuck?

Email or call us. Include the serial number of the gateway, so we can take a look straight away.

Go to support