Quick answer
Best documented local-first stack: Ecowitt outdoor sensors + GW2000 or GW3000, integrated via Ecowitt’s official Home Assistant integration (HTTP pull from gateway) or Home Assistant’s built-in Ecowitt integration (HTTP push to HA).
Also viable locally:
- Tempest — local UDP broadcast documented by WeatherFlow.
- Davis WeatherLink Live — local UDP broadcast commonly used by integrations.
- Ambient Weather — Custom Server HTTP push with community Home Assistant integrations (more manual than Ecowitt).
“Local data” here means your automations can run if the internet drops, assuming LAN devices stay online.
Who this guide is for
- Privacy-conscious owners who want readings to stay on the home network.
- Home Assistant users — start with Home Assistant weather station guide.
- Buyers comparing Ecowitt vs Ambient local behavior — see comparison.
Pair with Ethernet guide if Wi‑Fi reliability is a concern.
Local vs cloud data paths
Sensors --RF--> Gateway/Console --LAN--> Home Assistant / local DB
|
+--> (optional) Manufacturer cloudCloud-only path: Home Assistant polls AmbientWeather.net or similar — simple setup, external dependency.
Local path: Gateway IP or UDP packet on LAN — better for uptime, latency, and privacy.
Local data options compared
| Brand | Local mechanism | Official HA integration | Notes |
|---|---|---|---|
| Ecowitt | HTTP API on GW2000/GW3000; HTTP push to HA | Yes (HACS + built-in) | Ecowitt publishes LAN API protocol docs |
| Ambient | Custom Server HTTP push | Cloud default; local via community | Verify firmware 4.2.8+ and console IP |
| Davis | WeatherLink Live UDP | WeatherLink integration ecosystem | Hardware cost higher |
| Tempest | UDP (documented port) | Tempest/WeatherFlow integration | All-in-one hub |
Ecowitt local HTTP
Ecowitt gateways expose local HTTP services used by the official integration. Home Assistant lists GW2000 and GW3000 as supported gateways with Local Push (built-in) or pull (official HACS).
Typical kit: Ecowitt WS90 + gateway — compare GW2000 vs GW3000.
Verify: Gateway firmware, HA integration version, and that Home Assistant accepts HTTP for push mode.
Ambient Custom Server
Ambient consoles can push to a custom server URL on your LAN (documented in Ambient firmware release notes for supported versions). Community projects (e.g. awnet_local, ha-ambient-local) receive that push into Home Assistant.
Caveats (based on community documentation):
- Not as turnkey as Ecowitt’s official integration.
- Console settings may need reapplication after reboot — some tools automate healing.
- Default Ambient HA integration remains cloud API.
Products: Ambient WS-5000, WS-2902.
Davis WeatherLink Live
WeatherLink Live bridges Davis RF stations to IP. Integrations commonly consume UDP broadcasts on the local subnet.
Product: Davis Vantage Vue.
Local operation does not require WeatherLink Cloud for LAN consumers, though cloud may still be used for mobile apps.
Tempest UDP
WeatherFlow documents local UDP output from the Tempest hub. Home Assistant users often configure the Tempest integration to prefer local packets.
Product: Tempest Weather System.
Trade-off vs Ecowitt: Less modular expansion; simpler single-unit install.
Buyer checklist
- Decide push vs pull — Ecowitt supports both patterns.
- Test LAN reachability — VLANs and guest Wi‑Fi can block hub ↔ HA traffic.
- Plan Ethernet for gateways in weak Wi‑Fi areas.
- Avoid subscription-dependent automations — no subscription guide.
- Document gateway IP and integration version for future you.
FAQs
See structured FAQs in metadata. Local integration steps change with Home Assistant releases — always cross-check current integration docs.
