[amazonechocontrol] Error: Web Socket close 1005. Reason: null

[FranzSchi]

Expected Behavior

The plugin works without the error message in the logs

Current Behavior

The error seems to occour quite often even in 3.2.0-RC1
2021-12-18 12:36:42.944 [INFO ] [control.internal.WebSocketConnection] - Web Socket close 1005. Reason: null
2021-12-18 12:37:45.542 [INFO ] [control.internal.WebSocketConnection] - Web Socket close 1005. Reason: null
2021-12-18 12:38:47.830 [INFO ] [control.internal.WebSocketConnection] - Web Socket close 1005. Reason: null
2021-12-18 12:39:52.595 [INFO ] [control.internal.WebSocketConnection] - Web Socket close 1005. Reason: null
2021-12-18 12:40:57.149 [INFO ] [control.internal.WebSocketConnection] - Web Socket close 1005. Reason: null
2021-12-18 12:41:59.994 [INFO ] [control.internal.WebSocketConnection] - Web Socket close 1005. Reason: null

Possible Solution

Seems this thread already has a homemade binary
https://community.openhab.org/t/error-web-socket-close-1005-reason-null/130072

Steps to Reproduce (for Bugs)

1. install the Plugin
2. Add an amazon Account
3. (not sure if required) add a SmartHomeDevice

Context

Not sure if this decreases performance.
Errors should be fixed in General
See also: https://community.openhab.org/t/error-web-socket-close-1005-reason-null/130072

Your Environment

• 3.2.0-RC1 (Plugin is vanilla)
• Docker Image
• Raspbian Buster + Docker

[openhab-bot]

This issue has been mentioned on openHAB Community. There might be relevant details there:

https://community.openhab.org/t/error-web-socket-close-1005-reason-null/130072/8

[jaywiseman1971]

The fix version is here.

https://search.maven.org/remotecontent?filepath=org/smarthomej/addons/bundles/org.smarthomej.binding.amazonechocontrol/3.2.7/org.smarthomej.binding.amazonechocontrol-3.2.7.jar

Best, Jay

[openhab-bot]

This issue has been mentioned on openHAB Community. There might be relevant details there:

https://community.openhab.org/t/openhab-3-2-release-discussion/130327/3

[openhab-bot]

This issue has been mentioned on openHAB Community. There might be relevant details there:

https://community.openhab.org/t/amazon-echo-control-error-web-socket-close-1005-still-happening-on-3-2-0/130305/6

[lsiepel]

This is probably not fixed within the openHAB version. It might have been fixed in the smarthomej version.
For reference: #14129 (comment)
Related openHAB PR's : https://github.com/openhab/openhab-addons/pulls?q=is%3Apr+is%3Aclosed+merged%3A2021-05-01..2025-01-01+in%3Atitle+amazonechocontrol+

Would be nice if you can confirm this is still an issue in openHAB version 4.2.0