Merging and splitting devices
When more than one connector reports the same real-world device, the device can appear more than once in Xyte — creating duplicate entries, duplicate incidents, and an inflated device count. The instances aren't always physical units: one may be the physical device (e.g. via the edge collector) and another a cloud representation of it (e.g. the entry the Zoom cloud exposes for a room).
Merging combines these duplicates into one device made of multiple instances (physical or cloud). Splitting reverses it. A merged device is counted once for licensing.
Demo
What can be merged
| Instances merged | Example |
|---|---|
| Physical + vendor cloud | A Crestron device discovered by the Xyte Edge Agent and also reported by the Crestron cloud connector |
| Physical + monitoring cloud | A Crestron device discovered by the Xyte Edge Agent and also monitored through Domotz |
| Vendor cloud + platform cloud | A Crestron room system reported by the Crestron cloud connector and represented by a related Zoom Rooms instance |
| Physical + vendor cloud + platform cloud + monitoring cloud | The same Crestron room system reported by the Crestron cloud connector, discovered by the Xyte Edge Agent, represented as a Zoom Rooms instance, and monitored as a Crestron device in Domotz |
Rules
- Up to 4 devices per merge.
- All must belong to the same customer.
- All must be in the same space (a merged device lives in one space and moves between spaces as a unit).
How to merge
- Select the duplicate devices (2–4) in the device list.
- Choose Merge.
- Pick a default instance — it provides the icon/name shown in list and tile views, and is the instance actions run against.
- Confirm.
How a merged device behaves
- Display & actions: shows the default instance's name/icon (renameable); actions run on the default instance.
- Incidents: surfaced from all instances together; offline tracking can be disabled per instance.
- Billing: counted as one device, whether its instances are physical or cloud representations.
- Location & child devices: all instances stay in one space and move together; child devices are listed per instance rather than combined.
Merged device status
A merged device has one overall status, combined from its instances (symmetric — order doesn't matter).
Legend: 🟢 OK · 🟡 Warning · 🔴 Error · ⚫ Offline · ⚪ Never seen · 🟣 Connector disconnected
| A \ B | 🟢 OK |
🟡 Warn |
🔴 Error |
⚫ Offline |
⚪ Never |
🟣 Disconnected |
|---|---|---|---|---|---|---|
| 🟢 OK | 🟢 OK | 🟡 Warn | 🔴 Error | 🟡 Warn | 🟢 OK | 🟢 OK |
| 🟡 Warn | 🟡 Warn | 🟡 Warn | 🔴 Error | 🟡 Warn | 🟡 Warn | 🟡 Warn |
| 🔴 Error | 🔴 Error | 🔴 Error | 🔴 Error | 🔴 Error | 🔴 Error | 🔴 Error |
| ⚫ Offline | 🟡 Warn | 🟡 Warn | 🔴 Error | ⚫ Offline | ⚫ Offline | ⚫ Offline |
| ⚪ Never | 🟢 OK | 🟡 Warn | 🔴 Error | ⚫ Offline | ⚪ Never | 🟣 Disconnected |
| 🟣 Disconnected | 🟢 OK | 🟡 Warn | 🔴 Error | ⚫ Offline | 🟣 Disconnected | 🟣 Disconnected |
In short: Error always wins; among live statuses (OK / Warning / Device offline) a mismatch resolves to Warning; passive statuses (Never seen, Connector disconnected) defer to any live status, and Connector disconnected outranks Never seen when all instances are passive.
Splitting
Open the merged device → Split → confirm. It separates back into standalone devices.
Deleting an integration
If you delete a connector and one of its devices is part of a merged device, the merge is split. Xyte warns you and shows the impact before you confirm.
Audit log
Merge and split actions are logged, e.g. "Merged devices: [device 1] and [device 2]" and "Split device [default] into [default] and [device 2]."
Need to merge a lot of devices?
Merging is a manual process, one set at a time. If you have a large number of duplicate devices to merge, you don't have to do it all yourself — reach out to [email protected] and we'll be happy to help.