Hort Assistant.

What Hort Assistant is, and what it is not.

The word Assistant in Hort Assistant is deliberate. Home Assistant, the software platform underneath, has spent over a decade earning that name — it assists the homeowner in managing their home. Hort Assistant is the same idea applied to agricultural environments. It assists the grower in managing their growing operation. It does not replace the grower, does not make the decisions, does not lock the grower into a specific way of doing things. It handles the tedium of constant monitoring, the repetitive decisions of routine control, and the record-keeping of what happens so the grower can focus on growing.

Hort Assistant is not a company. There is no Hort Assistant, Inc. There are no Hort Assistant products to buy. When someone in the collective says "we use the Hort Assistant approach at our operation," what they mean is they have configured Home Assistant to handle agricultural monitoring following patterns that work — patterns shared through the collective, refined through real deployments, and freely available to any other grower who wants to learn from them.

Hort Assistant is also not Home Assistant with a custom badge. Home Assistant is the underlying platform. Hort Assistant is the agricultural configuration of that platform — the specific integrations, dashboards, automations, and practices that make Home Assistant work well for growing. A grower who installs Home Assistant gets a capable home automation platform. A grower who installs Home Assistant and configures it following Hort Assistant patterns gets a capable agricultural monitoring and control system. The difference is configuration, not software.

Why Home Assistant.

Home Assistant did not start as agricultural software. It started in 2013 as a personal project to unify the smart-home devices in one person's house. Over the decade since, it has grown into one of the most widely deployed open-source platforms in the world, with millions of users, thousands of supported devices, an active developer community, and capabilities that now rival or exceed commercial home automation products that cost thousands of dollars.

The choice to build the collective's monitoring approach on Home Assistant rather than on an agriculture-specific platform is deliberate. Several reasons matter:

It exists and it works.

Home Assistant has been in production longer than most agriculture-specific IoT platforms have existed. It has been refined through years of actual deployment by people who depend on it for their homes. The core is stable, the documentation is substantial, and the failure modes are well-understood. Building on Home Assistant means inheriting all of that maturity rather than starting over with an agriculture-specific platform that has to earn the same trust from scratch.

It supports nearly every device a grower might use.

Home Assistant has integrations for thousands of devices — sensors, controllers, cameras, switches, gateways, weather stations, radios. Most devices a grower encounters have either direct Home Assistant support or can be integrated with modest effort. This means the grower is not locked into a specific vendor's device ecosystem. Buy the sensor that fits the job; Home Assistant handles the integration.

It runs on commodity hardware.

A complete Home Assistant installation runs on a small computer — a Raspberry Pi 4 or 5, a used mini PC, a dedicated Home Assistant Yellow or Green device. Hardware cost is typically moderately priced. No specialized agricultural hardware required.

It is genuinely open source.

Home Assistant is licensed under the Apache 2.0 license. The code is public, the development happens in the open, and anyone can fork, modify, or self-host the platform. This is not "open-source" as a marketing term — it is the real thing. A grower who deploys Home Assistant can be confident that the platform cannot be yanked away, made proprietary, or dramatically changed against their wishes.

It has a rapidly maturing agricultural community.

While not designed for agriculture, Home Assistant has been adopted by a growing number of growers, researchers, and educators. Integrations for specific agricultural needs have appeared — soil probes, irrigation controllers, commercial greenhouse systems. The OpenAgTechnology collective is part of this broader community, contributing patterns specifically useful for growers.

It does not depend on any single vendor.

Home Assistant is maintained by a nonprofit foundation and a community of developers. No single company controls the project. If any specific contributor or sponsor disappears, the project continues. This is unlike virtually every commercial agricultural IoT platform, where the platform's future depends on a single company's continued existence and business decisions.

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. Covered in detail in the Understanding Sensors lesson. 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 — WiFi, BLE, Zigbee, LoRa, cellular, Ethernet. Covered in Understanding Communications. Most Hort Assistant deployments use multiple communications technologies — BLE for short-range greenhouse sensors, WiFi 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: Raspberry Pi 4 or 5 for smaller deployments, a used mini PC for larger ones, or dedicated Home Assistant hardware like the Home Assistant Green for operations wanting a turnkey appliance. The hub computer 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.

The capabilities depend on what the grower chooses to deploy, but the typical Hort Assistant installation provides:

Continuous environmental monitoring.

Temperature, humidity, VPD, CO2, soil moisture, light intensity — whatever sensors the grower installs, continuously read and logged. The grower can see current values on a dashboard, review trends over any historical period, and query specific times or conditions.

Custom alerts.

Notifications when conditions cross thresholds the grower defines. Temperature out of range, humidity too high, soil moisture too low, sensor offline, door opened at unusual hours, pump running too long or not at all. Alerts route to phone notifications, SMS, email, voice calls, or any combination. The grower controls what triggers alerts, to whom, at what time of day.

Automation.

Actions the system takes based on conditions. Turn on a fan when temperature exceeds 82°F. Open a vent when humidity climbs above 85 percent. Run irrigation on a schedule unless soil moisture is already adequate. Log a spray application when a specific switch is activated. Automation logic lives in the grower's Home Assistant instance, is visible to the grower, and can be modified at any time.

Dashboards tuned to the operation.

Custom views of the data that match how the grower thinks about the operation. A quick-check view for the phone with the most-critical values. A detailed view for the office computer with trends and alert status. Role-specific views for workers who need access to some information but not all. Dashboards are configured by the grower to show what they want to see.

Historical data and analysis.

Every reading stored for as long as the grower configures — commonly 30 days of detailed data and years of summary data. The grower can review specific events, compare seasons, analyze what happened before a problem, or export data for use in other tools. This is a monitoring capability most commercial products provide poorly if at all.

Integration with other tools.

Home Assistant integrates with thousands of other services. Weather data from government sources. Calendar events from Google Calendar. Messages through any common messaging service. AI tools through OpenAI, Anthropic, or local model integrations. The grower can build workflows that connect sensor events to notifications, to document generation, to external systems, to AI analysis — whatever the operation needs.

Local operation regardless of internet.

Nothing critical depends on an internet connection. If the internet goes down, the hub continues receiving sensor data, running automations, storing history, and displaying dashboards on the local network. Alerting that depends on external notification services pauses during an outage and resumes when the connection returns, but the core monitoring and control continues.

Getting started.

A grower new to Hort Assistant does not need to build everything at once. The right progression is one layer at a time, proving each works before adding the next.

Step 1: Install Home Assistant on a small computer.

A Raspberry Pi 4 or 5 with an SD card, or a used mini PC, or a dedicated Home Assistant device. Follow the official Home Assistant installation instructions. This step alone gets the grower a running Home Assistant instance — no sensors yet, but the platform is operational. Expect an hour or two for this step including basic setup.

Step 2: Add a few starter sensors.

Start with two or three BLE temperature and humidity sensors placed in the area the grower wants to monitor. Pair them with Home Assistant through the Bluetooth integration. Within an afternoon, the grower has a working monitoring system with live data on a dashboard.

Step 3: Configure basic alerts.

Set up notifications when temperature or humidity crosses meaningful thresholds. Use Home Assistant's mobile app for push notifications, or integrate with SMS or email services. The grower should receive a test alert and confirm the notification works before depending on the system.

Step 4: Expand sensor coverage.

Add more sensors as the grower identifies needs — soil moisture, light, CO2, water flow, door sensors, cameras. Each addition follows the same pattern: physical installation, pairing with Home Assistant, adding to dashboards, configuring alerts where relevant.

Step 5: Build useful automations.

Start with simple automations — a fan that runs when temperature exceeds a threshold, an alert when soil moisture drops below a level. Test each automation carefully before trusting it with consequential decisions. Build complexity gradually as the grower gains confidence.

Step 6: Add field sensors if the operation extends beyond the building.

LoRa sensors with a gateway bring field monitoring into the same Home Assistant dashboard that shows the greenhouse. The LoRa setup adds a day of work initially but then scales to cover acres with additional sensors at modest cost.

Step 7: Integrate with other tools as valuable.

AI for data analysis. Voice assistants for hands-free queries. Weather integrations for context. Cloud backup for data resilience. Each integration earns its place by solving a specific problem.

Most growers who follow this progression have a working, useful monitoring system within a week of starting and continue refining it for months or years. The system grows as the operation evolves.

Where to find configurations the collective shares.

One of the collective's main contributions is a growing library of Hort Assistant configurations — specific setups that work well for specific situations. A configuration for greenhouse monitoring with BLE sensors. A configuration for LoRa-based field monitoring. A configuration for integrating industrial soil probes via Modbus. A configuration for an automated ventilation system with fail-safe defaults.

These configurations are more than just technical recipes. Each one includes the reasoning behind the choices — why these sensors, why this placement, why this threshold, what failure modes are protected against, what to watch for during commissioning. A grower using a configuration is not just copying files; they are learning what good looks like for their situation. And because the configurations are plain text, the grower can modify them to fit their specific operation.

Configurations are distributed through the collective's public repositories (as they are established) and through community forums. A grower who wants a specific configuration and does not find one can describe their need, and the collective often produces one — with contribution from members who have solved similar problems.

Costs.

Total cost of a typical Hort Assistant installation breaks down roughly as follows:

Hub computer.

Raspberry Pi 4 or 5 with accessories: a modest amount. Used mini PC: a moderate amount. Home Assistant Green appliance:. Home Assistant Yellow:. Most small-to-mid operations are well-served by the lower end of this range.

Starter sensors.

Consumer BLE temperature and humidity sensors: little each. Five sensors for basic greenhouse coverage: a modest amount. Higher-quality sensors (professional-grade soil probes, industrial CO2 sensors, accurate PAR sensors): a moderate amount each, needed only for applications where the measurement matters enough to justify the cost.

Field monitoring additions.

LoRa gateway: a moderate amount for a good outdoor unit. LoRa sensors: a moderate amount each depending on sensor type and whether solar-powered. A typical small field deployment with a gateway and four to six sensors runs a substantial amount total.

Actuator integration.

Smart plugs for simple on/off control: little each. Relays for higher-current loads: a modest amount each. Solenoid valves for irrigation: a modest amount each plus installation plumbing. Costs scale with how much the grower chooses to automate.

Optional accessories.

Small UPS for the hub: a modest amount. Network switch and cable if running Ethernet: a moderate amount. External storage for backups: a modest amount.

Ongoing costs.

Electricity for the hub: per month. Optional Nabu Casa cloud service for easier remote access: $6.50 per month. Everything else about the system has no recurring cost. Replacement sensors or batteries every few years at typical consumer and commodity prices.

Total for a typical small operation.

A functional Hort Assistant installation covering basic greenhouse monitoring with a few sensors, notifications, and simple automation can be built for a moderate amount in initial hardware. A more comprehensive system with multiple zones, field sensors, and actuator control typically runs a substantial amount. Substantial commercial-grade installations integrating many sensors and automations run a substantial amount. In every case, total cost of ownership over five or ten years is a small fraction of comparable commercial monitoring products.

Where Hort Assistant fits and where it does not.

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

Hort Assistant is less appropriate for large commercial operations where a dedicated service contract, 24-hour professional support, and insurance-backed reliability are genuine requirements. Those operations are served by the legacy commercial control systems covered in Understanding the Technology Landscape — and those systems fit that context well. A Hort Assistant installation at a hundred-thousand-square-foot commercial greenhouse is possible but probably not the right choice. The operation needs something different and can afford to pay for it.

Hort Assistant is also less appropriate for growers who want a truly hands-off solution and are willing to pay subscription fees to avoid any technical engagement. A consumer IoT product from a commercial vendor may fit that preference better, with the understanding that the grower is trading ownership for simplicity. See Understanding the Technology Landscape for that tradeoff.

For everyone else — the wide middle of growing operations globally, where commercial systems are too expensive and pure DIY is too much work — Hort Assistant is built specifically for that situation.