Error ERR_SOCKET_DGRAM_NOT_RUNNING about node-red-contrib-knx-ultimate HOT 6 CLOSED

Hello
Never saw this error before.
Do you have other nodes (apart from knx-ultimate) using KNX?
Let me some time to ditch into.

from node-red-contrib-knx-ultimate.

For me, this is a socket error in some components of node-red, as i don't find any error having "ERR_SOCKET_DGRAM_NOT_RUNNING", or, stating on this https://discourse.nodered.org/t/raspberry-pi-and-udp/7129 or https://discourse.nodered.org/t/osc-error-udp-error/10571 it can be any issue related to UDP communication, maybe related to using an already occupied UDP Port.
Please update your node-red. Your version is very old, yet there is V. 1.0.xx

from node-red-contrib-knx-ultimate.

There is an other Docker container running with an other KNX lib running. You think this could cause this error? Is there a way to prevent Node-RED crashing?

from node-red-contrib-knx-ultimate.

Yes, change your KNX/IP router port directly in ETS and on the knx-ultimate config node.

from node-red-contrib-knx-ultimate.

at fsm. (/hbvisu-data/node_modules/knx/src/FSM.js:178:23)

I think line 178 in FSM.js should be handled by an try and catch, to prevent application stop? Because it's called in a cb function of setTimeout. The lines after are never executed.

try { sm.socket.close(); } catch(err) { }

from node-red-contrib-knx-ultimate.

Hello
yes, i'll open an issue for that, but i've more than 1400 users and no one has connection problems.
You have for sure some issue in your chain. Please see my question on the other issue thread. Thanks.

from node-red-contrib-knx-ultimate.