Ankündigung

**ITler** · 21.03.2016, 16:19

Zitat von snowdd Beitrag anzeigen

Hast Du den (neueren) conn_sep branch benutzt? Da ist derzeit ein bug drin, mit dem Master-Branch funktioniert es bei mir tadellos.

Habe den Fehler im Quellcode gefunden. Die Ausgabe wurde gecacht, weshalb mein nachgelagertes Script die Daten nicht sofort bekommen hat. Ich habe ein stdout.flush() ergänzt und seither funktioniert es prima.

**grisu911** · 29.03.2016, 08:39

Hallo,

ich bekomme knxd einfach nicht zum laufen. Habe es nach der Beschreibung installiert:
https://github.com/smarthomeNG/smart...tallation_knxd
Die Zeile:

Code:

 
 KNXD_OPTS=="-u /tmp/eib -u /var/run/knx -i -b ipt:192.168.188.XX"

ist entsprechend angepasst auf meine Weinzel 730

Code:

 
 KNXD_OPTS=="-u /tmp/eib -u /var/run/knx -i -b ipt:192.168.178.202"

Leider startet knxd nicht mit folgender Fehlermeldung:

Code:

pi@raspberrypi:~ $ sudo /etc/init.d/knxd start
[....] Starting knxd (via systemctl): knxd.serviceJob for knxd.service failed. See 'systemctl status knxd.service' and 'journalctl -xn' for details.
 failed!

Kann mir vielleicht jemand helfen wie ich das zum laufen bekomme bzw. wie ich eingrenzen kann wo der Fehler lliegt.

Gruß Grisu

**ITler** · 29.03.2016, 08:46

Hallo Grisu, welche Distribution / Version hast auf deinem Pi und welche Conf wurde angepasst?

**cmalo** · 29.03.2016, 08:48

Schau mal was da oben steht.

Zitat von grisu911 Beitrag anzeigen

See 'systemctl status knxd.service' and 'journalctl -xn' for details.

Ruf mal die Befehle auf:

Code:

systemctl status knxd.service
journalctl -xn

**grisu911** · 29.03.2016, 08:55

Code:

pi@raspberrypi:~ $ systemctl status knxd.service
● knxd.service - KNX Daemon
   Loaded: loaded (/lib/systemd/system/knxd.service; enabled)
   Active: activating (auto-restart) (Result: exit-code) since Di 2016-03-29 01:                13:43 CEST; 1s ago
  Process: 787 ExecStart=/usr/bin/knxd $KNXD_OPTS (code=exited, status=1/FAILURE                )
 Main PID: 787 (code=exited, status=1/FAILURE)

Code:

pi@raspberrypi:~ $ journalctl -xn
No journal files were found.

Hier die Ausgaben.

**eib1607** · 29.03.2016, 09:01

hi,
mach mal noch die option -t 65535 (->hoher loglevel) rein und schau mal in die datei /var/log/syslog (tail -f /var/log/syslog) da stehen die traceausgaben von knxd drin.

vielleicht kommen da mehr infos an.

**cmalo** · 29.03.2016, 09:10

Ruf den knxd mal bitte auf der Commandline auf:

Code:

sudo /usr/bin/knxd  -u /tmp/eib -u /var/run/knx -i -b ipt:192.168.178.202

**grisu911** · 29.03.2016, 12:35

Code:

pi@raspberrypi:~ $ sudo /usr/bin/knxd  -u /tmp/eib -u /var/run/knx -i -b ipt:192.168.178.202
E00000013: OpenInetSocket 6720: bind: Address already in use
initialisation of the knxd inet protocol failed: Address already in use

im syslog ist folgendes zu finden:

Code:

Mar 29 04:49:20 raspberrypi systemd[1]: Starting KNX Daemon...
Mar 29 04:49:20 raspberrypi knxd[6711]: E00000016: OpenLocalSocket /tmp/eib: bind: Address already in use
Mar 29 04:49:20 raspberrypi systemd[1]: knxd.service: main process exited, code=exited, status=1/FAILURE
Mar 29 04:49:20 raspberrypi knxd[6711]: initialisation of the knxd unix protocol failed: Address already in use
Mar 29 04:49:20 raspberrypi systemd[1]: Failed to start KNX Daemon.
Mar 29 04:49:20 raspberrypi systemd[1]: Unit knxd.service entered failed state.

Nach einfügen der Option: -t 65535 kommt gleiches Ergebnis:

Code:

 
 pi@raspberrypi:~ $ sudo /etc/init.d/knxd start [....] Starting knxd (via systemctl): knxd.serviceJob for knxd.service failed. See 'systemctl status knxd.service' and 'journalctl -xn' for details.  failed!

**grisu911** · 29.03.2016, 12:47

Hallo,
sehr gerade das anscheinend bei den installation was schief gegangen sein muss:

Code:

pi@raspberrypi:~ $ sudo apt-get upgrade
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Paketaktualisierung (Upgrade) wird berechnet... Fertig
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
1 nicht vollständig installiert oder entfernt.
Nach dieser Operation werden 0 B Plattenplatz zusätzlich benutzt.
Möchten Sie fortfahren? [J/n] j
knxd (0.10.13-3) wird eingerichtet ...
addgroup: Die Gruppe »knxd« existiert bereits als Systemgruppe. Programmende.
Warnung: Das von Ihnen angegebene Home-Verzeichnis /var/lib/knxd existiert bereits.
Der Systembenutzer »knxd« existiert bereits. Programmende.
Job for knxd.service failed. See 'systemctl status knxd.service' and 'journalctl -xn' for details.
Job for knxd.service failed. See 'systemctl status knxd.service' and 'journalctl -xn' for details.
invoke-rc.d: initscript knxd, action "start" failed.
dpkg: Fehler beim Bearbeiten des Paketes knxd (--configure):
 Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
E: Sub-process /usr/bin/dpkg returned an error code (1)

Oder???

**cmalo** · 29.03.2016, 12:57

Der knxd läuft bereits(OpenInetSocket 6720: bind: Address already in use).
Jetzt sehe ich gerade, dass Du

Code:

sudo /etc/init.d/knxd start

aufgerufen hast. In der Anleitung steht nichts davon. Das brauchst du auch nicht, da der knxd als socketdeamon konfiguriert ist.
Mit dem Befehl kannst du den Status Prüfen:

Code:

systemctl status knxd.socket

**grisu911** · 29.03.2016, 13:31

Code:

pi@raspberrypi:~ $ systemctl status knxd.socket
● knxd.socket - KNX Daemon (socket)
   Loaded: loaded (/lib/systemd/system/knxd.socket; enabled)
   Active: active (running) since Di 2016-03-29 14:16:41 CEST; 1min 46s ago
   Listen: /var/run/knx (Stream)
           [::]:6720 (Stream)

In der syslog sind trotzdem alle 10s folgende Einträge zu finden:

Code:

Mar 29 14:22:59 raspberrypi systemd[1]: Starting KNX Daemon...
Mar 29 14:22:59 raspberrypi knxd[945]: E00000016: OpenLocalSocket /var/run/knx: bind: Address already in use
Mar 29 14:22:59 raspberrypi knxd[945]: initialisation of the knxd unix protocol failed: Address already in use
Mar 29 14:22:59 raspberrypi systemd[1]: knxd.service: main process exited, code=exited, status=1/FAILURE
Mar 29 14:22:59 raspberrypi systemd[1]: Failed to start KNX Daemon.
Mar 29 14:22:59 raspberrypi systemd[1]: Unit knxd.service entered failed state.
Mar 29 14:23:09 raspberrypi systemd[1]: knxd.service holdoff time over, scheduling restart.
Mar 29 14:23:09 raspberrypi systemd[1]: Stopping KNX Daemon...
Mar 29 14:23:09 raspberrypi systemd[1]: Starting KNX Daemon...
Mar 29 14:23:09 raspberrypi rsyslogd-2007: action 'action 17' suspended, next retry is Tue Mar 29 14:23:39 2016 [try http://www.rsyslog.com/e/2007 ]
Mar 29 14:23:09 raspberrypi knxd[953]: E00000016: OpenLocalSocket /var/run/knx: bind: Address already in use
Mar 29 14:23:09 raspberrypi knxd[953]: initialisation of the knxd unix protocol failed: Address already in use
Mar 29 14:23:09 raspberrypi systemd[1]: knxd.service: main process exited, code=exited, status=1/FAILURE
Mar 29 14:23:09 raspberrypi systemd[1]: Failed to start KNX Daemon.
Mar 29 14:23:09 raspberrypi systemd[1]: Unit knxd.service entered failed state.
Mar 29 14:23:20 raspberrypi systemd[1]: knxd.service holdoff time over, scheduling restart.
Mar 29 14:23:20 raspberrypi systemd[1]: Stopping KNX Daemon...
Mar 29 14:23:20 raspberrypi systemd[1]: Starting KNX Daemon...
Mar 29 14:23:20 raspberrypi knxd[956]: E00000016: OpenLocalSocket /var/run/knx: bind: Address already in use
Mar 29 14:23:20 raspberrypi knxd[956]: initialisation of the knxd unix protocol failed: Address already in use
Mar 29 14:23:20 raspberrypi systemd[1]: knxd.service: main process exited, code=exited, status=1/FAILURE
Mar 29 14:23:20 raspberrypi systemd[1]: Failed to start KNX Daemon.
Mar 29 14:23:20 raspberrypi systemd[1]: Unit knxd.service entered failed state.

Auf groupwrite muss mit ctrl + c abgebrochen werden:

Code:

pi@raspberrypi:~ $ knxtool groupwrite ip:127.0.0.1 1/1/0 1
^C

**eib1607** · 29.03.2016, 15:40

hi,
nehme mal die option -i raus die ist bei systemd obsolet.

**grisu911** · 29.03.2016, 18:30

Option -i ist jetzt raus, ändert aber an den Zustand nichts.

Gruß Grisu

**eib1607** · 30.03.2016, 06:02

Ich habe bei mir 2 Raspi 2 laufen einer mit siemens bcu startparameter

KNXD_OPTS=" -e 1.1.251 -t 65535 -D -T -R -S -c tpuarts:/dev/ttyAMA0"
und der zweite greift auf meine ip scnittstelle Wago 750 zu

KNXD_OPTS=" -e 1.1.249 -t 65535 -D -T -R -S -c ipt:192.168.0.27"

probiers doch mal mit meinen configs musst natürlich deine ip einstellen.

**grisu911** · 30.03.2016, 20:14

knxd scheint mit:

Code:

KNXD_OPTS=" -e 1.1.249 -t 65535 -D -T -R -S -c ipt:192.168.178.202"

zu laufen.

Code:

pi@raspberrypi:~ $ /etc/init.d/knxd status
● knxd.service - KNX Daemon
   Loaded: loaded (/lib/systemd/system/knxd.service; enabled)
   Active: deactivating (stop-sigterm)
  Process: 804 ExecStart=/usr/bin/knxd $KNXD_OPTS (code=exited, status=0/SUCCESS)
 Main PID: 804 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/knxd.service
           └─805 /usr/bin/knxd -e 1.1.249 -t 65535 -d /var/log/knxd.log -D -T -R -S -c ipt:192.168.178.2...

bzw.

Code:

pi@raspberrypi:~ $ systemctl status knxd.service
● knxd.service - KNX Daemon
   Loaded: loaded (/lib/systemd/system/knxd.service; enabled)
   Active: deactivating (stop-sigterm)
  Process: 836 ExecStart=/usr/bin/knxd $KNXD_OPTS (code=exited, status=0/SUCCESS)
 Main PID: 836 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/knxd.service
           └─837 /usr/bin/knxd -e 1.1.249 -t 65535 -d /var/log/knxd.log -D -T -R -S -c ipt:192.168.178.2...

Trotzdem kann ich nicht schalten.

Im Log befinden sich folgende Angaben:
syslog:

Code:

Mar 30 21:03:12 raspberrypi systemd[1]: knxd.service stop-sigterm timed out. Killing.
Mar 30 21:03:12 raspberrypi systemd[1]: Failed to start KNX Daemon.
Mar 30 21:03:12 raspberrypi systemd[1]: Unit knxd.service entered failed state.
Mar 30 21:03:22 raspberrypi systemd[1]: knxd.service holdoff time over, scheduling restart.
Mar 30 21:03:22 raspberrypi systemd[1]: Stopping KNX Daemon...
Mar 30 21:03:22 raspberrypi systemd[1]: Starting KNX Daemon...
Mar 30 21:03:22 raspberrypi systemd[1]: knxd.service: Got notification message from PID 805, but reception only permitted for main PID 804
Mar 30 21:03:22 raspberrypi knxd[804]: Layer 3(00E5FC60,56FC22FA) Open
Mar 30 21:03:22 raspberrypi knxd[804]: Layer 8(00E701E0,56FC22FA) Open
Mar 30 21:03:22 raspberrypi knxd[804]: Layer 0(00E70688,56FC22FA) Open
Mar 30 21:03:22 raspberrypi knxd[804]: Layer 0(00E70688,56FC22FA) Openend
Mar 30 21:03:22 raspberrypi knxd[804]: Layer 8(00E701E0,56FC22FA) Opened
Mar 30 21:03:22 raspberrypi rsyslogd-2007: action 'action 17' suspended, next retry is Wed Mar 30 21:03:52 2016 [try http://www.rsyslog.com/e/2007 ]
Mar 30 21:03:22 raspberrypi knxd[804]: Layer 3(00E5FC60,56FC22FA) registerLayer2 00E70208
Mar 30 21:03:22 raspberrypi knxd[804]: Layer 3(00E5FC60,56FC22FA) registerLayer2 00E70208 = 1
Mar 30 21:03:22 raspberrypi knxd[804]: Layer 4(00E910C0,56FC22FA) GroupCacheInit
Mar 30 21:03:22 raspberrypi knxd[804]: Layer 3(00E5FC60,56FC22FA) registerLayer2 00E910C0
Mar 30 21:03:22 raspberrypi knxd[804]: Layer 3(00E5FC60,56FC22FA) registerLayer2 00E910C0 = 1
Mar 30 21:03:22 raspberrypi knxd[804]: Layer 4(00E910C0,56FC22FA) GroupCacheEnable
Mar 30 21:03:22 raspberrypi knxd[804]: Layer 2(00E91330,56FC22FA) Open
Mar 30 21:03:22 raspberrypi knxd[804]: Layer 0(00E913F8,56FC22FA) Open
Mar 30 21:03:22 raspberrypi knxd[804]: Layer 0(00E913F8,56FC22FA) Openend
Mar 30 21:03:22 raspberrypi knxd[804]: Layer 2(00E91330,56FC22FA) Opened
Mar 30 21:03:22 raspberrypi knxd[804]: Layer 3(00E5FC60,56FC22FA) registerLayer2 00E91330
Mar 30 21:03:22 raspberrypi knxd[804]: Layer 3(00E5FC60,56FC22FA) registerLayer2 00E91330 = 1
Mar 30 21:03:22 raspberrypi knxd[804]: Layer 8(00EB1E60,56FC22FA) OpenSystemdSocket
Mar 30 21:03:22 raspberrypi knxd[804]: Layer 8(00EB1E60,56FC22FA) SystemdSocket opened
Mar 30 21:03:22 raspberrypi knxd[804]: Layer 8(00EC23B8,56FC22FA) OpenSystemdSocket
Mar 30 21:03:22 raspberrypi knxd[804]: Layer 8(00EC23B8,56FC22FA) SystemdSocket opened
Mar 30 21:04:52 raspberrypi systemd[1]: knxd.service stop-sigterm timed out. Killing.
Mar 30 21:04:52 raspberrypi rsyslogd-2007: action 'action 17' suspended, next retry is Wed Mar 30 21:05:22 2016 [try http://www.rsyslog.com/e/2007 ]
Mar 30 21:04:52 raspberrypi systemd[1]: Failed to start KNX Daemon.
Mar 30 21:04:52 raspberrypi systemd[1]: Unit knxd.service entered failed state.
Mar 30 21:05:03 raspberrypi systemd[1]: knxd.service holdoff time over, scheduling restart.
Mar 30 21:05:03 raspberrypi systemd[1]: Stopping KNX Daemon...
Mar 30 21:05:03 raspberrypi systemd[1]: Starting KNX Daemon...
Mar 30 21:05:03 raspberrypi knxd[836]: Layer 3(01F5EC60,56FC235F) Open
Mar 30 21:05:03 raspberrypi knxd[836]: Layer 8(01F6F1E0,56FC235F) Open
Mar 30 21:05:03 raspberrypi knxd[836]: Layer 0(01F6F688,56FC235F) Open
Mar 30 21:05:03 raspberrypi knxd[836]: Layer 0(01F6F688,56FC235F) Openend
Mar 30 21:05:03 raspberrypi knxd[836]: Layer 8(01F6F1E0,56FC235F) Opened
Mar 30 21:05:03 raspberrypi knxd[836]: Layer 3(01F5EC60,56FC235F) registerLayer2 01F6F208
Mar 30 21:05:03 raspberrypi knxd[836]: Layer 3(01F5EC60,56FC235F) registerLayer2 01F6F208 = 1
Mar 30 21:05:03 raspberrypi knxd[836]: Layer 4(01F900C0,56FC235F) GroupCacheInit
Mar 30 21:05:03 raspberrypi knxd[836]: Layer 3(01F5EC60,56FC235F) registerLayer2 01F900C0
Mar 30 21:05:03 raspberrypi knxd[836]: Layer 3(01F5EC60,56FC235F) registerLayer2 01F900C0 = 1
Mar 30 21:05:03 raspberrypi knxd[836]: Layer 4(01F900C0,56FC235F) GroupCacheEnable
Mar 30 21:05:03 raspberrypi knxd[836]: Layer 2(01F90330,56FC235F) Open
Mar 30 21:05:03 raspberrypi knxd[836]: Layer 0(01F903F8,56FC235F) Open
Mar 30 21:05:03 raspberrypi knxd[836]: Layer 0(01F903F8,56FC235F) Openend
Mar 30 21:05:03 raspberrypi knxd[836]: Layer 2(01F90330,56FC235F) Opened
Mar 30 21:05:03 raspberrypi knxd[836]: Layer 3(01F5EC60,56FC235F) registerLayer2 01F90330
Mar 30 21:05:03 raspberrypi knxd[836]: Layer 3(01F5EC60,56FC235F) registerLayer2 01F90330 = 1
Mar 30 21:05:03 raspberrypi knxd[836]: Layer 8(01FB0E60,56FC235F) OpenSystemdSocket
Mar 30 21:05:03 raspberrypi knxd[836]: Layer 8(01FB0E60,56FC235F) SystemdSocket opened
Mar 30 21:05:03 raspberrypi knxd[836]: Layer 8(01FC13B8,56FC235F) OpenSystemdSocket
Mar 30 21:05:03 raspberrypi knxd[836]: Layer 8(01FC13B8,56FC235F) SystemdSocket opened
Mar 30 21:05:03 raspberrypi systemd[1]: knxd.service: Got notification message from PID 837, but reception only permitted for main PID 836
Mar 30 21:05:22 raspberrypi ntpd[569]: clock is now synced
Mar 30 21:05:22 raspberrypi rsyslogd-2007: action 'action 17' suspended, next retry is Wed Mar 30 21:05:52 2016 [try http://www.rsyslog.com/e/2007 ]
Mar 30 21:06:33 raspberrypi systemd[1]: knxd.service stop-sigterm timed out. Killing.
Mar 30 21:06:33 raspberrypi rsyslogd-2007: action 'action 17' suspended, next retry is Wed Mar 30 21:07:03 2016 [try http://www.rsyslog.com/e/2007 ]
Mar 30 21:06:33 raspberrypi systemd[1]: Failed to start KNX Daemon.
Mar 30 21:06:33 raspberrypi systemd[1]: Unit knxd.service entered failed state.
Mar 30 21:06:43 raspberrypi systemd[1]: knxd.service holdoff time over, scheduling restart.
Mar 30 21:06:43 raspberrypi systemd[1]: Stopping KNX Daemon...
Mar 30 21:06:43 raspberrypi systemd[1]: Starting KNX Daemon...

knxd.log:

Code:

Layer 1(0089C330,56FC23D7) Connect failed with error 24
Layer 1(0089C330,56FC23E1) Connectretry
Layer 1(0089C3F8,56FC23E1) Send(020): 08 01 C0 A8 B2 29 0E 58 08 01 C0 A8 B2 29 0E 58 04 04 02 00
Layer 0(0089C3F8,56FC23E1) Send(026): 06 10 02 05 00 1A 08 01 C0 A8 B2 29 0E 58 08 01 C0 A8 B2 29 0E 58 04 04 02 00
Layer 0(0089C3F8,56FC23E1) Recv(008): 06 10 02 06 00 08 00 24
Layer 1(0089C3F8,56FC23E1) Recv(002): 00 24
Layer 1(0089C330,56FC23E1) Connect failed with error 24
Layer 1(0089C330,56FC23EB) Connectretry
Layer 1(0089C3F8,56FC23EB) Send(020): 0Layer 3(012B5C60,56FC2428) Open
Layer 8(012C61E0,56FC2428) Open
Layer 0(012C6688,56FC2428) Open
Layer 0(012C6688,56FC2428) Openend
Layer 8(012C61E0,56FC2428) Opened
Layer 3(012B5C60,56FC2428) registerLayer2 012C6208
Layer 3(012B5C60,56FC2428) registerLayer2 012C6208 = 1
Layer 4(012E70C0,56FC2428) GroupCacheInit
Layer 3(012B5C60,56FC2428) registerLayer2 012E70C0
Layer 3(012B5C60,56FC2428) registerLayer2 012E70C0 = 1
Layer 4(012E70C0,56FC2428) GroupCacheEnable
Layer 2(012E7330,56FC2428) Open
Layer 0(012E73F8,56FC2428) Open
Layer 0(012E73F8,56FC2428) Openend
Layer 2(012E7330,56FC2428) Opened
Layer 3(012B5C60,56FC2428) registerLayer2 012E7330
Layer 3(012B5C60,56FC2428) registerLayer2 012E7330 = 1
Layer 8(01307E60,56FC2428) OpenSystemdSocket
Layer 8(01307E60,56FC2428) SystemdSocket opened
Layer 8(013183B8,56FC2428) OpenSystemdSocket
Layer 8(013183B8,56FC2428) SystemdSocket opened
Layer 3(012B5C60,56FC2428) L3 started
Layer 1(012E73F8,56FC2428) Send(020): 08 01 C0 A8 B2 29 0E 58 08 01 C0 A8 B2 29 0E 58 04 04 02 00
Layer 8(013183B8,56FC2428) New Connection
Layer 8(013299B8,56FC2428) ClientConnection Init
Layer 8(013299B8,56FC2428) RecvMessage(002): 00 70
Layer 4(012E70C0,56FC2428) GroupCacheEnable
Layer 8(013299B8,56FC2428) SendMessage(002): 00 70
Layer 8(013299B8,56FC2428) RecvMessage(005): 00 26 00 00 00
Layer 7(01339E74,56FC2428) OpenGroupSocket
Layer 4(0133A340,56FC2428) OpenGroupSocket RW
Layer 3(012B5C60,56FC2428) registerLayer2 0133A340
Layer 3(012B5C60,56FC2428) registerLayer2 0133A340 = 1
Layer 7(01339E74,56FC2428) OpenGroupSocket complete
Layer 8(013299B8,56FC2428) SendMessage(002): 00 26
Layer 0(012E73F8,56FC2428) Send(026): 06 10 02 05 00 1A 08 01 C0 A8 B2 29 0E 58 08 01 C0 A8 B2 29 0E 58 04 04 02 00
Layer 0(012E73F8,56FC2428) Recv(008): 06 10 02 06 00 08 00 24
Layer 1(012E73F8,56FC2428) Recv(002): 00 24
Layer 1(012E7330,56FC2428) Connect failed with error 24
Layer 1(012E7330,56FC2432) Connectretry
Layer 1(012E73F8,56FC2432) Send(020): 08 01 C0 A8 B2 29 0E 58 08 01 C0 A8 B2 29 0E 58 04 04 02 00
Layer 0(012E73F8,56FC2432) Send(026): 06 10 02 05 00 1A 08 01 C0 A8 B2 29 0E 58 08 01 C0 A8 B2 29 0E 58 04 04 02 00
Layer 0(012E73F8,56FC2432) Recv(008): 06 10 02 06 00 08 00 24
Layer 1(012E73F8,56FC2432) Recv(002): 00 24
Layer 1(012E7330,56FC2432) Connect failed with error 24
Layer 1(012E7330,56FC243C) Connectretry
Layer 1(012E73F8,56FC243C) Send(020): 08 01 C0 A8 B2 29 0E 58 08 01 C0 A8 B2 29 0E 58 04 04 02 00
Layer 0(012E73F8,56FC243C) Send(026): 06 10 02 05 00 1A 08 01 C0 A8 B2 29 0E 58 08 01 C0 A8 B2 29 0E 58 04 04 02 00
Layer 0(012E73F8,56FC243C) Recv(008): 06 10 02 06 00 08 00 24
Layer 1(012E73F8,56FC243C) Recv(002): 00 24
Layer 1(012E7330,56FC243C) Connect failed with error 24
Layer 1(012E7330,56FC2446) Connectretry
Layer 1(012E73F8,56FC2446) Send(020): 08 01 C0 A8 B2 29 0E 58 08 01 C0 A8 B2 29 0E 58 04 04 02 00
Layer 0(012E73F8,56FC2446) Send(026): 06 10 02 05 00 1A 08 01 C0 A8 B2 29 0E 58 08 01 C0 A8 B2 29 0E 58 04 04 02 00
Layer 0(012E73F8,56FC2446) Recv(008): 06 10 02 06 00 08 00 24
Layer 1(012E73F8,56FC2446) Recv(002): 00 24
Layer 1(012E7330,56FC2446) Connect failed with error 24
Layer 8(013299B8,56FC244E) RecvMessage(009): 00 27 38 00 00 80 75 09 02
Layer 7(01339E74,56FC244E) Send(005): 00 80 75 09 02
Layer 4(0133A340,56FC244E) Send GroupSocket T_DATA_XXX_REQ A_GroupValue_Write 75 09 02
Layer 3(012B5C60,56FC244E) Enqueue L_Data low from 0.0.0 to 7/0/0 hops: 07 T_DATA_XXX_REQ A_GroupValue_Write 75 09 02
Layer 3(012B5C60,56FC244E) RecvData L_Data low from 0.0.0 to 7/0/0 hops: 06 T_DATA_XXX_REQ A_GroupValue_Write 75 09 02
Layer 8(012C61E0,56FC244E) Send_Route L_Data low from 1.1.249 to 7/0/0 hops: 06 T_DATA_XXX_REQ A_GroupValue_Write 75 09 02
Layer 1(012C6688,56FC244E) Send(014): 29 00 BC E0 11 F9 38 00 04 00 80 75 09 02
Layer 0(012C6688,56FC244E) Send(020): 06 10 05 30 00 14 29 00 BC E0 11 F9 38 00 04 00 80 75 09 02
Layer 2(012E7330,56FC244E) Send L_Data low from 1.1.249 to 7/0/0 hops: 06 T_DATA_XXX_REQ A_GroupValue_Write 75 09 02
Layer 1(012E7330,56FC2450) Connectretry
Layer 1(012E73F8,56FC2450) Send(020): 0

Kann damit jemand was anfangen und mir weiter helfen???

Gruß Grisu

Ankündigung

eibd(war bcusdk) Fork -> knxd

Kommentar

Kommentar

Kommentar

Kommentar

Kommentar

Kommentar

Kommentar

Kommentar

Kommentar

Kommentar

Kommentar

Kommentar

Kommentar

Kommentar

Kommentar