v3.0 not discovered by Alexa #58
Comments
|
Original comment by Daniele Testa (Bitbucket: danieletesta, GitHub: danieletesta). Same here. Not working with my esp8266 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. |
|
Original comment by Kai Wienberg (Bitbucket: kaiwienberg, ). I have the same problem, my ESP8266 does not get discovered with the example sketch |
|
Original comment by Adam Byers (Bitbucket: adamslab, GitHub: adamslab). 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. |
|
Original comment by Daniele Testa (Bitbucket: danieletesta, GitHub: danieletesta). 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. They claim that the Hue API is easier to use as the API is openly documented and adds additional features as dimming etc. I ended up just creating a super simple REST API together with an Alexa skill. Much better than having this crap break between versions. |
|
Original comment by Adam Byers (Bitbucket: adamslab, GitHub: adamslab). 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.3.0 ESP8266 board version it discovered just fine. Showed up a some kind of Hue bulb. The dimming even worked. So, I think the issue is between the latest Fauxmo code and the latest ESP8266 core for Arduino. |
|
Original comment by Daniele Testa (Bitbucket: danieletesta, GitHub: danieletesta). 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. |
|
Original comment by Luca Inox (Bitbucket: LucaInox, ). Hello Daniele and Others, we are all on the same boat. This is my enviroment: Arduino IDE 1.8.7 - Echo Dot Mini 3rd generation - ESP8266 2.3.0 or 2.4.2 - fauxmoESP 3.02 - ==> device never discovered by Alexa. |
|
Original comment by Stefan Grünwald (Bitbucket: stefan84, GitHub: stefan84). One issue I found on trying to get it running is, that enable is by default true but I think it should be false. So you have to call fauxmo.enable(false); and fauxmo.enable(true); Now it works again with my Echo Dot. |
|
Original comment by Luca Inox (Bitbucket: LucaInox, ). Stefan are you using an echo dot 3rd generation? It seems to me that 3rd generation echo devices are not supported (yet). |
|
Original comment by Daniele Testa (Bitbucket: danieletesta, GitHub: danieletesta). Luca, wouldn't that be very odd? The code is suppose to emulate a Philipps Hue device, which even has an "open" API. Why would support for Hue break in 3rd generation? If that is true, it's just absurd. |
|
Original comment by Luca Inox (Bitbucket: LucaInox, ). Daniele, many people here claim that using framework 2.3.0 the code works with echo dot 2nd generation. I have a 3rd generation device and i was not able to see my wemos D1 mini discovered by Alexa. I only loaded the basic example provided with the library just fixing the minor bug file name "credentials.sample.h". |
|
Original comment by Andrew D (Bitbucket: [Andrew Drummond](https://bitbucket.org/Andrew Drummond), ). Changing from lwIP variant "v2 lower memory" to "v2 higher bandwidth" in the arduino ide allowed my "devices" to be discovered when they were not before. Hope this helps others. |
|
Original comment by Luca Inox (Bitbucket: LucaInox, ). Andrew D please can you tell us about your enviroment? ESP8266 Framework version number, Arduino IDE version, echo generation etc. and also where to find that lwIP variant parameter? |
|
Original comment by Andrew D (Bitbucket: [Andrew Drummond](https://bitbucket.org/Andrew Drummond), ). 2.5.0-dev, but also tried and succeeded with 2.4.0 framework. |
|
Original comment by Luca Inox (Bitbucket: LucaInox, ). sorry nothing for me the only difference is echo dot v3 i tried to follow exactly your enviroment. |
|
Original comment by Stuckey (Bitbucket: Stuckeymax, GitHub: Stuckeymax). I have a Philips Hue Bridge v1.0 talking to three Philips bulbs. Having this bridge device will not help with the ESP8266 emulating Hue. The Hue bridge is a bridge between Ethernet and the Philips bulbs, which speak 2.4-GHz Zigbee, not 802.11, My current problem: the compiler error message: 'class fauxmoESP; has no member named 'onMessage' working on how to get 2.3.0 going. |
|
Original comment by Carlos Yz (Bitbucket: [Carlos Yamazaki](https://bitbucket.org/Carlos Yamazaki), ). Stuckey, the function call is different in 2.4.4 and 3.02 examples: 3.0.2 and onMessage function exists only in version 2.4.4 and below causing the error, in my case |
|
Original comment by Peter Feerick (Bitbucket: pfeerick, GitHub: pfeerick). With v2.4.2 of the ESP8266 Arduino Core, I was able to get a ESP8266 'Witty' module working perfectly so far by setting the lwIP option to 'v1.4 Higher Bandwidth'. 'v2 Higher Bandwith' made the difference between the ESP8266 being discoverable by the Echo Dot Gen2, but would make the ESP8266 crash if I issued a voice command which asked for a specific brightness to be set. Simply on and off commands were fine, but soon as I asked for a specific brightness it would crash and the WDT would trigger a reset. 'v1.4 Higher Bandwidth' seems to have resolved that, and it is working great so far. Thanks for pointing that out as a possibility... I thought my new echo dot was going to be about as useful as a hockey puck! :D |
|
Original comment by Rob Janssen (RobIII) (Bitbucket: [Rob Janssen](https://bitbucket.org/Rob Janssen), ). Same here. Works fine on an Arduino Uno, Wemos d1 mini doesn't work (not v2.x nor 3.x). Echo dot v2. |
|
Original comment by Luca Inox (Bitbucket: LucaInox, ). I tried to replicate your steps but no success. So i want to enumerate here what i did to find if i misunderstood your post. Then i edited fauxmoESP.cpp char match[] = {"POST /api"}; Then i edited the fauxmoESP_Basic.ino i left fauxmo.addDevice("light 1"); and deleted fauxmo.addDevice("light 2"); Compiled everything successfully. |
|
Original comment by Stuckey (Bitbucket: Stuckeymax, GitHub: Stuckeymax). If you have a Philips Hue Bridge on your network, Alexa will not discover your fauxmo devices. 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. 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. Just tell Alexa to discover, she'll say no new devices, and in a minute or two, your new device name will be recognized. I'm using kakopappa's irdevkit.ino version found at https://gist.github.com/kakopappa/02299a8ceec0aaaad3ea3bd7f2af8066 Works well. I can get four button-push commands out of it to a single device using the four binary states of 1) Command on while state is off; 2) Command off while state is on; 3) Command on while state is on; and 4) Command off while state is off. Right now, I'm using only three of these for a Somfy 3-button handheld remote. |
|
Original comment by miscmail23 (Bitbucket: miscmail23, GitHub: miscmail23). so do you guys know when fauxMo would support 3rd gen of Alexa? |
|
Original comment by Stuckey (Bitbucket: Stuckeymax, GitHub: Stuckeymax). miscmail = Have you tried this one? https://gist.github.com/kakopappa/02299a8ceec0aaaad3ea3bd7f2af8066 You can view network packet activity in the IDE's serial port window. |
|
Original comment by Arpad (Bitbucket: ArpadB, GitHub: ArpadB). There is a separate issue about the 3rd gen echo dot. (#66) |
|
Original comment by Xose Pérez (Bitbucket: [Xose Pérez](https://bitbucket.org/Xose Pérez), ). Thanks, pushed the change to |
|
Original comment by Jack Murphy (Bitbucket: JacktheRipperOC, ). So, as a newbie, I just loaded the current demo code (has fauxmo.setPort(80)) and libraries from Adafruit, and my devices on my Feather HAZZAH was discovered the second time (first time my Dot was offline). I'm using the 1.8.8 IDE (1.8.19.0 from the Windows Store), Board was the "Adafruit Feather HAZZAH ESP 8266", FauxmoESP 3.1.0, 115,200 baud to serial port. Dot Gen3. What did I do right? I came here because my Dot was offline on my first attempt (keeps doing that: any suggestions?). |
|
Original comment by ed bourne (Bitbucket: edbourne, ). also, as a newbie, I just loaded the current demo code, my device is a NodeMCU Amica esp8266 (use the NodeMCU 1.0 (ESP 12E Module). First pass at home didn't work, after scanning this list, I set the lwIP version to v2 Higher Bandwidth (have no idea what this does!) and it worked, I could see "yellow lamp, pink lamp, etc" on my Alexa devices list. I have both Dot v2, and the latest echo plus (2nd Gen). I brought my setup to the office, and .... crickets. The two big differences being that I'm using a dot 3, and I have no idea what the router is setup like at the office. I can't discover the esp8266 on my work environment. Dot 3 works fine, esp8266 works fine (with other things, ie basic web server), just the discovery of the fauxmo devices doesn't work. |
|
Original comment by Stuckey (Bitbucket: Stuckeymax, GitHub: Stuckeymax). Ed – If any existing Philips Hue hubs at your office, power those down during discovery and then switch them back on after. Router might have strange ports blocked, but if Alexa works there, LAN-linked stuff usually will too. Don’t know how big your co is, might try speaking with IT unless they’re gestapo types. Stuckey |
|
Original comment by ed bourne (Bitbucket: edbourne, ). Oops said V2, meant V1.4 Higher bandwidth. The router use at my office seems to be the issue. Any idea what ports are used by fauxmo, or what I might look for on the router that is blocking my Alexa from finding the added devices? |
|
Original comment by ed bourne (Bitbucket: edbourne, ). Found this: https://forums.developer.amazon.com/articles/46667/what-tcpudp-ports-does-echo-use.html |
|
Original comment by Stuckey (Bitbucket: Stuckeymax, GitHub: Stuckeymax). Is dot in comm with amazon servers, taking voice commands, answering questions? SMc |
|
Original comment by Jason Thrasher (Bitbucket: [Jason Thrasher](https://bitbucket.org/Jason Thrasher), ). xoseperez: Thanks for all of your work on this project! This thread was helpful in getting fauxmoesp working for my D1mini. I’ll report it’s working when writing the firmware using:
I did have to unplug my Philips Hue hub. No ports were treated specially on my firewall/router (which is a pfSense). I asked Alexa to discover devices, and found I couldn’t use the Alexa app on my phone to connect my ESP8266. After it was connected and working, I found I could update to
And it continued to work! I didn’t try to initiate the connection routine with esp8266 2.5.2, though it seems the bugs have been worked out, so it’s worth trying. -Jason |
|
Original comment by arul chris (Bitbucket: [Arul Chirs](https://bitbucket.org/Arul Chirs), ). (ESP8266 D1 mini) was able to add only 3 devices. on adding 4 or + devices as in the example none of the devices was discovered. as quote by @andy Droid changed lwIP variant "v2 lower memory" to "v2 higher bandwidth. and configured 8 devices now Alexa was able to discovered all the eight devices. 😀 |
|
Original comment by Carlos Nascimento (Bitbucket: [Carlos Nascimento](https://bitbucket.org/Carlos Nascimento), ). 650/5000 My project is running with an ESP8266-01 and Arduino UNO. Ja I edited the bibliote line 83 to: if (request.indexOf ("ssdp: discover")> 0 || request.indexOf ("upnp: rootdevice")> 0 || request.indexOf ("device: basic: 1")> 0) { Arduino IDE 1.8.10 12 Relay Design (12 Devices) Does anyone have any other suggestions? |
|
Original comment by Carlos Nascimento (Bitbucket: [Carlos Nascimento](https://bitbucket.org/Carlos Nascimento), ). My project is running with an ESP8266-01 and Arduino UNO. I edited the Liberie line 83 to: if (request.indexOf ("ssdp: discover")> 0 || request.indexOf ("upnp: rootdevice")> 0 || request.indexOf ("device: basic: 1")> 0) { Arduino IDE 1.8.10 12 Relay Design (12 Devices) Does anyone have any other suggestions? |
|
Original comment by Stuckey (Bitbucket: Stuckeymax, GitHub: Stuckeymax). Carlos – Have you tried shutting down the 4 recognized devices plus your Philips Hue hub if you have one, then trying to recognize 1 new device at a time, then switching the others back on? I have 2 recognized ESP8266 devices working with Alexa, but had to shut down Philips Hue hub to get either of them to connect. In my system, I have one Echo dot and one fairly old Echo cylinder. Best wishes and Merry Christmas, hope you get it figured out, Stuckey McIntosh Atlanta |
|
Original comment by Vlad Voinea (Bitbucket: [Vlad Voinea](https://bitbucket.org/Vlad Voinea), ). HI guys, Could you please help me with 2 issues ? Using the latest fauxmoESP/master echo dot 3 correctly discovers an emulated Philips Hue which can be turned ON and OFF using voice commands. But it cannot be controlled from the Alexa app like a normal Smart Home light (toggle it like a button from the app). Second issue, I tried to using the fauxmoESP/master-2.4.X (as this one uses Wemo emulation) but I cannot get it working. I updated the discovery response and now my emulated Wemo is found by Alexa but I cannot get it to correctly process SetBinaryState commands. I would like to mention that I managed to get the original Fauxmo library to correctly emulate Wemo using a Raspberry Pi. Any help would be appreciated. Thank you |
|
Original comment by Carlos Nascimento (Bitbucket: [Carlos Nascimento](https://bitbucket.org/Carlos Nascimento), ). Stuckey - I don't have the Philips Hue hub. I am just running ESP8266 with the fauxmo library. I would like to control 12 devices with a single ESP8266, but it is difficult. |
|
Original comment by Zuriel Hdez (Bitbucket: [Zuriel Hdez](https://bitbucket.org/Zuriel Hdez), ). I have a similar problem, i can upload a code with two devices and work fine. But when i edit the same code and upload alexa dont recognize more so i can brake the rule of two devices. Carlos Nascimiento, dont change some line in the librarie o similar? i hope today review the code more deep, try to find something what can help Nice day for everyone Regards from Mexico |
|
Original comment by Stuckey (Bitbucket: Stuckeymax, GitHub: Stuckeymax). Carlos - Could be a 2-bit variable in fauxmo that needs to be a 4-bit variable for your 12-device setup. I’ve never looked into the source code for that, but xoseperez might know where to look, or what gives rise to the 4-device limitation. SMc |
|
Original comment by Stuckey (Bitbucket: Stuckeymax, GitHub: Stuckeymax). Carlos – Hope you have your no-more-than-4 issue straightened out. I added 3 more ESP8266 devices to my system yesterday so that in total I have 5, each with a different Alexa-recognized name. I did not encounter any problems adding the 5th device, didn’t have to shut down any other discovered/controllable devices. Best regards, Stuckey Arduino IDE 1.8.9 |
|
Original comment by Chris McKeever (Bitbucket: [Chris McKeever](https://bitbucket.org/Chris McKeever), ). Is this still working? A previously connected device/code no longer can be discovered. |
|
Original comment by Roger Hoggarth (Bitbucket: [Roger Hoggarth](https://bitbucket.org/Roger Hoggarth), ). @{5ddd491a7095a40d12530342} did you get it working Chris. My previously working Wemo-emulation and Phillips-hue emulation projects no longer can be discovered. Tried resetting my Echo devices. No luck so far. |
|
Original comment by Chris McKeever (Bitbucket: [Chris McKeever](https://bitbucket.org/Chris McKeever), ). yes and no. After I removed the devices from Alexa, they started to work again. I did work on the code some that my project was using, but I do not think I did anything that would have resolved the issue. Im pretty sure it was after I removed the device and re-added that it all got back in line. BUT I can confirm that as of a few weeks ago, this library was still working with Alexa. I do need to try it again, as I need to connect a device. I will report back when I get a chance |
|
Original comment by Doelectric Domotica Profesional (Bitbucket: [Doelectric Domotica Profesional](https://bitbucket.org/Doelectric Domotica Profesional), ). I have tried the example on an esp 01 with an alexa ecoflex and everything works fine. switching on and off and regulation. |
|
Closing stale issue. |
Original report by GeneBean (Bitbucket: genebean, GitHub: genebean).
If I use v2.3.0 of this repo with Arduino Core 2.3.0 for the ESP8266 my nodeMCU 1.0 (esp-12E) module is discovered by the Alexa app. If I update to the 3.0 version of this repo my device is never found nor is anything other than the wifi connection and free heap shown in the serial console.
In both cases I was using the provided example sketch and only changed my wifi creds and the plug name.
I did try adding
#define DEBUG_FAUXMO_VERBOSE trueto the 3.0 version of the sketch but it didn't change a thing.The text was updated successfully, but these errors were encountered: