Commands

[exalate-issue-sync]

Support commands - these might reboot the device, restart the Player, or control external devices - e.g. turn off/on TV screen.

Commands are defined in three ways:

• Command code: these type of commands are configured in the Display Setting Profile on the CMS and sent to the display in the <commands> node of Register Display. They contain a code, a command string and a validate string.
• Shell command widget: these are on a Layout and either have a command code or a command string.
• Schedule commands: these appear in the return from the schedule XMDS call and always refer to a command code.

The command string should be executed by the Player as the user account running the player and if a validate string is passed the output of the command should be tested and a true/false notify status request sent with lastCommandSuccess property.

There are various uses cases for commands:

• Rebooting the device
• Turning a connected monitor on/off
• Executing a 3rd party script which does some other actions

The CMS and other players have support for various other functionality such as RS232 commands, Android intents, HTTP requests, etc. For the moment these are out of scope and can be addressed in a later issue.