KNX component stopped working after upgrading to 0.86.3

[fluppie]

Home Assistant release with the issue:

0.86.3

Last working Home Assistant release (if known): 0.85.1

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

Hassbian on Raspberry Pi 3B+

Component/platform:

KNX / https://www.home-assistant.io/components/knx/

Description of problem:

After upgrading to 0.86.3 the KNX component doesn't work/connect anymore.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

knx:
  tunneling:
    host: '192.168.1.5'
    port: 3671
    local_ip: '192.168.1.241'
  expose:
    - type: 'datetime'
      address: '4/0/0'

Traceback (if applicable):

2019-01-27 21:58:06 ERROR (MainThread) [xknx.log] <CouldNotParseKNXIP description="wrong HPAI length" /> Traceback (most recent call last): 
File "/srv/homeassistant/lib/python3.5/site-packages/xknx/io/udp_client.py", line 87, in data_received_callback knxipframe.from_knx(raw) 
File "/srv/homeassistant/lib/python3.5/site-packages/xknx/knxip/knxip.py", line 78, in from_knx pos += self.body.from_knx(data[pos:]) 
File "/srv/homeassistant/lib/python3.5/site-packages/xknx/knxip/connect_response.py", line 55, in from_knx pos += self.control_endpoint.from_knx(raw[pos:]) 
File "/srv/homeassistant/lib/python3.5/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-01-27 21:58:08 WARNING (MainThread) [homeassistant.components.knx] 
Can't connect to KNX interface: Could not establish connection

Additional information:

[Julius2342]

that exception is from KNX library itself - which was not changed for 2 years. Are you sure you did not change anything in your setup?

[fluppie]

The only command that I've ran: sudo hassbian-config upgrade homeassistant I'll go to my electrical board and power cycle the KNX bus to make sure it's not a coincidence.

[fluppie]

After power cycling the KNX bus and interface, it's partially working, but still not like it did before.

2019-01-27 23:04:51 ERROR (MainThread) [xknx.log] Error while syncing device: <CouldNotParseTelegram description="payload invalid" device_name="Verwarming terras 1e" group_address="1/0/103" payload=""/> 2019-01-27 23:08:41 WARNING (MainThread) [xknx.log] Error: reading rading group address from KNX bus failed: ErrorCode.E_CONNECTION_ID 2019-01-27 23:08:56 WARNING (MainThread) [xknx.log] Error: reading rading group address from KNX bus failed: ErrorCode.E_CONNECTION_ID

Error: reading rading group address from KNX bus failed: ErrorCode.E_CONNECTIONID 23:09 util/async.py (WARNING) Heartbeat failed - reconnecting 23:09 util/async_.py (WARNING) Error: reading rading group address from KNX bus failed: ErrorCode.E_CONNECTIONID 23:09 util/async.py (WARNING) Error: reading rading group address from KNX bus failed: ErrorCode.E_CONNECTIONID 23:09 util/async.py (WARNING) Error: reading rading group address from KNX bus failed: ErrorCode.E_CONNECTIONID 23:08 util/async.py (WARNING) Error: reading rading group address from KNX bus failed: ErrorCode.E_CONNECTIONID 23:08 util/async.py (WARNING) Error while syncing device: <CouldNotParseTelegram description="payload invalid" device_name="Verwarming terras 1e" groupaddress="1/0/103" payload=""/> 23:04 util/async.py (ERROR)

[stale[bot]]

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.