During discovery we include an InputController capability and as per the documentation we include a list of supported inputs. For example:
{ "interface": "Alexa.InputController", "type": "AlexaInterface", "version": "3" "inputs": [ { "name": "Playlist" }, { "name": "Radio" }, { "name": "Songcast" }, { "name": "Television" }, { "name": "Spotify" } ] }
However, if I utter "Alexa, change input to radio on <device>", my backend receives the following payload:
{ "header": { "namespace": "Alexa.InputController", "name": "SelectInput", "payloadVersion": "3", "messageId": "544020a3-f66b-4c25-8405-847ff378dc9d", "correlationToken": "..." }, "endpointId": "2s37rota", "payload": { "input": "TUNER" } }
This is definitely unexpected behaviour! Furthermore, since there may not be an input named "TUNER", we correctly respond with an INVALID_VALUE and alexa then reports the device is not responding!!
Can you confirm if the names provided in the "input" property during discovery are referenced when requesting to change the input?