FYI.. I'm on the docker server for cookie management. I don't know if that is part of it. I'm going to go back over to the original deployment method. I just haven't done so.
However, I'm getting these error messages.
app:36922022-09-09 04:06:34.022 pmerrorEchoApp (v4.2.0.7) | wakeupServerResp Exception: java.lang.Exception: No response data exists for async request
app:36922022-09-09 04:06:34.018 pmerrorEchoApp (v4.2.0.7) | wakeupServerResp | Stack Trace: java.lang.Exception: No response data exists for async request
at hubitat.scheduling.AsyncResponse.getData(AsyncResponse.groovy:71)
at user_app_tonesto7_Echo_Speaks_1655.wakeupServerResp(user_app_tonesto7_Echo_Speaks_1655.groovy:2226)
app:36922022-09-09 04:06:33.989 pmerrorEchoApp (v4.2.0.7) | wakeupServerResp Server may be down / unreachable
app:36922022-09-09 03:51:33.806 pmerrorEchoApp (v4.2.0.7) | wakeupServerResp Exception: java.lang.Exception: No response data exists for async request
app:36922022-09-09 03:51:33.802 pmerrorEchoApp (v4.2.0.7) | wakeupServerResp | Stack Trace: java.lang.Exception: No response data exists for async request
at hubitat.scheduling.AsyncResponse.getData(AsyncResponse.groovy:71)
at user_app_tonesto7_Echo_Speaks_1655.wakeupServerResp(user_app_tonesto7_Echo_Speaks_1655.groovy:2226)
app:36922022-09-09 03:51:33.775 pmerrorEchoApp (v4.2.0.7) | wakeupServerResp Server may be down / unreachable
app:36922022-09-09 03:36:33.747 pmerrorEchoApp (v4.2.0.7) | wakeupServerResp Exception: java.lang.Exception: No response data exists for async request
app:36922022-09-09 03:36:33.743 pmerrorEchoApp (v4.2.0.7) | wakeupServerResp | Stack Trace: java.lang.Exception: No response data exists for async request
at hubitat.scheduling.AsyncResponse.getData(AsyncResponse.groovy:71)
at user_app_tonesto7_Echo_Speaks_1655.wakeupServerResp(user_app_tonesto7_Echo_Speaks_1655.groovy:2226)
For my setup, this happens when echo speaks on hubitat can't get to the echo-speaks-server - of course there are several reasons why the server isn't working. I think one cause is the server was rebooted but the hubitat side still has an connection and hasn't closed it on failure.
@tonesto7 I have flipped back to Heroku. Because I have been seeing some issues Announcements was working on ECOBEE devices started see this error in the event logs
So, I have reset and rebuilt the app again (redeployed). I'm noticing with the new Google Browser this prevents the cookie from being captured correctly. This is a built-in alert from the browser. I used Edge Chrome (private Mode) and worked like a champ. (Note I still see errors in the browser log, but I don't know if it was from getting all the browser issues worked out.)
However, I am seeing from the test page that should allow to test individual devices it now doesn't allow for that. Device options are missing. I'm using 2.3.3.113 moving 2.3.3.114
I am struggling pretty bad with getting local server set up on Pi. I've been bouncing all over here and Google trying to get a fresh install of Debian Bullseye working for me but I keep hitting road block after road block. Wrong dependencies....outdated.....wrong paths....it's a mess. Can anyone help?
By fresh install I assume you used the Raspberry Pi Imager with an official image, I prefer the 64 bit image now over 32 bit. As for running the local server docker image that I posted above just seems to work. I did a second test on a Synolgoy NAS with it on my development hub and it seems to be stable also.
Do the docker install then install docker-compose, Unzip the github project into a directory, edit the start.sh file to have the "static" ip address of your Pi and then follow the server instructions in the Echo Speaks Hubitat app.
Two weeks up and running with a couple of reboots due to updating raspberry pi's kernel and other security updates. The container has been rock solid, and my speak and music request to various Echo's has been flawless when making the request from the Hubitat.
I was able to capture the logs from the Docker container for a "cookie" refresh:
9-17-2022 - 10:14:13pm info: Server Wakeup Received | Reason: (runCookieRefresh)
9-17-2022 - 10:14:15pm verbose: refreshCookie request received
9-17-2022 - 10:14:15pm debug: cookieData: [object Object]
9-17-2022 - 10:14:18pm info: Successfully Refreshed Alexa Cookie...
9-17-2022 - 10:14:19pm info: ** Alexa Cookie Data sent to Hubitat Cloud Endpoint Successfully! **
9-17-2022 - 10:14:42pm warn: Restarting after cookie refresh attempt
clean
1
graceful setting timeout for PID: 1
9-17-2022 - 10:14:45pm info: -- Echo Speaks Web Service Starting Up! Takes about 10 seconds before it's available... --
getRemoteCookie...
9-17-2022 - 10:14:45pm info: ** Echo Speaks Config Service (v2.7.2) is Running at (IP: 192.168.20.251 | Port: 8091) | ProcessId: 1 **
9-17-2022 - 10:14:45pm info: ** On Heroku: (false) **
9-17-2022 - 10:14:45pm info: Checking for Server Version Updates...
9-17-2022 - 10:14:45pm info: ** Retrieved Alexa Cookie Data from Hubitat Cloud Endpoint Successfully! **
9-17-2022 - 10:14:46pm info: ** Alexa Cookie Data Received from Hubitat Cloud Endpoint has been Confirmed to be Valid! **
9-17-2022 - 10:14:46pm debug: Alexa Login Status: Login Successful (Retreived from Hubitat)
9-17-2022 - 10:14:46pm silly: Echo Speaks Alexa API is Actively Running at (IP: 192.168.20.251 | Port: 8091) | ProcessId: 1
9-17-2022 - 10:14:46pm error: AlexaGuardDataSupport | No Alexa Guard Appliance Data found...
9-17-2022 - 10:14:46pm info: ** ServerVersion Sent to Hubitat Cloud Endpoint Successfully! **
9-17-2022 - 10:14:46pm info: Server Version is Up-to-Date.
9-18-2022 - 10:24:36pm info: Server Wakeup Received | Reason: (healthCheck)
I see most people are using Raspberry PI, with whatever flavor of Linux. I have a number of BSD servers. One is running Node.js and Node Red. Is there a server version that will run on BSD? I don't really want to get into a bunch of linux compatibility stuff on my BSD boxes.
You don't even need to run Docker if you don't want to. It's all JS. The only trick might be launching it on boot, but look to see what Node Red does to launch and you're almost done.
How did you get this running on your QNAP? I have container station open but not seeing echo server pull up under the \Create\Docker Hub\ section. At least I'm not seeing which image you are using there. Thanks.
Well if anyone has this working on a QNAP via Container Station, please let me know.
@tonesto7 hasn’t released the local docker container yet so not running it yet. I do run NodeRed, InfluxDB, Grafana, and AlexaTTS in QNAP Container Station today. Once the Echo Speaks container is released I will give it a try.
Hey everyone - I just read through this thread about Heroku going paid. I have a rPI running Homebridge that I could rather easily use to also run a local AS server but I have learned to listen to the more experienced creators of apps like @tonesto7 so I am staying the course with Heroku until he releases the Uber fix he promised. I will add $7 to my prior contribution and encourage others to do so too so he is rewarded for the excellent work he has done and will do for our smart homes. I am convinced this is the best way to keep my Alexa speaks solution working trouble free. As for Heroku, I think their move to a fee structure is a desperation play because the economy is in the toilet.
.
I understand that Heroku was bought by Salesforce so possibly just a businessing up with less concern for students and hobbyists.
Possibly short-sighted because student users become knowledgeable fans and bring their experience and enthusiasm to their eventual employers - but I digress again.
