LogoLogo
  • Ruuvi Developer Documentation
  • Ruuvi Hardware
    • RuuviTag B
    • RuuviTag Pro
    • Ruuvi Gateway
    • Ruuvi DevShield
    • Ruuvi Connector Kit
    • TMP 117 External Sensor
  • Ruuvi Connector System
    • Introduction
    • Expansion boards
    • Cables
    • Connectors
  • Ruuvi Sensor Firmware
    • 1.2.12
    • 2.5.9
    • 3.X
      • 3.x Sensors
      • 3.x Heartbeat
    • Device Firmware Update (DFU)
  • Ruuvi Gateway Firmware
    • GW Getting Started
    • GW Web-UI
      • Greeting window
      • Internet connection settings
        • Connection via Wi-Fi
        • Connection via Ethernet
      • Software update
      • Automatic configuration download
      • Automatic updates
      • Access Settings from LAN
      • Cloud Options
        • Backend: HTTP(s)
        • Backend: MQTT(s)
        • Backend: Statistics
      • Time Synchronisation Options
      • Bluetooth Scanning Settings
      • Configuration completion
      • Authentication when accessing from LAN
    • GW Install custom firmware
    • GW nRF52811 Firmware
      • GW nRF52811 selftest
      • GW nRF52811 scanning
      • GW nRF52811 repeating
      • GW nRF52811 UART communication
  • GW ESP32 Firmware
    • GW ESP32 WiFi Hotspot
    • GW ESP32 Button
    • GW ESP32 LED
    • GW ESP32 HTTP Client
    • GW ESP32 MQTT client
  • GW Data formats
    • HTTP: Time-stamped data from Bluetooth-sensors
    • HTTP: Data from Bluetooth-sensors without timestamps
    • MQTT: Time-stamped data from Bluetooth-sensors
    • MQTT: Data from Bluetooth-sensors without timestamps
    • HTTP GET /history (with timestamps) and decoding
    • HTTP: Gateway status
    • Gateway configuration
  • GW Examples
    • Polling mode
    • Poll endpoint "/metrics"
    • Configuration update via API
    • Firmware update via API
    • Configuration download from a remote server via API
    • MQTT examples
    • Home Assistant
    • MQTT+AWS IoT Core
  • Communicate with RuuviTag devices via Bluetooth
    • Bluetooth advertisements
      • Data format 3 (RAWv1)
      • Data format 4 (URL)
      • Data format 5 (RAWv2)
      • Data format C5 (Cut-RAWv2)
      • Data format 8 (Encrypted environmental)
    • Bluetooth connection
      • DIS (Device Information Service)
      • NUS (Nordic UART Service)
        • Heartbeat transmissions
        • Read logged history
    • Real Time Transfer (RTT)
  • Communicate with Ruuvi Cloud
    • Ruuvi Cloud
      • User API
      • Gateway API
      • Internal API
      • Alerts
      • Cloud stored app settings
  • Ruuvi Community projects
    • Integrations
Powered by GitBook
On this page
Edit on GitHub
  1. Communicate with Ruuvi Cloud
  2. Ruuvi Cloud

Alerts

Ruuvi Cloud alerts

PreviousInternal APINextCloud stored app settings

Last updated 1 year ago

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.

Alert channel
Free
Basic
Pro
Business

UI Icon

Yes

Yes

Yes

Yes

Push notification

No

Yes

Yes

Yes

Email

No

No

Yes

Yes

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.

Alert type
Free
Basic
Pro
Business

Temperature

Yes

Yes

Yes

Yes

Humidity

Yes

Yes

Yes

Yes

Air pressure

Yes

Yes

Yes

Yes

Movement

Yes

Yes

Yes

Yes

Signal level

Yes

Yes

Yes

Yes

No data*

No

No

Yes

Yes

Delayed trigger*

No

No

No

Yes

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.

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

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

UI Notification
Push notification
Email alert
Alert triggering and getting resolved