[RELEASE] Echo Speaks


#384

Agreed with posters above. Both manual + token refresh do not function for me; US based.


#385

Definitely not working for me and Iā€™m in the US.

Neither normal login/refresh nor manual token work.


#386

Just tried mine again and not working. I'm in US.


#387

I am down in the US too.....waiting patiently for a fix. :slight_smile:
app:20592019-06-20 08:07:04.687 am errorjava.lang.IllegalArgumentException: No json exists for response on line 1116 (cookieRefreshResp)

app:20592019-06-20 08:07:04.685 am tracecookieRefreshResp...

app:20592019-06-20 08:06:46.048 am debugDevice Data Received and Updated for (2) Alexa Devices | Took: (1987ms) | Last Refreshed: (10.0 minutes)

app:20592019-06-20 08:06:34.780 am traceprocessData Received | Version: 2.2.1 | onHeroku: true | serverUrl: null

app:20592019-06-20 08:06:34.578 am tracegetCookieData() Request Received...

app:20592019-06-20 08:06:34.439 am debugwakeUpServer Completed... | Process Time: (308ms)

app:20592019-06-20 08:06:34.439 am tracewakeUpServerResp...

app:20592019-06-20 08:02:04.695 am errorjava.lang.IllegalArgumentException: No json exists for response on line 1116 (cookieRefreshResp)

app:20592019-06-20 08:02:04.688 am tracecookieRefreshResp...

app:20592019-06-20 08:01:34.784 am traceprocessData Received | Version: 2.2.1 | onHeroku: true | serverUrl: null

app:20592019-06-20 08:01:34.572 am tracegetCookieData() Request Received...

app:20592019-06-20 08:01:34.369 am debugwakeUpServer Completed... | Process Time: (278ms)

app:20592019-06-20 08:01:34.369 am tracewakeUpServerResp...

app:20592019-06-20 07:57:04.666 am errorjava.lang.IllegalArgumentException: No json exists for response on line 1116 (cookieRefreshResp)

app:20592019-06-20 07:57:04.663 am tracecookieRefreshResp...

app:20592019-06-20 07:56:46.044 am debugDevice Data Received and Updated for (2) Alexa Devices | Took: (1992ms) | Last Refreshed: (10.0 minutes)

app:20592019-06-20 07:56:34.818 am traceprocessData Received | Version: 2.2.1 | onHeroku: true | serverUrl: null

app:20592019-06-20 07:56:34.589 am tracegetCookieData() Request Received...

app:20592019-06-20 07:56:34.400 am debugwakeUpServer Completed... | Process Time: (264ms)

app:20592019-06-20 07:56:34.400 am tracewakeUpServerResp...

app:20592019-06-20 07:52:04.743 am errorjava.lang.IllegalArgumentException: No json exists for response on line 1116 (cookieRefreshResp)

app:20592019-06-20 07:52:04.736 am tracecookieRefreshResp...

app:20592019-06-20 07:51:34.908 am traceprocessData Received | Version: 2.2.1 | onHeroku: true | serverUrl: null


#388

In US. Manual cookie entry via Heroku worked for me. Needed to input both cookie and csrf values.


#389

What method did you use to get the cookie for manual entry?


#390

I used these steps: to get the cookie and the csrf value.


#392

Did you have to remove double quotes or add anything to the cookie?

Update: Disregard. The manual cookie and CSRF worked.

Update 2: So the manual entry of the cookie and CSRF was accepted and the app shows a cookie date of today, but my Echo devices are not actually announcing anything.


#393

I followed the steps of @rvrolyk and entered the cookie manually. What is the CSRF and where do we get it? Also, how will I know if it is working?


#394

After you initially copy the cookie from the browser, paste it into a text editor. The CSRF should be one of the items listed. I missed it at first.

As I posted above, even though everything seemed OK in Heroku with the manual entry and Echo Speaks shows a cookie in the app on HE, my Echo Dots are not announcing.


#395

@pcgirl, sorry I forgot to mention the CSRF. As @jkudave mentioned, it's buried in the cookie string itself (csrf=...).

I don't have any Dots but my Tap and 1st gen Echo did work last night and this morning.


#396

@rvrolyk I can see the CSRF in the data. Do I include that also in the cookie or do I just take the data up to the CSRF for the cookie? Which part of the CSRF do I enter? Just the number after CSRF=?


#397

I used the entire cookie string and it seemed to work.
For the CSRF you just want the number after the =


#398

I think it worked because my Echos are showing in the log now. Not sure if they are working though as I am not at home.


#399

Mine show too, but are not working.


#400

I got all that but non of my echos are speaking.

The only app that's working with the cookie is the Alexa TTS one by @ogiewon


#401

OK. Got things working. Redid the steps to get the cookie using FireFox instead of chrome. Added a semicolon to the end and pasted it into the Heroku app, along with the CSRF. Everything seems to be working for the moment.


#402

Finally got my echos to speak....However auto refresh for cookie does not work. So until that is fixed I am using @ogiewon Alexa TTS app to notify me when the cookie doesn't work anymore.


#403

I will have a server update out this afternoon with fixes...


#404

I'm almost caught up at work then I can work on the fixes...