An alarm rule says what raises an alarm, how serious it is, and who is told. Alarms here supplement your approved smoke, carbon monoxide and other safety systems. They never replace them.
Before you start
- You need the Manage IoT Alarms right. Without it you do not see the Alarms tab in the settings.
- To have people told in steps, create an escalation policy first, or create one from the rule. See Alarm Escalation Explained.
Create a rule
- Go to Settings → Devices (IoT) → Alarms → Rules and choose New rule.
- Give it a Rule name.
- Under What raises it, choose A reading is outside its limit, Something happens, A device stops responding or Raised by an automation. An automation decides when a rule of the last kind is raised: there is nothing to watch.
- For the other three, choose what the rule Applies to: One device, A room, A whole site, Every device of a type or Every device, then pick the device, room, site or type.
- Choose What to watch. For a reading, also choose how to Compare (goes above, goes below, becomes, stops being or changes at all) and the Value.
- Set the timings:
- For a reading: Reset margin means the alarm re-arms only once the reading is back past the limit by that much. Must last (minutes) raises the alarm only if the problem lasts that long. Clear after it has been normal for (minutes) stops an alarm from clearing and re-raising when a reading hovers at its limit.
- For a device that stops responding: Silent for (minutes).
- For something that happens: Clear by itself after (minutes), at least 1. The alarm still waits to be acknowledged.
- Choose the Severity: Critical (someone must respond now; it passes quiet hours), Major, Minor or Info. A new rule starts at Major.
- Write the Alarm title (needed, up to 200 characters) and, if you like, the Message and What to do about it (up to 500 characters each). To add a value such as the device's name, choose its chip under the title or message, for example
{{device.name}}. - Under Who is told, choose an escalation policy, or keep Built-in default. To make a policy now, choose New policy.
- Decide on Allow people to shelve this alarm, Watch only and Turned on. Watch only records the rule's alarms but tells nobody; it switches Turned on off, and the other way round.
- Choose Save rule.
Check it before you rely on it
- Choose Replay history to see how often the rule would have raised an alarm. Set From and To (it starts at the last 30 days) and choose Replay. It shows how many alarms it would have raised on how many devices, the busiest ten minutes, a chart of Alarms per day and how long a typical alarm lasted. "Nothing was sent. This is a replay of stored history." It uses your unsaved changes.
- Choose Preview who is told to see how many devices the rule matches and who each step reaches. It warns "Step 1 has nobody who can be told." when a step reaches nobody, and when someone cannot see all of the devices. A person who cannot see a device is not told about its alarms: give them access to the device.
Create rules from a template
- Open Devices (IoT) → Automations → Templates. This needs the Manage IoT Automations right too.
- Choose a template that includes an alarm rule, such as Freezer too warm, Smoke or carbon monoxide, Door left open or Device offline, and choose Choose.
- Fill in what it asks for, choose Review, check What this will create, then choose Review and create.
Everything a template makes starts turned off, so you can check it first. Turn a rule on with its switch in Settings → Devices (IoT) → Alarms → Rules.
On KamoMobile
KamoMobile has the same rule editor: open Devices (IoT), then Settings → Alarms → Rules, and choose New rule. You can also reach Alarm rules from the bottom of the Alarms screen.
Result
The rule is listed with what raises it, its severity, the number of devices it watches and how many alarms are open. Its switch turns it on and off. When it raises an alarm, the alarm appears on the Alarms tab and people are told as its policy says.
If it doesn't work
- "Another item already has this name." Choose a different name for the rule.
- "This rule matches no devices yet." The rule is saved, but it watches nothing. Check the devices you chose, and that they report what you picked.
- Turning a Critical rule off, or lowering its severity, asks for your password.
Good to know
Alarms depend on device vendors, networks and power, and can be delayed or fail. See IoT Is Not a Safety System.
관련 기사
이 질문에 대한 답변을 다른 가이드.
Alarm Escalation 설명
에스컬레이션은 알람이 누군가에게 도달하도록 합니다. 아무도 그것을 인정하지 않는 경우, 다음 단계는 더 많은 사람들을 말한다, 등. 정책은 단계의 목록입니다. 에스컬레이션 정책은 8 단계까지 있습니다. 각 단계는 그것이 일어날 때, 누가 말하고 방법. 첫 번째 단계는 즉시 될 수 있습니다. 앞으로 각 단계는, 경보가 올려진 후에 대부분의 7 일에서 나중에 옵니다. 나중에 단계는 아무도가…
Acknowledge에 대한 방법
알람은 당신이 그것을 본 다른 모든 것을 말해주고 그것을 취급합니다. 또한 정책의 다음 단계에 대한 경보를 중지합니다. 시작하기 전에 Acknowledge IoT 알람이 오른쪽과 알람의 장치에 액세스해야합니다. 장치 (IoT)을 열 수 있는 사람은 알람 탭을 볼 수 있지만, 이 권리는 Acknowledge를 참조하십시오. 웹에서 1. 열린 장치 (IoT) → 알람, 또는 알람 알림에서…
자동화를 만드는 방법
자동화는 무언가가 일어날 때 그것의 자신의 단계 실행합니다: 독서는 한계를 교차하고, 장치는 사건을 보고하거나, 시간 도착합니다, 태양 상승 또는 세트, 위치 변화 형태, 또는 경보 변화합니다. 시작하기 전에 IoT 자동화가 필요합니다. 자동화 탭을 볼 수 없습니다. 자동화는 당신의 접근으로 실행합니다. 당신이 그것을 저장하면, 그것은 당신이 할 수있는 단지 할 수 있습니다. 당신이…
IoT Is Not a Safety System
IoT Devices is not an alarm-monitoring, emergency-response or life-safety system. This article says what that means in practice. What not to rely on it for Protecting life, health or property. Detecting or responding to…
과거 활동에 대한 자동화를 테스트하는 방법
자동화가 생동하기 전에 저장 된 역사를 다시 재생하여 종종 실행되는 방법을 볼 수 있습니다. 아무것도 보내거나 변경되지 않습니다 : 저장 된 역사의 재생입니다. 시작하기 전에 IoT Automations를 올바르게 관리하고 빌더에서 자동화가 열립니다. 저장될 필요가 없습니다: 재생은 당신의 unsaved 변화를 이용합니다. 지원하다 1. 건축업자의 바닥에, Replay 역사를 선택하십시오.…
Site Modes Explained
A site mode is the state a site is in. Every site starts in Occupied. The built-in modes are Occupied, Away, Night and Holiday, and your organization can add its own. Automations can read a site's mode and change it.…
