As an Amazon Associate, Akermin earns from qualifying purchases. Product links on this page are affiliate links.
Set up long-term logging in seven steps: write down the question the data must answer; choose sensors whose accuracy and drift suit it and intervals that match how fast each quantity changes; place and label each logger according to the question; calibrate or cross-check at the start and plan the same at the end; size memory and power for the full period with margin; establish a download and backup routine that does not depend on one app; and schedule a review of the data every month so problems are caught while they can still be fixed.
Step 1: The question
“Is the basement damp?” needs humidity and temperature at the coldest wall and mid-room for a winter. “Is the office ventilated for its occupancy?” needs CO₂ at 1 to 5 minute intervals for several weeks with occupancy notes. “Does the greenhouse overheat?” needs temperature every 5 minutes through a summer. Write the question; every later choice follows from it.
Step 2: Sensors and intervals
| Quantity | Accuracy for most studies | Interval | Notes |
|---|---|---|---|
| Temperature | ±0.5 °C | 10 to 15 min | Shield from sun and heat sources |
| Humidity | ±3% RH | 5 to 10 min | Log dew point or compute it later |
| CO₂ | ±(50 ppm + 3%) | 1 to 5 min | Control automatic baseline correction |
| PM2.5 | ±10 µg/m³ or 10% | 1 min average | Fan sensors need mains power |
| Pressure | ±1 hPa | 15 to 60 min | For compensation and radon interpretation |
| Radon | ±10% at 30 days | Device-determined (hourly) | Months of data needed |
See how often sensors should record data and the selection guides for temperature and humidity loggers, CO₂ loggers and air quality loggers.
Step 3: Place and label
Follow placement rules for each sensor; photograph each logger in place; label it with its ID and location; record height and distance from walls, windows and sources. A second logger at a reference position (mid-room or outdoors) makes the primary logger’s data interpretable. See why placement changes measurements.
Step 4: Calibrate at both ends
Before deployment: salt test for humidity, outdoor check for CO₂, ice bath or comparison for temperature, side-by-side for particles. Record the as-found values. Repeat at the end. The difference is drift, and it may need to be applied as a correction to the record. See calibration vs adjustment.
Step 5: Power and memory
Battery life and memory at the chosen interval must exceed the study length by a margin. For cloud loggers, confirm they buffer through Wi-Fi outages. For USB loggers, plan the download visits. Mains-powered loggers need a socket that will not be switched off by a cleaner or a timer.
Step 6: Data routine
- Download or export at least monthly to CSV.
- Store files in dated folders in two places.
- Check each export opens, has correct timestamps and no gaps.
- Keep a metadata file with everything from Step 3 and every event affecting the space.
Cloud dashboards are convenient and impermanent; the CSV is the record. See how to export and read data.
Step 7: Review monthly
Chart the month. Look for flat lines (dead sensor, full memory), steps (moved logger), gaps (power), and drift. Compare against the reference logger. Fix problems before the next month’s data is lost.
Common failures
- Memory full at week six of a twelve-week study.
- Logger moved by a cleaner; data continues from a different spot.
- Cloud service changed its export; a year of data becomes hard to retrieve.
- No calibration at the start; a systematic offset is discovered too late.
- No occupancy or event notes; the pattern in the data cannot be explained.
Loggers for each quantity are in the environmental monitoring category; for the underlying instrument, see what an environmental data logger is.
Recommended Tools
Products shown because their documented specifications fit this guide. Price and availability are on Amazon and can change.
Frequently Asked Questions
How often should I download data from a long-term logger?
Before the memory fills and at least monthly, so a failure loses at most a month. Cloud loggers should be exported quarterly as a backup against service changes.
Do I need to calibrate before and after a long study?
Yes. A check at the start proves the sensor was right; a check at the end shows how much it drifted, which is needed to interpret the record. Log both.
What metadata should I keep?
Logger model and serial, sensor accuracy, location and height, interval, start and end times, calibration results, and a note of every event that affected the space (works, occupancy changes, moves).
Affiliate disclosure: Akermin earns a commission from qualifying Amazon purchases made through links on this page. Our editorial picks are based on documented specifications and owner feedback, not commissions.




