Environment Settings
The Environment tab in Settings controls how occupancy is calculated tenant-wide, and is where you manage the spaces your sensors are grouped into.
Occupancy inference
- An "Enable occupancy inference" toggle. Off by default until you're ready to use it — see Occupancy Index for what turning it on unlocks.
- Four weight fields — VOC, absolute humidity, temperature, and Wi-Fi client count — controlling how much each signal contributes to the blended occupancy index. They must sum to exactly 1.00; the Save button is blocked with a live running total until they do (the server independently re-checks this too, so there's no way to save an invalid combination even by working around the UI).
- An environmental sample interval — how often readings are taken, from 5 minutes (the default and the minimum) up to 1 hour. Five minutes is the shortest interval at which the sensor's gas element gives a stable reading rather than noise, so shorter values are refused. A change applies to every sensor with an environmental sensor fitted straight away — no restart needed.
Space Management
Below the occupancy settings: the full registry of spaces for your tenant.
- Rename, retire, or merge a space into another one.
- Every sensor bound to a space gets its own row with a fixed / roaming placement-mode toggle — "fixed" means the sensor is expected to stay put (so a signal-pattern drift is worth flagging); "roaming" means it's expected to move around, so drift is normal.
- If a sensor's signal pattern suggests it's moved, a relocation banner appears, worded differently depending on what happened: a warning for a fixed sensor that moved unexpectedly, or a lower-key note for a roaming sensor that's been matched to (or newly registered at) a new position. Dismissing a banner is remembered on this device/browser — there's no separate server-side record of having seen it, so it can reappear if you check from somewhere else.
- Each space has an optional window facing selector (the 8 compass points, or "Not set") — this sharpens the sun's warming effect to that specific room instead of applying a whole-site assumption. It's unset by default and never required.
Why it matters
Occupancy inference is a blend of several imperfect signals, not a direct headcount sensor — being able to see and tune the weights (rather than trusting an opaque black box) is what makes the result trustworthy enough to act on. Space Management is the other half of that: the index is only as good as knowing which sensor covers which room, and whether it's actually still where you think it is.