Thanks Dave! That is what I was Missing.
1 Like
This AM I was scanning some logs and saw an anomaly and began to explore it. I had noted that 2 of my Echo devices were incorrectly identified in HE. Dev 477 and 478 on the left column say I have 2 Echo Show 5's. I don't.
I have maintained my list of Echo devices and their devtype ID's and knew immediately where to look. Indeed, in the App code at about line 7132 the table lists the problem:
There is no table I know of where these can be looked up and verified (there must be!) but I've been adding new things over the years and was comfortable making the change:
I removed this line from the 'Amazon Echo Shows section:
"A4ZXE0RM7LQ7A" : [ c: [ "a", "t" ], i: "echo_show_5", n: "Echo Show 5 (Gen5)" ],
And added this line to the Amazon Echo Dot section:
"A4ZXE0RM7LQ7A" : [ c: [ "a", "t" ], i: "echo_dot_gen5", n: "Echo Dot (Gen5)" ],
saved. and reran the detection on Echo Speaks and the device correctly identifies.
I'd like to add - just trying to find if a device is a gen 4 or Gen 5 is very difficult. It used to be you could hit the 'about' on a device in your alexa app. That no longer seems to work. Nor does the device itself have it embossed, and even asking it 'what are you' gets you stuck in Alexa stupidity responses.
What I did find, is the 'Devices' option on my Amazon page under the Accounts and Lists. It doesn't show the DevType code which would be really nice, but it does detail the identity of your device models including their Generations.
Lastly, this error WAS noted some time ago by another. I'm just passing my hack on in case it helps others. I previously submitted PR's for 4-5 units and they are now in the 4.3.0.1 version. This was not a new item, but an bug fix in my driver that I'm sharing.
The "you still need to log in to Amazon" issue has been reported before, but I can't seem to get around it. I'm using a local server, and things used to work fine, but for the past couple of months Echo Speaks hasn't been working.
I get:
I go to the login page and log in successfully:
But when I close that window (without hitting "save settings"), I still see "you still need to log in to Amazon."
The log shows this:
I have followed these instructions:
I have also reset the service data and recreated the server (which is running in Docker).
Again, this used to work. I get the idea from some of the previous reports that, although people saw this error, their Echo Speaks setup still worked, but mine no longer does.
Any suggestions? Thanks!
try the 2nd on a differnt browser or clear cache
Along these lines, try an incognito/private browser window.
1 Like
Thanks for the suggestions. I had tried both (and just tried again--I've used Firefox, Edge, and Brave), but no luck.
