# Alerts

Ruuvi Cloud supports sending alert notifications based on user-configured settings. This page describes what accout levels have access to which alerts and how they are sent.

The alerts can be received as UI icon in apps or station.ruuvi.com dashboard, through push notification in mobile apps and emails.

<div align="left"><figure><img src="/files/r3RurZKfMcFNHYG1RxvE" alt="" width="160"><figcaption><p>UI Notification</p></figcaption></figure></div>

<div align="left"><figure><img src="/files/GX6eW0VaXKibuJX6Jvpn" alt="" width="375"><figcaption><p>Push notification</p></figcaption></figure></div>

<div align="left"><figure><img src="/files/5S6F8vX389RndH8mRvC7" alt="" width="375"><figcaption><p>Email alert</p></figcaption></figure></div>

<table><thead><tr><th>Alert channel</th><th width="100">Free</th><th width="100">Basic</th><th width="100">Pro</th><th width="100">Business</th></tr></thead><tbody><tr><td>UI Icon</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr><tr><td>Push notification</td><td>No</td><td>Yes</td><td>Yes</td><td>Yes</td></tr><tr><td>Email</td><td>No</td><td>No</td><td>Yes</td><td>Yes</td></tr></tbody></table>

There are different type of alerts you can configure for yourself, the table below lists which alerts are allowed for which account types.

Alerts marked with \* are under development and expected to be available by summer 2023.

<table><thead><tr><th>Alert type</th><th width="100">Free</th><th width="100">Basic</th><th width="100">Pro</th><th width="100">Business</th></tr></thead><tbody><tr><td>Temperature</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr><tr><td>Humidity</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr><tr><td>Air pressure</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr><tr><td>Movement</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr><tr><td>Signal level</td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr><tr><td>No data*</td><td>No</td><td>No</td><td>Yes</td><td>Yes</td></tr><tr><td>Delayed trigger*</td><td>No</td><td>No</td><td>No</td><td>Yes</td></tr></tbody></table>

Alerts trigger once and wait until they are resolved before they can be triggered again. However, reconfiguring an alert such as adjusting alert trigger limits or disabling and re-enabling it will always resolve alert, which leads to a new trigger if the alert condition remains after reconfigruration. Image below shows trigger-events with red arrow and resolve-events with blue arrow.

Additionally, alerts can trigger at most once per hour for user and alert per sensor, this reduces spam in case where e.g. fridge swings back and forth the alert thresholds. Business users can configure delay before triggering an alert for e.g. walk-in freezers which might spike up for a short while when someone enters and then drop back to allowed range.

<figure><img src="/files/Prr0p9BKi0fAiDNh2ZVg" alt=""><figcaption><p>Alert triggering and getting resolved</p></figcaption></figure>

For full details of alert triggering and resolving logic, please see the following flowchart.

<figure><img src="/files/rK5nEm5DM0A601NQc0m5" alt=""><figcaption></figcaption></figure>

The time constants for throttles are:

| Feature                          | Time                                          |
| -------------------------------- | --------------------------------------------- |
| Gateway data processing interval | 1 minute                                      |
| Sensor data processing interval  | 1 / 5 / 10 minutes, depending on subscription |
| Alert triggered hysteresis       | 60 minutes                                    |
| Alert resolved hysteresis        | 5 minutes                                     |
| Offline alert scan interval      | 1 minute                                      |
| Alert trigger delay              | User defined                                  |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ruuvi.com/communicate-with-ruuvi-cloud/cloud/alerts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.