there are a lot of dots and exclamation marks in your post but this doesn’t make it faster or more productive to find a fix for the issue. Please keep in mind that we all do our best to remove all of the issues. If there is still a memory leak in the version @J-N-K provided -i don’t think so- more people will report it. If you scared about “the other quality in town: SYSTEM CRASH” you can disable the binding until it is fully fixed. Thanks for being patient and for your feedback in any way.
Unfortunately not. It would be nice to see the full configuration of those that DO NOT experience problems. Maybe something is sent along which prevents the unsuccessful connect but since I neither use the binding nor own a supported device it‘s not so easy to debug.
After the hint of @summerguy i checked the ioBroker Project and it seems they also have a problem with Amazon login depending on the cookies. They wrote that the reason is a little change in the HTTP-Headers, but not what changed. Maybe this is the same issue -i don’t know at the moment- but i still check the headers and the cookies. There is no push on the ioBroker project because they want to test the changes. It is possible to reproduce this “endless web socket loading” in the browser. If i re-send the web socket request it never returns a response, so the same for the binding. This is what i got at the moment.
As i understood there is no one which do not experience problems. Only people who do not experience memory problems with the current release version, but it seems they all have web socket problems.
I too had the Out Of Memory issue being reported by everyone else.
The patched version of the binding has fixed this.
I’m still getting the connection failures in the log but my Echo Text-To-Speech is still working so I’m not sure exactly which Amazon connects are failing.
Happy to do any testing for the developers that might help. I’m in the UK so will be using the UK Amazon portal page.
Just as an extra, my system didn’t crash from the memory leak because I caught it in time. I have the system information binding monitoring a few basic vital signs - including free memory - and some rules that push alerts to my phone via the OpenHAB Cloud if anything’s wrong. This is fairly easy and well worth doing.
I am using 2.5.3-1 and related amazoncontrol binding.
I think to remember that at least one person reported to have problems even with an older version.
@J-N-K What about the jetty version, do you know if it changed since 2.5.3-1?
I didnt found a dependency for jetty in the add-on pom so i think the main project of openHAB decide which one is used?!?
