Myriad Playout is capable of sending a wide variety of notifications for a variety of reasons, and each Notification can be sent to a different destination.
Myriad can also send notifications via several different "Channels", and you can mix and match to send notifications via different methods to different users.
- Email: The most common, this will send a simple email notification to the specified recipient(s) via email
- Twitter DM: This will send a Twitter Direct Message to the specified person via Twitter's messaging platform
- Pushover.net: This sends a notification via the Pushover.net platform which will then notify the specified recipients via the pushover app installed on their mobile phone. You can also specify different priority levels for the notifications.
One of the great advantages to the Pushover system is that notifications can be given a Priority level that allows end users to control how dramatically then will be notified, even able to bypass Do Not Disturb settings in some cases, which is ideal for broadcast emergencies. For more about the Pushover system, see https://www.pushover.net
Setting up Notifications
There are 2 parts to settings up Notifications - configuring the Notification Channels, and then configuring the Notification Events and Subscribers for each notification.
Configuring Notification Channels
A Notification Channel is the actual method that messages will be sent via - for example, an email notification requires the Email Channel to be configured with the correct email server to send via, Twitter requires you to authorise Myriad to send Twitter DMs on your behalf, and Pushover needs an API key so it can send notifications.
To configure the notification channels, in Myriad Playout, click on Settings, then Database Settings>Database Settings, then click on the Notifications tab:
To enable a channel, you tick the box in the On column, then click on the Edit cog.
Configuring the Email channel:
To configure Myriad to send emails, you will need the email server details from your internet service provider or email provider - most commonly this will be called an "SMTP Server".
In the screenshot below, we have configured Myriad to send emails via Office 365, and we have to give Myriad the email address we will send from, the username and password for our email account, as well as the server name (smtp.office365.com) and the "port" number to send it to - in this case port 587 and using the SSL/TLS option:
Every email provider is different, so you will need to check with your provider for the correct settings.
Once you have entered the details, click the OK button and you can test the Channel by clicking the Test button and entering an email address to send a test email to.
Configuring the Twitter Channel:
Configuring the Twitter Channel is a lot easier - just click the Edit Cog button and this will launch the Twitter website in your normal desktop browser, and you will be prompted to login to Twitter, then you just need to click the "Authorize app" button:
After you click Authorize App, you will then be shown a numeric PIN that you need to type into the prompt that Myriad is displaying. Type in the number and click OK.
Once this is done, the Twitter Settings Summary should show "Authorised" and you can click the Test button to send a test Direct Message to a specified Twitter screenname.
Configuring the Pushover channel:
Before you can configure the Pushover channel, you will need to create a Pushover account - the easiest way to do this is to download the Pushover Android or iOS application from the App store and create your account from there, but you can also do it from the Pushover website.
Once you have setup an account, you need to get an "Application/API Token" from the pushover website. Enter a useful name such as "Myriad Playout v5" and then check the box to agree to the Terms and Conditions and click "Create Application":
Once created, the browser will then show you the Application "API Token", copy all of this text and paste it into the prompt Myriad is showing and click OK:
To test Pushover notifications, you will need the pushover "User Key" for the person you want to send the notification to. You will need to ask your users to locate this information in their Pushover account and give you the details:
Once you have completed configuring the Channels, click the OK button to save the Database Settings.
Configuring Notification Events
Now that you have configured the Channels (above) you can now configure who should receive notifications of events. Underneath the Notification Channels section of the Database Settings Window you will see a number of "Custom Notifications" and also any Global Events - for example License expiring.
Custom Notifications: Custom notifications can be triggered from the Command language so you can use these to send any message you like. See the Command Language document that is available on the Myriad Playout help menu for more information on using Custom Notifications.
The majority of Notifications are actually configured Per-Station - for example, you might have different teams for each Station that you want to be be notified if the Log has to auto scheduled etc.
To edit these Station Notifications, go back into the Database Settings window, select the Stations tab, then double click on the Station to edit it's settings, and go to the Notifications tab:
For each event you can enter multiple email addresses, Twitter user names (starting with the @symbol) or Pushover User Keys (starting with "pushover:") all separated with commas.
When you have entered the details of the recipients, click OK to save the changes to the Station Settings.
For example, in the screenshot below we want to send a notification whenever a user deletes an Advert from the scheduled Log, and we want to send it to the management email address, as well as a Twitter DM and a Pushover notification:
We have also entered JUST a twitter account for the Log Auto-Restarting, and also set a Pushover alert with the highest priority "Emergency" (2) if the Scheduled Log runs out.
Please sign in to leave a comment.