Regular KNX Link Loss since upgrade to 2.2

How does everyone connect to the KNX? I have an Weinzierl IP Interface (not router) and had no problems until the last few days (upgraded to 2.2 on christmas).
What I experienced:

  1. my RPi 2 was more stressed than usual (>25% CPU compared to easy <10% usually)
  2. I had accidentially knxd installed in parallel

As I’m using an KNX IP Interface, I normally connect via built in calimero with pretty standard configuration. What did I do yesterday (after having KNX detach Events nearly every 5mins):

  1. deactivated knxd
  2. rebooted my Pi

since then, it seems to work, at least not another detach event.

What I did do in the knx.cfg:

  • added busaddr (0.0.0, it’s Default, I know)
  • added ignorelocalevents=false (also Default)
  • set autoReconnectPeriod=10

hth?

As I have use the eibmarkt KNX IP Interface I haven’t the knxd service installed.

Similar knx.cfg settings with one exception I use the autoReconnectPeriod standard setting (have used …=10 as well without success).

Yesterday, I found an interesting thread on GitHub including a link to an updated kns jar file.

Since then, I dont’f face the link loss issue.

Do you get double telegrams as described in the github thread? I don’t… My KNX works (and ever had) fine - except the detach events lately, which seem to be solved. #strange

I still have to restart the OH2 service on a DAILY basis due to this issue.

I am the only one?

That’s what my log says.

2018-02-23 00:17:37.438 [WARN ] [nx.internal.connection.KNXConnection] - KNX link has been lost (reason: server request on object tunneling link link (closed) 192.168.0.7:3671 TP1 medium, device 1.3.25, hopcount 6)
2018-02-23 00:17:37.443 [INFO ] [nx.internal.connection.KNXConnection] - KNX link will be retried in 10 seconds
2018-02-23 00:17:37.457 [ERROR] [.binding.knx.internal.bus.KNXBinding] - Received detach Event.
2018-02-23 00:17:37.649 [INFO ] [nx.internal.connection.KNXConnection] - Established connection to KNX bus on 192.168.0.7:3671 in mode TUNNEL.
2018-02-23 00:17:47.457 [INFO ] [nx.internal.connection.KNXConnection] - Trying to (re-)connect to KNX...
2018-02-23 00:17:47.496 [INFO ] [nx.internal.connection.KNXConnection] - Established connection to KNX bus on 192.168.0.7:3671 in mode TUNNEL.
2018-02-23 00:17:47.506 [INFO ] [nx.internal.connection.KNXConnection] - Connected to KNX
2018-02-23 00:17:50.515 [WARN ] [al.bus.KNXBindingDatapointReaderTask] - Autorefresh: Cannot read value for item 'alarmSensorGPS' from KNX bus: no confirmation reply received for L-Data.req from 1.3.25 to 11/7/100, low priority hop count 6 repeat tpdu 00 00: timeout
2018-02-23 00:17:50.519 [WARN ] [al.bus.KNXBindingDatapointReaderTask] - Autorefresh: Remaining retries for address '11/7/100' = '2'
2018-02-23 00:17:53.576 [WARN ] [al.bus.KNXBindingDatapointReaderTask] - Autorefresh: Cannot read value for item 'currAzimut' from KNX bus: no confirmation reply received for L-Data.req from 1.3.25 to 11/7/5, low priority hop count 6 repeat tpdu 00 00: timeout
2018-02-23 00:17:53.578 [WARN ] [al.bus.KNXBindingDatapointReaderTask] - Autorefresh: Remaining retries for address '11/7/5' = '2'
2018-02-23 00:17:56.633 [WARN ] [al.bus.KNXBindingDatapointReaderTask] - Autorefresh: Cannot read value for item 'currPressureBaro' from KNX bus: no confirmation reply received for L-Data.req from 1.3.25 to 11/7/26, low priority hop count 6 repeat tpdu 00 00: timeout
2018-02-23 00:17:56.637 [WARN ] [al.bus.KNXBindingDatapointReaderTask] - Autorefresh: Remaining retries for address '11/7/26' = '2'
2018-02-23 00:17:59.693 [WARN ] [.binding.knx.internal.bus.KNXBinding] - Value '-2.3' could not be sent to the KNX bus using datapoint 'command DP 11/7/10 currTemp, DPT main 0 id 9.001, low priority' - retrying one time: no confirmation reply received for L-Data.req from 1.3.25 to 11/7/10, low priority hop count 6 repeat tpdu 00 80 87 1a
2018-02-23 00:18:02.695 [WARN ] [.binding.knx.internal.bus.KNXBinding] - Value '-2.3' could not be sent to the KNX bus using datapoint 'command DP 11/7/10 currTemp, DPT main 0 id 9.001, low priority' - retrying one time: no confirmation reply received for L-Data.req from 1.3.25 to 11/7/10, low priority hop count 6 repeat tpdu 00 80 87 1a
2018-02-23 00:18:05.699 [WARN ] [al.bus.KNXBindingDatapointReaderTask] - Autorefresh: Cannot read value for item 'blndRight' from KNX bus: no confirmation reply received for L-Data.req from 1.3.25 to 11/5/135, low priority hop count 6 repeat tpdu 00 00: timeout
2018-02-23 00:18:05.703 [WARN ] [al.bus.KNXBindingDatapointReaderTask] - Autorefresh: Remaining retries for address '11/5/135' = '2'

what’s your knx.cfg?

for the record, I use this one:

ip=192.168.xx.xx
#busaddr=
ignorelocalevents=true
type=TUNNEL
#port=
localIp=192.168.xx.yy
#serialPort=
#pause=
#timeout
#readRetries
#autoReconnectPeriod=30
#maxRefreshQueueEntries=
#numberOfThreads=
#scheduledExecutorServiceShutdownTimeoutString=
#useNAT=true

Thx, Thomas

I use exactly the same knx.cfg.

Still no joy - I just returned from holidays during which I could not access OH anymore. All of a sudden, the KNX link has been lost.

How is your KNX interface configured in the ETS?

Thanks for this excellent hint and all your help, Thomas!

After digging deeper in my ETS configuration, I found out that my KNX/IP interface wasn’t able to use more than one tunnel - due to the physical address I assigned. The documentation states clearly that I have to choose an address which is followed by four empty addresses.

Now that the interface is able to use all five tunnels, the issue seems to be gone :-).

hi guys

I’m experiencing the same problem (my devices: openhab 2.3.0-1 (openhabian 1.4.1) on RPi3, Weinzierl 731 interface, tunnel mode) where my OpenHAB is loosing connection to the IP interface periodically (in different timeframes). @GoldenEye: what exactly did you change in your Weinzierl ETS configuration?

my config:
Bridge knx:ip:bridge [
ipAddress=“192.168.0.xx”,
portNumber=3671,
localIp=“192.168.0.xx”,
type=“TUNNEL”,
readingPause=50,
responseTimeout=5,
readRetriesLimit=10, <- I will comment this out
autoReconnectPeriod=5
]