Tunnel connection timed out

[modir]

$ sudo knxmap -v  scan 192.168.1.36 1.1.1-1.1.10
[selector_events.py:59 -             __init__() ] Using selector: EpollSelector
[main.py:235 -                 main() ] Scanning 1 target(s)
[core.py:124 - _knx_description_worker() ] Scanning ('192.168.1.36', 3671)
[core.py:127 - _knx_description_worker() ] Sending 0. KnxDescriptionRequest to ('192.168.1.36', 3671)
[__init__.py:44 -        parse_message() ] Parsing KnxDescriptionResponse
[__init__.py:47 -        parse_message() ] Parsing KnxConnectResponse
[__init__.py:71 -        parse_message() ] Parsing KnxDeviceConfigurationAck
[__init__.py:68 -        parse_message() ] Parsing KnxDeviceConfigurationRequest
[__init__.py:71 -        parse_message() ] Parsing KnxDeviceConfigurationAck
[__init__.py:68 -        parse_message() ] Parsing KnxDeviceConfigurationRequest
[__init__.py:71 -        parse_message() ] Parsing KnxDeviceConfigurationAck
[__init__.py:68 -        parse_message() ] Parsing KnxDeviceConfigurationRequest
[__init__.py:71 -        parse_message() ] Parsing KnxDeviceConfigurationAck
[__init__.py:68 -        parse_message() ] Parsing KnxDeviceConfigurationRequest
[tunnel.py:67 -   connection_timeout() ] Tunnel connection timed out

Most of the command of knxmap do not work for me. I always get the "tunnel connection timed out". I am wondering if the problem is maybe with a library you are using which is not ready for python 3.8.

[takeshixx]

I cannot really tell you what's the problem, but indeed I guess it might be related to newer Python versions. When I was actively working on this project a couple of years ago, asyncio was still in early development stages. During that time, also a lot of API stuff changed. I assume after Python 3.4 even more asyncio-related code changed.

Maybe try running it with Python 3.4, e.g. via Docker (docker pull python:3.4). In case that works I could just add a Dockerfile. Unfortunately, I currently don't have a running KNX setup to test it myself.

[modir]

I installed now Python 3.4 and tested it. With 3.4 it works without any problems. So it must be indeed a problem with the newer version.
I could install python 3.4 on Fedora with sudo dnf install python3.4 and then activated an env with:

python3.4 -m venv env
source env/bin/activate

For me this works well. But true maybe it helps others if you add a Dockerfile.