node-red exits - Uncaught Exception with node-dweetio

Which node are you reporting an issue on?

node-dweetio

What are the steps to reproduce?

run a flow with a node-dweetio for 12-36 hours

What happens?

node-red process exits with the following error messages:

1 Jan 06:30:10 - [red] Uncaught Exception:
1 Jan 06:30:10 - Error: not opened
at WebSocket.send (/root/.node-red/node_modules/node-dweetio/node_modules/ws/lib/WebSocket.js:181:16)
at WS.send (/root/.node-red/node_modules/node-dweetio/node_modules/socket.io-client/lib/transports/websocket.js:107:22)
at WS.Transport.packet (/root/.node-red/node_modules/node-dweetio/node_modules/socket.io-client/lib/transport.js:178:10)
at Socket.packet (/root/.node-red/node_modules/node-dweetio/node_modules/socket.io-client/lib/socket.js:295:22)
at SocketNamespace.packet (/root/.node-red/node_modules/node-dweetio/node_modules/socket.io-client/lib/namespace.js:64:17)
at reset (/root/.node-red/node_modules/node-dweetio/node_modules/socket.io-client/lib/socket.js:512:34)
at Socket.maybeReconnect (/root/.node-red/node_modules/node-dweetio/node_modules/socket.io-client/lib/socket.js:539:16)
at Socket.EventEmitter.emit (/root/.node-red/node_modules/node-dweetio/node_modules/socket.io-client/lib/events.js:170:22)
at Socket.onConnect (/root/.node-red/node_modules/node-dweetio/node_modules/socket.io-client/lib/socket.js:411:12)
at WS.Transport.onConnect (/root/.node-red/node_modules/node-dweetio/node_modules/socket.io-client/lib/transport.js:139:17)

What do you expect to happen?

Please tell us about your environment:

• Node-RED version: v1.0.3
• node.js version: v13.5.0
• npm version: 6.13.4
• Platform/OS: Node.js docker container

Start with the node-dweetio WebSocket.send stack trace, especially node-dweetio/node_modules/ws/lib/WebSocket.js and its socket.io-client transport calls. Reproduce the long-running flow for 12–36 hours in the Node.js Docker environment described. Done means the node-red process no longer exits from the reported “not opened” exception.