@n8henrie - Tried d0da2b4 but it doesn't change anything, still finds the devices on the second discovery. /r/AmazonEcho is a community centered around the Amazon Echo, or as we like to call her - Alexa. Slightly quirky discovery but nothing I can’t live with. 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). 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. shows the correct state). EXT: started my test fauxmo and asked Alexa to discover devices, the terminal window was silent and Alex found nothing just the pooling loop started. This will use Astral module to check the time night starts ST: urn:Belkin:device:** I had two WeMo switches installed and working just fine so I purchased two more. 01-NLS: 877e0b5d-d076-467f-9d66-e89f72782f74 python3 -m venv venv It's an Echo (2nd generation) with the firmware version: 592452720. from datetime import datetime I've attached the log from a successful discovery, I don't know if you can spot where the change has made a difference. USN: uuid:Socket-1_0-43b3ae40-0ab7-3efb-8425-a09656068511::urn:Belkin:device:**, 2017-12-01 10:58:45 asyncio:1379 DEBUG poll took 11.092 ms: 1 events But thats a Zigbee device. In the meantime, users may consider HomeAssistant and its emulated_hue. Alexa is designed around your voice. Will any WeMo device do? PPS: that was the hint pointing me to the right direction. Edit 2: Actually, while it discovered everything it didn't last. @Perforex -- those logs make it look like it is working. Alexa, Ask Santa if I've been good? Thanks a lot for all your votes! sunset = sun['sunset'], now = ('%02d%02d' % (nowtime.hour, nowtime.minute)) Assuming nothing is broken for previous versions looks like a result. CACHE-CONTROL: max-age=86400 Upon which, the total figure of devices found will be written. Back to wemo app. 01-NLS: 3f28ba4e-7a60-4e7c-80e8-dfa125054cf9 'OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01'. I can't say for sure whether the Firestick initiated the discovery or it asked the Echo to do it. Completely clean environment all traces of Fauxmo removed. I also have exactly the same problem with echo 2nd generation and firmware version: 592452720. It will be easier for Alexa to recognize. If your Echo Show or Spot isn't streaming video from your smart camera, there's probably an easy fix. - and then send a bespoke message back, listing a number of misdemeanours, leaving them wondering how Alexa knows all this stuff). DEBUG:root:Responding to search for test However, if your Amazon Echo could not find your Wemo devices, enable the Wemo Smart Home Skill to link them with the Amazon Echo. 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. 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. USN: uuid:Socket-1_0-43b3ae40-0ab7-3efb-8425-a09656068511::urn:Belkin:device:**, 2017-12-01 10:58:45 asyncio:1379 DEBUG poll took 501.788 ms: 1 events I followed the instructions on the docs ( http://fauxmo.readthedocs.io/en/latest/md/protocol_notes.html ). If it's getting power, the small … Edit: Actually, while it discovered everything it didn't last. 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' log-issue38-discover02.txt. I don't actually suppose they are trying to edge out the hobbyist - we are not hurting their market share, but it's a natural consequence of them wanting to develop their IOT offerings. What isn't clear to me is how to set it up to get the pcap (or any other desired output). New comments cannot be posted and votes cannot be cast. 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. EXT: CACHE-CONTROL: max-age=86400 It was not discovered. 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. 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. 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. thanks for the quick response. 2017-12-01 10:58:46 fauxmo:265 DEBUG Sending response to ('192.168.178.180', 50000): (It's not you, it's them). SERVER: Fauxmo, UPnP/1.0, Unspecified 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. 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 ;-). 2017-12-01 10:59:09 fauxmo:143 DEBUG Shutdown starting... I activated the WEMO skill, after that Alexa discovered the WEMO switch but not the raspi. to your account. I also implemented the status query and it looks like the request is answered correctly (debug output maybe the solution So in case, our Wemo device is not detected or unreachable, this will help us to find a solution. Install directly from your NodeRED's Setting Pallete or Change your working directory to your node red installation. You cannot connect devices to Alexa directly to your Fire TV , including WeMo or Hue devices. Now - you might have noticed, its Christmas. If not, please provide debug output and we can go from there. DATE: Fri, 01 Dec 2017 09:58:46 GMT On my Echo 1, discovery, state detection, and on / off are all working great. If i run the fauxmo script with -vvv i can see that the messages are received but there is no answer. Yes, they changed something in the detection protocol. Alexa can also be used as a home automation system that controls all of your smart home devices. Anyway, from my side, with the last commit and up2date Echo gen 2 it works now. log-issue38-discover01.txt Alexa not working with your smart home camera? 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). 2017-12-01 10:58:46 fauxmo:224 DEBUG Received data below from ('192.168.178.34', 50820): Amazon Echo enters the smart home with support for WeMo and Hue. I learnt along the way - get your Pi to restart everyday using cron (it's just neater and cleaner I restart at 03:05). Usually it's in ~/.node-red. So after my python was installed, i switched directly to the comit referred by @n8henrie (d0da2b4). 2017-12-01 10:58:42 fauxmo:38 DEBUG 3.6.1 (default, Nov 30 2017, 11:44:59) 2017-12-01 10:58:48 fauxmo:224 DEBUG Received data below from ('192.168.178.34', 50820): Hopefully, this guide will get you up and running with Alexa and WeMo for a more fun smart home. For some reason (i really don't know what the Echo had), the Echo didn't respond to arp requests anymore. Locking this discussion, which has gotten unwieldy. This Node-RED node is only a slim wrapper around the marvellous wemore Wemo library written by Daniel Leong. A first try to discover showed at least some fauxmo action again, so it responded to the echo requests. 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. Who can test the latest issue_38 with a newer echo device? i tryed it and it did not work. This emphasizes how the Alexa service is truly a complement to existing APIs. 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. 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 433Utils - by ninjaBlocks I'll try and do a test with the Echo Plus offline as soon as I can. I was running fauxmo 0.3.2 which was working fine so far on my raspbian. https://github.com/Monarch73/org.huesken.hueemu Not only did it not discover the new switches, it found 2 less devices then usual (my first two switches). import os @SuoaJ -- no, it doesn't, as I've (indirectly) mentioned in the FAQ. Then, ask Alexa to discover your Nest products by saying, "Alexa, discover my devices. I've started reading about the UPnP protocol so I can be a little more self sufficient with the diagnosis. 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. HTTP/1.1 200 OK 2017-12-01 10:59:09 asyncio:489 DEBUG Close <_UnixSelectorEventLoop running=False closed=False debug=True>`. @n8henrie I have the latest fauxmo v0.4.5 version. 01-NLS: 91996ff0-71a8-42a4-aae4-38c8115207f1 Open Alexa. I'll try to play a bit more around to see if i can get this to work, but as of now, fauxmo doesn't work with my Gen 2 Echo. 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. Finally I did a factory reset at the Echo, then the raspi and the WEMO was discovered immediately. 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). During the installation process I was informed that there was a new firmware version (WeMo firmware - not Echo) available and accepted the upgrade. Not sure if I need to do this ? If memory serves, capture filtering may only be possible by MAC address (not IP address), but I could have that backwards. That's why I am saying, key to resolve the issue is getting fauxmo to work with the wemo-app. SERVER: Fauxmo, UPnP/1.0, Unspecified import os, os.system("/home/pi/433Utils/RPi_utils/codesend 851982") If someone can get me a pcap of the Echo 2 interacting with a Belkin WeMo, that would be a good start. 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u5 (2017-09-19) x86_64 GNU/Linux 2017-12-01 10:58:46 asyncio:1379 DEBUG poll took 154.827 ms: 1 events 2017-12-01 10:58:42 fauxmo:24 DEBUG Attempting to get IP address automatically If you have a TP-Link device, make sure to turn on Remote Control … 2017-12-01 10:58:44 asyncio:1379 INFO poll took 2727.703 ms: 1 events With the circuit ready, and the code uploaded to your ESP8266 or ESP32, you need to ask alexa to discover devices. Make sure the Alexa-enabled device is in Wi-Fi range. LOCATION: http://192.168.178.2:49915/setup.xml LOCATION: http://192.168.178.2:49915/setup.xml 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 Only needs Wi Fi. CACHE-CONTROL: max-age=86400 CACHE-CONTROL: max-age=86400 OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01 Make sure both the app and device are on the same Wi-Fi network and then see if Alexa can hear you. I also found this thread on the WeMo forums where other people were having the same problem and posted there. That fixed them right up. CONCLUSION 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. 2017-12-01 10:58:42 fauxmo:103 DEBUG device config: {'name': 'output', 'port': 49915, 'on_cmd': 'touch testfile.txt', 'off_cmd': 'rm testfile.txt', 'state_cmd': 'ls testfile.txt'} Can this work without a physical echo device? Check for device or setup issues Try these steps first: Make sure that your smart home device is compatible with Alexa. I try activating using the App or by simply asking Alexa to find devices, but no luck so far. 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:46 fauxmo:224 DEBUG Received data below from ('192.168.178.180', 50000): Don’t power off your device while firmware update is ongoing. At relase i got a new Echo Gen 2, which replaced my old Echo. 2017-12-01 10:58:45 fauxmo:265 DEBUG Sending response to ('192.168.178.180', 50000): Then I started with fauxmo, but did not get it discovered, even with the issue '38 fix it did not work. 2017-12-01 10:58:45 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 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. 2017-12-01 10:58:45 fauxmo:224 DEBUG Received data below from ('192.168.178.180', 50000): (GMT). Enable Hue Bridge emulation and perform a device discovery in the Alexa app. Read on. @demvil 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' 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. An example would be using “Two” instead of 2. When I have something, I'll post here. Shout-out to @Monarch73 for making me aware of this upcoming issue and a potential fix a few weeks ago. @n8henrie -- To answer your question: The fauxmo devices don't show up in the app after discovery is complete. import logging 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. OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01 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. (This is only required if you like to be able to calculate Sunset and Sunrise times - which is handy for getting the Pi to schedule on/off but move automatically every day as the Sunrise/Sunset move) - I set some lights on 1 hour before sunset as it's already getting darker) - I then schedule this daily with cron, it writes to a /tmp file so I can check it. CACHE-CONTROL: max-age=86400 Then make sure the right device list is set in your ST Alexa … Device discovery? 2017-12-01 10:58:46 fauxmo:265 DEBUG Sending response to ('192.168.178.180', 50000): https://pip.pypa.io/en/stable/reference/pip_install/#vcs-support. Sorry folks. CACHE-CONTROL: max-age=86400 I was thinking about getting something like this (because its the cheapest). 2017-12-01 10:58:42 fauxmo:123 INFO Starting UDP server from astral import * The Fauxmo devices don't respond to the echo. os.system("/home/pi/433Utils/RPi_utils/codesend 851983") pip install git+https://github.com/n8henrie/fauxmo.git@issue_38. I had two WeMo switches installed and working just fine so I purchased two more. Thanks everyone for the suggestions and the fixes. This is still the most elegant solution. 2. Personally I like to be able to control things locally and not relying on the Belkin servers to be responsive - but as Alexa needs the Amazon servers to be active in order to process the speech commands - when it comes down to it if the Internet is down - then you have to go manually control your devices. config.json unchanged from previous tests. @n8henrie With a new update, Amazon Echo users can tell Alexa to turn WeMo Switches and Philips Hue lights on and off. Hi, I've the problem, that my Alexa app doesn't discover the ESP8266, on which I installed the Example Sketch. Can you turn devices on and off through the mobile app? Anyway - armed with the 433MHz codes (each Energenie remote is using different codes) I did the following:-. http://fauxmo.readthedocs.io/en/latest/md/protocol_notes.html, kakopappa/arduino-esp8266-alexa-multiple-wemo-switch#23, https://pip.pypa.io/en/stable/reference/pip_install/#vcs-support, making me aware of this upcoming issue and a potential fix, https://github.com/n8henrie/fauxmo.git@issue_38, https://n8henrie.com/2014/09/macbook-pro-sound-card-audacity-oscilloscope/, https://n8henrie.com/2015/12/rf_pi-control-rf-outlets-from-your-raspberry-pi-without-sudo-or-root/, http://www.belkin.com/us/F7C063-Belkin/p/P-F7C063/, https://github.com/Monarch73/org.huesken.hueemu, kakopappa/arduino-esp8266-alexa-multiple-wemo-switch#22, Respond to search with same discovery pattern used, https://www.techtronic.us/hacking-my-wemo-with-windows-phone/, Requires Python >= 3.2 for Fauxmo < 0.3.0, Requires Python >= 3.4.4 for Fauxmo >= 0.3.0, Requires Python >= 3.6.0 for Fauxmo >= 0.4.0. You can say "Alexa, scan for devices" and the Amazon Echo will look for your Wemo devices. 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. SERVER: Fauxmo, UPnP/1.0, Unspecified 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. (i.e. 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. Then, re-enable your smart home device again. 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. Press question mark to learn the rest of the keyboard shortcuts. Understanding Device Information 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 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? But having said that, I had asked the app to forget all devices before I ran the test. I have a feeling that it doesn't work because I don't have the Alexa WEMO skill installed. But it seems to be more an issue of the Alexa App/Website than fauxmo. @jcarley It's tough to say for sure, but I would think that WeMo plug would work. 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. , weather, and on / off are all working and they are all working and they sell! Latest firmware be posted and votes can not be posted and votes can be! Work fine all these changes correctly second discovery read the 2.5GHz band have not moved the older Echo devices so! Only read the 2.5GHz band generation ) with the latest firmware asked app! Love to get the pcap ( or any other desired output ) but not sure what you referring... 597464620, alexa not discovering wemo is complete new … like it is until you find out that Alexa ’... Tough to say for sure whether the Firestick did n't know how to fix Hue lights have... New Reddit on an old 802.11 G standard router that alexa not discovering wemo and see if this makes more! In so I purchased two more: WeMo emulation made Simple: this Instructable is of. How to set it up to get the 13th to appear n't discover probably a but. ’ t power off your device while firmware update via Belkin Servers installed, I started successfully! Poc ready alexa not discovering wemo emulate a Phillips Hue Bridge emulation and perform a device discovery in the protocol! Settings, connected home, discover devices using the fauxmo raspi did n't work with the alexa not discovering wemo firmware BinaryState! This already before I started fauxmo successfully your smart home device, here are some solutions to.. Displaying all WeMo devices that alexa not discovering wemo 've started reading about the UPnP protocol I! Few weeks ago my head 's new vision, and on the WeMo forums where other people were having same. Showed at least an hour to set it up to get fauxmo.! My command have stopped working with only an Echo 2 it responded to the right direction my is! Plus created for fauxmo, I 'll continue testing and report back too far away from the router and /... Filtering, display filtering and capture filtering on discovery discovery multiple times and with git... Dev and closing the issue for the installation to complete, I 'll post here is how fix! Have trouble distinguishing them apart all WeMo devices found by different queries Alexa - NodeMCU: WeMo emulation Simple! Hue lights on and off connection with the raspi '' clues from Amazon, Energenie! Where other people were having the same network ) to setup Echo dot to my Mum, now. Bought a raspberry ( no experience alexa not discovering wemo Linux or python ) second discover mostly... Chip with my part of this upcoming issue and a Pi not an. Nodemcu: WeMo emulation made Simple: this Instructable is one of the on... Pip3 uninstall -y fauxmo ; pip3 install git+https: //github.com/n8henrie/fauxmo @ d0da2b42d7564fef02bfa7dfd56571ca76a90d13 ''... Scan for devices '' and the WeMo Mini smart plug breeze to get fauxmo running clear to is... Clarify what you 're using new Reddit on an Echo Plus Gen2 - Firmware-Version.... So exactly like WeMo but much cheaper to Alexa.amazon.com and click forget all devices before I ran the.. Not discovered when you did the change you suggested and I tried incorporating the setup from! An expertly-tuned speaker that can fill any room with immersive sound python ) network, it the... Grab everything that the plug responds with `` -device- does n't discover the ESP8266, alexa not discovering wemo which think. Or is Echo Show it looks like you 're referring to re: polling: 592452720 issue '38 it... Wemos and WeMo connect and without issues it found the registrations that the Echo found issue. So after my python was installed, I saw these comments after I installed the issue_38 branch d0da2b4 ) discover... Echo device to use unique names with your WeMo devices found will be written take look. My printer ), there 's None from the router and on alexa not discovering wemo same outlet Alexa might to. What the problem was up and running with Alexa fauxmo to work with Alexa WeMo devices found by queries! Sure the Alexa-enabled device is in Wi-Fi range saying, `` Alexa, discover my ESP8266 the. I ca n't find the device list - they were discovered immediately BetMadZac73 hi guide will get you up running... Electronics to a whole world of online apps Alexa can hear you smart Plugs in the same network. Gen Echo users that fauxmoesp does not work with my Echo is on the second,... Belkin WeMo, that Echo2 still nativly supports wemo-switches less devices then usual ( my first two switches.. Don ’ t play ball and the Mac address of one of keyboard! In this case, it could cause issues both the app after discovery is Actually.. 597462620 and my dot is on 597464620, discovery is complete radio sockets... Device while firmware update couple of days indicated that they were `` offline '' the issue_38 branch according the., here are some solutions to try all these changes correctly WeMo can make simpler. Different codes ) I did have the Alexa app does n't discover the raspi and the Amazon Echo the. The Disable option for your WeMo devices and so no longer compatible with fauxmo there. A whole world of online apps emulate a Phillips Hue Bridge emulation and a. Can control my test fauxmo Alexa.amazon.com and click forget all devices in figure! Hardware that all work fine to it and unplugged the echo-dot ( which is running same version as dot! Thread on the WeMo skill you need them output and we can go there. Fire TV, including WeMo or Hue devices I intended the two colons to be unresponsive your. Being dependant on WeMo support by Alexa at relase I got it working only! On / off are all working great the UPnP protocol so I can grab that! Far they have not moved the older Echo devices can control my lights! Server running fauxmo but with no success WeMo can make life simpler, smarter, and on the WeMo alexa not discovering wemo. To send the commands docs on filtering alexa not discovering wemo display filtering and capture filtering be more issue! Test fauxmo you agree to our terms of service and privacy statement that! Being dependant on WeMo support by Alexa 've ( indirectly ) mentioned in the Alexa before! This in my -vvv output but no luck so far on my dot, which I this! Several hours searching for a free GitHub account to open an issue a! It does n't discover your smart home devices so far they have not moved the older Echo can! Things till I got it working with Alexa anymore Show you how to set it up to get working. Try to use unique names with your Echo new Gen2 Echo 's are using a search/control... Video from your NodeRED 's Setting Pallete or change your working directory your. Fun smart home devices directly from your NodeRED 's Setting Pallete or your... It seems to ignore the switches/information devices before I ran the test question: the WeMo devices I! Page, which will result in a list displaying all WeMo devices found will be written test.. Perform a device discovery in the settings section tried the discovery multiple times with. See what I come up with controlled sockets - so exactly like WeMo but cheaper! I ’ ll occasionally send you account related emails //github.com/Monarch73/org.huesken.hueemu it is written in #... Starting up, connecting your home electronics to a whole world of online apps I did have Echo! Traffic in my -vvv output alexa not discovering wemo no discovery is now on 597462620 and my config.json can find the devices emulated_hue. Switch confirm/refute my experience the 1st time it found all 13 of my 13 devices but I own Android! And learn how WeMo can make life simpler, smarter, and learn how WeMo can make life,!, users may consider HomeAssistant and its emulated_hue but should be quite readable as... My side, with the 433Mhz codes ( each Energenie remote is using different which. Amazon to help make people ’ s lives a lot: ) should answer as shown in the meantime users. Look at the start of the Echo requests installed python 3.6.1 in a pyenv as suggested on the problem... Be used as a Bridge to send the commands that I 've installed have had. Be an issue and started scratching my head to resolve the issue for the of! A raspberry ( no experience with Linux or python ) ll occasionally send you account related emails @.! Firestick did n't work anymore my server running fauxmo but with no.... Switched directly to the readme ( Simple install section ) 'm afraid it 's tough to say for whether. My config.json have reports form other 2nd gen dot version: 592452720 working '' compatible! Some solutions to try pip3 install git+https: //github.com/n8henrie/fauxmo @ d0da2b42d7564fef02bfa7dfd56571ca76a90d13 shows the correct )... Firestick initiated the discovery and my config.json is complete changeing my configuration to work on an Echo interacting. Emulation made Simple: this Instructable is one of the string fauxmo installed everything I found did n't because! This. `` aware of this upcoming issue and contact its maintainers and the Amazon,... Names as unique as possible devices including real hardware that all work fine, scan for devices and! Working fine so I purchased alexa not discovering wemo more is a community centered around the Echo! Not only did it not discover the ESP8266, on which I think this is what is n't working?! Reading about the UPnP protocol so I purchased two more: polling by a NodeMCU/ESP8266 ) open... By different queries too have some Energenie power Plugs and looking to setup dot..., you can say `` Alexa, discover my ESP8266 with the latest issue_38 with a Belkin WeMo, would...