Connection service capabilities

Connection service capabilities

Compare authentication, automatic refresh intervals, historical behavior, and station discovery across supported connection services and local loggers. See Supported weather stations for models grouped by connection service.

Connection service or pathAuthenticationAutomatic real-time intervalHistorical behaviorStation discovery
Davis WeatherLinkAPI Key v2 and API Secret1 minuteRange-based history; historical access can require a WeatherLink subscriptionAccount stations
Netatmo account serviceAccount authorization10 minutesService ranges processed into local observations and summariesPersonal account stations; Netatmo Network on the map
Ecowitt CloudApplication Key and API Key1 minuteService cadence tiers across older rangesAccount devices and stations
AmbientWeather.netAPI Key1 minuteDevice history downloaded in bounded pagesAccount devices
AcuRite through Weather UndergroundWeather Underground sharing and credentials10 minutesUses Weather Underground data and history behaviorShared Weather Underground station
WiFiLogger for Davis consolesLocal-network endpoint30 secondsReads supported Davis station archive data; requires local reachabilityLocal-network discovery or manual endpoint
Weather UndergroundAPI Key and Station ID10 minutes for the selected stationRecent and hourly historical requests subject to provider limitsConfigured IDs and public-station discovery
WindyAPI key5 minutesRecent seven-day historical windowAccount stations and public-station discovery

Service and account limits

  • Polling intervals describe Weather Fusion’s selected-station schedule. The provider can still return an older observation.
  • Historical depth varies independently from real-time access. Account tier, station registration date, provider retention, and rate limits can reduce coverage.
  • Sensor coverage follows fields returned for the selected station. Two stations using the same provider can expose different cards, charts, and widget choices.
  • Public-network and METAR markers remain discovery sources, separate from personal stations and local history.
  • WiFiLogger requires local-network access whenever Weather Fusion needs to contact the logger.

Provider incidents and retry limits can temporarily pause requests while preserving saved configuration.