Crop protection
What is on your crop, how do you recognise it, and which products are authorised against it in your country?
What is on your crop, how do you recognise it, and which products are authorised against it in your country?
We've received your request and will be in touch soon.
➤ Personal contact within 1 business day
➤ A proposal tailored to your situation
Changes apply to your account. Leave a field empty to fall back to the default.
Open Preferences for multiple locations and timezoneEnter the pairing code we emailed you when your sensor came online, or a share code someone gave you.
A pairing code is emailed to the address you entered during WiFi setup, and only works for that address. A share code is one another user made to give you access to their device.
Tip: get the key first. Once your phone is on the data logger's setup network you have no internet to fetch one.
In development
This pairing screen is still being built. As soon as it is ready you can add your device here.
You can connect more than one. Every coordinator keeps its own devices; add another one with the form above.
Connect your own Zigbee coordinator. You get a pairing code that you enter once in the bridge next to your coordinator.
How to install the bridgeEnter this code in your bridge
The bridge runs next to your coordinator and needs two things: the address below and this code.
How to connect your own coordinator
https://fairgrow.eu/wp-json/fg-zb/v1
Expires in 15:00
Waiting for your bridge to report in...
What we are seeing
Your bridge reports every five minutes what the coordinator sees. This is what stood out.
Devices already on this coordinator
Your coordinator already runs these devices. Tick the ones you want to use in FairGrow and we will ask each of them what it is. Nothing moves and nothing is re-paired: they stay exactly where they are.
These devices are on your coordinator but not in FairGrow yet. Not sure which one it is? Let it blink. After adding you can give it a name yourself.
Send us your log
Send us what the bridge wrote. We put it next to what the platform saw itself, so we have both halves of the same problem.
Which system is the bridge running on?
Let the bridge send it itself
One line in a terminal. The bridge collects diagnose.txt, brug.log and installatie.log itself and sends them on behalf of your account, so you do not have to go looking for files.
The bridge can only send on your behalf once a pairing has succeeded. That has not happened here, so pick the files yourself or paste the text.
diagnose.txt · brug.log · installatie.log
Run the bridge with --diagnose first: it writes diagnose.txt with everything about your system that matters here.
Passwords and tokens are masked on arrival, so they are never stored or mailed.
Connected
Your coordinator is linked. Open the pairing window from its card to add your first device.
Switch a rule on or off, mark what may break through quiet hours, and pick who gets told.
Something is broken and needs you.
| On | Notification | Recipients |
|---|
Nothing is down yet, but it is heading that way.
| On | Notification | Recipients |
|---|
Who can be told when something goes wrong with this coordinator. Your own account is always in the list; the rest you manage here. The first time this list is copied from your weather alarms, after that the two are separate.
| Name | Telegram |
|---|
/start).Adding someone else? Let them do these 3 steps and send you their number. They also need to open @MetisGarden_bot once and press Start, otherwise Telegram blocks the alarm messages.
Your bridge reports every five minutes what the coordinator sees. Pick what you want to hear about. Everything that happens within five minutes arrives as one message.
Which way a message leaves. A recipient without a matching address is skipped.
| On | Channel |
|---|
These are the same quiet hours as your weather alarms. What you mark as Important breaks through them.
This is the exact text a real alarm sends. Edit it if you like, pick who gets it, and send.
Nothing is wrong right now, so this is an example message.
History of notifications sent for this coordinator. Newest first.
| Time | Recipient | Channel | Status | Error |
|---|
The sensors coming in through your data loggers, separate from the Zigbee devices. ·
Loading...
Up to about a week ahead a weather model can predict the weather per day. After that the possibilities drift further and further apart. That is why for day 7 to 14 we do not show an exact value but a range and probabilities. The wider the band, the more uncertain the outlook.
In the short term the models are usually close together. By default we leave the dots out there, so that they mean something on the days where it matters.
Toggle a rule on/off, adjust the threshold, and pick which contacts get notified.
| On | Alert type | Threshold | Recipients |
|---|
Email and Telegram chat ID per contact. Leave the Telegram chat ID empty and click 🔗 to link your contact automatically via @MetisGarden_bot. Only fill it in manually if you already know the ID.
/start).Adding someone else? Let them do these 3 steps and send you their number. They also need to open @MetisGarden_bot once and press Start, otherwise Telegram blocks the alarm messages.
| Name | Telegram chat ID |
|---|
Tip: don't know your contact's chat ID? Click 🔗 for a link + invitation message (in any language) you can send via Telegram, WhatsApp, SMS or email. Or have your contact send /id to @MetisGarden_bot.
The system checks the forecast every 30 minutes. You get a message automatically as soon as a threshold is crossed - except during quiet hours. Each event is sent only once.
Run the alarm engine now against the live forecast. Preview shows what WOULD fire without sending; Run live now actually delivers.
Compose and preview the message, then send it as a test or share it yourself via Telegram, WhatsApp, SMS or e-mail.
History of notifications sent for this alarm. Most recent first.
| Time | Recipient | Channel | Status | Error |
|---|---|---|---|---|
| Loading… | ||||
Tick the alarms this contact should be notified about. The same list is on the Rules tab; changes here show up there immediately and are saved right away.
Pick which contacts get a message for this alarm. They need an e-mail and/or Telegram ID (see Contacts tab).