Mine previously showed June 13. Now It shows nothing because I can't get it to refresh. The login page just keeps looping every time I enter my username and password.
It finally broke this morning. When I went to the amazon login page, I needed to complete a two factor authentication (it sent a 6 digit number to my cell phone).
Ever since I installed Echo Speaks about a month ago, it only works intermittently. At first it will successfully speak my message. After a few times, it will stop speaking. When I try it a day or two later, again the same pattern. It works at first, then stops working. I do not see any errors in the logs, but I do see a debug. I’m not sure if the display of debug in the log indicates a problem or not.
Echo Speaks is being called from within a rule, and the rule is executing perfectly except my message is not spoken after the first time, or after the first several times. Within the rule I have at least a 30 second delay between messages.
I was wondering how long it would take Amazon to change something and break this.
Hopefully @tonesto7 can figure out the work around. There are also lots of communities that have used this method to integrate. I bet there are some smart people already poking at it.
Not sure where you're all located but I'm in the UK and have not had any issues....yet! (kiss of death)
I've had occasional errors in the past and a device become unresponsive a couple of times, but all ok since 2.5
Possibly region specific?
I'm not sure why the cookies are now failing but if you're looking for a short term fix, you can manually enter the cookie and that seemed to fix it for me.
Open your echo speaks app
Click "Login Service Settings"
Click "Heroku App Settings"
In the Heroku pop-up, click "Open App" (at top)
In the new page that is opened, there should be a button to manually enter a cookie.