Thanks Dave! That is what I was Missing.
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.
Thanks for the suggestions. I had tried both (and just tried again--I've used Firefox, Edge, and Brave), but no luck.
I cannot remember how to get out of this cycle, in hub echo speaks says I am not logged into amazon, but in the server (running locally) I am.
Resolved 
This morning, none of my routines ran, so after some digging, I saw that my Amazon login expired in Hubitat/ echo speaks app. I logged back in and it all came back. Maybe that was your issue? I am guessing something happened on the Amazon side between last night and this am, as my alarms I set through echo devices outside of Hubitat also didn’t run.
Same here. I was no longer logged in. I had just looked at this within the last few days to see if my cookie was refreshing and it was. So something happened recently.
Aware of that. This is why I posted.
I saw nothing to indicate an issue. Everything worked here on the Hubitat and non-Hubitat side. In fact, my daughter has alarms set for every 15 minutes on school day mornings, and those all worked.
Do you have a recommended fix?
Logging in again does not fix it
Manual refresh doesn't fix it
Restarting the server and trying the above two also doesn't fix it
Unfortunately, I don’t have a fix. I’ve never run into this issue.
Try restarting the server again and then logging in using a private/incognito browser window. Login and make sure it shows that the cookie is OK (or whatever it shows, don’t recall off the top of my head). Leave that window open and go back to the app in Hubitat and see what happens.
You can also try temporarily disabling two factor authentication, if you have that enabled for you Amazon account.
I did this multiple times and got the screen that said it was okay. This is part of the issue.
see other thread. to resolve it i had to reset the server on hubitat and redo the server setup with newly generated callback url. if u have 2 phase login enabled it will prompt u to get an SMS to your phone. enter the code and make sure to check the never require it box for subsequent logins ( ,or some such language... don't remember the exact wording )
I use a OTP app, and always checked the never require on this device option.
I did reset the server on the HA side, and now I cannot get it to recognize that I logged in.