Strange, when I restart OpenHAB, I see the following in openhab.log:
2017-05-11 22:29:30.821 [INFO ] [g.tcp.AbstractDatagramChannelBinding] - The maximum buffer will be set to the default value of 1024
2017-05-11 22:29:30.821 [INFO ] [g.tcp.AbstractDatagramChannelBinding] - The interval to retry connection setups will be set to the default value of 5
2017-05-11 22:29:30.821 [INFO ] [g.tcp.AbstractDatagramChannelBinding] - The cron job to reset connections will be set to the default value of 0 0 0 * * ?
2017-05-11 22:29:30.822 [INFO ] [g.tcp.AbstractDatagramChannelBinding] - The setting to share channels within an Item will be set to the default value of true
2017-05-11 22:29:30.822 [INFO ] [g.tcp.AbstractDatagramChannelBinding] - The setting to share channels between the items with the same direction will be set to the default vaulue of true
2017-05-11 22:29:30.822 [INFO ] [g.tcp.AbstractDatagramChannelBinding] - The setting to share channels between directions will be set to the default vaulue of true
2017-05-11 22:29:30.823 [INFO ] [g.tcp.AbstractDatagramChannelBinding] - The setting to use address masks for incoming connections will be set to the default value of true
2017-05-11 22:29:30.860 [INFO ] [g.tcp.AbstractDatagramChannelBinding] - Listening for incoming data on /0:0:0:0:0:0:0:0:25001
2017-05-11 22:29:30.861 [INFO ] [b.core.service.AbstractActiveService] - UDP Refresh Service has been started
2017-05-11 22:29:30.861 [INFO ] [ing.tcp.protocol.internal.UDPBinding] - The maximum timeout for blocking write operations will be set to the default value of 3000
2017-05-11 22:29:30.862 [INFO ] [ing.tcp.protocol.internal.UDPBinding] - The blocking nature of read/write operations will be set to the default value of false
2017-05-11 22:29:30.862 [INFO ] [ing.tcp.protocol.internal.UDPBinding] - The preamble for all write operations will be set to the default value of
2017-05-11 22:29:30.863 [INFO ] [ing.tcp.protocol.internal.UDPBinding] - The postamble for all write operations will be set to the default value of
2017-05-11 22:29:30.863 [INFO ] [ing.tcp.protocol.internal.UDPBinding] - Updating states with returned values will be set to the default value of true
2017-05-11 22:29:30.863 [INFO ] [g.tcp.AbstractDatagramChannelBinding] - We will accept data coming from the remote end /192.168.3.10:25001
2017-05-11 22:29:30.863 [INFO ] [ing.tcp.protocol.internal.UDPBinding] - The character set will be set to the default value of ASCII
2017-05-11 22:29:30.864 [INFO ] [g.tcp.AbstractDatagramChannelBinding] - We will accept data coming from the remote end /192.168.3.10:10000
2017-05-11 22:29:31.117 [WARN ] [g.tcp.AbstractDatagramChannelBinding] - Received data "Scrambled data:28.40 Don 11 from an undefined remote end /192.168.3.10:10000. We will not process it"
2017-05-11 22:29:31.117 [WARN ] [g.tcp.AbstractDatagramChannelBinding] - No channel is active or defined for the data we received from /192.168.3.10:10000. It will be discarded.
2017-05-11 22:29:33.120 [WARN ] [g.tcp.AbstractDatagramChannelBinding] - Received data "Scrambled data 22:28.42 Don 11
Some messages are coming from “ing.tcp.protocol.internal.UDPBinding” and some from “g.tcp.AbstractDatagramChannelBinding”.
I think there is a contradiction between “We will accept data coming from the remote end /192.168.3.10:10000” and “No channel is active or defined for the data we received from /192.168.3.10:10000”.