What Logitech Sync brings into Offision

Logitech Sync is Logitech’s own management cloud — the Rally Bars, Tap Schedulers and Spots in the building already report to it. The Offision connection reads that cloud with a certificate you generate in Sync, and turns what it finds into rooms and sensors Offision can use. Nothing is installed on the devices, and Offision never talks to them directly.

It only ever reads. That is the first thing to know about this connection, and the difference that runs through everything below.

Rooms become spaces, desks never do

Logitech organises everything into places, and a place is either a room or a desk. Only rooms cross over: each room you check in the sync dialog becomes an IoT space in Offision. A desk place is never offered and never becomes a space, however many devices are sitting on it.

Devices are more forgiving. Every device syncs, including one whose place is a desk or a room you left unchecked — it simply arrives unbound, with no space and no room behind it. It still shows its own state; it just has nowhere to send a reading. Linking it later does not disturb anything you set by hand.

What makes a space useful is what you point it at. Each room carries a choice between Create new IoT space — Sensor data only, not bookable — and an existing bookable resource, which is the option that puts the readings on the booking calendar, the room’s panel and its signage.

Each product brings a different sensor suite

Every synced device appears as a Logitech Device, and its tiles show only what that product measures. Two products carry air sensors. Everything else reports whether it is online, and nothing more.

A product with no readings has no Status page at all — the entry disappears from the device dialog’s rail rather than showing an empty one. That is expected for a Rally Bar, and it is not a sign the sync went wrong.

The people count belongs to the room

No Logitech device reports a people count, and none ever will through this API. Logitech counts at the room level: the place carries the number, and Offision treats the room as occupied while that number is above zero.

The practical effect is a good one. A synced Logitech room shows People and State even when the only thing in it is an air sensor, because the count comes from the room rather than from any device you happened to link. It also means a device page never shows a headcount — look at the space, not the hardware.

It cuts the other way for automation. A booking policy that checks a meeting in or releases an empty room reads the device bound to that room, so it can act on a Spot or a Rally Board 65 and on nothing else. The room’s people count reaches reports and the calendar’s usage summary, but never a check-in.

The device’s name decides what it reports

Logitech’s API does not return a model code, so Offision reads the product family out of the device’s name as it appears in Logitech Sync, and matches it loosely.

What this does not sync

A Logitech room is not a calendar. The connection moves no bookings, no meetings and no people — rooms and calendars come from Microsoft 365 or Google Workspace, and Logitech Sync only adds sensing to rooms you already have. It does not create bookable resources either; it links to the ones you have made.

And there is no control in either direction. Offision cannot reboot a Logitech device, ask it to resync, or change a setting on it, because the Sync API offers no way to — so a Logitech device has no Controls page where a Neat device has one. Everything about the device itself stays in Logitech Sync.