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.
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
°C
RH %
hPa
lux
lux max
rain mm
battery %
V
LoRa rx
09:07
22.6
48.5
761.2
7520
21220
0
100
14.57
489
09:17
22.7
50.2
761.2
7562
21188
0
100
14.52
493
09:27
22.7
49.1
760.8
6922
8907
0
100
14.55
495
09:38
23.1
56.1
760.8
14401
18887
0
100
14.56
498
09:48
21.2
59.9
760.9
7487
10706
0
100
14.54
503
09:58
19.5
67.7
760.9
2335
3800
0
100
14.23
505
10:08
16.9
90.2
760.9
2029
2439
0
100
14.14
507
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.
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
temperaturehumidity ÷ 4°C (humidity ÷ 4 in grey)
26.817.78.6
11:0014:0017:0020:0023:0002:0005:0010:00
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
°C
RH %
hPa
lux
battery %
11:00
23.5
51.3
760.8
12727
—
12:00
16.2
87.6
760.3
2070
—
13:00
17
92.8
759.8
4934
—
14:00
19.7
79.4
759.8
5057
—
15:00
17.1
94.1
760.1
2391
—
16:00
15.3
100
760.6
86
—
17:00
14.5
100
760.8
0
—
18:00
14.6
100
761.4
0
—
19:00
14.3
100
761.8
0
—
20:00
14
100
761.9
0
—
21:00
13.7
100
761.9
0
—
22:00
12.8
100
761.8
0
—
23:00
12.7
100
761.2
0
—
00:00
12.2
100
760.8
0
—
01:00
11.4
100
760.8
0
—
02:00
11
100
760.5
0
—
03:00
10.8
100
760.8
0
—
04:00
10.4
100
761.4
206
—
05:00
12.4
100
762.1
1277
—
06:00
14.6
94.6
762.5
2093
—
07:00
17.6
74.5
762.7
2152
—
08:00
20.3
68.7
762.2
11773
—
09:00
23.5
54.1
761.7
27662
—
10:00
22.8
51
761
9101
—
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.
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
daily maxdaily min°C
30.316.83.4
09-1909-2309-2710-0110-0510-0910-1310-19
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.
mm per day
000
09-1909-2309-2710-0110-0510-0910-1310-19
Rain totals from the tipping bucket. A dry August into September; the water balance below stays on stored soil water and irrigation.
Day
Mean °C
RH %
hPa
lux
Battery %
10-10
15.7
87.8
761
3694
99.2
10-11
15.1
91.1
760.4
5765
98.4
10-12
15.2
83.6
760.4
5675
99
10-13
15.2
74.9
761.2
5169
98.9
10-14
15.7
58.5
761.2
6109
98.2
10-15
15.8
82.7
760.5
3771
99.1
10-16
15.1
89.6
760.2
5291
98.4
10-17
15.2
90.4
760.3
3503
99.2
10-18
15.4
90.5
760.9
3549
98.9
10-19
15.3
91.7
761.3
2619
98.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.
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.
Related datasets
Also in Weather data
Spray window, leaf wetness and degree-day data, hourly29 variables computed every hour from the station's own readings: dew point, vapour-pressure deficit, evapotranspiration, delta-T, spray quality with its limiting factor, inversion risk, leaf wetness and degree-days for the crop and 9 pests. Every field carries a calibration tier.
Disease and pest risk data for potato, onion and coffeeRisk per threat for the station's crop, every hour: percent, level, threat score, accumulated disease severity, the conducive hours behind the score and how much input data backed it. 22 models across potato, onion and coffee.
Read together with this page
Daily climate history since 1940 for your farm locationDaily climate for each station's location reaching back decades: temperature, rainfall, wind, radiation and reference evapotranspiration, backfilled once per location and topped up weekly. 7 fields.
Alert and advisory history for your farmThe append-only record of threshold alerts sent and of advisories generated, sent or held, with metric, rule, channel, delivery status, validity window and suppression reason. 28 fields across 2 datasets.