Hort Assistant.

What Hort Assistant is.

Hort Assistant is software running on a computer at the greenhouse or farm, monitoring and helping run the operation. We call it the grower's Internet-of-Things engine: it gathers readings from sensors, evaluates them, makes decisions, causes actions, and shares data with any endpoint the grower chooses.

The distinction worth keeping straight: Home Assistant is the platform; Hort Assistant is what we make of it. Home Assistant is open-source software, free to download, use, and modify, with integrations for thousands of sensors and devices. When we say Hort Assistant, we mean Home Assistant configured for agricultural monitoring and control, following the patterns in the library below: the sensor choices, dashboards, automations, and practices that make a general-purpose platform work like it was built for growing. Installing Home Assistant gets you the platform; configuring it the Hort Assistant way gets you an agricultural monitoring and control system you own outright.

Why Home Assistant is the platform.

The Home Assistant project started in 2013 as one person's smart-home unifier. A decade on, it is one of the most widely deployed open-source platforms in the world: millions of users, thousands of supported devices, an active developer community, and capabilities that rival commercial automation products costing thousands of dollars.

It integrates almost anything. Sensors, controllers, cameras, switches, gateways, weather stations, radios: most devices a grower encounters have direct Home Assistant support or integrate with modest effort. The grower is not locked into any vendor's ecosystem. Buy the sensor that fits the job; Home Assistant handles the integration.

It runs on commodity hardware. A complete installation runs on a small computer: a repurposed desktop, a used mini PC, a Raspberry Pi. No specialized agricultural hardware required.

It is genuinely open source. Apache 2.0 licensed, publicly developed, maintained by a nonprofit foundation with no single company in control. It cannot be yanked away, made proprietary, or changed against the grower's wishes; if any sponsor disappears, the project continues. That is unlike virtually every commercial agricultural IoT platform, whose future rides on one company's business decisions.

And its agricultural community is maturing fast. Growers, researchers, and educators keep adopting it; integrations for soil probes, irrigation controllers, and greenhouse systems keep appearing. This collective is part of that community.

One honest gap remains, and it is the reason this section exists: the official documentation at home-assistant.io is excellent, and nothing here replaces it, but it is written for a reader whose goals are lights, locks, and thermostats. A grower's goals are different. The failure modes are different, the hardware choices are different, the automations that pay for themselves are different. The guide library below teaches the platform the way a greenhouse veteran would: as a working part of a real operation. That agricultural layer is Hort Assistant.

The Hort Assistant stack.

A typical Hort Assistant deployment has four layers. The specific hardware and configurations vary by operation, but the shape is consistent.

Layer 1: Sensors and actuators. The physical devices that measure and act: temperature and humidity sensors, soil moisture probes, light sensors, flow meters, CO2 sensors, pressure transducers, relays, solenoid valves, cameras. The Hort Assistant approach favors commodity-priced devices where they fit and quality industrial devices where the application demands. A greenhouse operation might use inexpensive BLE temperature sensors for general coverage and a moderately priced industrial soil probe for the critical irrigation control point.

Layer 2: Communications. The radios and networks that move data from sensors to the hub computer: Wi-Fi, BLE, Zigbee, LoRa, cellular, Ethernet. Most Hort Assistant deployments use several at once: BLE for short-range greenhouse sensors, Wi-Fi or Ethernet for the hub's network connection, LoRa for field sensors. Home Assistant supports all of these through integrations.

Layer 3: The hub. A small computer running Home Assistant. This is where sensor data is received, stored, displayed, and acted upon. Typical hardware: a repurposed desktop or laptop, a used mini PC, a Raspberry Pi, or dedicated Home Assistant hardware for operations wanting a turnkey appliance. The hub sits in a protected location (office, mechanical room, packhouse) with wall power, network connection, and ideally a small UPS.

Layer 4: Access and integration. The ways the grower interacts with the system and how the system interacts with other tools. Web dashboards viewable on any device on the local network. Mobile apps for phone access. Optional cloud layer through Home Assistant's Nabu Casa service for secure remote access. Integrations with notification services, email, SMS, voice assistants, and AI tools. This is the layer where the grower's experience of the system lives.

What Hort Assistant does for a grower.

What you get depends on what you deploy, but a typical installation provides:

• Continuous monitoring. Temperature, humidity, VPD, CO2, soil moisture, light, whatever you install, read and logged around the clock, with live values and trends on a dashboard built the way you think about the operation.
• Custom alerts. A notification when a reading crosses a threshold you set, routed to phone, SMS, email, or voice, on your terms.
• Automation. Actions the system takes on its own: a fan above 82°F, a vent above 85% humidity, irrigation unless the soil is already wet. The logic is yours to see and change.
• Historical data. Every reading kept as long as you choose, to compare seasons, trace what led up to a problem, or export for other tools.
• It keeps working offline. The hub monitors, logs, and runs automations with no internet; only external notifications pause until the connection returns.

The hardware approach.

One decision in this section deserves to be named up front because it differs from what a grower will find almost everywhere else. Most Home Assistant resources recommend a Raspberry Pi or a Home Assistant Yellow / Green as the starting hardware. Those are reasonable for hobbyist deployments. For anything larger (a commercial greenhouse, a multi-zone operation, a grower who wants to add AI or computer vision or a deeper history database), the collective recommends something different.

The primary recommendation is a repurposed business-class desktop or laptop. An old office desktop or ThinkPad has more processing power, more memory, more storage, and more durability than a new Raspberry Pi. A laptop comes with its own battery, which serves as a free uninterruptible power supply when utility power blinks. Both can often be acquired free. Both support the graybox approach: one capable machine running Home Assistant alongside Docker, a database, a media server, file storage, a VPN, and anything else the operation needs.

Choosing Your Hardware is the deep-dive page. Repurposing a Desktop and Repurposing a Laptop cover the primary path. Using a Mini PC covers the secondary path. Purpose-Built HA Hardware covers the hobbyist tier honestly: where it fits, where it does not.

Installation methods.

Three installation methods the library covers in depth: Home Assistant OS (simplest path: dedicated OS), Home Assistant Supervised on Ubuntu (the graybox recommendation), and Home Assistant Container (bare Docker for hosts already running other services).

Getting started.

You don't build it all at once. Add one layer at a time, proving each before the next.

1. Install Home Assistant on a repurposed desktop, used mini PC, or Raspberry Pi, following the install guides above, an hour or two with setup.
2. Add a few starter sensors (two or three BLE temperature and humidity), pair them over Bluetooth, and you have live data by the afternoon.
3. Configure basic alerts for the thresholds that matter, and send yourself a test before you rely on it.
4. Expand coverage as needs appear: soil moisture, light, CO2, flow, doors, cameras.
5. Build automations gradually, simple ones first, each tested before you trust it with a real decision.
6. Add field sensors over LoRa when the operation reaches past the building, into the same dashboard.
7. Integrate other tools as they earn it: AI analysis, voice queries, weather, cloud backup.

Most growers have something useful running within a week, then refine it for months or years as the operation grows. Your First Hour is the walkthrough for day one.

The guide library: all 61 pages.

Every guide is a shared configuration with the reasoning behind it, not just the files, so you learn what good looks like for your situation and can adapt it in plain text. Organized by what a grower is trying to do, not by topic taxonomy. Type to filter, or jump to a group; if the pattern you need is not here yet, describe it, and a member who has solved something similar often shares theirs.

Costs.

A Hort Assistant system is mostly a one-time hardware cost. The hub is a Raspberry Pi or a used mini PC. Sensors start at a few dollars for a BLE temperature and humidity unit and climb only where precision earns it, a professional soil probe or PAR meter. Actuators (smart plugs, relays, valves) and LoRa field gear add cost as you automate and reach past the building. The one recurring cost is optional: Home Assistant's Nabu Casa remote-access service at $6.50 a month. Over five or ten years the total runs a small fraction of a comparable commercial system. For real prices by category, see the Catalog.

Where Hort Assistant fits.

Hort Assistant suits operations that want monitoring and control they own, at commodity prices, with the flexibility to adapt as needs change. That covers most small-to-mid-scale growing: greenhouses, high tunnels, container farms, small field operations, specialty crops, controlled environment rooms. Across most of that range it is at or near the best choice available.

Two situations call for something else. A large commercial operation that needs a dedicated service contract, 24-hour professional support, and insurance-backed reliability is better served by the legacy commercial control systems covered in the technology landscape, and those systems fit that context well. A grower who wants a hands-off solution and will pay a subscription to skip the technical side may prefer a consumer IoT product, trading ownership for simplicity. Everyone else (the wide middle, where commercial systems cost too much and pure DIY is too much work) is who Hort Assistant is built for.