HA 0.90.2 / 0.91.0: Setup of knx component is failing

Configuration
1

After an update from 0.89.2 to 0.90.2, the knx component fails to initialize:

2019-04-03 15:50:33 ERROR (MainThread) [homeassistant.setup] Error during setup of component knx
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/homeassistant/setup.py", line 151, in _async_setup_component
    hass, processed_config)
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/knx/__init__.py", line 86, in async_setup
    hass.data[DATA_KNX] = KNXModule(hass, config)
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/knx/__init__.py", line 137, in __init__
    self.init_xknx()
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/knx/__init__.py", line 145, in init_xknx
    rate_limit=self.config[DOMAIN][CONF_KNX_RATE_LIMIT])
TypeError: __init__() got an unexpected keyword argument 'rate_limit'

In the change log I saw, that rate_limit is a new optional configuration option for the knx component. Configuring it explicitly doesn’t help:

knx:
  rate_limit: 20
  tunneling:
    host: '192.168.4.221'
    port: 3671
    local_ip: '192.168.4.5'
  fire_event: True
  fire_event_filter: ["3/3/16"]

The error message reads, as if rate_limit was implemented only partly or if some parts of the xknx component aren’t properly updated in the HA RPi docker image (homeassistant/raspberrypi3-homeassistant:0.90.2), but then it shouldn’t work for anybody using this image.

Is there anything simple I’m missing? Is this a known issue?

2

Well, I hoped that this would only be a problem of a faulty docker image for version 0.90.2, but knx platform setup is failing with v0.91 as well.

If there’s still no one who could give me a hint, what I’m missing here (anything wrong with my config or a breaking change I missed), I’ll have to consider this a bug in the knx implementation.

I still wonder, if anybody except me also has this problem, as there are a couple of users in this forum also using the knx component… :thinking:

3

Well… Problem solved.

Some time ago I hacked a quick & dirty support for DPT16.000 sensors directly into the xknx component inside my local HA docker container.

Today I noticed, that my DPT16.000 sensors still worked magically, even with newly created containers definitely not containing my extensions to the component.

After a bit more digging into the issue I discovered, that HA obviously grabbed some files from a backup of the site-package xknx folder I copied to /config/xknx/ before updating the container and mixed them up with the files coming with the new container. This obviously led to the knx component initialization error at startup.

I have no clue, why files from the config root folder can supersede site-packages files coming with the installation. I’d consider this a bug, but I still wouldn’t rule out completely that I’m just missing something…