Bring your Home Assistant automations across
You built them once already. FairGrow reads them from your Home Assistant through the bridge you have, copies them into the workflow editor and leaves the originals exactly where they are.
Your automations come across as they are. What they can see is what changes.
In Home Assistant an automation reaches what is in your house: a sensor, a switch, a time, the sun. On a nursery that runs out quickly. “Should I irrigate” is not a question about a soil sensor alone. It is a question about yesterday’s rain, the evaporation of the last three days, the stage the crop is in and what the satellite saw on Tuesday. You rebuild nothing for that: you bring them across in one click, with their triggers, conditions and actions.
Copernicus Sentinel-2
Vegetation and moisture indices per parcel, with the cloud mask already run for you. What we take from Copernicus
NASA POWER
Weather history and forecast on your own coordinates, with no station to buy. How we use NASA POWER
FAO-56
Reference evapotranspiration, the calculation behind the irrigation advice. How the advice is built
EPPO codes
Pests and diseases under the same code your inspector and your label use. What an EPPO code is
SILAM
Pollen forecast for your location, next to everything else on the parcel.
Crop registration
What you applied, and what you are allowed to apply. Keeping your records
One click to move them. Nothing to keep running.
Your automations come across as you wrote them, old YAML spelling and all. After that two jobs disappear. Maintaining the data sources: Copernicus, NASA POWER, FAO-56 and EPPO are simply there, and they stay there when an API behind them changes. And copying things over by hand: switch a rule on here that has to run in Home Assistant, and FairGrow puts it there itself under its own name, and takes it away again the moment you switch it off here.
Three steps
The bridge you installed for your Zigbee coordinator does the asking.
Ask your bridge
In the workflow editor, press Fetch from Home Assistant. The bridge asks Home Assistant what automations it runs. It takes a few seconds.
See what is there
You get the list with name and type. Anything FairGrow already runs is marked managed by FairGrow, so you cannot take the same one across twice.
Take it over
Press Take over on the one you want. FairGrow writes its own copy. Your original in Home Assistant is not touched, not changed and not switched off.
Taking over is looking, not handing over
The copy arrives switched off. Always.
Nothing runs until you say so
Taking one over shows you what you have; it does not move control. The copy sits under Saved with its switch off, and nothing happens until you turn it on yourself. Until then Home Assistant keeps running the original exactly as before.
That gives you room to run both for a while and compare. When you are satisfied, switch the FairGrow copy on and the Home Assistant original off. In that order.
Or paste it yourself
No bridge yet, or just one automation? Open the YAML editor and paste. It reads Home Assistant YAML as it comes, including the parts that trip up most tools.
trigger, condition and action rather than the newer keys.on and off unquoted, which YAML 1.1 reads as true and false.delay: 00:05:00, which lands as a number instead of a time.Press Check and you get a report
What was understood, and anything wrong with the line and column it sits on. There is an example button that loads a real Home Assistant automation with exactly those pitfalls in it, so you can watch what the import does before you trust it with your own.
What comes across, and what does not
Nothing disappears quietly. We would rather tell you a line did not survive than run an automation that half works.
Comes across
- Triggers on state, numbers and time
- Conditions, including sun and time windows
- Actions on devices FairGrow knows
- The name and description you gave it
Stops at the report
- Anything pointing at a device FairGrow has never seen
- A light in your hallway, a media player, a doorbell
- A script that only exists in your house
- Service calls with no equivalent here
What did not make it is in the report with the line it sits on, so you see it before you switch the copy on.
Then make it a grower’s automation
Once it is here, the same automation can reach what it never could.
No bridge yet? Connect your own Zigbee coordinator first. Four steps, and nothing in your firewall has to open. Connect your coordinator
Which Zigbee hardware works. What breaks with off-the-shelf adapters and brands, and what we catch for you. See what works
Questions we get
Do I have to give up Home Assistant?
No. The bridge keeps working, your Zigbee network stays yours and your house keeps doing what it does. Plenty of growers run both: the house on Home Assistant, the land on FairGrow.
Does anything change in my Home Assistant?
Not when you take one over; then we only read. After that only if you switch it on: let a rule run in Home Assistant and FairGrow writes it there under its own name, with FairGrow in front of it and a note that you manage it on fairgrow.eu, and removes it when you switch it off here. Your own automations stay out of it.
Can I take the same one across twice?
No. Once it is here it shows as managed by FairGrow and the button is gone.
Can I get it back out?
Yes. Every automation here is YAML you can read and copy, and we keep every version, so you can restore an earlier one.
Nothing appears in the list. Why?
Your bridge tells us whether it can do this. An empty list usually means the bridge needs updating, or that no coordinator is connected yet.
Bring yours across
Tell us what you run today and we will walk you through it.