“The first proper hard freeze ends the field's work; from now, all work is at the bench.”
We've received your request and will be in touch soon.
➤ Personal contact within 1 business day
➤ A proposal tailored to your situation
Toggle a rule on or off, adjust the threshold, and choose who gets notified.
| On | Type | Lower limit | Upper limit | |
|---|---|---|---|---|
| … | ||||
The e-mail address is per device, the Telegram chat-ID belongs to your account.
/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.
Send a one-off test notification to verify e-mail + Telegram work.
Drag temperature and humidity to see how VPD changes. The marker shows which zone you are in.
-
Set thresholds. Blank = off. You get an alert when a reading crosses the bound (checked every 10 min).
| On | Alert type | Threshold | Recipients |
|---|
Pick which of your contacts get this device alarm. Contacts are managed centrally in Weather alarms.
No contacts yet. Add them in Weather alarms first.
The system checks 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.
Changes apply to your account. Leave a field empty to fall back to the default.
Open Preferences for multiple locations and timezoneHardware actions (SD card, firmware, WiFi) require an admin token on this device. You can still remove data from the database below.
–
Browser uploads the firmware binary to fairgrow.eu. The device then pulls it from there over HTTPS - no external host or credentials required.
.bin here or click to choose
Detects time-series gaps in the FairGrow DB and backfills missing rows from the device CSV log on SD. Useful after WiFi outages or device reboots.
Flash is destructive. Device reboots; expect ~15-25s silence; new firmware must successfully report back within 60s or ESP32 auto-rolls back. All commands queue on FairGrow and execute when device next checks in (max 30s).
These satellites are small stat boards that wirelessly measure or control things (like a pump or the shutters). Here is how the data reaches this list:
Because the gateway collects and forwards in batches, a value can be up to ~60 seconds old.
Live data from the persistent ESP-NOW receiver (Metis-ESP-NOW V1.1+). Auto-refresh on every heartbeat (~60s).
| ID | Type | MAC | Reading | VBat | RSSI | Heard by | Seq | Age |
|---|
The next datalogger that hears this sat will claim it. Name, location and calibration are preserved.
| SSID | loading... |
|---|---|
| BSSID | – |
| Channel / RSSI | – |
| STA IP / mask | – |
| Gateway | – |
| DNS server | – |
| MAC | – |
| Status | – |
| Reconnects | – |
| Last disconnect | – |
This is the path every reading travels. The sensor talks to one access point (BSSID) of your network (SSID); that box hangs off your router, which uses the DNS server to find its way to fairgrow.eu. If anything in that chain drops out, the readings stop coming in.
RSSI is how loudly the sensor hears that access point, in dBm. The number is always negative and closer to zero is better: from -60 you are comfortably fine, around -70 it gets marginal, and below -80 readings start to get lost.
Reconnects counts how often the connection has been restored since boot. One or two is normal. If that number keeps climbing, the sensor is usually not the problem but the access point it is attached to - check Visible access points below to see whether a stronger one is within reach. Last disconnect is the reason the network gave when it last dropped the link.
Measures signal strength, packet loss to your router and to the internet, how busy neighbouring networks on the same channel are, and disruption frames over a full day. You get concrete advice with it, for example which channel to choose.
This device is not sending diagnostic data yet; that requires firmware with WiFi diagnostics.
Full WiFi diagnosis, last 24 hours loading...
| SSID | BSSID | Ch | RSSI | |
|---|---|---|---|---|
| click Scan now to fetch (~10s) | ||||
Switching networks is risky. If the new password is wrong, device reverts to the current network automatically after 90 seconds.
A fresh scan of everything the SENSOR can hear right now - not what your phone hears, but what is receivable at that spot in the greenhouse or the house. The scan takes about ten seconds.
Compare the RSSI in this list with the current connection above. If an access point on the same network is 10 dBm or more stronger, there is something to gain. Channel matters too: 1, 6 and 11 do not overlap, so two strong access points on the same channel interfere with each other more than two on different channels.
Switch moves the sensor to a different network and is for administrators only. It is a safe action: if the new password is wrong, the device falls back to its current network by itself after 90 seconds.
–
The same signal strength, but over time. A single reading says little; here you can see whether the signal is steady or slowly sagging.
The coloured bands give the meaning: green is strong, yellow is marginal, red is too weak to rely on. A grey dashed line is a gap - no reading arrived in that period, so the device was offline.
A line that sags during the day and recovers at night usually points at something standing in the way or switching on. A line that steps once and stays there means the sensor jumped to a different access point.
Enter 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.
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.
We use cookies to improve your experience on our site.
You decide which cookies to accept.
Read more about this in our Privacy Policy.
| ID | MAC | Raw | % | VBat | RSSI | Seq | Age | Loss |
|---|
Add up to 10 locations. The weather widget on your dashboard shows them as a carousel: swipe right to see the next location.
💡 Tip: type a place name, postcode or address and pick the right place from the list; the coordinates are filled in for you.
⭐ The top location is the default: the weather, the irrigation workflow and the alarms use that place as long as you do not choose another one somewhere else. Drag a location to the top to make it the default.
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).