[RELEASE] Echo Speaks


#343

@tonesto7: Getting this with my oldest Echo Dot on latest HE firmware:

2019-06-10 04:24:20.900 pm errorjava.io.IOException: Block not found in id [1, -17, 23, -40, -7, -4, 1] [1.4.199/50] (devVersion)


#344

I just installed Echo Speaks today. Great app! But I'm seeing this in my logs and I'm not sure if it's significant or not. The discussion above about hubs slowing down is a little concerning. I notice that it seems to happen when I've selected more than 3 Echo devices.


#346

Would I need another Heroku account or will the one I have for Smartthings do the job?


#347

I believe you only need one Heroku account.


#348

So loading the app and driver is all that is needed or is there more involved?


#349

So lots of errors in the log, things seem to be working fine however

Thoughts?

Rick


#350

amazon has been returning an empty or no response occasionally. Are you running the latest version of the code.


#351

Good morning @tonesto7

Thanks for the suggestion to check the version. I didn't install all that long ago and since things were working, I didn't think to check before posting. I just updated and will check the logs and see what transpires

Thanks
Rick


#352

Can you help me understand this line?

try { } catch(ex) { log.error "wakeUpServerResp Error: ${response?.getErrorMessage() ?: null}" }

It results in the constant error message in the logs

java.lang.Exception: No response data exists for async request on line 1096 (wakeUpServerResp)

You're not catching anything here, so I'm not sure what's intended.

EDIT: Actually, it's this line resulting in the exception

def rData = response?.data ?: null


#353

Tony, can you clear up for me what the latest version is? In Post#1 of this thread, it says 2.4.0. But my Smartthings IDE has 2.5.0. Don't you use a common code base for both platforms? Should I copy the ST code into Hubitat? Thank you.


#354

Also this in the device now.

errorjava.lang.Exception: No response data exists for async request on line 2517 (asyncSpeechHandler)


#355

Still getting errors after upgrading to the current versions

Rick


#356

It's 2.5.0. Look in the code itself.


#357

Here's an update. I loaded the latest version of Echo Speaks a couple of days ago and it seemed to be working well until around 3:00 AM this morning. Here are the log files. It was suspiciously around the time that my hub blew up last week:



This happened across 9 of my echo devices:

I've now trimmed down the list to the 2 devices I use. The only reason is so I can play the traffic on one and the weather on another.


#358

Was this rename problem ever figured out? I have a bunch of different Echo devices that I have renamed in the Alexa app and Echo Speaks seem to try and rename it (says so in the logs), but they never get renamed.


#359

After a few days of having just two out of the nine devices installed, I have not seen one error in my log files. My hub seems very responsive and my announcements seem to be working just fine. Those are including the rules for playTraffic and playWeather.


#360

Getting this in my logs now Only one echo is working now out of 5.

dev:18962019-06-18 03:42:33.558 pm errorgroovy.json.JsonException: Unable to determine the current character, it is not a string, number, array, or object

The current character read is 'H' with an int value of 72
Unable to determine the current character, it is not a string, number, array, or object
line number 1
index number 0
HTTP/1.1 0 x-amzn-RequestId: f2f1e2bd-17bb-4228-b44a-91ff1e6263eb
^ on line 1135 (amazonCommandResp)
dev:18962019-06-18 03:42:29.121 pm warnAmazon Cookie State Values Missing

Now I can't get the session login to work. Loging into Amazon just loops and not saving the session info.

Using 2.5.0 of the app.

Update: Heroku app no longer captures alexa login cookie. Even a manual cookie doesn't work. I think Amazon changed its featureaccess cookie value.


#361

@tonesto7, App no longer works. Throwing a whole bunch of errors in the logs.

app:1372019-06-18 08:43:17.417 pm errorgroovy.json.JsonException: Unable to determine the current character, it is not a string, number, array, or object The current character read is 'H' with an int value of 72 Unable to determine the current character, it is not a string, number, array, or object line number 1 index number 0 HTTP/1.1 0 x-amzn-RequestId: 2b6fac2c-755c-43f8-9624-7b0476abc8e1 ^ on line 1700 (amazonCommandResp)

dev:1342019-06-18 08:39:44.169 pm warnAmazon Cookie State Values Missing: [cookie:session-id=143-7035812-7867627; session-id-time=2191624347l; ubid-main=131-0491031-5060562; x-main="VLyydlsl8R0ZCQAEY5Hq1LQt8xsm12Ip"; at-main="Atza|IwEBII1l542p-WRDOZa_kcmkjQmSsdoAwRi2D02_VCsvisV0nRJ0_9aBuFKHrzVpuZVoXVDvR1kFEASQEe_SK43S3Ni39iKqXRvsXK210eLbD74D0e4St5x2V1LpJHQ9E7BRcqBBGbLFLLP9ETt_HcwOuEZbHMRQAUyLFRBfhYj8ioSCmX8voRzzCpGHbtmiPfWvEBXMAobhzMQDu8WqbZuiclnL4gKu-h878Xod62yzEOG3GO4lt-X7A8Pzy-kp6Vs-ldqe90WyLoREhXCXHkT5IwIwKHhJYjesQaG0iZOmn4Ec6CNdDO1i8w4irfnHr-6o0NpDpeQLC9OUCuK5NBzzVBGo3vAVOmwmSLFp6dgIzHFAs6VxsFHSkaajZO4hmhvussgaUwZzQKDx8Pr00hk8GKVF7azXVNb4Bn_b3BSMtGp3FYvfuYAzdD0RPlB1-orBELro7M13rzAWkRtvWaTu4UUE"; sess-at-main="saPrijf+2fHY4sfcDr6O5X9vLFhj5ZoXxv/1UFKnrv4=", csrf:null]

Update: Amazon login no longer works on Heroku.


#362

Yup, something is definitely hosed. None of my Echo Dots are working and I'm getting multiple errors in my logs.


#363

@tonesto7 There are 2 errors happening that's causing errors.

1st one is the cookie format has changed and 2nd one is a error posting to the hub endpoint.... Heroku logs below.

2019-06-19T01:11:56.655931+00:00 heroku[router]: at=info method=POST path="/proxy/www.amazon.com/ap/signin" host=echo-speaks-XXXXXX.herokuapp.com request_id=6717e711-fb0d-4f0e-a015-bb40616866db fwd="XXXXXX-IP" dyno=web.1 connect=8ms service=976ms status=302 bytes=2699 protocol=https
2019-06-19T01:11:57.811539+00:00 app[web.1]: 6-19-2019 - 1:11:57am debug: 	Alexa Login Status: There was an error getting authentication
2019-06-19T01:12:01.903864+00:00 heroku[router]: at=info method=GET path="/config" host=echo-speaks-XXXXXX.herokuapp.com request_id=09e9a504-6858-442f-a8b9-d608b09ba1ef fwd="XXXXXX-IP" dyno=web.1 connect=1ms service=13ms status=304 bytes=348 protocol=https
2019-06-19T01:12:01.895232+00:00 app[web.1]: 6-19-2019 - 1:12:01am debug: 	/config page requested
2019-06-19T01:12:02.172071+00:00 heroku[router]: at=info method=GET path="/configData" host=echo-speaks-XXXXX.herokuapp.com request_id=adbb28be-2914-420d-bc0c-e8374dd3bb4e fwd="XXXXXXXX-IP" dyno=web.1 connect=1ms service=4ms status=304 bytes=261 protocol=https
2019-06-19T01:12:07.847728+00:00 app[web.1]: 6-19-2019 - 1:12:07am info: 	** ServerVersion Sent to Hubitat Cloud Endpoint Successfully! **
2019-06-19T01:12:07.863696+00:00 app[web.1]: 6-19-2019 - 1:12:07am error: 	ERROR: Unable to send Alexa Cookie Data to Hubitat: 504 - "No response from hub"
2019-06-19T01:12:08.044203+00:00 app[web.1]: 6-19-2019 - 1:12:08am error: 	generateAlexaCookie: You can try to get the cookie manually by opening https://echo-speaks-XXXXXXX.herokuapp.com/ with your browser.
2019-06-19T01:12:08.044660+00:00 app[web.1]: 6-19-2019 - 1:12:08am debug: 	Alexa Login Status: There was an error
2019-06-19T01:12:08.508684+00:00 app[web.1]: 6-19-2019 - 1:12:08am info: 	** ServerVersion Sent to Hubitat Cloud Endpoint Successfully! **
2019-06-19T01:18:16.370380+00:00 app[web.1]: 6-19-2019 - 1:18:16am debug: 	/config page requested