I’ve been doing extensive testing on how Amazon Echo’s do discovery… They seem to randomly pick an echo to act as the “master” on the network and be the lan to cloud relay.
Not every echo does discovery and it does seem random now Amazon picks which one. Once it picks that one, the others are just slaves to it. They will not attempt discovery, no matter what.
It appears the only option is a network sniffer to see which echo is acting as the master on the LAN and then power that down. It takes about an hour for my echo’s to realize the master is dead and pick a new master. I can’t seem to figure out a way to force a new master. Rebooting, discovery, etc. all seem to just “fail” thinking the previous master is still doing the job…
This probably explains most of what a few are seeing, if the one master echo isn’t seeing the network, or is offline then nothing gets discovered. The more you mess with it, rebooting stuff, turning stuff off, etc. the worse it gets.
We will have our Alexa Skill soon, and hopefully this will solve this local discovery issue… Until then, thanks for everyone trying different things. Keep it up, we will figure out the problem. However, I don’t think its related to the type of router or wireless access point. It has to do with how Amazon chooses which echo is going to be that “master” for the lan.
Just my two cents… Hopefully it helps.
