How SenseStack decides if an asset is Ready
The six operational states, how telemetry maps into them, and why an asset never flips instantly from Ready to Idle.
Every sauna, plunge, steam room and wellness space in SenseStack resolves to one of six operational states. The state is computed on the backend from live telemetry — you never have to interpret a raw number to know whether an asset is ready.
| State | What it means |
|---|---|
| Ready | Inside target band and stable. Safe to hand to a guest. |
| Preparing | Warming up (sauna/steam) or chilling down (plunge) toward target. |
| Recovering | Just came out of Ready and hasn't stabilised yet. Grace window. |
| Idle | Off-duty, out of hours, or unused for long enough to be considered dormant. |
| Attention | Drifted outside acceptable range or behaviour needs a human. |
| Offline | Device hasn't reported recently. Network or power issue. |
Per-asset language
The six states are universal, but the label your team sees adapts to the asset. Saunas show "Heating" instead of "Preparing", plunges show "Chilling", steam rooms show "Building Steam", ventilation shows "Ventilating" or "Air OK", filtration shows "Circulating" or "Water OK". Same engine, familiar words.
The grace window
When an asset leaves Ready — a door opens, a session ends, temperature dips — it doesn't drop straight to Idle. It enters Recovering for a configurable window (per asset type). This prevents the dashboard from flickering between states and gives staff a truthful "just used" signal.
Rule of thumb: if the dashboard is green (Ready), your team can hand the space over. If it's yellow (Preparing/Recovering) it's on its way. If it's orange (Attention) or grey (Offline) someone needs to look.
What's NOT inferred from telemetry
Maintenance, Cleaning, Closed, Reserved and Private Session are manual overlays — staff set them, the system respects them. SenseStack never guesses these from sensor patterns.