Atmos Console

01Setup

On first launch, a six-step onboarding sequence introduces the console, then configures it:

1. Tempest Station Telemetry — the app listens on your local network for your station's UDP broadcast automatically; if you want cloud history and backfill too, add a WeatherFlow personal access token, which is verified in-app before you continue.
2. Station Location — a label only: a name shown on the dashboard next to your station ID, set by GPS or typed in manually. It doesn't drive any weather logic by itself.
3. Units & Display — temperature, wind speed, rain rate, pressure, and lightning distance units, plus display options.
4. Data History & Privacy — a short note confirming observations are stored locally on the iPad; nothing changes on Tempest's or WeatherFlow's side.
5. Completion summary — a recap of what was configured. This step also requires checking a life-safety acknowledgment (Atmos Console is an informational dashboard, not a certified weather-warning service — for official watches and warnings, consult the National Weather Service) before the Continue button unlocks and the dashboard opens.

02The Dashboard

The dashboard is a single fixed screen — nothing scrolls, so it's safe to leave running on a 24/7 wall display. Atmos Console is built for iPad only.

Along the bottom, the event strip carries connection status, station/hub signal, storage size, and a feedback link — see Connection Status.

03Wind Card

The compass rose shows live wind direction; the column beside it reads current speed, gust, and the direction the gust came from. Below that, a Peak Gust block shows one range bar per day — today plus the six previous calendar days — each bar spanning that day's wind speeds on a shared color scale so you can compare magnitude across the week at a glance.

04Telemetry Strips

Six scrolling strips share the chosen time range: solar, temperature (with dew point), pressure, humidity, wind, and rain. A few things worth knowing:

• The temperature strip annotates the day's low and high; nearby overnight lows are merged into a single pair of annotations so labels don't collide.
• Gaps in coverage over five minutes are shown as a dashed, low-opacity band — this is diagnostic, not an error. Gaps bridged by history backfill are not marked, since that data has been repaired.
• Turn on Sync Cursor (Settings → Display) to scrub one strip and see a matching cursor and unified readout across all of them.
• The wind strip can be drawn as a meteogram (colored trace, default) or traditional barbs — also in Settings → Display.
• Tap the expand control on the Conditions panel to open a full-screen view where you can choose which strips are visible.

05Conditions

This panel lists what's currently happening and any recognized weather pattern, each as one line — a colored dot, then title and detail, with how long ago it started or ended on the right.

Text is templated from your station's own readings — the app does not generate free-text narration. Tap a lightning row for a detail view with strike counts, distance, and timeline. If regional phenomena are enabled and your coastal bearing is set, sea-breeze and land-breeze rows can appear here too.

06Connection Status

The bottom event strip reflects how your station is being heard. Atmos Console prefers your station's local UDP broadcast and falls back to the WeatherFlow cloud API when needed.

Tap the source/telemetry text (e.g. "UDP TELEMETRY NOMINAL") in the event strip for a popover explaining the active source and its update cadence. Station and hub signal strength (dBm) and battery voltage appear as separate fields in the event strip when available, not in the popover.

07Settings

Settings is organized by section:

• Units — temperature, wind, rain, pressure, and lightning distance.
• Connection — your WeatherFlow token, station, and location.
• Display — Keep Screen Awake, burn-in protection, sync cursor, wind strip style, and clock format (12/24-hour, local/UTC).
• Detection — the Regional Phenomena toggle and coastal bearing (sea breeze / land breeze) configuration.
• Notifications — alert notifications on/off.
• Data — history retention, CSV export, and a clearly-marked reset for local history.
• Demo, Feedback, Diagnostics — a lightning simulation for trying that panel without waiting for a real strike, a feedback/report sheet, and raw diagnostics detail.

08Data & History

Observation history is stored locally on-device, independent of retention on WeatherFlow's own cloud service.

• Retention: 90 days, 1 year (default), 2 years, or indefinitely.
• Export: save your history to CSV for analysis elsewhere.
• Reset: a destructive action with a confirmation step. It only clears the local copy — your data on WeatherFlow's servers is untouched.
• Backfill: if local history is empty and your API token is connected, the app will offer a one-time import of available cloud history so charts and wind history aren't starting from zero.

09Tips

• Leaving the console running 24/7 is expected — that's what the layout and burn-in protection are built for.
• If a reading looks frozen, check the event strip first: wind-only telemetry and STALE both explain a stalled non-wind value without anything being wrong with the station.
• Weak signal is usually an RSSI or distance issue between the station and your hub, not an app problem — the source popover in the event strip shows current signal strength.