Open pihome-shc opened 4 years ago
waooo, it worked this time but i can not see any device in alexa app.
root@pihome:~# python /var/www/amazon_echo/echo_pihome.py DEBUG:root:Listening for UPnP broadcasts DEBUG:root:got local address of 192.168.99.16 DEBUG:root:UPnP broadcast listener: new device registered DEBUG:root:FauxMo device 'First Floor' ready on 192.168.99.16:52001 DEBUG:root:UPnP broadcast listener: new device registered DEBUG:root:FauxMo device 'Hot Water' ready on 192.168.99.16:52002 DEBUG:root:UPnP broadcast listener: new device registered DEBUG:root:FauxMo device 'Ground Floor' ready on 192.168.99.16:52000 DEBUG:root:Entering fauxmo polling loop DEBUG:root:Responding to search for First Floor DEBUG:root:Responding to search for Hot Water DEBUG:root:Responding to search for Ground Floor DEBUG:root:Responding to search for First Floor DEBUG:root:Responding to search for Hot Water DEBUG:root:Responding to search for Ground Floor DEBUG:root:Responding to search for First Floor DEBUG:root:Responding to search for Hot Water DEBUG:root:Responding to search for Ground Floor DEBUG:root:Responding to setup.xml for First Floor DEBUG:root:Responding to setup.xml for Hot Water DEBUG:root:Responding to setup.xml for Ground Floor DEBUG:root:POST /upnp/control/basicevent1 HTTP/1.1 Host: 192.168.99.16:52001 Content-Type: text/xml; charset="utf-8" SOAPACTION: "urn:Belkin:service:basicevent:1#GetBinaryState" Content-Length: 298
<?xml version="1.0" encoding="utf-8"?>
<?xml version="1.0" encoding="utf-8"?>
<?xml version="1.0" encoding="utf-8"?>
@twa127 full log attached, i can see debug on rpi but in alexa app still No new devices found message. logs.zip
One step forward :-) can you do me a wireshark dump when running device discovery please
Can you try this one please
@twa127 here is logs for last fauxmo.py file. echo_log.zip
i was thinking if we switch to mqqt would that help to integrate voice commands ? or it does nt matter ?
Hi,
Sort term we need to get the your version of the Echo to connect to the Rpi, have you had chance to try the latest fauxmo.py ?
yes i did, and i had same results as @pihome-shc. even on my own version of installation. (i m doing test on my own installation that i did for this test)
Can you generate me a wireshark dump please
Sent from my iPhone
On 27 Mar 2020, at 16:03, dvdcut notifications@github.com wrote:
yes i did, and i had same results as @pihome-shc. even on my own version of installation. (i m doing test on my own installation that i did for this test)
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.
Sorry forgot to say while running device discovery
@dvdcut you can start capture and in bookmark bar you can filter out your echo and rpi ip address ip.addr == xxx.xxx.xxx.xxx || ip.addr == xxx.xxx.xxx.xxx (replace xxx.xxx.xxx.xxx with ip address)
You can do the same with a capture filter of ip host xxx.xxx.xxx.xxx and ip host yyy.yyy.yyyy.yyy
Please try this one for me, slightly deeper xml message content
From the logs you've posted it looks like we you are getting to the last step of device discovery
echo.zip wireshark capture and shelloutput
Hi
I can't see the response packets from the RPi although they must be on the network as the log shows that the hand-shack is happening,
By the way have yo tried voice command to find devices?
in the attached wireshark dump you can see the first four transaction steps 5, 7, 11 and 13
hare are the full wireshark capture,
you want to have remote session over teamviewer ? and you can connect to echo over web and rpi. may be this will help to do troubleshooting better ?
Hi,
Thanks for the log, still can't see the traffic between the RPi and the Echo. The only thing I'm doing different is that I'm running Wireshark on the RPi, which is running fauxmo.py.
Can you try rebooting Echo and your RPi while Wireshark is running and see if that allows you to capture all the traffic.
Teamviewer might be an option
Ok, i m going to put kids to bed, give me 30ish minuets and I will reboot rpi and echo.
On 27 Mar 2020, at 20:42, twa127 notifications@github.com wrote:
Hi,
Thanks for the log, still can't see the traffic between the RPi and the Echo. The only thing I'm doing different is that I'm running Wireshark on the RPi, which is running fauxmo.py.
Can you try rebooting Echo and your RPi while Wireshark is running and see if that allows you to capture all the traffic.
Teamviewer might be an option
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.
after rpi and echo reboot
http://www.pihome.eu/wp-content/uploads/2020/03/echo_reboot.zip
Hi for some reason that file did not upload
Sent from my iPhone
On 27 Mar 2020, at 22:26, PiHomeHVAC notifications@github.com wrote:
after rpi and echo reboot
http://www.pihome.eu/wp-content/uploads/2020/03/echo_reboot.zip
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.
Hi
If you have a WeMos D1 Mini knocking about please give this a try, it works okay with my old Echo https://github.com/kakopappa/arduino-esp8266-alexa-multiple-wemo-switch
that didn't get discovered by echo either, can we take this offline, send me email for further testing and we can crack this.
Can someone give this a try please
@twa127 sorry spoke to soon, wemo switch code worked perfect, and echo can discover two switches, https://github.com/kakopappa/arduino-esp8266-alexa-multiple-wemo-switch
let me try your new code now.
@twa127, great work, your last python code worked and turn on boost but voice command says First Flooor isnt responding please check its network connection or its power supply. worked on all other other zone it turn on boost ok and turn off boost as well. but that voice command need fixing.
okay great, it still needs some work on the getreseponse side as it is currently just posting a zero so I could test it quickly
@twa127 one thing very strange, each time i do voice command it try to connect to that 8266 wemo module which is at 192.168.99.15 whereas my rpi is 192.168.99.2,
DEBUG:root:Responding to ON for First Floor
State True on First Floor from client @ 192.168.99.15
DEBUG:root:Responding to search for First Floor
DEBUG:root:Responding to search for Hot Water
DEBUG:root:Responding to search for Ground Floor
DEBUG:root:Responding to search for First Floor
DEBUG:root:Responding to search for Hot Water
DEBUG:root:Responding to search for Ground Floor
DEBUG:root:Responding to search for First Floor
DEBUG:root:Responding to search for Hot Water
DEBUG:root:Responding to search for Ground Floor
DEBUG:root:Responding to search for First Floor
DEBUG:root:Responding to search for Hot Water
DEBUG:root:Responding to search for Ground Floor
DEBUG:root:Responding to search for First Floor
DEBUG:root:Responding to search for Hot Water
DEBUG:root:Responding to search for Ground Floor
DEBUG:root:Responding to search for First Floor
DEBUG:root:Responding to search for Hot Water
DEBUG:root:Responding to search for Ground Floor
DEBUG:root:Responding to search for First Floor
DEBUG:root:Responding to search for Hot Water
DEBUG:root:Responding to search for Ground Floor
DEBUG:root:Responding to setup.xml for First Floor
DEBUG:root:GET /setup.xml HTTP/1.1
Host: 192.168.99.2:52001
Accept: */*
Content-Type: application/json
DEBUG:root:Responding to search for First Floor
DEBUG:root:Responding to search for Hot Water
DEBUG:root:Responding to search for Ground Floor
DEBUG:root:Responding to search for First Floor
DEBUG:root:Responding to search for Hot Water
DEBUG:root:Responding to search for Ground Floor
DEBUG:root:Responding to setup.xml for Hot Water
DEBUG:root:GET /setup.xml HTTP/1.1
Host: 192.168.99.2:52002
Accept: */*
Content-Type: application/json
DEBUG:root:Responding to setup.xml for Ground Floor
DEBUG:root:GET /setup.xml HTTP/1.1
Host: 192.168.99.2:52000
Accept: */*
Content-Type: application/json
Tried it with the 8266 disconnected ?
Yes, and still trying to send command to eap8266 even esp doesn’t have same name and it same result even after removing it from alexa app
reboot the echo and see if that helps
@twa127 after removing all devices, and rebooting echo still the same
DEBUG:root:Responding to ON for Ground Floor
State True on Ground Floor from client @ 192.168.99.15
DEBUG:root:Responding to search for First Floor
DEBUG:root:Responding to search for Hot Water
DEBUG:root:Responding to search for Ground Floor
DEBUG:root:Responding to search for First Floor
DEBUG:root:Responding to search for Hot Water
DEBUG:root:Responding to search for Ground Floor
DEBUG:root:Responding to search for First Floor
DEBUG:root:Responding to search for Hot Water
DEBUG:root:Responding to search for Ground Floor
DEBUG:root:Responding to search for First Floor
DEBUG:root:Responding to search for Hot Water
DEBUG:root:Responding to search for Ground Floor
DEBUG:root:Responding to setup.xml for First Floor
DEBUG:root:GET /setup.xml HTTP/1.1
Host: 192.168.99.2:52001
Accept: */*
Content-Type: application/json
DEBUG:root:Responding to search for First Floor
DEBUG:root:Responding to search for Hot Water
DEBUG:root:Responding to search for Ground Floor
DEBUG:root:Responding to search for First Floor
DEBUG:root:Responding to search for Hot Water
DEBUG:root:Responding to search for Ground Floor
DEBUG:root:Responding to setup.xml for Hot Water
DEBUG:root:GET /setup.xml HTTP/1.1
Host: 192.168.99.2:52002
Accept: */*
Content-Type: application/json
DEBUG:root:Responding to setup.xml for Ground Floor
DEBUG:root:GET /setup.xml HTTP/1.1
Host: 192.168.99.2:52000
Accept: */*
Content-Type: application/json
I've added the code to get the boost state back to the echo fauxmo.zip
@twa127 for some reason its still looking for that ip even that esp8266 have new ip after reboot and its not discovering esp anymore and all PiHome devices are found after removing them and re scanning. dont know where from this 192.168.99.15 is coming
`root@pihome:~# sudo /usr/bin/python /var/www/amazon_echo/echo_pihome.py DEBUG:root:Listening for UPnP broadcasts DEBUG:root:got local address of 192.168.99.2 DEBUG:root:UPnP broadcast listener: new device registered DEBUG:root:FauxMo device 'First Floor' ready on 192.168.99.2:52001 DEBUG:root:UPnP broadcast listener: new device registered DEBUG:root:FauxMo device 'Hot Water' ready on 192.168.99.2:52002 DEBUG:root:UPnP broadcast listener: new device registered DEBUG:root:FauxMo device 'Ground Floor' ready on 192.168.99.2:52000 DEBUG:root:Entering fauxmo polling loop DEBUG:root:Responding to search for First Floor DEBUG:root:Responding to search for Hot Water DEBUG:root:Responding to search for Ground Floor DEBUG:root:Responding to search for First Floor DEBUG:root:Responding to search for Hot Water DEBUG:root:Responding to search for Ground Floor DEBUG:root:Responding to search for First Floor DEBUG:root:Responding to search for Hot Water DEBUG:root:Responding to search for Ground Floor DEBUG:root:Responding to setup.xml for First Floor DEBUG:root:GET /setup.xml HTTP/1.1 Host: 192.168.99.2:52001 Accept: / Content-Type: application/json
DEBUG:root:Responding to search for First Floor DEBUG:root:Responding to search for Hot Water DEBUG:root:Responding to search for Ground Floor DEBUG:root:Responding to search for First Floor DEBUG:root:Responding to search for Hot Water DEBUG:root:Responding to search for Ground Floor DEBUG:root:Responding to setup.xml for Hot Water DEBUG:root:GET /setup.xml HTTP/1.1 Host: 192.168.99.2:52002 Accept: / Content-Type: application/json
DEBUG:root:Responding to search for First Floor DEBUG:root:Responding to search for Hot Water DEBUG:root:Responding to search for Ground Floor DEBUG:root:Responding to setup.xml for Ground Floor DEBUG:root:GET /setup.xml HTTP/1.1 Host: 192.168.99.2:52000 Accept: / Content-Type: application/json
DEBUG:root:Responding to GetBinaryState DEBUG:root:State: 0 DEBUG:root:Responding to GetBinaryState DEBUG:root:State: 0 DEBUG:root:Responding to GetBinaryState DEBUG:root:State: 1 DEBUG:root:Responding to GetBinaryState DEBUG:root:State: 0 DEBUG:root:Responding to GetBinaryState DEBUG:root:State: 0 DEBUG:root:Responding to GetBinaryState DEBUG:root:State: 1 DEBUG:root:Responding to ON for Ground Floor State True on Ground Floor from client @ 192.168.99.15 DEBUG:root:Responding to search for First Floor DEBUG:root:Responding to search for Hot Water DEBUG:root:Responding to search for Ground Floor DEBUG:root:Responding to search for First Floor DEBUG:root:Responding to search for Hot Water DEBUG:root:Responding to search for Ground Floor DEBUG:root:Responding to search for First Floor DEBUG:root:Responding to search for Hot Water DEBUG:root:Responding to search for Ground Floor DEBUG:root:Responding to search for First Floor DEBUG:root:Responding to search for Hot Water DEBUG:root:Responding to search for Ground Floor DEBUG:root:Responding to setup.xml for First Floor DEBUG:root:GET /setup.xml HTTP/1.1 Host: 192.168.99.2:52001 Accept: / Content-Type: application/json
DEBUG:root:Responding to search for First Floor DEBUG:root:Responding to search for Hot Water DEBUG:root:Responding to search for Ground Floor DEBUG:root:Responding to search for First Floor DEBUG:root:Responding to search for Hot Water DEBUG:root:Responding to search for Ground Floor DEBUG:root:Responding to setup.xml for Hot Water DEBUG:root:GET /setup.xml HTTP/1.1 Host: 192.168.99.2:52002 Accept: / Content-Type: application/json
DEBUG:root:Responding to setup.xml for Ground Floor DEBUG:root:GET /setup.xml HTTP/1.1 Host: 192.168.99.2:52000 Accept: / Content-Type: application/json
DEBUG:root:Responding to ON for First Floor State True on First Floor from client @ 192.168.99.15 DEBUG:root:Responding to ON for Hot Water State True on Hot Water from client @ 192.168.99.15 DEBUG:root:Responding to OFF for Ground Floor State False on Ground Floor from client @ 192.168.99.15 DEBUG:root:Responding to search for First Floor DEBUG:root:Responding to search for Hot Water DEBUG:root:Responding to search for Ground Floor DEBUG:root:Responding to search for First Floor DEBUG:root:Responding to search for Hot Water DEBUG:root:Responding to search for Ground Floor DEBUG:root:Responding to search for First Floor DEBUG:root:Responding to search for Hot Water DEBUG:root:Responding to search for Ground Floor DEBUG:root:Responding to search for First Floor DEBUG:root:Responding to search for Hot Water DEBUG:root:Responding to search for Ground Floor DEBUG:root:Responding to setup.xml for First Floor DEBUG:root:GET /setup.xml HTTP/1.1 Host: 192.168.99.2:52001 Accept: / Content-Type: application/json
DEBUG:root:Responding to search for First Floor DEBUG:root:Responding to search for Hot Water DEBUG:root:Responding to search for Ground Floor DEBUG:root:Responding to search for First Floor DEBUG:root:Responding to search for Hot Water DEBUG:root:Responding to search for Ground Floor DEBUG:root:Responding to setup.xml for Hot Water DEBUG:root:GET /setup.xml HTTP/1.1 Host: 192.168.99.2:52002 Accept: / Content-Type: application/json
DEBUG:root:Responding to setup.xml for Ground Floor DEBUG:root:GET /setup.xml HTTP/1.1 Host: 192.168.99.2:52000 Accept: / Content-Type: application/json
DEBUG:root:Responding to OFF for First Floor State False on First Floor from client @ 192.168.99.15 DEBUG:root:Responding to OFF for Hot Water State False on Hot Water from client @ 192.168.99.15 DEBUG:root:Responding to search for First Floor DEBUG:root:Responding to search for Hot Water DEBUG:root:Responding to search for Ground Floor DEBUG:root:Responding to search for First Floor DEBUG:root:Responding to search for Hot Water DEBUG:root:Responding to search for Ground Floor DEBUG:root:Responding to search for First Floor DEBUG:root:Responding to search for Hot Water DEBUG:root:Responding to search for Ground Floor DEBUG:root:Responding to search for First Floor DEBUG:root:Responding to search for Hot Water DEBUG:root:Responding to search for Ground Floor DEBUG:root:Responding to setup.xml for First Floor DEBUG:root:GET /setup.xml HTTP/1.1 Host: 192.168.99.2:52001 Accept: / Content-Type: application/json
DEBUG:root:Responding to search for First Floor DEBUG:root:Responding to search for Hot Water DEBUG:root:Responding to search for Ground Floor DEBUG:root:Responding to search for First Floor DEBUG:root:Responding to search for Hot Water DEBUG:root:Responding to search for Ground Floor DEBUG:root:Responding to setup.xml for Hot Water DEBUG:root:GET /setup.xml HTTP/1.1 Host: 192.168.99.2:52002 Accept: / Content-Type: application/json
DEBUG:root:Responding to setup.xml for Ground Floor DEBUG:root:GET /setup.xml HTTP/1.1 Host: 192.168.99.2:52000 Accept: / Content-Type: application/json
DEBUG:root:Responding to GetBinaryState DEBUG:root:State: 0 DEBUG:root:Responding to GetBinaryState DEBUG:root:State: 0 DEBUG:root:Responding to GetBinaryState DEBUG:root:State: 0 DEBUG:root:Responding to search for First Floor DEBUG:root:Responding to search for Hot Water DEBUG:root:Responding to search for Ground Floor DEBUG:root:Responding to search for First Floor DEBUG:root:Responding to search for Hot Water DEBUG:root:Responding to search for Ground Floor DEBUG:root:Responding to search for First Floor DEBUG:root:Responding to search for Hot Water DEBUG:root:Responding to search for Ground Floor DEBUG:root:Responding to search for First Floor DEBUG:root:Responding to search for Hot Water DEBUG:root:Responding to search for Ground Floor DEBUG:root:Responding to setup.xml for First Floor DEBUG:root:GET /setup.xml HTTP/1.1 Host: 192.168.99.2:52001 Accept: / Content-Type: application/json
DEBUG:root:Responding to search for First Floor DEBUG:root:Responding to search for Hot Water DEBUG:root:Responding to search for Ground Floor DEBUG:root:Responding to search for First Floor DEBUG:root:Responding to search for Hot Water DEBUG:root:Responding to search for Ground Floor DEBUG:root:Responding to setup.xml for Hot Water DEBUG:root:GET /setup.xml HTTP/1.1 Host: 192.168.99.2:52002 Accept: / Content-Type: application/json
DEBUG:root:Responding to setup.xml for Ground Floor DEBUG:root:GET /setup.xml HTTP/1.1 Host: 192.168.99.2:52000 Accept: / Content-Type: application/json
DEBUG:root:Responding to GetBinaryState
DEBUG:root:State: 0
DEBUG:root:Responding to GetBinaryState
DEBUG:root:State: 0
DEBUG:root:Responding to GetBinaryState
DEBUG:root:State: 0
^CTraceback (most recent call last):
File "/var/www/amazon_echo/echo_pihome.py", line 97, in
The 192.168.99.15 is the address of the Echo
School boy error. 🤪 i had my echo reset to factory default as it was driving me crazy, i will setup again and let you know, but before reset boost worked but witj same voice message of not responding
here is complete log after factory resting echo, bost worked for hot water but device not responding voice message, same for turning off boost but again voice message device not responding.
root@pihome:~# sudo /usr/bin/python /var/www/amazon_echo/echo_pihome.py
DEBUG:root:Listening for UPnP broadcasts
DEBUG:root:got local address of 192.168.99.2
DEBUG:root:UPnP broadcast listener: new device registered
DEBUG:root:FauxMo device 'First Floor' ready on 192.168.99.2:52001
DEBUG:root:UPnP broadcast listener: new device registered
DEBUG:root:FauxMo device 'Hot Water' ready on 192.168.99.2:52002
DEBUG:root:UPnP broadcast listener: new device registered
DEBUG:root:FauxMo device 'Ground Floor' ready on 192.168.99.2:52000
DEBUG:root:Entering fauxmo polling loop
DEBUG:root:Responding to search for First Floor
DEBUG:root:Responding to search for Hot Water
DEBUG:root:Responding to search for Ground Floor
DEBUG:root:Responding to search for First Floor
DEBUG:root:Responding to search for Hot Water
DEBUG:root:Responding to search for Ground Floor
DEBUG:root:Responding to search for First Floor
DEBUG:root:Responding to search for Hot Water
DEBUG:root:Responding to search for Ground Floor
DEBUG:root:Responding to setup.xml for First Floor
DEBUG:root:GET /setup.xml HTTP/1.1
Host: 192.168.99.2:52001
Accept: */*
Content-Type: application/json
DEBUG:root:Responding to search for First Floor
DEBUG:root:Responding to search for Hot Water
DEBUG:root:Responding to search for Ground Floor
DEBUG:root:Responding to search for First Floor
DEBUG:root:Responding to search for Hot Water
DEBUG:root:Responding to search for Ground Floor
DEBUG:root:Responding to setup.xml for Hot Water
DEBUG:root:GET /setup.xml HTTP/1.1
Host: 192.168.99.2:52002
Accept: */*
Content-Type: application/json
DEBUG:root:Responding to search for First Floor
DEBUG:root:Responding to search for Hot Water
DEBUG:root:Responding to search for Ground Floor
DEBUG:root:Responding to setup.xml for Ground Floor
DEBUG:root:GET /setup.xml HTTP/1.1
Host: 192.168.99.2:52000
Accept: */*
Content-Type: application/json
DEBUG:root:Responding to GetBinaryState
DEBUG:root:State: 0
DEBUG:root:Responding to GetBinaryState
DEBUG:root:State: 0
DEBUG:root:Responding to GetBinaryState
DEBUG:root:State: 0
DEBUG:root:Responding to GetBinaryState
DEBUG:root:State: 0
DEBUG:root:Responding to GetBinaryState
DEBUG:root:State: 0
DEBUG:root:Responding to GetBinaryState
DEBUG:root:State: 0
DEBUG:root:Responding to ON for Hot Water
State True on Hot Water from client @ 192.168.99.15
DEBUG:root:Responding to search for First Floor
DEBUG:root:Responding to search for Hot Water
DEBUG:root:Responding to search for Ground Floor
DEBUG:root:Responding to search for First Floor
DEBUG:root:Responding to search for Hot Water
DEBUG:root:Responding to search for Ground Floor
DEBUG:root:Responding to search for First Floor
DEBUG:root:Responding to search for Hot Water
DEBUG:root:Responding to search for Ground Floor
DEBUG:root:Responding to search for First Floor
DEBUG:root:Responding to search for Hot Water
DEBUG:root:Responding to search for Ground Floor
DEBUG:root:Responding to setup.xml for First Floor
DEBUG:root:GET /setup.xml HTTP/1.1
Host: 192.168.99.2:52001
Accept: */*
Content-Type: application/json
DEBUG:root:Responding to search for First Floor
DEBUG:root:Responding to search for Hot Water
DEBUG:root:Responding to search for Ground Floor
DEBUG:root:Responding to search for First Floor
DEBUG:root:Responding to search for Hot Water
DEBUG:root:Responding to search for Ground Floor
DEBUG:root:Responding to setup.xml for Hot Water
DEBUG:root:GET /setup.xml HTTP/1.1
Host: 192.168.99.2:52002
Accept: */*
Content-Type: application/json
DEBUG:root:Responding to setup.xml for Ground Floor
DEBUG:root:GET /setup.xml HTTP/1.1
Host: 192.168.99.2:52000
Accept: */*
Content-Type: application/json
my Echo comes back with 'Okay' to turn ON and OFF
this is again 2nd generation and 3rd generation compatibility issue.
guess so, can you check if the WeMos Mini version gives the correct voice response
I think I can see a solution, I'll let you know
Please try this fauxmo.zip
@twa127 waoo man, that worked perfect.
may be stupid question: device description are set to Belkin International Inc. smart device, can this be changed or it has to be this name?
I think so, I'm guessing there is some string matching at the Echo end
Ended up not being much of a change from the original code, the broadcast packed from the later versions are different and the implementation of the SOAP response was too simple. I guess my older Echo is not too fussy :-)
@twa127 service stops after some time and looks like connection to sql isnt valid or disconnected. see service status below.
root@pihome:~# sudo systemctl status pihome_amazon_echo.service
● pihome_amazon_echo.service - Echo
Loaded: loaded (/lib/systemd/system/pihome_amazon_echo.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Mon 2020-03-30 12:52:24 BST; 22min ago
Process: 729 ExecStart=/usr/bin/python /var/www/amazon_echo/echo_pihome.py (code=exited, status=0/SUCCESS)
Main PID: 729 (code=exited, status=0/SUCCESS)
Mar 30 11:32:35 pihome python[729]: DEBUG:root:Responding to search for Ground Floor
Mar 30 11:32:36 pihome python[729]: DEBUG:root:Responding to search for First Floor
Mar 30 11:32:37 pihome python[729]: DEBUG:root:Responding to search for Hot Water
Mar 30 11:32:37 pihome python[729]: DEBUG:root:Responding to search for Ground Floor
Mar 30 11:32:38 pihome python[729]: DEBUG:root:Responding to search for First Floor
Mar 30 11:32:38 pihome python[729]: DEBUG:root:Responding to search for Hot Water
Mar 30 11:32:39 pihome python[729]: DEBUG:root:Responding to search for Ground Floor
Mar 30 12:52:24 pihome python[729]: DEBUG:root:Responding to GetBinaryState
Mar 30 12:52:24 pihome python[729]: CRITICAL:root:Critical exception: (2006, 'MySQL server has gone away')
Mar 30 12:52:24 pihome systemd[1]: pihome_amazon_echo.service: Succeeded.
Yes I saw the same thing, testing a fix now
Sent from my iPhone
On 30 Mar 2020, at 13:17, PiHomeHVAC notifications@github.com wrote:
@twa127 service stops after some time and looks like connection to sql isnt valid or disconnected. see service status below.
root@pihome:~# sudo systemctl status pihome_amazon_echo.service ● pihome_amazon_echo.service - Echo Loaded: loaded (/lib/systemd/system/pihome_amazon_echo.service; enabled; vendor preset: enabled) Active: inactive (dead) since Mon 2020-03-30 12:52:24 BST; 22min ago Process: 729 ExecStart=/usr/bin/python /var/www/amazon_echo/echo_pihome.py (code=exited, status=0/SUCCESS) Main PID: 729 (code=exited, status=0/SUCCESS)
Mar 30 11:32:35 pihome python[729]: DEBUG:root:Responding to search for Ground Floor Mar 30 11:32:36 pihome python[729]: DEBUG:root:Responding to search for First Floor Mar 30 11:32:37 pihome python[729]: DEBUG:root:Responding to search for Hot Water Mar 30 11:32:37 pihome python[729]: DEBUG:root:Responding to search for Ground Floor Mar 30 11:32:38 pihome python[729]: DEBUG:root:Responding to search for First Floor Mar 30 11:32:38 pihome python[729]: DEBUG:root:Responding to search for Hot Water Mar 30 11:32:39 pihome python[729]: DEBUG:root:Responding to search for Ground Floor Mar 30 12:52:24 pihome python[729]: DEBUG:root:Responding to GetBinaryState Mar 30 12:52:24 pihome python[729]: CRITICAL:root:Critical exception: (2006, 'MySQL server has gone away') Mar 30 12:52:24 pihome systemd[1]: pihome_amazon_echo.service: Succeeded.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.
Recently bought Amazon Echo for kids to give me option to interact with voice control for some learning, so far kids happy asking questions but it got me thinking to what it takes to implement voice commands for PiHome. any one have any experience in voice command with Google Home and Amazon Echo?