A Tempest weather station outside our house has reported to Home Assistant for months. Last week it got a website from WeeWX’s stock template. Every reading sat in gauges, tables, and monthly summaries, and none of it answered what we actually ask. What’s it like out there right now?
So this weekend we built a replacement and called it Field Guide. It’s only reachable from our home network or Tailscale, so I can’t link to it, but these screenshots come close.

These day and night captures were taken about an hour apart, which is why the numbers differ. Drag the divider to move between them.
Why bother
Forecasts describe a region. The station describes our yard, and the two don’t always agree.
The first screen gives you the temperature, a sentence about how it feels, and the day’s high and low, which is enough to decide on a coat. This morning the low was -0.6 °C at 7:50, and the dewpoint sat right on top of the temperature for most of the night. That means frost on the car, and it’s nicer to know before you go outside.
In summer, the line we’ll read most is the lightning note. East of the Cascades, a dry thunderstorm can start a wildfire, so “Quiet skies.” is the sentence we want to see.
Celsius and millimeters are the default, and Fahrenheit and inches are one tap away. The page remembers which you picked, so nobody in the house has to convert anything in their head.
The first screen
I wanted the temperature big enough to read from across the room, with something nice to look at beside it. That’s the Stuart Range on the right. Its ridgeline comes from USGS elevation data, so the shape of the mountains is real; the snow, trees, and sky are illustrated. Day and night moods switch at sunset, which the page works out from the almanac rather than a clock. There’s a button for switching by hand.
Headlines are set in Fraunces, a soft serif that suits a notebook. Body text is Manrope, and small labels and figures use IBM Plex Mono.
Under the first screen are four plates, numbered I to IV like the color plates in a field guide. Each one has a small label (“The moving air,” “Every little drop,” “Above the treetops,” and “The weight of the sky”), a headline, and one big number. More detail sits behind a disclosure, written as full sentences like “The moon is in its first quarter phase and 44% illuminated.”
All four plates, opened. From here on, the screenshots follow this site’s theme. Press d to see the other mood.
Live wind
Only the wind plate moves. Every three seconds the hub reports the wind, and a live needle follows it around the compass rose. Underneath is a trace of the last ten minutes with the peak marked.
If the readings stop, the needle comes to rest and the number falls back to the five-minute average. With reduced motion turned on, nothing animates. Other headline numbers update every five minutes, and the page checks for them every minute so an open tab stays current all day.
The rose’s petals show where the wind has come from over the last 24 hours.
It doesn’t make things up
Field Guide never fills a gap. Zero means a measured zero, and a missing reading shows as a dash. Chart lines stop where data is missing and start again after it. Sunrise and sunset in the sky chapter carry the label “calculated crossings, not a forecast,” and the lightning note won’t call the sky quiet unless the sensor is reporting.
Pressure needed the most care. We noticed the station’s pressure readings weren’t adding up, and we’re working through that with Tempest. On Sunday afternoon we also corrected the station’s altitude, which the software uses to turn measured pressure into a sea-level reading. That made the line on the chart jump by more than an inch of mercury in one step. Our first version called that “Rising.” Now the chart marks the jump as a calibration, pressure records start again after it, and the plate says “Record stepped: calibration, not weather.”
When we measured it on Sunday, November 15, about one in five of the station’s minute reports never reached the house. A warning about that every morning would teach us to ignore warnings, so the page stays quiet at normal levels. It speaks up after fifteen minutes without a reading, when a day’s coverage falls below 60%, or when a sensor reports a fault.
Four charts plot the last 24 hours in fifteen-minute means.
The notebook and the sky
The station notebook keeps the extremes and the date each one happened: the warmest moment, the coldest, the strongest gust, and the rain so far. Under the rain total it says, “This is the observed total, without filling gaps.”
A single line in the sky chapter draws the day from sunrise through solar noon to sunset, with golden hour shaded at each end, beside a short note about the moon.
Station records sit above the daylight timeline and the moon note.
Plain sentences
Early versions read like a status screen, full of “Disabled,” “No cloud contact yet,” and counters without context. We rewrote every reading as a sentence with the number inside it.
At the bottom, the Instrument chapter covers the station itself, in sentences like “The battery sits at 2.80 volts.” Signal strength is described in words, and reset codes become reasons, so the hub “restarted 4 days ago after losing power.”
Field Guide never talks about itself. It doesn’t mention versions, when recording began, or why a chart is short, and if something has nothing useful to say, it doesn’t appear at all. Its build history lives in the documentation.
The Instrument chapter ends with a reminder that these are observations.
What it’s built on
Field Guide is a skin for WeeWX, the open source weather software that receives the station’s broadcasts, keeps the archive, and draws every chart. The setup also uses:
- weatherflow-udp, the WeeWX driver that decodes the Tempest’s broadcasts
- Cheetah, the template engine WeeWX uses
- PyEphem, for the sun and the moon
- Home Assistant, which gets a copy of every reading
- Fraunces, Manrope, and IBM Plex Mono, all under the SIL Open Font License
- The USGS 3D Elevation Program, whose public-domain data gives the Stuart Range its shape
The hardware is a Tempest weather system (the station and its hub) and a UGREEN iDX6011 Pro server that runs everything. I’ve also written about how we self-host it.
What’s next
The Tempest is getting company. An Ecowitt GW3000 gateway will collect readings from a second outdoor sensor array, a second lightning detector, soil sensors, a pool thermometer, and a laser that measures snow depth.
Today, and what joins it
Wind, rain, light, lightning, temperature, humidity, and pressure.
radio
Tempest hub
Also uploads to Tempest's servers on AWS, over MQTT.
-
WS90 sensor array
Wind, rain, temperature, humidity, light, and UV.
-
WH57 lightning sensor
Lightning strikes and their distance.
-
WH52 soil sensors
Soil moisture, temperature, and conductivity.
-
WN36 pool thermometer
Pool water temperature.
-
LDS01 laser distance sensor
Snow depth.
radio
GW3000 gateway
Has its own temperature, humidity, and pressure sensors.
No internet upload.
Our server
Gets both over the home network.
Field Guide
One page for both.
The Ecowitt gateway joins the Tempest on the same server. Unlike the Tempest hub, it stays on the home network with no internet upload.
The Tempest measures rain well, but it can’t tell you what’s piling up. This winter, the number we’ll want first thing in the morning is how much snow is on the ground, and the laser will measure it.