If you feel the urge to update follow these steps: [B]sudo -i git clone [URL]https://github.com/knxd/knxd.git[/URL] cd /root/knxd dpkg-buildpackage -b -uc cd .. sudo dpkg -i knxd_*.deb knxd-tools_*.deb [/B]
[A.tpuarts] debug = debug-A.tpuarts device = /dev/ttyAMA0 driver = tpuart filters = log [debug-A.tpuarts] error-level = 0x9 trace-mask = 0x3ff [debug-server] name = mcast:knxd [main] addr = 1.1.254 client-addrs = 1.1.255:8 connections = server,A.tpuarts systemd = systemd [server] debug = debug-server discover = true router = router server = ets_router tunnel = tunnel
-- Unit knxd.service has begun starting up. Jan 06 22:41:03 SmartHomeNG knxd[1116]: E00000055: [ 1:main] There is no KNX addr= in section 'main'. Jan 06 22:41:03 SmartHomeNG knxd[1116]: F00000000: [ 1:main] Error setting up the KNX router. Jan 06 22:41:03 SmartHomeNG systemd[1]: knxd.service: Main process exited, code=exited, status=2/INVALIDARGUMENT Jan 06 22:41:03 SmartHomeNG systemd[1]: Failed to start KNX Daemon.
KNXD_OPTS="-e 1.1.254 -E 1.1.255:8 -D -T -R -S -f9 -B log -t 1023 -b tpuarts:/dev/ttyAMA0"
lrwxrwxrwx 1 root root 7 Jan 4 17:14 serial0 -> ttyAMA0
KNXD_OPTS="-DTRS -t 0xffc -f 9 -b tpuarts:/dev/ttyKNX1"
[B]/usr/lib/knxd_args [/B]-e 1.1.61 -E 1.1.62:8 -D -T -R -S -f9 -B log -t 1023 -b tpuarts:/dev/ttyAMA0
KNXD_OPTS=/etc/knxd.ini
systemctl stop knxd.socket systemctl stop knxd.service systemctl start knxd.socket systemctl start knxd.service
KNXD_OPTS="-e 1.1.61 -E 1.1.62:8 -D -T -R -S -f9 -B log -t 1023 -b tpuarts:/dev/ttyAMA0"
sudo systemctl disable serial-getty@ttyAMA0.service
ACTION=="add", SUBSYSTEM=="tty", ATTRS{id}=="00241011", KERNELS=="20201000.serial", SYMLINK+="ttyKNX1", OWNER="knxd"
[A.tpuarts] debug = debug-A.tpuarts device = /dev/ttyKNX1 driver = tpuart [debug-A.tpuarts] error-level = 0x9 trace-mask = 0xffc [debug-server] name = mcast:knxd [main] connections = server,A.tpuarts systemd = systemd [server] debug = debug-server discover = true router = router server = ets_router tunnel = tunnel
[smarthome@SmartHomeNG ~]$ sudo systemctl status knxd.service ● knxd.service - KNX Daemon Loaded: loaded (/lib/systemd/system/knxd.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Wed 2018-01-03 23:53:15 CET; 6s ago Process: 757 ExecStart=/usr/bin/knxd $KNXD_OPTS (code=exited, status=2) Main PID: 757 (code=exited, status=2) Jan 03 23:53:15 SmartHomeNG systemd[1]: Failed to start KNX Daemon. Jan 03 23:53:15 SmartHomeNG systemd[1]: knxd.service: Unit entered failed state. Jan 03 23:53:15 SmartHomeNG systemd[1]: knxd.service: Failed with result 'exit-code'.
KNXD_OPTS="-DTRS -t 0xffc -f 9 -b tpuarts:/dev/ttyKNX1" [A.tcp] server = knxd_tcp systemd-ignore = true [B.ipt] driver = ipt filters = C.pace ip-address = 10.0.0.101 [C.pace] delay = 30 filter = pace [main] addr = 1.1.75 client-addrs=1.1.76:8 cache = D.cache connections = A.tcp,B.ipt systemd = systemd
[smarthome@SmartHomeNG ~]$ sudo udevadm info -a /dev/ttyAMA0
Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/devices/platform/soc/20201000.serial/tty/ttyAMA0':
KERNEL=="ttyAMA0"
SUBSYSTEM=="tty"
DRIVER==""
ATTR{close_delay}=="50"
ATTR{closing_wait}=="3000"
ATTR{custom_divisor}=="0"
ATTR{flags}=="0x10000000"
ATTR{io_type}=="2"
ATTR{iomem_base}=="0x20201000"
ATTR{iomem_reg_shift}=="0"
ATTR{irq}=="81"
ATTR{line}=="0"
ATTR{port}=="0x0"
ATTR{type}=="32"
ATTR{uartclk}=="0"
ATTR{xmit_fifo_size}=="16"
looking at parent device '/devices/platform/soc/20201000.serial':
KERNELS=="20201000.serial"
SUBSYSTEMS=="amba"
DRIVERS=="uart-pl011"
ATTRS{driver_override}==""
ATTRS{id}=="00241011"
ATTRS{irq0}=="81"
looking at parent device '/devices/platform/soc':
KERNELS=="soc"
SUBSYSTEMS=="platform"
DRIVERS==""
ATTRS{driver_override}=="(null)"
looking at parent device '/devices/platform':
KERNELS=="platform"
SUBSYSTEMS==""
DRIVERS==""
EIB_ARGS="--daemon --Server --Tunnelling --Discovery --GroupCache --listen-tcp" EIB_ADDR="0.0.1" EIB_IF="tpuarts:/dev/ttyAMA0"
admin@smarthome:/$ sudo udevadm info -a --name=/dev/ttyAMA0
Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/devices/dev:f1/tty/ttyAMA0':
KERNEL=="ttyAMA0"
SUBSYSTEM=="tty"
DRIVER==""
ATTR{irq}=="83"
ATTR{line}=="0"
ATTR{port}=="0x0"
ATTR{type}=="32"
ATTR{flags}=="0x10002000"
ATTR{iomem_base}=="0x20201000"
ATTR{custom_divisor}=="0"
ATTR{iomem_reg_shift}=="0"
ATTR{uartclk}=="3000000"
ATTR{xmit_fifo_size}=="16"
ATTR{close_delay}=="50"
ATTR{closing_wait}=="3000"
ATTR{io_type}=="2"
looking at parent device '/devices/dev:f1':
KERNELS=="dev:f1"
SUBSYSTEMS=="amba"
DRIVERS=="uart-pl011"
ATTRS{id}=="00341011"
ATTRS{irq0}=="83"
Einen Kommentar schreiben: