Hi everyone,
When I tried to link my Alexa account to HerokuApp I've got a page that looks exactly like Alexa's login page, but that was not the original page (see image). I've got worried, since I'd provide my Alexa's credentials for a third party. Why use a look alike page? Why not ask clearly for the credentials not impersonating Amazon's page? Should I not be worried? Well ... I'm. I'd like very much use this app, but ... no, I'll not.
It is the Alexa page. This is the OATH authentication between the Alexa servers and the Heroku servers. The Heroku servers do not get the Alexa login information just an expiring token. The token is renewed every 10 days (not sure of the time period).
I see that device in my ignored devices. I would think it would be ignored. 
I guess we should be OK with this error.
Thanks for mentioning this. I will take a look and see what I can find
I traced the ID string (A1MPSLFC7L5AFK) in the "Unused Devices" tab of Echo Speaks back to my devices in Amazon.com. It was listed as some type of "Amazon Shopping Device". I deleted it within Amazon.com (manage devices) and no longer have that specific error.
However, I see the error below popped up a few hours ago. Not sure what it might be. I'll watch it for a while to see what happens. ???
@lados I am getting the same "Hostname Not Found" | Msg: alexa.amazon.com continuously. I'm not sure what that's about. I do have ONE echo device Offline, one of about 9. Rebooting my hub to see if it makes it stop.
EDIT: adding more detail:
Rebooted hub, starts out like this (like 10 times)
Echo (v3.3.0.1) | getDeviceActivity | Status: (400) | Message: Bad Request | Data: [message:Rate exceeded]
Then:
Echo (v3.3.0.1) | getPlaybackState | HostName Not Found | Msg: alexa.amazon.com
Echo (v3.3.0.1) | getDeviceActivity | HostName Not Found | Msg: alexa.amazon.com
Echo (v3.3.0.1) | getPlaylists | HostName Not Found | Msg: alexa.amazon.com
nearly continuously... It really brings my hub to its knees.
My issue with the MissingPropertyException is still ongoing as well. I also seem to have a new issue.
2020-02-21 11:17:01.223 am [error](http://192.168.0.8/installedapp/configure/3025)EchoApp (v3.5.0.0) | receiveEventData Error: groovy.lang.MissingPropertyException: No such property: AFF5OAL5E3DIU for class: java.lang.String
The new issue, and I think it started the same time as the issue above, is the following:
EchoApp (v3.5.0.0) | The Echo Speaks app has NOT received any device data from Amazon in the last (459830) seconds. There maybe an issue with the scheduling. Please open the app and press Done/Save.
Following the advise to open the app & press Done/Save DOES WORK. It stops the error from occurring for several hours although I have not timed the elapsed time before it reoccurs.
Not sure why deleting the Amazon Shopping Device from my Amazon.com account (device management) but I haven't gotten any errors in the last 18 hrs or so. Will keep monitoring the logs and let you know if the errors start up again. Just ironic- deleted the Amazon Shopping Device and presto- no more errors (at least for the last 18 hrs). Whats bad is: I don't even know what the Amazon Shopping Device is or how it got assigned to my Amazon account.
A Dash button perhaps? Amazon app on a mobile device? Amazon shopping browser extension?
Have you looked under Manage Your Content and Devices under your account on amazon.com?
Enabling Alexa Guard creates a new device too ????
Yes, I deleted the device from there and presto!
I have not been able to duplicate this 
What are your device detection settings like?
Can you send me a screenshot of the entire device detection prefs page?
Here is mine:
...and presto- new errors. Anyone else having similar errors? I'm pretty sure its effecting hub performance.
Make sure you are running the latest code.
I’m not sure how this weird loop only happens on Hubitat.
I’ve been trying to track it down on my side but can’t get it to happen on my 3 hubs
Continuing to get errors so I went back and reinstalled the ES device(s) and apps. Also reinstalled the Hubitat app. I'm going to reboot all the Alexa devices, network components and HE hub. ll monitor and update status. Thanks for trying to help- It is much appreciated.
How many Echo devices do you have enabled? I only have 2 of my Alexa devices enabled for announcements, and I have no errors.
We are using 14 Echo devices.
I installed the latest update (3.5.0.0) when it came out, and now we went down to only having one error about every 3 minutes (I believe).
A lot better then it was before!
I tried disabling several of my "echo devices" just to see if too many devices is the culprit. No impact- Anytime HE "speaks" through Echo Speaks, I get errors. I'm worse now than I ever been.
That error just means you Heroku server went into a deep sleep and needs to manually started, by restarting the instance on dashboard.heroku.com
Download the Hubitat app
