Simple Hardware knowledge base
  • Welcome
  • Simple HW
  • CHAT
  • HOW TO PURCHASE THE DEVICES
    • Whom do we sell to
    • Pricing
    • Ordering and payment
    • Delivery
    • Shipping
    • Batteries shipping
      • Lithium transportation
    • Guarantee
    • Tracking
    • Packaging
    • Accessories
    • Documentation
    • Qualified and premium partners
    • Customization
      • Custom branding
      • Custom hardware and software
      • Custom device settings from the factory
    • Customer Portal
  • PROVISIONING AND DEVICE SETUP
    • Prerequisites
    • Step-by-step provisioning
    • Physical Installation
    • Reconfiguration of the devices
    • Troubleshooting
      • Troubleshooting process
      • Steps to troubleshoot:
    • Quality control
  • PRE-SALES SUPPORT
    • Radio zones and power
    • Whitepapers
      • Tapes whitepaper
      • Machine Monitoring Whitepaper
      • Location tracking whitepaper
      • Shock/Drop Detection Whitepaper
      • Reed Switch Whitepaper
      • Temperature (cold chain) monitoring whitepaper
    • Impact and Fall Protection Rating Test
    • Webinars
    • Blog posts
    • Datasheets and certifications
  • LPWAN
    • SIGFOX
      • Introduction to Sigfox
      • Connect to Sigfox
      • Sigfox coverage
      • How to Access Data From Your Devices
      • Monarch - Multizone Devices
      • Sigfox Support
      • Devices Ideal for Sigfox Atlas Tracking
      • Geolocation precision and possibilities
    • LoRAWAN
  • SENSORS
    • Button
      • Button in API 6
    • Accelerometer
    • Magnetometer
    • Reed switch
    • WiFi module
    • Gas
    • Dry switch
    • Leak
    • Light
    • Dry Switches
    • Temperature & Humidity sensors
    • Temperature Reaction Time
    • Devices for Temperature and Humidity Monitoring
  • NEXT/API 7 GENERATION
    • Introduction
  • SIMPLE/API 6 GENERATION
    • API 6
      • Before integrating API 6 devices
      • Overview For Beginners
      • Overview for Experts
      • Device states
      • WiFi User Modes
    • User Modes
      • Mode-Independent Information And Events
        • Heartbeats
          • Heartbeat 1 and Heartbeat 2
          • Heartbeat 3
        • Appended payload
        • Alerts
        • Sensor-triggered mode-independent events
        • Analog monitoring independent events
        • Other mode-independent events
      • Standard User Modes
      • Wifi User Modes
        • Press me WiFi
        • Guard me WiFi
        • Track me WiFi
        • Trace me WiFi
        • Don’t drop me WiFi
        • Reed switch on/off WiFi
        • Light on/off WiFi
        • Temperature threshold alert WiFi
        • Temperature change alert WiFi
      • Wifi Atlas User Modes
      • Wifi SuperLocal User Modes
        • Press me WiFi SuperLocal
        • Guard me WiFi SuperLocal
        • Track me WiFi SuperLocal
        • Trace me WiFi SuperLocal
        • Don’t drop me WiFi SuperLocal
        • Reed switch on/off WiFi SuperLocal
        • Light on/off WiFi SuperLocal
        • Temperature threshold alert WiFi SuperLocal
        • Temperature change alert WiFi SuperLocal
    • Uplink
    • Downlink Information
    • Encoding
      • 8 binary flags (byte bits)
      • SimpleTime
      • SimpleTemp
        • Here are all the SimpleTemp true temperature values
        • Here are all the SimpleTemp temperature hysteresis values
      • Accelerometer Data
      • Magnetometer data
    • API 6 Reset Triggers and Configuration Loss
    • API 6 Table
    • Factory Mode
    • Device Overview
      • Device Documentation
        • SimplePack
          • Legacy
            • SimplePack 2.0 Introduction
            • SimplePack 2.0 Accelerometer Lockout (Continuous Triggering Error)
            • SimplePack 2.0 User Modes (API 5)
            • SimplePack API 2, 4, 5 and 6 comparison
        • SimpleLeak
        • SimpleIndustry And SimpleMeter
          • SimpleIndustry
          • SimpleMeter
          • Battery Replacement
            • Battery Replacement in SimpleIndustry and SimpleMeter Devices
          • SimpleIndustry CO2 or SimpleIndustry CH4 Sensors
        • CheckFox
          • Starting with the CheckFox and the CheckFox Dashboard
          • All You Need to Know About the SIM Card in Your CheckFox and GSM connectivity
          • CheckFox Device User Guide
          • Sigfox Coverage Measurement Methodology With the CheckFox
          • CheckFox Troubleshooting Guide
          • Advanced
            • Technology Used to Run the CheckFox Dashboard
            • CheckFox Dashboard Data Export
            • CheckFox Log Data Interpretation
            • CheckFox Uplink Payload Description
      • Basic operations
        • SimplePack and SimplePack Plus: Basic operations
        • SimpleLeak: Basic operations
        • SimpleMeter/SimpleIndustry: Basic operations
        • What should you see on the Sigfox Backend
    • Working With Devices
      • Device Registration
      • Device Certificates
      • Device Downlink
      • Correct Device Placement
      • Radio Zone Switch
      • Battery longevity and levels
      • Magnet Range for SimplePack 4.0 Plus Motion & Door Sensor and others
        • Magnet: 30Ă—10Ă—1 (magnetic force: 1.1 kg)
        • Magnet: 40Ă—13Ă—1 (magnetic force: 1.5 kg)
        • Magnet: 20Ă—10Ă—2 (magnetic force: 2 kg)
        • Magnet: 30Ă—10Ă—2 (magnetic force: 2.6 kg)
        • Magnet: 30Ă—15Ă—2 (magnetic force: 3.3 kg)
        • Magnet: 40Ă—20Ă—10 (magnetic force: 20 kg)
    • IO Frog
      • First Message
      • Tracing
      • WiFi Tracing
      • Door Monitoring
      • Luggage Monitoring
      • Office Chair Monitoring
      • Leak Detection
      • Temperature Monitoring
      • Public Channel Setup
      • Manhole Cover Monitoring
  • TECHNICAL SUPPORT
    • Contact Support
    • RMA Process
      • Create RMA Number
    • Sigfox Backend Access
    • IO Frog Access
    • Consulting Services and Senior Project Management
Powered by GitBook
On this page
  • Introduction
  • Alert settings

Was this helpful?

  1. SIMPLE/API 6 GENERATION
  2. User Modes
  3. Mode-Independent Information And Events

Alerts

PreviousAppended payloadNextSensor-triggered mode-independent events

Last updated 2 years ago

Was this helpful?

The behavior of almost every mode-specific event sent as an uplink message by all API 6 user modes (with the exception of Stupid modes) can be further fine-tuned using a feature we call Alerts. Using alerts, you can customize how many messages and frames are sent, if events request downlink or disarm the device and how they are indicated by the LED and the beeper. You can also set up event repetition.

Introduction

Alerts are event extensions that allow various additional settings and can enable and customize event repetitions. In every user mode, up to 3 mode-specific events are predefined in the API 6 code to be alerts 1-3 (you cannot assign an alert number to an event manually). This allows you to choose one mode-specific event from a user mode you want to use and modify its behavior.

Example: events and their respective alerts

Event name (hex)

Assigned alert number

Start of movement (0x20)

1

End of movement (0x21)

2

Tracing tag (0x22)

3

Alert settings

Every alert is controlled by four registers - a total of 12 registers (from 0x23 to 0x2E).

Alert configuration is controlled by registers 0x23, 0x26 and 0x29 for Alerts 1, 2 and 3 respectively. The 8 binary flags (bits) of this one-byte value modify the following:

Bit

Set to 0

Set to 1

7

Single message

Message sent three times

6

Uplink only alert message

5

No change to device status

Disarm after alert is sent

4

Standard 3 frames transmitted

Only one frame message will be sent

3

Short beep indication turned off

Short beep indication turned on, bit 1 set to 0 has a higher priority than this

2

LED indication turned off

LED indication turned on

1

Beeper indication turned off

Beeper indication turned on

0

(empty)

(empty)

Example: If you set the Alert 1 configuration register (0x23) to value 0x82 (10000010) while using the Trace me user mode (0x04) above, the device would beep when movement is detected and a Start of movement event (0x20) would be sent three times.


Alert number of repetitions registers (0x25, 0x28 and 0x2B for Alerts 1, 2 and 3 respectively) control how many repeated event messages will be sent (the events will only be repeated with a repetition interval defined). The values of these registers are just numbers without any special encoding. Up to 256 repeated event messages can be sent (the device will still send one event even with value set to 0x00).

Example: If you set the Alert 1 repetition interval register (0x24) to 1 minute (0x41) and the Alert 1 number of repetitions register (0x25) to 10 (0x0A) while using the Trace me user mode (0x04) above, you would receive a Start of movement event (0x20) once the movement is detected and then every minute for a total of 11 messages (1 original and 10 repeated ones).


Alert delay registers (0x2C, 0x2D and 0x2E for Alerts 1, 2 and 3 respectively) control the delay of the event - the time from detecting an event trigger to the event being actually sent.

Example: If you set the Alert 1 delay register (0x2C) to 1 minute (0x41) while using the Trace me user mode (0x04) above, you would receive a Start of movement event (0x20) one minute after movement was detected.

Alert repetition interval registers (0x24, 0x27 and 0x2A for Alerts 1, 2 and 3 respectively) control the time period to resend the alert event (the event will only be resent if you’ve defined the number of repetitions). The values of these registers are encoded as a value in a single byte.

Trace me user mode (0x04)
SimpleTime
Alert message requests downlink