Data as of Sep 26, 2026 · Based on 32 AI responses from ChatGPT Search and Google AI Mode · See how Parse measures this
Brands AI recommends here
Named in 100% of answers
Named in 91% of answers
Named in 75% of answers
Named in 28% of answers
Source | Citation share |
|---|---|
 Ambient Weather Station - Home Assistanthttps://www.home-assistant.io/integrations/ambient_station/ | 5% |
Ecowitt - Home Assistanthttps://www.home-assistant.io/integrations/ecowitt | 5% |
WeatherFlow - Home Assistanthttps://www.home-assistant.io/integrations/weatherflow | 4% |
Ambient Weather Station - Home Assistanthttps://www.home-assistant.io/integrations/ambient_station/ | 3% |
 Ecowitt Weather Quick Starthttps://www.ecowitt.com/api/quickstart/product | 3% |
Ecowitt - Home Assistanthttps://www.home-assistant.io/integrations/ecowitt/ | 3% |
WeatherFlow - Home Assistanthttps://www.home-assistant.io/integrations/weatherflow/ | 3% |
 Looking for best possible local weather station for homeassistant - Hardware - Home Assistant Communityhttps://community.home-assistant.io/t/looking-for-best-possible-local-weather-station-for-homeassistant/424352 | 2% |
Weather station... most compatible with ha? - Hardwarehttps://community.home-assistant.io/t/weather-station-most-compatible-with-ha/873489 | 2% |
Weather Station recomendation 2026 - Home Assistant Communityhttps://community.home-assistant.io/t/weather-station-recomendation-2026/1006194 | 2% |
Question: Which personal weather stations expose a documented API and support Home Assistant without a paid subscription?
ChatGPT SearchSep 20, 2026
Yes. If by “without a paid subscription” you mean you buy the hardware once and can get your own station data into Home Assistant without paying a recurring cloud fee, the strongest options are:
| Station ecosystem | Documented API | Home Assistant | Subscription required? | Local operation |
|---|---|---|---|---|
| Ecowitt | Yes — local HTTP API + cloud API | Official HA integration | No |
Question: Which personal weather stations expose a documented API and support Home Assistant without a paid subscription?
Google AI ModeSep 20, 2026
Question: Which personal weather stations expose a documented API and support Home Assistant without a paid subscription?
ChatGPT SearchSep 16, 2026
Question: Which personal weather stations expose a documented API and support Home Assistant without a paid subscription?
Google AI ModeSep 16, 2026
Question: Which personal weather stations expose a documented API and support Home Assistant without a paid subscription?
Google AI ModeSep 12, 2026
Question: Which personal weather stations expose a documented API and support Home Assistant without a paid subscription?
ChatGPT SearchSep 8, 2026
Question: Which personal weather stations expose a documented API and support Home Assistant without a paid subscription?
Google AI ModeSep 8, 2026
Question: Which personal weather stations expose a documented API and support Home Assistant without a paid subscription?
ChatGPT SearchSep 4, 2026
Question: Which personal weather stations expose a documented API and support Home Assistant without a paid subscription?
Google AI ModeSep 4, 2026
| WeatherFlow Tempest | Yes — REST + WebSocket + local UDP | Official HA integration | No for your own station | Yes |
| Ambient Weather | Yes — REST/JSON API | Official HA integration | No recurring fee for API access | Via Ecowitt-compatible/local methods on some models |
 Netatmo Weather Station | Yes — developer API | Official HA integration | No recurring fee | No — cloud dependent |
 Davis Instruments / WeatherLink | Yes — WeatherLink v2 API | HA support is possible, but the integration/API situation is more complicated | Depends on hardware/service | Depends on gateway |
Ecowitt is probably the clearest match if your priorities are documented API + Home Assistant + no subscription + local data.
Home Assistant has a first-party Ecowitt integration that uses a local HTTP callback. The station/gateway sends measurements directly to HA, so the cloud isn't required for the HA connection.
Ecowitt also documents its LAN HTTP API; its current documentation specifically lists an HTTP API protocol dated January 2026.
The important hardware is the gateway rather than simply the sensor array. Current HA-supported examples include:
Home AssistantBest fit if: you want Home Assistant to continue receiving weather data even if the vendor's cloud is unavailable.
The Tempest system has a particularly well-documented API. WeatherFlow provides REST and WebSocket APIs and personal access tokens for station owners.
More importantly for HA, Home Assistant has a local-only WeatherFlow integration that receives data directly from the Tempest device over UDP. HA and the station need to be on the same subnet.
WeatherFlow's current API policy explicitly says that station owners can access their own observations and forecasts for personal use without a special agreement or subscription.
So you can have:
Tempest → local network → Home Assistant
with no paid cloud subscription involved.
Best fit if: you want a polished consumer station with an unusually good developer API and native local HA support.
Ambient Weather exposes REST/JSON APIs for retrieving your station's real-time and historical data.
Home Assistant has an official Ambient Weather Station integration requiring an Application Key + API Key.
There is also a significant wrinkle: the normal HA integration is cloud-based, whereas some Ambient Weather hardware has an Ecowitt-compatible/local upload mechanism. HA itself recommends ecowitt2mqtt for users wanting a local option.
Best fit if: you like Ambient Weather hardware and don't mind using its cloud API, or select a model/gateway that can be integrated locally.
Netatmo has a documented developer API and Home Assistant has an official integration.
There's no indication of a paid subscription being necessary for the basic weather-station API/HA use. However, HA explicitly says its Netatmo integration communicates with Netatmo's cloud service and requires an internet connection and Netatmo account.
So it satisfies:
Davis's WeatherLink v2 API is documented and supports Davis stations uploading to WeatherLink.com. The API allows owners to access their own station data.
But Davis has historically had multiple generations of connectivity products and API arrangements, so “Davis” isn't a single subscription/API model. I'd verify the exact console/gateway before buying.
If you're buying specifically for Home Assistant and no recurring subscription, I'd narrow the field to:
One subtle distinction is worth emphasizing: “has an API” doesn't necessarily mean “has a free API,” and “works with Home Assistant” doesn't necessarily mean “works locally.” Ecowitt and Tempest are the two that most cleanly satisfy all three requirements.
If you tell me your budget and whether you care about rainfall, lightning, air quality, or soil moisture, I can narrow this to specific current models and compare their sensors/API/local behavior.
Best fit if: you want a polished consumer station with an unusually good developer API and native local HA support.
Ambient Weather exposes REST/JSON APIs for retrieving your station's real-time and historical data.
Home Assistant has an official Ambient Weather Station integration requiring an Application Key + API Key.
There is also a significant wrinkle: the normal HA integration is cloud-based, whereas some Ambient Weather hardware has an Ecowitt-compatible/local upload mechanism. HA itself recommends ecowitt2mqtt for users wanting a local option.
Best fit if: you like Ambient Weather hardware and don't mind using its cloud API, or select a model/gateway that can be integrated locally.
Netatmo has a documented developer API and Home Assistant has an official integration.
There's no indication of a paid subscription being necessary for the basic weather-station API/HA use. However, HA explicitly says its Netatmo integration communicates with Netatmo's cloud service and requires an internet connection and Netatmo account.
Several top-tier personal weather stations (PWS) offer robust, documented local APIs or native integrations that connect directly to Home Assistant completely free of charge, requiring zero subscriptions or cloud dependency.
Ecowitt (e.g., GW2002, GW3002, HP2551, or standalone gateways)Davis Instruments (e.g., Vantage Pro2 or Vantage Vue with WeatherLink Live / WeatherLink Console)Would you like to narrow down these options based on your budget, mounting preferences (all-in-one vs. separate sensors), or local vs. Wi-Fi connection constraints?
The strongest choices are stations with local LAN APIs or documented local protocols (no vendor cloud subscription required):
| Station ecosystem | API / protocol | Home Assistant support | Subscription needed? |
|---|---|---|---|
| Ecowitt (GW1000/GW1100/GW1200/GW2000/GW3000 gateways + sensors) | Local HTTP API, Ecowitt protocol, custom server push | Official HA integration | No |
| WeatherFlow Tempest | Local UDP API; documented cloud API also available | Official HA integration (local) | No for local use |
| Ambient Weather WS-series (WS-2902, WS-5000, etc.) | API available; some consoles support custom server/local push methods | Official HA integrations | No, but many setups are cloud-oriented |
| Davis Vantage systems | WeatherLink APIs; some local options depend on gateway/console | HA integrations/custom setups | Local options vary |
Best fits for a subscription-free, local-first Home Assistant setup:
Avoid buying a station that only says “works with our app” unless it documents one of:
For a new purchase focused on Home Assistant, I would shortlist Ecowitt GW2000/GW3000 and WeatherFlow Tempest.
Several personal weather stations (PWS) offer documented or native local APIs and integrate with Home Assistant completely free of charge and without any paid subscription.
The top options that fit your criteria include:
Ecowitt (Gateways / Sensor Arrays)
ecowitt2mqtt in ambient mode or HACS local workarounds), you can harvest data locally.AWN+ ) for extra features, the standard API and Home Assistant cloud/local polling integrations work entirely under the free tier. (Note: If strict 100% local operation without any cloud dependency is your goal, Ecowitt or WeatherFlow are smoother choices than Ambient).[2]Would you like to compare the sensor ecosystem and pricing between Ecowitt and WeatherFlow Tempest?
Yes. If by “no paid subscription” you mean the station should expose a documented API that you can use without paying a recurring fee, and there should be a reasonably straightforward Home Assistant path, the strongest options are:
| Station/platform | Documented API | HA support | Subscription needed? | Best for |
|---|---|---|---|---|
| Ecowitt (GW2000/GW3000 + sensors) | Yes — local HTTP API | Built-in Ecowitt integration | No | Best value / local-first |
| WeatherFlow Tempest | Yes — REST, WebSocket, local UDP | Built-in local integration | No | Best polished modern system |
| Davis WeatherLink Live | Yes — documented local HTTP/UDP API | Custom/HACS integrations | No for local API | Best high-end/pro-grade hardware |
| Ambient Weather | Yes — cloud API + local options | Built-in HA integration | No separate API subscription | Good hardware selection |
Ecowitt is probably the cleanest answer if your priorities are documented API + Home Assistant + no recurring fee + local operation.
Ecowitt documents an HTTP API interface for the LAN, and current Ecowitt documentation explicitly provides a Home Assistant integration. Home Assistant also has a native Ecowitt integration.
The architecture is essentially:
Outdoor sensors → Ecowitt gateway → HTTP → Home Assistant
That means your weather data doesn't have to leave your network.
Good combinations include a GW2000/GW3000 gateway with the sensor suite you want. You can build a fairly elaborate station—temperature/humidity, wind, rain, UV, solar radiation, soil moisture, air quality, etc.—without tying the basic functionality to a cloud subscription.
WeatherFlow's Tempest is another excellent choice.
The Tempest API is unusually well documented: WeatherFlow provides REST and WebSocket APIs, and also documents the local UDP interface.
Even better for Home Assistant, the official integration is local-only and reads the Tempest directly over UDP. Home Assistant explicitly describes it as a local-push integration; the HA server and Tempest need to be on the same subnet.
So you can use:
Tempest → local UDP → Home Assistant
with no API subscription.
The cloud API is also available if you want forecasts/history/cloud-derived data, but it isn't necessary for basic local station telemetry.
The WeatherLink Live has a documented local HTTP API that returns current weather as JSON and a local UDP real-time feed. Davis explicitly documents both interfaces.
That is important because you don't need the WeatherLink cloud service just to get data into your own system.
There are Home Assistant custom integrations supporting WeatherLink Live/local polling.
The catch is that Davis's cloud WeatherLink v2 API has subscription-dependent data permissions. The documentation distinguishes Basic, Pro and Pro+ access, particularly for historical data.
So I'd specifically choose WeatherLink Live + local API, rather than designing the system around the cloud API.
Ambient Weather has a documented cloud API and a native Home Assistant integration. HA requires an Application Key and API Key for the owner-station integration.
There is also a local route: Home Assistant documents using ecowitt2mqtt with Ambient Weather devices for local operation.
So it can absolutely satisfy the no paid subscription requirement, but its HA story is somewhat less clean than Ecowitt's native local integration or Tempest's native local UDP integration.
If I were buying specifically for Home Assistant + documented API + no recurring subscription, I'd shortlist:
One important distinction: “has an API” doesn't necessarily mean “API is free.” Davis's WeatherLink cloud API, for example, has subscription-dependent permissions, while its local WeatherLink Live API doesn't have that recurring-cloud-service dependency.
If you tell me your budget and which sensors you care about (rain, wind, UV, lightning, soil moisture, indoor CO₂, etc.), I can narrow this to the 2–3 actual station models I'd buy for Home Assistant.
The architecture is essentially:
Outdoor sensors → Ecowitt gateway → HTTP → Home Assistant
That means your weather data doesn't have to leave your network.
Good combinations include a GW2000/GW3000 gateway with the sensor suite you want. You can build a fairly elaborate station—temperature/humidity, wind, rain, UV, solar radiation, soil moisture, air quality, etc.—without tying the basic functionality to a cloud subscription.
WeatherFlow's Tempest is another excellent choice.
The Tempest API is unusually well documented: WeatherFlow provides REST and WebSocket APIs, and also documents the local UDP interface.
Even better for Home Assistant, the official integration is local-only and reads the Tempest directly over UDP. Home Assistant explicitly describes it as a local-push integration; the HA server and Tempest need to be on the same subnet.
So you can use:
Tempest → local UDP → Home Assistant
with no API subscription.
The cloud API is also available if you want forecasts/history/cloud-derived data, but it isn't necessary for basic local station telemetry.
Davis Instruments is worth considering if you want something more professional.
The WeatherLink Live has a documented local HTTP API that returns current weather as JSON and a local UDP real-time feed. Davis explicitly documents both interfaces.
That is important because you don't need the WeatherLink cloud service just to get data into your own system.
There are Home Assistant custom integrations supporting WeatherLink Live/local polling.
The catch is that Davis's cloud WeatherLink v2 API has subscription-dependent data permissions. The documentation distinguishes Basic, Pro and Pro+ access, particularly for historical data.
So I'd specifically choose WeatherLink Live + local API, rather than designing the system around the cloud API.
Ambient Weather has a documented cloud API and a native Home Assistant integration. HA requires an Application Key and API Key for the owner-station integration.
There is also a local route: Home Assistant documents using ecowitt2mqtt with Ambient Weather devices for local operation.
So it can absolutely satisfy the no paid subscription requirement, but its HA story is somewhat less clean than Ecowitt's native local integration or Tempest's native local UDP integration.
If I were buying specifically for Home Assistant + documented API + no recurring subscription, I'd shortlist:
Several personal weather stations (PWS) offer documented local or push APIs and integrate smoothly with Home Assistant completely free, requiring no cloud subscription or paid tiers.
The top options that meet these criteria include:
Ecowitt (Gateways like GW1000, GW1100, GW2000, GW3000) : Ecowitt is widely considered the gold standard for local smart home integration. Their Wi-Fi gateways feature a built-in local HTTP API and custom server configuration. The official Home Assistant Ecowitt Integration acts as a local receiver endpoint; you simply point your Ecowitt gateway (via their mobile app) to push data directly to your Home Assistant IP on your local network. It is entirely local, fast, and free.Davis Instruments (WeatherLink Live / Console) : Davis professional-grade stations have a documented local API available when the datalogger/gateway is on your local network. While the official out-of-the-box cloud link has historical limitations, community-maintained local integrations via HACS (such as the Davis WeatherLink Live Integration ) poll the device locally over your LAN to expose dozens of sensor metrics completely cloud-free.Would you like help setting up the local push configuration for Ecowitt or finding the right HACS repository for Davis/WeatherFlow?
Yes. If your requirements are (1) a documented API/protocol, (2) a real PWS rather than just forecast data, (3) native or straightforward Home Assistant support, and (4) no recurring subscription, the shortlist is fairly small.
| Station ecosystem | Documented API/protocol | Home Assistant | Subscription required? | My take |
|---|---|---|---|---|
| Ecowitt | Yes — local HTTP API + cloud API | Native, local push | No | ⭐ Best overall |
| WeatherFlow Tempest | Yes — local UDP + cloud REST API | Native, local | No | ⭐ Best premium option |
| Ambient Weather | Yes — REST API | Native, but cloud-based | No for normal station access | ⭐ Good if you prefer conventional sensors |
| Davis Instruments | Yes — WeatherLink API | Community/native options vary by hardware | Depends on hardware/API path | Excellent hardware, more complicated |
| AcuRite / La Crosse | Limited/closed or third-party approaches | Possible via workarounds | Often service-dependent | I wouldn't choose them for an API-first HA setup |
Ecowitt is probably the best fit if Home Assistant + no cloud subscription + open/local integration is your priority.
Home Assistant's official Ecowitt integration receives data directly from the gateway over your LAN. It supports gateways such as the GW1200, GW2000 and GW3000 and exposes temperature, humidity, pressure, wind, rain, lightning, soil moisture, air quality and other sensors depending on what you've connected.
Even better, Ecowitt publishes a documented HTTP LAN API and continues to publish its API documentation; its current documentation lists the HTTP API protocol as of January 2026.
Why I'd buy it:
Particularly interesting: a gateway + WS90/WS80/etc. sensor combination lets you choose the exact sensors you need rather than replacing an entire station.
WeatherFlow's Tempest is another excellent choice.
Home Assistant has an official local WeatherFlow integration that communicates directly with the Tempest system using UDP. It doesn't require the cloud and requires HA and the station to be on the same subnet.
That gives you a particularly nice architecture:
Tempest → local network → Home Assistant
rather than:
Tempest → vendor cloud → Home Assistant
The cloud API is also documented and available, but you don't need it for basic HA sensor integration. Home Assistant exposes temperature, humidity, pressure, wind, rain, UV/solar radiation, lightning and other measurements.
Downside: Tempest is substantially more expensive than the Ecowitt ecosystem, and the sensor philosophy is different—it is a very compact, largely sensor-less-looking unit rather than a traditional weather station with lots of replaceable probes.
Ambient Weather also checks the boxes surprisingly well.
Ambient Weather publishes RESTful APIs for retrieving real-time and historical PWS data, and users can generate their own API key from their Ambient Weather Network account. The vendor documents rate limits and the API itself.
Home Assistant has an official Ambient Weather Station integration. The catch is that it communicates through the Ambient Weather cloud rather than directly with the station.
There is also an interesting distinction: Home Assistant's Ambient Weather Network integration can read public station data without an API key, although with reduced sensor data.
For your own station, though, I'd use the normal Ambient Weather integration/API.
If I were buying specifically for Home Assistant + API + no subscription, I'd rank them:
One important distinction: "has an API" doesn't necessarily mean "the API is free." For example, Davis's WeatherLink API is documented and uses API tokens, but the exact availability/limitations depend on the WeatherLink hardware/account arrangement.
If you tell me your budget (e.g. <$200, <$400, <$600) and whether you want rain + wind + lightning + indoor sensors, I can narrow this down to 3–5 specific stations/gateway combinations that are particularly good for Home Assistant.
That gives you a particularly nice architecture:
Tempest → local network → Home Assistant
rather than:
Tempest → vendor cloud → Home Assistant
The cloud API is also documented and available, but you don't need it for basic HA sensor integration. Home Assistant exposes temperature, humidity, pressure, wind, rain, UV/solar radiation, lightning and other measurements.
Downside: Tempest is substantially more expensive than the Ecowitt ecosystem, and the sensor philosophy is different—it is a very compact, largely sensor-less-looking unit rather than a traditional weather station with lots of replaceable probes.
Ambient Weather also checks the boxes surprisingly well.
Ambient Weather publishes RESTful APIs for retrieving real-time and historical PWS data, and users can generate their own API key from their Ambient Weather Network account. The vendor documents rate limits and the API itself.
Home Assistant has an official Ambient Weather Station integration. The catch is that it communicates through the Ambient Weather cloud rather than directly with the station.
There is also an interesting distinction: Home Assistant's Ambient Weather Network integration can read public station data without an API key, although with reduced sensor data.
For your own station, though, I'd use the normal Ambient Weather integration/API.
If I were buying specifically for Home Assistant + API + no subscription, I'd rank them:
Several reliable personal weather stations (PWS) offer documented APIs, local push/pull capabilities, and seamless, subscription-free integration into Home Assistant.
The top options that do not require paying a monthly cloud fee for local or direct data access include:
Ecowitt Stations (e.g., HP2551, GW1100, GW2000 gateways) : Ecowitt is widely considered the gold standard for local smart home integration. Their gateways feature a built-in local web interface and natively support custom server configurations. The core Ecowitt Integration in Home Assistant works completely locally by having the hardware push data directly to your Home Assistant IP over your local network—no cloud connection or subscription required.Davis Instruments (Vantage Pro2 / Vantage Vue with WeatherLink Console or WeatherLink Live) : Davis professional-grade stations feature a fully documented local API (v1/current_conditions ) accessible via your local network IP when connected to a WeatherLink IP/Wi-Fi console or WeatherLink Live device. The community and core-supported WeatherLink integration queries this local endpoint completely bypassing any paid WeatherLink tier requirements.ecowitt2mqtt or custom interceptors. However, if you want a seamless native out-of-the-box local experience without extra bridging tools, Ecowitt or Tempest are much smoother choices.If you'd like, let me know:
I can help you choose the best specific model for your setup.
Yes. If your requirements are (1) a real, documented API, (2) Home Assistant support, and (3) no recurring subscription, the shortlist is actually fairly good.
| System | API | Home Assistant | Subscription needed? | My take |
|---|---|---|---|---|
| Ecowitt | Yes — local HTTP API + cloud API | Official integration | No | ⭐ Best overall |
| WeatherFlow Tempest | Yes — REST + WebSocket + local UDP | Official local integration | No for your own station | ⭐ Best premium option |
| Ambient Weather | Yes — documented REST API | Official integration | No | ⭐ Good, but cloud-dependent |
| Davis Instruments | Yes — WeatherLink v2 + local APIs on some hardware | Community/HACS options | Not necessarily | Excellent hardware, more complicated |
Ecowitt is unusually friendly to Home Assistant.
Current Ecowitt gateways such as the GW1200/GW2000/GW3000 have a documented local HTTP protocol, and Home Assistant has an official Ecowitt integration that uses local push rather than a cloud service.
Ecowitt's documentation currently explicitly provides both an HTTP API interface for LAN and an API for its cloud service.
The important bit: the local Home Assistant integration doesn't require a paid cloud subscription. Your gateway sends measurements directly to HA.
Good families to look at include:
Home Assistant supports temperature, humidity, pressure, wind, rain, lightning, soil moisture, PM sensors, CO₂ and more depending on the attached sensors.
Verdict: If you're building a new HA installation and want to avoid vendor lock-in, I'd start here.
WeatherFlow's Tempest has a properly documented REST and WebSocket API. You can create a personal access token and access your own station's observations.
Even better for Home Assistant, HA has an official local WeatherFlow integration that communicates directly with Tempest over UDP. It doesn't require the cloud API at all.
WeatherFlow explicitly permits owners to access their own station's observation and forecast data for personal use without a paid subscription.
The Tempest is particularly attractive if you want:
Verdict: Best premium/modern choice, especially if you're willing to pay more up front for the hardware.
Ambient Weather has a documented REST API requiring an Application Key and Device/API Key.
Home Assistant has an official Ambient Weather Station integration using that API.
Popular stations include the WS-2902, WS-2000, and WS-5000 families. Ambient specifically advertises Home Assistant compatibility and its API on the WS-2902 product page.
The distinction from Ecowitt/Tempest is important:
Ambient Weather's official HA integration goes through Ambient Weather's cloud.
You don't need the paid AWN+ subscription just to use the station/API, but you are dependent on the free Ambient Weather service. Ambient also documents local protocols for some hardware, and HA notes that ecowitt2mqtt can provide a local option.
Verdict: Good choice, particularly if you like the Ambient hardware, but Ecowitt is cleaner if "local-first" is the priority.
Davis Instruments is the interesting case.
The WeatherLink v2 API is documented and supports Davis stations connected to WeatherLink.com. The API has a default limit of 1,000 calls/hour, which is plenty for typical HA polling.
However, Davis's current API has subscription-dependent data permissions. For example, Basic access can provide current WeatherLink Live/Console data at 15-minute intervals but doesn't provide historical data.
The way around that is local access. WeatherLink Live has a documented local API, and community HA integrations can poll it directly.
So Davis can absolutely be subscription-free, but you need to choose the hardware/logger carefully.
Verdict: Fantastic if you prioritize measurement quality and durability, but it's not as plug-and-play for HA as Ecowitt or Tempest.
If I were optimizing specifically for Home Assistant + documented API + no subscription, I'd rank them:
One particularly important distinction: "has an API" isn't enough. I'd favor stations where the API is local and documented, because then a vendor changing its cloud service, API limits, or subscription structure can't break your Home Assistant installation. On that criterion, Ecowitt and Tempest stand out.
If you tell me your approximate budget (e.g. <$200, $200–400, $400+) and whether you want rain + wind + UV + lightning, I can narrow this to the 2–3 specific station kits I'd buy today, including their HA integration method.
Home Assistant has an official Ambient Weather Station integration using that API.
Popular stations include the WS-2902, WS-2000, and WS-5000 families. Ambient specifically advertises Home Assistant compatibility and its API on the WS-2902 product page.
The distinction from Ecowitt/Tempest is important:
Ambient Weather's official HA integration goes through Ambient Weather's cloud.
You don't need the paid AWN+ subscription just to use the station/API, but you are dependent on the free Ambient Weather service. Ambient also documents local protocols for some hardware, and HA notes that ecowitt2mqtt can provide a local option.
Verdict: Good choice, particularly if you like the Ambient hardware, but Ecowitt is cleaner if "local-first" is the priority.
Davis Instruments is the interesting case.
The WeatherLink v2 API is documented and supports Davis stations connected to WeatherLink.com. The API has a default limit of 1,000 calls/hour, which is plenty for typical HA polling.
However, Davis's current API has subscription-dependent data permissions. For example, Basic access can provide current WeatherLink Live/Console data at 15-minute intervals but doesn't provide historical data.
The way around that is local access. WeatherLink Live has a documented local API, and community HA integrations can poll it directly.
So Davis can absolutely be subscription-free, but you need to choose the hardware/logger carefully.
Verdict: Fantastic if you prioritize measurement quality and durability, but it's not as plug-and-play for HA as Ecowitt or Tempest.
Several popular personal weather stations (PWS) offer documented APIs, local push/pull capability, and native or custom Home Assistant integration without requiring any paid subscriptions.
The best options feature robust local or free cloud integrations:
Ecowitt (Wittboy, GW1000/GW2000 gateways)
Ambient Weather
Davis Instruments (Vantage Vue / Vantage Pro2 with WeatherLink IP or Logger)
If you are deciding between these, let me know:
