olili
(olili)
January 29, 2023, 8:37pm
21
Dear Jeremy,
in most cases the “channel metadata name” is equal to the slot value.
In a few cases it was different.
There I added the channel meta data as synonym to the slot. eg. rtl → r. t. l.
All used synonyms are already shown in my last post.
O.
jeshab
(Jeremy)
January 29, 2023, 9:32pm
22
I was referring to the channelMetadata.name
property included in the ChannelController
request, in the event you deploy your own skill based on the documentation I mentioned above.
Below is the request received by the skill when asking schalte auf kanal r. t. l.
{
"directive": {
"header": {
"messageId": "<messageId>",
"namespace": "Alexa.ChannelController",
"name": "ChangeChannel",
"payloadVersion": "3",
"correlationToken": "<correlationToken>"
},
"endpoint": {
"scope": {
"type": "BearerToken",
"token": "<accessToken>"
},
"endpointId": "<endpointId>",
"cookie": {
"capabilities": "<capabilities>"
}
},
"payload": {
"channel": {},
"channelMetadata": {
"name": "RTL"
}
}
}
}
olili
(olili)
January 30, 2023, 7:12am
23
Dear Jeremy,
in my custom skill I do not use the ChannelController. As written, I defined my own “channel slot” including synonyms in the alexa developer console.