Datacake Docs
  • Welcome
  • Get Started
  • Changelog
  • Best practices
    • Best practices: Getting started
    • Best practices: Resolution (Timeframe)
    • Best practices: Dashboards
    • Best practices: Reports
    • Best practices: Grouping Devices
  • Datacake LNS
    • Getting Started
    • Gateways
      • Milesight LoRaWAN Gateway - UG6x
      • RAKwireless WisGate Edge Light 2
    • Devices
    • Add Devices without Gateway
  • Wireless IoT Hub
    • Overview
    • Datasheet
    • Getting Started
  • Device
    • Product
    • Configuration
    • Claiming
    • Historical Data
    • Database
      • Configuration Fields
      • Fields
        • Manual input
        • Field Roles
        • Formulas
        • Mapping Fields
      • Data retention & Datapoints
      • Examples
        • Mapping 4-20mA Signals
        • Converting Units
  • Dashboards
    • Global Dashboards
      • Setting Homepage
    • Device Dashboards
    • Multi-Device Dashboards
    • Widgets
      • Value Widget
      • Chart Widget
      • Image Map
      • Map Widget
      • Text Widget
      • SOS Widget
      • Boolean Widget
      • iFrame Widget
      • Downlink Widget
      • Set Value Widget
      • Measurement List Widget
      • Heatmap Widget
      • Table Widget
      • Image Widget
  • Portal
    • Multi-Tenancy (Workspaces)
    • Reports
      • Energy Report
    • Administrators
    • Members
      • API Users
    • Security & Privacy
    • Billing
      • Support Packages
      • VAT Exemption / Tax ID
      • SMS Credits
      • Access Invoices
      • Unused time and Remaining time in Invoices (Prorations)
      • Codes
    • White Label
    • Rules
      • Legacy Rule Engine
        • Sending notifications via Telegram
      • New Rule Engine
        • Rule Engine Table Overview
        • Copy/Paste and Template Functionality
        • Advanced Rule Engine E-Mail and Webhook Templates
        • Time Restrictions
        • Actions
          • Set Value
    • Zones
  • Cake Red
    • Get Started
    • Overview
  • LoRaWAN
    • Get Started
      • CSV Import
      • Custom LoRaWAN Device
    • Configuring LNS
      • The Things Stack (TTN / TTI) Automated Setup
      • The Things Stack (TTN / TTI) Manual Setup
      • Loriot
      • Kerlink Wanesy
      • Helium
      • ChirpStack
      • Tektelic
      • Actility ThingPark
      • Senet
      • Milesight Gateway
      • KPN
    • Downlinks (LoRaWAN)
      • Set Time Frame
    • Securing Webhooks
    • Payload Decoders
      • Location and GPS
      • Access Gateway Metadata
      • Access Measurements
      • Global Variables
    • Using Cayenne LPP
    • Converting Payload
  • Generic API Devices
    • HTTP Downlinks
  • Integrations
    • MQTT
    • Particle
      • Get Started
      • Adding Integrations
      • Decoding Payloads
      • Calling Functions
      • Templates
        • Particle Tracker One
    • Incoming Webhooks
    • Outgoing Webhooks
      • Securing Outgoing Webhooks in Datacake
    • Golioth
    • Blues Wireless Notecard
    • Sigfox
    • Swarm Asset Tracker
    • Grandcentrix Modbus Cloud Connect
    • YuDash LYNX IoT Gateway
    • Dragino NB-IoT
      • Changing NB-IoT Bands
    • Hardwario CHESTER
    • 1NCE OS
  • API
    • Exporting Data
    • Record Measurements via API
    • Node RED to Datacake
    • Generate Access Token
    • Internal MQTT
      • Get Started
      • MQTT Documentation
      • MQTT over WebSocket
      • Example Code
    • GraphQL API
      • Using GraphQL
      • Device Creation
      • Tutorials
        • Read Group via Tags
  • Guides
    • Python
    • Send Slack Notifications
    • Forward Data to Cake Red
    • Multiple Data Feeds
    • Automated Dynamic Downlinks
    • Ingesting JSON Data into Datacake API Devices
    • Working with Default HTTP Decoder on API Devices and Code Examples
    • Accessing Measurements in Decoders
    • Connecting Datacake to Notion Using Zapier
    • How to set up and use location on non-GPS devices
    • How to integrate with AWS IoT Core
    • How to Schedule Mass-Downlinks (Multicast) using Datacake Rule Engine
    • How to Map Sensor Values to Ranges or Booleans, Strings using Mapping Fields
    • Understanding Internal vs. External MQTT Brokers on Datacake
    • Sending UDP Messages between 1NCE OS and Datacake
    • Concepts of LoRaWAN Payload Decoders on Datacake
    • How to check if a value stays above or below limits for given time
Powered by GitBook
On this page
  • Set Value
  • Overview
  • Example

Was this helpful?

  1. Portal
  2. Rules
  3. New Rule Engine
  4. Actions

Set Value

Last updated 6 hours ago

Was this helpful?

Set Value

This guide shows you how you can use the set value feature.

Overview

The action "Set Value" is a very powerful feature in the rule engine. You can set a value of a specific field regarding a measurement of another one. In the example below you can see how to use this for alarming.

We have a short video reviewing the feature:

General

  • Description is meant to be used for documenting and better understanding of you own rules.

  • At Set value on the triggering device you can select a field where you want to set a value to. If you have selected a field, you can set a value afterwards.

  • If you want to set a value on a specific device you can define which value should be applied to which field of a single device. This can be useful if you have an overall alarming/monitoring device for several devices combined.

Advanced Settings

  • Execute action when conditions are becoming fulfilled: If enabled, the action is executed when conditions are becoming fulfilled.

  • Execute action when conditions are fulfilled consecutively: If enabled, the action is executed a second, third, etc., time when conditions are fulfilled consecutively.

  • Timeout between multiple executions when conditions are fulfilled: Set the minimum amount of time in seconds that must pass before the action is executed again.

  • Execute action when conditions are no longer fulfilled: If enabled, the action is executed when conditions are no longer fulfilled. This setting can be used to revert actions, e.g., to send an all-clear notification.

Time restrictions

See Time Restrictions for detailed information.

Example

Video Guide

Video will be attached shortly.

Step by step

If you have no rule created yet, create a new rule by navigating to Rule Engine -> Add Rule.

In this example we will react to a new device measurement so select the template for New Measurement Recorded.

Choose a name for your new rule.

Set a preferred filter for the devices so that you can apply this rule to a single device or specific group of devices.

The "Selected Triggers" are set for "New Measurement" by default in this template. You only need to define which fields you want to observe. So please choose a field for "Trigger Only On Specific Measurements". In the next step you define the conditions when to set a value. Please define a condition for a field you chose earlier.

Last but not least, you can define an Action to be executed when the condition become true. Please click "Add Action" and select "Set Value". Then click on next.

Select the field you want a value to be set, define the value and hit "Update Action". Now you are ready to go!

Summarized in the shown example we observe the field "Temperature". When a new measurement is recorded, there is a check if the new measured Temperature is below or equal to 0°. If this is true, we set another field "ALARM_TEMPERATURE" to true.