Triggers

Triggers allow you to automate actions within the Akiles system, transforming it into an access automation platform. This makes it possible to create intelligent behaviors between doors, sensors, and devices, automating processes that would normally require manual intervention. A trigger defines that when a specific event occurs, the system automatically executes an action on a Gadget, without requiring any member intervention. This allows you to create automations and automatic reactions between devices, sensors, and access points.

How do triggers work?

Every trigger is made of three parts:

Source event → Conditions (optional) → Action

1. Source event — the thing that starts the trigger (a sensor turning on, a door opening, a schedule beginning…).
2. Conditions — optional extra checks that must all be true for the action to run. If you don’t add any, the action always runs.
3. Action — what the system does in response (open a door, activate a relay, call an elevator…).

For example: If the entrance door opens (source), and it’s within office hours (condition), then call the elevator to the ground floor (action).

What events can start a trigger?

When you create a trigger you first choose what it triggers on. There are two options:

Gadget state or signal

The trigger starts when a Gadget changes state or emits a signal:

• State — a condition that stays on or off over time. For example a door being open or closed, or a wired sensor being active or inactive. The trigger fires the moment the state changes.
• Signal — a momentary event, like a button press or a short pulse from a wired input. It happens at a single instant, with no “on” or “off” that lasts over time.

Schedule

The trigger starts when the current time enters or leaves a Schedule. You choose:

• The Schedule (for example, office hours: Monday–Friday 9:00–18:00).
• When it fires: Entering schedule (at the start of the allowed period) or Leaving schedule (at the end).

This lets you run actions automatically at the boundaries of a schedule, with no sensor or manual action involved. For example, unlock the main entrance every morning when office hours begin, and lock it again when they end.

Power cuts and clock sync: the device re-applies the current schedule state whenever it powers on, as soon as it knows the correct time. For example, if a door is set to unlock during office hours and the device loses power in the middle of the day, it will unlock again by itself once it powers back on and syncs its clock (because the current time is still within the schedule). It does not, however, replay boundaries it missed while it was off: if the device was powered off across the whole schedule period, it simply applies the state that’s correct for the moment it comes back. For this reason, schedule triggers work best with actions that set a clear state (such as unlock or lock) rather than actions that toggle back and forth.

Conditions

Conditions act as gates: the action only runs when all conditions are met. They are combined with an “AND”, so every condition has to be true at the same time. If you add no conditions, the action always runs when the source event happens.

There are two types of condition:

• Current time is within schedule — the action only runs if the current time falls inside the chosen Schedule. Use it to restrict an automation to certain hours or days.
• Gadget is in state — the action only runs if another Gadget is currently in a given state. Use it to make one automation depend on the situation of a different door or sensor.

For example, you can make “when the motion sensor activates, turn on the lights” only run when it’s outside daytime hours, or make “when the button is pressed, open the gate” only run when the barrier is currently closed.

What actions can a trigger execute?

When a trigger runs, the system automatically executes an action on a Gadget, for example:

• Open a door
• Unlock an access point
• Activate a relay
• Close a door
• Call an elevator

These actions are executed without requiring a user to manually activate the Gadget. The action can be on the same device as the source, or on a different Akiles device.

Automations between devices

The source Gadget and the target Gadget don’t have to be on the same device. An Akiles device can trigger an action on another Akiles device, so you can connect a sensor to one device and react on another. When devices act on each other directly, they do so locally as long as they are within Bluetooth range of one another.

Trigger logs

All trigger executions are recorded in the Logs section. This allows you to see: what event was detected (for example a sensor turning ON or OFF, or a schedule beginning), what action was executed, and when it occurred.

Who can create triggers?

To create or manage triggers you need Superadmin permissions in the Admin Panel. If you don’t have them, request them from your Akiles consultant or contact us at support@akiles.app.

Practical examples

Automatic opening between doors

When a door is detected as open, the system can automatically open another one.

If the entrance door opens → automatically call the elevator to the entrance floor.

Automation with sensors

If a sensor detects presence in a specific area, the system can automatically activate an access point.

If the motion sensor detects presence → open the garage door.

Integration with external systems

If an external device wired to the system changes state, Akiles can react automatically.

If an alarm sensor is activated → unlock an emergency exit door.

Scheduled opening and closing

Using a Schedule as the source, you can open and close access points automatically at set times.

Entering the “office hours” schedule → unlock the main entrance. Leaving the “office hours” schedule → lock the main entrance.

Automation limited to certain hours (with a condition)

Add a schedule condition so an automation only runs at the times you want.

If the motion sensor activates, and the current time is within the “night” schedule → turn on the corridor lights.

Automation that depends on another door (with a condition)

Add a gadget-state condition so an automation only runs depending on the state of another Gadget.

If the exit button is pressed, and the barrier is currently closed → open the barrier.