Treat maintenance as data quality control
A clean, level, powered station is more valuable than a feature-rich station with unknown history. Log each cleaning, battery change, outage, move, and nearby site change so you can distinguish equipment issues from real weather.
Monthly or as indicated
Seasonally
After severe weather
Troubleshoot before replacing a sensor
Rain total is zero or too low
Inspect the inlet for debris, make sure the collector is level, verify the tipping mechanism moves freely only as manufacturer instructions allow, and check recent battery or connection changes. Compare event timing with a nearby reference, not just a monthly total.
Temperature or humidity jumps
Look for direct sun, reflected heat, vents, irrigation, a loose radiation shield, weak power, or a recent sensor move. Clean only with manufacturer-approved methods and allow the sensor to stabilize before judging it.
Wind is erratic or calm
Check for a bent mast, blocked cups, wrong direction alignment, low batteries, or new obstructions. Turbulence beside roofs and trees is a siting limitation, not necessarily a fault.
Console or app is missing data
Confirm power, distance, radio obstructions, router changes, account status, and timestamps. Preserve any local export before resetting; record the gap rather than inventing values later.
Reference comparison: use trends, not false precision
Compare several days or similar events with a trusted nearby observation. Distance, elevation, storm tracks, terrain, timing, and exposure can make genuine differences. Investigate a persistent directional bias or sudden step change, especially following maintenance, construction, or a storm.
Use rainfall units when checking totals, connect reliable rain data to water-harvesting estimates, and use the simulator to make an observed rate easier to picture.