Alexa SmartHome skill - not finding #22

sciencegirl100 · 2017-11-02T14:20:43Z

Installed on my NodeMCU, went through Alexa app to add... nothing.
So, turns out you need the smart home skill for the devices you want to add.
The WeMo skill requires you to enter your wireless SSID and the WeMo device's MAC address.
This breaks the compatibility with these wemo emulator projects unfortunately.

So, has anyone gotten past this? Is there a generic smarthome skill I'm unaware of?

P.S. I made sure all devices were on the same network and I even reset my Echo Dot. Nothing :/

dougstrickland · 2017-11-03T20:24:51Z

Have you tried coding your ssid in your script?
like:

const char* ssid = "My_Network";
const char* password = "XXXXXXXXXXXXXXXX";

sciencegirl100 · 2017-11-03T20:32:07Z

I set the SSID and WPA2 password, I was able to ping it from my PC as well as my phone from the same network that the Echo is on

Braandn · 2017-11-04T19:53:09Z

Same problem

MacSass · 2017-11-05T17:58:31Z

Same problem here - but only after my Alexa updated to the latest firmware.
Before I could discover the ESP emulated devices with no problem - you could monitor the answer to the Alexa search request in the serial console ...
Now, when I do a search, the ESP does not seem to "see" any broadcast request and does not respond - thus Alexa does not show any devices.
I will try with the WeMo skill, but if that required a MAC address and it only works this way it would mean we would need "false" MAC adresses???
As said - until lately no skill was needed and Alexa found the emulated Wemos devices on the ESP8266 with no problem ...

MacSass · 2017-11-05T18:15:26Z

Update:
Using my "old" Amazon Echo (1st generation) the devices are discovered with no skill required (no wemos skill activated). Devices can be controlled. The Echo FW version is 591448720.
The second generation Echo does not seem to be able to control or discover the devices with the latest Fw that was released today.
Looks like Amazon is really messing up big time with the second generation Echo (sound is way worse than with the old one - now this).
Let´s see if Amazon fixes that or if the kill my old Echo for this by updating it´s FW as well ...

sciencegirl100 · 2017-11-08T15:07:09Z

maybe someone just needs to make a smart home skill for the ESP8266. I might give it a shot, but no guarantees.

arnowillig · 2017-11-24T14:20:45Z

@MacSass Same here, 2nd gen. Echo does not finde the devices, Echo FW version is 592452720.
However, the echo DOES send HTTP requests (GET to /setup.xml and /eventservice.xml and POST to /upnp/control/basicevent1).
POST body is this:
<?xml version="1.0" encoding="utf-8"?><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><u:GetBinaryState xmlns:u="urn:Belkin:service:basicevent:1"><BinaryState>1</BinaryState></u:GetBinaryState></s:Body></s:Envelope>

I think the echo tries to read the current state of the emulated WeMo switch, but then fails to enumerate the device. :-(

Anyone a solution yet?
akw

kakopappa · 2017-11-25T02:41:53Z

hello @MacSass @arnowillig @sciencedude100 @Braandn

Thank you for your input guys

I have added GetBinaryState support to single switch version. Can you guys test it and let me know. I have an Eco at home. It does not send GetBinaryState

https://gist.github.com/kakopappa/02299a8ceec0aaaad3ea3bd7f2af8066

ma7gdp · 2017-11-26T13:56:18Z

I just tried the code you have on a "WemosD1 mini" and the echo dot 2nd gen is still reports "No new devices found". The serial on the WemosD1 is outputting the usual though:

Sending response to 192.168.1.74
Port : 50000
Response sent !
192.168.1.74, port 50000
192.168.1.74, port 50000
########## Responding to setup.xml ... ########

Sending :urn:Belkin:device:controllee:1boxBelkin International Inc.Socket3.1415Belkin Plugin Socket 1.0
uuid:Socket-1_0-38323636-4558-4dda-9188-cda0e61957d9221517K01017690urn:Belkin:service:basicevent:1urn:Belkin:serviceId:basicevent1/upnp/control/basicevent1/upnp/event/basicevent1/eventservice.xml

########## Responding to setup.xml ... ########

Sending :urn:Belkin:device:controllee:1boxBelkin International Inc.Socket3.1415Belkin Plugin Socket 1.0
uuid:Socket-1_0-38323636-4558-4dda-9188-cda0e61957d9221517K01017690urn:Belkin:service:basicevent:1urn:Belkin:serviceId:basicevent1/upnp/control/basicevent1/upnp/event/basicevent1/eventservice.xml

RootCNC · 2017-12-01T15:44:26Z

Same, doesn't work with Sonos One with Alexa built in- unable to discover devices =[ great project and keep up the good work! I will be following it!

kakopappa · 2017-12-02T04:52:57Z

@RootCNC can you try https://gist.github.com/kakopappa/02299a8ceec0aaaad3ea3bd7f2af8066

tommyfranke · 2017-12-03T19:03:29Z

@kakopappa, thank's for the great work.
The above code works wonderful on my new Amazon Dot V2 with actual Firmware 595459620.
My Nodemcu was found at once, you don't need the Wemo-Skill!!!
Switching works fine.

Btw: It seems to me that the "eventservice.xml" never get called by Echo Dot, is it not needed?

ZoMiGo · 2017-12-06T12:02:09Z

hi i have Amazon Dot V2 with actual Firmware 595459620 my problem is alexa dont found any devices.
i use https://gist.github.com/kakopappa/02299a8ceec0aaaad3ea3bd7f2af8066

arnowillig · 2017-12-06T13:03:25Z

hi, same here. I got an Amazon Echo gen.2. Even with the original WeMo plug the Amazon Echo does not find the hardware. However, I can see the device is queried. Even an "GetDeviceState" upnp POST message is sent by the Echo hardware. Strange, hm? I suppose this is a bug in the firmware. My Amazon Echo gen.1 works beautifully with the original WeMo plug as well with a simulated device. Ciao, Arno 2017-12-06 13:02 GMT+01:00 Goran <[email protected]>:

…

hi i have Amazon Dot V2 with actual Firmware 595459620 my problem is alexa dont found any devices. i use https://gist.github.com/kakopappa/02299a8ceec0aaaad3ea3bd7f2af8066 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#22 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAXll3MuXiEUCkXcXZcSZ9D45Odig2j-ks5s9oJDgaJpZM4QPwo4> .

-- Arno Willig <[email protected]> ウィリグ・アーノ

RootCNC · 2017-12-08T11:26:32Z

@kakopappa I've just ran the software now and unfortunately it doesn't seem to work. =[

I have gone into the Alexa app to see the version number and its not listed where amazon says it should, I was hoping this might help debug the problem.

I can see in the serial terminal Alexa is sending something to the ESP8266 but still doesnt discover any devices. =[

The Sonos one with Alexa does with the Wemo insight version perfectly so not too sure.

sciencegirl100 · 2017-12-17T03:50:33Z

This still isn't found on my Alexa V2 (Firmware: 597464620)

MacSass · 2017-12-17T23:26:39Z

Thanks for your work on this Kakopappa - I will try this latest version during the week, although I do not have too much hope looking at past responses.
I could provide some network trace if that helps if you let me know what you would need ...

MacSass · 2017-12-18T20:52:32Z

Hello, I have tried with the new script found here:
[https://gist.github.com/kakopappa/02299a8ceec0aaaad3ea3bd7f2af8066]
and can confirm that no devices are found with that script with the new generation Alexa devices (tried Echo v2 and Echo Plus).
Both - the old and the new script - do not show any reaction at all when I do a "discover" in the Alexa app if there is only a new generation Alexa doing the search.
Interesting fact:
As soon as I have one "old" Alexa device (Echo Dot in my case) in the same network then both scripts do find devices with no problem.
It looks like the new devices send out a different broadcast string, as I never see a response from the ESP with the new devices. I would have expected that this:

if(request.indexOf('M-SEARCH') > 0) {
        if(request.indexOf("urn:Belkin:device:**") > 0) {
            Serial.println("Responding to search request ...");
            respondToSearch();
        }
    }

get´s triggered - but it does not with the new device (ip ....28 in attached logs), only if an old device is in the network as well the ESP responds to the broadcast of the old device (ip ...24 in attached logs)

I have attached the output of the script for V2 device only and for combination of V2+V1 Alexa device.

I think the broadcast of the generations is different and the listening ESP never get´s triggered by the new device. Thus it seems to be needed to modify the trigger criteria?
If I find the time I will see if I can do a network trace to check what the difference in query broadcast of the two generations is, that should clarify things.

Regards - MacSass

New script - Echo Plus and Echo Dot.txt
New script - Echo Plus only.txt

MacSass · 2017-12-18T22:20:58Z

Hi,
I did a network trace and think I´m getting a little bit clearer on the issue:
While old devices send a SSDP broadcast containing "urn:Belkin:device:**" (which the ESP is looking for) the new devices send a SSDP broadcast with "upnp:rootdevice". Thus the ESP does never respond to the broadcast of the new Alexa devices.

When I do change the trigger that ESP is looking for to:

if(request.indexOf('M-SEARCH') > 0) {
if(request.indexOf("upnp:rootdevice") > 0) {
Serial.println("Responding to search request ...");
respondToSearch();
}
}

and also change the response string, then I can get the new device to discover the ESP!

I did an initial test and the script then seems to work fine for me. I have attached my modified script below and would appreciate any feedback, as I might not really fully understand what I´m doing :-)

irdevkit-macsass.txt

Regards - MacSass

sciencegirl100 · 2017-12-19T00:10:16Z

It Works!
Arduino Log
However, the repository's code doesn't work. Not sure why.
I ended up having to reset my Echo Dot V2 ( hold Mute & Vol - ).
Make sure the echo and esp8266 are on the same wireless. I've had issues with them on the same network, but on different APs.

EDIT:
Odd, I added in printing the request to terminal in the master branch and now it works.

Issue fixed kakopappa/arduino-esp8266-alexa-multiple-wemo-switch#22 (comment)

ma7gdp · 2017-12-20T21:21:42Z

Is anyone else having an issue with getting this working? The serial output on my WemosD1mini shows activity when EchoDotV2 is discovering, but only ever shows "########## Responding to setup.xml ... ########" never the piece which @sciencedude100 shows in their Arduino log: "########## Responding to /upnp/control/basicevent1 ... ##########". It feels like it is almost there.

MacSass · 2017-12-20T22:05:35Z

Hello ma7gdp,
yes - I´m still having issues. As long as I only have my Echo Plus (new gen) in the network, devices still do NOT get discovered. I see requests for UDP Belkin in the log and responses being sent, but devices do not show up.
Also I do NOT see responses like "######### Responding to setup.xml ... ########".

As much as I can say this is caused by the fact that the response that get´s send currently is having:
"USN: uuid:" + persistent_uuid + "::urn:Belkin:device:**\r\n"
while the new gen devices expect a response of:
"USN: uuid:" + persistent_uuid + "::upnp:rootdevice\r\n"

I will verify my assumption in a minute, but I´m pretty confident because as soon as I add a 1st gen device (echo dot) to the network the discovery works fine (because 1st gen device is happy with the response).

Doing some more testing right now ...

MacSass · 2017-12-20T22:34:21Z

Hi again,
ok - I can confirm that this seems to be the root cause.
Changing
"USN: uuid:" + persistent_uuid + "::urn:Belkin:device:**\r\n" in switch.cpp to
"USN: uuid:" + persistent_uuid + "::upnp:rootdevice\r\n"
does allow to discover devices with 2nd generation Echos. Also it still works if only a 1st gen Echo is in the network - so this seems to be a solution as much as I can see.

After changing a devices state I do see continious responses to

Responding to /upnp/control/basicevent1 ...

about every 1 second. Not sure if those requests really happen or if this is another issue that should be looked at in a different thread / issue.

ma7gdp · 2017-12-21T10:03:22Z

Hey thanks @MacSass for taking a look. I only have Gen2 echo dot so cannot test the various combinations of scenarios with Gen1 etc. I can say though that even with the change to rootdevice in switch.cpp there are still no devices found by Alexa on the Gen2 dot. The serial output I get is as below (.97 is the Gen2 and the WemosD1mini is on .98). Still just "Responding to setup.xml" nothing else. Looks like the Gen2 is expecting a different response to the setup.xml request (assuming that the setup.xml request is Gen2 asking WemosD1mini to identify itself so Gen2 can list it via Alexa app).

btw... Thanks for taking the time. If only I had a Gen1 ... I probably would not have even noticed things weren't quite as they should be.

Udp multicast server started at 239.255.255.250:1900
WebServer started on port: 80
WebServer started on port: 81
Adding switches upnp broadcast responder
Adding switch : office lights index : 0
Adding switch : kitchen lights index : 1
Got UDP Belkin Request..

Sending response to 192.168.1.97
Port : 50000
Response sent !
########## Responding to setup.xml ... ########

Sending :urn:Belkin:device:controllee:1office lightsBelkin International Inc.Socket3.1415Belkin Plugin Socket 1.0
uuid:Socket-1_0-38323636-4558-4dda-9188-cda0e61957d9-80221517K01017690urn:Belkin:service:basicevent:1urn:Belkin:serviceId:basicevent1/upnp/control/basicevent1/upnp/event/basicevent1/eventservice.xml

MacSass · 2017-12-21T12:23:53Z

Hi ma7gdp,
I can get devices discovered with both, my Echo Dot (current version - whatever that is) and my "new" Echo Plus, depending on what I put into the switch.cpp. But I still have some issues with devices switching if only one of them is on the network.
Currently I´m not clear if devices are "linked" to a certain Echo if they are only linked to the account.
So I need to do more testing or additional network traces to get clarity on this.

So there definitely seems still something to be going on in what the devices expect as response for discovery and switching.
Fortunately the Christmas break is coming up and I should have some more time to look into this into more detail and do more testing.
I hope to have some more information / data in the upcoming days ... hopefully even before Christmas ...

ma7gdp · 2017-12-21T13:54:03Z

Great. No more work this year for me so happy to help out with any testing or traces at my end. Tricky part is understanding whats in the echo code without the original/working devices to "sniff". Cheers again.

ma7gdp · 2017-12-22T22:36:46Z

Picked up on your comment regarding the accounts. After lots of various testing I found issues with having a "household" Amazon account. Saying "Alexa switch accounts" and then "Alexa discover devices" did the trick. Not only did the Echo find the devices but it also allowed me to trigger them and the serial output of the WemosD1mini showed the catch of the event. Bottom line .... I can now trigger a relay by saying "Alexa switch office lights on" etc.. Thanks all. To confirm I have 2x latest EchoDots only on my network.

kakopappa · 2018-01-28T12:20:00Z

@AvisIoT @TetsudouSenpai

I have updated the website to show the device id now.

MacSass · 2018-01-28T12:59:11Z

Hi @AvisIoT ,
I already spoke to Kakopappa about adding device ID to sinric.com. I guess he will do that soon, also some more enhancements are planned.
Until then you can also use the attached code to:

Control more than one device
Get deviceID for devices
If the attached code (rename to .ino) receives a request for an unknown device it will put out the deviceID in the serial console.

What you need to do:
Add your api an wifi credentials to the attached code. Create device on sinric and have it discovered by alexa. Issue command through alexa and you will see the deviceID in the serial console.

You can then replace the existing dummy device IDs in the code with your correct ones ...

As said Kokopappa will make more enhancements soon to make it easier - I guess.

Regards - MacSass

switch_multi_sinric.txt

MacSass · 2018-01-28T13:00:14Z

Uhhhh - He has been faster than me :-)

still my code might be useful for some that want to control multiple devices ...

AvisIoT · 2018-01-28T15:03:25Z

Thank you @kakopappa and @MacSass . I will test/experiment more next weekend. Have ordered few relay modules, once they arrive will put this to real life use... the multi-device code will be really useful in that case. @kakopappa also looking forward to update on issue #10 (kakopappa/sinric#10)

RanTalbott · 2018-02-04T10:53:05Z

To add some useful, but also some confusing, information.

I had some trouble getting Alexa to discover one of my experiments until I made the change that MacSass suggested. Thank you for that.

But...

It also discovered one that didn't have the change.
The Dot told me that it hadn't discovered anything. The Android app revealed that it had.
The new experiment has 7 switches. Only the last 3 were discovered. I tweaked the debug code a little bit, and confirmed that initial responses for all 7 were sent. But the Dot is only asking for setup.xml for those last three. I'll post more about this after I do some more investigating.

charles · 2018-02-05T13:34:15Z

My echo dot stop find my devices after updated my apple time capsule from version 7.7.8 to 7.7.9. After that I try every possible solution here with no success. My solution was a downgrade to 7.7.8.

I hope that helps someone.

LiamFatz · 2018-03-03T15:44:57Z

@kakopappa
You're a legend. This resolved the issue for me.
Location - Ireland
Devices - Echo Gen 2 & nodeMCU
Your website is very clean & user-friendly. Simple to add multiple devices.
Thanks

tollermine · 2018-03-22T20:36:19Z

My Echo Dots where not able to finde anything... this fixed it for me:

if(request.indexOf('M-SEARCH') >= 0) { //if(request.indexOf("urn:Belkin:device:**") > 0) { if((request.indexOf("upnp:rootdevice") >= 0) || (request.indexOf("urn:Belkin:device:**") >= 0) || (request.indexOf("_urn:Belkin:device:_**") >= 0)) { Serial.println("Responding to search request ..."); respondToSearch(); } }

hinkey247 · 2018-04-07T19:49:27Z

Hi / Thank you kakopappa finally got this system working - ok 2 relays can be detected and used with Alexa 2nd Gen and NodeMCU, but how to add more switches? I have added one but cannot be discovered. Many Thanks - Hinkey :)

hinkey247 · 2018-04-07T20:16:30Z

Sorry guys just realised i hadn't given new port :) Works 100%

santosh09142 · 2018-05-06T06:03:36Z

Hi, I am new for IOT techno. I am using NodeMcu 1.0 ESP8266 12E. with Alexa plus FW:608490620. I tried kakopappa latest code and in serial monitor some transaction is happing about setup.xml. but still alexa is not discovering.

Please let me

kakopappa · 2018-05-06T06:09:32Z

Try sinric.com

…

On Sun, May 6, 2018 at 1:03 PM santosh09142 ***@***.***> wrote: Hi, I am new for IOT techno. I am using NodeMcu 1.0 ESP8266 12E. with Alexa plus FW:608490620. I tried kakopappa latest code and in serial monitor some transaction is happing about setup.xml. but still alexa is not discovering. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#22 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHIM5jTKH4zl6WW3REkZiSCufiLfdUCDks5tvpI5gaJpZM4QPwo4> .

santosh09142 · 2018-05-06T07:02:25Z

Thanks kakopappa, for fast reply, I did created switch object on sinric app and tried to search from Alexa app, App. found that object, but when i trigger switch on/off nothing happening on relay as will as on serial monitor.

i have added to replaypin in your script.

hinkey247 · 2018-05-06T07:08:45Z

Could it be not assigning new port for relay switch device?

kakopappa · 2018-05-06T07:09:59Z

when you ask Alexa to turn on or off you should see that request in serial monitor Do you see it? You have to turn on off trigger

…

On Sun, May 6, 2018 at 2:02 PM santosh09142 ***@***.***> wrote: Thanks kakopappa, for fast reply, I did created switch object on sinric app and tried to search from Alexa app, App. found that object, but when i trigger switch on/off nothing happening on relay as will as on serial monitor. i have added to replaypin in your script. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#22 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHIM5mi-nPfzAzHr0j1QdKgRkLtrqCEYks5tvqACgaJpZM4QPwo4> .

santosh09142 · 2018-05-06T07:12:19Z

no i didnt see any activity trigger on/off activity on serial monitor.

santosh09142 · 2018-05-06T08:36:25Z

Hi hinkey247, I did not understand your question. But if it is regards to assign GPIO port. Then yes I have assigned 14 And 4 in this case and same has been as relaypin1 and relaypin2. Regards Santosh Patil

…

On Sun, 6 May 2018, 12:38 hinkey247, ***@***.***> wrote: Could it be not assigning new port for relay switch device? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#22 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Aj_2z8_CTUKyo7WVmdspDSpNnvmoxQVtks5tvqF-gaJpZM4QPwo4> .

hinkey247 · 2018-05-06T10:01:12Z

The port number in your source code for the router device number. Ie port port 80.

santosh09142 · 2018-05-06T10:19:53Z

Hi, Yes it configured. Port 80 is for office and 81 For kitchen. Regards Santosh Patil

…

On Sun, 6 May 2018, 15:31 hinkey247, ***@***.***> wrote: The port number in your source code for the router device number. Ie port port 80. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#22 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Aj_2z7z_CBaQLscSVq03tNhh7R_h6qE4ks5tvsnqgaJpZM4QPwo4> .

santosh09142 · 2018-05-07T02:14:17Z

Hi,
I am attaching trigger script which was working after some modification, stated above.

one more question :
for single trigger script i have not used any skill, but for this we are using "sinric" ?

myTest.txt

Hyperpalette · 2018-06-18T20:35:39Z

Isn’t Synric another AWS like (public cloud server)?

Hyperpalette · 2018-06-18T20:39:12Z

And if it is, is it not much different than Ewelink?

@n8henrie

n8henrie/fauxmo#38 (comment) kakopappa/arduino-esp8266-alexa-multiple-wemo-switch#22 (comment) @n8henrie -- To answer your question: The fauxmo devices don't show up in the app after discovery is complete. I currently have several devices including real hardware that all work fine. --However-- Based on @ertgtct suggestion I did some experimentation and now I can find the devices on discovery. Specifically I changed the response in the function "respond_to_search" from: response = '\n'.join([ 'HTTP/1.1 200 OK', 'CACHE-CONTROL: max-age=86400', f'DATE: {date_str}', 'EXT:', f'LOCATION: {location}', 'OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01', f'01-NLS: {uuid.uuid4()}', 'SERVER: Fauxmo, UPnP/1.0, Unspecified', 'ST: urn:Belkin:device:**', f'USN: uuid:Socket-1_0-{serial}::upnp:rootdevice', ]) + '\n\n' To: response = '\n'.join([ 'HTTP/1.1 200 OK', 'CACHE-CONTROL: max-age=86400', f'DATE: {date_str}', 'EXT:', f'LOCATION: {location}', 'OPT: "http://schemas.upnp.org/upnp/1/0/"; ns=01', f'01-NLS: {uuid.uuid4()}', 'SERVER: Fauxmo, UPnP/1.0, Unspecified', 'ST: ::upnp:rootdevice', f'USN: uuid:Socket-1_0-{serial}::upnp:rootdevice', ]) + '\n\n'` (the change is the ST: clause) As yet I haven't managed to get the devices working but I suspect that's more to do with my environment rather than the fauxmo code. I've attached the log from a successful discovery, I don't know if you can spot where the change has made a difference. I'll continue testing and report back when I have a fully functioning system. log06.txt Thanks.

lackdaz · 2018-09-19T09:12:39Z

Picked up on your comment regarding the accounts. After lots of various testing I found issues with having a "household" Amazon account. Saying "Alexa switch accounts" and then "Alexa discover devices" did the trick. Not only did the Echo find the devices but it also allowed me to trigger them and the serial output of the WemosD1mini showed the catch of the event. Bottom line .... I can now trigger a relay by saying "Alexa switch office lights on" etc.. Thanks all. To confirm I have 2x latest EchoDots only on my network.

After scouring most of the forums. This was my fix!!!

santosh09142 · 2018-09-19T09:42:26Z

Hi lacdaz,

Can you elaborate more on this topic . Because I can see script work for 4 device and not more then that.

lackdaz · 2018-09-19T17:06:29Z

Hi lacdaz,

Can you elaborate more on this topic . Because I can see script work for 4 device and not more then that.

Hey buddy, just check out the sinric that @kakopappa authored as well.

There is much less bloat in the code and its just a simpler implementation than this one you are attempting. Yes, you need to link the sinric skill.

kakopappa mentioned this issue Nov 21, 2017

unable to find devices #23

Open

sciencegirl100 closed this as completed Dec 19, 2017

kakopappa added a commit to kakopappa/arduino-esp8266-alexa-wemo-switch that referenced this issue Dec 19, 2017

Issue 22 fix added.

3f02d13

Issue fixed kakopappa/arduino-esp8266-alexa-multiple-wemo-switch#22 (comment)

jtai mentioned this issue Mar 4, 2018

There is a possible mistake in emulate.js dhleong/wemore#14

Closed

lackdaz mentioned this issue Sep 19, 2018

Alexa can't discover devices and invocations not working kakopappa/sinric#117

Closed

rajnish1959 mentioned this issue Oct 13, 2019

How does GPIO are decided by sinric on ESP 8266? sinricpro/language-files#8

Closed

pvint mentioned this issue Oct 8, 2020

Echo doesn't discover device vintlabs/fauxmoESP#25

Closed

Alexa SmartHome skill - not finding #22

Alexa SmartHome skill - not finding #22

Comments

sciencegirl100 commented Nov 2, 2017

dougstrickland commented Nov 3, 2017

sciencegirl100 commented Nov 3, 2017

Braandn commented Nov 4, 2017

MacSass commented Nov 5, 2017

MacSass commented Nov 5, 2017

sciencegirl100 commented Nov 8, 2017

arnowillig commented Nov 24, 2017

kakopappa commented Nov 25, 2017

ma7gdp commented Nov 26, 2017

RootCNC commented Dec 1, 2017

kakopappa commented Dec 2, 2017

tommyfranke commented Dec 3, 2017

ZoMiGo commented Dec 6, 2017

arnowillig commented Dec 6, 2017 via email

RootCNC commented Dec 8, 2017

sciencegirl100 commented Dec 17, 2017

MacSass commented Dec 17, 2017

MacSass commented Dec 18, 2017

MacSass commented Dec 18, 2017 • edited Loading

sciencegirl100 commented Dec 19, 2017 • edited Loading

ma7gdp commented Dec 20, 2017 • edited Loading

MacSass commented Dec 20, 2017

MacSass commented Dec 20, 2017

Responding to /upnp/control/basicevent1 ...

ma7gdp commented Dec 21, 2017

MacSass commented Dec 21, 2017

ma7gdp commented Dec 21, 2017

ma7gdp commented Dec 22, 2017

kakopappa commented Jan 28, 2018

MacSass commented Jan 28, 2018

MacSass commented Jan 28, 2018

AvisIoT commented Jan 28, 2018 • edited Loading

RanTalbott commented Feb 4, 2018

charles commented Feb 5, 2018

LiamFatz commented Mar 3, 2018

tollermine commented Mar 22, 2018

hinkey247 commented Apr 7, 2018

hinkey247 commented Apr 7, 2018

santosh09142 commented May 6, 2018 • edited Loading

kakopappa commented May 6, 2018 via email

santosh09142 commented May 6, 2018

hinkey247 commented May 6, 2018

kakopappa commented May 6, 2018 via email

santosh09142 commented May 6, 2018

santosh09142 commented May 6, 2018 via email

hinkey247 commented May 6, 2018

santosh09142 commented May 6, 2018 via email

santosh09142 commented May 7, 2018 • edited Loading

Hyperpalette commented Jun 18, 2018

Hyperpalette commented Jun 18, 2018

lackdaz commented Sep 19, 2018

santosh09142 commented Sep 19, 2018

lackdaz commented Sep 19, 2018

MacSass commented Dec 18, 2017 •

edited

Loading

sciencegirl100 commented Dec 19, 2017 •

edited

Loading

ma7gdp commented Dec 20, 2017 •

edited

Loading

AvisIoT commented Jan 28, 2018 •

edited

Loading

santosh09142 commented May 6, 2018 •

edited

Loading

santosh09142 commented May 7, 2018 •

edited

Loading