Skip to content
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

devices still register on alexa after uninstall the plugin #25

Open
nnhhuu opened this issue Feb 7, 2019 · 5 comments
Open

devices still register on alexa after uninstall the plugin #25

nnhhuu opened this issue Feb 7, 2019 · 5 comments

Comments

@nnhhuu
Copy link

nnhhuu commented Feb 7, 2019

Hello,
i installed this node in order to control some HA devices with alexa using node-red, there was very straight forward process for the first device, alexa recognize, when i started to add the devices (about 20) i notice that all the devices were duplicated in alexa, every time that i "discover devices", the devices were duplicated, sometime there were 4 or 5 with the same name. after i fight with this for a few days, i decided to uninstall the node and keep using the alexa-local node, BUT... the devices still being discovered by alexa, even though the node is not installed anymore... extrange....

i have echo 2 and echo 3 at home, i notice that when i disconnect the echo3 form the network, those devices are not discovered, but if do the discovery with the echo3 all those devices are discovered...

Any idea?

THANK YOU

@caobach42
Copy link

caobach42 commented Feb 14, 2020

I have this issue on echo dot3 too, even upgraded to 1.0.0, any idea to fix it?
first i need to remove all devices first for fresh node-red installation but even i forget all devices, stop node-red then discover again, all devices just reappeared. is it possibility issue by echo dot itself?
Thanks

@MattL0
Copy link

MattL0 commented Feb 18, 2020

is this still an issue ? Just downloaded vs 1.0.0 to try.

wanted to set my binary /on/off with this instead of with the hue emulator( which expose a rgb -diming node to node red... but it works)

@fraser73
Copy link

fraser73 commented Mar 3, 2020

I've just upgraded my node red / raspbian setup to the current version and I'm seeing this behavior. There are now two of everything - even after I disable the current nodes and restart node red (even if I reboot the system) However I can't find anywhere that the config data might persist?

@fraser73
Copy link

fraser73 commented Mar 3, 2020

I've just had a bit more of a dig into the problem and it seems (at least in my case) that if you stop node-red, (I also shut down the system that was running it for good measure).

Then from the web portal, I got Echo to forget all the smart home devices, rescanned and it still found the old wemo emulated devices.

To fix this, it seems that if you manually "forget" each device individually through the web portal Echo actually forgets them, as when you rescan after doing this, it doesn't find any of the old devices.

After this you can re-start node-red and re-scan for only the current devices.

If someone else can replicate this behaviour, I think it can be put down to a bug with Amazon, not node-red-contrib-wemo-emulator.

@caobach42
Copy link

@fraser73 it is not work for me :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants