knxd empfängt nur noch Daten, sendet aber keine mehr

[chris5020]

ok, war vielleicht schlecht geschrieben, das Problem hat nix mit dem Wiregate zu tun, sondern tritt auch auf, wenn man statt dem wiregate ein normales IP-Interface nimmt.

Bei dem Projekt, um das es hier geht, habe ich leider kein Wiregate, da muss eben ein kleiner Raspi als Schnittstelle herhalten

[Intenos]

Hallo Christian,
leider geht bei mir von openHAB in Richtung KNX nie ein Befehl durch.

Da knxd grundsätzlich funktioniert und ich von dieser Ebene aus auf den Bus schreiben kann, vermute ich, dass das Probleme eine Ebene höher zu suchen ist. Kann es an calimero liegen? Mir scheint das ausgehend der Link zwischen calimero und knxd nicht funktioniert.

Mit aktiviertem Logging
- log:set DEBUG org.openhab.binding.knx
- log:set DEBUG tuwien.auto.calimero
erhalte ich beispielhaft folgende Loggingeinträge.

Betätigen eines KNX-Schalters:
20:54:49.902 [INFO ] [smarthome.event.ItemCommandEvent ] - Item 'Licht_EG_Esszimmer' received command OFF
20:54:49.924 [DEBUG] [tuwien.auto.calimero ] - calimero.link.224.0.23.12:3671: indication from 12.0.3
20:54:49.924 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Received groupWrite Event.

Schalten des Lichts von openHAB aus (nichts passiert):
21:02:08.237 [INFO ] [smarthome.event.ItemCommandEvent ] - Item 'Licht_EG_Esszimmer' received command ON
21:02:08.241 [INFO ] [tuwien.auto.calimero ] - calimero.link.224.0.23.12:3671: send message to 0/1/0, wait for confirmation
21:02:08.241 [DEBUG] [.binding.knx.internal.bus.KNXBinding] - Wrote value 'ON' to datapoint 'command DP 0/1/0 Licht_EG_Esszimmer, DPT main 0 id 1.001, low priority'
21:02:08.242 [DEBUG] [tuwien.auto.calimero ] - calimero.link.224.0.23.12:3671: cEMI L-Data.ind from 12.0.5 to 0/1/0, low priority hop count 6 tpdu 00 81
21:02:08.243 [DEBUG] [tuwien.auto.calimero ] - KNXnet/IP Routing 224.0.23.12:3671: add to multicast loopback frame buffer: L-Data.ind from 12.0.5 to 0/1/0, low priority hop count 6 tpdu 00 81
21:02:08.245 [DEBUG] [tuwien.auto.calimero ] - KNXnet/IP Routing 224.0.23.12:3671: sending cEMI frame seq 0, non-blocking, attempt 1 (channel 0) 06 10 05 30 00 11 29 00 bc e0 c0 05 01 00 01 00 81
21:02:08.246 [DEBUG] [tuwien.auto.calimero ] - calimero.link.224.0.23.12:3671: send to 0/1/0 succeeded
21:02:08.248 [DEBUG] [tuwien.auto.calimero ] - process 224.0.23.12:3671: group write to 0/1/0 succeeded
21:02:08.249 [DEBUG] [tuwien.auto.calimero ] - KNXnet/IP Routing 224.0.23.12:3671: discard multicast loopback cEMI frame: L-Data.ind from 12.0.5 to 0/1/0, low priority hop count 6 tpdu 00 81

Weiß jemand ob oder wie in calimero etwas eingestellt bzw. untersucht werden kann? Interessanterweise meldet openHAB das es den Befehl geschrieben hat.

[ScanxTaz]

Hi !

Sorry for :

1. The English
2. Waking up dead thread, but I've a question about the "time out"...
I've finally adopted OH2, which seems to be a good framework for what I'd like to do
It was working for a while (maybe 2 months) now, and I've decided this week-end to improve a little bit, integrating recurrent updates about temperature probes for my ventilation system.

I don't know if this issue was existing before, nor if it's really related with the read, from the KNX bus, of the probe temperature, but now, suddenly, the KNX calimero driver start to loose connection with the knx interface.

The interface I use is the USB one from Eibmarkt...

USB HID Device [KNX-USB Manufacturer KNX-USB Interface (Rail mounted)]

I know, you'll say that it's not the perfect one, but it did the job for years with KNXWEB, and I'd like to keep it if possible (expensive at that time), and also, I've no more place for an IP gateway in my electricity panel.

So, the logs of the issue (you'll see, suddenly the "cannot find an active data connection" appears from nowhere... I'm even not doing anything at all..

19:42:57.944 [INFO ] [marthome.event.ItemStateChangedEvent] - BureauPlafond changed from OFF to ON
19:42:58.774 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'BureauPlafond' received command OFF
19:42:59.989 [INFO ] [marthome.event.ItemStateChangedEvent] - BureauPlafond changed from ON to OFF
19:43:04.819 [INFO ] [marthome.event.ItemStateChangedEvent] - VMC_Temp_2 changed from 12.9 to 13.0
19:43:09.748 [INFO ] [marthome.event.ItemStateChangedEvent] - VMC_Temp_3 changed from 16.9 to 17.0
19:43:11.703 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'kodi:kodi:ccd3b0a6-f9e7-99c6-4424-807dba047b44' changed from ONLINE to OFFLINE
19:43:12.362 [INFO ] [me.event.ThingStatusInfoChangedEvent] - 'kodi:kodi:ccd3b0a6-f9e7-99c6-4424-807dba047b44' changed from OFFLINE to ONLINE
[COLOR=#FF0000]19:43:19.374 [WARN ] [tuwien.auto.calimero                ] - KNXnet/IP Tunneling 192.168.0.100:3671: connection state response status: server could not find active data connection with specified ID
19:43:29.376 [WARN ] [tuwien.auto.calimero                ] - KNXnet/IP Tunneling 192.168.0.100:3671: connection state response status: server could not find active data connection with specified ID
19:43:39.378 [WARN ] [tuwien.auto.calimero                ] - KNXnet/IP Tunneling 192.168.0.100:3671: connection state response status: server could not find active data connection with specified ID[/COLOR]
19:43:41.135 [INFO ] [marthome.event.ItemStateChangedEvent] - network_device_192_168_0_100_time changed from 1.045957 to 1.065956
19:43:42.762 [INFO ] [marthome.event.ItemStateChangedEvent] - network_device_f6eb0400_time changed from 26.588903 to 28.228835
[COLOR=#FF0000]19:43:49.380 [WARN ] [tuwien.auto.calimero                ] - KNXnet/IP Tunneling 192.168.0.100:3671: connection state response status: server could not find active data connection with specified ID
19:43:56.028 [INFO ] [marthome.event.ItemStateChangedEvent] - network_device_192_168_0_26_time changed from 1.93292 to 1.722929
19:43:59.380 [WARN ] [tuwien.auto.calimero                ] - KNXnet/IP Tunneling 192.168.0.100:3671: received disconnect response status 0x21 (no active data connection with that ID)
19:43:59.384 [WARN ] [nx.internal.connection.KNXConnection] - KNX link has been lost (reason: no heartbeat response on object tunneling link link (closed) 192.168.0.100:3671 TP1 medium, device 15.15.229, hopcount 6)[/COLOR]
19:43:59.401 [ERROR] [.binding.knx.internal.bus.KNXBinding] - Received detach Event.
19:43:59.423 [WARN ] [tuwien.auto.calimero                ] - KNXnet/IP Tunneling 192.168.0.100:3671: close connection - no heartbeat response
19:44:41.132 [INFO ] [marthome.event.ItemStateChangedEvent] - network_device_192_168_0_100_time changed from 1.065956 to 1.386943
19:44:42.775 [INFO ] [marthome.event.ItemStateChangedEvent] - network_device_f6eb0400_time changed from 28.228835 to 26.956888
19:44:56.026 [INFO ] [marthome.event.ItemStateChangedEvent] - network_device_192_168_0_26_time changed from 1.722929 to 1.690931
19:45:41.137 [INFO ] [marthome.event.ItemStateChangedEvent] - network_device_192_168_0_100_time changed from 1.386943 to 0.919962

My knx.cfg configuration :

ip=192.168.0.100
port=3671
busaddr=15.15.229
ignorelocalevents=true
timeout=10000
pause=100
tuwien.auto.calimero=DEBUG

Could you please help me ???

The "funny" thing is that I see KNXD still working properly in journalctl, where the logs continue to "run" normally, and I see the telegrams from my probes sending values on the KNX bus, but nothing is happening anymore in OH2 logs (karaf nor /var/log/openhab2/*.log)

Thanks a lot !

[gerald07]

Hallo,

Ich habe auch das Problem, dass der knxd nach einer gewissen Zeit (1-2Stunden nicht mehr sendet).
Empfangen tut er aber noch.
Wenn ich mit dem ETS (Gruppenmonitor) verbinde, so sehe ich die Telegramme.
Verbinde ich mich mit der ETS direkt auf das IP-Gateway, so sehe ich die Telegramme nicht mehr.

Die Konfiguration sieht so aus:

• Debian stretch
• knxd aktueller Master-branch
• Weinzierl 731 ip-Gateway
• Konfig: --eibaddr=1.1.241 --client-addrs=1.1.242:5 -c -D -T -S --send-delay=30 -b ipt:192.168.0.7

Interessant ist, daß die gleiche Konfiguration auf meinem Server unter Ubuntu 16.04.4 LTS mit knxd 0.14.19-2 einwandfrei funktioniert.
Ich würde gerne ein Logfile bereitstellen, weiß aber nicht, wie ich das bekomme. Bzw. wie man den Loglevel einstellt.

Bitte um Unterstützung.