How Weather Fusion gets data

The weather station model identifies the physical hardware and sensors. Most stations first send observations to a separate connection service such as WeatherLink, Ecowitt Cloud, AmbientWeather.net, Weather Underground, or Windy. Weather Fusion authenticates with that service, retrieves the stations available to the account or configuration, and keeps a stable service-and-station identity for each local database.

WiFiLogger provides a local path for compatible Davis consoles: Weather Fusion contacts the logger directly over the local network. METAR and public-network markers remain transient map sources, separate from configured station history.

Current observations

The selected connection has its own automatic polling interval. A successful response is normalized into Weather Fusion measurements, giving cards, station details, maps, and widgets a consistent measurement catalog across services. The observation timestamp remains the source of truth for freshness.

Historical observations

Provider-specific policies determine the ranges, cadence, rate limits, and account checks used to retrieve history. Weather Fusion stores accepted observations in the selected station’s local .wfdb package. Historical and Observations then render from local storage as users move between screens.

Derived context

Weather Fusion combines provider readings with local summaries and, when coordinates are valid, sun, moon, and limited Apple Weather context. Derived values remain identified separately from provider-supplied physical-sensor readings; required inputs and attribution remain part of availability decisions.