See Logitech sensor data around Offision

Once a Logitech device is synced, its readings stop belonging to the device. They land on the space it sits in, roll up to the room and floor, and surface from there — each place answering a different question.

On the device — is it healthy right now

The device’s own page shows the live picture: online state, serial number, when it last reported, and a Sensor data tile per reading. This is the page for this sensor is behaving strangely; everything below is about the room.

Only a Spot or a Rally Board 65 has this page. For a Rally Bar, a Tap or a Tap Scheduler the Status entry is simply absent from the rail, because the product reports no readings to show.

On the space — what the room is reporting

Open Spaces in the same dialog and pick one — the same rooms also have a page of their own under Room Control › Spaces. A space shows the latest readings for the room as a whole, Devices in this space, and the row that decides everything downstream: which bookable resource it feeds.

This is also the page that always has a People count and a State, even when the only device in the room is an air sensor. The count comes from the room in Logitech, not from any device — so look here for a headcount, never at a device page.

Back in time — View history

Every sensor-data section carries View history, which opens the same chart wherever you start from: pick a reading, pick a range, and see how it moved. This is where a stuffy afternoon meeting room stops being an anecdote and becomes a CO2 curve that peaks at the same hour every day.

Across the estate — Device monitoring

Devices › Device monitoring lists Logitech devices alongside every other device family. This is the page for the morning sweep — is anything offline anywhere — rather than for one room’s story.

On the booking calendar — how the room was used

This is what linking a space to a bookable resource is for. On the booking calendar, a finished meeting’s pop-up grows a usage summary: actual usage against the booked slot, the peak number of people against the room’s capacity, and a people-over-time curve — the difference between a booked room and a used one, measured rather than argued.

That summary is a record, not an automation. A booking policy that checks a meeting in or releases an empty room reads the device bound to the resource, so it works from a Spot or a Rally Board 65 and from nothing else — the room’s own people count feeds the summary and the reports, never the check-in.

On signage

A board can carry the readings live — the info bar’s people count and air-quality chips, and the environment and occupancy widgets. The board reads the floor and room its screen is bound to, so a linked Logitech room’s numbers appear on whatever screen stands there. Setting the bar up is a signage article: The Info bar widget.

Air chips need a room with an air sensor behind them. A room whose only Logitech hardware is a Rally Bar can show people and occupancy, but never temperature or CO2 — there is nothing in the room measuring them.

The controls Offision does not have

Every other room-hardware connection in Offision offers at least a reboot. Logitech Sync offers none, and this is a property of Logitech’s API rather than a setting somewhere: it is read-only, so there is no Controls page on a Logitech device, no resync, and no scheduled overnight reboot.

Anything that changes the device — renaming it, restarting it, updating it — is done in Logitech Sync. Open in Logitech Sync, on the device’s page, is the shortest way there, and it lands on that exact device.