Start a response when something happens
An event trigger starts an Application on its own: when a radar sees a drone, when a battery drops below a limit, or when a device goes offline. The Quickstart built one for radar detections; this guide covers every kind and how alarms compete.
Before you begin
- A console account with the organization administrator role.
- An Application to start, for example the one from the Quickstart.
Pick what starts it
Open Manage›Access & Integrations›Event Triggers. Each trigger shows what it waits for, which Application it starts, its priority and when it last fired.
| Event type | Fires when |
|---|---|
| Detection | A sensor reports an object, for example a radar seeing a drone. You set the object type, a minimum confidence and optionally the sensor. |
| Telemetry Threshold | A reading of one device crosses a limit, for example batteryPercentage below 25 or windSpeed above 12. |
| Asset Status | One device's status matches, for example isOnline is false, or a given operationalMode. |
| Webhook | Another system calls a secret address. See Start runs from other systems. |
| Integration bridge | A message arrives through the Integration Hub. See Integration Hub. |
Create a trigger
Name it and choose the event
Select Add Event Trigger, enter a Name and choose the Event type. The event type can't be changed later.
Describe the event
Fill in what the event must look like.
For a detection, also choose Who responds:
- The detecting asset: the Application runs on the device that saw it.
- Chosen by Dispatch Rules: your Dispatch Rules pick a device, aimed
at where the object was seen. The Application receives that position as
latitudeandlongitude.
Choose what it starts
Pick the Application and the Skill. Under Only inside site, limit it to events inside one of your sites, or leave Anywhere.
Set how much it matters
Field Does Priority (0–100) Decides whether this alarm may take a busy drone. Default 75. Cooldown (seconds) After firing, the trigger waits this long before it fires again. Default 300. Auto-start Starts the run at once. Off: the run waits in Executions until someone selects Start. Active Switch the trigger off without deleting it. Select Create.
The object type must match exactly. A sensor reports your own drones as FRIENDLY_UAV, so a trigger on UAV doesn't fire for your responding drone. A trigger with no object type fires for every detection, your own drones included.
Detection, telemetry and status triggers are checked every 30 seconds, so a run can start up to half a minute after the event.
When alarms compete
Every run has a priority. A free drone is always preferred. A drone that is busy is only taken over by a run of strictly higher priority; the run that loses it is cancelled.
| Started by | Priority |
|---|---|
| You, by hand | 0 |
| A schedule | 50 |
| An event trigger | 75, or what you set |
An alarm at 75 takes a drone off a scheduled patrol, but not off another alarm at 75. Give your most important alarm a higher value, such as 90, so it can interrupt the others.
What you have now
- Responses that start on their own, from a detection, a reading or a status.
- Alarms ranked by how much they matter.
Troubleshooting
- The trigger never fires. Check that it is Active, that the object type matches exactly, and that Only inside site isn't excluding where the event happens.
- It fired once and then not again. The Cooldown is still running.
- It fired but no drone flew. No device was free, or every busy one held a run of equal or higher priority. Test the case in Dispatch Rules.
- Your own drone keeps triggering it. Filter on an object type such as UAV, not an empty one.