Describe the bug
I edited a device which was originally setup as Smart Plug to be a Multimedia device in order to add playback functionality (specifically play/pause). I checked the "Playback" and "Power" options after changing the Device Type. However after doing this Alexa responds with "Sorry I don't know that" when attempting to ask to play/pause the edited device. Power functions still works and brand new devices do not seem to have this issue.
I have tried re-linking my account, deleting and re-adding the device, and renaming a new device which worked.
I have other custom Multimedia devices setup so it is odd that this edited one does not work the same. Perhaps there is some sort of server side caching of the original device causing the issue?
To Reproduce
1) Setup a Smart Plug device on the web portal & discover via Alexa
2a) Delete device and re-add new device with same name but Multimedia type
2b) Edit device to be Multimedia instead of Smart Plug
3) Delete & re-discover device in Alexa App
4) Attempt to use p[ay/pause function on new/re-added device
Expected behavior
Alexa should respond to play/pause approrpiately.
Log Output
N/A - command does not reach Node-Red flow
Environment (please complete the following information):
Node-RED node version: v9.7.1
Node-RED version: v3.0.2
Additional context
Node installed via NPM on Raspberry Pi Linux
Describe the bug I edited a device which was originally setup as Smart Plug to be a Multimedia device in order to add playback functionality (specifically play/pause). I checked the "Playback" and "Power" options after changing the Device Type. However after doing this Alexa responds with "Sorry I don't know that" when attempting to ask to play/pause the edited device. Power functions still works and brand new devices do not seem to have this issue.
I have tried re-linking my account, deleting and re-adding the device, and renaming a new device which worked. I have other custom Multimedia devices setup so it is odd that this edited one does not work the same. Perhaps there is some sort of server side caching of the original device causing the issue?
To Reproduce 1) Setup a Smart Plug device on the web portal & discover via Alexa 2a) Delete device and re-add new device with same name but Multimedia type 2b) Edit device to be Multimedia instead of Smart Plug 3) Delete & re-discover device in Alexa App 4) Attempt to use p[ay/pause function on new/re-added device
Expected behavior Alexa should respond to play/pause approrpiately.
Log Output N/A - command does not reach Node-Red flow
Environment (please complete the following information):
Additional context Node installed via NPM on Raspberry Pi Linux