Upgrading to 2022.11 remove route_back from config and my HA is out of service

Hi folks,

I did my annual upgrade, from 2021.11 to 2022.11 and the KNX integration is not working due to the migration from the configuration file to the Integration UI for the setup of the TCP/IP connection with KNX bus.
HA is running into a docker swarm cluster and the route_back: true is mantatory to able xknx to call with the KNX bus.
But route_back is not available in the Integration configuration UI, and the local_ip is mandatory whereas it is not true (with route_back: true, local_ip must not be provided).

Can you help me to solve this issue ?

Since the knx configuration is not in the configuration file, have you a workaround to manually update the configuration to add route_back: true into the xknx configuration ?

I tried with local_ip: 0.0.0.0, save result.

Logs from ha during startup:

home-assistant_service.1.8s8f592db8cp@node06rpi48    | 2022-11-05 21:31:49.617 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: knx
home-assistant_service.1.8s8f592db8cp@node06rpi48    | 2022-11-05 21:32:49.727 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: knx
home-assistant_service.1.8s8f592db8cp@node06rpi48    | 2022-11-05 21:33:04.208 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Tunneling @ 192.168.68.10 (TCP)' for knx integration not ready yet: Tunnel connection could not be established; Retrying in background

Kind ragards,

Laurent

It is. Select “Tunneling” and find it on the next page of the options flow.


Don’t manually mangle with the config entry :grimacing:

local_ip is used to select the used network interface if you have multiple. Set it to 0.0.0.0 - it should be fine (leaving blank isn’t possible in the flow so there is that workaround).

That said, HA should be run with net=host in Docker and nothing of that would be needed.

Thank you @farmio

I tried with 0.0.0.0 but it not changed it.
The net=host feature is not available on a Docker Swarm cluster, containers can run on various nodes of the cluster (I have 6 rpi on it).

route_back was added in xknx is release 0.17.0 to be able to manage the callback tcp host/port dynamically and it is working fine.

This parameter is still available in xknx library but not available in the new Integration setup UI.

Can I add the param into the ha database ?

In the details setup of the Tunneling, route_back is not here:

And the next page of the setup for tunneling too:

This is an explicit requirement for Home Assistant Container :person_shrugging:

No. route_back doesn’t have any effect on TCP connections. Thats a UDP only thing.
Maybe your interface just doesn’t support TCP (xknx didn’t support TCP before the shift to UI config in HA).

It’s the 3rd option :eyes:

Btw. this is not a good idea. In HA breaking changes should provide migrations for existing setups. These are usually kept 3 months before they are removed.

Thank you a lot @farmio :slight_smile:
I apology, my eyes didn’t see the “with route back” phrase on the 3rd setup and I was focus on tcp setup, but the tunneling mode is, you are right, throw udp.

So solved subjet, I hope this will help other people.

Kind regards,

1 Like