Down devices at HQ
Dan Fletcher, an IT support lead at Northwind, asked which devices at the HQ site were down. Memtro listed them with type, zone, room and when their status last changed, so he knew which floor to visit.
Which devices at the HQ site are down right now?
Domotz monitors your networks. Memtro reads collectors with status and organization, the devices each one sees with status, importance, type, vendor, model, zone and tags, one device's detail and inventory, alerts by severity and status, a device's up and down history, organizations, tags and alert profiles. When asked and granted, it can resolve alerts, rename, annotate, tag, exclude or delete devices, set managed or unmanaged, back up a configuration, apply alert profiles, and power devices and outlets on, off or cycle them. IP and MAC addresses, ports and credentials are never returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Domotz tool, reads what it needs, and answers with the source cited.
These tools change something in Domotz. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once Domotz is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Which devices at the HQ site are down?
What critical alerts are still open this week?
How often did the core switch go down in the last week?
Which vital devices are tagged printer?
Power-cycle outlet 4 on the comms room PDU.
Dan Fletcher, an IT support lead at Northwind, asked which devices at the HQ site were down. Memtro listed them with type, zone, room and when their status last changed, so he knew which floor to visit.
Maya Okafor, a network engineer at Acme Ltd, asked Memtro to cycle the outlet feeding a frozen access point. Memtro cycled that one outlet, cutting and restoring its power, and a later read of the device list showed the access point online again.
The teams that lean on Domotz most, a question each of them asks, and what they connect beside it.
A record in Domotz is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In the Domotz Portal, open Settings → Services → API Keys and create a Full Access key. Copy the key and the endpoint, both shown once. An Agent Activation key cannot read anything.
In Memtro, open Connections → Domotz and paste the Endpoint and the API key.
An administrator grants the power, delete and alert actions by name only to the people who may use them.
Ask which devices at the HQ site are down.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Domotz tools are the same everywhere.
Only when you ask, and only what it has been granted: resolve an open alert; rename a device or set its importance, type, vendor, model, zone, room, serial or notes; set a device inventory field; tag a device; remove a tag from a device; create a tag; add a contact to an organization; set a device managed or unmanaged (per-device licensing); back up a device's configuration; exclude a device from monitoring; apply a shared alert profile to a device; remove an alert profile from a device; turn a device on or off, power-cycle or reboot it; turn a power outlet on or off, or cycle it; delete a device. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
Endpoint and API key. In the Domotz Portal, open Settings → Services → API Keys and create a Full Access key. Copy the key and the endpoint, both shown once. An Agent Activation key cannot read anything.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time