Weather station data from your own field: raw readings, hourly and daily series

Raw uplinks about every 10 minutes plus hourly and daily roll-ups, 33 fields across 3 datasets: temperature, humidity, pressure, light, rainfall, wind, position, battery and radio telemetry.

Catalogue entries: Weather station readings, Hourly weather roll-up, Daily weather roll-up.

Questions this data answers

  • How cold did it get on this field last night, against the last 30 nights, for frost damage claims and variety choice?
  • How much rain fell on this field this week, day by day, rather than at the nearest airport?
  • What did the station read in the last hour: temperature, humidity, pressure, light, rain, battery?
  • Is the battery trending down over the month, and will the station go quiet before the panel is checked?
  • When did the station last report, and where are the gaps in the radio link?
  • What was the daily mean temperature and humidity through August on this field, for the agronomy report?

3 views of 1 station

A station reports about every 10 minutes, and the platform keeps 3 separate views of those same readings. The raw series is every uplink exactly as sent: temperature, humidity, pressure, light and its peak, rainfall at 0.2 mm resolution, wind speed, gusts and direction wherever an anemometer is fitted, position when the receiver has a fix, battery voltage and percent, and radio telemetry. The hourly view takes the mean of each hour with rainfall summed instead. The daily view takes the mean of each day plus the battery fields, the series behind a month or a season, 1 row per day. A chart over a week should read the hourly view; a chart over a season, the daily view; a question about a single reading goes straight back to the raw series.

Reading the weather station data samples

The 10 raw uplinks shown here come from the potato station at Naivasha, about 2,490 m above sea level, which is exactly why the barometer reads 760 hPa. The 24-hour chart runs temperature from 10 °C before dawn to 24 °C in the early afternoon and humidity from above 90 % down to near 40 % across those same hours, precisely the pair the derived variables turn into dew point and vapour-pressure deficit. The 30-day chart shows highland nights near 8 to 10 °C against days near 23 to 25 °C, a 14-degree swing every single day, with no rain across the whole window.

Gaps in the weather station data

A gap in the series is either a gap in the radio link or a station that simply lost power. An hourly mean gets computed from whatever packets arrived, the risk models count the missing hours against their own data completeness, and the alert rules find nothing at all in a silent window rather than guessing. A station uploading in bursts on a marginal link can read as offline on a short check and complete on a longer one, so the window matters.

Reading the station battery

The daily view keeps battery specifically because it’s the field that predicts an outage before it happens. A station on solar reads 100 % through a sunny day and drops steadily through a cloudy week, and the daily mean makes that trend visible. A mean sliding under 80 % is the actual signal to check the panel, before the station goes quiet on its own.

Access to the weather station data

Served only to keys on the account that owns the station, and only for stations approved for exposure. A new station always arrives as pending and only answers over the API once approved. On an account running several stations, gateway_id picks one directly; leave it out and the primary station answers instead.

Weather station readings

Raw ~10-minute uplinks from the gateway weather station. Firmware-calibrated; the MQTT bridge is pass-through.

The last 10 uplinks, the potato station at Naivasha, 2,490 m

Time UTC°CRH %hPaluxlux maxrain mmbattery %VLoRa rx
09:0722.648.5761.2752021220010014.57489
09:1722.750.2761.2756221188010014.52493
09:2722.749.1760.869228907010014.55495
09:3823.156.1760.81440118887010014.56498
09:4821.259.9760.9748710706010014.54503
09:5819.567.7760.923353800010014.23505
10:0816.990.2760.920292439010014.14507
10:18—————————
10:28—————————

Pressure near 760 hPa is the station altitude, about 2,490 m. lora_rx_count is link telemetry. Wind fields are absent on this station; stations with an anemometer report them.

Dataset idfarm.weather.raw
Cadence~10 min
EndpointGET /farm/weather
Key scopefarm:read
Declared fields20
History2026-03 to today
Coverageyour own stations
StatusOwn sensors, own account

Narrowed to your own gateways and to devices approved for API exposure.

Only for the account that owns the hardware. Readings and everything computed from them are served to keys on the owning account and to nobody else. The way to get this dataset is a station on your own field, or your own sensors sent in through Sensor Ingest. A NuaSense station on the field is what produces these rows; the hardware is described at nuasense.com/products.

Fields

FieldUnitNote
temperature°Cair temperature
humidity%
pressurehPa
lightlux
light_maxlux
rainfallmm
wind_speedm/s
wind_gustsm/s
wind_direction°
gps_lat°only when gps_fix=true
gps_lon°only when gps_fix=true
gps_altmonly when gps_fix=true
battery_voltageV
battery_percent%
lora_rx_count—link telemetry
fw_version—link telemetry
rain_clickscountfw19 raw — ×0.2691 = rainfall mm
wind_clickscountfw19 raw
wind_hz_avgHzfw19 raw — ×0.667 = wind_speed m/s
wind_hz_peakHzfw19 raw — peak, feeds wind_gusts

Filters

gateway_id

The same call, three ways

curl -G https://api.nuasense.com/api/nuasense/v1/farm/weather \
  -H "Authorization: Bearer nua_live_…" \
  -d start=-30d -d start=-24h -d fields=temperature,humidity,rainfall

Through the MCP connector the same read is the platform_dataset tool with dataset=farm.weather.raw. Through a scheduled export it is one job with the same filters, delivered as a file. Every dataset takes the same arguments: start and end, every with agg, fields, limit up to 5,000, order, and the tags it declares.

Hourly weather roll-up

Hourly means of the gateway weather station's own readings — temperature, humidity, pressure, rainfall, wind speed and gusts, and light — rolled up server-side from the raw uplinks.

24 hours, hourly means, the potato station at Naivasha, 2,490 m

Temperature and humidity move against each other through the day: humidity above 90 % before dawn, near 40 % in the afternoon. The derived variables page turns this pair into dew point and vapour-pressure deficit.
Hour UTC°CRH %hPaluxbattery %
11:0023.551.3760.812727—
12:0016.287.6760.32070—
13:001792.8759.84934—
14:0019.779.4759.85057—
15:0017.194.1760.12391—
16:0015.3100760.686—
17:0014.5100760.80—
18:0014.6100761.40—
19:0014.3100761.80—
20:0014100761.90—
21:0013.7100761.90—
22:0012.8100761.80—
23:0012.7100761.20—
00:0012.2100760.80—
01:0011.4100760.80—
02:0011100760.50—
03:0010.8100760.80—
04:0010.4100761.4206—
05:0012.4100762.11277—
06:0014.694.6762.52093—
07:0017.674.5762.72152—
08:0020.368.7762.211773—
09:0023.554.1761.727662—
10:0022.8517619101—

Hourly rows are means of the ~6 uplinks inside each hour, computed server-side. Rainfall in the hourly roll-up is the hour's sum.

Dataset idfarm.weather.hourly
Cadencehourly
EndpointGET /farm/weather/hourly
Key scopefarm:read
Declared fields7
History2026-03 to today
Coverageyour own stations
StatusOwn sensors, own account

Narrowed to your own gateways and to devices approved for API exposure.

Only for the account that owns the hardware. Readings and everything computed from them are served to keys on the owning account and to nobody else. The way to get this dataset is a station on your own field, or your own sensors sent in through Sensor Ingest. A NuaSense station on the field is what produces these rows; the hardware is described at nuasense.com/products.

Fields

FieldUnitNote
temperature°C
humidity%
pressurehPa
rainfallmm
wind_speedm/s
wind_gustsm/s
lightlux

Filters

gateway_id

The same call, three ways

curl -G https://api.nuasense.com/api/nuasense/v1/farm/weather/hourly \
  -H "Authorization: Bearer nua_live_…" \
  -d start=-30d -d start=-24h -d fields=temperature,humidity,rainfall

Through the MCP connector the same read is the platform_dataset tool with dataset=farm.weather.hourly. Through a scheduled export it is one job with the same filters, delivered as a file. Every dataset takes the same arguments: start and end, every with agg, fields, limit up to 5,000, order, and the tags it declares.

Daily weather roll-up

Daily means of the gateway weather station's own readings — temperature, humidity, pressure, light and the battery state of the station — rolled up server-side from the raw uplinks.

30 days of daily extremes and rain, the potato station at Naivasha, 2,490 m

Highland nights: minimum near 8 to 10 °C, maximum near 23 to 25 °C, a 14-degree daily swing. The frost advisory reads the forecast minimum against this history.
Rain totals from the tipping bucket. A dry August into September; the water balance below stays on stored soil water and irrigation.
DayMean °CRH %hPaluxBattery %
10-1015.787.8761369499.2
10-1115.191.1760.4576598.4
10-1215.283.6760.4567599
10-1315.274.9761.2516998.9
10-1415.758.5761.2610998.2
10-1515.882.7760.5377199.1
10-1615.189.6760.2529198.4
10-1715.290.4760.3350399.2
10-1815.490.5760.9354998.9
10-1915.391.7761.3261998.9

Last 10 daily rows. The daily roll-up carries means; extremes and sums are read from the raw series with every=1d and agg=min, max or sum.

Dataset idfarm.weather.daily
Cadencedaily
EndpointGET /farm/weather/daily
Key scopefarm:read
Declared fields6
History2026-03 to today
Coverageyour own stations
StatusOwn sensors, own account

Narrowed to your own gateways and to devices approved for API exposure.

Only for the account that owns the hardware. Readings and everything computed from them are served to keys on the owning account and to nobody else. The way to get this dataset is a station on your own field, or your own sensors sent in through Sensor Ingest. A NuaSense station on the field is what produces these rows; the hardware is described at nuasense.com/products.

Fields

FieldUnitNote
temperature°C
humidity%
pressurehPa
lightlux
battery_voltageV
battery_percent%

Filters

gateway_id

The same call, three ways

curl -G https://api.nuasense.com/api/nuasense/v1/farm/weather/daily \
  -H "Authorization: Bearer nua_live_…" \
  -d start=-30d -d start=-24h -d fields=temperature,humidity,rainfall

Through the MCP connector the same read is the platform_dataset tool with dataset=farm.weather.daily. Through a scheduled export it is one job with the same filters, delivered as a file. Every dataset takes the same arguments: start and end, every with agg, fields, limit up to 5,000, order, and the tags it declares.