> For the complete documentation index, see [llms.txt](https://luum.io/llms.txt).
> Canonical page: [Custom Programming Guide](https://luum.io/docs/amatis/programming/custom-programming).

LUUM.IO

# **Custom Programming Guide** - GUIDE

## About This Guide

Welcome to the custom programming guide for the Amatis Lighting Control System. In this guide, you'll find straightforward explanations of how scenes work and step-by-step instructions on how to set them up. Whether you're looking to use the default scenes, adjust current ones, or create brand new scenes to match your needs, this guide will walk you through the process with ease.

## Necessary Parts

The following parts will be necessary to complete this guide:

1. A functional Amatis lighting controls system
2. Amatis wireless control devices, such as motion sensors, wall switches, or input devices
3. Amatis wireless load controllers or X-PoE switches

## System Setup

Before getting started with custom programming, ensure all devices are properly connected. The devices should be in locations within the app, and configuration options such as motion and switch control already applied (if editing existing scenes). Once a location in the app has been set up, and devices are in the location, custom programming can begin.

![system_setup](https://luum.io/guides/assets/custom-programming-guide/system_setup.png)

## Step 1: Create New Scene

To create a new scene, navigate to the "Scenes" tab of a location and select "Add New Scene":

![new_scene](https://luum.io/guides/assets/custom-programming-guide/new_scene.png)

> **Default Scenes**
> If any options have been applied in the Configuration tab, default scenes will have been generated. These scenes can be edited by clicking on them and following the same instructions below. Any scene can also be deleted, including default scenes generated by Configuration. See Deleting a Scene below.
>
Give the scene a name, and select "Create Scene":

![scene_name](https://luum.io/guides/assets/custom-programming-guide/scene_name.png)

## Step 2: Triggers

Inside a scene, you will see 'Triggers' and 'Actions'. Triggers are events that cause the scene to activate. To add a trigger, select "Add New Trigger":

![new_trigger](https://luum.io/guides/assets/custom-programming-guide/new_trigger.png)

In this example, there already is a wall switch with default switch control doing the on and off scenes. However, there are two inputs from an Amatis AM-SW6 wireless input device in the location as well. Button one of the input device will be used to trigger this custom scene.

Select the input device in the "Device" field. To trigger on the press of button one, select "Button1". Select "Save Trigger" to save the trigger to the scene:

![set_trigger](https://luum.io/guides/assets/custom-programming-guide/set_trigger.png)

> **Multiple Triggers**
> Scenes can have as many or as few triggers as desired. They can even have no triggers if they are intended to be triggered from the cloud.
>
## Step 3: Actions

Actions are the changes that occur when the scene is activated. Once the triggers are in place, select "Add New Action" to add an action to the scene:

![new_action](https://luum.io/guides/assets/custom-programming-guide/new_action.png)

In this example, there are two X-PoE ports in the location. This scene will be programmed to set those ports to 50%.

Select the output device in the "Device" field. To control the level of an X-PoE port, select "Set Auto Level Port (mask,%,fade)". Then select "Save Action" to save the action to the scene:

![set_action](https://luum.io/guides/assets/custom-programming-guide/set_action.png)

Once the action is saved, edit the action by dropping it down. In this action, the ports to be controlled can be defined, as well as the level they should go to and fade time to use. Select "Save Changes" to update the action:

![action_settings](https://luum.io/guides/assets/custom-programming-guide/action_settings.png)

## Step 4: Sync & Test

Once the scene is configured, sync the devices to upload the new programming. Test the scene by opening its row's Actions menu (⋮) in the Scenes tab and selecting "Apply Scene".

## Deleting a Scene

Any scene can be deleted, including a scene you created and a default scene generated by the Configuration tab.

1. Open the location's Scenes tab.
2. Find the scene you want to delete and open its row's Actions menu (⋮).
3. Select Delete "&lt;Scene Name&gt;" for that scene.
4. Review the confirmation, then select Delete Scene.

![Scenes table with the Actions menu open and Delete Lights 50% highlighted](https://luum.io/guides/assets/custom-programming-guide/delete_scene.png)

![Delete Scene confirmation button highlighted](https://luum.io/guides/assets/custom-programming-guide/delete_scene_confirm.png)

The scene disappears from the app immediately after you confirm. Devices continue using their existing programming until you sync them.

## Deleting Triggers and Actions

To keep a scene but delete a trigger or action, open the scene from the Scenes tab. This also works for default scenes generated by Configuration.

1. Select the checkbox beside each trigger or action you want to delete.
2. Select Delete Selected, which appears alongside Cancel. Select Cancel instead to leave the items in place.

![An action checked with the Delete Selected button highlighted](https://luum.io/guides/assets/custom-programming-guide/delete_trigger_action.png)

Delete Selected removes the selected items from the app immediately, without a confirmation dialog. The scene remains. Sync the devices for the programming changes to take effect.

> **Sync After Deleting**
> Deleting a scene, trigger, or action changes what you see in the app immediately. Devices continue using their existing programming until you sync them. Sync the devices after deleting, then test the updated behavior.
>
## Scene Visibility

If you would like the scenes to be visible in the app, and have buttons to activate them, select the visibility toggle for any given scene in the scene tab:

![visibility_toggle](https://luum.io/guides/assets/custom-programming-guide/visibility_toggle.png)

This will create a button to activate the scene from the overview tab of the location:

![current_status](https://luum.io/guides/assets/custom-programming-guide/current_status.png)

## Advanced Options

### Trigger Definitions

Here are the definitions for the common available triggers in the Amatis system:

| Wall Switch Triggers |  |
| --- | --- |
| **Top Release <br> Bottom Release** | Trigger when the top or bottom button is released after a press |
| **Top Long Press <br> Bottom Long Press** | Trigger when the top or bottom button is pressed and held for an extended period |
| **Top Long Release <br> Bottom Long Release** | Trigger when the top or bottom button is released after a long press |

| Input Triggers |  |
| --- | --- |
| **Button# <br> Button#_Release:** | Trigger when the input is activated or deactivated after a short activation, with the number indicating the specific input |
| **Long_Press# <br> Long_Release#:** | Trigger when the input remains activated or deactivated after a long activation, with the number indicating the specific input |
| **ToggleOn# <br> ToggleOff#:** | Trigger when the input is toggled on or off using a short press, with the number indicating the specific input |
| **Button#_#Pulse:** | Trigger when the input is pulsed a certain number of times, with the first number indicating the specific input, and the second number indicating the number of pulses, up to 3 times |

| Other Triggers |  |
| --- | --- |
| **onBoot** | Trigger when the device initially powers up |

> **Advanced Triggers**
> Advanced triggers, such as motion, daylight, and load shed, should be enabled through the configuration tab and the generated scenes may be edited if necessary.
>
### Action Definitions

Here are the definitions for the common available actions in the Amatis system:

| Output Level Actions |  |
| --- | --- |
| **Set Auto Duty/Level <br> Manual Duty/Level** | Set the target light level and fade time (on specified channels, if applicable) |
| **Set Auto Duty/Level Port <br> Set Manual Duty/Level Port** | Set the target light level and fade time on specified ports<sup class="docs-footnote-ref">[1](https://luum.io/docs/amatis/programming/custom-programming#fn-1)</sup> |
| **Halt Fade** | Stop any ongoing fade (on specified channels, if applicable) |
| **Cloud Dim** | Allow control via the in-app slider |

> **Auto vs. Manual Duty/Level**
> Set Manual Duty/Level will ignore daylight control, Set Auto Duty/Level will go to the target level and allow daylight harvesting to take over if enabled.
>
| Color Tuning Actions |  |
| --- | --- |
| **Set Target Color <br> Set Target Color Auto** | Set the target color temperature, target level, and fade time on specified ports<sup class="docs-footnote-ref">[1](https://luum.io/docs/amatis/programming/custom-programming#fn-1)</sup> |
| **Increment Color <br> Decrement Color** | Increase or decrease the color temperature by a specified amount on specified ports<sup class="docs-footnote-ref">[1](https://luum.io/docs/amatis/programming/custom-programming#fn-1)</sup> |

Color tuning is only available on X-PoE switches and should be used exclusively when adjusting port levels for color-tunable fixtures. This prevents both fixture channels from being set to 100% simultaneously, which would result in excessive brightness. To ensure proper operation, the X-PoE switch channels must be set with load types that match the warm and cool LED color temperatures of the fixture.

> **Advanced Actions**
> Advanced actions, such as device modes, device calibration, and functionality enabling, should be reserved for very unique use cases. More information on these actions can be requested from the support team.
>
<span id="fn-1">Applicable to X-PoE devices only.</span>

## Related Information

### Technical Support

Questions about scenes can be sent to [support@luum.io](mailto:support@luum.io). Include the site and the step you are on.

### Document Feedback

While we have taken great care to ensure the accuracy and completeness of this document, we welcome your feedback and suggestions. If you notice any errors or omissions, or feel a topic could benefit from further explanation, please email your feedback to [support@luum.io](mailto:support@luum.io).

### Revision History

| Date | Revision | Notes |
| --- | --- | --- |
| 11/17/2026 | B | Added instructions and screenshots for deleting scenes, triggers, and actions, including default scenes and syncing devices after deletion. |
| 11/3/2026 | A | Converted to the current guide format. |

### Disclaimer

All rights, title, and interest in and to this guide, including without limitation all copyright, trademark, patent, trade secret, and other proprietary rights, belong solely and exclusively to Luum.io and/or its licensors. This guide is provided solely for the purpose of creating and editing scenes in the Amatis app, and no license or other rights are granted or implied hereby. No part of this guide may be reproduced, distributed, or transmitted in any form or by any means, including photocopying, recording, or other electronic or mechanical methods, without the prior written permission of Luum.io. The contents of this guide are subject to change without notice. The information contained herein is provided on an 'as is' basis and is for informational purposes only. Luum.io makes no warranty, express or implied, as to the accuracy, completeness, or usefulness of this information, nor does it assume any legal liability or responsibility for the consequences of any errors or omissions therein. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

---

_©2026 Luum.io. All rights reserved._
