# Supported weather stations

URL: https://pro-weather.com/docs/supported-hardware

> Model-by-model list of the weather stations Pro Weather works with, which ones connect by pasting a URL, and which need weewx, Meteobridge or CumulusMX in between.

Pro Weather works with most personal weather stations that can send data over
the internet. This page lists the models by brand and tells you which setup
path yours takes.

There are only three answers, and the table says which one applies to you:

| Path | What it means |
| --- | --- |
| **Native API connection** | Davis only. Paste a WeatherLink API key, nothing to configure on the station. |
| **Direct (paste a URL)** | Your firmware has a Customized or custom-server field. Copy two values in and you are done. |
| **Via weewx, Meteobridge or CumulusMX** | The firmware has no custom-server field, so a small piece of software relays the data. |

## Why one integration covers so many brands

Most consumer WiFi weather stations are built by **Fine Offset** and sold under
other names. They all run the same **EasyWeatherPro** firmware and are all
configured through the same **WS View** app, so they all expose the same
Customized upload with the same field names.

That is why Ecowitt, Froggit, Sainlogic, Eurochron and Ambient Weather stations
set up identically here: from our side they are one protocol. If your station
runs EasyWeatherPro or is configured through WS View, it will very likely work
even if the exact model is not in the table.

## What each path involves

### Native API connection: Davis Instruments

The deepest integration we have. Pro Weather reads your station through the
WeatherLink v2 API, auto-discovers every station and sensor on the account, and
backfills history. Nothing is configured on the station itself.

Full walkthrough: [Connect a WeatherLink station](https://pro-weather.com/docs/getting-started/connect-weatherlink).

### Direct: paste a URL into your station

For every EasyWeatherPro and WS View device. In the app, open your device →
**Weather Services** → **Customized**, then:

- **Customized:** Enable, protocol **Ecowitt**
- **Server IP / Hostname:** `i.pro-weather.com`
- **Path:** the short path from your dashboard, for example `/i/f3a91c…`
- **Port:** `80`
- **Upload interval:** 60 seconds

  The Customized upload in this firmware family speaks plain HTTP only and does
  not follow redirects, so `i.pro-weather.com` accepts plain HTTP on port 80 and
  forwards your readings over an encrypted connection from there. Pointing a
  gateway at `pro-weather.com` on port 443 will never work.

Full walkthrough: [Connect other hardware](https://pro-weather.com/docs/getting-started/connect-hardware).

### Via weewx, Meteobridge or CumulusMX

Some firmware only offers a fixed list of destinations (Weather Underground,
Weathercloud, AWEKAS) with no way to enter your own server. Bresser and Vevor
stations are the common examples.

For those, run **weewx**, **Meteobridge** or **CumulusMX** alongside the station
and point its Wunderground-protocol upload at your Pro Weather URL. This is also
the path for the long tail of older hardware: Oregon Scientific, La Crosse,
AcuRite, Hideki/TE923, Peet Bros, RainWise, Fine Offset USB models, SDR
receivers and one-wire sensors.

The configuration for each of those three programs is in
[Connect other hardware](https://pro-weather.com/docs/getting-started/connect-hardware).

> **A note on DNS redirect tricks**
>
  You may see advice to redirect `rtupdate.wunderground.com` to another server
  with Pi-hole or AdGuard so a locked-down station uploads somewhere else. It
  does work, but it silently breaks your real Weather Underground upload and
  every other device on the network that uses that hostname. We would rather you
  relay through weewx or Meteobridge, which is reversible and does not hijack
  anyone else's traffic.

## Which readings come through

Everything your hardware sends that we can recognise, in both Ecowitt and
Wunderground field naming:

| Reading | Notes |
| --- | --- |
| Temperature, humidity, dew point | Dew point is derived when the station does not send it |
| Pressure | Both sea-level and station (absolute) pressure |
| Wind speed, gusts, direction | Plus the derived wind chill and apparent temperature |
| Rain | Rate, event, hour, day, month and year totals; piezo gauges included |
| Solar radiation and UV | |
| Indoor temperature and humidity | From the console |
| PM1, PM2.5, PM10 | With AQI or EAQI banding |
| CO2 | From WH45 and WH46 modules, with their own temperature and humidity |
| Lightning | Strike count, distance and time of the last strike (WH57, DP60) |
| Extra temperature channels | Up to 8 WH31/WN31 room sensors |
| Soil moisture and soil temperature | Up to 8 channels each |
| Leaf wetness | Up to 8 channels |
| Evapotranspiration | When the station computes it |
| Battery status | Per-sensor low-battery flags are honoured |

> **Lightning and extra channels are live-only**
>
  Lightning and the extra temperature channels appear on your site's **Sensors**
  tab with current readings, but they are deliberately not written to the
  long-term archive, so they do not appear in historic charts. Everything else
  in the table above is archived and charted normally.

Anything your station does not send is simply absent; nothing is invented to
fill a gap.

## Not listed?

If your station's app has a Customized or custom-server option in Ecowitt or
Wunderground format, use the direct path above and it will very likely work. If
it does not, weewx supports a remarkably long list of hardware and is the
reliable fallback.