USB Port Zuweisung, fehlendes Verzeichnis /dev/serial/by-id
Einbindung von Geräten
111
Beiträge
7
Kommentatoren
17.2k
Aufrufe
6
Watching
-
-
Ah cool, das hat schon mal geklappt.
Aber sehen kann ich da dann noch nichts
pi@raspberrypi:~ $ cd /etc/apt/sources.list.d pi@raspberrypi:/etc/apt/sources.list.d $ -
@thomas-braun said in USB Port Zuweisung, fehlendes Verzeichnis /dev/serial/by-id:
ls -lAh
Ich werde noch ein Kommandozeilenprofi, wenn es so weiter geht :blush:
pi@raspberrypi:/etc/apt/sources.list.d $ ls -lAh insgesamt 20K -rw-r--r-- 1 root root 57 29. Jan 17:54 backports.list -rw-r--r-- 1 root root 93 29. Jan 17:54 bullseye-proposed-updates.list -rw-r--r-- 1 root root 100 29. Jan 17:55 nodesource.list -rw-r--r-- 1 root root 88 29. Jan 17:55 pivccu.list -rw-r--r-- 1 root root 191 29. Jan 17:55 raspi.list pi@raspberrypi:/etc/apt/sources.list.d $ -
@thomas-braun said in USB Port Zuweisung, fehlendes Verzeichnis /dev/serial/by-id:
ls -lAh
Ich werde noch ein Kommandozeilenprofi, wenn es so weiter geht :blush:
pi@raspberrypi:/etc/apt/sources.list.d $ ls -lAh insgesamt 20K -rw-r--r-- 1 root root 57 29. Jan 17:54 backports.list -rw-r--r-- 1 root root 93 29. Jan 17:54 bullseye-proposed-updates.list -rw-r--r-- 1 root root 100 29. Jan 17:55 nodesource.list -rw-r--r-- 1 root root 88 29. Jan 17:55 pivccu.list -rw-r--r-- 1 root root 191 29. Jan 17:55 raspi.list pi@raspberrypi:/etc/apt/sources.list.d $@n811e sagte in USB Port Zuweisung, fehlendes Verzeichnis /dev/serial/by-id:
sudo rm b* cd sudo apt update -
@n811e sagte in USB Port Zuweisung, fehlendes Verzeichnis /dev/serial/by-id:
sudo rm b* cd sudo apt update@thomas-braun said in USB Port Zuweisung, fehlendes Verzeichnis /dev/serial/by-id:
sudo apt update
diese 3 Zeilen, soll ich jetzt nacheinander eingeben?
-
@thomas-braun said in USB Port Zuweisung, fehlendes Verzeichnis /dev/serial/by-id:
sudo apt update
diese 3 Zeilen, soll ich jetzt nacheinander eingeben?
-
@thomas-braun said in USB Port Zuweisung, fehlendes Verzeichnis /dev/serial/by-id:
sudo rm /etc/apt/sources.list.d/b*
Ok.
hab ich gemacht
Kannst Du mir sagen was das bewirkt? -
@thomas-braun said in USB Port Zuweisung, fehlendes Verzeichnis /dev/serial/by-id:
sudo rm /etc/apt/sources.list.d/b*
Ok.
hab ich gemacht
Kannst Du mir sagen was das bewirkt?@n811e sagte in USB Port Zuweisung, fehlendes Verzeichnis /dev/serial/by-id:
Kannst Du mir sagen was das bewirkt?
Vielleicht. Wenn du die Ausgabe von
sudo apt updatebekannt gibst.
-
@n811e sagte in USB Port Zuweisung, fehlendes Verzeichnis /dev/serial/by-id:
Kannst Du mir sagen was das bewirkt?
Vielleicht. Wenn du die Ausgabe von
sudo apt updatebekannt gibst.
sudo apt update OK:1 http://security.debian.org/debian-security bookworm-security InRelease OK:2 http://deb.debian.org/debian bookworm InRelease Holen:3 http://deb.debian.org/debian bookworm-updates InRelease [52,1 kB] Holen:4 http://archive.raspberrypi.org/debian bookworm InRelease [23,6 kB] OK:5 https://apt.pivccu.de/piVCCU stable InRelease OK:6 https://deb.nodesource.com/node_18.x nodistro InRelease Holen:7 http://archive.raspberrypi.org/debian bookworm/main armhf Packages [362 kB] Es wurden 438 kB in 4 s geholt (112 kB/s). Paketlisten werden gelesen… Fertig Abhängigkeitsbaum wird aufgebaut… Fertig Statusinformationen werden eingelesen… Fertig Aktualisierung für 2 Pakete verfügbar. Führen Sie »apt list --upgradable« aus, um sie anzuzeigen. W: http://security.debian.org/debian-security/dists/bookworm-security/InRelease: Schlüssel ist im veralteten Schlüsselbund trusted.gpg gespeichert (/etc/apt/trusted.gpg), siehe den Abschnitt MISSBILLIGUNG in apt-key(8) für Details. W: http://deb.debian.org/debian/dists/bookworm/InRelease: Schlüssel ist im veralteten Schlüsselbund trusted.gpg gespeichert (/etc/apt/trusted.gpg), siehe den Abschnitt MISSBILLIGUNG in apt-key(8) für Details. W: http://deb.debian.org/debian/dists/bookworm-updates/InRelease: Schlüssel ist im veralteten Schlüsselbund trusted.gpg gespeichert (/etc/apt/trusted.gpg), siehe den Abschnitt MISSBILLIGUNG in apt-key(8) für Details. -
sudo apt update OK:1 http://security.debian.org/debian-security bookworm-security InRelease OK:2 http://deb.debian.org/debian bookworm InRelease Holen:3 http://deb.debian.org/debian bookworm-updates InRelease [52,1 kB] Holen:4 http://archive.raspberrypi.org/debian bookworm InRelease [23,6 kB] OK:5 https://apt.pivccu.de/piVCCU stable InRelease OK:6 https://deb.nodesource.com/node_18.x nodistro InRelease Holen:7 http://archive.raspberrypi.org/debian bookworm/main armhf Packages [362 kB] Es wurden 438 kB in 4 s geholt (112 kB/s). Paketlisten werden gelesen… Fertig Abhängigkeitsbaum wird aufgebaut… Fertig Statusinformationen werden eingelesen… Fertig Aktualisierung für 2 Pakete verfügbar. Führen Sie »apt list --upgradable« aus, um sie anzuzeigen. W: http://security.debian.org/debian-security/dists/bookworm-security/InRelease: Schlüssel ist im veralteten Schlüsselbund trusted.gpg gespeichert (/etc/apt/trusted.gpg), siehe den Abschnitt MISSBILLIGUNG in apt-key(8) für Details. W: http://deb.debian.org/debian/dists/bookworm/InRelease: Schlüssel ist im veralteten Schlüsselbund trusted.gpg gespeichert (/etc/apt/trusted.gpg), siehe den Abschnitt MISSBILLIGUNG in apt-key(8) für Details. W: http://deb.debian.org/debian/dists/bookworm-updates/InRelease: Schlüssel ist im veralteten Schlüsselbund trusted.gpg gespeichert (/etc/apt/trusted.gpg), siehe den Abschnitt MISSBILLIGUNG in apt-key(8) für Details.@n811e sagte in USB Port Zuweisung, fehlendes Verzeichnis /dev/serial/by-id:
sudo mv /etc/apt/trusted.gpg /etc/apt/trusted.gpg.d/ sudo apt update sudo apt full-upgrade -
@n811e sagte in USB Port Zuweisung, fehlendes Verzeichnis /dev/serial/by-id:
sudo mv /etc/apt/trusted.gpg /etc/apt/trusted.gpg.d/ sudo apt update sudo apt full-upgrade -
ok, habe ich so gemacht
Zigbee bleibt aber auch nach einem Neustart Gelb :confused: -
@thomas-braun said in USB Port Zuweisung, fehlendes Verzeichnis /dev/serial/by-id:
iob diag
da kommt folgendes raus:
======== Start marking the full check here =========
Skript v.2023-10-10 *** BASE SYSTEM *** Static hostname: raspberrypi Icon name: computer Operating System: Debian GNU/Linux 12 (bookworm) Kernel: Linux 6.1.21-v7l+ Architecture: arm Model : Raspberry Pi 4 Model B Rev 1.4 Docker : false Virtualization : none Kernel : armv7l Userland : armhf Systemuptime and Load: 21:17:24 up 52 min, 2 users, load average: 1.87, 1.77, 1.70 CPU threads: 4 *** RASPBERRY THROTTLING *** Current issues: No throttling issues detected. Previously detected issues: No throttling issues detected. *** Time and Time Zones *** Local time: Tue 2024-01-30 21:17:25 CET Universal time: Tue 2024-01-30 20:17:25 UTC RTC time: Tue 2024-01-30 20:17:25 Time zone: Europe/Berlin (CET, +0100) System clock synchronized: yes NTP service: active RTC in local TZ: no *** User and Groups *** pi /home/pi pi adm dialout cdrom sudo audio video plugdev games users input render netdev gpio i2c spi iobroker *** X-Server-Setup *** X-Server: false Desktop: Terminal: tty Boot Target: graphical.target *** MEMORY *** total used free shared buff/cache available Mem: 8.3G 2.4G 5.7G 1.0M 355M 5.8G Swap: 104M 0B 104M Total: 8.4G 2.4G 5.8G 7898 M total memory 2320 M used memory 106 M active memory 2196 M inactive memory 5464 M free memory 32 M buffer memory 306 M swap cache 99 M total swap 0 M used swap 99 M free swap Raspberry only: oom events: 0 lifetime oom required: 0 Mbytes total time in oom handler: 0 ms max time spent in oom handler: 0 ms *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/root ext4 117G 8.0G 105G 8% / devtmpfs devtmpfs 3.7G 0 3.7G 0% /dev tmpfs tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs tmpfs 1.6G 912K 1.6G 1% /run tmpfs tmpfs 5.0M 16K 5.0M 1% /run/lock /dev/mmcblk0p1 vfat 253M 51M 202M 20% /boot tmpfs tmpfs 790M 0 790M 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Tue Jan 30 20:24:31 2024] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 smsc95xx.macaddr=DC:A6:32:CB:3B:DC vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=tty1 root=PARTUUID=4927e89a-02 rootfstype=ext4 fsck.repair=yes rootwait [Tue Jan 30 20:24:32 2024] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Quota mode: none. [Tue Jan 30 20:24:32 2024] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. [Tue Jan 30 20:24:36 2024] EXT4-fs (mmcblk0p2): re-mounted. Quota mode: none. Show mounted filesystems \(real ones only\): TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime `-/boot /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,flush,errors=remount-ro Files in neuralgic directories: /var: 2.0G /var/ 1.1G /var/log/journal/ce513f1a44ff4c9dbd382eb66e08c51e 1.1G /var/log/journal 1.1G /var/log 709M /var/lib Archived and active journals take up 1.0G in the file system. /opt/iobroker/backups: 93M /opt/iobroker/backups/ 4.0K /opt/iobroker/backups/redistmp /opt/iobroker/iobroker-data: 477M /opt/iobroker/iobroker-data/ 317M /opt/iobroker/iobroker-data/files 102M /opt/iobroker/iobroker-data/backup-objects 67M /opt/iobroker/iobroker-data/files/javascript.admin 48M /opt/iobroker/iobroker-data/files/javascript.admin/static The five largest files in iobroker-data are: 34M /opt/iobroker/iobroker-data/objects.jsonl 33M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.1797d034.js.map 27M /opt/iobroker/iobroker-data/files/material/static/js/2.73100bd6.chunk.js.map 25M /opt/iobroker/iobroker-data/states.jsonl 21M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.aaea95f8.js.map USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/* in your adapter setups, please always prefer the links 'by-id': /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_46f93a68f7d8eb11893d0815b9da5f8b-if00-port0 *** NodeJS-Installation *** /usr/bin/nodejs v18.19.0 /usr/bin/node v18.19.0 /usr/bin/npm 10.2.3 /usr/bin/npx 10.2.3 /usr/bin/corepack 0.22.0 nodejs: Installed: 18.19.0-1nodesource1 Candidate: 18.19.0-1nodesource1 Version table: 18.19.0+dfsg-6~deb12u1 500 500 http://security.debian.org/debian-security bookworm-security/main armhf Packages *** 18.19.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 100 /var/lib/dpkg/status 18.18.2-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.18.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.17.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.16.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.14.2-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.14.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.13.0+dfsg1-1 500 500 http://deb.debian.org/debian bookworm/main armhf Packages 18.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.9.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages Temp directories causing npm8 problem: 0 No problems detected Errors in npm tree: *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Core adapters versions js-controller: 5.0.17 admin: 6.12.0 javascript: 7.1.6 Adapters from github: 1 Adapter State + system.adapter.admin.3 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.alexa2.0 : alexa2 : raspberrypi - enabled + system.adapter.backitup.0 : backitup : raspberrypi - enabled + system.adapter.cloud.0 : cloud : raspberrypi - enabled + system.adapter.device-watcher.0 : device-watcher : raspberrypi - enabled + system.adapter.discovery.0 : discovery : raspberrypi - enabled + system.adapter.ecovacs-deebot.0 : ecovacs-deebot : raspberrypi - enabled + system.adapter.history.0 : history : raspberrypi - enabled + system.adapter.hm-rega.0 : hm-rega : raspberrypi - enabled + system.adapter.hm-rpc.0 : hm-rpc : raspberrypi - enabled, port: 12001 + system.adapter.hm-rpc.1 : hm-rpc : raspberrypi - enabled, port: 12010 + system.adapter.hm-rpc.2 : hm-rpc : raspberrypi - enabled, port: 0 + system.adapter.homeconnect.0 : homeconnect : raspberrypi - enabled + system.adapter.iot.0 : iot : raspberrypi - enabled + system.adapter.jarvis.0 : jarvis : raspberrypi - enabled + system.adapter.javascript.0 : javascript : raspberrypi - enabled + system.adapter.klf200.0 : klf200 : raspberrypi - enabled + system.adapter.mqtt.0 : mqtt : raspberrypi - enabled, port: 1886, bind: 0.0.0.0 + system.adapter.net-tools.0 : net-tools : raspberrypi - enabled + system.adapter.omada.0 : omada : raspberrypi - enabled, port: 443 + system.adapter.onvif.0 : onvif : raspberrypi - enabled, port: 80, 7575, 8000, 8080, 8081, 8899 + system.adapter.pushover.0 : pushover : raspberrypi - enabled + system.adapter.samsung.0 : samsung : raspberrypi - enabled + system.adapter.samsung_tizen.0 : samsung_tizen : raspberrypi - enabled, port: 8002 + system.adapter.scenes.0 : scenes : raspberrypi - enabled + system.adapter.shelly.0 : shelly : raspberrypi - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.shelly.1 : shelly : raspberrypi - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.sonoff.0 : sonoff : raspberrypi - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.synology.0 : synology : raspberrypi - enabled, port: 5000 + system.adapter.tankerkoenig.0 : tankerkoenig : raspberrypi - enabled + system.adapter.tr-064.0 : tr-064 : raspberrypi - enabled + system.adapter.tuya.0 : tuya : raspberrypi - enabled + system.adapter.upnp.0 : upnp : raspberrypi - enabled system.adapter.vis-canvas-gauges.0 : vis-canvas-gauges : raspberrypi - disabled system.adapter.vis-colorpicker.0 : vis-colorpicker : raspberrypi - disabled system.adapter.vis-hqwidgets.0 : vis-hqwidgets : raspberrypi - disabled system.adapter.vis-icontwo.0 : vis-icontwo : raspberrypi - disabled + system.adapter.vis-inventwo.0 : vis-inventwo : raspberrypi - enabled system.adapter.vis-jqui-mfd.0 : vis-jqui-mfd : raspberrypi - disabled system.adapter.vis-material-webfont.0 : vis-material-webfont : raspberrypi - enabled system.adapter.vis-materialdesign.0 : vis-materialdesign : raspberrypi - enabled system.adapter.vis-plumb.0 : vis-plumb : raspberrypi - disabled system.adapter.vis-timeandweather.0 : vis-timeandweather : raspberrypi - enabled system.adapter.vis.0 : vis : raspberrypi - enabled + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.wled.0 : wled : raspberrypi - enabled + system.adapter.worx.0 : worx : raspberrypi - enabled + system.adapter.yahka.0 : yahka : raspberrypi - enabled + system.adapter.zigbee.0 : zigbee : raspberrypi - enabled, port: /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_46f93a68f7d8eb11893d0815b9da5f8b-if00-port0 system.adapter.zigbee2mqtt.0 : zigbee2mqtt : raspberrypi - disabled + instance is alive Enabled adapters with bindings + system.adapter.admin.3 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.hm-rpc.0 : hm-rpc : raspberrypi - enabled, port: 12001 + system.adapter.hm-rpc.1 : hm-rpc : raspberrypi - enabled, port: 12010 + system.adapter.hm-rpc.2 : hm-rpc : raspberrypi - enabled, port: 0 + system.adapter.mqtt.0 : mqtt : raspberrypi - enabled, port: 1886, bind: 0.0.0.0 + system.adapter.omada.0 : omada : raspberrypi - enabled, port: 443 + system.adapter.onvif.0 : onvif : raspberrypi - enabled, port: 80, 7575, 8000, 8080, 8081, 8899 + system.adapter.samsung_tizen.0 : samsung_tizen : raspberrypi - enabled, port: 8002 + system.adapter.shelly.0 : shelly : raspberrypi - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.shelly.1 : shelly : raspberrypi - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.sonoff.0 : sonoff : raspberrypi - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.synology.0 : synology : raspberrypi - enabled, port: 5000 + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.zigbee.0 : zigbee : raspberrypi - enabled, port: /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_46f93a68f7d8eb11893d0815b9da5f8b-if00-port0 ioBroker-Repositories stable : http://download.iobroker.net/sources-dist.json beta : http://download.iobroker.net/sources-dist-latest.json Active repo(s): stable Installed ioBroker-Instances Used repository: stable Adapter "admin" : 6.13.15 , installed 6.12.0 [Updatable] Adapter "alexa2" : 3.26.4 , installed 3.26.3 [Updatable] Adapter "alias-manager": 1.2.6 , installed 1.2.6 Adapter "backitup" : 2.9.8 , installed 2.9.8 Adapter "cloud" : 4.4.1 , installed 4.4.1 Adapter "device-watcher": 2.9.6 , installed 2.9.6 Adapter "discovery" : 4.2.0 , installed 4.2.0 Adapter "ds18b20" : 2.0.5 , installed 2.0.5 Adapter "ecovacs-deebot": 1.4.13 , installed 1.4.13 Adapter "history" : 3.0.1 , installed 3.0.1 Adapter "hm-rega" : 4.0.0 , installed 4.0.0 Adapter "hm-rpc" : 1.16.0 , installed 1.15.19 [Updatable] Adapter "homeconnect" : 1.3.0 , installed 1.3.0 Adapter "iot" : 2.0.11 , installed 2.0.11 Adapter "jarvis" : 3.1.8 , installed 3.1.8 Adapter "javascript" : 7.1.6 , installed 7.1.6 Controller "js-controller": 5.0.17 , installed 5.0.17 Adapter "klf200" : 1.1.2 , installed 1.1.2 Adapter "mqtt" : 5.1.0 , installed 5.1.0 Adapter "net-tools" : 0.2.0 , installed 0.2.0 Adapter "onvif" : 1.1.1 , installed 1.1.1 Adapter "pushover" : 3.0.6 , installed 3.0.6 Adapter "samsung" : 0.5.11 , installed 0.5.11 Adapter "samsung_tizen": 1.0.0 , installed 1.0.0 Adapter "scenes" : 2.3.9 , installed 2.3.9 Adapter "shelly" : 6.6.1 , installed 6.6.1 Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "socketio" : 6.6.0 , installed 6.6.0 Adapter "sonoff" : 3.0.3 , installed 3.0.3 Adapter "synology" : 3.0.1 , installed 3.0.1 Adapter "tankerkoenig" : 3.3.7 , installed 3.3.7 Adapter "tr-064" : 4.2.18 , installed 4.2.18 Adapter "tuya" : 3.15.0 , installed 3.15.0 Adapter "upnp" : 1.0.21 , installed 1.0.21 Adapter "vis" : 1.5.4 , installed 1.5.4 Adapter "vis-canvas-gauges": 1.0.1, installed 1.0.1 Adapter "vis-colorpicker": 2.0.3 , installed 2.0.3 Adapter "vis-hqwidgets": 1.4.0 , installed 1.4.0 Adapter "vis-icontwo" : 1.3.0 , installed 1.3.0 Adapter "vis-inventwo" : 3.3.3 , installed 3.3.3 Adapter "vis-jqui-mfd" : 1.0.12 , installed 1.0.12 Adapter "vis-materialdesign": 0.5.9, installed 0.5.9 Adapter "vis-plumb" : 1.0.2 , installed 1.0.2 Adapter "vis-timeandweather": 1.2.2, installed 1.2.2 Adapter "web" : 6.2.3 , installed 6.1.10 [Updatable] Adapter "wled" : 0.7.2 , installed 0.7.2 Adapter "worx" : 2.3.4 , installed 2.3.4 Adapter "ws" : 2.5.10 , installed 2.5.8 [Updatable] Adapter "yahka" : 1.0.3 , installed 1.0.3 Adapter "zigbee" : 1.10.1 , installed 1.10.1 Adapter "zigbee2mqtt" : 2.13.4 , installed 2.13.4 Objects and States Please stand by - This may take a while Objects: 19613 States: 15311 *** OS-Repositories and Updates *** Hit:1 http://archive.raspberrypi.org/debian bookworm InRelease Hit:2 http://deb.debian.org/debian bookworm InRelease Hit:3 http://deb.debian.org/debian bookworm-updates InRelease Hit:4 http://security.debian.org/debian-security bookworm-security InRelease Hit:5 https://deb.nodesource.com/node_18.x nodistro InRelease Hit:6 https://apt.pivccu.de/piVCCU stable InRelease Reading package lists... Pending Updates: 0 *** Listening Ports *** Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 0.0.0.0:1886 0.0.0.0:* LISTEN 1001 19220 2620/io.mqtt.0 tcp 0 0 0.0.0.0:1882 0.0.0.0:* LISTEN 1001 19188 2568/io.shelly.1 tcp 0 0 0.0.0.0:1883 0.0.0.0:* LISTEN 1001 21636 2483/io.sonoff.0 tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 17641 964/iobroker.js-con tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 17653 964/iobroker.js-con tcp 0 0 10.0.3.1:53 0.0.0.0:* LISTEN 0 14899 1035/dnsmasq tcp 0 0 192.168.2.113:9292 0.0.0.0:* LISTEN 1001 18414 2281/io.hm-rpc.2 tcp 0 0 0.0.0.0:8400 0.0.0.0:* LISTEN 1001 24624 2907/io.jarvis.0 tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 17410 1024/sshd: /usr/sbi tcp 0 0 192.168.2.113:12010 0.0.0.0:* LISTEN 1001 17407 2232/io.hm-rpc.1 tcp 0 0 192.168.2.113:12001 0.0.0.0:* LISTEN 1001 19532 2200/io.hm-rpc.0 tcp6 0 0 :::8095 :::* LISTEN 1001 23137 3015/io.onvif.0 tcp6 0 0 :::8082 :::* LISTEN 1001 21252 2795/io.web.0 tcp6 0 0 :::8081 :::* LISTEN 1001 17072 1811/io.admin.3 tcp6 0 0 :::8000 :::* LISTEN 1001 25799 2868/io.upnp.0 tcp6 0 0 :::46799 :::* LISTEN 1001 20335 2808/io.yahka.0 tcp6 0 0 :::22 :::* LISTEN 0 17412 1024/sshd: /usr/sbi udp 0 0 0.0.0.0:5353 0.0.0.0:* 1001 23644 2949/io.wled.0 udp 0 0 192.168.2.113:5353 0.0.0.0:* 1001 20016 2512/io.tr-064.0 udp 0 0 0.0.0.0:5353 0.0.0.0:* 108 12028 403/avahi-daemon: r udp 0 0 0.0.0.0:1900 0.0.0.0:* 1001 21502 2868/io.upnp.0 udp 0 0 0.0.0.0:35724 0.0.0.0:* 1001 23568 2868/io.upnp.0 udp 0 0 0.0.0.0:40457 0.0.0.0:* 108 12030 403/avahi-daemon: r udp 0 0 0.0.0.0:6666 0.0.0.0:* 1001 21897 2633/io.tuya.0 udp 0 0 0.0.0.0:6667 0.0.0.0:* 1001 21898 2633/io.tuya.0 udp 0 0 0.0.0.0:5683 0.0.0.0:* 1001 20629 2412/io.shelly.0 udp 0 0 10.0.3.1:53 0.0.0.0:* 0 14898 1035/dnsmasq udp 0 0 0.0.0.0:67 0.0.0.0:* 0 14895 1035/dnsmasq udp 0 0 0.0.0.0:68 0.0.0.0:* 0 909 846/dhclient udp6 0 0 :::51412 :::* 108 12031 403/avahi-daemon: r udp6 0 0 :::5353 :::* 108 12029 403/avahi-daemon: r *** Log File - Last 25 Lines *** 2024-01-30 21:14:11.605 - error: shelly.1 (2568) [MQTT] Wrong MQTT authentification of client "shellyplus1-a8032abcbcd8" 2024-01-30 21:14:11.628 - info: shelly.1 (2568) [MQTT] Client Close: (shellyplus1 / shellyplus1-a8032abcbcd8 / shellyplus1#a8032abcbcd8#1) (false) 2024-01-30 21:14:39.489 - info: javascript.0 (1828) script.js.Beleuchtung.Debug_Licht: Wert:trueWert:system.adapter.shelly.1bestätigt:true 2024-01-30 21:15:06.296 - error: shelly.1 (2568) [MQTT] Wrong MQTT authentification of client "shellyplus1-a8032abcbcd8" 2024-01-30 21:15:06.325 - info: shelly.1 (2568) [MQTT] Client Close: (shellyplus1 / shellyplus1-a8032abcbcd8 / shellyplus1#a8032abcbcd8#1) (false) 2024-01-30 21:15:09.499 - info: javascript.0 (1828) script.js.Beleuchtung.Debug_Licht: Wert:trueWert:system.adapter.shelly.1bestätigt:true 2024-01-30 21:15:15.639 - info: tr-064.0 (2512) forEachConfiguredDevice: in GetSpecificHostEntry 13(fritz.box/08:96:D7:8B:8C:54) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpecificHostEntry serviceType=urn:dslforum-org:service:Hosts:1: 500 - {"code":500} 2024-01-30 21:15:39.543 - info: javascript.0 (1828) script.js.Beleuchtung.Debug_Licht: Wert:trueWert:system.adapter.shelly.1bestätigt:true 2024-01-30 21:16:02.990 - error: shelly.1 (2568) [MQTT] Wrong MQTT authentification of client "shellyplus1-a8032abcbcd8" 2024-01-30 21:16:03.009 - info: shelly.1 (2568) [MQTT] Client Close: (shellyplus1 / shellyplus1-a8032abcbcd8 / shellyplus1#a8032abcbcd8#1) (false) 2024-01-30 21:16:09.575 - info: javascript.0 (1828) script.js.Beleuchtung.Debug_Licht: Wert:trueWert:system.adapter.shelly.1bestätigt:true 2024-01-30 21:16:39.565 - info: javascript.0 (1828) script.js.Beleuchtung.Debug_Licht: Wert:trueWert:system.adapter.shelly.1bestätigt:true 2024-01-30 21:16:47.975 - info: tr-064.0 (2512) forEachConfiguredDevice: in GetSpecificHostEntry 13(fritz.box/08:96:D7:8B:8C:54) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpecificHostEntry serviceType=urn:dslforum-org:service:Hosts:1: 500 - {"code":500} 2024-01-30 21:16:59.510 - error: shelly.1 (2568) [MQTT] Wrong MQTT authentification of client "shellyplus1-a8032abcbcd8" 2024-01-30 21:16:59.532 - info: shelly.1 (2568) [MQTT] Client Close: (shellyplus1 / shellyplus1-a8032abcbcd8 / shellyplus1#a8032abcbcd8#1) (false) 2024-01-30 21:17:09.594 - info: javascript.0 (1828) script.js.Beleuchtung.Debug_Licht: Wert:trueWert:system.adapter.shelly.1bestätigt:true 2024-01-30 21:17:39.602 - info: javascript.0 (1828) script.js.Beleuchtung.Debug_Licht: Wert:trueWert:system.adapter.shelly.1bestätigt:true 2024-01-30 21:17:56.062 - error: shelly.1 (2568) [MQTT] Wrong MQTT authentification of client "shellyplus1-a8032abcbcd8" 2024-01-30 21:17:56.088 - info: shelly.1 (2568) [MQTT] Client Close: (shellyplus1 / shellyplus1-a8032abcbcd8 / shellyplus1#a8032abcbcd8#1) (false) 2024-01-30 21:18:09.613 - info: javascript.0 (1828) script.js.Beleuchtung.Debug_Licht: Wert:trueWert:system.adapter.shelly.1bestätigt:true 2024-01-30 21:18:19.159 - info: tr-064.0 (2512) forEachConfiguredDevice: in GetSpecificHostEntry 13(fritz.box/08:96:D7:8B:8C:54) device seems offline but we never saw it since adapter was started:Error: sendSOAPActionRequest Error action=GetSpecificHostEntry serviceType=urn:dslforum-org:service:Hosts:1: 500 - {"code":500} 2024-01-30 21:18:39.618 - info: javascript.0 (1828) script.js.Beleuchtung.Debug_Licht: Wert:trueWert:system.adapter.shelly.1bestätigt:true 2024-01-30 21:18:55.875 - error: shelly.1 (2568) [MQTT] Wrong MQTT authentification of client "shellyplus1-a8032abcbcd8" 2024-01-30 21:18:55.894 - info: shelly.1 (2568) [MQTT] Client Close: (shellyplus1 / shellyplus1-a8032abcbcd8 / shellyplus1#a8032abcbcd8#1) (false) 2024-01-30 21:19:09.575 - info: javascript.0 (1828) script.js.Beleuchtung.Debug_Licht: Wert:trueWert:system.adapter.shelly.1bestätigt:true============ Mark until here for C&P =============
iob diag has finished.
Press any key for a summary
-
Copy text starting here:
======================= SUMMARY ======================= v.2023-10-10 Static hostname: raspberrypi Icon name: computer Operating System: Debian GNU/Linux 12 (bookworm) Kernel: Linux 6.1.21-v7l+ Architecture: arm Installation: native Kernel: armv7l Userland: armhf Timezone: Europe/Berlin (CET, +0100) User-ID: 1000 X-Server: false Boot Target: graphical.target Pending OS-Updates: 0 Pending iob updates: 5 Nodejs-Installation: /usr/bin/nodejs v18.19.0 /usr/bin/node v18.19.0 /usr/bin/npm 10.2.3 /usr/bin/npx 10.2.3 /usr/bin/corepack 0.22.0 Recommended versions are nodejs 18.19.0 and npm 10.2.3 Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 8.3G 2.5G 5.6G 1.0M 472M 5.8G Swap: 104M 0B 104M Total: 8.4G 2.5G 5.7G Active iob-Instances: 40 Active repo(s): stable ioBroker Core: js-controller 5.0.17 admin 6.12.0 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: + system.adapter.admin.3 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 19613 States: 15311 Size of iob-Database: 34M /opt/iobroker/iobroker-data/objects.jsonl 4.1M /opt/iobroker/iobroker-data/states.jsonl =================== END OF SUMMARY ======================= Mark text until here for copying ===
-
Copy text starting here:
======================= SUMMARY ======================= v.2023-10-10 Static hostname: raspberrypi Icon name: computer Operating System: Debian GNU/Linux 12 (bookworm) Kernel: Linux 6.1.21-v7l+ Architecture: arm Installation: native Kernel: armv7l Userland: armhf Timezone: Europe/Berlin (CET, +0100) User-ID: 1000 X-Server: false Boot Target: graphical.target Pending OS-Updates: 0 Pending iob updates: 5 Nodejs-Installation: /usr/bin/nodejs v18.19.0 /usr/bin/node v18.19.0 /usr/bin/npm 10.2.3 /usr/bin/npx 10.2.3 /usr/bin/corepack 0.22.0 Recommended versions are nodejs 18.19.0 and npm 10.2.3 Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 8.3G 2.5G 5.6G 1.0M 472M 5.8G Swap: 104M 0B 104M Total: 8.4G 2.5G 5.7G Active iob-Instances: 40 Active repo(s): stable ioBroker Core: js-controller 5.0.17 admin 6.12.0 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: + system.adapter.admin.3 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 19613 States: 15311 Size of iob-Database: 34M /opt/iobroker/iobroker-data/objects.jsonl 4.1M /opt/iobroker/iobroker-data/states.jsonl =================== END OF SUMMARY ======================= Mark text until here for copying ===
Und der Adapter 'Kaltstart' sieht im Log wie aus?
Instanz stoppen,
iob logs --watch | uniqanschauen, Instanz wieder starten.
-
Und der Adapter 'Kaltstart' sieht im Log wie aus?
Instanz stoppen,
iob logs --watch | uniqanschauen, Instanz wieder starten.
Was soll ich denn alles kopieren, nachdem ich iob logs --watch | uniq eingegeben habe?
Der hört ja nie auf, oder wie verstehe ich das? -
Was soll ich denn alles kopieren, nachdem ich iob logs --watch | uniq eingegeben habe?
Der hört ja nie auf, oder wie verstehe ich das?@n811e den Start der Instanz, die du extra vorher gestoppt hast
-
Was soll ich denn alles kopieren, nachdem ich iob logs --watch | uniq eingegeben habe?
Der hört ja nie auf, oder wie verstehe ich das?@n811e sagte in USB Port Zuweisung, fehlendes Verzeichnis /dev/serial/by-id:
Der hört ja nie auf, oder wie verstehe ich das?
Mit
Strg-Chört 'der' auch wieder auf das Log anzuzeigen. -
@thomas-braun said in USB Port Zuweisung, fehlendes Verzeichnis /dev/serial/by-id:
iob logs --watch | uniq
So, jetzt habe ichs:
2024-01-31 20:02:23.295 - info: host.raspberrypi "system.adapter.zigbee.0" enabled 2024-01-31 20:02:24.689 - info: host.raspberrypi instance system.adapter.zigbee.0 started with pid 17095 2024-01-31 20:02:37.047 - info: zigbee.0 (17095) starting. Version 1.10.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.19.0, js-controller: 5.0.17 2024-01-31 20:02:37.259 - info: zigbee.0 (17095) delete old Backup files. keep only last 10 2024-01-31 20:02:37.265 - info: zigbee.0 (17095) Starting Zigbee npm ... 2024-01-31 20:02:37.047 - info: zigbee.0 (17095) starting. Version 1.10.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.19.0, js-controller: 5.0.17 2024-01-31 20:02:37.259 - info: zigbee.0 (17095) delete old Backup files. keep only last 10 2024-01-31 20:02:37.265 - info: zigbee.0 (17095) Starting Zigbee npm ... 2024-01-31 20:02:38.106 - info: zigbee.0 (17095) Installed Version: iobroker.zigbee@1.10.1 2024-01-31 20:03:44.528 - error: zigbee.0 (17095) Starting zigbee-herdsman problem : "network commissioning timed out - most likely network with the same panId or extendedPanId already exists nearby" 2024-01-31 20:03:44.531 - error: zigbee.0 (17095) Failed to start Zigbee 2024-01-31 20:03:44.532 - error: zigbee.0 (17095) Error herdsman start 2024-01-31 20:03:44.528 - error: zigbee.0 (17095) Starting zigbee-herdsman problem : "network commissioning timed out - most likely network with the same panId or extendedPanId already exists nearby" -
@thomas-braun said in USB Port Zuweisung, fehlendes Verzeichnis /dev/serial/by-id:
iob logs --watch | uniq
So, jetzt habe ichs:
2024-01-31 20:02:23.295 - info: host.raspberrypi "system.adapter.zigbee.0" enabled 2024-01-31 20:02:24.689 - info: host.raspberrypi instance system.adapter.zigbee.0 started with pid 17095 2024-01-31 20:02:37.047 - info: zigbee.0 (17095) starting. Version 1.10.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.19.0, js-controller: 5.0.17 2024-01-31 20:02:37.259 - info: zigbee.0 (17095) delete old Backup files. keep only last 10 2024-01-31 20:02:37.265 - info: zigbee.0 (17095) Starting Zigbee npm ... 2024-01-31 20:02:37.047 - info: zigbee.0 (17095) starting. Version 1.10.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.19.0, js-controller: 5.0.17 2024-01-31 20:02:37.259 - info: zigbee.0 (17095) delete old Backup files. keep only last 10 2024-01-31 20:02:37.265 - info: zigbee.0 (17095) Starting Zigbee npm ... 2024-01-31 20:02:38.106 - info: zigbee.0 (17095) Installed Version: iobroker.zigbee@1.10.1 2024-01-31 20:03:44.528 - error: zigbee.0 (17095) Starting zigbee-herdsman problem : "network commissioning timed out - most likely network with the same panId or extendedPanId already exists nearby" 2024-01-31 20:03:44.531 - error: zigbee.0 (17095) Failed to start Zigbee 2024-01-31 20:03:44.532 - error: zigbee.0 (17095) Error herdsman start 2024-01-31 20:03:44.528 - error: zigbee.0 (17095) Starting zigbee-herdsman problem : "network commissioning timed out - most likely network with the same panId or extendedPanId already exists nearby"@n811e sagte in USB Port Zuweisung, fehlendes Verzeichnis /dev/serial/by-id:
2024-01-31 20:03:44.528 - error: zigbee.0 (17095) Starting zigbee-herdsman problem : "network commissioning timed out - most likely network with the same panId or extendedPanId already exists nearby"
Versuch doch mal eine andere PanId, offenbar funkt da noch ein anderes Netzwerk in deinen Bereich.
Kann sein, dass du anschließend alles neu anlernen musst.
Support us
505
Online32.7k
Benutzer82.4k
Themen1.3m
Beiträge