Signal VortexUser Documentation

Weather and the Weather Response Profile

Requires the site to have a location set and the tenant-wide "Enable weather data" setting on — see weather ingest. Without either, this box shows a quiet explanatory state instead of a chart.

Below the metric/range picker, the Environment screen always shows a third box: the site's weather, and — once there's enough history — how the space actually responds to it.

The weather box

  • Its own picker: Temperature, Precipitation, or Cloud Cover — independent of whatever metric you've picked above, and doesn't cost an extra request per metric, since one call already returns every field.
  • The same actual-solid / forecast-dashed / shaded-uncertainty-band pattern as the Occupancy Index chart, so the two read the same way at a glance.

Weather Response Profile

Below the weather box, for the currently selected space: a breakdown of how that space's occupancy and Wi-Fi client count tend to move under different weather conditions.

  • Below your workspace's configured minimum-weeks-of-history threshold, you'll just see one plain sentence — "not enough weather history yet…" — rather than a table full of asterisks and caveats.
  • Once past that threshold, results are grouped under section headings by condition — Rain, Clear & hot, Cold snap, Snow/ice — with one row per combination of day-of-week group and time of day.
  • Each row shows the effect on both the occupancy index and the Wi-Fi client count side by side, so you can see whether the two actually move together for a given condition or not.
  • Every computed effect is shown with its own sample count right next to it — there are no exceptions to this. A combination that hasn't accumulated enough observations yet shows its own "not enough data yet (N observations)" message and nothing else, rather than a number you'd have to second-guess.
  • You will not see a confidence chip or label attached to a number — a percentage next to a chip still reads as fact to most people, chip or not, so the honesty lives in the sample count instead.
  • The copy never implies there's a "normal" direction for any condition (e.g. that rain should obviously mean higher occupancy) — what actually happens is learned per site, never assumed, and stated as whatever the data shows for your space.

Why it matters

"Does bad weather actually change how busy this space gets, or how the Wi-Fi behaves?" is a real, useful question — but only if the answer is honest about how much data it's actually based on. This panel is built so a thin sliver of history reads as thin, not as a confident-looking (and possibly wrong) conclusion.