KNX Binding: tunneling request with invalid rcv-seq - sporadic dysfunction - help needed

Hi Stefan, George,

I have exactly the same issue and would appreciate your help in finding a solution. :slight_smile:

I am using a Siemens IP interface N148/22 (no router).
At first everything works fine, but after a while there is a sync issue. The cause is not really known.
I also updated manually my KNX binding from 1.10 to the latest version of the KNX binding (version 1.11.0.201708271339) but seemly the issue remains.

Here is a typical extract:

2017-11-26 18:04:56.462 [WARN ] [tuwien.auto.calimero                ] - KNXnet/IP Tunneling xxx.yyy.zzz.www:3671: tunneling request with invalid rcv-seq 42, expected 45
2017-11-26 18:04:57.462 [WARN ] [tuwien.auto.calimero                ] - KNXnet/IP Tunneling xxx.yyy.zzz.www:3671: tunneling request with invalid rcv-seq 42, expected 45
2017-11-26 18:04:58.462 [WARN ] [tuwien.auto.calimero                ] - KNXnet/IP Tunneling xxx.yyy.zzz.www:3671: tunneling request with invalid rcv-seq 43, expected 45
2017-11-26 18:04:59.462 [WARN ] [tuwien.auto.calimero                ] - KNXnet/IP Tunneling xxx.yyy.zzz.www:3671: tunneling request with invalid rcv-seq 43, expected 45

Strange that if the value corresponds (after 256 events), the sync is again established, but only for a while. :frowning_face:

Is there a newer version of the binding available I could use?
Any suggestions?

Thanks !
Filip