KNX-Adapter - keine UDP-Verbindung - OpenKNX-Adapter i.O.
-
@Glasfaser
Anscheinend gibt es hierzu keine Lösung?
Da der OpenKNX-Adapter mit den gleichen Einstellungen läuft, kann ich den KNX-Adapter damit also nicht mehr betreiben.
Schade um das Geld für die Lizenz. -
@glasfaser Welche Einstellungen muss ich dazu bitte ändern im Container?
Also Container anhalten, und dann etwas ändern und neu starten?
Oder Container löschen und neu erstellen? -
Systemdata Bitte Ausfüllen Hardwaresystem: Synology DS723+ Arbeitsspeicher: 34GB Festplattenart: 4 TB HDD Betriebssystem: Buanet Docker v 9.0.1 Node-Version: Nodejs-Version: 18.19.0 NPM-Version: 10.2.3 Installationsart: Docker Image genutzt: Docker official image v 9.0.1 Ort/Name der Imagedatei: Buanet iobroker Nach Restore über das Backup-Tool läuft die KNX-Adapter-Instanz nicht mehr, udp bekommt keine Verbindung.
Bei gleichen Einstellungen bekommt der openKNX-Adapter jedoch eine Verbindung.
KNX-Lizenz ist gültig (grün), ETS-Datei konnte auch erfolgreich eingelesen werden, nur udp läuft im Gegensatz zum openKNX-Adapter nicht.knx.0 Zeit debug Nachricht knx.0 2024-01-20 06:35:27.266 info Send : description Request : 06 10 02 03 00 0e 08 01 ac 11 00 02 90 1d sent to 192.168.178.50:3671 knx.0 2024-01-20 06:35:27.266 info Connected - local UDP Server listening on 172.17.0.2:36893 knx.0 2024-01-20 06:35:27.265 info Event : UDP - listening knx.0 2024-01-20 06:35:27.265 info Using UDP with local IP: 172.17.0.2 knx.0 2024-01-20 06:35:26.266 info STATE_NOT_CONNECTED : Stop connection : STATE_NOT_CONNECTED(0) to STATE_NOT_CONNECTED(0). knx.0 2024-01-20 06:35:26.266 info ... not able to close connection, because already closed knx.0 2024-01-20 06:35:26.265 info Connection persists.....closing now knx.0 2024-01-20 06:35:26.265 info ...set STATE-NOT-CONNECTED knx.0 2024-01-20 06:35:25.264 info STATE_NOT_CONNECTED : Try to connect / reconnect : STATE_DISCONNECT_REQUEST(15) to STATE_NOT_CONNECTED(0). knx.0 2024-01-20 06:35:25.264 info ... not able to close connection, because already closed knx.0 2024-01-20 06:35:25.263 info Connection persists.....closing now knx.0 2024-01-20 06:35:25.263 info STATE_DISCONNECT_REQUEST : no defined handling for transition from State: STATE_CONNECTION_STATE_RESPONSE(6) to STATE_DISCONNECT_REQUEST(15). knx.0 2024-01-20 06:35:25.263 info Received CONNECTIONSTATE_RESPONSE : 06 10 02 08 00 08 00 21 192.168.178.50:3671 ChID : 0 SeqCntIN : 0 SeqCntOUT : 0 msgCode : [object Object] knx.0 2024-01-20 06:35:25.263 info STATE_CONNECTION_STATE_REQUEST : no defined handling for transition from State: STATE_DESCRIPTION_REQUEST(17) to STATE_CONNECTION_STATE_REQUEST(5). knx.0 2024-01-20 06:35:25.263 info Send : UDP Connection State Request : 06 10 02 07 00 10 00 00 08 01 00 00 00 00 92 b4 sent from Port: to 192.168.178.50:3671 knx.0 2024-01-20 06:35:23.262 info Send : description Request : 06 10 02 03 00 0e 08 01 ac 11 00 02 92 b4 sent to 192.168.178.50:3671 knx.0 2024-01-20 06:35:23.261 info Connected - local UDP Server listening on 172.17.0.2:37556 knx.0 2024-01-20 06:35:23.261 info Event : UDP - listening knx.0 2024-01-20 06:35:23.261 info Using UDP with local IP: 172.17.0.2 knx.0 2024-01-20 06:35:22.262 info STATE_NOT_CONNECTED : Stop connection : STATE_NOT_CONNECTED(0) to STATE_NOT_CONNECTED(0). knx.0 2024-01-20 06:35:22.262 info ... not able to close connection, because already closed knx.0 2024-01-20 06:35:22.261 info Connection persists.....closing now knx.0 2024-01-20 06:35:22.261 info ...set STATE-NOT-CONNECTED knx.0 2024-01-20 06:35:21.260 info STATE_NOT_CONNECTED : Try to connect / reconnect : STATE_DISCONNECT_REQUEST(15) to STATE_NOT_CONNECTED(0). knx.0 2024-01-20 06:35:21.260 info ... not able to close connection, because already closed knx.0 2024-01-20 06:35:21.259 info Connection persists.....closing now knx.0 -
@nubbbi sagte in KNX-Adapter - keine UDP-Verbindung - OpenKNX-Adapter i.O.:
Buanet Docker v 9.0.1
Würde ich dann auch noch gleichzeit auf die neue Image Version aktualisieren !
@glasfaser Das habe ich gemacht.
Müssen dann neben dem Mounting von /docker/iobroker zu /opt/fhem noch Ports zugewiesen werden?
Ich habe 3671-3671-udp und 7234-8081-tcp eingestellt, aber der Container bricht beim Start bei Schritt 3 ab. -
@glasfaser Das habe ich gemacht.
Müssen dann neben dem Mounting von /docker/iobroker zu /opt/fhem noch Ports zugewiesen werden?
Ich habe 3671-3671-udp und 7234-8081-tcp eingestellt, aber der Container bricht beim Start bei Schritt 3 ab.@nubbbi sagte in KNX-Adapter - keine UDP-Verbindung - OpenKNX-Adapter i.O.:
Ich habe 3671-3671-udp und 7234-8081-tcp eingestellt, aber der Container bricht beim Start bei Schritt 3 ab.
Warum soll er abbrechen !?
Bei Host brauchen keine Ports gemappt werden .
Zeige mal das LOG , so kann ich nur raten
-
@glasfaser Das habe ich gemacht.
Müssen dann neben dem Mounting von /docker/iobroker zu /opt/fhem noch Ports zugewiesen werden?
Ich habe 3671-3671-udp und 7234-8081-tcp eingestellt, aber der Container bricht beim Start bei Schritt 3 ab.@nubbbi sagte in KNX-Adapter - keine UDP-Verbindung - OpenKNX-Adapter i.O.:
Müssen dann neben dem Mounting von /docker/iobroker zu /opt/fhem
noch Ports zugewiesen werden?Das gleiche wie deine Einstellungen im alten Container , zu Ordner Mounts !
-
@glasfaser Das habe ich gemacht.
Müssen dann neben dem Mounting von /docker/iobroker zu /opt/fhem noch Ports zugewiesen werden?
Ich habe 3671-3671-udp und 7234-8081-tcp eingestellt, aber der Container bricht beim Start bei Schritt 3 ab. -
@nubbbi sagte in KNX-Adapter - keine UDP-Verbindung - OpenKNX-Adapter i.O.:
bricht beim Start bei Schritt 3 ab.
zusätzlich ... kann man hiermit mehr sehen :
Trage in der ENV ein
DEBUG = true.
 code_text ```iobroker date,stream,content 2024/01/28 19:33:12,stdout,This Script will exit now. 2024/01/28 19:33:12,stdout, 2024/01/28 19:31:23,stdout,[DEBUG] IoBroker is not running! 2024/01/28 19:31:23,stdout,[DEBUG] If you want to stop or restart your container you have to do it manually. 2024/01/28 19:31:23,stdout,[DEBUG] This enables you to investigate or fix your issue on the command line. 2024/01/28 19:31:23,stdout,[DEBUG] Debug mode prevents the container from exiting on errors. 2024/01/28 19:31:23,stdout, 2024/01/28 19:31:23,stdout,For more information see ioBroker Docker image docs (https://docs.buanet.de/iobroker-docker-image/docs). 2024/01/28 19:31:23,stdout,Please check your configuration and try again. 2024/01/28 19:31:23,stdout,[DEBUG] No connection to databases possible ... 2024/01/28 19:31:23,stdout,[DEBUG] Could not connect to states database at 127.0.0.1:9000 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! 2024/01/28 19:31:23,stdout,[DEBUG] Could not connect to states database at 127.0.0.1:9000 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! 2024/01/28 19:31:23,stdout,[DEBUG] Error message: 2024/01/28 19:31:23,stdout,Checking database connection... Failed. 2024/01/28 19:30:30,stdout, 2024/01/28 19:30:30,stdout,[DEBUG] Done. 2024/01/28 19:30:30,stdout,[DEBUG] No custom states db settings detected. 2024/01/28 19:30:30,stdout,[DEBUG] Checking custom states db settings... 2024/01/28 19:30:30,stdout, 2024/01/28 19:30:30,stdout,[DEBUG] Done. 2024/01/28 19:30:30,stdout,[DEBUG] No custom objects db settings detected. 2024/01/28 19:30:30,stdout,[DEBUG] Checking custom objects db settings... 2024/01/28 19:30:30,stdout, 2024/01/28 19:30:30,stdout,[DEBUG] Done. 2024/01/28 19:30:30,stdout,[DEBUG] No multihost settings detected. 2024/01/28 19:30:30,stdout,[DEBUG] Checking multihost settings... 2024/01/28 19:30:30,stdout, 2024/01/28 19:30:30,stdout,(Re)setting permissions (This might take a while! Please be patient!)... Done. 2024/01/28 19:30:30,stdout, 2024/01/28 19:30:30,stdout,-------------------------------------------------------------------------------- 2024/01/28 19:30:30,stdout,----- Step 3 of 5: Checking ioBroker Installation ----- 2024/01/28 19:30:30,stdout,-------------------------------------------------------------------------------- 2024/01/28 19:30:30,stdout, 2024/01/28 19:30:30,stdout,Existing installation of ioBroker detected in "/opt/iobroker". 2024/01/28 19:30:30,stdout, 2024/01/28 19:30:30,stdout,-------------------------------------------------------------------------------- 2024/01/28 19:30:30,stdout,----- Step 2 of 5: Detecting ioBroker Installation ----- 2024/01/28 19:30:30,stdout,-------------------------------------------------------------------------------- 2024/01/28 19:30:30,stdout, 2024/01/28 19:30:30,stdout, 2024/01/28 19:30:30,stdout, 2024/01/28 19:30:30,stdout,-------------------------------------------------------------------------------- 2024/01/28 19:30:30,stdout,----- Step 1 of 5: Preparing Container ----- 2024/01/28 19:30:30,stdout,-------------------------------------------------------------------------------- 2024/01/28 19:30:30,stdout, 2024/01/28 19:30:30,stdout,!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 2024/01/28 19:30:30,stdout,!!!! https://docs.buanet.de/iobroker-docker-image/docs/ !!!! 2024/01/28 19:30:30,stdout,!!!! For more information see ioBroker Docker image documentation: !!!! 2024/01/28 19:30:30,stdout,!!!! Please make sure to deactivate if no longer needed. !!!! 2024/01/28 19:30:30,stdout,!!!! This will extend the logging output and may slow down container start. !!!! 2024/01/28 19:30:30,stdout,!!!! Environment variable DEBUG is set to true. !!!! 2024/01/28 19:30:30,stdout,!!!! DEBUG LOG ACTIVE !!!! 2024/01/28 19:30:30,stdout,!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 2024/01/28 19:30:30,stdout, 2024/01/28 19:30:30,stdout,-------------------------------------------------------------------------------- -
 code_text ```iobroker date,stream,content 2024/01/28 19:33:12,stdout,This Script will exit now. 2024/01/28 19:33:12,stdout, 2024/01/28 19:31:23,stdout,[DEBUG] IoBroker is not running! 2024/01/28 19:31:23,stdout,[DEBUG] If you want to stop or restart your container you have to do it manually. 2024/01/28 19:31:23,stdout,[DEBUG] This enables you to investigate or fix your issue on the command line. 2024/01/28 19:31:23,stdout,[DEBUG] Debug mode prevents the container from exiting on errors. 2024/01/28 19:31:23,stdout, 2024/01/28 19:31:23,stdout,For more information see ioBroker Docker image docs (https://docs.buanet.de/iobroker-docker-image/docs). 2024/01/28 19:31:23,stdout,Please check your configuration and try again. 2024/01/28 19:31:23,stdout,[DEBUG] No connection to databases possible ... 2024/01/28 19:31:23,stdout,[DEBUG] Could not connect to states database at 127.0.0.1:9000 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! 2024/01/28 19:31:23,stdout,[DEBUG] Could not connect to states database at 127.0.0.1:9000 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! 2024/01/28 19:31:23,stdout,[DEBUG] Error message: 2024/01/28 19:31:23,stdout,Checking database connection... Failed. 2024/01/28 19:30:30,stdout, 2024/01/28 19:30:30,stdout,[DEBUG] Done. 2024/01/28 19:30:30,stdout,[DEBUG] No custom states db settings detected. 2024/01/28 19:30:30,stdout,[DEBUG] Checking custom states db settings... 2024/01/28 19:30:30,stdout, 2024/01/28 19:30:30,stdout,[DEBUG] Done. 2024/01/28 19:30:30,stdout,[DEBUG] No custom objects db settings detected. 2024/01/28 19:30:30,stdout,[DEBUG] Checking custom objects db settings... 2024/01/28 19:30:30,stdout, 2024/01/28 19:30:30,stdout,[DEBUG] Done. 2024/01/28 19:30:30,stdout,[DEBUG] No multihost settings detected. 2024/01/28 19:30:30,stdout,[DEBUG] Checking multihost settings... 2024/01/28 19:30:30,stdout, 2024/01/28 19:30:30,stdout,(Re)setting permissions (This might take a while! Please be patient!)... Done. 2024/01/28 19:30:30,stdout, 2024/01/28 19:30:30,stdout,-------------------------------------------------------------------------------- 2024/01/28 19:30:30,stdout,----- Step 3 of 5: Checking ioBroker Installation ----- 2024/01/28 19:30:30,stdout,-------------------------------------------------------------------------------- 2024/01/28 19:30:30,stdout, 2024/01/28 19:30:30,stdout,Existing installation of ioBroker detected in "/opt/iobroker". 2024/01/28 19:30:30,stdout, 2024/01/28 19:30:30,stdout,-------------------------------------------------------------------------------- 2024/01/28 19:30:30,stdout,----- Step 2 of 5: Detecting ioBroker Installation ----- 2024/01/28 19:30:30,stdout,-------------------------------------------------------------------------------- 2024/01/28 19:30:30,stdout, 2024/01/28 19:30:30,stdout, 2024/01/28 19:30:30,stdout, 2024/01/28 19:30:30,stdout,-------------------------------------------------------------------------------- 2024/01/28 19:30:30,stdout,----- Step 1 of 5: Preparing Container ----- 2024/01/28 19:30:30,stdout,-------------------------------------------------------------------------------- 2024/01/28 19:30:30,stdout, 2024/01/28 19:30:30,stdout,!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 2024/01/28 19:30:30,stdout,!!!! https://docs.buanet.de/iobroker-docker-image/docs/ !!!! 2024/01/28 19:30:30,stdout,!!!! For more information see ioBroker Docker image documentation: !!!! 2024/01/28 19:30:30,stdout,!!!! Please make sure to deactivate if no longer needed. !!!! 2024/01/28 19:30:30,stdout,!!!! This will extend the logging output and may slow down container start. !!!! 2024/01/28 19:30:30,stdout,!!!! Environment variable DEBUG is set to true. !!!! 2024/01/28 19:30:30,stdout,!!!! DEBUG LOG ACTIVE !!!! 2024/01/28 19:30:30,stdout,!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 2024/01/28 19:30:30,stdout, 2024/01/28 19:30:30,stdout,-------------------------------------------------------------------------------- -
 code_text ```iobroker date,stream,content 2024/01/28 19:33:12,stdout,This Script will exit now. 2024/01/28 19:33:12,stdout, 2024/01/28 19:31:23,stdout,[DEBUG] IoBroker is not running! 2024/01/28 19:31:23,stdout,[DEBUG] If you want to stop or restart your container you have to do it manually. 2024/01/28 19:31:23,stdout,[DEBUG] This enables you to investigate or fix your issue on the command line. 2024/01/28 19:31:23,stdout,[DEBUG] Debug mode prevents the container from exiting on errors. 2024/01/28 19:31:23,stdout, 2024/01/28 19:31:23,stdout,For more information see ioBroker Docker image docs (https://docs.buanet.de/iobroker-docker-image/docs). 2024/01/28 19:31:23,stdout,Please check your configuration and try again. 2024/01/28 19:31:23,stdout,[DEBUG] No connection to databases possible ... 2024/01/28 19:31:23,stdout,[DEBUG] Could not connect to states database at 127.0.0.1:9000 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! 2024/01/28 19:31:23,stdout,[DEBUG] Could not connect to states database at 127.0.0.1:9000 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! 2024/01/28 19:31:23,stdout,[DEBUG] Error message: 2024/01/28 19:31:23,stdout,Checking database connection... Failed. 2024/01/28 19:30:30,stdout, 2024/01/28 19:30:30,stdout,[DEBUG] Done. 2024/01/28 19:30:30,stdout,[DEBUG] No custom states db settings detected. 2024/01/28 19:30:30,stdout,[DEBUG] Checking custom states db settings... 2024/01/28 19:30:30,stdout, 2024/01/28 19:30:30,stdout,[DEBUG] Done. 2024/01/28 19:30:30,stdout,[DEBUG] No custom objects db settings detected. 2024/01/28 19:30:30,stdout,[DEBUG] Checking custom objects db settings... 2024/01/28 19:30:30,stdout, 2024/01/28 19:30:30,stdout,[DEBUG] Done. 2024/01/28 19:30:30,stdout,[DEBUG] No multihost settings detected. 2024/01/28 19:30:30,stdout,[DEBUG] Checking multihost settings... 2024/01/28 19:30:30,stdout, 2024/01/28 19:30:30,stdout,(Re)setting permissions (This might take a while! Please be patient!)... Done. 2024/01/28 19:30:30,stdout, 2024/01/28 19:30:30,stdout,-------------------------------------------------------------------------------- 2024/01/28 19:30:30,stdout,----- Step 3 of 5: Checking ioBroker Installation ----- 2024/01/28 19:30:30,stdout,-------------------------------------------------------------------------------- 2024/01/28 19:30:30,stdout, 2024/01/28 19:30:30,stdout,Existing installation of ioBroker detected in "/opt/iobroker". 2024/01/28 19:30:30,stdout, 2024/01/28 19:30:30,stdout,-------------------------------------------------------------------------------- 2024/01/28 19:30:30,stdout,----- Step 2 of 5: Detecting ioBroker Installation ----- 2024/01/28 19:30:30,stdout,-------------------------------------------------------------------------------- 2024/01/28 19:30:30,stdout, 2024/01/28 19:30:30,stdout, 2024/01/28 19:30:30,stdout, 2024/01/28 19:30:30,stdout,-------------------------------------------------------------------------------- 2024/01/28 19:30:30,stdout,----- Step 1 of 5: Preparing Container ----- 2024/01/28 19:30:30,stdout,-------------------------------------------------------------------------------- 2024/01/28 19:30:30,stdout, 2024/01/28 19:30:30,stdout,!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 2024/01/28 19:30:30,stdout,!!!! https://docs.buanet.de/iobroker-docker-image/docs/ !!!! 2024/01/28 19:30:30,stdout,!!!! For more information see ioBroker Docker image documentation: !!!! 2024/01/28 19:30:30,stdout,!!!! Please make sure to deactivate if no longer needed. !!!! 2024/01/28 19:30:30,stdout,!!!! This will extend the logging output and may slow down container start. !!!! 2024/01/28 19:30:30,stdout,!!!! Environment variable DEBUG is set to true. !!!! 2024/01/28 19:30:30,stdout,!!!! DEBUG LOG ACTIVE !!!! 2024/01/28 19:30:30,stdout,!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 2024/01/28 19:30:30,stdout, 2024/01/28 19:30:30,stdout,--------------------------------------------------------------------------------@nubbbi sagte in KNX-Adapter - keine UDP-Verbindung - OpenKNX-Adapter i.O.:
Please make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software!
Zeige mal vom vorhanden Container , die Full Ausgabe von
iob diag -
@nubbbi
Kann es sein, dass der Port 9000, der hier erwartet wird, bereits anders genutzt wird? Nämlich bei mir von Portainer? -
@nubbbi sagte in KNX-Adapter - keine UDP-Verbindung - OpenKNX-Adapter i.O.:
Nämlich bei mir von Portainer?
Richtig , den mußt du ändern !!!
-
@glasfaser Wenn ich den Port 9000 für den Container Portainer ändere, komme ich aber nicht mehr auf dessen Weboberfläche.
-
sieht dann so aus , also über den Port 8020 erreichbar :
Portainer ist im Bridge Modus :
.
.
*** ioBroker-Installation *** ioBroker Status Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Plea se make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Plea se make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! No connection to databases possible ... Core adapters versions js-controller: 5.0.17 admin: 6.12.0 javascript: "javascript" not found Adapters from github: 0 Adapter State Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Plea se make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Plea se make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! -
*** ioBroker-Installation *** ioBroker Status Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Plea se make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Plea se make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! No connection to databases possible ... Core adapters versions js-controller: 5.0.17 admin: 6.12.0 javascript: "javascript" not found Adapters from github: 0 Adapter State Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Plea se make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Plea se make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! -
@glasfaser Also, ich öffne die Einstellungen zum Container, gehe auf "Terminalfenster öffnen" und dann "Mit Befehl starten" und da gebe ich "iob diag" ein - soweit richtig?
Mir gelingt es aber nicht, das Ergebnis per STRG-C zu kopieren.
-
@nubbbi sagte in KNX-Adapter - keine UDP-Verbindung - OpenKNX-Adapter i.O.:
Mir gelingt es aber nicht, das Ergebnis per STRG-C zu kopieren.
Steht in der Beschreibung !!
vorher STRG-A dann STRG-C
-
@glasfaser vorher heißt, wenn da steht "drücke eine Taste, um Summary zu erstellen"?
Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.
Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.
Mit deinem Input könnte dieser Beitrag noch besser werden 💗
Registrieren AnmeldenSupport us
321
Online32.9k
Benutzer83.0k
Themen1.3m
Beiträge