FYI no disconnects since updated app. Fingers crossed. Cheers
Thanks @DarrenJ I appreciate the update. I donāt have the disconnect issues others have so it can be a bit of a black box.
Sorry just discovered another disconnect
With the test version, I have no difference.
I can only add devices if I go North America (I am here in Hungary), but okay. Otherwise connection timeout and does not find the wall swtiches under āsmart plugā, it finds only my 3 Alexa Shows.
I added the switches, clicked the one roomās where I am sittingā¦ nothing happensā¦ and after 1 minute, it switched up. Okay, I clicked again, sitting here for 5 minutes and it is still on.
So it is still not usable for me 
(after 2 more minutes it switched off itself, but in Homey dashboard it shows ON)
Did you see this?
It looks like weāre not the only ones suffering from this problem.
tldr: the HomeBridge dev came up with a fix to a ā429ā error by sending a blank user agent, but there are subsequent reports of the ārate exceeded responseā error weāre seeing. Theyāre suggesting Amazon has intentionally or unintentionally poisoned the API.
Maybe randomising the user agent or adopting something user-specific as part of the UA? Just guessing.
@Andy_Henderson thank you thats a really great thread with some information ill im hopefull after having a quick look that ill release a fix tonight.
Looks like amazon are specifically targeting apps like mine to stop them, if that is the case this may become a game of wack-a-mole and amazon has a lot more resources than me and my hour of spare time each week.
Best of luck!
FWIW Iām an advocate of Hanlonās razor: āNever attribute to malice that which is adequately explained by stupidity.ā
Andy
The app is working fine. @HS64 problem sounds like the one I have from time to time with not beeing able to log into any of the Amazon servers. That is an Amazon problem and I solved it by trying over several days and suddenly all OK
A new version has been released which fixes the smart device connections!
I have submitted it to be reviewed by Athom and it will roll out automatically.
Just out of interest, what was your fix for this?
Hello, thanks for you app.
I want to buy an Echo Spot 2024, is you app support it ?
Thanks
@staeff when making a request I send through certain headers, for example when you visit ANY website, the sever is sent (in the header) information such as what web ābrowserā your using. Its called an agent header, I was sending through this information when I made requests on the their old apps API end point, but amazon had started blocking any request using my agent.
So I changed the request header, the issue is never the the ācodeā that needs to change - I changed a single word ā¦ its figuring out whats going on and this app is not a very high priority for me, I really donāt have much spare time. @Andy_Henderson doing the leg work and finding others having the same issue was really the key that fixed this, I just read the thread and applied it to my code. My one device which is connected directly to alexa (a diffuser) started working again.
@Pierre_V - No, I dont own that device
If you want I may can help you to integrate it
Thanks for the explanation, I didnāt need it as dumbed down 
I was interested if you did set the UserAgent to be empty/some other fixed value or if you now use some randomly generated string as one of the replies in the mentioned github issue was suggesting?
I absolutely get that you have better things to do in your life then to maintain this app, but exactly because of this I was wondering why you do not make it open source? Iām sure you are a good guy but still being able to verify the code would also give me a better feeling when entering my Amazon credentials somewhere 
And that shows how we as homey app developers need support by the community of these apps. Contribute in these ways, provide usefull testing results and help figure out what happens in certain use cases is very valuable
1 Like
All code and apps are reviewed by Athom for that reason.
Regarding security my advice would be if you donāt feel comfortable then donāt do it.
As to why it doesnāt have an open source licence - thatās because a private repo, so as far as Iām aware it canāt use an open source licence.
As to why it doesnāt have an open source licence - thatās because a private repo, so as far as Iām aware it canāt use an open source licence.
My suggestion was less to what license you should choose (though homebridge-alexa-smarthome and alexa-remote2 both use MIT for example). Please be as restrictive as you want in relation how people are allowed to (re)use your code. But making the code/repository public and allowing people to contribute can potentially allow you to free up more of your time and help the community to add support for their unsupported devices.
I just installed, finally I could choose EU server with success, and it seems to work as well.
Thank you!
