Exception in socket.emit

[waldbaer]

I just had the following exception in my NodeRED setup which actually caused about 10 NodeRED reboots in a row.

Used version (node-red-contrib-luxtronik2): 0.5.3

Exception Backtrace:

an 02 22:19:25 rpi0 Node-RED[449]: 2 Jan 22:19:25 - [red] Uncaught Exception:
Jan 02 22:19:25 rpi0 Node-RED[449]: 2 Jan 22:19:25 - [error] TypeError: Cannot read property 'end' of null
Jan 02 22:19:25 rpi0 Node-RED[449]:     at Luxtronik.<anonymous> (/home/pi/.node-red/node_modules/node-red-contrib-luxtronik2/node_modules/luxtronik2/luxtronik.js:567:26)
Jan 02 22:19:25 rpi0 Node-RED[449]:     at Socket.emit (events.js:400:28)
Jan 02 22:19:25 rpi0 Node-RED[449]:     at emitErrorNT (internal/streams/destroy.js:106:8)
Jan 02 22:19:25 rpi0 Node-RED[449]:     at emitErrorCloseNT (internal/streams/destroy.js:74:3)
Jan 02 22:19:25 rpi0 Node-RED[449]:     at processTicksAndRejections (internal/process/task_queues.js:82:21)
Jan 02 22:19:25 rpi0 systemd[1]: nodered.service: Main process exited, code=exited, status=1/FAILURE
Jan 02 22:19:25 rpi0 systemd[1]: nodered.service: Failed with result 'exit-code'.
Jan 02 22:19:45 rpi0 systemd[1]: nodered.service: Service RestartSec=20s expired, scheduling restart.
Jan 02 22:19:46 rpi0 systemd[1]: nodered.service: Scheduled restart job, restart counter is at 1.
Jan 02 22:19:46 rpi0 systemd[1]: Stopped Node-RED graphical event wiring tool.

So far I did not further analyze the affected code. But these 10 reboots just happened without any modification in NodeRED. Maybe the heatpump had a problem or any of the involved network hardward. But suddenly the system somehow recovered and NodeRED was working again without any exceptions.