A monitoring system sounds like a big technical thing. Strip it down and it needs exactly two things: a sensor to gather what you care about, and a way to get that reading to you, wherever you actually are. Everything else in the box just serves those two jobs. See it that way and you can build one for the price of a few coffees, or buy one, and stop wondering what is happening when you are not in the room.
01The need.
You cannot be everywhere. You sleep, you run errands, you leave for the weekend, and that is exactly when the heater quits, the pump fails, the cooler drifts, or the power blinks. Monitoring is the plain answer to "what is happening while my back is turned." It is the most useful first system most growers build, because the first time it texts you at 2 a.m. it pays for itself.
02Sense it, get it to you.
Every monitoring system, cheap or commercial, comes down to two jobs. One or more sensors gather the reading you care about: a temperature, a moisture level, whether a door is open (Understanding Sensors has the plain-language depth). And that reading has to reach you, or whoever needs it, or it was never worth gathering in the first place. Sense it, get it to you: that is the whole concept, before anything gets technical.
Everything else is plumbing that serves those two jobs. It matters, and each piece has its own plain-language lesson, but none of it is the concept:
- Power to keep the sensor running. Understanding Power.
- A way to communicate the reading onward. Understanding Communications.
- Somewhere for it to land and stay. Understanding Data.
- Something to read it on, a dashboard or an alert, for a human or an AI. Understanding Controls · Understanding AI.
You do not need any of it to be fancy. A $12 sensor on Wi-Fi, sending to a free dashboard that texts you, does both jobs completely. Appropriate technology says build the smallest thing that gets the job done.
03Building blocks, not a menu.
Do not think of a monitoring system as a shopping list where you pick one item per row. Think of the pieces as building blocks: a sensor, a small board, a gateway, a relay, a switch, Home Assistant, an endpoint. Each one does one clear job, and you snap them together into the system your place actually needs. That is closer to building with Lego than shopping off a shelf.
The building blocks come in different sizes. A sensor or a relay is small: it does one thing. A gateway is a bit bigger: it reads a sensor and carries the reading on, and nothing else. Home Assistant is a big block, already assembled: it senses, keeps, and uses data, all in one box, which is exactly why so many growers reach for it first. Less for you to put together, more capability the moment you turn it on. A small board and a gateway is more assembly and more to learn, but it costs less and it bends to a narrow job, like watching one cooler. Same building blocks, different sizes, and the right one depends on what you are actually trying to solve, not on which one sounds more serious.
Electronics went through this exact shift once already, and it is worth seeing clearly, because it is what makes the building blocks possible at all. For most of the last century a circuit was purpose-built: a fixed arrangement of parts, wired to do exactly one job, and a new job meant a new circuit. The microcontroller broke that. It is one general piece of hardware, cheap enough to put in almost anything, and what it does is decided by the software loaded onto it, not by how it is wired. The design work moved from hardware to software: instead of building a new circuit for a new job, you write new code for the same chip.
That is the whole reason a sensor, a small board, a gateway, and Home Assistant can be building blocks instead of fixed appliances. The same few-dollar board reads a soil probe this week and a cooler's temperature next week, because the difference is a few lines of code, not a different piece of hardware. See the fuller arc in the history of greenhouse technology and where it is headed in future CEA technology.
04How it works.
This stack is Collect·Have·Use, start to finish: the sensor and radio collect, the reading lands somewhere you have it, and a dashboard or alert lets you use it. Sense, power, and communicate are how you collect; somewhere for the reading to land is how you have it; something to read it on is how you use it.
Most of Open Agriculture Technology's hardware know-how lives here. We lean on the Home Assistant ecosystem and its standard way of describing sensors, so you ride on a huge open-source community rather than inventing your own.
05Collect: build the system.
| Buy a monitor | ~$40–200 | A ready-made temperature/humidity monitor that texts you. No wiring. The fastest way to the 2 a.m. alert. |
|---|---|---|
| Build it yourself | ~$12–60 | A small board, a sensor, and an afternoon. Cheaper, yours to repair, and it grows with you. The Build section has the sketches. |
| A hub and many sensors | ~$150–600 | A small home computer running Home Assistant, with sensors across several zones: one dashboard for the whole place. |
Go deeper
Hardware & Software · The Hort Assistant section · the eight Fundamentals lessons · ESP32 sketches and push methods in the Build section.
06Have: keep the readings.
A monitor that only shows the current number is half a system. The other half is keeping the readings, so today's number has yesterday's and last winter's to sit next to. As data is king puts it, keep them and keep them yours: wherever they land, you should be able to pull them out and take them with you.
Where a reading lands is your choice, and it should stay that way. A sealed, single-purpose monitor usually keeps your history with whoever made it: cancel the subscription and the record goes with it. Build the system out of open building blocks instead and the reading is yours from the first second, free to land on a service you pay for, a small server in the closet, or both at once. Open Agriculture Technology does not sell you the place your data lands. We publish one open message every building block can speak, so the pieces do not end up stuck talking only to each other, and we run a live demonstration endpoint so you can watch a reading travel from a sensor to a screen before you decide where yours goes: see it working. Where the reading can actually land, compared side by side, is on the Connectivity page.
And a kept reading is only worth keeping if it's true. Before you trust a number (or act on it), make sure the sensor behind it isn't quietly lying: trust your gauge.
07Use: see it, get told.
- Act: an alert when a number crosses a line you set. The text that saves the crop.
- Make sense of it: a dashboard and history that turn a wall of numbers into "this room runs hot every afternoon" or "humidity spiked the night the mold started."
Those are the same readings used at two speeds: a fast loop that acts today and a slow loop that learns across seasons. The fast one needs tonight's number; the slow one needs all the ones you kept.
And once the readings are flowing and yours, every other stack on this site (Environment, Root Zone, Light) is just a different thing to point the same system at.
The shortest version
A monitoring system needs two things: a sensor to gather what matters, and a way to get that reading to you. Build the smallest thing that does both (a $12 sensor that texts you counts), keep the readings and keep them yours, and use them to get told when something is wrong and to spot trouble early.
Frequently asked questions.
How do I monitor my greenhouse remotely?
Put a sensor (usually temperature and humidity to start) in the greenhouse, connect it to power and to a network (Wi-Fi if you have it, a long-range radio or cellular if you do not) and have it send readings to a dashboard or service you can open on your phone, with alerts when a number crosses a line. You can buy a ready-made monitor that does this, or build one with a small board and a sensor for around $12 to $30. The key parts are a reliable sensor, a way to carry the reading, and somewhere to see it and be alerted.
What is a farm or greenhouse monitoring system?
It is a setup that measures conditions (temperature, humidity, soil moisture, and so on) and makes them visible and actionable when you are not standing there. Every one, cheap or commercial, comes down to the same two jobs: one or more sensors gather the reading, and it reaches you or whoever needs it, with power, a communication link, storage, and a dashboard or alert as the supporting pieces in between. The differences between an inexpensive build and a commercial system are scale and polish, not the basic shape.
Can I use Home Assistant for a greenhouse or farm?
Yes. It is one of the most popular foundations for grower-built monitoring. Home Assistant is free, open-source software that runs on a small computer, collects readings from inexpensive sensors, shows them on dashboards, and sends alerts or runs automations. Because it is widely used and community-supported, you ride on a large ecosystem instead of inventing your own, and the readings stay yours to keep and export. It scales from a single sensor to a whole multi-zone operation.
How do farm sensors connect to the internet?
Through one of three common paths: Wi-Fi (simple where you have coverage), a long-range radio like LoRa (which can reach a sensor a mile or more from the house with very little power, ideal for fields and outbuildings), or cellular (where there is no other network). The sensor sends its reading over that link to a hub or service that stores and displays it. The right choice depends on distance, power, and whether you already have a network where the sensor sits.
What do I need to build a sensor monitoring system?
At minimum: a small board (an inexpensive microcontroller), a sensor for what you want to measure, power, and a place to send the readings (often free software like Home Assistant or a simple endpoint). From there you add a way to be alerted. A basic build runs around $12 to $60 and an afternoon of setup, and it is closer to assembling building blocks than to electronics design: each piece does one clear job and they snap together.
How much does a greenhouse monitoring system cost?
Anywhere from about $12 to thousands, depending on scale. A single build-it-yourself temperature/humidity sensor with alerts is roughly $12 to $30. A ready-made monitor runs about $40 to $200. A small-computer hub running Home Assistant with sensors across several zones runs about $150 to $600, depending on how many zones you cover. Commercial multi-zone systems tied into climate equipment cost much more. The good news: you can start at the low end and grow, because the readings are the same shape at every level.
Do I have to store my sensor data in the cloud?
No. Where a reading lands is a separate choice from the sensor that produces it. Readings can go to a paid cloud service, a small server you run yourself, or local software like Home Assistant or farmOS, and an open setup can send to more than one place at once. Sealed single-purpose monitors usually keep your history with the manufacturer; cancel the subscription and the record goes with it. If the pieces speak an open message format, you can change where readings land without replacing a single sensor.