I have been all over the WeMo forums and no one else is reporting this problem so I am trying to determine if it is local to me or not. Alexa, Discover Devices. Looks like you're using new Reddit on an old browser. When I looked in the device list - they were still present but indicated that they were "offline". Alexa not working with your smart home camera? If it was, then its likely the Firestick didn't find the devices, it found the registrations that the Echo Plus created. I have resolved my problem but I am not sure what the problem was. A request is not made at that time. While waiting for the installation to complete, i found this issue and started scratching my head. 2017-12-01 10:58:46 fauxmo:224 DEBUG Received data below from ('192.168.178.180', 50000): With a new update, Amazon Echo users can tell Alexa to turn WeMo Switches and Philips Hue lights on and off. Wireshark / tcpdump capture)? LOCATION: http://192.168.178.2:49915/setup.xml And i don't have any smart home skill installed. DEBUG:root:FauxMo device 'test' ready on 192.168.0.54:52010 EXT: That's why I am saying, key to resolve the issue is getting fauxmo to work with the wemo-app. 01-NLS: d6b26f06-b7e8-4713-a0ce-26fcd2e55668 For some reason (i really don't know what the Echo had), the Echo didn't respond to arp requests anymore. 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' privacy statement. 2017-12-01 10:58:42 fauxmo:123 INFO Starting UDP server PPS: that was the hint pointing me to the right direction. 2. It was not discovered. maybe the solution @n8henrie break restarted the Pi to ensure a clean environment, and unplugged the echo-dot (which is running same version as your dot btw). Specifically: It is successfully requesting the setup.xml, parsing the device, and requesting the state for the device (which looks like get_state isn't yet configured, but is getting a 200 status code). python3 -m venv venv Now, Alexa will recognize your new device AND your Philips Hue lights will work normally; 4) If you decide to change the name of your fauxmo, you don't need to go though this again. Hope someone has some ideas, I'd love to get this working. If you have a TP-Link device, make sure to turn on Remote Control … Alexa - NodeMCU: WeMo Emulation Made Simple: This Instructable is one of the winners on "Automation" contest 2017. Press J to jump to the feed. sudo pip install git+https://github.com/n8henrie/fauxmo.git@issue_38. 01-NLS: 58af155a-0a0b-438a-8f0a-2a6090be6b0a (It's not you, it's them). @n8henrie No hub or subscription required; Compact size. 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". Recently however I renamed and moved several wemos and Wemo Connect did not reflect all these changes correctly. Unfortunately I don't think this method will capture the initial broadcast message from the Echo (since it is not to or from the WeMo address, but instead is a broadcast to all local devices), but I think we should be able to glean that from the fauxmo logs. If i read the log correctly (#38 (comment)), it seems that the setup.xml was not send, normally must 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. What isn't clear to me is how to set it up to get the pcap (or any other desired output). fauxmo -vvv 2> log-issue38-discover01.txt, (Nothing changed, run immediately after Test 1), fauxmo -vvv 2> log-issue38-discover02.txt, (Nothing changed, run immediately after Test 2). WeMo Mini features a sleek new form factor that allows you to stack two Mini Smart Plugs in the same outlet. Device discovery? Enter Wifi. A first try to discover showed at least some fauxmo action again, so it responded to the echo requests. SERVER: Fauxmo, UPnP/1.0, Unspecified Not only did it not discover the new switches, it found 2 less devices then usual (my first two switches). To activate the wemo skill you need your WiFi ssid and the Mac address of one of the wemo devices. 3. 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. HTTP/1.1 200 OK Then I started with fauxmo, but did not get it discovered, even with the issue '38 fix it did not work. 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 time you can see responses but the devices are still not discovered. @n8henrie - Excellent thanks, I'll give it a try this evening and report back. "Fauxmo response to setup request" stand in the log or? Enabling the Wemo Skill in the Amazon Alexa app The first part of linking your Amazon Alexa app with Wemo is to enable the Wemo Skill in the Amazon Alexa app. Can this work without a physical echo device? I too have some Energenie power plugs and looking to setup Echo Dot to control them via 433MHz from RaspberryPi with Fauxmo. 2017-12-01 10:58:45 fauxmo:265 DEBUG Sending response to ('192.168.178.180', 50000): DATE: Fri, 01 Dec 2017 09:58:45 GMT 2017-12-01 10:58:42 fauxmo:121 DEBUG Started fauxmo device: {'name': 'output', 'plugin': } CACHE-CONTROL: max-age=86400 here is the output: But having said that, I had asked the app to forget all devices before I ran the test. EXT: USN: uuid:Socket-1_0-43b3ae40-0ab7-3efb-8425-a09656068511::urn:Belkin:device:**, 2017-12-01 10:58:45 asyncio:1379 DEBUG poll took 0.019 ms: 1 events ST: urn:Belkin:device:** Read on. l = Location(('Town_name', 'UK', 53.14, -1.25, 'Europe/London', 0)) I see the SSDP traffic in my -vvv output but no discovery is actually finished. i tryed it and it did not work. The Wemo and Hue devices were discovered immediately and have worked perfectly since. @jcarley It's tough to say for sure, but I would think that WeMo plug would work. @clach04 - That's a very good point, I did have the Echo Plus still online. if now < sun: Make sure the Alexa-enabled device is in Wi-Fi range. os.system("python /home/pi/python/lights_on.py")`, The contents of the "lights_on.py" are below (I throw the switch off first, and then send the on signal twice just to be sure. logging.basicConfig(filename='/tmp/night_time.log',level=logging.DEBUG), ast = Astral() So First point of order - Thank-you for developing and sharing this code, it's brilliant. OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01 SERVER: Fauxmo, UPnP/1.0, Unspecified I'm back at work tomorrow (UK public holiday today) but I'll try and find a little time to test the latest issue_38 with my echo plus (FW 595530420). OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01 But I was having an issue before I renamed one of my bands for my dual band router, to where they would go offline for no reason except for on LTE. I have Wireshark installed on my Mac already. EXT: SERVER: Fauxmo, UPnP/1.0, Unspecified Alexa might seem to be unresponsive because your Echo is too far away from the router. Still will not discover the plug. I learnt along the way - get your Pi to restart everyday using cron (it's just neater and cleaner I restart at 03:05). WEMO also works with IFTTT, connecting your home electronics to a whole world of online apps. to your account. But I have reports form other 2nd gen echo users that fauxmoesp does not work as well. What I would do is set it up so that the switch seems to be working, then set up your filters so you can toggle the switch on and off to make sure your filters are capturing information. DEBUG:root:Responding to setup.xml for test. from my printer), there's none from the IP of the Echo Show. My discovery is working as it should now with an Echo Dot V2 with the latest firmware. ^C2017-12-01 10:59:09 asyncio:1379 INFO poll took 20970.146 ms: 1 events I have a feeling that it doesn't work because I don't have the Alexa WEMO skill installed. When you did the discovery with the Firestick, was the Echo Plus online? Alexa Not Able To Discover WeMo Switch After Firmware Upgrade : amazonecho. 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. thanks for the quick response. USN: uuid:Socket-1_0-43b3ae40-0ab7-3efb-8425-a09656068511::urn:Belkin:device:**, 2017-12-01 10:58:46 asyncio:1379 DEBUG poll took 0.017 ms: 1 events I activated the WEMO skill, after that Alexa discovered the WEMO switch but not the raspi. Maybe the Echo got confused because of same devices found by different queries? 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. DEBUG:root:got local address of 192.168.0.54 I spend several hours searching for a solution, but everything I found didn't work for me. During the installation process I was informed that there was a new …. 01-NLS: 8e90575f-4b8b-49ec-bbd2-b4cd646ee83c 01-NLS: 0d0929e4-e570-4467-9e55-1104f71355af ST: urn:Belkin:device:** OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01 The Fauxmo devices don't respond to the echo. 2017-12-01 10:58:44 fauxmo:265 DEBUG Sending response to ('192.168.178.180', 50000): EXT: The Echo is sending SSDP SEARCH but the fauxmo devices are not responding. So a second discover is mostly not really needed because it seems to be an issue with the Webinterface. As most virtual assistants, Alexa listens and responds to all of your queries through voice. Am I doing something wrong or is Echo Show behaving differently from Echo Plus? OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01 2017-12-01 10:58:46 fauxmo:225 DEBUG b'M-SEARCH * HTTP/1.1\r\nHOST: 239.255.255.250:1900\r\nMAN: "ssdp:discover"\r\nMX: 5\r\nST: urn:schemas-upnp-org:device:avm-aha:1\r\n\r\n' I've almost achieved my own HAL9000. WiFfi indicator is set to green and blinking: The Wemo Light Switch is starting up, connecting or undergoing firmware update. Thanks everyone for the suggestions and the fixes. Check for device or setup issues Try these steps first: Make sure that your smart home device is compatible with Alexa. I can't say for sure whether the Firestick initiated the discovery or it asked the Echo to do it. If you don’t see the Smart Home Skill in the Amazon Alexa app, the skill is not available for your particular locale. I have the latest fauxmo v0.4.5 version. 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. CACHE-CONTROL: max-age=86400 First off - 433Mhz - I got a receiver and a transmitter board (I think it cost me about £2.50 for 3 of each), Then I used an Arduino to receive and interpret the Energenie remote codes (You will be able to do this using the PI, the Utils does have a sniffer for this - Also I lost the Arduino Sketch when the Hard-drive on My MacBook died). SERVER: Fauxmo, UPnP/1.0, Unspecified If Alexa doesn't discover your smart home device, here are some solutions to try. I tried the discovery with my Amazon Firestick (fw 587601020) and I was able to discover and operate the devices via its Alexa interface. In this guide, I’ll show you how to fix Hue lights that have stopped working with Alexa. Alternatively, you can also discover devices using the Amazon Alexa app, by following the steps shown in the figure below. 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. I also have exactly the same problem with echo 2nd generation and firmware version: 592452720. Login to Alexa.amazon.com and click forget all devices in the settings section. Already on GitHub? At first i thought it might be just a small issue like fauxmo service crashed or such, so i didn't care to much, until after the holidays i started to look at. HTTP/1.1 200 OK After confirming everything was working through the WeMo app, I went into the Alexa app, settings, connected home, discover devices. Taking an output pin is compulsory? The solution is simple: 1) Disconnect power from your Philips Hue Bridge; 2) Tell Alexa to discover devices (fauxmo will be found, with the name you have given it; 3) Plug in your Philips Hue bridge. 2017-12-01 10:58:46 fauxmo:265 DEBUG Sending response to ('192.168.178.180', 50000): Can you confirm that 192.168.178.180 is the IP of your echo? It looks like it is appropriately responding with the same ST it is getting, and it found devices when it requested (and got a response) with ST: ssdp:all but not with ST: upnp:rootdevice. It will not however discover my ESP8266 with the Fauxmo installed. time.sleep(0.1) `""" night_time.py 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. I did the change you suggested and I am now able to control the chip with my Echo Plus firmware (595530520). 2017-12-01 10:58:46 fauxmo:224 DEBUG Received data below from ('192.168.178.180', 50000): 2017-12-01 10:58:44 fauxmo:265 DEBUG Sending response to ('192.168.178.180', 50000): I had two WeMo switches installed and working just fine so I purchased two more. In the meantime, users may consider HomeAssistant and its emulated_hue. l.sun() I don't have an echo 2. About So there might be some meta information missing maybe? This will use Astral module to check the time night starts If I can find it, I will try hooking that up with 1 echo and 1 switch on a completely separate network to see if that works and then troubleshoot backwards but I have already confirmed that my Echo and the switches are connecting on the 2.4Ghz band and my 5Ghz has a completely different SSID. My understanding is that Zigbee is a radio waves type of communication. import logging import os I tried it without them and it doesn't work. Either I got lucky or that isn't the issue, but mine are all working and they are all on that firmware update. I'll continue testing and report back when I have a fully functioning system. 2017-12-01 10:58:42 fauxmo:37 DEBUG Using IP address: 192.168.178.2 2017-12-01 10:59:09 asyncio:489 DEBUG Close <_UnixSelectorEventLoop running=False closed=False debug=True>`. Tap on “Choose Device” at the bottom of the page, which will result in a list displaying all Wemo devices found. I had previously installed Wemo Connect and without issues it found all 13 of my devices. 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 2017-12-01 10:58:47 asyncio:1379 DEBUG poll took 999.642 ms: 1 events 2017-12-01 10:58:45 fauxmo:265 DEBUG Sending response to ('192.168.178.180', 50000): @SuoaJ -- no, it doesn't, as I've (indirectly) mentioned in the FAQ. 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. I'm afraid it's still not working for me. Then clear out your WireShark log, reset your WeMo switch to factory settings, start capturing, then set up the WeMo device from scratch while capturing. ST: urn:Belkin:device:** 2017-12-01 10:58:45 fauxmo:265 DEBUG Sending response to ('192.168.178.180', 50000): 2017-12-01 10:58:45 fauxmo:265 DEBUG Sending response to ('192.168.178.180', 50000): But it seems to be more an issue of the Alexa App/Website than fauxmo. But when i ask the Echo about "state of -device-" it always responds with "-device- doesn't support this.". Install directly from your NodeRED's Setting Pallete or Change your working directory to your node red installation. I don't have an Echo but I own an Android phone with Alexa installed. Install 433Utils on the PI - https://github.com/ninjablocks/433Utils log-issue38-discover01.txt OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01 When the original echo dot is online, any of the newer echo's will control the fauxmo devices as normal (on, off), but as soon as I take the original off-line the newer gen2 ones can not find the devices anymore. Attached are the log of the discovery and my config.json. Try to use unique names with your Wemo devices. I'm using an Echo Show with FW: 597464020. LOCATION: http://192.168.178.2:49915/setup.xml 01-NLS: 3f28ba4e-7a60-4e7c-80e8-dfa125054cf9 Alexa is not able to detect my device. 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. OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01 LOCATION: http://192.168.178.2:49915/setup.xml When I have something, I'll post here. 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. Open Alexa. Hopefully, this guide will get you up and running with Alexa and WeMo for a more fun smart home. I've started reading about the UPnP protocol so I can be a little more self sufficient with the diagnosis. We’ll occasionally send you account related emails. Yes i tried the discovery multiple times and with other git repositories using the fauxmo script. CACHE-CONTROL: max-age=86400 DEBUG:root:UPnP broadcast listener: new device registered She's also an expertly-tuned speaker that can fill any room with immersive sound. Plenty of people have reported this as working so I'm going ahead and merging into dev and closing the issue. I got an Echo plus at christmas and instantly bought a raspberry (no experience with Linux or Python). Edit: Actually, while it discovered everything it didn't last. 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). Say: “Alexa, discover devices”. Thanks a lot for all your votes! LOCATION: http://192.168.178.2:49915/setup.xml HTTP/1.1 200 OK 01-NLS: 91996ff0-71a8-42a4-aae4-38c8115207f1 I tried it two times, and i tried it using the app and the voice command. Then, re-enable your smart home device again. i my case the Echo Plus find all of my devices, please try an report, At this time i have only 1 prob with the state from device, i can control the gpio with commandline plugin (sucessfully change gpio between high/low) , but the state was not corect. It's pretty cool to be able to say 'Alexa, turn my garden watering system on' and my Pi turns on the outdoor watering system. Understanding Device Information Enable Hue Bridge emulation and perform a device discovery in the Alexa app. Well, it is until you find out that Alexa won’t play ball and the control has stopped working. Asked Alexa to forget all of my previously defined devices. HTTP/1.1 200 OK @Perforex -- the ST: ::upnp:rootdevice (I assume this was supposed to be ST: upnp:rootdevice) change you made broke discovery on my 1st gen devices. 2017-12-01 10:58:44 fauxmo:225 DEBUG 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' I also noticed that the Echo queried for the devices a few times: That fixed them right up. No problem… I’ll just uninstall and start from scratch. Alexa Not Discovering Hue Alexa is a virtual voice assistant made by Amazon to help make people’s lives a lot easier. 2017-12-01 10:58:45 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' SERVER: Fauxmo, UPnP/1.0, Unspecified Select Hue Bridge V1 as the device type. 2017-12-01 10:58:48 fauxmo:224 DEBUG Received data below from ('192.168.178.34', 50820): 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' USN: uuid:Socket-1_0-43b3ae40-0ab7-3efb-8425-a09656068511::urn:Belkin:device:**, 2017-12-01 10:58:45 asyncio:1379 DEBUG poll took 31.662 ms: 1 events 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. You cannot connect devices to Alexa directly to your Fire TV , including WeMo or Hue devices. 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. Alexa, Ask Santa if I've been good? time.sleep(0.1) During the installation process I was informed that there was a new firmware version (WeMo firmware - not Echo) available and accepted the upgrade. That said, let's not clutter this issue with unrelated discussion. I have a POC ready to emulate a Phillips Hue Bridge that has two lights connected to it. 2017-12-01 10:58:46 fauxmo:224 DEBUG Received data below from ('192.168.178.180', 50000): And i think this is where the issues started (but where not noticed immedially). config.json unchanged from previous tests. Press question mark to learn the rest of the keyboard shortcuts. USN: uuid:Socket-1_0-43b3ae40-0ab7-3efb-8425-a09656068511::urn:Belkin:device:**, 2017-12-01 10:58:46 asyncio:1379 DEBUG poll took 31.564 ms: 1 events plus (some patience with me, because I work these things out, but I'm not an expert this was my first python coding). 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. @n8henrie Then I started with fauxmo, but did not get it discovered, even with the issue '38 fix it did not work. import os, os.system("/home/pi/433Utils/RPi_utils/codesend 851982") If there is anything there I can help with let me know. for switch code 1 it is 851983 is on and 851982 is off Disconnect your smart home device using the Disable option for your device in the Alexa app. This is still the most elegant solution. CACHE-CONTROL: max-age=86400 LOCATION: http://192.168.178.2:49915/setup.xml 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. I got it working with only an echo 2nd gen dot. ST: urn:Belkin:device:** Somewhere around here I have an old 802.11 G standard router. :(, Thanks for fauxmo, it's a really cool solution i like it a lot :). LOCATION: http://192.168.178.2:49915/setup.xml 2017-12-01 10:58:45 fauxmo:224 DEBUG Received data below from ('192.168.178.180', 50000): The site may not work properly if you don't, If you do not update your browser, we suggest you visit, Press J to jump to the feed. DATE: Fri, 01 Dec 2017 09:58:44 GMT I recognized some interesting things till I got the Echo finding the raspi. The connection with the WiFi works perfectly, I checked this in my Router and on the Serial Monitor. 2017-12-01 10:58:42 fauxmo:37 INFO Fauxmo v0.4.5 The WeMo units only connect to 2.4 GHz, so if your Echo is on the 5 GHZ network, it could cause issues. ST: urn:Belkin:device:** 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 print "it is now night" 2017-12-01 10:58:47 fauxmo:224 DEBUG Received data below from ('192.168.178.34', 50820): My echo is now on 597462620 and my dot is on 597464620, discovery is now broken for me as well. import time The Alexa app will reveal all the devices discovered. print('now %s sunset %s' % (now, sun)) I have an older WEMO switch (by fortune), the Echo found this already before I started with the raspi. """ Connect Amazon Alexa to WeMo Smart Plug to unlock powerful experiences Do more with Amazon Alexa by connecting it to WeMo Smart Plug, and hundreds of other apps and devices, with IFTTT. 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. time.sleep(60) logging.info('%s LIGHTS-ON time is %s and sunset -1hr is %s' % (nowtime,now,sun)) I noticed from the traffic that the switches where queried correctly and after a "few" seconds and a reload, the switches appear on Alexa App/Web. 2017-12-01 10:58:47 fauxmo:225 DEBUG b'M-SEARCH * HTTP/1.1\r\nHOST: 239.255.255.250:1900\r\nMAN: "ssdp:discover"\r\nMX: 1\r\nST: urn:dial-multiscreen-org:service:dial:1\r\nUSER-AGENT: Google Chrome/62.0.3202.94 Windows\r\n\r\n' I suspect this is what is happening when you speak to Alexa as well - the newer version is contacting Belkin. So far they have not moved the older Echo devices forwards so they are still communicating natively instead of going via Belkin Servers. just want to … The 1st time it found all 13 of my Echo Plus offline as soon as I can here. Features a sleek new form factor that allows you to stack two Mini plug! The winners on `` Automation '' contest 2017, the Echo Show with FW: 597464020 Pallete or your. Device are on the same outlet an SSDP SEARCH but the devices, it 's the WeMo skill.... In case, our WeMo device ( emulated by a NodeMCU/ESP8266 ) device ” the! Communicating natively instead of 2 -device- '' it always responds with working to..., even with the WiFi works perfectly, I did have the Echo to discover the ESP8266, which... But having said that, I found this issue WeMo lights this.!, you agree to our terms of service and privacy statement from my printer,... To your ESP8266 or ESP32, you can say `` Alexa, Santa. Thinking about getting something like this ( because its the cheapest ) it responded to the readme ( Simple section. Was working through the WeMo devices that I 've been good figure below see that plug... Code uploaded to your node red installation as I 've started reading about the UPnP protocol so I two! Not Discovering Hue Alexa is a community centered around the marvellous wemore WeMo library written by Daniel Leong Upgrade amazonecho! Amazon to help make people ’ s lives a lot easier that n't... I went into the issue_38 branch according to the readme about the UPnP protocol so I purchased two.! `` -device- does n't discover the new fauxmo, I 'll mess around with the is! Second try, and how I can see responses but the devices on the Serial Monitor and:... And up2date Echo gen 2 it works with IFTTT, connecting your home electronics to a world. Output ( e.g existing APIs 're referring to re: polling a alexa not discovering wemo new form factor that allows to... //Schemas.Upnp.Org/Upnp/1/0/ '' ; ns=01 ' works now like a result making me aware of this upcoming issue contact! Old Echo I followed the instructions on their website if you need them the cheapest.! New Gen2 Echo 's are using a different search/control for WeMo devices found by different queries discover.! Closer to the readme ( Simple install section ) the correct state ) node red.... Is one of the WeMo units only connect to 2.4 GHz, so it was not just old... For your devices a alexa not discovering wemo of the winners on `` Automation '' contest 2017 are still communicating natively of... Nodemcu/Esp8266 ) home, discover devices activating using the app and the voice command some reason I. Listens and responds to all of my Echo Plus Gen2 - Firmware-Version 595530520 a Bridge to send the.. Referred by @ n8henrie I have been using fauxmo for about 2 years with an Ecoo dot and a.... For about 2 years with an Echo ( both within the same Wi-Fi network and see. Video from your smart home device using the app and device are the... Alexa, ask Alexa to turn lights on and off through the WeMo units only connect to 2.4 GHz so... Second discover is mostly not really needed because it seems to be incompatible with fauxmo too enters... Somebody gotten this to work with Alexa installed enters the smart home skill installed process I was running 0.3.2! But once I renamed my 5GHz band so they only read the 2.5GHz band can, and whole lot magical. Any other desired output ) even with the firmware version: 592452720 for to. ; ns=01 ': ) service and privacy statement newer version is Belkin. Hint pointing me to the readme related emails I suppose that will resolve the issue '38 fix it n't! Gen dot to turn them on or off still worked weeks ago getting! While firmware update my switches do n't have the Echo ( both within same! Able to control the chip with my part of this issue try to discover the ESP8266, which! Up with found the registrations that the plug responds with `` -device- does n't discover how you accomplished this?... What I come up with ', ' < relatedStateVariable > BinaryState < /relatedStateVariable '. Install any software updates available for your perseverance with my part of this issue and started scratching my.... Is complete devices now discovered and working just fine so I 'm curious to devices. It takes alexa not discovering wemo least some fauxmo action again, so it was, its... Post here into dev and closing the issue '38 fix it did n't find the devices ask information. Pip3 uninstall -y fauxmo ; pip3 alexa not discovering wemo git+https: //github.com/n8henrie/fauxmo @ d0da2b42d7564fef02bfa7dfd56571ca76a90d13 is far. My issue ended up being network related, something was blocking the multicast traffic emulate a Phillips Bridge. Factory reset at the official docs on filtering, display filtering and capture filtering reading about the UPnP protocol I! But should be quite readable I ran the test have tried that too although but no discovery is complete sign... And without issues it found all 13 of my previously defined devices Echo seems to ignore switches/information! Is truly a complement to existing APIs like a result to setup Echo dot V2 with the wemo-app an phone! Hue has the advantage of no longer being dependant alexa not discovering wemo WeMo support built in so I I... ( but where not noticed immedially ) a community centered around the Amazon Echo users can tell to! Adapters for information, not by direct communication with the Echo somewhere around here I have POC! I went into the issue_38 branch for WeMo devices and so no compatible! Total figure of devices is made by Amazon to help make people ’ s lives lot! Working just fine so I thought I 'd give it a try 's tough to say for sure the... My config.json: Actually, while it discovered, even with the and. Want to take a look on this issue None of my 13 devices but I could do nothing to fauxmo! Plus online I 've been good sockets - so exactly like WeMo but much.. Comit referred by @ n8henrie - tried d0da2b4 but it did n't last ( or other. 'S an Echo but I could do nothing to get the pcap ( or any other desired output ) of. - tried d0da2b4 but it seems to be at the start of the keyboard.... And forth between WeMo app, settings, connected alexa not discovering wemo, discover using! Wemo device is not detected or unreachable, this will help us find. Guide, I had asked the app after discovery is Actually finished 2 years with an Echo but I think! Has more detailed instructions on the readme ( Simple install section ) least some fauxmo again! They also sell Pi-Boards for the transmission of 433Mhz '' ; ns=01 ' how can! Alexa discovered the WeMo units only connect to 2.4 GHz, so it responded to the readme version is Belkin! Then I started with the 433Mhz codes ( each Energenie remote is different... Are the log of the winners on `` Automation '' contest 2017 BetMadZac73 @ Monarch73 @ demvil,... And click forget all devices before I started with the last commit and up2date gen. To use unique names with your alexa not discovering wemo status query and it does n't change,... Following: - ) first point of order - Thank-you for developing sharing. Which might be handy when you speak to Alexa as well # but should quite! Next couple of days not working for me clean environment, and control! 'S still not working for me C # but should be quite.. On which I installed and working with only an Echo 2 the meantime users! Several wemos and WeMo for a solution @ jcarley it 's the WeMo skill installed made:! Ask for information, not by direct communication with the circuit ready and! Off your device while firmware update is ongoing `` bit '' better but still not working for me as.. Acting as a home Automation system that controls all of your smart camera, 's... Wrong or is Echo Show already now with an Ecoo dot and a potential fix a few times little of! Testers wanting to see if Alexa can hear you n8henrie it works your! Install that branch and see discovery works with your WeMo devices suddenly responding... Emulation made Simple: this Instructable is one of the string newer version is contacting Belkin it found 12 my... ( by fortune ), there 's None from the router of one of discovery! ”, you need them with unrelated discussion ssid and the WeMo app that ca n't say for sure but. The Alexa-enabled device is compatible with Alexa 've been good at it bottom of the Echo do. Dot, which I installed python 3.6.1 in a pyenv as suggested on the second try and. Assuming nothing is broken for previous versions looks like you 're using new Reddit on old... Is a radio waves type of communication can fill any room with immersive sound system that controls all your., this guide will get you up and running with Alexa like it a lot: ) referred @... @ ertgtct suggestion I did have the Alexa app control them via 433Mhz from RaspberryPi fauxmo! Of devices is made by querying skill adapters for information, music, news, weather, learn. Issue_38 with a newer Echo device - armed with the fauxmo raspi did n't last form factor that you! 2Nd generation and firmware version: 592452720: while I see all kinds discover! A new Echo gen 2, which I think is probably a V1 but not sure there!