DOT doesn't recognize the ESP device

[vintlabs]

DOT doesn't recognize the ESP device

[pvint]

Original comment by Ben Steiner (Bitbucket: bgsteiner, GitHub: bgsteiner).

---

I am having the same issue as stated above

[pvint]

Original comment by Xose Pérez (Bitbucket: [Xose Pérez](https://bitbucket.org/Xose Pérez), ).

---

Is it an Echo Plus or a v1? There is a ticket for v2 devices: #39

[pvint]

Original comment by Ben Steiner (Bitbucket: bgsteiner, GitHub: bgsteiner).

---

V2 echo dot

[pvint]

Original comment by Bryant Bunderson (Bitbucket: bryantbunderson, GitHub: bryantbunderson).

---

Same, looks like mine is a 2nd Generation Echo Dot. Had to find that on the box. The Alexa app says it's running software version 597465220. I'll check out issue #39.

[pvint]

Original comment by Nils (Bitbucket: nilz90, GitHub: nilz90).

---

Had the same problem and tried some hours. Then I found out some intresting things.

ESP8266: Use Arduino Core 2.3 for your ESP (in the boardmanager) (found it in the description)

On ESP32 the newest Master would not work for me, I just found one device with it. But I got lucky with the fork of Frank Hellmann (sandman72 on github)

now everything is working as aspected with my V2 Dot

let me know if this is working for you

[pvint]

Original comment by Bryant Bunderson (Bitbucket: bryantbunderson, GitHub: bryantbunderson).

---

Nils! You're a genius! Switching to version 2.3 in the esp8266 part of the
Boards Manager got everything working with my Echo Dot V2! What made you
think to use version 2.3 instead of the latest which is 2.4? Is there a
know problem with 2.4? Anyway, awesome find! Thank you very much!

[pvint]

Original comment by Nils (Bitbucket: nilz90, GitHub: nilz90).

---

hehe that would be nice to be a genius. But no, I just read it in the README.md , what a shame.

I think here is also a big misunderstanding on "Gen2" devices. I have a dot v2 which must also be a "gen1" device because on my esp32 I use a quiet old version of fauxmo as I mentioned before.
So real "gen2" devices must be the new Echo Plus and Echo 2nd Gen (not dot).
Lets call "gen2" devices: late 2016 devices ?!

My challenge now is to get my esp32 working with a Echo late 2016 because:

esp32 with Fauxmo 2.3 (sandman72 fork ) and echo dot v2 -> working
esp32 with Fauxmo 2.4 and echo dot v2 -> working but finds only one device

at this moment I could not get my hands on a late 2016 device but I don't think esp32 and late 2016 device are not working at this moment. But I will test it in about 2 weeks and try to fix it and make a pull.

[pvint]

Original comment by Ben Steiner (Bitbucket: bgsteiner, GitHub: bgsteiner).

---

Bryant are you using the example I still seem to be unable to discover the device I have tried on two different esp modules.

[pvint]

Original comment by Nils (Bitbucket: nilz90, GitHub: nilz90).

---

@bgsteiner do you use an eps8266 or an esp32?

I know you can get it working I tried both with my dot v2.

Pls try V2.3 of Fauxmo and turn on the serial monitor when searching with your dot. Is there any output like in the first post ?

[pvint]

Original comment by Bryant Bunderson (Bitbucket: bryantbunderson, GitHub: bryantbunderson).

---

Ben, yes, I am using the fauxmoESP_Basic example. The example compiled and
loaded and the Echo Dot was able to find it. However, I then changed the
name of the fauxmo device 'addDevice("My Yellow Button")' to
'addDevice("switch one")' and the Echo Dot could no longer find it BUT it
was there anyway. I can say "Alexa switch one off" and the serial monitor
shows the command coming through. When I connect an LED (I chose my own
pin) then the LED would turn off and on. I did have to remove the negate
from this line. "digitalWrite(LED, !state)" to "digitalWrite(LED, state)".
I assume that the example program was meant to pull a switch low rather
than drive it high. Long story short, it's working. Before I figured out
how to use the board manager properly, I deleted all the ESP hardware in
the Arduino settings and it downloaded everything down fresh. I then add
the esp section in the board manager and picked version 2.3. I don't think
that's necessary though.

[pvint]

Original comment by Ben Steiner (Bitbucket: bgsteiner, GitHub: bgsteiner).

---

Looks like this won't work with me neither version of fauxmo or the board will work with my echo dot. I guess I'll have to try another route.
All I get is

#!arduino

HTTP/1.1 200 OK
CACHE-CONTROL: max-age=86400
DATE: Mon, 22 Jun 2015 17:24:01 GMT
EXT:
LOCATION: http://192.168.2.124:52000/setup.xml
OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01
01-NLS: 4445564F154600
SERVER: Unspecified, UPnP/1.0, Unspecified
X-User-Agent: redsonic
ST: urn:Belkin:service:basicevent:1
USN: uuid:Socket-1_0-4445564F154600::urn:Belkin:service:basicevent:1

[pvint]

Original comment by Nils (Bitbucket: nilz90, GitHub: nilz90).

---

that output shows you that your esp is responding the broadcast message from your dot. So I don't think it's your routers fault assumed they are in the same subnet.

#!arduino

#include <Arduino.h>
#ifdef ESP32
    #include <WiFi.h>
#else
    #include <ESP8266WiFi.h>
#endif
#include "fauxmoESP.h"
#include "credentials.sample.h"
// #include <RCSwitch.h>

#define SERIAL_BAUDRATE                 115200
#define LED                             2

//RCSwitch mySwitch = RCSwitch();

fauxmoESP fauxmo;

// -----------------------------------------------------------------------------
// Wifi
// -----------------------------------------------------------------------------

void wifiSetup() {

    // Set WIFI module to STA mode
    WiFi.mode(WIFI_STA);

    // Connect
    Serial.printf("[WIFI] Connecting to %s ", WIFI_SSID);
    WiFi.begin(WIFI_SSID, WIFI_PASS);

    // Wait
    while (WiFi.status() != WL_CONNECTED) {
        Serial.print(".");
        delay(100);
    }
    Serial.println();

    // Connected!
    Serial.printf("[WIFI] STATION Mode, SSID: %s, IP address: %s\n", WiFi.SSID().c_str(), WiFi.localIP().toString().c_str());

}

void setup() {

    // Init serial port and clean garbage
    Serial.begin(SERIAL_BAUDRATE);
    Serial.println();
    Serial.println();

    // Wifi
    wifiSetup();

    // LED
    pinMode(LED, OUTPUT);
    digitalWrite(LED, HIGH);

    //Switch

   // mySwitch.enableTransmit(4); //DigitalPIN 2 Transmitter

    // You can enable or disable the library at any moment
    // Disabling it will prevent the devices from being discovered and switched
    fauxmo.enable(true);

    // Add virtual devices
    fauxmo.addDevice("Lampe");
	  fauxmo.addDevice("TV");
	  fauxmo.addDevice("Fenster");

    // fauxmoESP 2.0.0 has changed the callback signature to add the device_id,
    // this way it's easier to match devices to action without having to compare strings.
    fauxmo.onSetState([](unsigned char device_id, const char * device_name, bool state) {
        Serial.printf("[MAIN] Device #%d (%s) state: %s\n", device_id, device_name, state ? "ON" : "OFF");
        
        if( (strcmp(device_name, "Lampe") == 0)){
          if(state){
           // mySwitch.switchOn("xxx", "xxx");
            } else{
            //mySwitch.switchOff("xxx", "xxx");
              }
          }//end of if


          if( (strcmp(device_name, "TV") == 0)){
          if(state){
          //  mySwitch.switchOn("xx", "xxx");
            } else{
         //   mySwitch.switchOff("xxx", "xxx");
              }
          }//end of if

          if( (strcmp(device_name, "Fenster") == 0)){
          if(state){
          //  mySwitch.sendTriState("xxx");
            } else{
        //    mySwitch.sendTriState("xxx");
              }
          }//end of if
        
        
        
    });

    // Callback to retrieve current state (for GetBinaryState queries)
    fauxmo.onGetState([](unsigned char device_id, const char * device_name) {
        return !digitalRead(LED);
    });

}

void loop() {

    // Since fauxmoESP 2.0 the library uses the "compatibility" mode by
    // default, this means that it uses WiFiUdp class instead of AsyncUDP.
    // The later requires the Arduino Core for ESP8266 staging version
    // whilst the former works fine with current stable 2.3.0 version.
    // But, since it's not "async" anymore we have to manually poll for UDP
    // packets
    fauxmo.handle();

    static unsigned long last = millis();
    if (millis() - last > 5000) {
        last = millis();
        Serial.printf("[MAIN] Free heap: %d bytes\n", ESP.getFreeHeap());
    }

}

here is my test code, just replace the mySwitch stuff with your stuff.

[pvint]

Original comment by Ben Steiner (Bitbucket: bgsteiner, GitHub: bgsteiner).

---

I tried this and was unable to get anything to work. I get the same output and alexa just can't find it. I tried loading fauxmo onto my raspberry pi automation server and my echo dot found it with no problems so I'll wait for some code revisions and maybe try again.

[pvint]

Original comment by Guru Inamdar (Bitbucket: ginamdar, GitHub: ginamdar).

---

@nilz90 thank you!! - your suggestion worked :) , I tried all 2.4.2 to 2.3.0 builds but nothing worked. And it was working while back w/o issues. Hard time to find the correct version and boards.

1. Alexa Dot v2 - build -601481020

2. Uninstalled ESP8266 board and installed 2.3.0 version as suggested above.
   

3. fauxmoesp 2.3.0 installed

and finally Alexa discovered the device.

fyi - i tried all fauxmo version with new esp board (i think 2.4.2) and i was seeing usual chatter between my nodemcu and alexa in serial monitor but it always ended up with NO device discovery.

[pvint]

Original comment by michael hines (Bitbucket: [michael hines](https://bitbucket.org/michael hines), ).

---

Wow, it worked right out of the box. Follow Nils advice.

[pvint]

Original comment by Dave Smart (Bitbucket: Wiredhome, GitHub: Wiredhome).

---

I took a wireshark log with 2.4.1, and in the response from the ESP to the SSDP query, the transaction never completed successfully. It always terminated in the middle of the XML response. I was using VisualMicro in Visual Studio 2017, and haven't found how to "downstep" to 2.3.0.

Switching to the Arduino IDE I repeated the failure mode, then did downstep to 2.3.0 and it works as expected. So, it seems reasonably clear that something in the 2.4.1 version is causing this.

Side Note: Many thanks for the fauxmoESP library! I hope to put it to full use very soon (where now I'm only at this early experimental stage).

[pvint]

Original comment by Xose Pérez (Bitbucket: [Xose Pérez](https://bitbucket.org/Xose Pérez), ).

---

Sorry for the late-late reply.
New version uses a completely different approach. Maybe you'd want to give it a go.

[pvint]

Original comment by Hichem Brh (Bitbucket: [Hichem Brh](https://bitbucket.org/Hichem Brh), ).

---

Hi There

My Echo Dot is detecting the ESP8266 after I’ve downgraded ESP8266 Librairy to 2.3.0 But t can’t control it.

When I say Alexa turn on device, it says “Device doesn’t support it“

Do you have any idea how to solve this issue ??

Thanks guys

[pvint]

Original comment by Chirag Ajmera (Bitbucket: nccchirag, GitHub: nccchirag).

---

Emulated hue has stopped working with Echo dot gen 2

Setup
tinyPICO with fauxmoESP_Basic sketch 3.1.0
Echo dot gen 2 with software version 649649821
Echo show -- not connected initially

Issue
No devices are being discovered when connecting just the echo dot (gen2)

Findings
Connecting echo show & then initiating the device discovery via echo dot seems to find all the emulated devices

Summary
Echo dot gen 2 does not independently discover devices, instead it requires a newer generation device in the network for emulated discovery to work!

[pvint]

Original comment by Chris McKeever (Bitbucket: [Chris McKeever](https://bitbucket.org/Chris McKeever), ).

---

Sorry for the cross-issue spam ..

This thread is old – but can anyone confirm that fauxmoESP does in fact still work? I have an device that does work, but it has been connected for over a year.

When I try to set up a new device using

• fauxmoESP 3.1.1
• esp8266 2.7.1

I can not get Alexa to see anything. I have tried rolling down to fauxmoESP 3.1.0 (as that was what I was running) - no luck. As well as changing esp8266 down several versions.

Read many threads of similar issues but always seems to be someone that can get it to work.

[pvint]

Original comment by Chirag Ajmera (Bitbucket: nccchirag, GitHub: nccchirag).

---

what echo device are you using?

also, you might want to try installing TASMOTA firmware and enable emulation from within that (it has two options – hue & belkin)

[pvint]

Original comment by Chris McKeever (Bitbucket: [Chris McKeever](https://bitbucket.org/Chris McKeever), ).

---

gen 3 devices, all 3 of them

[pvint]

Original comment by Chirag Ajmera (Bitbucket: nccchirag, GitHub: nccchirag).

---

some things to try

1. verify networking – in fact connect just the router and echo dot (1nos only)

   1. UDP & UPNP should not be blocked – you may be knowing this, but documenting for info
   2. try a new router if possible

2. Use a separate Amazon Alexa Account

   1. try changing language to EN → IT → EN with discovery each time

3. Hard reset 1nos echo dot & try configuring again

4. Try installing TASMOTA firmware and enable emulation from within that (it has two options – hue & belkin)

5. Try emulation using https://github.com/Aircoookie/Espalexa

Good luck!

[pvint]

Original comment by Chris McKeever (Bitbucket: [Chris McKeever](https://bitbucket.org/Chris McKeever), ).

---

@{557058:9c609a25-2f04-4da5-826f-555e2b07ee19} Thanks for the reply. I had swapped to EspAlexa and that does find the devices.

I did also find something else of interest with fauxmo. Alexa does find the device, its just not indicated or seen as new. Its almost like it finds a new copy, but it does label it with the new name (both appear). But what is frustrating, selecting it in the Alexa UI to move to a new group moves the original.

Just to re-iterate, this is for a new physical ESP8266 connected to the network, not another faux device on a single ESP8266. So I wonder if thats some known limitation of this?

I need to play around with this config again now that I have some more information and I know the device itself does get recognized

[pvint]

Original comment by Chris McKeever (Bitbucket: [Chris McKeever](https://bitbucket.org/Chris McKeever), ).

---

maybe I was in the code too much. Re-working it, new chip – all seems to work as intended. That was a lot of cycles lost … Thanks for the help

[pvint]

Closing stale issue.