Adding the first sensor is the moment Home Assistant stops being abstract software and starts being a monitoring system. A Bluetooth temperature and humidity sensor is the standard first addition because the integration is simple, the sensors are inexpensive, the measurements are immediately useful, and the pattern teaches concepts that apply to every subsequent sensor. This page walks through the full process — choosing the sensor, placing it correctly, pairing it with Home Assistant, understanding the entities it produces, naming them properly, organizing by location, and verifying the readings make sense. By the end, the grower has real-world temperature and humidity data flowing into Home Assistant, visible on a dashboard, queryable through history, and ready to be used in automations.
Choosing the first sensor.
Any BLE (Bluetooth Low Energy) temperature and humidity sensor works. A few families are widely used, well-supported, and inexpensive.
SensorPush HT1. Modestly priced. Well-regarded in agriculture specifically. Good accuracy, strong battery life (years on a CR2477 coin cell), reliable BLE broadcast. Native Home Assistant integration. The collective's catalog includes a detailed entry on this sensor; see the [SensorPush HT1 catalog entry](/catalog) for specifics.
Govee BLE sensors (H5075, H5100, H5101, H5102, H5104, H5179). Roughly little each. Much cheaper than SensorPush, with correspondingly modest accuracy (usually ±0.5°C temperature, ±5% humidity, which is fine for most agricultural use). Integrated through the Home Assistant Bluetooth integration. Good for broad low-cost coverage across many zones.
Xiaomi LYWSD03MMC and similar. Around little depending on source. Very cheap Chinese-market sensors with active community firmware (custom firmware flashed over BLE). Accuracy is usable for relative trends but less reliable for absolute readings.
Aranet4 and Aranet2. Roughly a moderate amount. Higher-tier professional sensors including CO2 measurement in the Aranet4. Overkill for a first sensor but worth knowing about for deployments with CO2 or higher-accuracy requirements.
For a first sensor with no specific constraint, a SensorPush HT1 strikes a good balance of cost, accuracy, reliability, and agricultural relevance. A grower on a very tight budget can start with a Govee sensor — the integration works the same way, and the concepts transfer. A grower already owning any BLE sensor can use what they have; the walkthrough applies generically.
Placement before pairing.
Sensor placement affects the value of the data. A sensor in the wrong place produces readings that are technically accurate and practically misleading. Taking a few minutes to think about placement before pairing saves repairing later.
Put the sensor where the plants are. A sensor on a workbench measures workbench conditions. A sensor at canopy height in the middle of the growing zone measures what the plants actually experience. The gap can be significant — plant canopy temperature can differ from room air temperature by several degrees, especially with overhead lights or cold drafts.
Avoid direct sunlight. A sensor in direct sun reads the sensor's own heating from the sun, not the actual air temperature. Readings can be 5 to 10°F higher than reality. If the sensor must live in a zone that gets direct sun, use a small solar radiation shield (a simple white enclosure with ventilation) to block direct light while allowing airflow.
Avoid equipment heat and cold sources. Don't place the sensor directly above a heater (reads the heater's exhaust), next to a cooling vent (reads the cold air), or against a cold exterior wall (reads the wall).
Match the sensor's measurement zone to the question being asked. A sensor meant to track ambient greenhouse conditions should be at representative canopy height in a representative location. A sensor meant to track propagation mat conditions should be at substrate level inside the propagation zone. A sensor meant to track walk-in cooler conditions should be near the product being stored. Different questions want different placements.
Keep it within BLE range. For BLE sensors, range to the receiving device (the Home Assistant host or a BLE proxy) matters. Practical BLE range through open space is about 30 feet; through walls it is much less. If the first sensor is further from the Home Assistant host than reliable range allows, either move the sensor closer for initial pairing and then to its final location, or plan for a BLE proxy to extend coverage. The [Bluetooth Low Energy integration](/home-assistant/integrations/ble) page covers range extension with ESPHome-based BLE proxies.
Label the physical sensor. Before deployment, write a small label on the sensor itself — "Greenhouse Zone 1 canopy" or similar. Sensors accumulate, and a sensor in a drawer without a label is a sensor with lost identity. Masking tape and a marker work fine.
A common beginner mistake is rushing to pair the sensor before thinking about where it will actually live. The five minutes of placement planning is worth it.
Adding Bluetooth capability to Home Assistant.
Home Assistant needs access to Bluetooth hardware to talk to BLE sensors. Several options:
Built-in Bluetooth. Most laptops and many mini PCs have Bluetooth built in. Home Assistant uses it automatically if the operating system recognizes it. For Ubuntu Server hosts, confirm the Bluetooth driver is loaded with `hciconfig` or `bluetoothctl` — the hardware should appear.
USB Bluetooth adapter. A cheap USB Bluetooth dongle adds Bluetooth to any host that doesn't have it. Cambridge Silicon Radio (CSR)-based dongles are common and work reliably with Linux; modern Bluetooth 5.0 adapters are preferred for better range and reliability.
BLE proxy via ESPHome. For coverage beyond the Home Assistant host's location, ESPHome-based BLE proxies extend the Bluetooth reach. A small ESP32 device running ESPHome's Bluetooth proxy firmware, placed anywhere on the network, forwards BLE observations to Home Assistant. Useful for large operations where one host-location Bluetooth adapter cannot reach all sensors. Covered on the [Bluetooth Low Energy integration](/home-assistant/integrations/ble) page.
Home Assistant Yellow includes Bluetooth as part of its integrated radio. No additional hardware needed.
For a first sensor located near the Home Assistant host (the common first-hour scenario), the built-in or USB Bluetooth is usually sufficient.
Pairing the sensor.
With the sensor placed (or held close to the Home Assistant host for initial discovery), and Bluetooth available on the host, pair the sensor through Home Assistant.
Power on the sensor. Most BLE sensors advertise immediately when powered on. Some require a button press or a specific action to start advertising; check the sensor's documentation.
Navigate to Settings → Devices & Services.
If the Bluetooth integration is already configured and the sensor is a supported type, the sensor appears under "Discovered" at the top of the page, often within a minute of powering on. Click "Configure" or the sensor name to add it.
If the Bluetooth integration is not yet configured, Home Assistant may prompt to add it when the first BLE device is detected, or the grower can add it manually: click "Add Integration," search for "Bluetooth," follow the setup.
For some sensor types, a specific integration handles them better than the generic Bluetooth integration. SensorPush has a dedicated integration. Aranet has one. Govee has multiple depending on the specific model. If the generic Bluetooth integration detects the sensor, that usually works; for better features a dedicated integration may be available. Search the Devices & Services add integration list for the sensor's manufacturer name.
Follow the prompts.
Each integration's setup is slightly different. Most walk the grower through confirming the device, giving it a name, and optionally assigning an area. Complete the steps.
After setup, the sensor appears as a device in the Devices & Services list. Clicking it shows the entities it produces and their current states.
Understanding the entities produced.
A single BLE temperature and humidity sensor typically produces several entities.
`sensor.firstsensortemperature` — the current air temperature reading. Updates whenever the sensor broadcasts (every 1 to 60 seconds depending on the sensor).
`sensor.firstsensorhumidity` — the current relative humidity. Updates on the same cadence.
`sensor.firstsensorbattery` — the battery level of the sensor, usually as a percentage or voltage. Updates on the sensor's reporting cadence.
`sensor.firstsensorsignal_strength` — the BLE signal strength (RSSI) as received by the Home Assistant host. Useful for diagnosing range issues.
The exact entities depend on the sensor. Some produce additional entities for pressure, dew point, VPD, or other derived values. The integration documentation lists what each specific sensor produces.
View the entities.
Settings → Devices & Services → click the device. The device page lists all the entities and their current states. Click any entity to see detail, including a history graph.
Developer Tools → States. A comprehensive list of every entity in Home Assistant with its current state. Useful for confirming an entity's exact name and current value.
Developer Tools → Events. Shows events firing in real time. When the sensor updates, the relevant state change events appear here.
Naming and organizing.
The default names Home Assistant generates (based on the sensor model and a sequence number) work but are not memorable. A sensor called `sensor.goveeh50751a2btemperature` is harder to read in automations than `sensor.greenhousezone1temperature`.
Rename the device.
Settings → Devices & Services → click the device → click the pencil icon next to the name. Choose a descriptive name — "Greenhouse Zone 1 Canopy" is clearer than "Govee Sensor 1."
Rename the entities.
For each entity under the device, click it and then the settings gear icon to rename. The entity ID (the internal name used in YAML and automations) can also be changed here, though the collective recommends setting it once and keeping it stable afterward. Renaming an entity's ID later requires updating every automation, template, and dashboard that references it.
Convention suggestion for entity IDs: `sensor.locationmeasurement`, all lowercase, underscores between words. Examples: `sensor.greenhousezone1temperature`, `sensor.propagation1humidity`, `sensor.walkincoolertemperature`. Consistent naming scales to dozens of sensors without confusion.
Assign to an area.
Settings → Areas & Zones → Add Area to create "Greenhouse Zone 1" (or whatever location). Then back in the device's settings, assign the device to that area. All of the device's entities automatically inherit the area.
Areas are how Home Assistant groups entities for dashboards, automations, and queries. "Show me all temperature sensors in Greenhouse Zone 1" works when the sensors are properly assigned to areas; it does not work when they are not.
The [Organizing Home Assistant for a Farm](/home-assistant/agriculture/organizing) page covers area and naming conventions that scale to multi-zone operations.
Verifying the readings make sense.
A sensor reading a number does not mean the reading is correct. A quick sanity check catches configuration errors and sensor placement mistakes early.
Compare to a reference thermometer. A handheld digital thermometer held near the BLE sensor should read within a degree or two of what the BLE sensor reports. A larger discrepancy suggests either a calibration issue or a placement problem (the reference thermometer is in a different thermal zone than the BLE sensor thinks it is in).
Compare to expected conditions. Does the reading make sense for the location? A greenhouse at 82°F mid-afternoon in summer is plausible; a greenhouse at 40°F in summer is not. A reading that is clearly wrong usually points to a placement problem (sensor in direct sun, sensor near a heat source) more than a sensor problem.
Watch the reading for ten minutes. Temperature readings should change gradually if at all. Readings that jump around wildly (10°F in one minute, back again the next) suggest a problem — weak signal, interference, or a failing sensor.
Check the battery level. A freshly installed sensor should report near 100% battery. A sensor reporting 20% battery out of the box had the battery installed some time ago or is experiencing low-voltage conditions.
Check the signal strength. RSSI values closer to 0 are better (RSSI is a negative number; -50 dBm is good, -90 dBm is weak). Readings dropping to -85 or worse suggest the sensor is near the edge of range and may produce intermittent data.
Looking at the history.
Once the sensor has been reporting for at least a few minutes, Home Assistant has a short history available.
Click the entity in Devices & Services, or navigate to the History tab in the interface.
A graph appears showing the sensor's readings over time. The default view is the last 24 hours; longer ranges are available through the date picker.
Early on, the graph will be sparse. Over hours and days the history accumulates. After a week, meaningful patterns appear — daily temperature cycles, humidity responses to ventilation, the effect of overhead lights turning on and off. The history is where a sensor becomes genuinely useful — not just the current reading, but the trend.
Entity detail view provides basic graphing and statistics. For deeper analysis, the [Grafana Integration](/home-assistant/dashboards/grafana) covers the pattern of feeding Home Assistant data into Grafana for more sophisticated historical analysis.
Adding the sensor to a dashboard.
The default dashboard shows some entities automatically. A custom dashboard tile for the new sensor makes the readings more prominent.
Overview dashboard → edit (top-right pencil icon) → Add Card → Entities or Sensor card.
Select the new temperature or humidity entity. The card appears on the dashboard. Save the changes.
[Your First Dashboard](/home-assistant/getting-started/first-dashboard) covers dashboard design more comprehensively. For now, having the first sensor's readings prominently visible is enough.
What to do next.
The first sensor is working. Options for the immediate next steps:
Add more sensors. The pattern just learned applies to every subsequent sensor. Multiple sensors across multiple zones quickly build a meaningful monitoring picture.
Build a first automation. Now that real data is flowing, an automation that acts on the data becomes useful. [Your First Automation](/home-assistant/getting-started/first-automation) walks through building one.
Design a purposeful dashboard. A first dashboard with the sensors visible in context — layout that fits a phone screen, readings organized by zone, alert states visible — turns the system into something the grower checks with satisfaction rather than suspicion. [Your First Dashboard](/home-assistant/getting-started/first-dashboard) covers the design.
Let the data accumulate. Sometimes the right next step is patience. Let the sensor report for a few days. Review the history. Notice patterns — daily cycles, reaction to ventilation or heating, the effect of cloudy vs. sunny days. The understanding that comes from simply watching the data is the foundation for more ambitious use later.