What a Webex Control Hub connection brings into Offision
Workspaces become IoT spaces and Webex devices become Offision devices, one way only. Which devices report sensor readings and which never will, what unchecking an item actually deletes, and what the connection does not touch.
A Cisco Webex Control Hub connection is a read connection. Offision asks Control Hub what workspaces and devices your organization has, mirrors them, and then polls the room devices for what their sensors can see. Nothing is written back: Control Hub stays the place your Webex estate is managed.
Workspaces come first, devices follow
Control Hub’s workspace is the concept that matters — it is the physical room. Each workspace you sync becomes an IoT space in Offision, and each Webex device becomes an Offision device attached to the space its workspace became.
That order is a rule, not a preference: a device whose workspace has not been synced is skipped, and the sync says so. Tick the workspace and the device together, or the workspace first.
When you tick a workspace you also say what it links to: Create new IoT space, which gives you sensor readings and nothing else, or an existing bookable resource, which ties the readings to a room people actually book.
Unchecking is not the same for a space and a device
This is the part worth reading twice, because the two behave differently:
- Unchecking a workspace removes only this connection’s mapping. If that space is also fed by another integration, the space survives with its bookable resource still attached. It is deleted only when this was its last connection.
- Unchecking a device deletes that device.
Both are reversible in practice: ticking the item again later restores what was there rather than creating a duplicate, because nothing is destroyed outright.
The dialog asks before it does any of it, naming the count.
Only xAPI devices report readings
A device row carries an xAPI chip when Control Hub says the device supports it — a RoomOS endpoint such as a Room Bar, Board, Desk or Navigator. Its tooltip reads “Supports remote control”, and it decides two things:
- Sensor readings. Only xAPI devices are polled. A device without the chip syncs, appears in the list, and shows Online or Offline — but its sensor tiles stay empty forever. That is not a fault to chase.
- Reboot. Rebooting is the one command Offision can send, and only to an xAPI device that is reachable.
Where a device does report, the readings are temperature, humidity, air quality, noise level, people count and occupancy — the last derived from the people count, falling back to whether the device says anybody is present.
A people count of unavailable is not the same as zero, and Offision keeps them apart rather than drawing an empty room.
A workspace with no devices is not broken
You can sync a workspace that has no Webex hardware in it. The space is created and stays empty of readings, because readings come from devices. Nothing is wrong; there is simply nothing to ask.
What this does not sync
- Bookings, meetings and calendars. A Webex connection brings hardware and sensors, never a schedule. Rooms are booked through Offision’s own booking, or through a calendar integration.
- People. No users, no directory, no attendance.
- Configuration. Offision does not change a device’s settings, its name in Control Hub, or its workspace assignment. Fix those in Control Hub; the next sync picks them up.
- Control beyond reboot. There is no volume, no dialling and no configuration — reboot is the whole of it.