Cause 100% CPU consumption when mini server is at Config 15.3 Beta 3

[hoschult]

module seems to be not working when running current beta (Config 15.3 Beta 3). The problem looks like: (1) node red process consumes 100% CPU even if there are no flows activated (2) structure file is recieved, however selector in nodes does not respect the correlation (a switch in room xyz) To isolate the issue I gave the mini server config node an ip address which is not reachable and redeployed the flow - CPU utilization of 100% was gone away; Switching back to the working ip address, high cpu load comes back. How to reproduce the problem: a) take a brand new node red instance b) install node-red-contrib-loxone c) connect to a mini server which is running at Config 15.3 Beta 3 d) observe looping node-red process with top etc... on os level (consumes about 100% cpu)

Loxone Config 15.3 Beta 2 was ok --> I'm not sure if issue is on Loxone side. However (and from my point of view), node-red-contrib-loxone should be robust enough to not go in nested loops (causing 100% cpu utilization) when receiving suspicious Loxone responses.