KNXD add-on: convert your KNX-USB interface into an IP interface that can be used by HA

Does this combination support extended frames?

I use TPUART USB Modul from busware: busware.de : TUL

It’s using the NCN5130 transceiver and like it is written here NCN5130, it supports extended frames.

Do you think its just not transmitting extended frames? Can I configure this behaviour?

Hello there :slight_smile:

I am using the TPUART USB Modul from busware.de. It was working well for quite a while, but suddenly it stopped. So the problem I have is, that I am not longer able to program devices via ETS6 → knxd (with the help of the TPUART stick). The task is starting, but then it seems there’s appearing a timeout and it’s canceled…

The logs are showing the following:

[12:39:19] INFO: Interface:      tpuart
[12:39:19] INFO: Device:         /dev/ttyACM0
[12:39:19] INFO: Address:        1.1.0
[12:39:19] INFO: Client Address: 1.1.75:5
[12:39:19] INFO: Filters:        single
[12:39:19] INFO: Log-Level:      debug
[12:39:19] INFO: IP-Address:     
[12:39:19] INFO: Dest-Port:      99
s6-rc: info: service init-knxd-config successfully started
s6-rc: info: service svc-knxd: starting
s6-rc: info: service svc-knxd successfully started
s6-rc: info: service legacy-services: starting
I00000131: [ 1:main] 0.14.63: knxd /etc/knxd.ini
I00000129: [ 1:main] Connected: cfg:interface-tpuart.
I00000129: [ 1:main] Connected: cfg:A.tcp.
I00000129: [ 1:main] Connected: cfg:server.
W00000126: [ 1:main] knxd should not run as root
N00000127: [23:router.pace_] The 'pace' filter without a queue acts globally.
W00000116: [18:interface-tpuart] TPUART error state x17
W00000115: [20:tpuart.retry_] spurious send_Next
W00000117: [18:interface-tpuart] TPUART state wait should not happen
s6-rc: info: service legacy-services successfully started

Unfortunately, I don’t know where the problem lies, because these problems came out of nothing. Maybe you can give me a valuable hint in the right direction. I already re-installed the software, bought a knew TPUART stick and changed the KNX-cable. Nothing changed…

Well, I found the problem of this behavior. In my case, the Add-on “RaspberryMatic” caused the issues. It seems, a same port is used or something like this. I’m not yet sure about it and don’t have a solution yet for using both Add-ons together - but knxd is working fine again :partying_face:

I using Home Assistant Operating System 13.2 and could not make it work.
Show error:

[20:51:16] INFO: Interface:      tpuart
[20:51:16] INFO: Device:         /dev/ttyAMA0
[20:51:16] INFO: Address:        0.0.1
[20:51:16] INFO: Client Address: 0.0.2:8
[20:51:16] INFO: Filters:        single
[20:51:16] INFO: Log-Level:      warning
[20:51:16] INFO: IP-Address:     
[20:51:16] INFO: Dest-Port:      99
s6-rc: info: service init-knxd-config successfully started
s6-rc: info: service svc-knxd: starting
s6-rc: info: service svc-knxd successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
F00000105: [15:interface-tpuart] Link down, terminating

Also see error report here but not fix: After update to 11.2 KNXD Add On on /dev/ttyAMA0 stopped working · Issue #2966 · home-assistant/operating-system · GitHub

I try install on Raspbian Bookworm and it working but not with HAOS.