GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Subscribe to RSS
Already on GitHub? Sign in to your account. If i run the fauxmo script with -vvv i can see that the messages are received but there is no answer. Also, please update to the latest fauxmo version though I don't think it will fix this issue, since I don't see Belkin in any of your Echo requests.
It's an Echo 2nd generation with the firmware version: Yes i tried the discovery multiple times and with other git repositories using the fauxmo script. I also have exactly the same problem with echo 2nd generation and firmware version: I have the latest fauxmo v0. Looks like that firmware is probably an issue.
Control Raspberry Pi GPIO Using Amazon Echo (Fauxmo)
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. Shout-out to Monarch73 for making me aware of this upcoming issue and a potential fix a few weeks ago. 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. Not sure if I need to do this? I think the key to takle this issue is to get fauxmo to work on echo2 with the wemo-app and asking users to activate the wemo-skill.
To activate the wemo skill you need your WiFi ssid and the Mac address of one of the wemo devices. I tried the Mac of my server running fauxmo but with no success.
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.
The wemo app is also unable to detect any fauxmo-devices. That's why I am saying, key to resolve the issue is getting fauxmo to work with the wemo-app. I suppose that will resolve the issue for the wemo-skill auto-magically Hiya, I have been using fauxmo for about 2 years with an Ecoo Dot and a Pi.The Amazon Echo is able to control certain types of home automation devices by voice. Fauxmo provides emulated Belkin Wemo devices that the Echo can turn on and off by voice, locally, and with minimal lag time.
As of version v0. Otherwise, check out the FAQ section at the bottom for tips on installing an older Fauxmo version though note that I will not be continuing development or support for older versions.
These devices are then exposed individually, each requiring its own port, and may be referred to as a Fauxmo device or a Fauxmo instance. The Echo interacts with each Fauxmo device as if it were a separate WeMo device.
This is a good strategy for testing features in development — for actually contributing to development, clone the repo as per below. If you want to use them, you either need to clone the repo or you can download them individually using tools like wget or curl by navigating to the file in your web browser, clicking the Raw button, and using the resulting URL in your address bar.
Plugins are small user-extendible classes that allow users to easily make their own actions for Fauxmo to run by way of Alexa commands. They were previously called Handlers and may be referred to as such in places in the code and documentation.
Fauxmo v0. A few plugins and the ABC from which the plugins are required to inherit may be included and installed by default in the fauxmo. Any pre-installed plugins, like the rest of the core Fauxmo code, have no third party dependencies. As of Fauxmo v0. Users can easily create their own plugins, which is the motivation behind most of the changes in Fauxmo v0.
In addition to the above, if you intend to share your plugin with others, I strongly recommend that you:. Be aware, when fauxmo loads a plugin, it will add the directory containing the plugin to the Python path, so any other Python modules in this directory might be loaded by unscrupulous code.
This behavior was adopted in part to facilitate installing any plugin dependencies in a way that will be available for import e. NB: You may need to manually install additional dependencies for these to work — look for the dependencies in the module level docstring. I recommend that you copy and modify config-sample. Fauxmo will use whatever config file you specify with -c or will search for config. The minimal configuration settings are:. Each user plugin should describe its required configuration in its module-level docstring.
Please see config-sample for a more concrete idea of the structure of the config file, using the built-in SimpleHTTPPlugin for demonstration purposes. I am not a technology professional and make no promises regarding the security of this software.
Specifically, plugins such as CommandLinePlugin execute arbitrary code from your configuration without any validation. That said, if your configuration can be tampered with i.To get a confirmation of change in state for GPIO you either look at the terminal in which you will run the code or use this instructable to connect GPIO for this project to an LED for visual check.
Did you use this instructable in your classroom? Add a Teacher Note to share how you incorporated it into your lesson. The Echo discovery ends in 20 secs; before the script can respond to discovery if all 26 gpio pins are included.
Hence in the above source code only the gpio16 - gpio26 are added as devices and can be controlled. Looking for a fix or alternative I installed it, It runs with no errors, but Alexa does not find any device. I am in Germany, my Alexa speaks German.
Is there a problem with this? Reply 2 years ago. I tried something. I wrote the IP:Port in my browser - an the raspeberry reacted. So I am sure, the script is running.
But Alexa still cant find the devices from raspberry. But it finds the Hue-Lamp from Philips. Reply 8 months ago. Also use a static IP address on your raspberry pi. If your raspberry pi IP address changes you will have to have Delete the fauxmo devices from the Alexa App and redo the discovery process again Hint: When trying to discover your fauxmo devices place fauxmo.
The fauxmo. Reply 9 days ago. Hey there, i also have that problem My pi is also reacting when i try to contact it via browser. Still Alexa can't find the device I ended up fixing mine, but I am unsure exactly how; however, I narrowed down a couple things I did. I had a problem using the amazon echo, but I tried my sons amazon dot and it worked flawless.
Troubleshoot Smart Home Device Discovery Issues
Your gpiocontrol. I have one working and only using 3 gpio ports I'm trying to get another rPi running with a different 3 ports but can't get Alexa to discover the ports. The way fauxmo. Of course each raspberry pi will HAVE different IP addresses otherwise you would not be able to talk to each raspberry pi over your Ethernet.
You DHCP server or your router does this for you automatically. Is there another way to autostart the script without using crontab? Reply 1 year ago. I'm having the same problem. Adding the cron with reboot directive or adding to rc. Logging in when the device boots up to run a command is not the same functionality as a reboot directive in cron. By surendrakane Follow. More by the author:.GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Already on GitHub? Sign in to your account. Python 3. Can see another device retrieving setup. I can however see the request going out, so assume that the Echo is not recognising our response string. For info, the IP address of the Echo is Going through the log file a bit more, I can see that the request received from the Echo is different to the other devices:.
It could be, I'll not be able to check things out for a couple days, sorry. Your logs look like mostly search requests that may be from other devices, they don't look like the usual Echo requests I wonder about UPNP requests from the media player on your other Pi. The initial request from the Echo is showing up as 'Man: "ssdp:discover"' whereas the one we responded to had 'MAN: "ssdp:discover"'. Checked protocols. While I've got you, just wanted to say absolute kudos to you for doing this project.
Pretty fantastic functionality, so thank you very much for all of your efforts. Need to brush up on my Python skills first though.
Good catch, that could be it. I wonder why it's now coming out as Man:? The following change in protocols. The echo is definitely It looks like it is the discovery patterns - I'll try your change to protocols.
I was thinking of trying a physical reset of the Echo as it has been a fair few attempts to discover devices. Otherwise I'll get wireshark out to have a proper look at what is going on.
I am learning far too much about UPnP here. Way more than I intended to when I started this home automation lark. As to adhering to standards - some overly zealous developer at Amazon didn't like the aesthetics of "MAN" vs "Man"? I'm in the same boat after changing the string - fauxmo responds now but the Echo doesn't see device. Can anyone provide a dump from a real wemo device so we can fix this?
Okay - went out and bought a Wemo to try this with. Got the trace attached but not had a proper look at it yet. I'll look at it tonight or tomorrow but if you want to have a look at it in the meantime, feel free. I've been following this post silently but I've read the other issue 38 and installed the dev branch but still didn't work either.I spend several hours searching for a solution, but everything I found didn't work for me.
I tested the following things: - Reinstall this and serveal other sketches that I found - Checking if Upnp is activated on the router which it was - Tested the whole thing in another wifi network - Installing an older version of fauxmoESP tested 2. So in the end of this research I have no idea anmore what the problem could be. Nobody seems to have the same problem. Are you using the example sketch from the library or your own? I also looked in the debug information: On startup every thing seems to work ok, no errors, but when searching for devices in the alexa app, theres no message at all, it seems, that the ESP isn't registering anything.
I am having the exact same problem. My ESP connects to the network, I've tried numerous different codes and sketches. Curiously, Alexa states that "22 smart home devices" are discovered I have 5 or 6 other legitimate devices but none of the Arduino devices appear on the Alexa app nor can they be controlled. For example, if I called one "Fan" which is on the ESP, "Fan" doesn't appear on the list and Alexa says it doesn't recognise the name.
Do you see them registering on the debug log? Does the debug log show the UDP discovery messages? This is my debug log with one device called "switch one". I had this exact problem, too. All my old echo devices work fine. New ones only work if there is an old echo device in the network which can be used as a relay. As soon as a new echo device is "alone" in the network, there is no communication with a fauxmoesp device.
Hi I wasn't aware the new Echo devices worked differently No discovery message? Hi, having the same issue. Just got my Echo 2nd Gen. Unfortunately i cannot verify that it works on 1st Gen Device. XXX" when i start discovery process via Alexa App. I will get an echo dot 1st gen tomorrow or the day after Hey, Before or after attaching a 1st gen dot to your network? With the newest version of the fauxmoESP-Lib was updated yesterdayI receive search requests, but the echo don't discover any new devices That would probably mean the Echo is expecting something specific on those services that the library is not providing Like i mentioned my echo 2nd gen now works with current version.
Only when switching on emulated device Alexa is saying there is no response. But still switching on sockets via rcswitch library. Fabian: i could share my code if u are interested? Then you could try if it works with your echo 2nd gen.
It only takes a minute to sign up. I am trying to connect to Alexa for voice controlling. I have Amazon Alexa Echo 2 from which I am trying to discover my nodemcu as a smart home device. Alexa is not able to detect my device. If you are using fauxmoESP library version 3. You may degrade fauxmoESp version to 2. Sign up to join this community. The best answers are voted up and rise to the top. Home Questions Tags Users Unanswered. Asked 1 year, 6 months ago.
Active 3 months ago. Viewed 2k times. Here is my sketch I am trying to use to detect. Taking an output pin is compulsory? I have tried that too although but no output found. Thank you! Active Oldest Votes.
Are you able to connect wifi? Yes it worked before itself. And yes i was able to connect through Wifi. Sign up or log in Sign up using Google. Sign up using Facebook.If I use v2. If I update to the 3.
In both cases I was using the provided example sketch and only changed my wifi creds and the plug name. Same here. Not working with my esp on version 3. I see that the lib switched from emulating WeMo to emulating Philipps Hue? Does that mean that I manually have to enable the Philipps Hue skill for Alexa before this works?
If so, that should be mentioned in the documentation, because now it's not.
In any case, I am also unable to enable that skill, because when trying to enabling it in the Alexa app, it just forwards me to the Philipps page and wants me to login. After logging in, it searches for some "philipps bridge" which if of course can not find and there is no way to skip that step. I'm wondering if the switch to the Hue protocol means that a Hue bridge is required now. That seems to be the only way to add Hue devices to Alexa is via a bridge excepting v1 Hue devices.
Kind of sad that this isn't in the documentation and the move to a method that requires another device in the chain. Adam, I think the code is emulating a Hue Bridge, but I am not sure. I also think it's weird that they would switch to a completely new protocol all of sudden without any deeper documentation on what's going on.
They should have created a completely new project instead of just updating the version number to 3. Much better than having this crap break between versions. Hello Daniele, After some head banging last night some hints in other threads lead me to this I found that if you're using the Arduino IDE if you switch to the 2.
Showed up a some kind of Hue bulb. The dimming even worked. Ok, that's cool. I might give it another try. However, this kind of proves my point. If a software can break because of changes in the framework, it's most likely not good code. Not following framework guidelines etc. Having to be afraid that everything will stop working every time the software gets a new version or the frameworks gets an update is not very pleasant.
Also, if the newest version of the framework breaks the code, why haven't this been noticed and fixed? Is nobody using this code? Is nobody maintaining it? This bug was reported 2 months ago with no response. Hello Daniele and Others, we are all on the same boat. This is my enviroment: Arduino IDE 1. You have to fall back to ESP 2. Had this problem yesterday.Alexa voice command won't turn on my lights.
Now it works fine for me with my Echo Dot 2nd generation. One issue I found on trying to get it running is, that enable is by default true but I think it should be false.