Actions

Each action has the following base parameters:

Parameter Description
Description Name / description of the action
Enabled If disabled, the action won't be initialized
Category Action category
Action Type Defines the action type
Substitution Table The substitution table used for this action
Retry if failed If enabled, the action will be executed again if it has failed
Retry Count Amount of retries (0 = unlimited)
Retry Interval The retry interval

DMX Scene

The DMX Scene action allows to trigger DMX scenes using IP-based DMX controllers (Sunlite / ProLED / Nicolaudie devices).

Parameter Description Supports Placeholders
Device DMX Controller
Scene Index Scene Index number
Page Index Subpage within the scene
Command Scene On, Scene Dimmer Set, Scene Speed Set, Scene Color Set
Value Command value (0 - 1000) or hexadecimal RGB value for scene color set (e.g. #FF0000 for red) ✔️

Ember+ Consumer (Generic)

This action sets a value of any Ember+ provider to the event status or a custom value.

Parameter Description Supports Placeholders
Device The Ember+ provider
Path Path to the property (e.g. /Root/Input 1/Gain)
Value Desired value the property should be set to ✔️
Set to event status If enabled, the value will be set to 1 if the associated event is active, otherwise to 0.
Absolute Path OID of the property. This field can be left empty and will be populated automatically if the path is set.

Ember+ GPIO

This action sets a value of an Ember+ GPIO node to the event status.

Parameter Description
Device The Ember+ provider
GPIO Node Name Name of the GPIO node
GPI Number The GPI number
Absolute Path OID of the property. This field can be left empty and will be populated automatically if the path is set.

Ember+ Matrix

This action sets a crosspoint in an Ember+ matrix.

Parameter Description Supports Placeholders
Device The associated device
Matrix Name Name of the Ember+ matrix node
Source ID The source ID ✔️
Destination ID The destination ID ✔️
Channel Count Channel/crosspoint count
Absolute Path OID of the property. This field can be left empty and will be populated automatically if the path is set.

TIP

The channel count can be used to set multiple crosspoints at once (e.g. for stereo connects). The source and destination ID will automatically increase by one.

Example:

Source ID: 10
Destination ID: 50
Channel Count: 2
Resulting crosspoints: 10 -> 50 and 11 -> 51

File

The file action allows to generate arbitrary text-based files with dynamic content.

Parameter Description Supports Placeholders
Path Absolute storage path for the generated file ✔️
Filename Filename including extension (e.g. output.xml) ✔️
Content File Content ✔️

UNC paths are supported, but without authentication.

If the destination path requires authentication, the Broadcast Suite Core service needs be run as domain user with appropriate rights.

G&D KVM Crosspoint Addon

The G&D action sets a crosspoint in a G&D KVM matrix.

Parameter Description Supports Placeholders
Device The associated KVM device
Console Name Name of the console unit ✔️
CPU Name Name of the CPU unit ✔️

HTTP GET

Issues an HTTP GET Request

Parameter Description Supports Placeholders
Request URI URI for the HTTP Request ✔️

TIP

Depending on your network architecture, you might need to configure a proxy server before you can use this action.

HTTP POST

Issues an HTTP POST Request which can be used to send text, JSON or XML content to external systems or web services.

Parameter Description Supports Placeholders
Request URI URI for the HTTP Request ✔️
Content Type The content type used in the HTTP header
Request Body The body of the POST request ✔️

TIP

Depending on your network architecture, you might need to configure a proxy server before you can use this action.

IHSE Crosspoint Addon

This action sends one or multiple crosspoints to IHSE KVM matrices (draco series).

Parameter Description Supports Placeholders
Device IHSE KVM matrix
Crosspoints A list of crosspoints (one per line) ✔️

The crosspoint format is as follows:

[PREFIX]_[SOURCE_ID]:[PREFIX]_[DESTINATION_ID]

// e.g. CON_1003:CPU_3003

Livewire GPIO

Sets a GPO of an Axia xNode to the status of the associated event.

Parameter Description Supports Placeholders
Device The GPIO device
GPIO Port Number GPIO Port Number
GPO Pin Number The GPO (Pin) of the GPIO port

Log

This is a simple action to create custom log entries in the Broadcast Suite Core log file.

Parameter Description Supports Placeholders
Log Entry Custom log message ✔️

PhoneBox GPIO

This action triggers a GPI on a PhoneBox server.

Parameter Description Supports Placeholders
Device Associated PhoneBox Server
Source Port UDP Source Port (must match the PhoneBox configuration)
Destination Port Destination Port (must match the PhoneBox configuration)
GPI Number GPI Number
GPI Value true / false
Use Event Status If enabled, the event status (on / off) rather than the configured GPI value will be used

RS-232

With the RS-232 action, custom scripts can be sent to a serial port.

Parameter Description Supports Placeholders
COM Port Name of the serial port (e.g. COM1)
Baudrate Baudrate
Databits Amount of data bits
Stopbits Sets the stop bits
Parity Parity configuration
Script Custom RS-232 script. After each line, a line break (\r\n) is being sent to the serial port. ✔️
Interval The interval in milliseconds in which the commands are being sent

Script

This action allows executing custom scripts. Currently, it supports PowerShell (.ps1), Batch (.bat) and VB-Scripts (.vbs).

IMPORTANT

Please note that these scripts are being executed as the same user as Broadcast Suite Core. On Windows systems, this is usually Local System.

Parameter Description Supports Placeholders
Script Type Batch or VB-Script
Script Name Name of the script
Script Content The actual PowerShell or Batch Script ✔️

Send E-Mail

The Send E-Mail action allows sending custom notifications whenever a specific event occurs.

TIP

Before you can use this action, you need to configure an SMTP server in the system settings.

Parameter Description Supports Placeholders
To Address Recipient(s) of the e-mail. Multiple addresses can be added comma-separated.
Subject Subject of the message ✔️
Body Body of the message ✔️
Use HTML If enabled, HTML can be used in the e-mail body
Priority Message priority

SNMP TRAP

As the name suggests, you can send custom SNMP v1 TRAP telegrams.

Parameter Description Supports Placeholders
Destination Address Trap destination address
Destination Port Destination port (usually 162)
OID Trap OID (Object Identifier) ✔️
Value Trap Value ✔️
Community String The SNMP communtiy string (default: public)

You may use the OID of SLG Broadcast for custom traps: 1.3.6.1.4.1.38083.111 and children of this OID.

TCP

The TCP action is useful to send text-based telegrams, e.g., control commands, to an external system.

Parameter Description Supports Placeholders
Destination Address Destination address of the TCP packet
Destination Port Destination port
Payload The payload/content of the TCP packet. ✔️
Verify Response If enabled, the action waits for a response after sending the TCP telegram.
Expected Response If no response has been received or if the response does not match, the action will fail. ✔️

Telegram

This action sends notifications via the messaging platform Telegram.

Parameter Description Supports Placeholders
Recipients List of message recipient IDs (comma-separated). You can find your Telegram ID here.
Message The telegram message ✔️

TIP

Before you can use this action, you need to set an API key in the system settings.

Telnet

This action allows to send one ore multiple commands to a Telnet device.

Parameter Description Supports Placeholders
Device The associated device
Commands Telnet commands (one command per line) ✔️
Expected Response The expected response for the commands above. If the response contains this value, the action has succeeded.
Interval After each command, the telnet script pauses for the configured amount of time (milliseconds)

UDP

The UDP action is useful to send text-based telegrams, e.g., control commands, to an external system.

Parameter Description Supports Placeholders
Destination Address Destination address of the UDP packet
Destination Port Destination port
Payload The payload / content of the UDP packet. ✔️