KNX component isn't trying to reconnect to the KNX gateway if connection was unsuccessful

[mishoboss]

Home Assistant release with the issue:
0.72.1

Last working Home Assistant release (if known):
no

Operating environment (Hass.io/Docker/Windows/etc.):
Linux

Component/platform:
KNX

Description of problem:
KNX component isn't trying to reconnect to the KNX gateway if connection was unsuccessful. Currently all KNX devices become "unavailable" until Home Assistant is restarted.

[Julius2342]

I received a couple of reports that something does not work within KNX on recent versions of home-assistant. Was there anything related to UDP changed within home-assistant recently?

[balloobbot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

[moustic999]

I have the latest version of HA 0.82.1
I have currently lot of issue with KNX, it seems that component get broken after a while.
It was not the case in older version ( 0.81,.... )

[balloobbot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

[Alexander-Krause-Glau]

From time to time, I have the same problem as @mishoboss in Home Assistant 0.86.3 with a Hager TYF120 KNX network gateway. Again, restarting home assistant (dockerized, restarting container) solves the problem.

[Julius2342]

May you activate KNX packet log and paste the output?

within home-assistant configuration please add:

logger:
  default: warning
  logs:
    xknx.telegram: debug
    xknx.knx: debug

[Alexander-Krause-Glau]

For my understanding: You are talking about the log entries, which are displayed when the problem occurs, right?

Will do, but may take some time, depending on the next problem occurence.

[Julius2342]

Yes, i try to find out the internal state of the module when this happens.

[Alexander-Krause-Glau]

Here is the log. The component does not seem to try to reconnect, since there are no further log entries (except the home assistant setup stuff) :

<KNXIPHeader HeaderLength="6" ProtocolVersion="16" KNXIPServiceType="KNXIPServiceType.CONNECT_REQUEST" Reserve="0" TotalLength="26" />
 body="<ConnectRequest control_endpoint="<HPAI 192.168.178.44:55089 />" data_endpoint="<HPAI 192.168.178.44:55089 />" request_type="ConnectRequestType.TUNNEL_CONNECTION" />" />
2019-03-14 06:02:29 ERROR (MainThread) [xknx.log] <CouldNotParseKNXIP description="wrong HPAI length" />
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/xknx/io/udp_client.py", line 87, in data_received_callback
    knxipframe.from_knx(raw)
  File "/usr/local/lib/python3.6/site-packages/xknx/knxip/knxip.py", line 78, in from_knx
    pos += self.body.from_knx(data[pos:])
  File "/usr/local/lib/python3.6/site-packages/xknx/knxip/connect_response.py", line 55, in from_knx
    pos += self.control_endpoint.from_knx(raw[pos:])
  File "/usr/local/lib/python3.6/site-packages/xknx/knxip/hpai.py", line 23, in from_knx
    raise CouldNotParseKNXIP("wrong HPAI length")
xknx.exceptions.exception.CouldNotParseKNXIP: <CouldNotParseKNXIP description="wrong HPAI length" />
2019-03-14 06:02:30 WARNING (MainThread) [homeassistant.components.knx] Can't connect to KNX interface: Could not establish connection

[stale]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.