What’s the Difference Between a Zone and a Room in Butlr?

Rang Luo

Updated July 30, 2026 00:07

Overview

When setting up Butlr sensors, it's essential to understand the difference — and overlap — between Zones and Rooms. Though both can be used for presence detection, they function differently within the Butlr Dashboard and API.

Despite their names, Zones and Rooms are not hierarchical for data purposes — neither contains the other, and each has its own occupancy calculation. They are separate, parallel objects in our spatial model, each serving distinct purposes. For a deeper look at Butlr's spatial data structure, see our Data Model Hierarchy.

What is a Room?

A Room represents a real-world, enclosed space such as an office, conference room, or bedroom. It's the main spatial unit where sensors are assigned and data is aggregated.

Key behaviors:

Each sensor can belong to only one Room.
Both Presence Mode and Traffic Mode sensors report to the Room they're assigned to.
Room boundaries do not crop the sensor's field of view (FOV). As long as the sensor's center is inside the Room, the entire FOV contributes to that Room's occupancy data.

What is a Zone?

A Zone is a virtual area used to segment larger spaces for more detailed monitoring — for example, a group of desks, a seating area, or an entry zone.

Key behaviors:

Sensors are not assigned to Zones. Zone data comes from the overlapping area between the Zone boundary and the sensor's FOV.
Zone boundaries can crop sensor coverage — only detections inside the Zone count toward Zone data.
Zones can overlap to represent multi-purpose or composite areas (e.g., team clusters, activity zones).
Only Presence Mode sensors contribute to Zone data; Traffic Mode sensor data is ignored at the Zone level.

Use Zones when you want:

Fine-grained detection within part of a sensor's view (e.g., a single desk or seating area).
Overlapping regions to group or compare multiple areas (e.g., department clusters, meeting zones).

Key Differences at a Glance

Feature	Room	Zone
Purpose	Represents a real physical space (e.g., office, meeting room, bedroom).	Virtual area for detailed monitoring within a space.
Sensor Assignment	Each sensor is assigned to one Room.	Sensors are not assigned; data depends on overlap with the sensor’s FOV.
Boundary Behavior	Does not crop the sensor’s FOV — the full coverage counts if the sensor’s center is inside the Room.	Can crop the sensor’s FOV — only detections within the Zone boundary are counted.
Overlap	Rooms should not overlap.	Zones can overlap to represent combined or shared areas.
Supported Modes	Works with both Presence and Traffic sensors.	Works with Presence sensors only.
Data Use	Provides room-level occupancy and traffic data.	Provides fine-grained activity data within part of a space.

How Zones Are Organized in the Sidebar

Zones and Rooms are independent for occupancy and traffic data — but the Dashboard's left-hand navigation still has to decide where to list each Zone. Butlr assigns this automatically based on the Zone's geometry relative to nearby Rooms:

A Zone can be listed nested under a Room, or directly under its Floor.
This is decided automatically and re-evaluated whenever a Zone or a nearby Room is moved or resized — it isn't something you set directly.

It exists purely to organize the navigation tree. It has no effect on occupancy data, sensor assignment, or how Zone and Room boundaries interact.

Why this matters

Because this placement is automatic, it can land somewhere you don't expect — especially for a Zone that's meant to span several Rooms or a larger area, like a shared collaboration space laid over multiple smaller rooms. It can even change on its own after resizing a nearby Room, without the Zone itself moving at all.

If you want a Zone to always appear directly under its Floor, regardless of automatic placement, turn on Show at floor level in that Zone's settings. See How to Pin a Zone to Floor Level in the Sidebar for the steps.

Common Misconceptions

“Zones must belong to a Room” → Not exactly — you never assign a Zone to a Room directly, and Zone data is calculated independently of Room data. But Butlr does automatically decide a Zone's Room association based on geometry, purely to organize the sidebar. See How Zones Are Organized in the Sidebar, above.
“Room borders crop the sensor’s FOV” → False. The whole FOV contributes if the sensor’s center is within the Room.
“Traffic Mode works with Zones” → False. Zone-level data ignores Traffic Mode sensors.
“Zone data rolls up into Room data automatically” → Not always. Data aggregation depends on how the Room and Zone boundaries align.

Installer Tips

✔️ Always assign sensors to a Room if using Traffic Mode.
✔️ Label Zones clearly to reflect usage patterns (e.g., Desk_12_East, FocusArea_B).
✔️ Use overlapping Zones carefully to group desks by team, area, or usage type.
✔️ If a Zone is meant to represent a large or shared area spanning multiple Rooms, turn on Show at floor level so it doesn't get buried under just one of them in the sidebar.