node-red-contrib-loxone icon indicating copy to clipboard operation
node-red-contrib-loxone copied to clipboard

Uncaught exception on regular basis

Open janwadebock opened this issue 1 year ago • 4 comments

I have on regular basis an uncaught exception due to which Nodered restarts completely.

Context: I am running nodered in docker on a synology. Running Nodered docker version 4.0.5-22

those are the installed nodes: image

Sometimes, the nodered docker container restarts with this error message: 2024-12-02T08:13:41.597648451Z stdout 2 Dec 08:13:41 - [red] Uncaught Exception: 2024-12-02T08:13:41.598272672Z stdout 2 Dec 08:13:41 - [error] ReferenceError: data is not defined 2024-12-02T08:13:41.598371360Z stdout     at API. (/data/node_modules/node-red-contrib-loxone/loxone/loxone.js:263:21) 2024-12-02T08:13:41.598436433Z stdout     at API.emit (node:events:518:28) 2024-12-02T08:13:41.598481788Z stdout     at Connection. (/data/node_modules/node-lox-ws-api/lib/API.js:119:14) 2024-12-02T08:13:41.598536132Z stdout     at Connection.emit (node:events:518:28) 2024-12-02T08:13:41.598580044Z stdout     at Connection.handle_message (/data/node_modules/node-lox-ws-api/lib/Connection.js:176:18) 2024-12-02T08:13:41.598626870Z stdout     at WebSocketConnection. (/data/node_modules/node-lox-ws-api/lib/Connection.js:142:14) 2024-12-02T08:13:41.598676245Z stdout     at WebSocketConnection.emit (node:events:518:28) 2024-12-02T08:13:41.598744180Z stdout     at WebSocketConnection.processFrame (/data/node_modules/websocket/lib/WebSocketConnection.js:554:26) 2024-12-02T08:13:41.598793436Z stdout     at /data/node_modules/websocket/lib/WebSocketConnection.js:323:40 2024-12-02T08:13:41.598837317Z stdout     at processTicksAndRejections (node:internal/process/task_queues:85:11)

How can I debug this further ?

janwadebock avatar Dec 02 '24 11:12 janwadebock