Code 7 Radio

0 views

Skip to first unread message

Christina Smith

unread,

Aug 3, 2024, 5:34:25 PM8/3/24

to nactsadlodown

With just your streaming URL and other station metadata, you can follow a no-code process to make your radio station available to Alexa. Before you start, check the prerequisites listed in Steps to Create a Music Skill.

Radio station owners, not aggregators, are eligible to use the RSK portal. You should add a station only if you own and operate it. For example, in the United States, terrestrial radio stations are usually owned and operated by the entity that holds the station's Federal Communications Commission license.

If you have some software development experience, you can also use the Alexa Skills Kit Command Line Interface (ASK CLI) to create a radio skill. For details, see Create a new skill with the ASK CLI, and contact your Alexa Music representative.

ASK custom skills require the user to enable the skill in their Alexa app before they can play the station. RSK skills, however, are autoenabled. All a customer has to do is request the station. Alexa then makes a playback announcement such as "Playing 101.2 Daily Horoscopes," and starts the stream.

RSK supports features such as multi-room playback, and setup of alarms or routines that include radio station playback. These advanced capabilities are not currently available through ASK custom skills.

You can edit and update station metadata, such as station name, alternative names, streaming URL, and station logo artwork. (The only field you can't edit is the station ID, which is unique to each station in the RSK catalog.) You can update station metadata for a single station or a group of stations.

When you select all stations, you can make changes that apply to multiple stations. For example, if you want to change the Allowed Countries for all of your stations, select all stations and then update the Allowed Countries field in the multistation dialog box.

To capture all of the ways in which a customer might ask for your station, up to five alternative station names are allowed for each applicable language. Use commas to separate each alternative name. If the station name is not in English, include the English spelling. Don't use special characters such as accent marks and umlauts. Optional field.

A station's call sign consists of a series of letters. Call signs aren't used in some countries. If your station has no call sign, repeat the primary station name here instead. Don't leave the field blank.

To deprecate your custom skill after your RSK skill launches, choose Yes. Otherwise, choose No. Allow at least 4 months for disablement. In the meantime, don't remove the skill yourself, or the user receives an error message and can't initiate RSK playback. Instead, hide the skill (see Disable existing ASK custom skills).

Either the primary language spoken on the radio station or the primary language Alexa supports in the country to which the station broadcasts. For a list, click Supported languages. For details, see Supported Alexa Features by Country for International Version Echo Devices.

A locale refers to a language and the location (country) in which it's spoken. The language is usually represented by two lower-case letters, such as pt (Portuguese). The country is often represented by two capital letters, such as DE (Deutsch) for Germany or ES (Espaa) for Spain. Language and country codes are combined to form locale codes like es-MX (Spanish language, Mexico) and ar-SA (Arabic language, Saudi Arabia). Click Supported locales to see if your station's locale is represented in the list. If not, select the language Alexa supports in the country to which your station broadcasts. For details, see Supported Alexa Features by Country for International Version Echo Devices.

If you've already set up your station as a custom ASK skill, you can also make it available through RSK. Station requests from users who have already enabled your custom skill will continue to route to that skill. To set up the custom skill for eventual removal, find the Disable custom skill field, and then select Yes.

Allow at least 4 months for disablement. In the meantime, don't remove the custom skill yourself. If you do, existing users receive an error message and cannot initiate playback. Instead, hide the custom skill so that new users can't enable it. To do so, sign in to the Alexa Developer Console, and then select the checkbox next to skill you want to hide. From the drop-down list, select Hide. The skill can't be disabled until you hide it.

The ingestion process takes up to 72 hours from the time you submit a new station or make changes to your station. When your changes are live on Alexa, the station status is updated to Published.

The Analytics Dashboard lets you access station metrics, such as the unique number of customers listening to your station on Alexa and the number of times the station has been accessed. Station metrics become available about 48 hours after station publication.

To test a station, ask Alexa to play a station name, or use the station's alternative name, call sign, or frequency. Your customers can use the same identifiers. They don't have to enable any new skill to access the station, because the catalog content is autoenabled.

Radio station frequencies aren't unique. Station 101.2, for example, is a different station in one country or region than it is in another. If a customer asks Alexa to play a particular frequency but provides no other information, Alexa uses the customer's location to determine which station to play. As a result, testing by station frequency alone in different regions produces different results. To avoid ambiguity, provide other identifying information, such as the station name, in your request (for example, "Alexa, play 102.1 Developer News.").

Ten-codes, also called ten-signals, are abbreviations used to shorten common phrases in radio communications. Thus allowing for brevity and standardization of messages. They have been widely used by law enforcement, and in Citizens Band (CB) radio transmissions.

The codes were developed in 1937, and expanded in 1974, by the Association of Public-Safety Communications Officials-International (APCO). Ten-codes remain in common use, but have been phased out in some areas in favor of plain language.

I want to write a little dashboard/application where you can change three variables A,B,C using sliders (continuous levels allowed) and a fourth variable Faktor using radio buttons (since only 4 levels are allowed).

A second issue is that I want to unite the three current windows into one window (dashboard or application). I can select them all for Combine Windows, but when trying to send them to Dashboard builder, only the graph builder window appears, not the silders. How can I drag my silder/radio buttons into the Dashboard/Application builder?

Names Default to Here(1); states that the variable values only apply to this script. You do not need address the Here namespace and the syntax is Here:A . But that brings about another issue, the formula columns G1scale, G2scale, etc. will have formula like :G1*A. Once the script is run, or if you try to open the table at a later date the variable A is unknown. A couple suggestions are:

I was trying to build my graph using Dashboard Builder/Application Builder, since that was recommended by many people when starting JSL/application building, but I will implement your tips and delve further into containers etc.

I havent used DashboardBuilder except a simple example. I use Application Builder or just write a script to create an application. You might like to read about it. Some really like it. Others who have been scripting for a while, usually handle things via JSL.