core: KNX Integration stopped working in 2022.8.7

The problem

KNX Integration stopped working / responding after some time. Either Switches, Lights, Temperatur sensor, motion detectors were not working anymore and logfile was spammed with quite a few entries regarding connections and data types error?!

i am more than happy to test und can provide additional logs/information if needed.

i reverted back to 2202.8.6 and until now it seems to be working.

What version of Home Assistant Core has the issue?

core-2022.8.7

What was the last working version of Home Assistant Core?

core-2022.8.6

What type of installation are you running?

Home Assistant OS

Integration causing the issue

knx

Link to integration documentation on our website

https://www.home-assistant.io/integrations/knx/

Diagnostics information

config_entry-knx-613e6fdc6c723035b73d8c08d2521a21.json.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Well the changes introduced with `xknx 1.0.1` may or may not be the culprint, but i am by no mean an expert:



Logger: xknx.log
Source: /usr/local/lib/python3.10/site-packages/xknx/io/tunnel.py:579
First occurred: 26. August 2022 um 11:56:18 (1172 occurrences)
Last logged: 09:11:31

Received TunnellingRequest with unexpected sequence number. Discarding frame: <TunnellingRequest communication_channel_id="16" sequence_counter="0" cemi="<CEMIFrame code="L_DATA_IND" src_addr="IndividualAddress("1.1.62")" dst_addr="GroupAddress("5/1/12")" flags="1011110011100000" tpci="TDataGroup()" payload="<GroupValueWrite value="<DPTArray value="[0xc,0x74]" />" />" />" />
Received TunnellingRequest with unexpected sequence number. Discarding frame: <TunnellingRequest communication_channel_id="16" sequence_counter="0" cemi="<CEMIFrame code="L_DATA_IND" src_addr="IndividualAddress("1.1.99")" dst_addr="GroupAddress("5/0/4")" flags="1011110011100000" tpci="TDataGroup()" payload="<GroupValueWrite value="<DPTArray value="[0x0,0x1d]" />" />" />" />
Received TunnellingRequest with unexpected sequence number. Discarding frame: <TunnellingRequest communication_channel_id="16" sequence_counter="0" cemi="<CEMIFrame code="L_DATA_IND" src_addr="IndividualAddress("1.1.62")" dst_addr="GroupAddress("5/1/12")" flags="1011110011100000" tpci="TDataGroup()" payload="<GroupValueWrite value="<DPTArray value="[0xc,0x60]" />" />" />" />
Received TunnellingRequest with unexpected sequence number. Discarding frame: <TunnellingRequest communication_channel_id="16" sequence_counter="0" cemi="<CEMIFrame code="L_DATA_IND" src_addr="IndividualAddress("1.1.73")" dst_addr="GroupAddress("4/1/4")" flags="1011110011100000" tpci="TDataGroup()" payload="<GroupValueWrite value="<DPTBinary value="0" />" />" />" />
Received TunnellingRequest with unexpected sequence number. Discarding frame: <TunnellingRequest communication_channel_id="16" sequence_counter="0" cemi="<CEMIFrame code="L_DATA_IND" src_addr="IndividualAddress("1.1.101")" dst_addr="GroupAddress("0/0/3")" flags="1011110011100000" tpci="TDataGroup()" payload="<GroupValueWrite value="<DPTArray value="[0xc9,0xb,0x22]" />" />" />" />


Logger: xknx.log
Source: /usr/local/lib/python3.10/site-packages/xknx/io/tunnel.py:377
First occurred: 26. August 2022 um 11:56:15 (580 occurrences)
Last logged: 09:11:24

Received DisconnectRequest from tunnelling sever.


Logger: xknx.log
Source: runner.py:119
First occurred: 26. August 2022 um 11:56:20 (538 occurrences)
Last logged: 09:09:27

L_DATA_CON Data Link Layer confirmation timed out for <TunnellingRequest communication_channel_id="16" sequence_counter="0" cemi="<CEMIFrame code="L_DATA_REQ" src_addr="IndividualAddress("15.15.250")" dst_addr="GroupAddress("2/6/4")" flags="1011110011100000" tpci="TDataGroup()" payload="<GroupValueWrite value="<DPTArray value="[0xff]" />" />" />" />
L_DATA_CON Data Link Layer confirmation timed out for <TunnellingRequest communication_channel_id="16" sequence_counter="1" cemi="<CEMIFrame code="L_DATA_REQ" src_addr="IndividualAddress("15.15.250")" dst_addr="GroupAddress("2/4/4")" flags="1011110011100000" tpci="TDataGroup()" payload="<GroupValueWrite value="<DPTArray value="[0x66]" />" />" />" />
L_DATA_CON Data Link Layer confirmation timed out for <TunnellingRequest communication_channel_id="16" sequence_counter="2" cemi="<CEMIFrame code="L_DATA_REQ" src_addr="IndividualAddress("15.15.250")" dst_addr="GroupAddress("1/1/3")" flags="1011110011100000" tpci="TDataGroup()" payload="<GroupValueWrite value="<DPTBinary value="False" />" />" />" />
L_DATA_CON Data Link Layer confirmation timed out for <TunnellingRequest communication_channel_id="16" sequence_counter="0" cemi="<CEMIFrame code="L_DATA_REQ" src_addr="IndividualAddress("15.15.250")" dst_addr="GroupAddress("1/1/3")" flags="1011110011100000" tpci="TDataGroup()" payload="<GroupValueWrite value="<DPTBinary value="True" />" />" />" />
L_DATA_CON Data Link Layer confirmation timed out for <TunnellingRequest communication_channel_id="16" sequence_counter="0" cemi="<CEMIFrame code="L_DATA_REQ" src_addr="IndividualAddress("15.15.250")" dst_addr="GroupAddress("1/1/3")" flags="1011110011100000" tpci="TDataGroup()" payload="<GroupValueWrite value="<DPTBinary value="False" />" />" />" />



### Additional information

The integration was rocksolid until this update. Running an MDT KNX IP Interface on the same network without any issues. UI KNX Integration Settings is set to UDP (i think was automigrated, i was using KNX since yaml editing was a thing)

About this issue

Original URL
State: closed
Created 2 years ago
Reactions: 2
Comments: 32 (13 by maintainers)

Most upvoted comments

I was waiting for confirmation that this was already in the upcoming/latest release, so i have updated to latest verison and can confirm that this is no issue anymore, thanks for fixing it.

northalpha on Sep 12, 2022

@NicoLouis-be this should be fixed with 2022.9 (beta) since you are using NAT mode.

can confirm 2022.9.0b5 has fixed the problem for me

NicoLouis-be on Sep 7, 2022

@NicoLouis-be this should be fixed with 2022.9 (beta) since you are using NAT mode.

farmio on Sep 6, 2022

indeed it all worked for a very long time, i updated yesterday from i think 2022.8.3 to 2022.8.7 I’m at work at the moment but i can test beta this evening if that one is not working i will revert back and test 2022.8.6 and lower to check the version that the problem occurs

I use a loxone controller, config: tunneling mode default address: 15.15.250 multicast group: 224.23.12 multicast port: 3671 local IP: 10.10.1.5 state updater: ON rate limit: 20 tuneling type: UDP with route back/NAT mode host: 10.10.1.30 port 3671

EDIT:

Hi,

I also have the problem with KNX stops working after some time. Mostly about .5 to 2 hours after restart. The Problem appeared with 2022.8.7. On 2022.8.4 there was no problem.

I just remember that i did a reload of the integration yesterday and then it did work for a while but it reoccured. It could be a different problem but it also has some similarities

Edit 2: Temp log gives a good indication when it failed Capture 1: updated Home assistant 2: 20:33 noticed knx buttons didn’t work and reloaded the integration, 3: 00:51 failed receiving again

NicoLouis-be on Sep 6, 2022

If you are using NAT mode (route_back) then https://github.com/home-assistant/core/pull/77627 should make things better. You can test this by using HA 2022.9.0beta1 and newer.

If you are using normal UDP or even TCP tunnels then you should not see warnings about TunnellingRequest with sequence number ever 😬

@technikbutze unfortunately the markdown parser here seems to crop some of the logs. Could you please upload it as file or send me via discord?

farmio on Sep 1, 2022

@farmio,

ok, what can I help

I will try to setup logging and tcpdump in the next days… I will come to you with more information, when available

Thanks

gorman553 on Aug 29, 2022