KNX Binding, OpenHAB2 makes ETS5 application downloads fail

Hi,

I am using ETS5 to manage my KNX home automation and OpenHAB2 to allow me to turn everything on or off using the Android app and my computer.

However, if OpenHAB2 is running while I am performing a device upgrade, it keeps sending T_Disconnect telegrams to my ETS5 and the device in question, making everything slower and eventually even failing the device upgrade.

I’ve included captured traffic logs but they are in ETS5 format and not easily readable (unless you can read KNX wire protocol).

This is a normal update cycle:

<CommunicationLog xmlns=“http://knx.org/xml/telegrams/01”>

<Telegram Timestamp=“2018-11-17T18:08:10.0223791Z” Service=“L_Data.ind” FrameFormat=“CommonEmi” RawData=“2900B05011100001064E437A5CA70281”/>

<Telegram Timestamp=“2018-11-17T18:08:10.0228001Z” Service=“L_Data.con” FrameFormat=“CommonEmi” RawData=“2E00B0600001111000CE”/>

<Telegram Timestamp=“2018-11-17T18:08:10.0232449Z” Service=“L_Data.con” FrameFormat=“CommonEmi” RawData=“2E00B06000011110037E0A7B97”/>

<Telegram Timestamp=“2018-11-17T18:08:10.0845369Z” Service=“L_Data.ind” FrameFormat=“CommonEmi” RawData=“2900B0501110000100FE”/>

</CommunicationLog>

While this is one when OpenHAB2 is active:

<CommunicationLog xmlns=“http://knx.org/xml/telegrams/01”>

<Telegram Timestamp=“2018-11-17T18:01:45.3223658Z” Service=“L_Data.con” FrameFormat=“CommonEmi” RawData=“2E00B06000011110036E0C5578”/>

<Telegram Timestamp=“2018-11-17T18:01:45.3452345Z” Service=“L_Data.ind” FrameFormat=“CommonEmi” RawData=“2900B060000200010081”/>

<Telegram Timestamp=“2018-11-17T18:01:45.3452982Z” Service=“L_Data.ind” FrameFormat=“CommonEmi” RawData=“2900B060000200010081”/>

<Telegram Timestamp=“2018-11-17T18:01:45.6530256Z” Service=“L_Data.ind” FrameFormat=“CommonEmi” RawData=“2900B0501110000100EE”/>

<Telegram Timestamp=“2018-11-17T18:01:45.6540195Z” Service=“L_Data.ind” FrameFormat=“CommonEmi” RawData=“2900B060000211100081”/>

<Telegram Timestamp=“2018-11-17T18:01:45.6541099Z” Service=“L_Data.ind” FrameFormat=“CommonEmi” RawData=“2900B060000211100081”/>

<Telegram Timestamp=“2018-11-17T18:01:45.7566596Z” Service=“L_Data.ind” FrameFormat=“CommonEmi” RawData=“2900B050111000010F424C55780FA1042603C7023AC6031B27”/>

<Telegram Timestamp=“2018-11-17T18:01:45.756963Z” Service=“L_Data.con” FrameFormat=“CommonEmi” RawData=“2E00B0600001111000C2”/>

<Telegram Timestamp=“2018-11-17T18:01:45.7579076Z” Service=“L_Data.ind” FrameFormat=“CommonEmi” RawData=“2900B060000211100081”/>

<Telegram Timestamp=“2018-11-17T18:01:45.757972Z” Service=“L_Data.ind” FrameFormat=“CommonEmi” RawData=“2900B060000211100081”/>

<Telegram Timestamp=“2018-11-17T18:01:45.7580272Z” Service=“L_Data.ind” FrameFormat=“CommonEmi” RawData=“2900B060000200010081”/>

<Telegram Timestamp=“2018-11-17T18:01:45.7580837Z” Service=“L_Data.ind” FrameFormat=“CommonEmi” RawData=“2900B060000200010081”/>

</CommunicationLog>

You can try to open up an issue on https://github.com/openhab/openhab2-addons for the developers to look into this

Of course… you should have OH2 service down while making such changes to your KNX devices.

Of course… you should have OH2 service down while making such changes to your KNX devices.

I resorted to shutting down openhab to perform the download but OpenHAB should not interfere with traffic on the bus, especially not if it isn’t related to OpenHAB functions…

I’ll create an issue in github, thanks.