fauxmojs icon indicating copy to clipboard operation
fauxmojs copied to clipboard

Devices not discoverable by Gen 2 Echos

Open alanpuccinelli opened this issue 6 years ago • 12 comments

While debugging the discoveryService.js I can see that the XML formed in response doesn't appear to be compliant with what the latest echo firmware expects. I suspect its a matter of updating the response in similar fashion to how the guys on the original fauxmo project did.

It looks like the new Echos are now requesting a metainfoservice.xml and eventservice.xml response and perhaps the setup.xml isn't formed correctly either.

See this issue for reference: https://github.com/n8henrie/fauxmo/commit/1c3389c0b9bfd16e96d87591afc007e1399c36c1

alanpuccinelli avatar Apr 19 '18 02:04 alanpuccinelli

There's a new release on the dev branch of fauxmo. Would it solve this issue? https://github.com/n8henrie/fauxmo/tree/dev

timothe avatar Apr 27 '18 11:04 timothe

@alanpuccinelli I will look at the python project and see if I can make some changes that will work. I do not have a Gen 2 Echo and have no way to test it at the moment.

dsandor avatar May 30 '18 12:05 dsandor

@dsandor I do, if I can be of any help

timothe avatar May 30 '18 12:05 timothe

@timothe Sure! I assume the python version is just emulating a different device class. I will try to get some cycles over the next few days and see if I can get a branch of this project running with the same device class that the python code is using and maybe you can test it.

dsandor avatar Jun 06 '18 17:06 dsandor

@dsandor Hi, I also have a 2nd gen echo (French version), if I can help you to test on my echo, jusk ask me :)

TanguyNa avatar Aug 21 '18 17:08 TanguyNa

I have a 3rd gen echo. I can help too :)

50l3r avatar Nov 01 '18 20:11 50l3r

Hi @TanguyNa and @50l3r can you confirm it is not working at the moment. Also are you able to log out the discovery messages that we get from those devices? I recently acquired an Echo Show and an Echo Spot so I am hoping that I can troubleshoot the messages from those. I will ping you both again when I patch the code and you can re-test.

dsandor avatar Nov 09 '18 12:11 dsandor

I have a 2nd gen show and 2nd gen echo. If I ask them to scan for a fauxmojs device, they don't detect it as per the above. However, if I go to https://alexa.amazon.co.uk and scan for devices in there, my fauxmojs device is discovered. However, all attempts to invoke it result in Alexa telling me it is unresponsive.

How do I help debug this?

biddster avatar Jan 03 '19 23:01 biddster

I'm using a 3rd gen echo dot in here and I have the same problem. Tried a few ways but alexa can't find any new devices with the echo dot. Same problem with https://alexa.amazon.de.

It looks like the python version has been fixed?! When there will be an update for the NodeJS Version?

djsunrise19 avatar Jan 07 '19 10:01 djsunrise19

Add me to the list as well. In the last few weeks (not really sure when), my mother's Echo 2nd gen is not discovering fauxmojs devices like it used to (but it does still discover the "real" WeMo switch). For grins, I just called her and asked her to disconnect the power from her Echo, and then asked her to ask her Echo DOT to discover devices, and interestingly, the fauxmojs devices re-appeared in her list of Smart Home devices. Does appear to be something specific to her Echo 2nd Gen, that is not (or not yet) affecting Echo Dot (2nd Gen).

johngo7470 avatar Jan 14 '19 01:01 johngo7470

I'm using a 3rd gen echo dot in here and I have the same problem.

ezar avatar Jan 27 '19 06:01 ezar

A few days ago, I visited my mom, deleted and re-discovered all devices using the Echo 2nd Gen, and found them again. Possibly the power cycle helped in some way...

johngo7470 avatar Jan 27 '19 21:01 johngo7470