Provider and sensor availability

A measurement passes through several availability checks before Weather Fusion displays it.

Provider access

The source must expose the field through the configured API, local endpoint, or public airport report. Account tier, authorization scope, retention, and request limits can affect real-time and historical access independently.

Station hardware or report content

A personal weather station must include the relevant sensor or module and transmit a usable value. Stations on the same provider can therefore have different measurement catalogs.

Airport (METAR) requires no personally owned hardware. Availability depends on the fields included in the airport report, and older archives can contain fewer measurements than current reports. A missing report field does not imply a sensor setup problem.

Data context

Real Time needs a current value. Historical 24h and Day need stored observations, while Week, Month, and Year commonly need compatible summaries. A measurement appears in each Historical period after enough compatible records have been stored and summarized for that range.

Weather Fusion also preserves each metric’s statistic and time window. A provider can expose today’s rain while another exposes rolling 24-hour rain, for example. Both belong to the Rain family, while their distinct metric identities keep the values correctly labeled and prevent one window from standing in for another.

Rain totals and rates on every surface come from one shared calculation over stored observations. Netatmo rain totals report today’s rainfall. Ecowitt stations with an ordinary and a piezoelectric rain gauge expose them as separate sources, and widgets show rain from the ordinary rain gauge.

Surface support

Cards, charts, map markers, tables, and widget families support different presentation forms. Direction can accompany wind speed in a widget, for example, while a historical wind-direction distribution requires enough valid speed and direction samples for a wind rose.

Sensor organization

For compatible providers, Automatic or Custom sensor groups determine where attributable measurements appear and in what order. Hiding or moving a measurement changes presentation while preserving the provider value and stored record.

When a value is missing, check source access, station hardware or report fields, observation time, selected period, and layout visibility first. These checks distinguish an availability condition from a data-repair problem.

See Supported measurements for the normalized catalog and the coverage of each view.