-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Newly added echo device nodes say, "...not sure what went wrong", but still actually work. #81
Comments
Try this: remove echo from your Alexa Amazon account, reset echo to default (checkin YouTube how for your echo), Alexa should tell that to does perform a reset, add again it to account, say Alexa to discover devices. |
I am having the same problem with the 9th device I added. I don't understand the removing the echo from the Amazon account. I have 3 echo dots and the app on my iPad all 4 respond in the same way for the 9th device. |
If you have all 3 dots with one account, one dot will be the master, the others just mirror. If the master has a problem all others will have. I suggest 3 different accounts. To reset you need first to delete echos from account, then do reset. How to do reset search depends on echo type |
Hey, my issue resolved when I simply power cycled my Dot. It must have been the master. Try unplugging all your Alexa devices one by one till it resolves. Take note of the master for future reference. |
Thanks the support desk mantra 'have you tried turning it of and back on again' worked again. |
@datech please add this to your troubleshooting guide, too. Worked fine, after I tried several other things on my raspberry pi with node-red on docker. Thanks a lot! 👍 |
Thanks, @tt2g89 Troubleshooting page has been updated: Alexa: "I am not quite sure what went wrong" |
SUMMARY
I have 15 or so nodes that work fine. But if I add another it will respond as above when activated. No issues with discovery and the previous 15 still work fine. All devices on same subnet. Issue is independent of what is connected downstream in the flow.
ECHO DEVICES
MODULE VERSION
CONFIGURATION
CONSOLE OUTPUT
STEPS TO REPRODUCE
For me the testbed and fireplace echo device nodes are problematic.
EXPECTED RESULTS
They should reply with OK like the rest.
ACTUAL RESULTS
They say something like not sure what went wrong.
The text was updated successfully, but these errors were encountered: