Domotz Setup Beta

Domotz is a network monitoring platform that discovers and watches the devices on each customer site's local network. Once connected, Junto can tell whether a whole site is offline or a single device is down, show a device's uptime and latency history, read Internet speed tests, trace what a device is plugged into, and review Domotz alerts -- so the agent can answer "is the office down?" or "why does this printer keep dropping?" during a ticket.

This integration is read-only. Junto never changes anything in Domotz.

How Junto Connects

You connect Domotz once for your organization with an API key from the Domotz Portal. Each Domotz collector monitors one site, so you then map each collector to the Junto company it belongs to. A company with several sites can have several collectors.

Prerequisites

• A Junto Admin or Owner account
• A Domotz account with access to the Domotz Portal and permission to create API keys
• Customer companies in Junto, imported from your PSA, to map collectors to

Step 1: Create an API Key in Domotz

1. Sign in to the Domotz Portal.
2. Go to Settings > API keys and create a new key, for example named Junto.
3. Copy the key value and store it securely.
4. Note the API endpoint shown next to the key. It depends on your Domotz region and ends in /public-api/v1.

Step 2: Configure in Junto

1. Go to Settings > Integrations > Domotz.

2. Click Add configuration.

3. Complete the form:

   Field	What to enter
   API key	The key from Step 1. It is encrypted when stored.
   API endpoint	The regional endpoint from Step 1. The default is the US East endpoint; replace it if the Domotz Portal shows a different one. It must be a domotz.com address ending in /public-api/v1.
   Active	Leave on. Turn it off later to pause agent access without deleting the connection.

4. Click Create configuration. Junto checks the key and endpoint against Domotz before saving.

5. Click Test connection on the configuration card to confirm the connection.

The configuration card shows the connected Domotz account, the last four characters of the key, and the endpoint host.

Step 3: Map Collectors to Companies

Agents only read the collectors mapped to the company they are working on, so a company must have at least one mapped collector before the agent can use Domotz for it.

1. Click Map companies on the configuration card. The dialog lists one row per Domotz collector.
2. For each collector, pick the Junto company it belongs to, or leave it Not mapped.
3. Click Save mappings.

You can also click Run auto-map. Junto matches collectors to companies by collector name, then by the collector's Domotz organization name. Auto-map only fills companies that don't have a collector yet; map additional sites for a company by hand.

Each collector belongs to one company, and a company can own several collectors. A collector that no longer exists in Domotz is marked Removed.

What the Agent Can Do

All Domotz capabilities are read-only and low risk, so none require approval.

Sites

Capability	What Junto can do	Risk level
List collectors	List a company's collectors (one per site) with online status, WAN IP, agent version, and Domotz organization	Low
Collector uptime	A site's uptime percentage, downtime intervals, and connection events over a time window (the last 7 days by default). A collector that is down usually means the whole site lost power or Internet	Low
Monitored networks	The networks a collector monitors, with IP, netmask, and VLAN, plus any active IP address conflicts	Low
Speed tests	Internet speed test results the collector measured for its site, in Mbps (the last 7 days by default)	Low

Devices

Capability	What Junto can do	Risk level
List devices	List the devices a collector discovered -- switches, firewalls, access points, printers, cameras, servers, and IoT -- with status, type, vendor, model, IPs, and MAC; filter by status or search by name, IP, MAC, vendor, model, or type	Low
Get device	Full details of one device: status, type, vendor, model, OS, firmware, serial, zone, IPs, MAC, open ports, and inventory fields	Low
Device uptime	A device's uptime percentage, downtime intervals, and state changes, alongside its collector's uptime so a site-wide outage is easy to spot (the last 7 days by default)	Low
Device latency	Ping latency history with minimum, median, and maximum delay and packet loss (the last 24 hours by default)	Low
Device metrics	The SNMP and driver metrics Domotz collects for a device, such as CPU, memory, temperature, interface, or toner values	Low

Alerts and Topology

Capability	What Junto can do	Risk level
List alerts	Alert events from your Domotz alert rules across all of a company's collectors (the last 72 hours by default), newest first; filter by collector, device, severity (Critical, High, Warning, Info), or status (Open, Resolved)	Low
Network topology	Which device connects to which at a site -- for example firewall to switch, switch to access point -- with each end's name, type, and status	Low

Scope and Behavior

• One customer at a time: Every request runs against one mapped company. The agent only accepts collectors mapped to that company.
• Several sites: When a company has more than one collector, the agent asks which site you mean, or lists the collectors so you can pick one. With a single collector, it is selected automatically.
• Local networks only: Domotz sees devices on the site's local networks, not remote users' laptops. A problem limited to one remote user is usually not network-side.
• SNMP community strings are never returned, even though Domotz includes them in device data.

Example requests:

• "Is Acme's main office down? Check the Domotz collector."
• "Acme's front-desk printer keeps dropping off. Show its uptime and latency for the last day."
• "Internet at Acme's warehouse feels slow. Compare this week's speed tests with last week's."
• "What is Acme's conference room access point plugged into?"
• "List open Domotz alerts for Acme."

Managing the Connection

• Update the key or endpoint: Click Edit, enter the replacement, and click Update configuration. Leave API key blank to keep the current key.
• Change accounts: A key that belongs to a different Domotz account clears every collector mapping, because collector IDs belong to the previous account. Reopen Map companies and map collectors again.
• Pause the integration: Click Edit, turn off Active, and save. The configuration and mappings remain saved.
• Disconnect: Click Disconnect and confirm. This removes Junto's saved API key and collector mappings. Nothing changes in Domotz.

Troubleshooting

• Save fails on the API endpoint -- Copy the endpoint exactly as the Domotz Portal shows it next to your key. It must be a domotz.com address ending in /public-api/v1.
• Connection test fails -- Check that the key is still active in the Domotz Portal and that the endpoint matches your account's region.
• "Not mapped to a Domotz collector" -- Open Map companies and map at least one collector to the company.
• The agent asks which collector to use -- The company has several mapped sites. Name the site, or ask the agent to list the company's collectors first.
• A remote user's laptop isn't listed -- Domotz only discovers devices on the site's local networks. Check the user's device in your RMM instead.
• No collectors in the mapping dialog -- Confirm the API key's account can see your collectors in the Domotz Portal.