You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The "pause" command is broken on three of the eight Multimedia devices in my account that have the playback interface assigned. I believe all other commands are working, but pause results in Alexa responding with "I'm sorry, I don't know" or similar. All three devices have the following interfaces assigned: Channel, Input, Playback, Power, and Speaker. A fourth device with the same interfaces assigned is fully functional, all commands including pause work on that device. I have deleted the devices from the Alexa app and re-detected, as well as deleting the Amazon OAuth tokens and re-linking the skill to my account multiple times. This previously fixed the broken input command on one of the affected devices, but has had no effect on the pause command.
Log Output
None.
Environment (please complete the following information):
Node-RED node version: 0.4.67
Node-RED version: 1.3.5
The text was updated successfully, but these errors were encountered:
Describe the bug
The "pause" command is broken on three of the eight Multimedia devices in my account that have the playback interface assigned. I believe all other commands are working, but pause results in Alexa responding with "I'm sorry, I don't know" or similar. All three devices have the following interfaces assigned: Channel, Input, Playback, Power, and Speaker. A fourth device with the same interfaces assigned is fully functional, all commands including pause work on that device. I have deleted the devices from the Alexa app and re-detected, as well as deleting the Amazon OAuth tokens and re-linking the skill to my account multiple times. This previously fixed the broken input command on one of the affected devices, but has had no effect on the pause command.
Log Output
None.
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: