[RELEASE] Echo Speaks V4

Ranger_Shack · July 24, 2023, 1:15am

Everyone should know,, you have to enter a credit card for this.
As it is not "free" cheap but not free.

jtp10181 · July 24, 2023, 1:28am

Its free if you host your own cookie server: [GUIDE] Echo Speaks Server on Docker (or without)

terminal3 · July 24, 2023, 1:28am

If you are referring to the Heroku service then there are quite a few post about that. It use to be free,but they started charging back in Nov of last year.

This app is free if you use your own a local server, as I do and many others. There are a number of post about how to do that as well.

Ranger_Shack · July 24, 2023, 1:41am

Yes that is what I was speaking of.
Thanks.

jbaruch · July 25, 2023, 3:26am

I see tons of errors in the logs out of the blue (running vanilla service on Heroku).

It started with 408 errors on cookie refresh (for 2 weeks now), and today I also got this:

app:682023-07-24 10:24:20.656 PMerrorEchoApp (v4.2.2.0) | wakeupServerResp Exception: java.lang.Exception: No response data exists for async request
app:682023-07-24 10:24:20.652 PMerrorEchoApp (v4.2.2.0) | 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_163.wakeupServerResp(user_app_tonesto7_Echo_Speaks_163.groovy:2228)
app:682023-07-24 10:24:20.624 PMerrorEchoApp (v4.2.2.0) | wakeupServerResp Server may be down / unreachable
app:682023-07-24 10:24:20.613 PMwarn EchoApp (v4.2.2.0) | wakeupServerResp: 503

Any ideas about what's going on?

jtp10181 · July 25, 2023, 11:58am

According to one of the devs up above those errors are from the app trying to connect with the cookie server, which is failing. Same errors were posted above and discussed.

jbaruch · July 25, 2023, 2:20pm

Thanks for the reference, @jtp10181. I saw those discussions. Most of them are about troubles people get setting up standalone servers. I use the vanilla Heroku, and the code is up to date (according to github, at least), so I am unsure how to debug the server errors.

P.S. That's why I advocated separate the threads

jkudave · July 25, 2023, 2:28pm

The 503 response indicates that your cookie server is not responding. It seems that your Heroku instance is not responding to requests.

jbaruch · July 25, 2023, 2:32pm

That's what I figured... But it looks good from what I can tell. What are the debugging procedures for it?

jkudave · July 25, 2023, 2:34pm

That actually isn't good. You should be seeing that you are logged into Amazon. You need to complete that step. Click on the Goto Login Page button and complete the steps to login to your Amazon account. Step 7 in the guide below.

jbaruch · July 25, 2023, 2:49pm

Duh, obviously, I was logged in (not sure when I logged out). I logged back in, and forced cookie refresh, but the cookie is still not refreshed:

jkudave · July 25, 2023, 2:50pm

It may take a bit for that page to refresh. You might need to exit and go back in.

jbaruch · July 25, 2023, 2:50pm

I see it trying:

jkudave · July 25, 2023, 2:53pm

If you keep getting those wakeup server response errors, you still have something going on with the Heroku side of things. It has been quite some time since I used Heroku and I no longer have an account, so I can't go and look. I would go back through the guide I posted and make sure you have everything set correctly.

jbaruch · July 25, 2023, 2:55pm

It's been working for at least a few years, so I am sure the setup is good. Heroku logs show the app crashes, and when it recovers, I am logged out (that's how I ended up not being logged in). Maybe Heroku service troubles though...

jkudave · July 25, 2023, 2:57pm

You might want to consider standing up you own cookie server. It is relatively easy to do if you have the resources and follow the guide/s posted by @jtp10181.

jbaruch · July 25, 2023, 3:02pm

The whole idea of using the vanilla Heroku server is that it's well-maintained, and automatically updated (it deploys on changes in my GitHub, which is getting synced with @tonesto7's GitHub) so I don't need to babysit it.
Well. Here are Heroku logs, BTW, if that helps?

jkudave · July 25, 2023, 3:05pm

I'm not a Heroku expert, but that log shows a 503 status, meaning the server/service is not responding - "Connection closed without response"

This is equivalent to the error you are seeing in your Hubitat logs.

You've got an issue there somewhere.

jbaruch · July 25, 2023, 3:07pm

This much I figured I am just going to re-deploy everything. Fun!

Thanks for your help, @jkudave! I'll stop flooding the thread now

jbaruch · July 25, 2023, 3:35pm

I lied about stopping the flood! I know what happened! This is going to be a valuable reply for a change!

Hub Migration Instructions!
When migrating between hubs, new hub information needs to be updated on the Heroku Settings page. In the Config Vars section, there are two settings to update with the new hub information:

The appCallbackUrl should include the UID for the new hub.
The smartThingsUrl should include the new UID and access token (I used the Maker API app to get the token).