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
  • 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
    • 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
  • Overview
  • Practical Use Cases
  • Video-Guide
  • Setting Up Time Restrictions
  • Create a Rule
  • Configure Time Restrictions
  • Multiple Time Frames
  • Using Multiple Actions with Individual Time Restrictions

Was this helpful?

  1. Portal
  2. Rules
  3. New Rule Engine

Time Restrictions

This guide explains how you can set up time based weekday restrictions for individual actions on Datacake Rule Engine.

Last updated 6 months ago

Was this helpful?

Overview

This document provides an overview of the Time Restrictions feature within the Datacake Rule Engine. This feature allows users to specify time frames during which particular actions within a rule are permitted to trigger. If an action's associated time restriction is not met, the action will not execute, even if the rule's conditions are satisfied.

Practical Use Cases

  • Work Shift Notifications: Set up rules to notify specific team members based on shift times.

  • Off-Hours Monitoring: Limit notifications to business hours or specific time frames to reduce unnecessary alerts outside working hours.

  • Daily or Weekly Alerts: Schedule notifications or actions to occur only on certain days, for example, to align with weekly reporting needs.

Video-Guide

Setting Up Time Restrictions

Create a Rule

  • Begin by selecting the product for which you want to create a rule. This rule will apply to all devices within that product.

  • Choose a trigger condition (e.g., when a new measurement is received).

  • Set the rule’s conditions, such as “temperature is less than 10°C.”

Select an Action

  • Choose an action type (e.g., Email, Webhook, SMS, or Downlink) to execute when the rule’s conditions are met.

  • Customize the action details, such as the recipient for an email.

Configure Time Restrictions

  • In Advanced Settings, enable Time Restrictions.

  • Define the time frame for the action, specifying:

    • Days of the Week: Select specific days (e.g., Monday through Friday).

    • Time Range: Set the start and end times for each selected day.

  • Example: Configure an email notification to send only from 12 a.m. to 8 a.m., Monday through Friday. Notifications outside this period will not be sent.

Multiple Time Frames

  • For actions requiring more complex schedules, you can add multiple time restrictions. For example, create multiple time ranges within the same day.

Using Multiple Actions with Individual Time Restrictions

The Time Restrictions feature allows you to configure different time frames for each action within a single rule:

  • Example: Set an Email action to trigger only during a specified night shift (e.g., 12 a.m. to 8 a.m.) and a Webhook action to trigger at any time.

  • This is ideal for workflows involving shift-based alerts or targeted notifications based on time-sensitive needs.