FlytBase
FeaturesSupportHomeNew Releases
  • Introduction to FlytBase
    • What is FlytBase?
    • FlytBase Advantage
  • Getting started with your FlytBase Account
    • Creating a FlytBase Profile
    • Creating an Organization
    • Joining an Organization
    • Managing Your Organization
    • Roles and Permissions
    • Site Management
    • Setup Private Cloud Storage (AWS S3)
  • Navigating FlytBase
    • Navigating Your FlytBase Platform
  • MAPS AND OVERLAYS
    • Maps on FlytBase
    • Map Overlays
  • Device Management
    • DJI Dock 3 + FlytBase – The Future of Autonomous Ops Starts Here
    • Add and Setup Your Device
      • Register Your DJI Dock 3
      • Register Your DJI Dock 1 and 2
      • Register Your Hextronics Docks
    • Activating Device Subscription
    • Device Management
      • DJI Docks
        • Overview
        • Device Maintenance
        • Diagnostics
        • Device Logs
        • Firmware
        • Device Settings
          • Drone Control
          • Collision Avoidance Sensing (CAS)
      • Hextronics Docks
        • First Flight with Hextronics Atlas/Hextronics Universal
        • Overview
        • Diagnostics
        • Settings - Drone and Dock
        • Settings - Failsafes
        • Settings - Precision Landing
    • AirSense
  • Pre-Flight Modules
    • Learn More About Failsafes
      • Emergency Landing
      • Alternate Landing Location
      • DRC Visibility
    • Platform Settings
      • Preferences
      • Flight Configuration
      • Key Bindings
      • Checklist
      • Privacy
    • Planning
      • Mission Planning
        • Path Mission
        • Grid Mission
        • Importing a Mission using KML file
        • WPML Mission
        • Mission Breakpoint
      • Mission Management
      • Mission Scheduler
    • Zones
  • TERRAIN AND ALTITUDE VISUALIZATION
    • Terrain Visualization
      • Terrain Visualization for Missions
      • Terrain Visualization for Go To Location (GTL)
    • In-Flight Altitude Visualization
  • In-Flight Modules
    • Setting Up Your First Flight
    • Flight Execution
      • Go to Location (GTL)
    • Annotations
    • How to Manage Your Flight Operations
      • Fleet Management
      • How to Control Your Drone
        • Manual Drone Controls
        • Drone Access Control
      • Payload Controls
        • Manual Payload Controls
        • Payload Access Control
    • Video Wall
    • Audio Chat
    • Alerts and Notifications
    • Speaker and Spotlight
    • Live Mission Recorder
    • Guest Sharing with Maps
  • AVSS Parachute Integration
  • Post Flight Modules
    • Reviewing Your Flight Logs
    • Gallery
    • Reports
  • FLINKS AND FLOWS
    • Flinks
      • Flinks: Alarms
      • Flinks : Live Streaming
      • Flinks : Data Processing
        • Mapping Using DroneDeploy
        • Mapping Using Pix4D
        • Mapping Using Strayos
    • Flows
      • Flows : Alarms
      • Flows : Operational Notifications
  • Discover More
    • General FAQs
    • Contact Technical Support
Powered by GitBook
On this page
  • Creating your Alarm Flink
  • Configuring your Alarm Flink
  • Alarm Source Logs
  • Modifying and Deleting an Alarm Source

Was this helpful?

  1. FLINKS AND FLOWS
  2. Flinks

Flinks: Alarms

PreviousFlinksNextFlinks : Live Streaming

Last updated 1 month ago

Was this helpful?

Alarm Flink seamlessly integrates various alarm sources such as sensors, cameras, fences to trigger real-time dashboard notifications or automated workflows via Flows when thresholds are met.

Creating your Alarm Flink

  • Navigate to the Operations Dashboard and click on the Navigation Drawer. From the dropdown menu, select Flinks.

Flink selection on the Operations Dashboard
  • In the Flinks library, set up your Custom Flink by choosing Alarms and clicking on Next.

  • Assign a name to your Flink. Optionally, add a description and an icon. Preview your Flink and click on Add.

  • Your new Flink will now appear in the My Flinks section.

Configuring your Alarm Flink

  • Go to My Flinks and select the Flink you just created. In the Configuration section you can assign a specific icon to the alarm.

  • After this move to the Alarm Sources section. All alarm sources associated with a Flink can be created and managed here. Click on Add Source to begin adding a new Alarm Source.

  • Here you can enter the name and a short description of the Alarm Source. After this click on Generate URL to proceed.

  • A follow-up window will display Source Details, which include:

    • A Trigger alarm Webhook URL. This URL can be used by an Alarm Source to send a notification to FlytBase.

    • A sample JSON Payload to provide details of the alarm when triggered. User can copy the JSON Payload format, paste it in the relevant environment (used for alarm sensor configuration), and modify the fields of the JSON Payload so that it accepts correct information.

    • Users can also test the recently created Alarm Source using the Test button. Testing the Alarm Source would only raise an alarm notification on the Integration Panel on the right side of the Dashboard.

    Note: Pressing the Test button will not trigger any Flows linked to the Alarm Source.

  • A Heartbeat URL to monitor and reflect the status of the alarm source on the FlytBase Dashboard. A Green status indicator in front of the alarm indicates an active alarm source.

These Webhook URLs can be used to integrate third-party sensors such as electronic fences, motion detection and thermal cameras with FlytBase.

  • To retrieve these URLs later, click on the Source Details button for the specific alarm source you want to integrate.

  • The Trigger alarm Payload (JSON) for the Alarm Source contains the following information:

//A sample JSON Payload
{
  "timestamp": 1708502346278, //Epoch time elapsed since Jan 1, 1970 in milliseconds
  "severity": 2,              //Integer value in the range 1-3, unknown is 0
  "description": "High temperature!", //User-defined string in double-quotes
  "latitude": 37.7749,        //Source Latitude in decimal format
  "longitude": -122.4194,     //Source Longitude in decimal format
  "altitude_msl": 100,        //Altitude at which the drone hovers over the source
                              //Value should be +ve, and Relative to Take-off (RLT)
  "metadata": {
    "sensor_id": "TempSensor12A", //User-defined additional data for the alarm
    "temperature": 50.2,          //Variable names in "", integers without quotes
    "battery_level": 80           //Strings in ""
  }
}

Alarm Source Logs

Next, click on the Alarm logs section, all alarms triggered for the selected Flink are recorded here. You can filter these logs by Alarm Source or by the date they were raised.

Modifying and Deleting an Alarm Source


  • After setting up a Flink and alarm sources within it, you will be able to see notifications on the Integrations Panel on the right hand side of the dashboard whenever an alarm source is triggered.

To modify an alarm source, tick the checkbox next to the specific alarm to first select it. Click the button located next to the Add Source button to update the name and description.

To remove one or more alarm sources, check the boxes next to the desired alarms. Click the button to delete the selected Alarm source(s).

Moving forward, you need to create an automation workflow to configure response action for the alarm sources from your drone fleet. To learn more about creating such automation workflows, refer to the documentation on.

Flows: Alarms
Adding a custom alarms Flink
Customizing your Flink
Configuring a new Alarm Flink
Adding a new Alarm Source
Trigger alarm webhook URL
Heartbeat alarm webhook URL
Alarm Logs
Editing an alarm source
Deleting an alarm source
Alarm notifications on the Integrations