Connect Logitech Sync
Generate a certificate in Logitech Sync, paste it and the organisation id into Offision, and sync the rooms and devices — about fifteen minutes, plus one poll before readings appear.
Logitech Sync is the one connection that authenticates with a certificate rather than a key you can paste from an email. You generate it in Logitech’s own console, hand Offision the certificate and its private key, then choose which rooms and devices to sync.
What to have ready
- A Logitech Sync organisation with its devices already enrolled and reporting
- A Logitech Sync sign-in that can reach the organisation’s API settings
- Somewhere secure for the private key — a password manager, not a chat message
- About fifteen minutes, plus one poll before the first readings arrive
1. Generate the certificate in Logitech Sync
Sign in to Logitech Sync and open the organisation’s API access page, then generate a certificate. Save three things before you leave the page: the certificate, the private key, and the organisation id.
The organisation id is not a loose detail. It is written into the certificate itself, and Offision sends both — so an id that does not match the certificate is refused outright rather than returning an empty result. If you are ever unsure which organisation a certificate belongs to, generate a fresh one rather than guessing.
2. Open Logitech Sync in Offision
The Logitech Sync tile is in the marketplace, filed under IoT monitoring, Environmental sensor and Audio video. The same connection also appears on Devices › Platform integration; either opens the same dialog.
Open Integrations3. Add the connection
Choose to add a connection. The form opens on Guidelines and the fields are on Setup — click straight through to it.
| Field | What to enter |
|---|---|
| Name | Anything that tells connections apart — the organisation’s name works |
| Branch management | Which part of the company owns the synced devices |
| API Base URL | Leave the default unless Logitech has told you otherwise |
| Org ID | The organisation id from step 1 |
| Certificate | The whole certificate, including its first and last lines |
| Private key | The matching key, pasted the same way |
| Poll interval (minutes) | Recorded on the connection and shown on its tile. Readings refresh about once a minute either way |
Save, and the connection appears with a green dot.
Editing the connection later shows Leave blank to keep the current certificate and key. — which means exactly that. Leave both boxes empty unless you are replacing the certificate.
4. Sync devices & spaces
Open the connection and choose Sync devices & spaces. The dialog lists what the certificate can see, in two sections: Spaces — Logitech’s rooms — and Devices, each with its product, place and whether it is online.
Check a room and give its readings a destination: Create new IoT space collects the data without making it bookable, and picking one of your bookable resources wires the room’s sensors to a room people actually book. Then check the devices and sync.
Only rooms appear under Spaces. A Logitech desk is never offered here, and that is not a fault — see What Logitech Sync brings into Offision.
5. Check it worked
Open Devices in the dialog’s rail and pick one — it should report online. A Spot or a Rally Board 65 grows a Status page whose Sensor data tiles fill within a poll or so; a Rally Bar or a Tap correctly has no Status page at all.
Then check the other direction: Open in Logitech Sync on the same page should land on this exact device in Logitech’s console. That proves the identifiers match and not merely the names. Where the readings go next is its own article: See Logitech sensor data around Offision.
When it goes wrong
| What you see | Usual cause |
|---|---|
| The save button stays disabled | Org ID, Certificate or Private key is empty — all three are required, and a certificate without its key will not do |
| Failed to load preview in the sync dialog | The certificate is wrong or expired, or the Org ID belongs to a different organisation than the certificate does |
| No spaces found, but devices are listed | The organisation has only desks. Only rooms become spaces |
| The connection shows Suspended, with a Resume action | The organisation’s API plan lapsed, or the certificate was deactivated. A refusal of that kind suspends the connection on the first occurrence; ordinary network failures take five in a row. Fix the cause, then Resume — recovery is deliberately manual |
| Editing appears to have cleared the certificate | It has not. Blank means keep the current one |
| A device is online but has no Status page | That product has no sensors — only Spot and Rally Board 65 report readings |
Tiles read - and never fill | The device is named so that Offision reads it as a Spot or a Board when it is neither. Rename it in Logitech Sync and sync again |