-
Notifications
You must be signed in to change notification settings - Fork 43
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
Old devices are still found #136
Comments
Remove all devices from alexa account, remove all echo from account, do hardware reset all echo, associate only one echo to account and discover. Notice what i happening. I suggest you to use a different account for each echo. Don't use general name for devices (if you do that) like "light", try to be more specific to help Alexa find device unique. |
Unfortunately the old devices are found anyway. |
Are you sure you hardware reset Echo? You didn't specified it |
Yeah, sorry. |
you better check your flow, chances are your old devices are hidden by new ones, or you are using mutiple flows. |
I am having a same issue. I was looking to move my implementation from one Pi node-red to another. However, this has confused Alexa. So, I returned to the original Pi. So, nothing should be found, yet they still appear. Am I doing this in the correct way? Can I have detailed description on a hard reset? It's not a factory reset, I hope as I have five devices to do. Currently I have unplugged all other devices and deleted all flows whilst trying to fix this. |
Glad to hear I'm not the only one. Also I found this. @Barabba11 |
IMHO Alexa is far to be a reliable predictable instrument, even though they are developing it from years seems bugs still and maybe other appears. To sniff the network you need an old ethernet hub or a router like mikrotik, which is able to log all traffic from Alexa IP for example |
I did that, too.
How can it be that Alexa finds devices when she is in the WIFI hotspot of my mobile phone. |
Check at http://alexa.amazon.com |
Well seems pretty clear that the issue still in Amazon servers, try to delete devices with the browser accessing your account, if there aren't try to setup a new account. |
I've discovered that one echo dot in particular is responsible in bringing back these devices. I have deregistered and unplugged this device for the foreseeable. Also had a long chat with Amazon and they are looking into whether they will replace the Dot Gen 2. |
I think I have found the problem. I think I have found the problem. I have tested the following. My Echo Dot with my account My Echo Dot with another account New Echo Dot with my account It seems that the echoes carry an internal list of all known devices. |
if you're sure you properly reset Echo (Alexa will tell it and take some time) then it's obvious an Amazon problem. I hope you wrote them about it, they need to be warned about |
I have been dealing with this problem for more than a year, hope there will be a solution.... Soon..... :) |
I have the same problem |
I figured out it was one echo in particular that kept on adding ghosts back
in. It’s an Amazon problem they refuse to admit/address. So, I just
unplugged that one when doing the updates.
…On Sun, 29 Nov 2020 at 22:10, jpg06 ***@***.***> wrote:
I have the same problem
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#136 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACIYJQKZQ5V6AVN4PIFHBTSSLBD7ANCNFSM4OXHRCHQ>
.
|
I unplug the echo spot (my older echo) and all seems's ok during a discover: no old device. |
SUMMARY
My NoeRed environment runs on an ioBroker server. After I moved the whole system incl. NodeRed my Alexa devices did not work anymore.
After I tried to set up everything anew I noticed that the devices are present in Alexa several times.
If I delete all devices and search again it will find the old ones.
Even if the ioBroker server incl. NodeRed are shut down
ECHO DEVICES
MODULE VERSION
CONFIGURATION
CONSOLE OUTPUT
EXPECTED RESULTS
No old equipment in Alexa
ACTUAL RESULTS
old equipment in Alexa
The text was updated successfully, but these errors were encountered: