NETIP_TUNNELING_SOCKET; Received Telegram: <KNX-group-address>@<IP-address> from <KNX-phys-address> has different data size as defined (defined:<x>, received:<y>).

NETIP_TUNNELING_SOCKET; Received Telegram: <KNX-group-address>@<IP-address> from <KNX-phys-address> has different data size as defined (defined:<x>, received:<y>).

BMS Server 2.0, BMS Platform, MP Server

The BMS Server has received a telegram from the field that does not match the respective definition regarding the length of the data.

The expected data size as defined in KNX / Telegram definitions does not match the received number of octets as sent by the device. There are multiple reasons for this issue:

• The imported ETS project is not correct or outdated.

• There is a KNX device which is not configured correctly or which is not part of the ETS project.

• Multiple ETS projects are used in the building but KNXnet/IP routing is activated and the same multicast address is used in all projects.

• Make sure the group address is properly configured in the ETS and choose a matching data size and type in KNX / Telegram definitions.

• Ensure that all KNX devices are programmed correctly.

• Ensure that there is no KNX device connected to the bus that is not part of ETS.

• Ensure that different ETS project are using different KNXnet/IP multicast addresses.