Skip to content
Current

Domotz: collectors, devices, uptime and alerts

5 min read · Updated Oct 8, 2026

Domotz watches the network at each site you manage. A small agent called a collector sits on the site's network and keeps track of every device it can see: switches, access points, printers, cameras, servers. This connector reads those collectors and their devices into Current every 10 minutes and hangs each one off the matching company, so a network problem shows up where your team already looks.

What Current reads

Data setWhat Current storesWhere it lands
CollectorsEach collector (one per monitored site): its name, the Domotz organization it belongs to, whether it is online and since when, its uptime this week, and its newest internet speed test (download and upload).The mapping panel on the Domotz card, and the company's network estate card
DevicesEvery device a collector watches: name, type, vendor and model, IP address, MAC address, serial number, whether it is up or down and since when, and whether you marked it important in Domotz.The company's network estate card and the network panel
Open alertsThe alerts your Domotz alert rules raised in the last 30 days that are still open: severity, when, and the rule's condition in Domotz's own words.The company's Domotz alerts
Note
What Current deliberately does not store
A device's notes, its SNMP settings, its open ports and its operating system details are never read. Current keeps facts about each device, not its configuration.

Connect it

  1. 1
    1 · Create an API key in Domotz
    Sign in to the Domotz Portal, open Settings, then API keys, and create a key. Domotz shows the key once, so copy it before you leave the page.
  2. 2
    2 · Copy the API endpoint
    The same page shows your account's API endpoint. It is a regional address that ends in /public-api/v1, for example https://api-us-east-1-cell-1.domotz.com/public-api/v1/. Copy it exactly.
  3. 3
    3 · Paste both and press Test connection
    In Current open Integrations, find Domotz in the Networking section, paste the endpoint and the key, and press Test connection. Current checks that the endpoint is a Domotz address before it sends anything, reads one page of your collector list to prove the key works, and only then stores the key, server-side.
Note
Your key only ever goes to Domotz
Current sends the key only to an https address that ends in domotz.com, and never follows a redirect to anywhere else. An endpoint that is not a Domotz address is refused with nothing sent.

Map collectors to your companies

After the first sync, Current matches each collector to a company by the name of its Domotz organization, or by the collector's own name when it has no organization. Names are compared with punctuation and suffixes like Inc and LLC removed, and a collector is matched only when exactly one company fits.

  1. 1
    Open the mapping panel
    Integrations, then Domotz, then Manage, then Customer mapping. It opens on the Unmapped tab.
  2. 2
    Check the automatic matches
    The Mapped tab lists every linked collector. Unmap a wrong match and map it to the right company; a mapping you set by hand is never overwritten by a later sync.
  3. 3
    Map or ignore the rest
    Press Map on an unmapped collector and pick its company. A collector that should never map (your own office, a lab) can be ignored.

The alerts it raises

  • +A device you marked important in Domotz that has been down for more than 15 minutes raises a critical alert on its company, naming the device. It clears itself when the device answers again.
  • +A collector that has been offline for more than 15 minutes joins the company's network alert as a warning, beside UniFi, Meraki and Auvik. An offline collector means Current cannot see that site, either because the site lost power or internet, or because the collector itself is off.

Mark a device important in Domotz to have Current watch it this way. Devices that are not marked important still show their status on the company page; they just do not raise an alert of their own.

When something looks wrong

What you seeWhat it means
Test connection says the endpoint is not a Domotz addressThe endpoint must start with https:// and end in domotz.com/public-api/v1. Copy it again from Settings, then API keys in the Domotz Portal.
Test connection is rejectedDomotz did not accept the key at that endpoint. The key and the endpoint must come from the same Domotz account. Create a new key if you are not sure, and paste both again.
A collector is missingCurrent lists every collector the key's account can see. A collector shared with your account by someone else appears only once they grant your account access in Domotz.
A device's status reads Not reportedDomotz marks some devices as hidden. Current shows their status as not reported rather than guessing whether they are up.
Note
Who can do this, and disconnecting
Connecting, testing, mapping and disconnecting are Tenant Admin actions. Disconnect stops the sync; the collectors, devices and alerts already read stay where they are, and reconnecting picks up from there. Partner (read-only) viewers never see any of this data; it is blocked at the database, not just hidden.
Was this helpful?