KNXd installation

[Jojioe]

Hi! I am really struggling with configurating of KNXd in ARMbian, can anyone help me with my simple task?
I have a simple purpose: I need to connect my KNX bus to Home Assistant, but it only possible with KNX integration, which asks for IP router. And I only have knx USB-interface (IC-USB-S.1). So, as I undersand it, I can use my USB interface as IP router via KNXd.
I suppose I had succesfully installed KNXd on my Linux PC:
image.png
But I dont understand how to configure knxd.conf file:
image.png
Do I need to type something after "-b usb:" if I have only one usb-connection? Do I need to type -D -T -R -S and if that so where it suppose to be?
Sorry for newbee quastions but I am not much experienced

[Tru]

Hi, instead of editing the configuration file you my use knxd_args command (possibly in the libexc folder) with --help which will tell you all possible options. You may then add them to the KNXD_ARGS in the second line.
You need at least the -R -S options to create a router. the "-b usb:" should be enough to find the USB interface.

[Jojioe]

Hi, instead of editing the configuration file you my use knxd_args command (possibly in the libexc folder) with --help which will tell you all possible options. You may then add them to the KNXD_ARGS in the second line.
You need at least the -R -S options to create a router. the "-b usb:" should be enough to find the USB interface.

So many quastions...
How and where I need to type in "knxd_args --help" ?
I know that it depends on my distribution kit, but where about I can find "libexc folder"?
I've typed these flags, but nothing changed after reboot, am I doing something wrong?
image.png
If "-b usb:" is not enough, can I somehow manually type usb-interface in?
What device do I need? May the problem be in this second device? I suppose it is a powere supply via micro-usb and I didnt think about it
image.png
image.png

[Tru]

Using USB interface is not recommended with knxs generelly. It may work but there are bad experiences. Better use an IP interface.
If your knxd is installed as a RPM you may list the files in it and search for knxd_args. When using the install from the distro it should bin in the libexec subfolder (typo above).
The changes in the config file should get activated, you may check the process parameters. Otherwise find out which commands are active.
You use systemd - check the entries of the service file and find the process parameters.

[Jojioe]

Using USB interface is not recommended with knxs generelly. It may work but there are bad experiences. Better use an IP interface.
If your knxd is installed as a RPM you may list the files in it and search for knxd_args. When using the install from the distro it should bin in the libexec subfolder (typo above).
The changes in the config file should get activated, you may check the process parameters. Otherwise find out which commands are active.
You use systemd - check the entries of the service file and find the process parameters.

Right now I haven't oportunity of using IP interface and after research I found that knxd could help me, a lot of users have no problem with using it and I probably did a miskakes somewhere but I couldnt recognize where.
Found knxd_args, but "knxd_args --help" didn't work:
image.png
cd

you may check the process parameters

How?

[Tru]

Well, pretty basic level here. To overcome your problems using a shell:
cd /lib
./knxd_args
cd /usr/libexec
cd /usr
cd libexec

Checking process parameters:
ps -edf | grep knxd
ps aux | grep knxd

Talking about USB interface. It has technical limitaitions you it may work but it may not. If there is a single USB connection "-b usb:" shoud be enough otherwise you may have to find out the details. You also have to make sure no other process like getty is occupying the device. I'm no expert with that but there are many threads about checking that. There is also a short description on https://github.com/knxd/knxd

[Smurf]

Please copy/paste console texts instead of screenshotting!

Also, please learn what $PATH is for. root doesn't include the current directory there, for safety reasons (and neither should anybody else really). You need to use "./knxd_args".

[Jojioe]

Well, pretty basic level here. To overcome your problems using a shell:
cd /lib
./knxd_args
cd /usr/libexec
cd /usr
cd libexec

Checking process parameters:
ps -edf | grep knxd
ps aux | grep knxd

Talking about USB interface. It has technical limitaitions you it may work but it may not. If there is a single USB connection "-b usb:" shoud be enough otherwise you may have to find out the details. You also have to make sure no other process like getty is occupying the device. I'm no expert with that but there are many threads about checking that. There is also a short description on https://github.com/knxd/knxd

Thank you!
Thats what I get:

root@jethubj80:/lib# ./knxd_args
[main]
systemd = systemd

root@jethubj80:/usr/libexec# ps -edf | grep knxd
ps aux | grep knxd
knxd 2570 1 0 Feb22 ? 00:00:13 /usr/bin/knxd -e 1.1.255 -E 0.0.2:8 -u /tmp/eib -D -T -R -S -b usb:
root 147764 145325 0 16:59 pts/1 00:00:00 grep knxd
knxd 2570 0.0 0.2 18776 4252 ? Ss Feb22 0:13 /usr/bin/knxd -e 1.1.255 -E 0.0.2:8 -u /tmp/eib -D -T -R -S -b usb:
root 147766 0.0 0.0 5908 632 pts/1 S+ 16:59 0:00 grep knxd

[Jojioe]

Please copy/paste console texts instead of screenshotting!

Also, please learn what $PATH is for. root doesn't include the current directory there, for safety reasons (and neither should anybody else really). You need to use "./knxd_args".

Well, finally, with all your help (really, thank you all!), I have moved on, with these parametres:

# configuration for knxd.service
KNXD_OPTS="-e 0.0.1 -E 0.0.2:8 -u /tmp/eib -D -T -R -S -b usb:"

I see knxd interface now in ETS5:
image.pngBut the problem is that I cant load programm in knx device, I am starting full load, click the programing button on device but nothing happen, ETS5 keep asking for click the programing button on the device.
I am sure that 0.0.1 adress is NOT using in my setup, so, I think, maybe the problem is that I have second usb device:
root@jethubj80:~# lsusb
Bus 001 Device 002: ID 28c2:001f Module Electronics KNX-USB Inteface
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Maybe, if I manually type the correct usb device in -b usb: it will work?

[Jojioe]

So, there is no answer?

[Smurf]

Well the first question is whether "normal" KNX traffic works.

No your other USB interfaces are not the problem.

Programming device addresses via knxd may or may not work depending on the phase of the moon, or rather the ETS version. You're better off plugging the USB interface into the laptop that's running the ETS. Once the physical address is "programmed" the rest should work without problem.

Personally I always set the physaddr before ever connecting the device to the "real" bus, I have a separate system for that, just a small KNX power supply and the USB interface – that's all it's good for anyway, really. For stable productive use you're better off with an IP interface or a TPUART. These USB things are a 25+-year-old hack to avoid installing a device specific driver on whatever Windows version was current at the time, and the situation hasn't improved much since then.

[Jojioe]

Well the first question is whether "normal" KNX traffic works.

No your other USB interfaces are not the problem.

Programming device addresses via knxd may or may not work depending on the phase of the moon, or rather the ETS version. You're better off plugging the USB interface into the laptop that's running the ETS. Once the physical address is "programmed" the rest should work without problem.

Personally I always set the physaddr before ever connecting the device to the "real" bus, I have a separate system for that, just a small KNX power supply and the USB interface – that's all it's good for anyway, really. For stable productive use you're better off with an IP interface or a TPUART. These USB things are a 25+-year-old hack to avoid installing a device specific driver on whatever Windows version was current at the time, and the situation hasn't improved much since then.

I tried to load only an app (when the physical address is loaded) - there is no reaction.
I've scanned the line for devices with knxd ang got this:
image.png
image.png
I tried Realtek just in case, but there is no big difference:
image.png
image.png
With direct connection to my PC everything is ok and i see all my devices:
image.png
image.png
And with direct connection I can download apps, everything is fine.