Can you recover a deleted Domotz device record?
When a device disappears from Domotz, an earlier RMMBackup snapshot can help you review the inventory and configuration details captured before it went missing. This guide explains how permissions, filters, plans, and device state affect what history is available.
Distinguish a deleted Domotz device from collector, permission, organization, visibility, or plan changes and use earlier snapshots safely.
On this page
Establish why the device is missing
Confirm the account, organization scope, API key permissions, collector availability, hidden and excluded-device settings, and plan before classifying a device as removed. Search by the native collector and device identifiers rather than hostname or IP address alone.
Review available audit, alert, activity, and network-event records for supporting evidence. Their absence does not prove that no change occurred because permissions and source retention can limit those streams.
Separate review from restoration
| Goal | What an earlier RMMBackup snapshot can do |
|---|---|
| Review earlier inventory | Show the original device and inventory data captured successfully |
| Inspect earlier configuration | Provide saved configuration-history artifacts that existed and were captured before access was lost |
| Explain disappearance | Supply available audit, alert, activity, and network history as evidence, without guaranteeing a cause |
| Restore the live device record | Not supported; RMMBackup does not call Domotz write operations |
An earlier record is reference data, not a device enrollment, monitoring policy, or working collector.
Check snapshot completeness
Use the most recent complete capture for the affected collection. If that collection was partial or failed, inspect its scoped failures before drawing conclusions. RMMBackup does not create deletion events from failed collections or use them as new comparison baselines.
Prepare before offboarding
Create and verify a full snapshot before removing a collector, changing organizations, rotating access, or ending a service. Download the ZIP, confirm important native IDs, and separately preserve any operational reports needed by the MSP.
Read the deleted-device recovery overview, Domotz export guide, configuration guide, and retention guide.
Official source
Domotz Public API developer portal
Official Domotz reference for device, collector, audit, alert, and history resources available through the Public API.