Setting Up Automation Schedules

Automation Schedules run a command at a set time, on set days – no one needs to remember to do it manually. Turn off a projector every night, power everything on before opening hours, or send a specific command on a recurring basis.

This is different from an Alert Rule, which reacts to a condition (like temperature crossing a threshold). A schedule reacts to the clock.

Creating a Schedule

1. Go to Alerts & Automation and find the Automation Scheduler section.
2. Click Add Automation Schedule.
3. Give it a name (e.g. “Nightly Shutter Close”).
4. Choose a Target Scope:
   • Node ID – one specific device.
   • Global – every device in the fleet.
   • Client – every device belonging to one client.
   • Display Type / Display Model – every device of that kind, wherever it is.
5. Choose a Command:
   • Reboot Node – restarts the Axion Displays Radar Node itself.
   • Power On / Power Off / Mute / Unmute – automatically routed to whichever control method that device actually has (RS232 or PJLink), so you don’t need to know which one it is.
   • If you targeted one specific Node ID, you’ll also see that device’s own available buttons listed directly – anything from a specific RS232 command to a PJLink function unique to that unit.
6. Set the Time and Timezone it should fire in. Picking a specific device automatically defaults the timezone to that device’s own configured zone.
7. Pick the Days it should run on (every day is selected by default).
8. Save. The schedule is active immediately.

Managing Existing Schedules

• Toggle the Enabled checkbox next to any schedule to pause or resume it without deleting it.
• Use the Edit button to change any part of a schedule.
• Use the Delete button to remove it permanently.

Reliability

Once a schedule has synced to a device at least once, that device keeps it cached locally and checks its own clock against it – so scheduled actions still fire on time even if that device’s internet connection happens to be down at that exact moment. Changes you make to a schedule sync out automatically the next time each affected device checks in.

Tips

• A schedule with no Node ID target (Global, Client, Display Type, or Display Model) applies to every device that currently matches – adding a new matching device later automatically picks it up too.
• If a device’s control protocol changes after a schedule was created, the schedule re-checks what’s actually available on that device each time it fires, rather than relying on what was true when you first set it up.