Your Ecowitt gateway, per-plot
One GW1100 / GW2000 / HP2553 gateway can drive ten different plots on Garden.gg. Soil moisture per bed, outdoor weather for the whole yard, greenhouse climate for the indoor channel — automatically routed.
How it works
Connect a device
Open Garden.gg → Profile → Sensor Devices. Name it, map each Ecowitt channel to a plot, and copy the short URL you get back.
Paste into the gateway
Ecowitt app → Device → Weather Services → Customized. Protocol Ecowitt, Server iot.garden.gg, Port 80, paste the path, save.
Watch charts light up
Within 2–3 minutes the plot Environment dashboards start showing temp, humidity, soil moisture, and rain rate — fanned out per channel.
Channel routing
Each channel on your Ecowitt gateway corresponds to a physical sensor. Map each to a different plot — one gateway covers your whole garden.
What you get, per plot
Wind, UV, solar, PM2.5, and battery data are preserved in the raw payload per reading so they're ready for future charts — no data is dropped on ingest.
Supported sensors
Temperature, humidity, wind speed / direction / gust, rain rate + totals, solar, UV.
Up to 8 wireless probes. Route each to a different plot for real per-bed readings.
Capacitive probes, percentage reading. Lands on the dedicated Soil Moisture chart.
Ambient CO₂ + temp/humidity. Populates the CO₂ chart on the mapped channel.
Per-channel air quality, stored in raw payload (dedicated chart coming later).
Indoor temp + humidity + barometric pressure. Map to a greenhouse plot if you have one.
Common questions
No. Device tokens, soil moisture charts, and rain charts are on the free Sprout tier.
The ingest path is only 21 chars total (/i/e/ggd_XXXXXXXXXXXX). Fits everywhere.
Yes. Open the device in Sensor Devices, hit Edit, remap any channel to any plot. No need to reconfigure the gateway.
The gateway will get a 401 on its next upload; historical readings stay on each plot. Generate a new device to resume.
iot.garden.gg on port 80 and not the main domain on 443?Ecowitt firmware only POSTs over plain HTTP. garden.gg redirects HTTP → HTTPS which the gateway doesn't follow, so uploads silently fail. iot.garden.gg accepts HTTP at our edge and forwards upstream to origin over HTTPS internally — data still travels encrypted, the gateway just doesn't have to do TLS. Newer GW2000 firmware that supports HTTPS can use garden.gg on 443 instead.
Ready to connect?
Free account, 5 minutes, no credit card.