Merging and splitting devices
When more than one connector reports the same real-world device, it can appear more than once in Xyte — one entry per connector.
Merging combines these duplicates into a single device with a primary instance and one or more secondary instances. Splitting reverses it. A merged device is counted once for licensing.
Video walkthrough
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 primary 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 primary instance's name/icon (renameable); actions run on the primary 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 a C2C connector, Edge Agent, or merged device
If you delete a C2C connector or Edge Agent 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.
If you delete the merged device itself, all instances in the merged device are deleted. To delete only one instance, split the merged device first, then delete the standalone device.
Audit log
Merge and split actions are logged, e.g. "Merged devices: [device 1] and [device 2]" and "Split device [primary] into [primary] 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.
Updated 20 days ago