Genetec Doors Showing Offline After Sync — CloudLink Reader-Timeout Setting

Applies to: XPressEntry integrated with Genetec Security Center via CloudLink

Symptom: A Full Sync completes without error, but Genetec Security Center shows some or all XPressEntry-managed doors/readers as offline.

Root Cause #

The most common cause is a reader/connection timeout value left at “0” in the Data Manager CloudLink settings. A timeout of 0 breaks the Genetec SDK login handshake used to report reader status back to Security Center — the sync itself succeeds, but the door-status heartbeat never completes. This has now been confirmed as the root cause across multiple customer sites; if you’re seeing this, you are not alone and it is not a data-corruption issue.

A second, equally common cause (see the naming section below) is a mismatch between the RIO interface name configured in Synergis Cloud Link and the Door name configured in Genetec Security Center — these must match exactly, and a mismatch will show as the same “never comes online” symptom even though the timeout setting is correct.

Fix: CloudLink Reader Timeout #

1. Open Data Manager → Settings for the Genetec connector.
2. Locate the CloudLink reader timeout field.
3. Confirm it is not set to 0. Set it to the recommended default (check your Data Manager version’s documentation, or contact support if unsure of the correct value for your environment).
4. Save the setting.
5. Restart the Data Manager service.
6. Re-run Full Sync and confirm doors show online in Security Center.

Fix: RIO Interface / Door Naming Convention #

This is a distinct and separate cause from the timeout setting above, and it’s easy to miss because nothing about it looks like an error — the door simply never comes online, with no useful message pointing to naming.

The RIO interface is precise about its naming convention. If the interface name (on the Synergis/Cloud Link side) doesn’t exactly match the door name (on the Genetec Security Center side), XPressEntry cannot resolve what that door is and it will never appear online — no error is raised, it just silently fails to link up. The naming rule:

• No spaces or special characters are allowed anywhere in the name.
• The match is case-sensitive — MobileReader1 and mobilereader1 are not the same name as far as this matching is concerned.
• The Door name in Genetec and the RIO interface’s Address must be identical, character-for-character.

Example. If the desired door name as displayed in Genetec is “Mobile Reader 1”, it must actually be created/named as MobileReader1 (no space) everywhere it appears:

Repeat this pattern (same channel, new numbering) for each additional reader/door — e.g. MobileReader2, MobileReader2-IN/-OUT, and so on.

Don’t confuse “Reader Labels” with “Reader Input / Output” (RIO) — they are two different settings in Config Tool, and mixing them up is a common source of confusion when working through this setup.

Area structure also matters. The door must sit under an area structure with two levels — an Outside area, and a child Inside area — with the door itself placed in the Inside area:

Outside Area
  >> Inside Area
      >>>> MobileReader1 (door)

⚠️ Very Important: Renaming a Door Later #

If you rename a door in Genetec after it’s already set up and working, do not simply edit/rename the existing RIO interface’s Address field to match. Editing the Address in place does not correctly re-link the interface — the door will drop offline and stay offline, and this is the single most common way a previously-working naming setup breaks.

Instead, when a door is renamed:

1. Delete the existing RIO interface entirely for that door (do not just edit it).
2. Create a brand-new RIO interface with the Address set to the new door name, following the exact naming steps above (matching Channel, no spaces/special characters, case-sensitive match to the new door name).
3. Recreate the Reader Labels (<new-name>-IN / <new-name>-OUT) under the new interface.
4. Proceed with the Partial Sync / Update RIO steps below as normal.

Treat a door rename as “delete and recreate the interface,” never as “rename the interface in place.”

Steps to fix a naming mismatch (e.g., after renaming a door or moving a reader to a new area) #

1. In Genetec Config Tool, rename the door (and confirm the Outside/Inside area structure above) to the exact name you intend to use — no spaces or special characters.
2. If this is a rename of a door that already had a working interface, delete that old RIO interface now rather than editing it (see the warning above).
3. Create a new RIO/Synergis interface with the Channel set to xpressentry and the Address set to the identical name you just used for the door (case-sensitive match).
4. Confirm the Manufacturer is set to Telaeris and the Model to your reader’s model (e.g. XPID200).
5. Set up the two Reader Labels for that interface (<name>-IN and <name>-OUT) — remember these are separate from the RIO Address itself.
6. In the XPressEntry server application, go to Tools → Settings → GENETEC and run Partial Sync Now.
7. Go to Setup → Data Manager, open the CloudLink tab (or RIO Settings field), and confirm the door you just renamed is checked/selected.
8. Click Update RIO, confirm, then OK → Save.
9. Run another Partial Sync.
10. In XPressEntry, go to Add/Edit Info → Doors, find the door, and confirm Start Zone = Outside and End Zone = Inside (or your equivalent zone names), and that the Entry/Exit reader assignments match what you configured in Config Tool.

If you’re renaming an existing door/moving a reader to a new area rather than setting one up fresh, expect the handheld-to-Genetec connection to briefly drop during this process — this is expected until the new interface is fully created and propagated through the steps above, not a sign that something went wrong.

If Neither of These Fixes It #

• Confirm the Genetec Security Center service itself is running and reachable.
• Check whether a recent Genetec upgrade changed SDK version compatibility — see PACS API/Version Incompatibility After an Upgrade.
• Contact the Telaeris Helpdesk with your Data Manager sync log, the exact timeout value you have configured, and the door/interface names you’re using (screenshots of both the Genetec door config and the RIO interface config side-by-side are the fastest way for support to spot a naming mismatch).

Related Articles #

• Sync Failing or Doors Showing Offline? Start Here (triage hub)
• Known Sync Error Messages — Quick Reference