I was getting notices that my Echo Speaks needed updating. I was able to get everything on the hubitat side updated, apps and drivers. Now it tells me that I need to update the server on Heroku. I cannot find instructions anywhere on how to update that. Can anyone help and explain how I update this?
Two ways to do this. Add Tonesto as a collaborator, or manually.
Here are the instructions. The first link gives the instructions for collaboration, the second (which is also linked from that page) gives the manual method.
Thank you so so much. Really appreciate you guys helping without making me feel like an idiot. Keep up the great work. I made sure to donate as I really appreciate the work on this app.
Has anyone figured out the issue in regards to the occasional echo device logging a blank lastVoiceActivity: ?
I saw @VilifiedFerret 's post that seems to fix the issue by commenting that one line out, but that does not really explain the issue of why only one device is having that issue and also is that line actually supposed to be commented out? I see in line 895 of the Echo Speaks Device driver there is a similar debug logging, but for wasLastSpokenToDevice: which is commented out.
My Cookie just expired and didn't autorefresh and now Amazon won't let me login, it just keeps resetting my password, For now EchoSpeaks is offline on my network
I've updated to the latest version (as of 5 mins ago latest versions) and still cannot login to Amazon, the password is right as I can login normally through a browser but on the heroku proxy link that it provides it will not accept my login details.
@tonesto7 posted that he's got a fix and you'll need to update the server part. I followed his automated server update procedures but haven't had a chance to log in yet but it now comes up to a login screen for me
I have the latest version and auto updates setup, I get the login page, login, it says successful got cookie but then just goes back to echo speaks and asks me to login again.
That's exactly what happens to me. I manually updated. Didn't know about the auto-update method. But also setup the auto-update yesterday, and still the same issue.