Merging and splitting devices
When more than one source reports the same real-world device, it can appear more than once in Xyte — one entry per source (the Xyte Edge, a cloud connector, or a device that connects to Xyte directly). Merging combines these duplicates into a single device with a primary instance and one or more secondary instances, and splitting reverses it. A merged device is counted once in your device totals.
Merging is available in organization portals where the feature is enabled for your account, and is currently marked Beta. Can't find the button? See the Troubleshooting tab.
Video walkthrough
How to merge
- Select the duplicate devices (2–4) in the Devices list, or in a space's or room's device view.
- Click Merge Devices.
- In the Merge Devices window, compare the devices side by side (image, name, connection method, vendor, model, submodel, IP/hostname, serial number, MAC address, firmware, status) and click Make Primary on the one you want in front. The window shows the space the merged device will be located in — the primary's space.
- Click Merge Devices to confirm.
Not sure which one to make primary? See Choosing the primary on the Advanced tab.
How to split
Splitting separates a merged device back into standalone devices. You can do it from two places:
- Devices list, or a space's or room's device view: select one or more merged devices and click Split Devices, then confirm.
- Space and room views: open the ⋯ menu on the merged device's card or tile and choose Split Device, then confirm.
After a split, every instance is a standalone device again. Splitting unlinks the instances; it does not move a secondary back to the space it came from — it stays where the merge put it, and you can move it yourself afterwards.
What you'll see after merging
- Devices list: the merged device appears as one row, under the primary's name, with its combined status. The Merge type column reads Merged (standalone devices read Standalone), and you can filter or sort by it.
- Space and room views: the merged device's card or tile carries a merge icon; hover it to see Merged device.
- Device page: one tab per instance across the top, each labelled with its source (for example Xyte Connect+ Edge, or the connector type, such as Poly Lens) and a colour bar for that instance's own status. The primary's tab opens first. Each tab has that instance's own Overview, Details, State, Incidents and Notes.
This is worth understanding before you pick the primary, because the Overview you land on is the primary's. Every instance's data is still there, one tab away — but the dashboard shown first is the one belonging to the primary's model. If the instance with the richer data is not the primary, its readings live behind its tab rather than on the front page.
How a merged device behaves
- Name & image: the merged device shows the primary instance's name and image in the device list, space views and the device page. You can rename it like any device.
- Status: one combined status, calculated from all instances (see Merged device status on the Advanced tab).
- Incidents and commands: combined across all instances (see Commands and incident tracking on the Advanced tab).
- Device counts: counted as one device in your device totals, 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.
What can be merged
Merge is for one physical device seen by different sources — for example, the same device discovered by the Xyte Edge and reported by a cloud connector.
| Instances merged | Example |
|---|---|
| Physical + vendor cloud | A Crestron device discovered by the Xyte Edge and also reported by the Crestron cloud connector |
| Physical + monitoring cloud | A Crestron device discovered by the Xyte Edge 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, represented as a Zoom Rooms instance, and monitored as a Crestron device in Domotz |
Rules
- 2 to 4 devices per merged device.
- All must belong to the same customer.
- They do not need to be in the same space already — when you merge, the secondary instances are moved into the primary's space. When you move the merged device, all its instances move with it.
- Two devices imported by the same cloud connector cannot be merged with each other. A device discovered by the Xyte Edge can be merged with one reported by a cloud connector, and devices from two different cloud connectors can be merged together.
- You need the right access to every device — see Permissions.
When devices can't be merged
If the selection doesn't fit, the Merge Devices button is greyed out and hovering it tells you why:
| What you selected | Message you see | What to do |
|---|---|---|
| Only one device | Select at least 2 devices to merge | Select 2–4 devices. |
| More than 4 devices | Select up to 4 devices to merge | Select up to 4. |
| Devices that belong to different customers | You can only merge devices belonging to the same customer | Make sure the duplicates are claimed under the same customer, then merge. |
| A device that is already merged | Merged devices cannot be selected for merging | To add another source to a merged device, split it first, then merge all the devices again in one step (up to 4). |
| Two or more devices from the same cloud connector | The merge is rejected when you confirm. | Nothing to merge — every device a connector imports is its own record. If one of them is a second network interface of the same unit that you don't need to monitor, you can delete it (see Two devices from the same connector on the Troubleshooting tab). |
Choosing the primary
No single connection sees the whole device. One knows it is up and answering on the network; another knows what the device says about itself — health, uptime, firmware, link speed, redundancy. Neither is the full story on its own.
That is what merging is for: bring the same physical device together from two or more sources, so their different depths add up to one complete picture, on one device your team opens once.
Whichever sources are involved, the same rule decides the primary: pick the instance whose Overview you want to see first. The primary's Overview becomes the front page and the other instances sit beside it as tabs. Nothing is lost either way — the front page simply follows the primary.
There is no way to change the primary of an existing merged device from the portal. To pick a different primary, split the device and merge it again, choosing the other instance. Nothing is lost — splitting and merging only link and unlink the records.
Use cases
Edge device + a vendor cloudThe most common case.
A device is discovered on the network by the Xyte Edge and is also reported by the vendor's own cloud — a Q-SYS camera in Q-SYS Reflect, for example, or a Poly bar in Poly Lens.
For many models the Xyte Edge contributes reachability — is it up, how does it respond to a ping — while the vendor cloud contributes what the device reports about itself. Where that holds, the vendor cloud is usually the side you want in front.
Edge device is the richer sourceThe reverse also happens. For a network switch, a DSP or a PDU with a full Edge driver, the Xyte Edge may read far more than the vendor's cloud does — port-level PoE, CPU and memory, temperature, fan state — while the cloud record carries little beyond presence.
Here the Edge instance is the richer side.
Two cloudsA room system can arrive from the vendor's connector and again from the platform it runs — a Crestron room reported by the Crestron connector and as a Zoom Rooms instance, or a device also monitored through Domotz.
Neither is obviously richer here; the two simply describe the device differently. Choose by which view your team works in day to day.
How Xyte identifies a device
When a device is onboarded, Xyte gives it an identity based on either its cloud identifier (for devices from a cloud connector) or the combination of its MAC address and serial number. This identity keeps the same device from being registered twice under the same source.
When the same physical device is brought in through different sources — for example a cloud connector and the Xyte Edge — each source creates its own record. Merging brings those records together, and you choose which ones represent the same device.
What merging changes on each record
Merging does not rewrite your devices. It links them and puts one of them in front.
On the primary instance — nothing changes. It keeps its own name, model, identifiers, details, state and history.
On each secondary instance — exactly one thing changes: it is moved into the primary's space. Its name, model, cloud identifier, serial number, MAC address, details, state, telemetry and incident history are all untouched, and it keeps reporting through its own source exactly as before.
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 · 🟣 Disconnected (the device's connection path, such as a connector, Edge or parent device, is down)
| 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 / Offline) a mismatch resolves to Warning; passive statuses (Never seen, Disconnected) defer to any live status, and Disconnected outranks Never seen when all instances are passive.
The primary doesn't decide the status. The combined status is what the device header, the device card and the devices list show, whichever instance is the primary. Each instance's own tab still shows that instance's own status. For example, if the Edge instance is OK and a cloud connector instance has an active incident (Error), the merged device shows Error even when the Edge is the primary, while the Edge tab shows OK. To see which instance is causing it, open the tabs.
Commands and incident tracking
- Incidents: incidents from every instance count towards the merged device. Turn off incident tracking on the device page applies to all its instances at once.
- Commands: the device page lists the commands of every instance, grouped by source — each command runs on the instance it belongs to.
Merging and child devices
Merging works on one device at a time — it joins duplicate records of the same device. It does not act on that device's child devices, and there's no setting to make them follow the parent automatically — merging is always per device, by design.
So if you merge a parent that has child devices — a Q-SYS Core, a Logitech room system, or any parent with children (Dante endpoints, a DSP processor, and so on) — only the parent's own duplicate records are merged. The children are left as they are: each stays its own device, still listed under the parent in the hierarchy. A child isn't a duplicate of its parent, so there's nothing to merge it into.
You'd only merge a child if that same child was also brought in through another source. In that case you merge the child's records on their own, exactly like any other device.
Device count: this never inflates your count. A child with no duplicate is a single device either way — merging only ever combines duplicates into one.
Deleting a merged device or a connector
- Deleting the merged device from the device list or a space view deletes all its instances. If any instance has child devices, you're asked whether to delete the children too; choose keep and those children stay as standalone devices. To delete only one instance, split the merged device first, then delete the standalone device.
- Deleting from the device page (Manage → Delete device) deletes the instance whose tab you are on. If that is the primary, all instances are deleted; if it is a secondary, only that instance is removed and the rest stay merged.
- Deleting a cloud connector deletes the devices it imported. If one of them was a merged device's primary, the remaining instance whose name comes first alphabetically becomes the primary. If only one instance remains, it becomes a standalone device. If the connector's device was a secondary, only that instance is removed.
Permissions
You need admin access to every device you merge, and permission to edit the primary's space when a device has to move into it.
Audit log
Merge and split actions are recorded in your organization's audit log (Settings → Audit Logs), for example "Merged shadow [device 2] into primary [device 1]" and "Split shadow [device 2] from primary [device 1]". Only organization admins can see the audit log, and how far back it goes depends on your plan.
I don't see Merge Devices
Merging is available in organization portals where the feature is enabled for your account, and is currently marked Beta. If every device you selected is already merged, you'll see Split Devices instead. If you still don't see Merge Devices, contact [email protected].
Merge Devices is greyed out
Your selection doesn't fit the merge rules. Hover the Merge Devices button to see why:
- Select at least 2 devices to merge — select 2–4 devices.
- Select up to 4 devices to merge — select up to 4.
- You can only merge devices belonging to the same customer — make sure the duplicates are claimed under the same customer, then merge.
- Merged devices cannot be selected for merging — to add another source to a merged device, split it first, then merge all the devices again in one step (up to 4).
Two devices from the same cloud connector don't grey the button out: the merge is rejected when you confirm (see Two devices from the same connector below). The full list is in When devices can't be merged on the Advanced tab.
Two devices from the same connector
Two devices imported by the same cloud connector cannot be merged with each other — the merge is rejected when you confirm. Every device a connector imports is its own record.
One physical device reported twice by a single connectorSome devices are discovered more than once by the same connector — most often a unit with two network interfaces, such as separate control and audio-network connections, which the provider reports as two devices with different MAC addresses.
Because two devices from the same connector can't be merged, these cannot currently be combined. If you do not want the second interface monitored, you can delete that device: it will be listed as excluded on the connector's devices page, will not be re-imported on the next sync, and will not count towards your device total. See Viewing C2C device status per connector.
The merged device is in the wrong space
When you merge, the secondary instances are moved into the primary's space. To put the merged device somewhere else, move it: all its instances move with it.
If you split it instead, the secondaries stay in the space the merge put them in, and you can move each one yourself afterwards.
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.
If you'd like help identifying or reconciling duplicates at scale, reach out to [email protected].
Updated 3 days ago
