
Smart-home gardening · 13 min read
A plant care app for Home Assistant - from a threshold to a forecast
Home Assistant can already tell you when a pot crosses a line. What it cannot tell you is how fast each pot is walking towards it. What a plant care app should add on top of Home Assistant, and how to set one up so the readings stay yours.
Botanical Legacy · Field notes ·
A threshold tells you the pot is dry. A plant needs someone who knew it would be, and when.
A line is not a forecast
Home Assistant already has a plant feature. Its Plant Monitor integration groups a plant's moisture, conductivity, light, temperature and battery readings into one entity, and lets you set a minimum and a maximum for each. While every value sits inside its limits the plant's state reads ok. When one leaves them, it reads problem. Out of the box the moisture limits are 20 and 60, and conductivity is checked against 500 and 3000. Light is the one reading judged over time: a problem is only reported if the brightest reading of the last few days (three by default) stayed below the minimum. It is set up in YAML, and it does what it says.
What it does is draw lines. It does not know what the plant is, how fast its pot dries, or when the line will be crossed. That is a fair division of labour: Home Assistant is the place the readings live. But it is why so many plant setups in Home Assistant end at a notification that says a pot is dry, often at night, often for a plant that would have been better watered two days earlier or left alone for two more.
The common advice is to tune the threshold. A better question is what a single number can know about a pot. Three things work against it.
The same line arrives at different speeds. The University of Illinois Extension lists what decides how often a houseplant needs water: the type of plant, temperature, humidity, light, pot size, plant size, the potting mix and drainage. Plants in unglazed clay pots, it notes, tend to need water more often. Change any of these and the days between a full pot and a dry one change with it. The RHS adds the season: in summer, with higher temperatures, plants are more active and dry out faster, and central heating lowers the humidity indoors, so pots can dry faster in winter too.
Plants do not agree on where the line belongs. Illinois sorts houseplants into groups: some want soil constantly moist but not soggy, some should dry moderately between waterings, some want soil very slightly moist at all times. One limit for the whole house waters some of them too early and others too late.
The probe sees a small part of the pot. A capacitance probe estimates the water in the soil from its electrical properties. The University of Florida IFAS Extension describes the sensing sphere of influence as small, about 1.6 inches (4 cm), and calls good contact between sensor and soil extremely critical. Illinois puts it more plainly for a home grower: a moisture probe "can be useful, but may not always be reliable". A reading is evidence about the pot, not the pot itself.
None of this argues against Home Assistant. It argues for a second layer: something that reads what Home Assistant measures and turns a stream of numbers into a rate, a date and a record. That is what a plant care app for Home Assistant is for.
What to do
Keep the readings in Home Assistant, and let apps read them from there. Home Assistant can hear a Bluetooth probe, a Zigbee hygrometer and a vendor's cloud sensor side by side. If every app you use reads from Home Assistant, you can change a probe or an app without losing the other. The sensor comparison covers how FYTA, the Xiaomi Mi Flora and others reach Home Assistant in the first place.
Give each app its own user and its own token. Home Assistant lets you create a user without the Administrator toggle. Its documentation says non-administrators can use Home Assistant and see their own dashboards, but cannot reach the configuration and system settings. Sign in as that user, create a long-lived access token under your profile's Security tab, and hand the app that token. Home Assistant's developer documentation says these tokens are valid for 10 years, so delete one in the same place when you stop using the app that holds it.
Set limits per plant, not one for the house. If you keep Plant Monitor alerts, give each plant entity its own moisture minimum, chosen from what that plant wants: a plant that should dry moderately between waterings needs a lower line than one that wants to stay evenly moist. Twenty is a default, not advice.
Seat the probe where the roots are. The RHS advises feeling for moisture about a third of the way down a container. Push the probe to that depth or deeper, then firm the compost around it: an air gap around the sensing part spoils the reading. Where to put it in the pot, and which pot to put it in, is covered in the placement guide.
Find the full mark for each pot. Water thoroughly, let the pot drain and empty the saucer, as the RHS advises. Once the reading settles, note it. That is what full looks like for that mix and that probe. A reading of 40% means one thing under a peat-free mix and another under a gritty one.
Expect the drying rate to move with the season. The RHS notes that plants in a cool room need water less often than in a warm one, and that pots can dry faster in winter when heating lowers the humidity. A rate measured in July is not a rate for December. Whatever you use should keep measuring, not learn once and stop.
Log what you did, not only what the probe saw. A jump in moisture could be a watering, a probe pushed deeper, or rain on a balcony pot. Home Assistant records the number. Only you know the reason, and the care log is where that reason lives.
Use one hygrometer per room before a probe per pot. Air temperature and humidity are shared by every plant in a room. One sensor on the wall describes all of them, and a soil probe is worth most in the pot you find hardest to judge.
Three ways this plays out
One line for the whole shelf
A Home Assistant automation sends a phone notification when any pot on a living-room shelf drops below 30%. In July the boston fern crosses it two days after watering and the snake plant after nine. The fern gets its notification on a Tuesday evening and is limp by Wednesday morning. The snake plant's notification arrives on schedule, and the guardian waters a plant that would happily have waited longer. The automation was correct both times: both pots did cross 30%. The lesson: a shared threshold is accurate about the soil and silent about the plant.
The reading that moved the date
A calathea has a Mi Flora probe, read by Home Assistant through its Xiaomi BLE integration. Before the probe, its next watering was forecast from the species average and the room. After a watering, the probe reports the compost drying over the following days, and the forecast stops being a guess: the drying rate is now the one this pot showed, and the next watering date moves to match it. Nothing about the calathea changed. What the forecast was made from did. The lesson: a sensor is most useful when its readings change a plan, not when they cross a line.
The probe that went quiet
A probe in a monstera runs out of battery on a Friday. In Home Assistant the entity turns unavailable, and the automation that watches for a value below 30% never fires: a sensor with no value is not below anything. By Monday the guardian has been trusting a number that stopped arriving three days ago. A care app watching the same probe should notice the silence itself, and fall back to an estimate rather than freeze the last reading. The lesson: a missing reading is information too, and something has to be looking for it.
What Botanical Legacy does with your Home Assistant
Botanical Legacy is a plant care app that reads sensors from your Home Assistant. It does not connect to any sensor brand's cloud. Any probe that Home Assistant can see, through any integration, can feed it.
- It reads, and only reads. You give it your Home Assistant address and a long-lived access token. Every request it makes is for the list of current states (
/api/states): it never calls a service, never changes an entity and creates no automations. The token is stored encrypted. Disconnect HA on the Sensors page deletes it from our side; then delete it in Home Assistant too. - Your Home Assistant needs a public address. Our servers ask your Home Assistant for readings, so the address must be reachable from the internet: Nabu Casa Cloud, a public hostname, or a tunnel such as Cloudflare Tunnel. Private and local network addresses are refused. The setup guide walks through each step.
- Five kinds of reading. An entity is read if it has one of five Home Assistant device classes (temperature, humidity, moisture, illuminance or conductivity) and a unit we can convert. Temperature in °F or K becomes °C, and conductivity in mS/cm becomes µS/cm. A reading with no unit, or one we do not recognise, is skipped rather than guessed.
- Each reading goes where it belongs. Soil moisture, light and conductivity bind to one plant, because they describe one pot. Humidity binds to a room, because air is shared. Temperature goes either way.
- We check every hour, and again when you open a sensor screen (at most once every ten minutes). One reading per sensor per hour is kept for the charts, for 30 days.
- A soil reading anchors the forecast. Each time a Specimen's Digital Shadow is recalculated, its latest soil reading, if it is under 72 hours old, becomes the starting moisture, and the forecast carries on from there.
- The pot teaches its own drying rate. Once a plant's probe has at least two readings over six hours since the last watering, and they fit a clear line, the Why this schedule card switches from Estimated to Measured: the drying rate comes from that pot, not the species average.
- The room counts as well. When a plant's model is recalculated it takes its room's latest temperature and humidity, if the reading is under four hours old. An older one is ignored, so a dead room sensor cannot freeze the forecast. A week of lux readings from a plant's light sensor tunes its modelled drying rate. That is lux only: there is no DLI and no light alert.
- A drop below 20% does not wait for the night. When a soil reading falls from above 20% to 20% or below, a watering alert goes out with the check that sees it, if watering alerts are on.
- Conductivity is watched as a trend. Readings are banded for nutrition, and a rising salt trend raises an alert before it reaches the excess level.
- A silent sensor is noticed. If a plant's sensor stops reporting for six hours, you get an in-app and push alert, and one email after 48 hours. Room sensors do not raise these. Until a reading returns, the model carries on from its own estimate.
- Auto-logging is yours to switch on. With a moisture sensor bound to a plant, Guardian → Preferences offers Auto-log watering from sensor, off by default. When on, a jump of 25 points or more that lands at 50% or wetter is logged as a watering, unless one was already logged in the last six hours.
Plants without a probe are modelled too, from their species, their room, your care log and, with local weather on, the weather outside, so a shelf with one sensor still has a forecast for every pot. Sensors belong to the Cultivator and Conservancy plans, and to the trial. If a plan ends we stop checking your Home Assistant; your bindings stay, and checking resumes if you subscribe again. What any sensor app should do with your data is covered in the sensor app guide.
What the model can't see
A probe measures a few centimetres of compost. If it sits against the pot wall, in a pocket of grit or above most of the roots, it reports soil the plant is not using, and no app can correct a probe in the wrong place.
A reading also arrives without a reason. A sudden rise could be a watering, rain, or a probe pushed deeper into wetter compost. Auto-logging guesses the first; only you know for certain.
And the model sees water, temperature, humidity, light and salt. It does not see a root that has started to rot, a pest under a leaf or a plant that has outgrown its pot. Those still need someone to look, lift the pot and, now and then, turn it out.
Frequently asked questions
Is there a plant care app that works with Home Assistant?
Yes. Botanical Legacy reads soil moisture, temperature, humidity, light and conductivity sensors from your Home Assistant, binds each one to a plant or a room, and uses the readings to forecast each plant's next watering. It reads only: it never changes anything in your Home Assistant. Sensors are part of the paid plans and the 14-day trial.
Does Home Assistant have plant care built in?
It has the Plant Monitor integration. It groups a plant's moisture, conductivity, light, temperature and battery readings into one entity, compares them with minimum and maximum limits you set in YAML, and reports ok or problem. It does not know the species, measure a drying rate or forecast when a limit will be reached.
Can a plant care app water my plants through Home Assistant?
Home Assistant can run a pump or a valve through an automation, but Botanical Legacy does not control devices. It only reads states. If you automate watering, keep that automation in Home Assistant, and let the app's care log record the watering so the forecast restarts from it.
Does my Home Assistant need to be reachable from the internet?
For Botanical Legacy, yes. Our servers fetch the readings, so they need an address they can reach: Nabu Casa Cloud, a public hostname, or a tunnel such as Cloudflare Tunnel. A local address such as homeassistant.local or 192.168.x.x is refused.
Which plant sensors work with Home Assistant?
Any sensor Home Assistant shows as an entity with a standard device class. Common ones are the Xiaomi Mi Flora through the Xiaomi BLE integration, FYTA through its own integration, Zigbee soil and room sensors, and ESPHome builds. Botanical Legacy reads the moisture, temperature, humidity, illuminance and conductivity classes.
Is it safe to give a plant app a Home Assistant token?
Make it a token for a user without administrator rights, which Home Assistant's own documentation describes as unable to reach configuration and system settings. A long-lived token lasts 10 years unless you delete it, so delete it under your profile's Security tab when you stop using the app.
Do I need a sensor in every pot?
No. One hygrometer per room covers the air for every plant in it, and a soil probe is most useful in the pot you find hardest to judge. Plants with no probe are still forecast from their species, their room and your care log, plus local weather where it is on.
Start your sanctuary
Botanical Legacy's free plan covers up to five Specimens, indoors or out, with continuous Digital Shadow modelling and soil checks that teach each Specimen's drying rate. Every new account also gets a 14-day trial of the paid plan, which adds sensor support through Home Assistant or an Ecowitt gateway, watering alerts when a probe drops to 20%, and local weather - so the reading in the pot changes the forecast for the plant.
Start your sanctuary - five free specimens, no payment required →
The threshold says the pot is dry. The forecast said so on Tuesday.
Sources
4 references
The plant-care facts on this page were checked against these references.
- Illinois Extension: extension.illinois.edu/houseplants/watering
- RHS houseplants: rhs.org.uk/plants/types/houseplants/growing-guide
- UF/IFAS Extension: ask.ifas.ufl.edu/publication/AE266
- RHS watering containers: rhs.org.uk/container-gardening/how-to-water-containers