Quick answer
If your primary goal is reliable local Home Assistant integration with minimal cloud dependency, an Ecowitt sensor array plus a GW2000 or GW3000 gateway is usually the most straightforward path. Ecowitt publishes an official Home Assistant integration that reads data from supported gateways on your LAN, and Home Assistant’s built-in Ecowitt integration lists GW2000/GW3000 as supported gateways.
Ambient Weather, Davis, and Tempest can also work with Home Assistant, but the integration model differs: Ambient often relies on cloud API or community local-push tools; Davis commonly uses WeatherLink Live; Tempest exposes local UDP/WebSocket APIs documented by WeatherFlow.
This guide compares documented compatibility and architecture — not hands-on accuracy rankings.
Who this guide is for
- You run Home Assistant and want weather entities for automations (awnings, heat pumps, irrigation hold-off, notifications).
- You prefer local LAN data over polling a cloud API.
- You are comparing Ecowitt vs Ambient Weather and want to understand gateway/console options before buying hardware.
See also: local data guide, no subscription guide, and Ethernet gateway guide.
How Home Assistant integrations actually work
Weather stations rarely speak directly to Home Assistant. A gateway or console aggregates RF sensor data, then Home Assistant receives it via one of these patterns:
- Local push (HTTP webhook) — device pushes to Home Assistant on your LAN (built-in Ecowitt integration; Ambient Custom Server with community integrations).
- Local pull (HTTP API) — Home Assistant polls the gateway IP (Ecowitt official HACS integration).
- Local broadcast (UDP) — console broadcasts packets on the LAN (Davis WeatherLink Live; Tempest hub).
- Cloud API — Home Assistant polls AmbientWeather.net or WeatherLink Cloud (works, but adds latency and external dependency).
Home Assistant classifies the built-in Ecowitt integration as Local Push. Ecowitt’s official integration uses local HTTP APIs on supported gateways.
Compatibility at a glance
| Platform | Typical hardware | HA integration path | Local LAN without cloud | Ethernet gateway |
|---|---|---|---|---|
| Ecowitt | WS90 + GW2000/GW3000 | Official HACS + built-in Ecowitt | Yes (documented) | GW2000/GW3000 |
| Ambient Weather | WS-2902 / WS-5000 console | Built-in Ambient (cloud) + community local push | Partial (Custom Server + add-ons) | WS-5000 console (model dependent) |
| Davis | Vantage Vue + WeatherLink Live | WeatherLink / community | Yes (UDP broadcast documented) | WeatherLink Live (Wi‑Fi/Ethernet) |
| Tempest | Tempest hub | Tempest integration / UDP | Yes (local UDP documented) | Wi‑Fi hub |
For a head-to-head of two popular ecosystems, see Ecowitt vs Ambient Weather.
Ecowitt (GW2000 / GW3000 + sensors)
Why it fits Home Assistant: Home Assistant’s integration docs explicitly list GW2000 (Ethernet and Wi‑Fi) and GW3000 (Ethernet and Wi‑Fi with data storage). Ecowitt’s official integration repository documents GW2000 and GW3000 as supported for local HTTP API access.
Typical setup: Outdoor array (e.g. Ecowitt WS90) → RF → GW2000 or GW3000 on your network → Home Assistant integration using the gateway IP.
Integration options:
- Ecowitt Official (HACS) — pulls live data from the gateway HTTP API on your LAN.
- Home Assistant Ecowitt (built-in) — configure DIY Custom Upload Server on the gateway to push to Home Assistant’s webhook endpoint (HTTP).
Verify before buying: Confirm your exact gateway model appears on the Ecowitt official integration compatibility table. Confirm your Home Assistant instance can accept HTTP on the upload path if using the built-in integration.
Gateway comparison: Ecowitt GW2000 vs GW3000.
Ambient Weather consoles
Default path: Home Assistant’s Ambient Weather integration uses AmbientWeather.net API keys — cloud-dependent.
Local path (advanced): Ambient consoles with Custom Server support (see Ambient firmware notes and community projects such as awnet_local) can push data to Home Assistant on your LAN. This is not as turnkey as Ecowitt’s official integration and may require maintaining console settings across reboots (community tools attempt to auto-heal this).
Models often discussed for local push: WS-2902 series, WS-2000, WS-5000 (verify firmware and console IP access for your exact SKU).
Product pages: Ambient WS-2902, Ambient WS-5000.
Davis Instruments + WeatherLink Live
Davis stations are commonly paired with WeatherLink Live for IP connectivity. Home Assistant users often consume local UDP broadcasts from WeatherLink Live (community/documented approaches vary by integration version).
Trade-off: Strong reputation for hardware build quality; ecosystem is less modular than Ecowitt for add-on environmental sensors.
Product page: Davis Vantage Vue.
Tempest WeatherFlow
Tempest documents local UDP (commonly cited port 50222) and WebSocket APIs for local consumers. Home Assistant has a Tempest/WeatherFlow integration path used by many self-hosters.
Trade-off: All-in-one industrial design with limited modular soil/add-on expansion compared to Ecowitt.
Product page: Tempest Weather System.
Buyer checklist
- Define “local” — LAN push/pull only, or is cloud backup acceptable?
- Pick the gateway/console first — HA compatibility is often determined by the hub, not the outdoor array alone.
- Check HTTP vs HTTPS — Ecowitt local push requires HTTP reachability to Home Assistant.
- Plan Ethernet if Wi‑Fi is weak — see Ethernet guide.
- Confirm subscription policy — see no subscription guide.
- Read manufacturer docs — verify RF band (915 MHz US vs 868 MHz EU) and sensor compatibility for your region.
FAQs
See frontmatter FAQs above for structured answers. Always re-check Home Assistant and manufacturer documentation before purchase — integrations change across Home Assistant releases.
