Alexa is not able to detect my device. EXT: Astral - by STFJunkie When you did the discovery with the Firestick, was the Echo Plus online? This will be a little tough for me to debug, as I don't have an Echo 2, and none of my echo devices are running that firmware. Those of you reporting issues with an Echo 2 -- does anyone have an actual Wemo device, and if so can you send me a pcap (i.e. to your account. I intend to have a play anyway, because you can get the server to respond with text for Alexa to say, and I might have some fun with the kids using that as a bit of a trick. DATE: Fri, 01 Dec 2017 09:58:44 GMT 2017-12-01 10:58:46 asyncio:1379 DEBUG poll took 154.827 ms: 1 events Press question mark to learn the rest of the keyboard shortcuts. I have an Echo Plus and would be willing to purchase a Belkin WeMo device to capture a pcap if somebody wants to help me through it. Now - you might have noticed, its Christmas. Here's how to fix it. CACHE-CONTROL: max-age=86400 She's also an expertly-tuned speaker that can fill any room with immersive sound. So it was not just an old fauxmo issue, but maybe a bigger one. I noticed that everything looked okay so far, but it didn't work anymore. I deleted my WEMO switch from Alexa throu the app and tried to discover it again, but Echo did not find the WEMO anymore, also the raspi was not discovered during this test. Environment: Everything in the house is a breeze to get working. 2017-12-01 10:59:09 fauxmo:146 DEBUG Shutting down server 0... I don't have an Echo but I own an Android phone with Alexa installed. Big mistake. EXT: PS: forgot to mention one small thing i noticed: Echo never requests the setup.xml, so it seems somehow to ignore the information it got from the query (or doesn't use it). By-The-Way - check Amazon, as Energenie have released their MiHome-Hub and they also sell Pi-Boards for the transmission of 433Mhz. I still don't have an Echo Plus (and don't plan to get one, since I don't have any Zigbee devices and my Echo works just fun), so I have no practical way of even trying to resolve this issue right now. I had previously installed Wemo Connect and without issues it found all 13 of my devices. Upon which, the total figure of devices found will be written. I don't have an echo 2. Any advice or good articles that anybody can recommend? I too have some Energenie power plugs and looking to setup Echo Dot to control them via 433MHz from RaspberryPi with Fauxmo. SERVER: Fauxmo, UPnP/1.0, Unspecified Any testers wanting to see if this makes discovery more reliable: pip3 uninstall -y fauxmo; pip3 install git+https://github.com/n8henrie/fauxmo@d0da2b42d7564fef02bfa7dfd56571ca76a90d13. Other devices that I've installed have all had the Alexa skill before they were discovered. That's why I am saying, key to resolve the issue is getting fauxmo to work with the wemo-app. I have a feeling that it doesn't work because I don't have the Alexa WEMO skill installed. Sign in Has somebody gotten this to work on an Echo Show already? MAC address. They are now all grayed out in the list of connected devices and show "(Offline)" and forgetting one and discovering results in them being not found. HTTP/1.1 200 OK HTTP/1.1 200 OK DEBUG:root:Responding to setup.xml for test. @n8henrie Relays and lights with friendly names beginning with a dollar sign ( $) will cause Tasmota to not "announce" them (i.e., be hidden) to Alexa. LOCATION: http://192.168.178.2:49915/setup.xml 2017-12-01 10:58:46 fauxmo:224 DEBUG Received data below from ('192.168.178.180', 50000): Consider logging (see the nighttime.py example later) to the /tmp so it's easy to check that your automation is running properly) LOCATION: http://192.168.178.2:49915/setup.xml ST: urn:Belkin:device:** 01-NLS: f795c3fa-0b25-4baf-a8a4-6733d284b978 WEMO is a growing family of innovative, easy-to-use products that use mobile internet to control your home electronics, power, water, and WiFi right from your smartphone or tablet. LOCATION: http://192.168.178.2:49915/setup.xml Sign up for a free GitHub account to open an issue and contact its maintainers and the community. But it seems to be more an issue of the Alexa App/Website than fauxmo. This will use Astral module to check the time night starts I was going to gift the old dot to my Mum, but now I'm going to keep it. 2017-12-01 10:58:46 fauxmo:225 DEBUG b'M-SEARCH * HTTP/1.1\r\nMX: 3\r\nST: upnp:rootdevice\r\nHOST: 239.255.255.250:1900\r\nMAN: "ssdp:discover"\r\n\r\n' I suspect this is what is happening when you speak to Alexa as well - the newer version is contacting Belkin. Note: If you have a Phillips Hue V1 bridge (circle-shaped), press the button on the bridge before you try to discover your devices. If i read the log correctly (#38 (comment)), it seems that the setup.xml was not send, normally must SERVER: Fauxmo, UPnP/1.0, Unspecified I'm beginning to wonder if Amazon are taking liberties with the standard but I need more studying before I can substantiate or refute such a scurrilous claim ;-). ST: urn:Belkin:device:** But I have reports form other 2nd gen echo users that fauxmoesp does not work as well. If you have Wemo devices that have similar names, your Alexa might have trouble distinguishing them apart. You should create short python scripts for turning on and off whichever devices you want, remember with energenie you can pair the sockets to the same button or to different buttons or to different ones (also the sockets will remember a code from another controller as well i.e. Alexa Not Able To Discover WeMo Switch After Firmware Upgrade : amazonecho. I also implemented the status query and it looks like the request is answered correctly (debug output Anyway, from my side, with the last commit and up2date Echo gen 2 it works now. Press J to jump to the feed. LOCATION: http://192.168.178.2:49915/setup.xml b'M-SEARCH * HTTP/1.1\r\nMX: 3\r\nST: upnp:rootdevice\r\nHOST: 239.255.255.250:1900\r\nMAN: "ssdp:discover"\r\n\r\n' b'M-SEARCH * HTTP/1.1\r\nMX: 3\r\nST: ssdp:all\r\nHOST: 239.255.255.250:1900\r\nMAN: "ssdp:discover"\r\n\r\n' b'M-SEARCH * HTTP/1.1\r\nMX: 3\r\nST: upnp:rootdevice\r\nHOST: 239.255.255.250:1900\r\nMAN: "ssdp:discover"\r\n\r\n' b'M-SEARCH * HTTP/1.1\r\nMX: 3\r\nST: ssdp:all\r\nHOST: 239.255.255.250:1900\r\nMAN: "ssdp:discover"\r\n\r\n' b'M-SEARCH * HTTP/1.1\r\nMX: 3\r\nST: upnp:rootdevice\r\nHOST: 239.255.255.250:1900\r\nMAN: "ssdp:discover"\r\n\r\n' b'M-SEARCH * HTTP/1.1\r\nMX: 3\r\nST: ssdp:all\r\nHOST: 239.255.255.250:1900\r\nMAN: "ssdp:discover"\r\n\r\n' b'M-SEARCH * HTTP/1.1\r\nMX: 3\r\nST: upnp:rootdevice\r\nHOST: 239.255.255.250:1900\r\nMAN: "ssdp:discover"\r\n\r\n' b'M-SEARCH * HTTP/1.1\r\nMX: 3\r\nST: ssdp:all\r\nHOST: 239.255.255.250:1900\r\nMAN: "ssdp:discover"\r\n\r\n' b'M-SEARCH * HTTP/1.1\r\nMX: 3\r\nST: upnp:rootdevice\r\nHOST: 239.255.255.250:1900\r\nMAN: "ssdp:discover"\r\n\r\n' b'M-SEARCH * HTTP/1.1\r\nMX: 3\r\nST: ssdp:all\r\nHOST: 239.255.255.250:1900\r\nMAN: "ssdp:discover"\r\n\r\n' 2017-12-01 10:58:46 fauxmo:224 DEBUG Received data below from ('192.168.178.180', 50000): Follow the instructions to get set-up (installing wiringpi as well) then test out the transmit/receive. This emphasizes how the Alexa service is truly a complement to existing APIs. The discovery of devices is made by querying skill adapters for information, not by direct communication with the devices. pip install git+https://github.com/n8henrie/fauxmo.git@issue_38. Amazon has more detailed instructions on their website if you need them. Some combination of these things will temporarily allow the discovery of the switches but the next time I go into the Alexa app they are grayed out and indicate "(Offline)". The Wemo and Hue devices were discovered immediately and have worked perfectly since. Please make sure you've taken these steps before submitting a new issue: The text was updated successfully, but these errors were encountered: What is your Echo firmware version and what type of device is it? usually I just throw some time switches on the plugs, but I got some more Energenie 433Mhz sockets , so I thought I will set up a fauxmo called "Christmas" and guess what, the new Gen2 echo can not find the device (even with the original dot online), but then when I ask the original dot to do the scan it finds it, registers it and the other echos can now turn Christmas on and off. 2017-12-01 10:58:46 fauxmo:224 DEBUG Received data below from ('192.168.178.180', 50000): Hi, have a look on this issue: If someone can get me a pcap of the Echo 2 interacting with a Belkin WeMo, that would be a good start. OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01 So there might be some meta information missing maybe? privacy statement. I tried it without them and it doesn't work. DEBUG:root:FauxMo device 'test' ready on 192.168.0.54:52010 So First point of order - Thank-you for developing and sharing this code, it's brilliant. Install 433Utils on the PI - https://github.com/ninjablocks/433Utils SERVER: Fauxmo, UPnP/1.0, Unspecified 2017-12-01 10:58:48 fauxmo:224 DEBUG Received data below from ('192.168.178.34', 50820): I was thinking about getting something like this (because its the cheapest). Unfortunately I was not extremely organised when I first set this up, So I can tell you 'how' and share some bits of code, but some I am missing. This is what Amazon tech support says: To use a smart home device with Amazon Fire TV or Amazon Fire TV Stick, you need to use a cloud-connected service, such as ecobee, Wink, Insteon, and SmartThings. I recognized some interesting things till I got the Echo finding the raspi. It will be easier for Alexa to recognize. ST: urn:Belkin:device:** CACHE-CONTROL: max-age=86400 Hiya, I have been using fauxmo for about 2 years with an Ecoo Dot and a Pi. first of all let me say you are doing a great job here! The Echo is sending SSDP SEARCH but the fauxmo devices are not responding. Not sure whats the issue with this, but in the Serial Monitor I can see the logs which is showing that I am getting ping from Alexa to my ESP8266. l = Location(('Town_name', 'UK', 53.14, -1.25, 'Europe/London', 0)) USN: uuid:Socket-1_0-43b3ae40-0ab7-3efb-8425-a09656068511::urn:Belkin:device:**, 2017-12-01 10:58:44 asyncio:1379 DEBUG poll took 12.268 ms: 1 events However: while I see all kinds of discover requests in the debug output (e.g. I know this is about cracking it with Pi, but I mention it, because My Mum has Energenie sockets already but I am not setting a Pi up at her house, because let's face it - Mums break tech all the time, she is getting an Echo and a MiHome Hum with 3 extra sockets for Christmas (And I am already anticipating my regret!!). CACHE-CONTROL: max-age=86400 CACHE-CONTROL: max-age=86400 The rest is just straight-forward use of the fauxmo set-up, when you receive an on or off command from Alexa you execute your on or off python command from the fauxmo session. Basically, to start you'll want to figure out the IP address and MAC address for the WeMo plug, then use WireShark filters to only capture or display information from that address. Really looking forward to get fauxmo running... @BetMadZac73 Hi. 2017-12-01 10:58:42 asyncio:947 DEBUG Datagram endpoint remote_addr=None created: (<_SelectorDatagramTransport fd=8 read=idle write=
>, ) In this case, it's the WeMo Mini smart plug. Edit: Actually, while it discovered everything it didn't last. When I have something, I'll post here. But after serveral hours of reading and trying I got the Echo to discover the raspi. I was about to do it the harder way by setting up a server on my Pi and exposing that to the world, so that I can write an Alexa Skill to send a post request to my server, enabling my raspberry Pi to respond to Alexa and also to then control devices. WEMO is a growing family of innovative, easy-to-use products that use mobile internet to control your home electronics, power, water, and WiFi right from your smartphone or tablet. 2017-12-01 10:58:47 asyncio:1379 DEBUG poll took 999.642 ms: 1 events Can you clarify what you're seeing / what "isn't working"? Select Hue Bridge V1 as the device type. print "it is still daytime" just want to … I activated the WEMO skill, after that Alexa discovered the WEMO switch but not the raspi. Can't use Wireshark for that. Read on. @clach04 - That's a very good point, I did have the Echo Plus still online. print "it is now night" https://github.com/kakopappa @n8henrie - Excellent thanks, I'll give it a try this evening and report back. 2017-12-01 10:58:46 fauxmo:265 DEBUG Sending response to ('192.168.178.180', 50000): from datetime import datetime When I looked in the device list - they were still present but indicated that they were "offline". So a second discover is mostly not really needed because it seems to be an issue with the Webinterface. EXT: I've made a small modification that should respond with the same ST: pattern the Echo sent out, seems to retain discovery on my Echo 1 and hopefully should also work for the newer devices. ^C2017-12-01 10:59:09 asyncio:1379 INFO poll took 20970.146 ms: 1 events All devices respond to requests from Alexa. Same issue here with latest ECHO PLUS Gen2 - Firmware-Version 595530520. I have an older WEMO switch (by fortune), the Echo found this already before I started with the raspi. """ USN: uuid:Socket-1_0-43b3ae40-0ab7-3efb-8425-a09656068511::urn:Belkin:device:**, 2017-12-01 10:58:46 asyncio:1379 DEBUG poll took 486.742 ms: 1 events It will not however discover my ESP8266 with the Fauxmo installed. HTTP/1.1 200 OK Every time it takes at least an hour to set up. - and then send a bespoke message back, listing a number of misdemeanours, leaving them wondering how Alexa knows all this stuff). Alexa not working with your smart home camera? I can still control them through the WeMo app and through Alexa but if I tell Alexa to forget one, it can't rediscover it without jumping through bizarre hoops as shown above. @n8henrie -- No, I intended the two colons to be at the start of the string. My Echo Firmware Version is 595530420. Here is the firmware that is causing the problem: WeMo_WW_2.00.10062.PVT-OWRT-LS You can find that in the WeMo app by clicking "More" in the lower right, "Settings & About" then "Firmware Versions". I also have a Philips Hue lightbulb. If memory serves, capture filtering may only be possible by MAC address (not IP address), but I could have that backwards. 2017-12-01 10:58:44 fauxmo:265 DEBUG Sending response to ('192.168.178.180', 50000): This Node-RED node is only a slim wrapper around the marvellous wemore Wemo library written by Daniel Leong. I had two WeMo switches installed and working just fine so I purchased two more. So the fauxmo Raspi didn't know how to reach the Echo (both within the same network). Alexa is designed around your voice. So after my python was installed, i switched directly to the comit referred by @n8henrie (d0da2b4). Alternatively, you can also discover devices using the Amazon Alexa app, by following the steps shown in the figure below. DATE: Fri, 01 Dec 2017 09:58:46 GMT RPi3 with fauxmo 0.4.5 is not responding to "b'M-SEARCH * HTTP/1.1\r\nMX: 3\r\nST: ssdp:all\r\nHOST: 239.255.255.250:1900\r\nMAN: "ssdp:discover"" requests at all. Sorry folks. shortly before the holidays, my family noticed that my switches don't work with alexa anymore. I have two Echo's and 4 switches and I essentially reset all of them (started from scratch) and now they are working - hopefully someone can figure out what the problem is to save some that hassle. A first try to discover showed at least some fauxmo action again, so it responded to the echo requests. What isn't clear to me is how to set it up to get the pcap (or any other desired output). OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01 OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01 @SuoaJ -- no, it doesn't, as I've (indirectly) mentioned in the FAQ. DATE: Fri, 01 Dec 2017 09:58:45 GMT Not sure what you're referring to re: polling. The 1st time it found 12 of my 13 devices but I could do nothing to get the 13th to appear. I can't install the skill because I don't have any real WEMO devices and the skill installation seems to insist that I have one it can find (I'm open to suggestions if anyone knows how I might get around this limitation). While doing so I found a statement from another echo2-user that alexa is actualy asking to activate the "wemo skill" when giving the command to detected new devices. That fixed them right up. I tried it two times, and i tried it using the app and the voice command. With the commit from @n8henrie it works a "bit" better but still not perfect. LOCATION: http://192.168.178.2:49915/setup.xml About here is the output: Who can test the latest issue_38 with a newer echo device? My echo is at 10.0.4.49 and the machine running fauxmo is at 10.0.4.45 - I did a power recycle on the Echo before doing the discovery. source venv/bin/activate Edit: I won't need to as my last ditch effort actually worked (I reset everything - all 4 switches and both Echos) and magically it is working. LOCATION: http://192.168.178.2:49915/setup.xml I don't have an IPhone but the wemo-android-app seems to do its own detection and seems to be incompatible with fauxmo too. But thats a Zigbee device. However , if you can solve it (Find how Alexa is scanning and respond to it) maybe it is still workable, because Alexa has to run the scan locally it can't rely on the Belkin servers to scan the local network. while a == 1 : SERVER: Fauxmo, UPnP/1.0, Unspecified My understanding is that Zigbee is a radio waves type of communication. I currently have several devices including real hardware that all work fine. Plug in a WeMo Mini Smart Plug, download the free app, and control your lights and appliances from your phone and your voice through Alexa, Google Assistant and Apple Home Kit. 2017-12-01 10:58:42 fauxmo:100 DEBUG plugin_vars: {} It seems to be important to restart the Echo from time to time, otherwise it seems to be in a very unknown state, as of not working correctly. the new Gen2 Echo's are using a different search/control for WeMo devices and so no longer compatible with fauxmo. Press question mark to learn the rest of the keyboard shortcuts. CACHE-CONTROL: max-age=86400 Recently however I renamed and moved several wemos and Wemo Connect did not reflect all these changes correctly. An example would be using “Two” instead of 2. 2017-12-01 10:58:46 fauxmo:224 DEBUG Received data below from ('192.168.178.1', 41766):