Unintended (emulated WeMo switch) activity if going to the Alexa Web App - Smart Home - Devices page about arduino-esp8266-alexa-multiple-wemo-switch

[wmweis62]

Unless I am seeing a glitch in Amazon’s service today, it appears that as of today Amazon is requiring Skills for device discovery now. Devices I have been able to discover without a Skill enabled for the past 6 months are no longer being discovered, even though the serial monitor is showing the UDP message and all the normal messages that follow. If this is true, we are going to have to rewrite some solutions we developed for people with limited mobility that we gave to them at no cost. From: Aruna Tennakoon <[email protected]> Sent: Sunday, March 18, 2018 9:04 AM To: kakopappa/arduino-esp8266-alexa-multiple-wemo-switch <[email protected]> Cc: wmweis62 <[email protected]>; Author <[email protected]> Subject: Re: [kakopappa/arduino-esp8266-alexa-multiple-wemo-switch] Unintended (emulated WeMo switch) activity if going to the Alexa Web App - Smart Home - Devices page (#36) I have seen issues like this often lately. It's something to do with router blocking the UDP or new firmware changes This is why I made Sinric smart home skill. I highly recommend you to move to Sinric smart home skill Checkout https://sinric.com

On Sun, Mar 18, 2018 at 8:54 PM wmweis62 ***@***.******@***.***>> wrote: I apologize for posting this here, but for now I am at a loss as to the best place for this. I am using the core sketch developed by kakopappa and others which allows for some callbacks to control some wemo emulated devices. I use this code in a very impactful way and would like to thank the developers. I have created voice activated controllers for beds and now doors so people with limited mobility can gain greater independence and I give those solutions to them at not cost. ( http://limitedmobility.solutions) The problem I am seeing is related to this core sketch although I am not suspecting a problem with the sketch. I raise this point here because I am at a loss with how to troubleshoot this problem and perhaps those more familiar with the way the messages from Amazon work in conjunction with this sketch can shed some light. So finally, here is the problem. The sketch is loaded on an ESP8266 NodeMCU E12 and it has 2 emulated WeMo switches. I connect my laptop to the ESP8266 and watch the serial port. When the upload finishes I observe the serial monitor and can see it obtain a IP address and see the following: Connecting to WiFi Connecting .... Connected to CenturyLink2749 IP address: 192.168.0.101 Begin multicast .. 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 : @@@@ ::getAlexaInvokeName @@@ FrontDoor index : 0 Adding switch : @@@@ ::getAlexaInvokeName @@@ BackDoor index : 1 The next step is to issue a Discovery using either a voice command or a discovery initiated by hitting the button in the Alexa app. During Discovery we should see additional text on the serial monitor that looks like the following. (At this lady’s house, discovery of this device never works and no additional text appears on the serial monitor during discovery. This exact same sketch works EVERYWHERE else with no problem.) So my question is this, how do I track where the UDP and the other are getting lost and I have no clue how to trace it. Again during Discovery I should see the UDP and other messages on the serial monitor, but at this DSL connected house I see none of these. Got UDP Belkin Request.. Sending response to 192.168.0.113 Port : 50000 Response sent ! Sending response to 192.168.0.113 Port : 50000 Response sent ! ########## Responding to setup.xml ... ######## localiP: 192.168.0.101 Sending :<?xml version="1.0"?><root><device><deviceType>urn:Belkin:device:controllee:1</deviceType><friendlyName>FrontDoor</friendlyName><manufacturer>Belkin International Inc.</manufacturer><modelName>Emulated Socket</modelName><modelNumber>3.1415</modelNumber><UDN>uuid:Socket-1_0-38323636-4558-4dda-9188-cda0e65e33ac-80</UDN><serialNumber>221517K0101769</serialNumber><binaryState>0</binaryState><serviceList><service><serviceType>urn:Belkin:service:basicevent:1</serviceType><serviceId>urn:Belkin:serviceId:basicevent1</serviceId><controlURL>/upnp/control/basicevent1</controlURL><eventSubURL>/upnp/event/basicevent1</eventSubURL><SCPDURL>/eventservice.xml</SCPDURL></service></serviceList></device></root> ########## Responding to setup.xml ... ######## localiP: 192.168.0.101 Sending :<?xml version="1.0"?><root><device><deviceType>urn:Belkin:device:controllee:1</deviceType><friendlyName>BackDoor</friendlyName><manufacturer>Belkin International Inc.</manufacturer><modelName>Emulated Socket</modelName><modelNumber>3.1415</modelNumber><UDN>uuid:Socket-1_0-38323636-4558-4dda-9188-cda0e65e33ac-81</UDN><serialNumber>221517K0101769</serialNumber><binaryState>0</binaryState><serviceList><service><serviceType>urn:Belkin:service:basicevent:1</serviceType><serviceId>urn:Belkin:serviceId:basicevent1</serviceId><controlURL>/upnp/control/basicevent1</controlURL><eventSubURL>/upnp/event/basicevent1</eventSubURL><SCPDURL>/eventservice.xml</SCPDURL></service></serviceList></device></root> From: Aruna Tennakoon ***@***.******@***.***>> Sent: Wednesday, January 10, 2018 8:00 PM To: kakopappa/arduino-esp8266-alexa-multiple-wemo-switch < ***@***.******@***.***>> Cc: wmweis62 ***@***.******@***.***>>; Author ***@***.******@***.***>> Subject: Re: [kakopappa/arduino-esp8266-alexa-multiple-wemo-switch] Unintended (emulated WeMo switch) activity if going to the Alexa Web App - Smart Home - Devices page (#36) Did you get it fixed? Let me know if it needs any code changes. Also try sinric smart home skill. It should be available in us On Thu, Jan 11, 2018 at 2:09 AM wmweis62 ***@***.******@***.***>> wrote: > Happy to report testing is going well for the fix for handling > GetBinaryState messages. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > < #36 (comment)>, > or mute the thread > < https://github.com/notifications/unsubscribe-auth/AHIM5t1bPLUvPrbYY2dZgKZju_x6fFG7ks5tJQrRgaJpZM4RZp1Q> > . > — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub< https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fkakopappa%2Farduino-esp8266-alexa-multiple-wemo-switch%2Fissues%2F36%23issuecomment-356800067&data=02%7C01%7C%7C49559769edfa4e7a941c08d558970963%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636512328068421147&sdata=cAY%2FHnHbO3JL4AUJ5twqFDft4nK4KnP5CYuykeJBGgA%3D&reserved=0>, or mute the thread< https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAcapexWTfNZaOEooJ2dHaVvIwJBNrrCpks5tJWslgaJpZM4RZp1Q&data=02%7C01%7C%7C49559769edfa4e7a941c08d558970963%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636512328068421147&sdata=PP0ReA33g68aTlcrYH8KHI6bnVGmZGpu3skIfoeUBqs%3D&reserved=0>. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#36 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHIM5pTvZ1rQt2sZNZNYf0JCMaHYyGilks5tfmcqgaJpZM4RZp1Q> .

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fkakopappa%2Farduino-esp8266-alexa-multiple-wemo-switch%2Fissues%2F36%23issuecomment-374001716&data=02%7C01%7C%7C719d724e4a214ee16f7008d58cd920fc%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636569786540848099&sdata=HifQXlKuiXaZlAkXTcS2aIEibBRVoInFovR%2F7NTLjm0%3D&reserved=0>, or mute the thread<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAcapez8TBc70mTDG64ms8-0-QJl2X3cjks5tfmldgaJpZM4RZp1Q&data=02%7C01%7C%7C719d724e4a214ee16f7008d58cd920fc%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636569786540848099&sdata=nhM3D5ZcFJxoQ6O0tf0tx0uMlNTSXyg1yg15eYUjDNs%3D&reserved=0>.

[wmweis62]

Happy to report testing is going well for the fix for handling GetBinaryState messages.

[kakopappa]

Did you get it fixed? Let me know if it needs any code changes. Also try sinric smart home skill. It should be available in us

…

On Thu, Jan 11, 2018 at 2:09 AM wmweis62 ***@***.***> wrote: Happy to report testing is going well for the fix for handling GetBinaryState messages. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#36 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHIM5t1bPLUvPrbYY2dZgKZju_x6fFG7ks5tJQrRgaJpZM4RZp1Q> .

[wmweis62]

Thanks for checking, yes all testing has gone well so far.

Sent from my Windows 10 phone

________________________________ From: Aruna Tennakoon <[email protected]> Sent: Wednesday, January 10, 2018 8:00:05 PM To: kakopappa/arduino-esp8266-alexa-multiple-wemo-switch Cc: wmweis62; Author Subject: Re: [kakopappa/arduino-esp8266-alexa-multiple-wemo-switch] Unintended (emulated WeMo switch) activity if going to the Alexa Web App - Smart Home - Devices page (#36) Did you get it fixed? Let me know if it needs any code changes. Also try sinric smart home skill. It should be available in us

On Thu, Jan 11, 2018 at 2:09 AM wmweis62 ***@***.***> wrote: Happy to report testing is going well for the fix for handling GetBinaryState messages. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#36 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHIM5t1bPLUvPrbYY2dZgKZju_x6fFG7ks5tJQrRgaJpZM4RZp1Q> .

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fkakopappa%2Farduino-esp8266-alexa-multiple-wemo-switch%2Fissues%2F36%23issuecomment-356800067&data=02%7C01%7C%7C49559769edfa4e7a941c08d558970963%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636512328068421147&sdata=cAY%2FHnHbO3JL4AUJ5twqFDft4nK4KnP5CYuykeJBGgA%3D&reserved=0>, or mute the thread<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAcapexWTfNZaOEooJ2dHaVvIwJBNrrCpks5tJWslgaJpZM4RZp1Q&data=02%7C01%7C%7C49559769edfa4e7a941c08d558970963%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636512328068421147&sdata=PP0ReA33g68aTlcrYH8KHI6bnVGmZGpu3skIfoeUBqs%3D&reserved=0>.

[wmweis62]

I apologize for posting this here, but for now I am at a loss as to the best place for this. I am using the core sketch developed by kakopappa and others which allows for some callbacks to control some wemo emulated devices. I use this code in a very impactful way and would like to thank the developers. I have created voice activated controllers for beds and now doors so people with limited mobility can gain greater independence and I give those solutions to them at not cost. (http://limitedmobility.solutions) The problem I am seeing is related to this core sketch although I am not suspecting a problem with the sketch. I raise this point here because I am at a loss with how to troubleshoot this problem and perhaps those more familiar with the way the messages from Amazon work in conjunction with this sketch can shed some light. So finally, here is the problem. The sketch is loaded on an ESP8266 NodeMCU E12 and it has 2 emulated WeMo switches. I connect my laptop to the ESP8266 and watch the serial port. When the upload finishes I observe the serial monitor and can see it obtain a IP address and see the following: Connecting to WiFi Connecting .... Connected to CenturyLink2749 IP address: 192.168.0.101 Begin multicast .. 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 : @@@@ ::getAlexaInvokeName @@@ FrontDoor index : 0 Adding switch : @@@@ ::getAlexaInvokeName @@@ BackDoor index : 1 The next step is to issue a Discovery using either a voice command or a discovery initiated by hitting the button in the Alexa app. During Discovery we should see additional text on the serial monitor that looks like the following. (At this lady’s house, discovery of this device never works and no additional text appears on the serial monitor during discovery. This exact same sketch works EVERYWHERE else with no problem.) So my question is this, how do I track where the UDP and the other are getting lost and I have no clue how to trace it. Again during Discovery I should see the UDP and other messages on the serial monitor, but at this DSL connected house I see none of these. Got UDP Belkin Request.. Sending response to 192.168.0.113 Port : 50000 Response sent ! Sending response to 192.168.0.113 Port : 50000 Response sent ! ########## Responding to setup.xml ... ######## localiP: 192.168.0.101 Sending :<?xml version="1.0"?><root><device><deviceType>urn:Belkin:device:controllee:1</deviceType><friendlyName>FrontDoor</friendlyName><manufacturer>Belkin International Inc.</manufacturer><modelName>Emulated Socket</modelName><modelNumber>3.1415</modelNumber><UDN>uuid:Socket-1_0-38323636-4558-4dda-9188-cda0e65e33ac-80</UDN><serialNumber>221517K0101769</serialNumber><binaryState>0</binaryState><serviceList><service><serviceType>urn:Belkin:service:basicevent:1</serviceType><serviceId>urn:Belkin:serviceId:basicevent1</serviceId><controlURL>/upnp/control/basicevent1</controlURL><eventSubURL>/upnp/event/basicevent1</eventSubURL><SCPDURL>/eventservice.xml</SCPDURL></service></serviceList></device></root> ########## Responding to setup.xml ... ######## localiP: 192.168.0.101 Sending :<?xml version="1.0"?><root><device><deviceType>urn:Belkin:device:controllee:1</deviceType><friendlyName>BackDoor</friendlyName><manufacturer>Belkin International Inc.</manufacturer><modelName>Emulated Socket</modelName><modelNumber>3.1415</modelNumber><UDN>uuid:Socket-1_0-38323636-4558-4dda-9188-cda0e65e33ac-81</UDN><serialNumber>221517K0101769</serialNumber><binaryState>0</binaryState><serviceList><service><serviceType>urn:Belkin:service:basicevent:1</serviceType><serviceId>urn:Belkin:serviceId:basicevent1</serviceId><controlURL>/upnp/control/basicevent1</controlURL><eventSubURL>/upnp/event/basicevent1</eventSubURL><SCPDURL>/eventservice.xml</SCPDURL></service></serviceList></device></root> From: Aruna Tennakoon <[email protected]> Sent: Wednesday, January 10, 2018 8:00 PM To: kakopappa/arduino-esp8266-alexa-multiple-wemo-switch <[email protected]> Cc: wmweis62 <[email protected]>; Author <[email protected]> Subject: Re: [kakopappa/arduino-esp8266-alexa-multiple-wemo-switch] Unintended (emulated WeMo switch) activity if going to the Alexa Web App - Smart Home - Devices page (#36) Did you get it fixed? Let me know if it needs any code changes. Also try sinric smart home skill. It should be available in us

On Thu, Jan 11, 2018 at 2:09 AM wmweis62 ***@***.***> wrote: Happy to report testing is going well for the fix for handling GetBinaryState messages. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#36 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHIM5t1bPLUvPrbYY2dZgKZju_x6fFG7ks5tJQrRgaJpZM4RZp1Q> .

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fkakopappa%2Farduino-esp8266-alexa-multiple-wemo-switch%2Fissues%2F36%23issuecomment-356800067&data=02%7C01%7C%7C49559769edfa4e7a941c08d558970963%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636512328068421147&sdata=cAY%2FHnHbO3JL4AUJ5twqFDft4nK4KnP5CYuykeJBGgA%3D&reserved=0>, or mute the thread<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAcapexWTfNZaOEooJ2dHaVvIwJBNrrCpks5tJWslgaJpZM4RZp1Q&data=02%7C01%7C%7C49559769edfa4e7a941c08d558970963%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636512328068421147&sdata=PP0ReA33g68aTlcrYH8KHI6bnVGmZGpu3skIfoeUBqs%3D&reserved=0>.

[kakopappa]

I have seen issues like this often lately. It's something to do with router blocking the UDP or new firmware changes This is why I made Sinric smart home skill. I highly recommend you to move to Sinric smart home skill Checkout https://sinric.com

…

On Sun, Mar 18, 2018 at 8:54 PM wmweis62 ***@***.***> wrote: I apologize for posting this here, but for now I am at a loss as to the best place for this. I am using the core sketch developed by kakopappa and others which allows for some callbacks to control some wemo emulated devices. I use this code in a very impactful way and would like to thank the developers. I have created voice activated controllers for beds and now doors so people with limited mobility can gain greater independence and I give those solutions to them at not cost. ( http://limitedmobility.solutions) The problem I am seeing is related to this core sketch although I am not suspecting a problem with the sketch. I raise this point here because I am at a loss with how to troubleshoot this problem and perhaps those more familiar with the way the messages from Amazon work in conjunction with this sketch can shed some light. So finally, here is the problem. The sketch is loaded on an ESP8266 NodeMCU E12 and it has 2 emulated WeMo switches. I connect my laptop to the ESP8266 and watch the serial port. When the upload finishes I observe the serial monitor and can see it obtain a IP address and see the following: Connecting to WiFi Connecting .... Connected to CenturyLink2749 IP address: 192.168.0.101 Begin multicast .. 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 : @@@@ ::getAlexaInvokeName @@@ FrontDoor index : 0 Adding switch : @@@@ ::getAlexaInvokeName @@@ BackDoor index : 1 The next step is to issue a Discovery using either a voice command or a discovery initiated by hitting the button in the Alexa app. During Discovery we should see additional text on the serial monitor that looks like the following. (At this lady’s house, discovery of this device never works and no additional text appears on the serial monitor during discovery. This exact same sketch works EVERYWHERE else with no problem.) So my question is this, how do I track where the UDP and the other are getting lost and I have no clue how to trace it. Again during Discovery I should see the UDP and other messages on the serial monitor, but at this DSL connected house I see none of these. Got UDP Belkin Request.. Sending response to 192.168.0.113 Port : 50000 Response sent ! Sending response to 192.168.0.113 Port : 50000 Response sent ! ########## Responding to setup.xml ... ######## localiP: 192.168.0.101 Sending :<?xml version="1.0"?><root><device><deviceType>urn:Belkin:device:controllee:1</deviceType><friendlyName>FrontDoor</friendlyName><manufacturer>Belkin International Inc.</manufacturer><modelName>Emulated Socket</modelName><modelNumber>3.1415</modelNumber><UDN>uuid:Socket-1_0-38323636-4558-4dda-9188-cda0e65e33ac-80</UDN><serialNumber>221517K0101769</serialNumber><binaryState>0</binaryState><serviceList><service><serviceType>urn:Belkin:service:basicevent:1</serviceType><serviceId>urn:Belkin:serviceId:basicevent1</serviceId><controlURL>/upnp/control/basicevent1</controlURL><eventSubURL>/upnp/event/basicevent1</eventSubURL><SCPDURL>/eventservice.xml</SCPDURL></service></serviceList></device></root> ########## Responding to setup.xml ... ######## localiP: 192.168.0.101 Sending :<?xml version="1.0"?><root><device><deviceType>urn:Belkin:device:controllee:1</deviceType><friendlyName>BackDoor</friendlyName><manufacturer>Belkin International Inc.</manufacturer><modelName>Emulated Socket</modelName><modelNumber>3.1415</modelNumber><UDN>uuid:Socket-1_0-38323636-4558-4dda-9188-cda0e65e33ac-81</UDN><serialNumber>221517K0101769</serialNumber><binaryState>0</binaryState><serviceList><service><serviceType>urn:Belkin:service:basicevent:1</serviceType><serviceId>urn:Belkin:serviceId:basicevent1</serviceId><controlURL>/upnp/control/basicevent1</controlURL><eventSubURL>/upnp/event/basicevent1</eventSubURL><SCPDURL>/eventservice.xml</SCPDURL></service></serviceList></device></root> From: Aruna Tennakoon ***@***.***> Sent: Wednesday, January 10, 2018 8:00 PM To: kakopappa/arduino-esp8266-alexa-multiple-wemo-switch < ***@***.***> Cc: wmweis62 ***@***.***>; Author ***@***.***> Subject: Re: [kakopappa/arduino-esp8266-alexa-multiple-wemo-switch] Unintended (emulated WeMo switch) activity if going to the Alexa Web App - Smart Home - Devices page (#36) Did you get it fixed? Let me know if it needs any code changes. Also try sinric smart home skill. It should be available in us On Thu, Jan 11, 2018 at 2:09 AM wmweis62 ***@***.***> wrote: > Happy to report testing is going well for the fix for handling > GetBinaryState messages. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > < #36 (comment)>, > or mute the thread > < https://github.com/notifications/unsubscribe-auth/AHIM5t1bPLUvPrbYY2dZgKZju_x6fFG7ks5tJQrRgaJpZM4RZp1Q> > . > — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub< https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fkakopappa%2Farduino-esp8266-alexa-multiple-wemo-switch%2Fissues%2F36%23issuecomment-356800067&data=02%7C01%7C%7C49559769edfa4e7a941c08d558970963%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636512328068421147&sdata=cAY%2FHnHbO3JL4AUJ5twqFDft4nK4KnP5CYuykeJBGgA%3D&reserved=0>, or mute the thread< https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAcapexWTfNZaOEooJ2dHaVvIwJBNrrCpks5tJWslgaJpZM4RZp1Q&data=02%7C01%7C%7C49559769edfa4e7a941c08d558970963%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636512328068421147&sdata=PP0ReA33g68aTlcrYH8KHI6bnVGmZGpu3skIfoeUBqs%3D&reserved=0>. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#36 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHIM5pTvZ1rQt2sZNZNYf0JCMaHYyGilks5tfmcqgaJpZM4RZp1Q> .

[wmweis62]

It seems that discovery is working again and devices in sketches without Sinric are being discovered as they always have been. As I mentioned, discovery has always worked in my home lab, until yesterday afternoon. I saw all the normal activity on the serial monitor related to discovery including the UDP message and the subsequent messages, so I made the assumption Amazon was going to start enforcing Skills perhaps as added security so someone could not simply put a rouge device on someone’s network and have it get discovered. From: Aruna Tennakoon <[email protected]> Sent: Sunday, March 18, 2018 9:04 AM To: kakopappa/arduino-esp8266-alexa-multiple-wemo-switch <[email protected]> Cc: wmweis62 <[email protected]>; Author <[email protected]> Subject: Re: [kakopappa/arduino-esp8266-alexa-multiple-wemo-switch] Unintended (emulated WeMo switch) activity if going to the Alexa Web App - Smart Home - Devices page (#36) I have seen issues like this often lately. It's something to do with router blocking the UDP or new firmware changes This is why I made Sinric smart home skill. I highly recommend you to move to Sinric smart home skill Checkout https://sinric.com

On Sun, Mar 18, 2018 at 8:54 PM wmweis62 ***@***.******@***.***>> wrote: I apologize for posting this here, but for now I am at a loss as to the best place for this. I am using the core sketch developed by kakopappa and others which allows for some callbacks to control some wemo emulated devices. I use this code in a very impactful way and would like to thank the developers. I have created voice activated controllers for beds and now doors so people with limited mobility can gain greater independence and I give those solutions to them at not cost. ( http://limitedmobility.solutions) The problem I am seeing is related to this core sketch although I am not suspecting a problem with the sketch. I raise this point here because I am at a loss with how to troubleshoot this problem and perhaps those more familiar with the way the messages from Amazon work in conjunction with this sketch can shed some light. So finally, here is the problem. The sketch is loaded on an ESP8266 NodeMCU E12 and it has 2 emulated WeMo switches. I connect my laptop to the ESP8266 and watch the serial port. When the upload finishes I observe the serial monitor and can see it obtain a IP address and see the following: Connecting to WiFi Connecting .... Connected to CenturyLink2749 IP address: 192.168.0.101 Begin multicast .. 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 : @@@@ ::getAlexaInvokeName @@@ FrontDoor index : 0 Adding switch : @@@@ ::getAlexaInvokeName @@@ BackDoor index : 1 The next step is to issue a Discovery using either a voice command or a discovery initiated by hitting the button in the Alexa app. During Discovery we should see additional text on the serial monitor that looks like the following. (At this lady’s house, discovery of this device never works and no additional text appears on the serial monitor during discovery. This exact same sketch works EVERYWHERE else with no problem.) So my question is this, how do I track where the UDP and the other are getting lost and I have no clue how to trace it. Again during Discovery I should see the UDP and other messages on the serial monitor, but at this DSL connected house I see none of these. Got UDP Belkin Request.. Sending response to 192.168.0.113 Port : 50000 Response sent ! Sending response to 192.168.0.113 Port : 50000 Response sent ! ########## Responding to setup.xml ... ######## localiP: 192.168.0.101 Sending :<?xml version="1.0"?><root><device><deviceType>urn:Belkin:device:controllee:1</deviceType><friendlyName>FrontDoor</friendlyName><manufacturer>Belkin International Inc.</manufacturer><modelName>Emulated Socket</modelName><modelNumber>3.1415</modelNumber><UDN>uuid:Socket-1_0-38323636-4558-4dda-9188-cda0e65e33ac-80</UDN><serialNumber>221517K0101769</serialNumber><binaryState>0</binaryState><serviceList><service><serviceType>urn:Belkin:service:basicevent:1</serviceType><serviceId>urn:Belkin:serviceId:basicevent1</serviceId><controlURL>/upnp/control/basicevent1</controlURL><eventSubURL>/upnp/event/basicevent1</eventSubURL><SCPDURL>/eventservice.xml</SCPDURL></service></serviceList></device></root> ########## Responding to setup.xml ... ######## localiP: 192.168.0.101 Sending :<?xml version="1.0"?><root><device><deviceType>urn:Belkin:device:controllee:1</deviceType><friendlyName>BackDoor</friendlyName><manufacturer>Belkin International Inc.</manufacturer><modelName>Emulated Socket</modelName><modelNumber>3.1415</modelNumber><UDN>uuid:Socket-1_0-38323636-4558-4dda-9188-cda0e65e33ac-81</UDN><serialNumber>221517K0101769</serialNumber><binaryState>0</binaryState><serviceList><service><serviceType>urn:Belkin:service:basicevent:1</serviceType><serviceId>urn:Belkin:serviceId:basicevent1</serviceId><controlURL>/upnp/control/basicevent1</controlURL><eventSubURL>/upnp/event/basicevent1</eventSubURL><SCPDURL>/eventservice.xml</SCPDURL></service></serviceList></device></root> From: Aruna Tennakoon ***@***.******@***.***>> Sent: Wednesday, January 10, 2018 8:00 PM To: kakopappa/arduino-esp8266-alexa-multiple-wemo-switch < ***@***.******@***.***>> Cc: wmweis62 ***@***.******@***.***>>; Author ***@***.******@***.***>> Subject: Re: [kakopappa/arduino-esp8266-alexa-multiple-wemo-switch] Unintended (emulated WeMo switch) activity if going to the Alexa Web App - Smart Home - Devices page (#36) Did you get it fixed? Let me know if it needs any code changes. Also try sinric smart home skill. It should be available in us On Thu, Jan 11, 2018 at 2:09 AM wmweis62 ***@***.******@***.***>> wrote: > Happy to report testing is going well for the fix for handling > GetBinaryState messages. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > < #36 (comment)>, > or mute the thread > < https://github.com/notifications/unsubscribe-auth/AHIM5t1bPLUvPrbYY2dZgKZju_x6fFG7ks5tJQrRgaJpZM4RZp1Q> > . > — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub< https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fkakopappa%2Farduino-esp8266-alexa-multiple-wemo-switch%2Fissues%2F36%23issuecomment-356800067&data=02%7C01%7C%7C49559769edfa4e7a941c08d558970963%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636512328068421147&sdata=cAY%2FHnHbO3JL4AUJ5twqFDft4nK4KnP5CYuykeJBGgA%3D&reserved=0>, or mute the thread< https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAcapexWTfNZaOEooJ2dHaVvIwJBNrrCpks5tJWslgaJpZM4RZp1Q&data=02%7C01%7C%7C49559769edfa4e7a941c08d558970963%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636512328068421147&sdata=PP0ReA33g68aTlcrYH8KHI6bnVGmZGpu3skIfoeUBqs%3D&reserved=0>. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#36 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHIM5pTvZ1rQt2sZNZNYf0JCMaHYyGilks5tfmcqgaJpZM4RZp1Q> .

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fkakopappa%2Farduino-esp8266-alexa-multiple-wemo-switch%2Fissues%2F36%23issuecomment-374001716&data=02%7C01%7C%7C719d724e4a214ee16f7008d58cd920fc%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636569786540848099&sdata=HifQXlKuiXaZlAkXTcS2aIEibBRVoInFovR%2F7NTLjm0%3D&reserved=0>, or mute the thread<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAcapez8TBc70mTDG64ms8-0-QJl2X3cjks5tfmldgaJpZM4RZp1Q&data=02%7C01%7C%7C719d724e4a214ee16f7008d58cd920fc%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636569786540848099&sdata=nhM3D5ZcFJxoQ6O0tf0tx0uMlNTSXyg1yg15eYUjDNs%3D&reserved=0>.

[wmweis62]

Discover devices is behaving ‘normal’ again Not sure what happened yesterday afternoon. Perhaps Amazon was testing a software change intended to make it tougher for rouge devices to be placed on people’s networks. (Rough devices could not get discovered unless a skill was also enabled, tougher for the bad guys to pull off) From: Bill Weis Sent: Thursday, March 29, 2018 5:13 PM To: 'kakopappa/arduino-esp8266-alexa-multiple-wemo-switch' <[email protected]> Subject: RE: [kakopappa/arduino-esp8266-alexa-multiple-wemo-switch] Unintended (emulated WeMo switch) activity if going to the Alexa Web App - Smart Home - Devices page (#36) Unless I am seeing a glitch in Amazon’s service today, it appears that as of today Amazon is requiring Skills for device discovery now. Devices I have been able to discover without a Skill enabled for the past 6 months are no longer being discovered, even though the serial monitor is showing the UDP message and all the normal messages that follow. If this is true, we are going to have to rewrite some solutions we developed for people with limited mobility that we gave to them at no cost. From: Aruna Tennakoon <[email protected]<mailto:[email protected]>> Sent: Sunday, March 18, 2018 9:04 AM To: kakopappa/arduino-esp8266-alexa-multiple-wemo-switch <[email protected]<mailto:[email protected]>> Cc: wmweis62 <[email protected]<mailto:[email protected]>>; Author <[email protected]<mailto:[email protected]>> Subject: Re: [kakopappa/arduino-esp8266-alexa-multiple-wemo-switch] Unintended (emulated WeMo switch) activity if going to the Alexa Web App - Smart Home - Devices page (#36) I have seen issues like this often lately. It's something to do with router blocking the UDP or new firmware changes This is why I made Sinric smart home skill. I highly recommend you to move to Sinric smart home skill Checkout https://sinric.com

On Sun, Mar 18, 2018 at 8:54 PM wmweis62 ***@***.******@***.***>> wrote: I apologize for posting this here, but for now I am at a loss as to the best place for this. I am using the core sketch developed by kakopappa and others which allows for some callbacks to control some wemo emulated devices. I use this code in a very impactful way and would like to thank the developers. I have created voice activated controllers for beds and now doors so people with limited mobility can gain greater independence and I give those solutions to them at not cost. ( http://limitedmobility.solutions) The problem I am seeing is related to this core sketch although I am not suspecting a problem with the sketch. I raise this point here because I am at a loss with how to troubleshoot this problem and perhaps those more familiar with the way the messages from Amazon work in conjunction with this sketch can shed some light. So finally, here is the problem. The sketch is loaded on an ESP8266 NodeMCU E12 and it has 2 emulated WeMo switches. I connect my laptop to the ESP8266 and watch the serial port. When the upload finishes I observe the serial monitor and can see it obtain a IP address and see the following: Connecting to WiFi Connecting .... Connected to CenturyLink2749 IP address: 192.168.0.101 Begin multicast .. 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 : @@@@ ::getAlexaInvokeName @@@ FrontDoor index : 0 Adding switch : @@@@ ::getAlexaInvokeName @@@ BackDoor index : 1 The next step is to issue a Discovery using either a voice command or a discovery initiated by hitting the button in the Alexa app. During Discovery we should see additional text on the serial monitor that looks like the following. (At this lady’s house, discovery of this device never works and no additional text appears on the serial monitor during discovery. This exact same sketch works EVERYWHERE else with no problem.) So my question is this, how do I track where the UDP and the other are getting lost and I have no clue how to trace it. Again during Discovery I should see the UDP and other messages on the serial monitor, but at this DSL connected house I see none of these. Got UDP Belkin Request.. Sending response to 192.168.0.113 Port : 50000 Response sent ! Sending response to 192.168.0.113 Port : 50000 Response sent ! ########## Responding to setup.xml ... ######## localiP: 192.168.0.101 Sending :<?xml version="1.0"?><root><device><deviceType>urn:Belkin:device:controllee:1</deviceType><friendlyName>FrontDoor</friendlyName><manufacturer>Belkin International Inc.</manufacturer><modelName>Emulated Socket</modelName><modelNumber>3.1415</modelNumber><UDN>uuid:Socket-1_0-38323636-4558-4dda-9188-cda0e65e33ac-80</UDN><serialNumber>221517K0101769</serialNumber><binaryState>0</binaryState><serviceList><service><serviceType>urn:Belkin:service:basicevent:1</serviceType><serviceId>urn:Belkin:serviceId:basicevent1</serviceId><controlURL>/upnp/control/basicevent1</controlURL><eventSubURL>/upnp/event/basicevent1</eventSubURL><SCPDURL>/eventservice.xml</SCPDURL></service></serviceList></device></root> ########## Responding to setup.xml ... ######## localiP: 192.168.0.101 Sending :<?xml version="1.0"?><root><device><deviceType>urn:Belkin:device:controllee:1</deviceType><friendlyName>BackDoor</friendlyName><manufacturer>Belkin International Inc.</manufacturer><modelName>Emulated Socket</modelName><modelNumber>3.1415</modelNumber><UDN>uuid:Socket-1_0-38323636-4558-4dda-9188-cda0e65e33ac-81</UDN><serialNumber>221517K0101769</serialNumber><binaryState>0</binaryState><serviceList><service><serviceType>urn:Belkin:service:basicevent:1</serviceType><serviceId>urn:Belkin:serviceId:basicevent1</serviceId><controlURL>/upnp/control/basicevent1</controlURL><eventSubURL>/upnp/event/basicevent1</eventSubURL><SCPDURL>/eventservice.xml</SCPDURL></service></serviceList></device></root> From: Aruna Tennakoon ***@***.******@***.***>> Sent: Wednesday, January 10, 2018 8:00 PM To: kakopappa/arduino-esp8266-alexa-multiple-wemo-switch < ***@***.******@***.***>> Cc: wmweis62 ***@***.******@***.***>>; Author ***@***.******@***.***>> Subject: Re: [kakopappa/arduino-esp8266-alexa-multiple-wemo-switch] Unintended (emulated WeMo switch) activity if going to the Alexa Web App - Smart Home - Devices page (#36) Did you get it fixed? Let me know if it needs any code changes. Also try sinric smart home skill. It should be available in us On Thu, Jan 11, 2018 at 2:09 AM wmweis62 ***@***.******@***.***>> wrote: > Happy to report testing is going well for the fix for handling > GetBinaryState messages. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > < #36 (comment)>, > or mute the thread > < https://github.com/notifications/unsubscribe-auth/AHIM5t1bPLUvPrbYY2dZgKZju_x6fFG7ks5tJQrRgaJpZM4RZp1Q> > . > — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub< https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fkakopappa%2Farduino-esp8266-alexa-multiple-wemo-switch%2Fissues%2F36%23issuecomment-356800067&data=02%7C01%7C%7C49559769edfa4e7a941c08d558970963%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636512328068421147&sdata=cAY%2FHnHbO3JL4AUJ5twqFDft4nK4KnP5CYuykeJBGgA%3D&reserved=0>, or mute the thread< https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAcapexWTfNZaOEooJ2dHaVvIwJBNrrCpks5tJWslgaJpZM4RZp1Q&data=02%7C01%7C%7C49559769edfa4e7a941c08d558970963%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636512328068421147&sdata=PP0ReA33g68aTlcrYH8KHI6bnVGmZGpu3skIfoeUBqs%3D&reserved=0>. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#36 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHIM5pTvZ1rQt2sZNZNYf0JCMaHYyGilks5tfmcqgaJpZM4RZp1Q> .

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fkakopappa%2Farduino-esp8266-alexa-multiple-wemo-switch%2Fissues%2F36%23issuecomment-374001716&data=02%7C01%7C%7C719d724e4a214ee16f7008d58cd920fc%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636569786540848099&sdata=HifQXlKuiXaZlAkXTcS2aIEibBRVoInFovR%2F7NTLjm0%3D&reserved=0>, or mute the thread<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAcapez8TBc70mTDG64ms8-0-QJl2X3cjks5tfmldgaJpZM4RZp1Q&data=02%7C01%7C%7C719d724e4a214ee16f7008d58cd920fc%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636569786540848099&sdata=nhM3D5ZcFJxoQ6O0tf0tx0uMlNTSXyg1yg15eYUjDNs%3D&reserved=0>.

[uDude]

Bill Weis ... did you work at LA? If so, PM me.

[wmweis62]

No I did not, sorry. Get Outlook for Android<https://aka.ms/ghei36> From: uDude Sent: Tuesday, May 22, 3:39 AM Subject: Re: [kakopappa/arduino-esp8266-alexa-multiple-wemo-switch] Unintended (emulated WeMo switch) activity if going to the Alexa Web App - Smart Home - Devices page (#36) To: kakopappa/arduino-esp8266-alexa-multiple-wemo-switch Cc: wmweis62, Author Bill Weis ... did you work at LA? If so, PM me. - You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fkakopappa%2Farduino-esp8266-alexa-multiple-wemo-switch%2Fissues%2F36%23issuecomment-390909763&data=02%7C01%7C%7C0f1775a560674b038add08d5bfbf7f89%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636625751551968723&sdata=Rzr%2F0HJdY8o%2FHdHQU2xIc%2F5fOexwE7DIEBi6A6zae1w%3D&reserved=0>, or mute the thread<https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAcapex6yJudSlfgk8Y4WrRz86-M915TZks5t086xgaJpZM4RZp1Q&data=02%7C01%7C%7C0f1775a560674b038add08d5bfbf7f89%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636625751551988769&sdata=cmkvnSbKjQ48ouWP865j9AaBmZiOPH8zEn95TyjoZBA%3D&reserved=0>.