Suggestions on how to narrow down reason for "CLOSE 1005 (no status received [internal]) [0 bytes]"

[J0ergL]

Dear all,

I am hoping for suggestions on how to narrow down the reason for "CLOSE 1005 (no status received [internal]) [0 bytes]".
My implementation runs for more then 5 days without disconnects using WS without SSL connecting as a client to SteVe running in the local network.
Connecting using SSL encryption to an CS my implementation disconnects after approximately 36h with:
2024-11-18 17:38:46,249 [DEBUG ] < CLOSE 1005 (no status received [internal]) [0 bytes] 2024-11-18 17:38:46,256 [DEBUG ] > CLOSE 1005 (no status received [internal]) [0 bytes] 2024-11-18 17:38:46,261 [DEBUG ] = connection is CLOSING 2024-11-18 17:38:46,266 [DEBUG ] < EOF 2024-11-18 17:38:46,267 [DEBUG ] > EOF 2024-11-18 17:38:46,267 [DEBUG ] = connection is CLOSED 2024-11-18 17:38:46,268 [DEBUG ] x closing TCP connection 2024-11-18 17:38:46,293 [ERROR ] Websockets.ConnectionClosed(): received 1005 (no status received [internal]); then sent 1005 (no status received [internal])
Any ideas on how to find the source for this discconect?

Any advice is appreciated. Thank you!

[J0ergL]

The mystery of this disconnect reason remains, however using the code of #616
reconnects automatically.