Login error in 2.3.8

Discussions about Z-Way software and Z-Wave technology in general
Post Reply
theforce
Posts: 2
Joined: 30 Dec 2017 01:06

Login error in 2.3.8

Post by theforce » 17 Oct 2018 00:03

Hi!

I had hoped that 2.3.8 would have fixed the login issue mentioned here: https://github.com/Z-Wave-Me/zwave-smarthome/issues/242 .

The login issue is related to this issue: https://github.com/Z-Wave-Me/home-automation/issues/441 .

I can confirm that even though the release notes of 2.3.8 states:

"- Added libraries for Raspbian Stretch"
"- Fixed socket not being closed on peer disconnect"

I keep getting this error after opening a web socket. The error occurs every time after the web socket is closed, either normally or abnormally, i.e. if the host is down, non-existent or disconnects unexpectedly. As long as the web socket is connected there is no error, but as soon as the socket is closed the error occurs and Z-way must be restarted in order to login again.

Detailed instructions of how to reproduce the error can be found here: viewtopic.php?f=3419&t=22347&start=30#p69949 .

Please note that the error occurs regardless if the host is up or down, the problem occurs when the connection closes. It is also not necessary so specify the protocol-parameter in the sockets.websocket constructor.

I'm running Raspbian Stretch on my Raspberry Pi 3 Model B.

Hope you can fix this issue as soon as possible. When it is fixed I will release a Z-way plugin which can control LG WebOS TVs with web sockets.

/Mattias

brizz
Posts: 5
Joined: 18 Oct 2017 19:15

Re: Login error in 2.3.8

Post by brizz » 17 Oct 2018 00:39

Can confirm I'm also still experiencing this issue trying to implement a plugin that uses websockets. All fine until you disconnect - then auth. does not work. Was also hoping this would be fixed :(

If I'm remembering right, it's related to an older internal state of OpenSSL becoming mangled. Another thread here: viewtopic.php?f=3419&t=24524

Post Reply