Muting a device for maintenance

Muting stops a device’s alarm notifications for a while, for example during maintenance or commissioning. The alarms still open, escalate and clear, and they are still recorded; nobody is told about them until the mute ends.

What a mute does

	During a mute
Alarm rules	Still evaluated. Alarms open, change severity and clear as usual.
Alarms page, bell counts, dashboards	Show the alarms as usual.
Notifications for opening and escalation	Not sent. The alarm’s timeline gets one line Muted: nobody was notified.
Reminders	Not sent while the mute lasts.
Notification of the resolution	Not sent for an alarm whose opening was never told.
Webhooks and flows	Still receive the alarm changes. A mute silences people, not systems.
Rules-card rules	Still run. A rule that reacts to the alarm still acts. To stop rules, use Manual mode (see Manual and Auto modes).

A mute can cover:

• every alarm of the device, including alarms raised by flows and rules, or
• one alarm rule of the device’s profile.

A mute lasts until its end time. The longest mute is 90 days, so a forgotten mute cannot silence a device for good. A new mute applies within about 10 seconds.

Set a mute

Mutes are set through the API; there is no button for them in the app in this release. You need Mute the alarms of a device (Admin by default). Use an API key with that right; see Authentication.

POST /tenant/{tenantId}/api/iot/devices/{deviceId}/alarm-mute
Content-Type: application/json

{
  "until": "2026-11-20T18:00:00+01:00",
  "reason": "Pump overhaul, ticket 4711"
}

Field	Meaning
until	Required. When the mute ends, as a date and time with offset. Must be in the future and at most 90 days away.
ruleId	Optional. The id of one alarm rule of the device’s profile. Absent or null: every alarm of the device.
reason	Optional, up to 500 characters.

Answers:

Message	Cause
“A mute must end in the future.”	until is now or in the past.
“A mute may last at most 90 days.”	until is too far away.
“Device not found.”	The device does not exist in your organisation, or is deleted.
“Alarm rule not found.”	ruleId is not a rule of the device’s profile.

See and lift mutes

GET    /tenant/{tenantId}/api/iot/devices/{deviceId}/alarm-mute
DELETE /tenant/{tenantId}/api/iot/devices/{deviceId}/alarm-mute
DELETE /tenant/{tenantId}/api/iot/devices/{deviceId}/alarm-mute?muteId={muteId}

GET lists the mutes in force with muteId, ruleId, until, reason, who set it and when. DELETE without muteId lifts every mute of the device; with it, only that one.

When a mute ends, notifications resume with the next alarm change. An alarm that opened during the mute and is still open is not announced again, but reminders scheduled for it go out once the mute is over.

Audit

Every mute and every lifted mute writes an audit entry on the device: who, when, the rule (or all), the end time. See Audit log.

Alternatives

Need	Use
Stop one alarm type for every device of a profile	Switch the rule off on the profile’s Alarm rules tab (and back on later). Alarms are then not recorded either.
Stop the Rules-card rules of a site while people work there	Manual mode on the site. Alarms keep working.
Quieter alarms, not silent ones	Raise the rule’s minimum severity, or add debounce. See Debounce, hysteresis and dampening.