Which occupancy sensors work with booking
Which occupancy sensors work with room and desk booking, model by model, across the four connections in the Marketplace — what each one reports, why a people counter is not an occupancy sensor, and where the hardware is bought.
Offision does not make sensors. It reads them: four connections in the Marketplace bring occupancy in from hardware you already own or buy from the vendor, and each is set up from its own tile. A room or desk is proved to be in use by one of these, and the automations that act on it are a separate decision made in the booking policy.
If the rooms already have video hardware in them, start with Get room occupancy from the video devices you already have — three of the four connections read devices that are already on the wall, and this page is what to buy for the rooms and desks they do not cover.
Open IntegrationsWhich connections report occupancy
| Connection | Models that report occupancy | How it reports | Set up in |
|---|---|---|---|
| Milesight | VS341 for one desk, VS370 for a whole room. AM308 is an air sensor that also reports motion | Occupied or not, sent directly by the sensor | What Milesight sensors report |
| Neat Pulse | Neat Bar, Board, Bar Pro, Frame, Board 50, Board Pro, Board 32, Bar Gen 2 and Center. Neat Pad and Pad Pro do not — they report air only | Derived: the room is occupied while the people count is above zero | What Neat Pulse syncs |
| Webex Control Hub | RoomOS devices carrying the xAPI chip — Room Bar, Board, Desk, Navigator | Derived from the people count, falling back to whether the device says anybody is present | What a Webex Control Hub connection brings in |
| Logitech Sync | Spot and Rally Board 65. Rally Bar, Tap, Tap Scheduler, Sight and Brio report no sensors at all | The device’s own presence reading. Its room people count feeds reports, not check-in | What Logitech Sync brings in |
These are not alternatives to each other. A building already full of Neat, Webex or Logitech room devices gets room occupancy without buying anything, because those devices are already sensing — though several models report nothing at all, and Get room occupancy from the video devices you already have is the list. Milesight is what covers the desks, and the rooms that have no video hardware in them at all.
Milesight has one hard prerequisite the others do not: its sensors reach Offision through a Milesight gateway on your own network, and that gateway must be running firmware 60.0.0.50 or newer — see Firmware 60.0.0.50 or newer. Older firmware sends the reading without saying which sensor took it, and nothing at the Offision end can work around it.
The full per-model readings — air, light, battery and the rest — are in each connection’s own article. Only occupancy is listed here.
The sensor must be linked to the room, not the floor
A sensor that is reporting perfectly still drives nothing until it is linked to the thing it watches. Every sensor carries a bind type:
- Resource — the sensor watches one bookable thing, this desk or this room. This is the one booking uses.
- Location — the sensor sits at a point on a floor plan without owning a resource. Useful for air sensors and for the occupancy map; no booking follows from it.
A sensor bound as a Location reports the floor, and a booking never sees it. It is the first thing to check when a desk never shows as taken — see Give the sensor its place.
A people counter is not an occupancy sensor
Booking reads one thing from a sensor: whether the space is occupied or empty. A headcount is neither needed nor used, which is why an inexpensive occupancy sensor is enough to check a booking in.
The reverse does not hold. A device that reports only a number of people, and never an occupied-or-empty state, does not drive booking. Milesight’s counting line — VS121, VS133 and VS135 — is a different product family from the occupancy sensors above and has not been checked against Offision; see These models do not count people.
Where to buy
From the vendor or from your Offision partner. Offision certifies and reads this hardware; it does not sell it, and there is no model on this page that has to be bought through Offision.
Two things belong in the budget beside the hardware. Milesight sensors need a Milesight gateway on the network to reach Offision at all, so the first sensor in a building costs more than the tenth. And each sensor takes an Occupancy sensor device licence, counted per device like a panel — see What your licence covers.
Coverage, mounting height and battery life are the manufacturer’s figures. Ask your supplier for the datasheet: how many desks one sensor can watch is a property of the sensor, not of Offision.
What this does not control
- What the booking does about the reading. Auto check-in, auto checkout and auto extend are three separate settings on the booking policy’s Others page, under Sensor — see Let an occupancy sensor check in, check out and extend a booking.
- Connecting the hardware. Each connection has its own tile in the Marketplace and its own guide; this page only says which models report occupancy once connected.
- Air quality, light level and battery. These arrive from the same sensors but drive no booking behaviour.