Automation actions

Topic Progress:

Making things happen

Once your automation starts it can begin triggering any of the devices connected that have a control widget in the devices list. This can be as simple as turning a few lights on or it can be a complex series of events, performing actions and then waiting for a time delay and performing further actions.

Automation delays are counted from the start of the automation, not from the last delay time. That means that to trigger 3 events 10 seconds apart you would need to add instant actions, then a 10 second delay, then a 20 second delay. This ensures there is never an unknown time due to slower actions (like dimming a light).

Motion is detected in a room

Multi reports tripped to the Nero gateway

Automation turns on room light

Timer counts down 30 minutes

Automation turns off room light


The automation is triggered when the Nero Multi in the bathroom trips (detects motion) whether it is armed or disarmed.

When using the Nero Multi as the trigger for a sensor light ensure that the timeout (Parameter 3) is configured for approximately 60-120 seconds. This will ensure new motion is detected and sent to the gateway to prevent the light turning off if people are still in the room.


The gateway sends an immediate command to the associated light to turn on. If multiple lights need to be turned on messages will be sent to each light to turn on.


The gateway starts a timer counting down the 30 minute delay. If the sensor re-trips within this time it will send a new update the to the gateway and the gateway will re-initialise the timer, starting back at 30 minutes.

Don’t forget that the Multi will also reset its timer when it detects new motion within the timeout period. This is why you should use a relatively short time when configuring sensor lights. We recommend having sensor light periods no shorter than 15 minutes for best reliability.


After the timer ends the gateway will send out the turn off command to the associated devices.