iob diag - Skript
ioBroker Allgemein
792
Beiträge
49
Kommentatoren
219.5k
Aufrufe
38
Watching
-
@thomas-braun glaube das wird zu Problemen führen da 98% der User das „All Good“ aufgrund der dominanten Schreibweise so lesen das „Alles OK“ ist und das vorherige Klein geschriebene einfach überlesen.
Ja, das sind auch meine Bedenken dabei. Was ich aber machen könnte:
Der Check wird nur zusätzlich ausgeführt, wenn zuvor die eigentliche Installation auf Korrektheit geprüft wurde. So als goodie. Wenn die Grundinstallation schon schief ist brauchste auch nicht auf Sicherheitslücken prüfen. -
Ja, das sind auch meine Bedenken dabei. Was ich aber machen könnte:
Der Check wird nur zusätzlich ausgeführt, wenn zuvor die eigentliche Installation auf Korrektheit geprüft wurde. So als goodie. Wenn die Grundinstallation schon schief ist brauchste auch nicht auf Sicherheitslücken prüfen. -
@thomas-braun das wäre vielleicht eine Maßnahme.
Eine eigentlich korrekt installierte nodejs@18 meldet sich so:
*** NodeJS-Installation *** /usr/bin/nodejs v18.20.8 /usr/bin/node v18.20.8 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.32.0 nodejs: Installed: 18.20.8-1nodesource1 Candidate: 18.20.8-1nodesource1 Version table: 20.19.2+dfsg-1 500 500 http://deb.debian.org/debian trixie/main arm64 Packages *** 18.20.8-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 100 /var/lib/dpkg/status 18.20.6-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages [...] 18.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected Checking for nodejs vulnerability: up to date, audited 10 packages in 2s found 0 vulnerabilities ██████ █████ ███ ██ ██████ ███████ ██████ ██ ██ ██ ██ ████ ██ ██ ██ ██ ██ ██ ██ ███████ ██ ██ ██ ██ ███ █████ ██████ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██████ ██ ██ ██ ████ ██████ ███████ ██ ██ v18.20.8 is end-of-life. There are high chances of being vulnerable. Please upgrade it.Eine falsch installierte nodejs@24:
*** NodeJS-Installation *** nodejs: N/A /usr/bin/node v24.1.0 /usr/bin/npm 11.4.1 /usr/bin/npx 11.4.1 /usr/bin/corepack 0.32.0 *** nodejs is NOT correctly installed *** find: '/opt/iobroker/node_modules': No such file or directory Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected -
Eine eigentlich korrekt installierte nodejs@18 meldet sich so:
*** NodeJS-Installation *** /usr/bin/nodejs v18.20.8 /usr/bin/node v18.20.8 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.32.0 nodejs: Installed: 18.20.8-1nodesource1 Candidate: 18.20.8-1nodesource1 Version table: 20.19.2+dfsg-1 500 500 http://deb.debian.org/debian trixie/main arm64 Packages *** 18.20.8-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 100 /var/lib/dpkg/status 18.20.6-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages [...] 18.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected Checking for nodejs vulnerability: up to date, audited 10 packages in 2s found 0 vulnerabilities ██████ █████ ███ ██ ██████ ███████ ██████ ██ ██ ██ ██ ████ ██ ██ ██ ██ ██ ██ ██ ███████ ██ ██ ██ ██ ███ █████ ██████ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██████ ██ ██ ██ ████ ██████ ███████ ██ ██ v18.20.8 is end-of-life. There are high chances of being vulnerable. Please upgrade it.Eine falsch installierte nodejs@24:
*** NodeJS-Installation *** nodejs: N/A /usr/bin/node v24.1.0 /usr/bin/npm 11.4.1 /usr/bin/npx 11.4.1 /usr/bin/corepack 0.32.0 *** nodejs is NOT correctly installed *** find: '/opt/iobroker/node_modules': No such file or directory Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected@thomas-braun Ich hab mal die aktuelle Testversion auf meinem Testsystem ausgeführt
Was hat es mit den *** FAILED SERVICES *** auf sich?
Die dunkel blaue Schrift ist nicht wirklich lesbar
Ist der npm notice hier wirklich sinvoll, das der Anwender aufgefordert wird über npm intall sich die neuste Version zu installieren? Das sollte doch besser über sudo apt full-upgrade aktualisiert werden.
-
@thomas-braun Ich hab mal die aktuelle Testversion auf meinem Testsystem ausgeführt
Was hat es mit den *** FAILED SERVICES *** auf sich?
Die dunkel blaue Schrift ist nicht wirklich lesbar
Ist der npm notice hier wirklich sinvoll, das der Anwender aufgefordert wird über npm intall sich die neuste Version zu installieren? Das sollte doch besser über sudo apt full-upgrade aktualisiert werden.
Der komplette Text zu nodejs vulnerabilty kommt nicht direkt aus dem Skript sondern vom Nodejs Security Team.
Da kann ich so nix dran machen.Was hat es mit den *** FAILED SERVICES *** auf sich?
Das sind Meldungen aus deinem System (genauer von systemd). Da wurden dann die aufgeführten Dienste nicht gestartet.
-
@thomas-braun Ich hab mal die aktuelle Testversion auf meinem Testsystem ausgeführt
Was hat es mit den *** FAILED SERVICES *** auf sich?
Die dunkel blaue Schrift ist nicht wirklich lesbar
Ist der npm notice hier wirklich sinvoll, das der Anwender aufgefordert wird über npm intall sich die neuste Version zu installieren? Das sollte doch besser über sudo apt full-upgrade aktualisiert werden.
Hab was angepasst. Schau mal bitte, ob die Meldungen zur npm Version nun verschwunden sind.
-
Hab was angepasst. Schau mal bitte, ob die Meldungen zur npm Version nun verschwunden sind.
@thomas-braun Das sieht besser aus.
*** NodeJS-Installation *** /usr/bin/nodejs v24.1.0 /usr/bin/node v24.1.0 /usr/bin/npm 11.3.0 /usr/bin/npx 11.3.0 /usr/bin/corepack 0.32.0 nodejs: Installed: 24.1.0-1nodesource1 Candidate: 24.1.0-1nodesource1 Version table: *** 24.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_24.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 24.0.2-1nodesource1 1001 500 https://deb.nodesource.com/node_24.x nodistro/main amd64 Packages 24.0.1-1nodesource1 1001 500 https://deb.nodesource.com/node_24.x nodistro/main amd64 Packages 24.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_24.x nodistro/main amd64 Packages 18.19.1+dfsg-6ubuntu5 500 500 http://archive.ubuntu.com/ubuntu noble/universe amd64 Packages Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected Checking for nodejs vulnerability: █████ ██ ██ ██████ ██████ ██████ ██████ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ██ ██ ██ ███ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ███████ ██████ ██████ ██████ ██████ ██Edit:
Und einmal mit nodejs 18*** NodeJS-Installation *** /usr/bin/nodejs v18.20.8 /usr/bin/node v18.20.8 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.32.0 nodejs: Installed: 18.20.8-1nodesource1 Candidate: 18.20.8-1nodesource1 Version table: *** 18.20.8-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 18.20.6-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.20.5-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.20.4-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.20.3-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.20.2-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.20.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.20.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.19.1+dfsg-6ubuntu5 500 500 http://archive.ubuntu.com/ubuntu noble/universe amd64 Packages 18.19.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.19.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.18.2-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.18.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.17.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.16.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.2-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.9.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected Checking for nodejs vulnerability: ██████ █████ ███ ██ ██████ ███████ ███████ ██ ██ ██ ██ ████ ██ ██ ██ ██ ██ ██ ██ ███████ ██ ██ ██ ██ ███ █████ ███████ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██████ ██ ██ ██ ████ ██████ ███████ ██ ██ v18.20.8 is end-of-life. There are high chances of being vulnerable. Please upgrade it. -
@thomas-braun Das sieht besser aus.
*** NodeJS-Installation *** /usr/bin/nodejs v24.1.0 /usr/bin/node v24.1.0 /usr/bin/npm 11.3.0 /usr/bin/npx 11.3.0 /usr/bin/corepack 0.32.0 nodejs: Installed: 24.1.0-1nodesource1 Candidate: 24.1.0-1nodesource1 Version table: *** 24.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_24.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 24.0.2-1nodesource1 1001 500 https://deb.nodesource.com/node_24.x nodistro/main amd64 Packages 24.0.1-1nodesource1 1001 500 https://deb.nodesource.com/node_24.x nodistro/main amd64 Packages 24.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_24.x nodistro/main amd64 Packages 18.19.1+dfsg-6ubuntu5 500 500 http://archive.ubuntu.com/ubuntu noble/universe amd64 Packages Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected Checking for nodejs vulnerability: █████ ██ ██ ██████ ██████ ██████ ██████ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ██ ██ ██ ███ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ███████ ██████ ██████ ██████ ██████ ██Edit:
Und einmal mit nodejs 18*** NodeJS-Installation *** /usr/bin/nodejs v18.20.8 /usr/bin/node v18.20.8 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.32.0 nodejs: Installed: 18.20.8-1nodesource1 Candidate: 18.20.8-1nodesource1 Version table: *** 18.20.8-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 18.20.6-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.20.5-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.20.4-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.20.3-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.20.2-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.20.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.20.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.19.1+dfsg-6ubuntu5 500 500 http://archive.ubuntu.com/ubuntu noble/universe amd64 Packages 18.19.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.19.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.18.2-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.18.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.17.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.16.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.2-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.9.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected Checking for nodejs vulnerability: ██████ █████ ███ ██ ██████ ███████ ███████ ██ ██ ██ ██ ████ ██ ██ ██ ██ ██ ██ ██ ███████ ██ ██ ██ ██ ███ █████ ███████ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██████ ██ ██ ██ ████ ██████ ███████ ██ ██ v18.20.8 is end-of-life. There are high chances of being vulnerable. Please upgrade it. -
Eine neue Testrunde!
Ich habe den Code des Skripts etwas aufgeräumt und Shellcheck hat jetzt nichts mehr zu bemängeln.Und ich habe den Part mit den ZigBee-Ports neugeschrieben (bzw. von KI schreiben lassen und nur hier und da was korrigiert). Hier wäre es insbesondere schön zu sehen, wie das bei mehreren ZigBee-Sticks und/oder Instanzen des Adapters aussieht. Auf meinem kleinen System schaut das so aus:
=== ZigBee Port Overview === Instance Configured Port Available by-id Ports Status -------- ---------------- ---------------------------- ------ zigbee.0 ...8-if00-port0 ...8-if00-port0 ✓ Matchingbzw. im anderen Fall
=== ZigBee Port Overview === Instance Configured Port Available by-id Ports Status -------- ---------------- ---------------------------- ------ zigbee.0 /dev/ttyUSB0 ...8-if00-port0 ✗ Not matchingWäre schön das bei komplexeren Setups mit mehrern Instanzen, Controllern mit tcp-AAAnbindung usw. mal zu sehen.
Link zur aktuellen Skript-Version im ersten Posting.
Danke an die fleißigen Tester! -
Fehlt da nicht ein wget?
-
Fehlt da nicht ein wget?
Oder ein curl...
Hab es ergänzt. -
Meine Zigbee Instanzen ( 5 an der Zahl ) werden so angezeigt:
USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': No Devices found 'by-id' *** ZigBee Settings *** ⚠ HINT: Your zigbee.0 COM-Port is NOT matching 'by-id'. Please check your setting: tcp ⚠ HINT: Your zigbee.1 COM-Port is NOT matching 'by-id'. Please check your setting: tcp ⚠ HINT: Your zigbee.2 COM-Port is NOT matching 'by-id'. Please check your setting: tcp ⚠ HINT: Your zigbee.3 COM-Port is NOT matching 'by-id'. Please check your setting: tcp ⚠ HINT: Your zigbee.4 COM-Port is NOT matching 'by-id'. Please check your setting: tcp Zigbee Network Settings on your coordinator / in nvbackup are: zigbee.X \nExtended Pan ID: \n*** MASKED *** \nPan ID: \n*** MASKED *** \nChannel: \n*** MASKED *** \nNetwork Key: \n*** MASKED *** To unmask the settings run 'iob diag --unmask' === ZigBee Port Overview === Instance Configured Port Available by-id Ports Status -------- ---------------- ---------------------------- ------ *** NodeJS-Installation *** -
Meine Zigbee Instanzen ( 5 an der Zahl ) werden so angezeigt:
USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': No Devices found 'by-id' *** ZigBee Settings *** ⚠ HINT: Your zigbee.0 COM-Port is NOT matching 'by-id'. Please check your setting: tcp ⚠ HINT: Your zigbee.1 COM-Port is NOT matching 'by-id'. Please check your setting: tcp ⚠ HINT: Your zigbee.2 COM-Port is NOT matching 'by-id'. Please check your setting: tcp ⚠ HINT: Your zigbee.3 COM-Port is NOT matching 'by-id'. Please check your setting: tcp ⚠ HINT: Your zigbee.4 COM-Port is NOT matching 'by-id'. Please check your setting: tcp Zigbee Network Settings on your coordinator / in nvbackup are: zigbee.X \nExtended Pan ID: \n*** MASKED *** \nPan ID: \n*** MASKED *** \nChannel: \n*** MASKED *** \nNetwork Key: \n*** MASKED *** To unmask the settings run 'iob diag --unmask' === ZigBee Port Overview === Instance Configured Port Available by-id Ports Status -------- ---------------- ---------------------------- ------ *** NodeJS-Installation ***Prima Hinweise!
Versuch jetzt nochmal. Hab den Code angepasst. -
Gerne:
USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': No Devices found 'by-id' *** ZigBee Settings *** ⚠ HINT: Your zigbee.0 COM-Port is NOT matching 'by-id'. Please check your setting: tcp ⚠ HINT: Your zigbee.1 COM-Port is NOT matching 'by-id'. Please check your setting: tcp ⚠ HINT: Your zigbee.2 COM-Port is NOT matching 'by-id'. Please check your setting: tcp ⚠ HINT: Your zigbee.3 COM-Port is NOT matching 'by-id'. Please check your setting: tcp ⚠ HINT: Your zigbee.4 COM-Port is NOT matching 'by-id'. Please check your setting: tcp Zigbee Network Settings on your coordinator / in nvbackup are: zigbee.X \nExtended Pan ID: \n*** MASKED *** \nPan ID: \n*** MASKED *** \nChannel: \n*** MASKED *** \nNetwork Key: \n*** MASKED *** To unmask the settings run 'iob diag --unmask' === ZigBee Port Overview === Instance Configured Port Available by-id Ports Status -------- ---------------- ---------------------------- ------ zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee.0 tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee.1 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee.2 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee.3 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee.4 tcp://192.168.0.99:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. tcp://192.168.0.99:20108 TCP Connection *** NodeJS-Installation ***Proxmox 9 HA-Cluster mit 3x HP prodesk 400 G6 i5
Bei einem downvote bitte melden, es könnte sein, dass dieser ungewollt ist! -
Gerne:
USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': No Devices found 'by-id' *** ZigBee Settings *** ⚠ HINT: Your zigbee.0 COM-Port is NOT matching 'by-id'. Please check your setting: tcp ⚠ HINT: Your zigbee.1 COM-Port is NOT matching 'by-id'. Please check your setting: tcp ⚠ HINT: Your zigbee.2 COM-Port is NOT matching 'by-id'. Please check your setting: tcp ⚠ HINT: Your zigbee.3 COM-Port is NOT matching 'by-id'. Please check your setting: tcp ⚠ HINT: Your zigbee.4 COM-Port is NOT matching 'by-id'. Please check your setting: tcp Zigbee Network Settings on your coordinator / in nvbackup are: zigbee.X \nExtended Pan ID: \n*** MASKED *** \nPan ID: \n*** MASKED *** \nChannel: \n*** MASKED *** \nNetwork Key: \n*** MASKED *** To unmask the settings run 'iob diag --unmask' === ZigBee Port Overview === Instance Configured Port Available by-id Ports Status -------- ---------------- ---------------------------- ------ zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee.0 tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee.1 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee.2 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee.3 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee.4 tcp://192.168.0.99:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. tcp://192.168.0.99:20108 TCP Connection *** NodeJS-Installation ***Oh, das ist jetzt etwas zu ausführlich in der Ausgabe. Mal schauen wie ich das eingefangen bekomme...
-
Gerne:
USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': No Devices found 'by-id' *** ZigBee Settings *** ⚠ HINT: Your zigbee.0 COM-Port is NOT matching 'by-id'. Please check your setting: tcp ⚠ HINT: Your zigbee.1 COM-Port is NOT matching 'by-id'. Please check your setting: tcp ⚠ HINT: Your zigbee.2 COM-Port is NOT matching 'by-id'. Please check your setting: tcp ⚠ HINT: Your zigbee.3 COM-Port is NOT matching 'by-id'. Please check your setting: tcp ⚠ HINT: Your zigbee.4 COM-Port is NOT matching 'by-id'. Please check your setting: tcp Zigbee Network Settings on your coordinator / in nvbackup are: zigbee.X \nExtended Pan ID: \n*** MASKED *** \nPan ID: \n*** MASKED *** \nChannel: \n*** MASKED *** \nNetwork Key: \n*** MASKED *** To unmask the settings run 'iob diag --unmask' === ZigBee Port Overview === Instance Configured Port Available by-id Ports Status -------- ---------------- ---------------------------- ------ zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee.0 tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee.1 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee.2 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee.3 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee.4 tcp://192.168.0.99:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 TCP Connection zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. ...//192.168.0.99:20108 ✗ Not matching zigbee. tcp://192.168.0.99:20108 TCP Connection *** NodeJS-Installation ***Probier jetzt nochmal bitte.
-
USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': No Devices found 'by-id' *** ZigBee Settings *** ⚠ HINT: Your zigbee.0 COM-Port is NOT matching 'by-id'. Please check your setting: tcp ⚠ HINT: Your zigbee.1 COM-Port is NOT matching 'by-id'. Please check your setting: tcp ⚠ HINT: Your zigbee.2 COM-Port is NOT matching 'by-id'. Please check your setting: tcp ⚠ HINT: Your zigbee.3 COM-Port is NOT matching 'by-id'. Please check your setting: tcp ⚠ HINT: Your zigbee.4 COM-Port is NOT matching 'by-id'. Please check your setting: tcp Zigbee Network Settings on your coordinator / in nvbackup are: zigbee.X \nExtended Pan ID: \n*** MASKED *** \nPan ID: \n*** MASKED *** \nChannel: \n*** MASKED *** \nNetwork Key: \n*** MASKED *** To unmask the settings run 'iob diag --unmask' === ZigBee Port Overview === Instance Configured Port Available by-id Port Status -------- ---------------- ---------------------------- ------ zigbee.0 tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 - TCP Connection zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 - TCP Connection zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 - TCP Connection zigbee.1 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 - TCP Connection zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 - TCP Connection zigbee. tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 - TCP Connection zigbee.2 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 - TCP Connection zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 - TCP Connection zigbee. tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 - TCP Connection zigbee.3 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 - TCP Connection zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 - TCP Connection zigbee. tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 - TCP Connection zigbee.4 tcp://192.168.0.99:20108 - TCP Connection zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 - TCP Connection zigbee. tcp://192.168.0.99:20108 - TCP Connection *** NodeJS-Installation *** -
USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': No Devices found 'by-id' *** ZigBee Settings *** ⚠ HINT: Your zigbee.0 COM-Port is NOT matching 'by-id'. Please check your setting: tcp ⚠ HINT: Your zigbee.1 COM-Port is NOT matching 'by-id'. Please check your setting: tcp ⚠ HINT: Your zigbee.2 COM-Port is NOT matching 'by-id'. Please check your setting: tcp ⚠ HINT: Your zigbee.3 COM-Port is NOT matching 'by-id'. Please check your setting: tcp ⚠ HINT: Your zigbee.4 COM-Port is NOT matching 'by-id'. Please check your setting: tcp Zigbee Network Settings on your coordinator / in nvbackup are: zigbee.X \nExtended Pan ID: \n*** MASKED *** \nPan ID: \n*** MASKED *** \nChannel: \n*** MASKED *** \nNetwork Key: \n*** MASKED *** To unmask the settings run 'iob diag --unmask' === ZigBee Port Overview === Instance Configured Port Available by-id Port Status -------- ---------------- ---------------------------- ------ zigbee.0 tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 - TCP Connection zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 - TCP Connection zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 - TCP Connection zigbee.1 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 - TCP Connection zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 - TCP Connection zigbee. tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 - TCP Connection zigbee.2 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 - TCP Connection zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 - TCP Connection zigbee. tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 - TCP Connection zigbee.3 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 - TCP Connection zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 - TCP Connection zigbee. tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 - TCP Connection zigbee.4 tcp://192.168.0.99:20108 - TCP Connection zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 - TCP Connection zigbee. tcp://192.168.0.99:20108 - TCP Connection *** NodeJS-Installation ***Und nochmal bitte einen Lauf... :-)
-
Für dich als Info, zur Sicherheit lösche ich das Script vorher immer.
USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': No Devices found 'by-id' *** ZigBee Settings *** ⚠ HINT: Your zigbee.0 COM-Port is NOT matching 'by-id'. Please check your setting: tcp ⚠ HINT: Your zigbee.1 COM-Port is NOT matching 'by-id'. Please check your setting: tcp ⚠ HINT: Your zigbee.2 COM-Port is NOT matching 'by-id'. Please check your setting: tcp ⚠ HINT: Your zigbee.3 COM-Port is NOT matching 'by-id'. Please check your setting: tcp ⚠ HINT: Your zigbee.4 COM-Port is NOT matching 'by-id'. Please check your setting: tcp Zigbee Network Settings on your coordinator / in nvbackup are: zigbee.X \nExtended Pan ID: \n*** MASKED *** \nPan ID: \n*** MASKED *** \nChannel: \n*** MASKED *** \nNetwork Key: \n*** MASKED *** To unmask the settings run 'iob diag --unmask' === ZigBee Port Overview === Instance Configured Port Available by-id Port Status -------- ---------------- ---------------------------- ------ zigbee.0 tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 - TCP Connection zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 - TCP Connection zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 - TCP Connection zigbee.1 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 - TCP Connection zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 - TCP Connection zigbee. tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 - TCP Connection zigbee.2 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 - TCP Connection zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 - TCP Connection zigbee. tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 - TCP Connection zigbee.3 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 - TCP Connection zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 - TCP Connection zigbee. tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 - TCP Connection zigbee.4 tcp://192.168.0.99:20108 - TCP Connection zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 - TCP Connection zigbee. tcp://192.168.0.99:20108 - TCP Connection *** NodeJS-Installation *** -
Für dich als Info, zur Sicherheit lösche ich das Script vorher immer.
USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': No Devices found 'by-id' *** ZigBee Settings *** ⚠ HINT: Your zigbee.0 COM-Port is NOT matching 'by-id'. Please check your setting: tcp ⚠ HINT: Your zigbee.1 COM-Port is NOT matching 'by-id'. Please check your setting: tcp ⚠ HINT: Your zigbee.2 COM-Port is NOT matching 'by-id'. Please check your setting: tcp ⚠ HINT: Your zigbee.3 COM-Port is NOT matching 'by-id'. Please check your setting: tcp ⚠ HINT: Your zigbee.4 COM-Port is NOT matching 'by-id'. Please check your setting: tcp Zigbee Network Settings on your coordinator / in nvbackup are: zigbee.X \nExtended Pan ID: \n*** MASKED *** \nPan ID: \n*** MASKED *** \nChannel: \n*** MASKED *** \nNetwork Key: \n*** MASKED *** To unmask the settings run 'iob diag --unmask' === ZigBee Port Overview === Instance Configured Port Available by-id Port Status -------- ---------------- ---------------------------- ------ zigbee.0 tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 - TCP Connection zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 - TCP Connection zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 - TCP Connection zigbee.1 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 - TCP Connection zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 - TCP Connection zigbee. tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 - TCP Connection zigbee.2 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 - TCP Connection zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 - TCP Connection zigbee. tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 - TCP Connection zigbee.3 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 - TCP Connection zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 - TCP Connection zigbee. tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 - TCP Connection zigbee.4 tcp://192.168.0.99:20108 - TCP Connection zigbee. tcp://192.168.0.64:20108 tcp://192.168.0.69:20108 tcp://192.168.0.79:20108 tcp://192.168.0.63:20108 tcp://192.168.0.99:20108 - TCP Connection zigbee. tcp://192.168.0.99:20108 - TCP Connection *** NodeJS-Installation ***@Shadowhunter23 sagte in iob diag - Skript:
zur Sicherheit lösche ich das Script vorher immer.
Brauchst du nicht.
curl überschreibt das Ziel immer mit dem aktuellen Inhalt.Schau bitte jetzt nochmal.
585
Online32.7k
Benutzer82.5k
Themen1.3m
Beiträge