Home · Blog · Plant moisture sensors that actually help — picking one and putting the readings to work

Smart-home gardening

Plant moisture sensors that actually help — picking one and putting the readings to work

Most plant sensors end up forgotten because the reading never reaches a decision. Here's how to choose one, what your app should do with it, and why the reading matters less than what runs around it.

Botanical Legacy · 2026-05-01 · 11 min read

  • soil moisture sensor
  • wifi soil moisture sensor
  • home assistant plant sensor
  • plant moisture monitor app
  • houseplant smart watering
  • smart plant care
  • houseplant care

Most plant sensors die in a drawer. Not because the hardware is bad — because the reading never connected to a decision.


Why most plant sensor setups stop being useful after a week

You buy a sensor. It comes with an app. You stick the probe in a pot, you pair it on your phone, and for about a week you check the screen every morning. Then the screen becomes another notification you swipe past. A month later the sensor is in a drawer.

This is the shape of almost every "smart plant" purchase I have watched friends make. The hardware is genuinely cheap and genuinely accurate. The problem is not the sensor. The problem is what happens — or does not happen — to the reading.

A moisture number is not advice. It is a measurement. The moment between your soil is at 22% and you should water this plant tonight is the entire job. Most apps that ship with a sensor leave that job to you. You are left translating numbers into care decisions on your own, every time, for every pot.

The sensor that lasts in your Sanctuary is the one whose readings are doing something on their own — feeding into a model that already knows your specimen, your room, and the rest of the schedule. That is the bridge most setups never build.


Three kinds of plant moisture sensor — pick the one that fits your home

Before getting into setup, it helps to know what you are actually choosing between. Plant moisture sensors fall into three rough categories, and the right one depends less on price than on how many plants you have and what your home is set up for.

Phone-paired probes (Bluetooth)

These are the small probes you see online for under €20 — Mi Flora is the canonical example, with a long tail of similar HHCC-branded clones. They are cheap, accurate enough, and the coin-cell battery lasts six months to a year. The catch is range: a phone-paired probe needs your phone (or a small relay device) nearby and listening to actually reach the cloud.

If you have one or two prized plants in the same room as your phone, these are perfect. If you have a Monstera in the bedroom and a Hoya in the kitchen, you will need a relay sitting in the middle.

Best for: small collections, single-room setups, no soldering.

Wifi-direct probes (often built on the ESP32 microcontroller)

A capacitive moisture probe wired to a small wifi-capable microcontroller gives you a sensor that does not need a hub. It joins your home wifi directly and pushes readings to wherever you point it.

The tradeoff is you build it yourself, or buy a pre-assembled board, and you are responsible for keeping the firmware up to date. Battery life is shorter, and you are managing one device per pot.

Best for: five or more plants, outdoor pots out of phone range, builders who want to own the stack.

Hub-connected probes (ZigBee or Thread mesh)

Aqara, Sonoff, and a handful of others sell soil sensors that talk to a smart-home hub over a low-power mesh network rather than over Bluetooth. The mesh reaches further than Bluetooth without needing each sensor to be in earshot of your phone, and the batteries last about as long as the phone-paired probes.

You need the hub, which adds €40–80 to the setup, but if you already run smart bulbs or door sensors you probably have one. Reading quality is comparable across all three classes; the real difference is range and battery management.

Best for: larger collections, homes that already run a smart-home hub, anyone who wants minimal upkeep.


How a moisture reading actually improves your plant care

Here is the part most tutorials skip. A moisture reading is most useful when something is already running that knows what to do with it.

If your plant care app keeps a running estimate of how much moisture is left in each pot — based on species, weather, room temperature, and how long it has been since you last watered — then a reading does something specific: it sharpens the estimate. The model goes from we think the soil is around 24% to the soil is 22%, measured a few minutes ago. Estimate becomes ground truth.

That is the integration that matters. Without it, the reading lives in its own silo: a number you have to interpret, every day, on top of everything else you are already doing for your plants.

This is what we built the Botanical Legacy sensor support around. When you connect a probe — whether it is a single Mi Flora in your favourite Calathea or a half-dozen Aqaras across a balcony — the readings flow into the per-plant Digital Shadow that is already running. Your watering reminders shift accordingly. If the room is drier than expected for the time of year, you hear about it earlier. If it is more humid, you hear about it later. You do not translate numbers into decisions; the model does.

A number on your phone is data. A specimen that gets the right care is the point.

Zone sensors when you cannot afford one per pot

Most people cannot put a probe in every pot, and they do not need to. A single sensor in the same room as a cluster of plants tells you a lot about the room — how warm it really is, how dry the air is, how those things are changing through the day. That is enough to nudge the model for every plant in the room without buying ten probes.

Botanical Legacy handles this by letting you bind a sensor either to a specific specimen or to a whole zone of your Sanctuary. One sensor, ten plants benefiting. It is the practical setup for most apartments.

What flows into the Digital Shadow today

Worth being plain about, because this is where most articles get hand-wavy. Three signals from Home Assistant feed your specimens' Digital Shadows:

  • Room temperature and humidity, bound to a zone in your Sanctuary — every plant in that room benefits from the same reading.
  • Per-specimen soil moisture, bound to a single plant. When a fresh reading exists, the Digital Shadow uses it as ground truth instead of the modelled estimate; the day's depletion is calculated forward from there.

When the soil reading and the model disagree — say, the model predicted 30% but the probe says 60% — the probe wins. This is the simplest honest behaviour: a real measurement beats a forecast.

In practice the room sensors and the soil sensors do different jobs. A room running 28°C in July versus 19°C in November is the single biggest predictor of how fast your soil dries. A soil probe in a specific pot is the ground truth for that pot. Both feed the same Shadow; both shift the watering schedule the right way; you do not need both for the model to be useful.

What happens when the sensor goes quiet

Sensors die. Batteries run out. Wifi drops. The honest design question is what your app does in the gap.

Our answer is: it falls back to the model. The estimate keeps running on species, weather, and last-watered date — exactly the way it does for plants without a sensor at all. When the readings come back, they sharpen the estimate again. You do not lose continuity. You do not get a blast of late notifications when a sensor reconnects after a week away.

This is the part you cannot really test until something breaks. Worth knowing before it does.


Three scenarios — the same Monstera, three weeks

These are illustrative, but they show what changes when a room sensor is feeding the model.

Scenario 1: A hot week

It is the first week of July. Your Monstera sits in an east-facing window. Without a sensor, the model leans on local weather and assumes a typical summer room. With a room sensor reporting 28°C and dry air, the model knows your apartment is hotter than the forecast says, and the watering nudge slides earlier — closer to day six than day nine.

Scenario 2: A cold, cloudy week

The next week brings 19°C and grey skies. Same plant, same pot. The room sensor sees the slowdown, the model eases off, and the nudge slides later — closer to day fourteen.

Scenario 3: The sensor goes offline mid-week

The probe's battery dies on a Wednesday. The model falls back to the modelled estimate based on species, season, and last-watered date. When you swap the battery on Saturday, the readings come back in and snap the estimate into focus again. No backlog of late notifications, no gap in care.

A fixed nine-day interval would have watered too late in July, too early in August, and not noticed the offline week at all. The Digital Shadow is closer to the right answer all three times.


The path that works today — Home Assistant as the bridge

The simplest path from "I have a sensor" to "my plant care app uses it" runs through Home Assistant. Home Assistant is a free, open-source smart-home platform that runs on a small computer in your home. It speaks every common smart-home protocol and presents your sensors as a uniform list any other app can read.

Home Assistant is the bridge we connect to today. Whatever sensor you bought, if Home Assistant can see it as a temperature or humidity entity, Botanical Legacy can use it.

If you already run Home Assistant, you will find a connect button in your Sanctuary settings. The on-screen guide takes about ten minutes — you generate a token in Home Assistant, paste it into Botanical Legacy along with your Home Assistant address, and pick which entities map to which specimen or zone. After that, the connection runs on its own.

If you do not run Home Assistant yet and the prospect feels heavy, it is reasonable to start without one. The Digital Shadow runs whether or not a sensor is connected — a real reading sharpens it, but the model does the heavy lifting either way. You can pick up sensors later when you are ready.


A note on building your own

If you would rather assemble your own probe than buy one, the practical path today is the same: build the probe, run an open-source firmware on it that the smart-home community already maintains, expose it through Home Assistant, then connect Home Assistant to Botanical Legacy. The community documentation around this is excellent and well-worn.

We do publish reference firmware for the path where the probe talks to us directly — no Home Assistant in the middle. The hardware works. The consumer-grade setup flow for it is not ready for a wider audience yet. We will publish a dedicated end-to-end build guide when the experience is something we are proud to put in front of someone who has never soldered before.


Frequently asked questions

Do I need a sensor in every pot?

No. One sensor per room is the right default for most people. A room sensor tells the model how warm and humid your space actually is — those are the two factors that vary the most across seasons and across rooms. A soil-moisture probe on a specific specimen is worth it for a high-value or finicky plant — a young propagation, a recovering Ficus, a rare species you are trying to dial in. When a soil probe is bound to a specimen, the Digital Shadow anchors on that reading directly instead of the modelled estimate.

Can the probe stay in the pot permanently?

Yes, if it is a capacitive sensor. Capacitive probes — including Mi Flora, ESP32 capacitive builds, and most Aqara and Sonoff models — are sealed against soil moisture and can live in the pot indefinitely. Older resistive probes (the ones with two metal prongs) corrode within a few months in damp soil. If you cannot tell from the listing which kind you have, look for "capacitive" in the spec sheet — and avoid anything cheaper than €5, which is almost always the corroding kind.

Will a phone-paired probe work without a hub?

Only if your phone is consistently in range of the sensor and the app is allowed to run in the background. In practice this means your phone is near the plant for most of the day, every day. For a single bedside plant this can work; for anything else, you want a relay device. A small Home Assistant install in your living room solves this for the entire home.

Does Botanical Legacy support voice assistants like Alexa or Google?

Not yet. We are not pretending to. Voice assistant support is on our roadmap — the underlying account scaffolding is there — but you cannot ask Alexa about your plants today. We will write about it on this blog the day it actually ships.

What happens if I cancel my Cultivator subscription?

Your sensor connection pauses with the rest of the Cultivator feature set. Your specimens and their history stay safe in your account. If you re-subscribe later, your existing sensors come back online with their previous bindings; you do not have to set them up again.


Try it yourself — sensor support is included with the trial

If you want to see what this actually looks like with your own sensors, every Botanical Legacy account starts with a 90-day Cultivator trial. That includes the full Digital Shadow, the local weather feature, and the Home Assistant integration. No payment required to start, and the free Observer plan keeps your first five specimens supported afterwards.

If you do not have a sensor yet and you are not sure where to start, the Digital Shadow article is the better first read — it explains how the underlying model works without any hardware at all. You can pick up a sensor later when you are ready.

Start your Sanctuary — free, no payment required →


A reading on your phone is data. A specimen that gets the right care is the point.


Botanical Legacy, May 2026. Home Assistant temperature, humidity, and per-specimen soil-moisture ingestion all ship today. We update this post when the integration changes.