nassir-malik/iot-pi3-alexa-automation

Use Raspberry Pi 3 as home automation device with Alexa

iot-pi3-alexa-automation's Issues

SOLVED: I own both echo dot 2nd gen and echo dot 3rd generation, if Alexa is NOT seeing your fauxmo Wemo plugs then you MUST USE a 3rd generation Echo dot residing on the same Wifi network as your project (for Alexa to discover the fauxmo Wemo plugs)

I have tested this theory for myself. I have three Wifi networks in my home. I had all my amazon devices on NETGEAR wifi using the 5 GHz . I have done this project before, making each of the 20 remote buttons on my Tempur-pedic bed a fauxmo device. In the ended, I added over 50 fauxmo devices to my Alexa app. I had to create 10 files, each file containing no more than five fauxmo devices each. Put all 10 scripts into cron and they all work wonderfully together.

#1 Reason, Alexa may not find your devices:
During the Alexa discover devices, Alexa will only discover, at most 5 fauxmo, devices during the 45 seconds. So if you have more than 5 devices, my suggestion is that you split them up into different scripts with 5 devices per script. Now, each script will be the same expect for the TRIGGERS and the if...elif...name = 'device1' blocks.

#2 Reason, Alexa may not find your devices:
You must have a 3rd generation Echo Dot on the same wifi network at you raspberry pi wifi. All Amazon Echo Dot devices use wifi to connect to the outside world. With my current project, I wanted to activate my garage door by using Alexa, but also have a website activate the door with a video of the inside of my garage. The wifi that works in that garage is on ARRIS wifi not my NETGEAR wifi network (where all my Alexa devices are located). So when I tried to discover the fauxmo devices, Alexa came up empty. So I came here, and saw that our leader recommend that an Amazon Echo Dot 2nd generation has to be on the same network. So I went and bought an Alexa Echo Dot 2nd generation from Amazon. Placed the Echo Dot 2nd generation on the ARRIS wifi and this was the output:
DEBUG:root:Responding to setup.xml for Triumph Garage
DEBUG:root:Responding to search for Volvo Garage
DEBUG:root:Responding to search for Triumph Garage
DEBUG:root:Responding to search for Volvo Garage
DEBUG:root:Responding to search for Triumph Garage
DEBUG:root:Responding to search for Volvo Garage
DEBUG:root:Responding to search for Triumph Garage
DEBUG:root:Responding to search for Volvo Garage
DEBUG:root:Responding to search for Triumph Garage
DEBUG:root:Responding to search for Volvo Garage
DEBUG:root:Responding to search for Triumph Garage
DEBUG:root:################################## handle_reques #######################
DEBUG:root:b'GET /setup.xml HTTP/1.1\r\nHost: 192.168.0.50:52000\r\nAccept: /\r\n\r\n'
DEBUG:root:################################## handle_reques #######################
DEBUG:root:Responding to setup.xml for Volvo Garage
DEBUG:root:################################## handle_reques #######################
DEBUG:root:b'GET /setup.xml HTTP/1.1\r\nHost: 192.168.0.50:52001\r\nAccept: /\r\n\r\n'
DEBUG:root:################################## handle_reques #######################
DEBUG:root:Responding to setup.xml for Triumph Garage
DEBUG:root:################################## handle_reques #######################
DEBUG:root:b'GET /setup.xml HTTP/1.1\r\nHost: 192.168.0.50:52000\r\nAccept: /\r\n\r\n'
DEBUG:root:################################## handle_reques #######################
DEBUG:root:Responding to setup.xml for Volvo Garage
DEBUG:root:################################## handle_reques #######################
DEBUG:root:b'GET /setup.xml HTTP/1.1\r\nHost: 192.168.0.50:52001\r\nAccept: /\r\n\r\n'
DEBUG:root:################################## handle_reques #######################
DEBUG:root:Responding to setup.xml for Triumph Garage
DEBUG:root:Responding to search for Volvo Garage
DEBUG:root:Responding to search for Triumph Garage
DEBUG:root:Responding to search for Volvo Garage

You will notice I never got a "POST" in the output list. So I decided to move one of my Echo Dot 3rd generation over to the ARRIS wifi. I of course had to do a factory reset to do this. If I did not do the factory reset, the echo dot, would just go back to the NETGEAR wifi network. So, yes, a factory reset was need to clear the NETGEAR wifi password from the device. Here is the output I got from the Echo Dot 3rd gen. (by this time I had factory reset the echo 2nd gen and powered it off so it was not in my Alexa App or on the wifi network):

DEBUG:root:Listening for UPnP broadcasts
DEBUG:root:got local address of 192.168.0.50
DEBUG:root:UPnP broadcast listener: new device registered
DEBUG:root:FauxMo device 'Volvo Garage' ready on 192.168.0.50:52000
DEBUG:root:UPnP broadcast listener: new device registered
DEBUG:root:FauxMo device 'Triumph Garage' ready on 192.168.0.50:52001
DEBUG:root: (Volvo) Left_garage_door closed
DEBUG:root: (Volvo) Left_garage_door_previous_action open
DEBUG:root: (Triumph) *******************************Right_garage_door closed
DEBUG:root: (Triumph) *******************************Right_garage_door_previous_action open
DEBUG:root:Entering fauxmo polling loop
DEBUG:root:Responding to search for Volvo Garage
DEBUG:root:Responding to search for Triumph Garage
DEBUG:root:Responding to search for Volvo Garage
DEBUG:root:Responding to search for Triumph Garage
DEBUG:root:Responding to search for Volvo Garage
DEBUG:root:Responding to search for Triumph Garage
DEBUG:root:Responding to search for Volvo Garage
DEBUG:root:Responding to search for Triumph Garage
DEBUG:root:Responding to search for Volvo Garage
DEBUG:root:Responding to search for Triumph Garage
DEBUG:root:################################## handle_reques #######################
DEBUG:root:b'GET /setup.xml HTTP/1.1\r\nContent-Type: application/json\r\nUser-Agent: Dalvik/2.1.0 (Linux; U; Android 7.1.2; AEODN Build/NS6531)\r\nHost: 192.168.0.50:52000\r\nConnection: Keep-Alive\r\nAccept-Encoding: gzip\r\n\r\n'
DEBUG:root:################################## handle_reques #######################
DEBUG:root:Responding to setup.xml for Volvo Garage
DEBUG:root:Responding to search for Volvo Garage
DEBUG:root:Responding to search for Triumph Garage
DEBUG:root:################################## handle_reques #######################
DEBUG:root:b'GET /setup.xml HTTP/1.1\r\nContent-Type: application/json\r\nUser-Agent: Dalvik/2.1.0 (Linux; U; Android 7.1.2; AEODN Build/NS6531)\r\nHost: 192.168.0.50:52001\r\nConnection: Keep-Alive\r\nAccept-Encoding: gzip\r\n\r\n'
DEBUG:root:################################## handle_reques #######################
DEBUG:root:Responding to setup.xml for Triumph Garage
DEBUG:root:################################## handle_reques #######################
DEBUG:root:b'POST /upnp/control/basicevent1 HTTP/1.1\r\nSOAPACTION: "urn:Belkin:service:basicevent:1#GetBinaryState"\r\nContent-Type: text/xml; charset="utf-8"\r\nAccept: \r\nUser-Agent: Dalvik/2.1.0 (Linux; U; Android 7.1.2; AEODN Build/NS6531)\r\nHost: 192.168.0.50:52000\r\nConnection: Keep-Alive\r\nAccept-Encoding: gzip\r\nContent-Length: 299\r\n\r\n<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">1</u:GetBinaryState></s:Body></s:Envelope>'
DEBUG:root:################################## handle_reques #######################
DEBUG:root:################################## response #######################
DEBUG:root:POST /upnp/control/basicevent1 HTTP/1.1
SOAPACTION: "urn:Belkin:service:basicevent:1#GetBinaryState"
Content-Type: text/xml; charset="utf-8"
Accept:
User-Agent: Dalvik/2.1.0 (Linux; U; Android 7.1.2; AEODN Build/NS6531)
Host: 192.168.0.50:52000
Connection: Keep-Alive
Accept-Encoding: gzip
Content-Length: 299

1

DEBUG:root:################################## handle_reques #######################
DEBUG:root:b'POST /upnp/control/basicevent1 HTTP/1.1\r\nSOAPACTION: "urn:Belkin:service:basicevent:1#GetBinaryState"\r\nContent-Type: text/xml; charset="utf-8"\r\nAccept: \r\nUser-Agent: Dalvik/2.1.0 (Linux; U; Android 7.1.2; AEODN Build/NS6531)\r\nHost: 192.168.0.50:52001\r\nConnection: Keep-Alive\r\nAccept-Encoding: gzip\r\nContent-Length: 299\r\n\r\n<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">1</u:GetBinaryState></s:Body></s:Envelope>'
DEBUG:root:################################## handle_reques #######################
DEBUG:root:################################## response #######################
DEBUG:root:POST /upnp/control/basicevent1 HTTP/1.1
SOAPACTION: "urn:Belkin:service:basicevent:1#GetBinaryState"
Content-Type: text/xml; charset="utf-8"
Accept:
User-Agent: Dalvik/2.1.0 (Linux; U; Android 7.1.2; AEODN Build/NS6531)
Host: 192.168.0.50:52001
Connection: Keep-Alive
Accept-Encoding: gzip
Content-Length: 299

#3 Reason,Alexa may not find your devices:
Well this one is not a reason. Alexa my tell you via her voice "no devices found", but there were devices found!!. So instead of initiating the discover devices verbally, I go to my Alexa App and select Devices in the lower Right Corner, then wait for the devices to start listing on my output screen from the script (this part):
DEBUG:root:Listening for UPnP broadcasts
DEBUG:root:got local address of 192.168.0.50
DEBUG:root:UPnP broadcast listener: new device registered
DEBUG:root:FauxMo device 'Volvo Garage' ready on 192.168.0.50:52000
DEBUG:root:UPnP broadcast listener: new device registered
DEBUG:root:FauxMo device 'Triumph Garage' ready on 192.168.0.50:52001
DEBUG:root: (Volvo) Left_garage_door closed
DEBUG:root: (Volvo) Left_garage_door_previous_action open
DEBUG:root: (Triumph) *******************************Right_garage_door closed
DEBUG:root: (Triumph) *******************************Right_garage_door_previous_action open
DEBUG:root:Entering fauxmo polling loop
DEBUG:root:Responding to search for Volvo Garage
DEBUG:root:Responding to search for Triumph Garage
DEBUG:root:Responding to search for Volvo Garage
.. will "eep repeating the device list....

Once I am past this point then in my Alexa App I hit the + (plus sign), in the upper RIGHT Corner, and then select "Add Device", then select "Plug", then select "Wemo", then select "Discover Devices". Alexa will come back with the number of devices she has found. If you still have not found your devices, reduce the number is she looking at (see #1 Reason above). If Alexa still has not found your devices try running discovery again. If after that your devices are not found and you have a Echo Dot 3rd generation on the same wifi and your raspberry pi, all I can say is start putting in logging.debug statements to see where the software is getting hung up at.

Since the output from the Echo 2nd generation Dot never puts out a "POST" command, I concluded that the Alexa Echo 2nd Gen no longer gives the appropriate response for the fauxmo devices. So get yourself an Echo 3rd Gen device and make sure you place it on the same wifi as your raspberry pi. Now the Alexa App can be running on any wifi network you want. What matters is the Echo 3rd gen DOT is on the SAME Wifi as your raspberry pi wifi network. I did not test to see if I had the raspberry pi on ARRIS hardwired network if it would work, but I suspect it would work.

In my home the ARRIS wifi is 192.168.0.X while the NETGEAR is 192.168.1.X.

By the way if you wait, Amazon Prime Days starts on July 15 and you will be able to pick up an Amazon Echo Dot 3rd generate for $24.99 ($25.00 off)

I hope this helps someone get there fauxmo devices working.

Regards,
GadgetAngel

Creating an light type device with color changing option for alexa..!!

Hi,

Can we create a light type device in alexa with color option using the script to control the hue devices.

Any help would be greatly appreciated

Thanks,

3rd Gen update for fauxmo.py

Hi Nassir,

I know you have updated fauxmo.py to adapt with 3rd gen alexa. But it looks like they have rolled out some new update on top of their 3rd gen, which has again caused issues with the existing fauxmo.py.
Will be glad if you can give it a look and see if fauxmo.py can be fixed again.

Using a 433mhz transmitter instead of a relay

Hi, this project is great to turn on/off a relay but what about having my blinds going up or down. I use raspberry pi to control 4 blinds by sending a code to a transmitter connected to GPIO 0 on my raspberry and it works great. Is there a way to call my program from within the rpi_name_port_gpio.py passing the signal code on or off for each of my blinds?

Originally posted by @ThierryDB in #18 (comment)

Pi turns LED off automatically after few seconds.

Thanks for the good instructions. I just have one problem with it. When I tell alexa to turn it on "kitchen" (in my case just an LED) it turns it on properly but after a few seconds the LED turns off without any command or text output in the terminal.
Any ideas on how to fix this problem?
Thanks

can't work with raspberry pi

Suddenly my echo dot can't discover new (and old) devices

After many week of using today the echo stopped seeing the devices it already knew and new ones.
In the alexa app says "Device is unresponsive".
Running the code says the following:

DEBUG:root:Listening for UPnP broadcasts
DEBUG:root:got local address of 192.168.1.8
DEBUG:root:UPnP broadcast listener: new device registered
DEBUG:root:FauxMo device 'Kitchen' ready on 192.168.1.8:55555
DEBUG:root:UPnP broadcast listener: new device registered
DEBUG:root:FauxMo device 'Living Room' ready on 192.168.1.8:55556
DEBUG:root:UPnP broadcast listener: new device registered
DEBUG:root:FauxMo device 'Fan' ready on 192.168.1.8:55557
DEBUG:root:Entering fauxmo polling loop
DEBUG:root:Responding to search for Kitchen
DEBUG:root:Responding to search for Living Room
DEBUG:root:Responding to search for Fan

When i ask alexa to discover my devices the following responses come:

################################## handle_reques #######################
b'GET /setup.xml HTTP/1.1\r\nHost: 192.168.1.8:55555\r\nAccept: /\r\nContent-Type: application/json\r\n\r\n'
################################## handle_reques #######################
DEBUG:root:Responding to setup.xml for Kitchen
################################## handle_reques #######################
b'GET /setup.xml HTTP/1.1\r\nHost: 192.168.1.8:55556\r\nAccept: /\r\nContent-Type: application/json\r\n\r\n'
################################## handle_reques #######################
DEBUG:root:Responding to setup.xml for Living Room
################################## handle_reques #######################
b'GET /setup.xml HTTP/1.1\r\nHost: 192.168.1.8:55557\r\nAccept: /\r\nContent-Type: application/json\r\n\r\n'
################################## handle_reques #######################
DEBUG:root:Responding to setup.xml for Fan

As i can tell the ports for the wemo devices are correct:

TRIGGERS = {"Kitchen": 55555,"Living Room":55556,"Fan":55557}

But still the alexa says that there are no new devices and shows none at the alexa app.
Echo Dot device Software Version: 3725203076
Script is running on Raspberry Pi 3B

getting errors while running the python program

this is the error.. Kindly do the needful

pi@raspberrypi:~/IOT-Pi3-Alexa-Automation-master $ sudo python RPi_name_port_gpio_8_Relays2.py
DEBUG:root:Listening for UPnP broadcasts
DEBUG:root:got local address of 192.168.0.110
DEBUG:root:UPnP broadcast listener: new device registered
DEBUG:root:FauxMo device 'pc' ready on 192.168.0.110:52004
DEBUG:root:UPnP broadcast listener: new device registered
DEBUG:root:FauxMo device 'living room' ready on 192.168.0.110:51000
DEBUG:root:UPnP broadcast listener: new device registered
DEBUG:root:FauxMo device 'room' ready on 192.168.0.110:52002
DEBUG:root:UPnP broadcast listener: new device registered
DEBUG:root:FauxMo device 'office' ready on 192.168.0.110:53000
DEBUG:root:UPnP broadcast listener: new device registered
DEBUG:root:FauxMo device 'tv' ready on 192.168.0.110:52003
DEBUG:root:UPnP broadcast listener: new device registered
DEBUG:root:FauxMo device 'light' ready on 192.168.0.110:52006
DEBUG:root:UPnP broadcast listener: new device registered
DEBUG:root:FauxMo device 'xbox' ready on 192.168.0.110:52005
DEBUG:root:UPnP broadcast listener: new device registered
DEBUG:root:FauxMo device 'kitchen' ready on 192.168.0.110:52000
DEBUG:root:Entering fauxmo polling loop
DEBUG:root:Responding to search for pc
Traceback (most recent call last):
File "RPi_name_port_gpio_8_Relays2.py", line 102, in
logging.critical("Critical exception: "+ e.args )
TypeError: cannot concatenate 'str' and 'tuple' objects

Led not turning on

So I followed the step on the git hub and everything works except for the led
I mean when the button is pressed on Alexa app it pops up on the command line with code and the Alexa app said it is on but the led does not turn on, is there a way to do this or not? Does it only work with relays? Please help.

Alexa installed in raspberry pi not recognizing the fauxmo device list

I have alexa installed and running successfully on my raspberry pi 3B+ and I can play with it. I understand from the fauxmo script that we can trick and have the pins of the raspberry pi to be interpreted as individual devices. I tried the steps outlined in the readme, but alexa responds as "No smart home devices found". Can you please assist if this can be possible with alexa installed on raspberry pi? If so, can you please guide what I'm missing?

Thanks,
Hemant.

Possibility to run scripts, not only GPIO

At this moment is possibile to only do on/off GPIO.
I have some scripts runed manually. I would like to have possibility to run this script by comand: "Alexa, turn SCRIPT1 on". Second "Alexa, turn SCRIPT1 off" will breat this script (where SCRIPT1 is a trigger for /home/pi/script1.py
Is it possible to prepare additional file, for this kidn of use?

Script not working on PI 4

Hi, I was recently use this script on my pi 4 but not working, the error is same at another "issues" in this forum #20 , in my case alexa and raspberry is connected to same wlan and i see both device, i have echo dot 3g...

Thanks for help me in advance :)

RPi 3 problems w/ New Code

So last year in dec I firstly installed this script and it worked just fine. But now i had to reinstall everything and now the code output looks a little different and alexa(gen 2. which worked before) does not find any new device.

I'll bold the new part.

Code Output:

pi@raspberrypi:~/Alexa/IOT-Pi3-Alexa-Automation-master $ sudo python3 RPi_name_port_gpio.py
DEBUG:root:Listening for UPnP broadcasts
DEBUG:root:got local address of 192.168.1.105
DEBUG:root:UPnP broadcast listener: new device registered
DEBUG:root:FauxMo device 'kitchen' ready on 192.168.1.105:52000
DEBUG:root:UPnP broadcast listener: new device registered
DEBUG:root:FauxMo device 'living room' ready on 192.168.1.105:51000
DEBUG:root:Entering fauxmo polling loop
DEBUG:root:Responding to search for kitchen
DEBUG:root:Responding to search for living room
DEBUG:root:Responding to search for kitchen
DEBUG:root:Responding to search for living room
DEBUG:root:Responding to search for kitchen
DEBUG:root:Responding to search for living room
DEBUG:root:Responding to search for kitchen
DEBUG:root:Responding to search for living room
DEBUG:root:Responding to search for kitchen
DEBUG:root:Responding to search for living room
DEBUG:root:Responding to search for kitchen
DEBUG:root:Responding to search for living room
DEBUG:root:Responding to search for kitchen
DEBUG:root:Responding to search for living room
DEBUG:root:Responding to search for kitchen
DEBUG:root:Responding to search for living room
DEBUG:root:Responding to search for kitchen
DEBUG:root:Responding to search for living room
DEBUG:root:Responding to search for kitchen
DEBUG:root:Responding to search for living room
DEBUG:root:Responding to search for kitchen
DEBUG:root:Responding to search for living room
DEBUG:root:Responding to search for kitchen
DEBUG:root:Responding to search for living room
DEBUG:root:Responding to search for kitchen
DEBUG:root:Responding to search for living room
DEBUG:root:Responding to search for kitchen
DEBUG:root:Responding to search for living room
################################## handle_reques #######################
b'GET /setup.xml HTTP/1.1\r\nHost: 192.168.1.105:52000\r\nAccept: /\r\n\r\n'
################################## handle_reques #######################
DEBUG:root:Responding to setup.xml for kitchen
################################## handle_reques #######################
b'GET /setup.xml HTTP/1.1\r\nHost: 192.168.1.105:51000\r\nAccept: /\r\n\r\n'
################################## handle_reques #######################
DEBUG:root:Responding to setup.xml for living room
################################## handle_reques #######################
b'GET /setup.xml HTTP/1.1\r\nHost: 192.168.1.105:52000\r\nAccept: /\r\n\r\n'
################################## handle_reques #######################
DEBUG:root:Responding to setup.xml for kitchen
################################## handle_reques #######################
b'GET /setup.xml HTTP/1.1\r\nHost: 192.168.1.105:51000\r\nAccept: /\r\n\r\n'
################################## handle_reques #######################
DEBUG:root:Responding to setup.xml for living room
DEBUG:root:Responding to search for kitchen
DEBUG:root:Responding to search for living room

Is there a step missing?

Hello, and thank you for your youtube vids on alexa and RPI.
I have followed the directions, and I get the following in the console.

DEBUG:root:Listening for UPnP broadcasts
DEBUG:root:got local address of 192.168.0.24
DEBUG:root:UPnP broadcast listener: new device registered
DEBUG:root:FauxMo device 'office' ready on 192.168.0.24:52000
DEBUG:root:Entering fauxmo polling loop

yet when I ask alexa to discover devices she says she cannot find any.
Alexa is on the same network as the RPI. Any suggestions ?

Cant add devices since april of 2020.

Hello.

i have been using system for a while now and has worked perfectly for months,until last wek i deleted devices and try to ad new. the process that i take has not changed but the devices are not added i am stuck at DEBUG:root:Responding to search for ....

do maybe anyone had any idea what coul it be ?

Using a 433mhz transmitter instead of a relay?

compatibility with raspberry pi

Hello! I've been watching all of your videos and they have been an excellent guide. I have a small problem that I can't seem to figure out. I have downloaded and installed this program and have it running on my raspberry pi. When I issue a voice command to my echo dot or use the app on my phone, it controls the GPIOs perfectly. I have also followed the amazon tutorial [https://developer.amazon.com/docs/alexa-voice-service/get-a-refresh-token.html] to enable my raspberry pi to allow voice commands. Each script works separately. I can ask alexa on my pi to tell me a joke or the weather. However, when I ask her (on the pi) to "turn on office", it doesn't work. I have built the raspberry pi to be a smart mirror. The mirror program works. The GPIO devices work. The Alexa voice works. But the last two don't work together? I would like to be able to turn on/off the display using voice commands sent to the GPIO. Any insight?

change ON\OFF to OPEN\CLOSE

Hi,
I followed your instructions and youtube video and it works. THANK!

I changed the device name from "Kitchen" to "GarageDoor"

Can you show me how to change from On\Off to Open\Close so that I can say

Alexa OPEN garagedoor (instead of Alexa turn ON garagedoor)

Thanks,

Ask Alexa the state of Device

Can you show me how to modify so that I can ask Alexa the state of the device?

example: Alexa Is Kitchen light ON? Alexa Is LivingRoom light OFF?

Thanks,

Unable to discover device

Hi @nassir-malik . I'm using raspberry pi zero W and Alexa android app. The code is running successfully in pi and the terminal keeps on printing DEBUG:root:Responding to search for Office Light. But when I ask Alexa to discover devices, she replies that she couldn't find any devices. Both pi and mobile are on the same wifi. Please suggest any working hacks. Thank you.

Not working with Raspberry Pi zero W

Nassir, you've done a tremendous job and the script is working flawlessly with Pi 3, but it is not working with Pi zero W. In Pi zero, after running the script, it goes into polling mode but Echo Dot 2nd Gen is unable to detect it.

not working on raspberry pi 3 with python fail at running script

Hello,

at running the python script at every time the same fail:

logging.critical("Critical exception: "+ e.args )
TypeError: cannot concatenate 'str' and 'tuple' objects

Alexa find the new Connections but when i want to take it on or off the server is not connected or the device don`t accept it, can anyone help me?

Is there annother option?

Thanks!!

Raspbian Jessie not connecting.

I could never find the ip address of the pi. When I hooked up a monitor to it, I noticed that the wifi adapter was not found.
I used the latest raspbian, (streach) and the wifi turned on, but Alexa will not discover.

Any Ideas?

Alexa not discover these device

Alexa not discover these device, -------> please suggest me

I am using alexa dot second generation.

IOT-Pi3-Alexa-Automation-master $ sudo python3 RPi_name_port_gpio_8_Relays2.py
DEBUG:root:Listening for UPnP broadcasts
DEBUG:root:got local address of 10.78.10.6
DEBUG:root:UPnP broadcast listener: new device registered
DEBUG:root:FauxMo device 'office' ready on 10.78.10.6:53000
DEBUG:root:UPnP broadcast listener: new device registered
DEBUG:root:FauxMo device 'xbox' ready on 10.78.10.6:52005
DEBUG:root:UPnP broadcast listener: new device registered
DEBUG:root:FauxMo device 'room' ready on 10.78.10.6:52002
DEBUG:root:UPnP broadcast listener: new device registered
DEBUG:root:FauxMo device 'pc' ready on 10.78.10.6:52004
DEBUG:root:UPnP broadcast listener: new device registered
DEBUG:root:FauxMo device 'kitchen' ready on 10.78.10.6:52000
DEBUG:root:UPnP broadcast listener: new device registered
DEBUG:root:FauxMo device 'tv' ready on 10.78.10.6:52003
DEBUG:root:UPnP broadcast listener: new device registered
DEBUG:root:FauxMo device 'living room' ready on 10.78.10.6:51000
DEBUG:root:UPnP broadcast listener: new device registered
DEBUG:root:FauxMo device 'light' ready on 10.78.10.6:52006
DEBUG:root:Entering fauxmo polling loop
DEBUG:root:Responding to search for office
DEBUG:root:Responding to search for xbox
DEBUG:root:Responding to search for room
DEBUG:root:Responding to search for pc
DEBUG:root:Responding to search for kitchen
DEBUG:root:Responding to search for tv
DEBUG:root:Responding to search for living room
DEBUG:root:Responding to search for light
DEBUG:root:Responding to search for office
DEBUG:root:Responding to search for xbox
DEBUG:root:Responding to search for room
DEBUG:root:Responding to search for pc
DEBUG:root:Responding to search for kitchen
DEBUG:root:Responding to search for tv
DEBUG:root:Responding to search for living room
DEBUG:root:Responding to search for light
DEBUG:root:Responding to search for office
DEBUG:root:Responding to search for xbox
DEBUG:root:Responding to search for room
DEBUG:root:Responding to search for pc
DEBUG:root:Responding to search for kitchen
DEBUG:root:Responding to search for tv
DEBUG:root:Responding to search for living room
DEBUG:root:Responding to search for light
DEBUG:root:Responding to search for office
DEBUG:root:Responding to search for xbox
DEBUG:root:Responding to search for room
DEBUG:root:Responding to search for pc
DEBUG:root:Responding to search for kitchen
DEBUG:root:Responding to search for tv
DEBUG:root:Responding to search for living room
DEBUG:root:Responding to search for light