Slave startet nicht mehr
-
@wusa sagte in Slave startet nicht mehr:
Wenn ich mir das Dateisystem zerschieße, dann stelle ich mir vor, dass die ganze Kiste nicht mehr funktioniert.
Nein, es sind Teile (inodes) defekt. Welche Auswirkungen das hat hängt davon ab, was in diesen Bereichen gespeichert war.
Ich denke hier ist ein Modul aus dem backitup-Adapter zerschossen. Deswegen den ach Möglichkeit noch mal drüber installieren.
-
@wusa sagte in Slave startet nicht mehr:
dann stelle ich mir vor, dass die ganze Kiste nicht mehr funktioniert.
das wäre der worst case, je nachdem wie man es sieht.
Ob es jetzt noch schlimmer ist wenn nur einzelne Dateien defekt sind, von denrn man nur nichts weiß, die aber schlafende Zeitbomben sind, bleibt deiner Wertung überlassen.@wusa sagte in Slave startet nicht mehr:
Ich denke hier ist mehr kaputt?
das sind Probleme von möglicherweise krummen Installationen
-
@thomas-braun sagte in Slave startet nicht mehr:
Ich denke hier ist ein Modul aus dem backitup-Adapter zerschossen. Deswegen den ach Möglichkeit noch mal drüber installieren.
Folgendes kommt beim drüber installieren:
pi@iob-slave:/opt/iobroker $ iob upgrade backitup@2.9.8 node:internal/modules/package_json_reader:92 throw error; ^ SyntaxError: Error parsing /opt/iobroker/node_modules/fs-extra/package.json: Unexpected end of JSON input at parse (<anonymous>) at read (node:internal/modules/package_json_reader:79:16) at readPackage (node:internal/modules/package_json_reader:140:10) at resolveExports (node:internal/modules/cjs/loader:580:15) at Module._findPath (node:internal/modules/cjs/loader:658:31) at Module._resolveFilename (node:internal/modules/cjs/loader:1120:27) at Module._load (node:internal/modules/cjs/loader:975:27) at Module.require (node:internal/modules/cjs/loader:1225:19) at require (node:internal/modules/helpers:177:18) at Object.<anonymous> (/opt/iobroker/node_modules/@iobroker/js-controller-cli/build/lib/setup.js:30:36) { path: '/opt/iobroker/node_modules/fs-extra/package.json' } Node.js v18.19.0 pi@iob-slave:/opt/iobroker $ -
Dann ist da
package_json_readerauch zerschossen.
Da ich den aber gar nicht im ioBroker habe kann ich dir auch nicht sagen wo du da ansetzten kannst.echad@chet:/opt/iobroker $ npm ls package_json_reader iobroker.inst@3.0.0 /opt/iobroker └── (empty) echad@chet:/opt/iobroker $ -
-
Okay, falsch geschaut...
cd /opt/iobroker npm ls fs-extrasagt?
-
Mir ist nicht bewusst, dass ich das Modul/Adapter hinzugefügt hätte.
Mir sagt fs-extra so auch nichts.
Hier ist die Ausgabepi@iob-slave:/opt/iobroker $ npm ls fs-extra npm ERR! code ELSPROBLEMS npm ERR! invalid: fs-extra@ /opt/iobroker/node_modules/fs-extra iobroker.inst@3.0.0 /opt/iobroker └─┬ iobroker.js-controller@5.0.17 ├─┬ @iobroker/db-objects-file@5.0.17 │ ├─┬ @iobroker/db-base@5.0.17 │ │ └── fs-extra@ deduped invalid: "^11.1.0" from node_modules/iobroker.js-controller, "^11.1.0" from node_modules/@iobroker/db-objects-file, "^11.1.0" from node_modules/@iobroker/db-objects-jsonl, "^11.1.0" from node_modules/@iobroker/js-controller-adapter, "^11.1.0" from node_modules/@iobroker/js-controller-cli, "^11.1.0" from node_modules/@iobroker/js-controller-common-db, "^11.1.0" from node_modules/@iobroker/js-controller-common, "^11.1.0" from node_modules/@iobroker/db-base │ └── fs-extra@ deduped invalid: "^11.1.0" from node_modules/iobroker.js-controller, "^11.1.0" from node_modules/@iobroker/db-objects-file ├─┬ @iobroker/db-objects-jsonl@5.0.17 │ ├─┬ @alcalzone/jsonl-db@3.1.0 │ │ └── fs-extra@10.1.0 │ └── fs-extra@ deduped invalid: "^11.1.0" from node_modules/iobroker.js-controller, "^11.1.0" from node_modules/@iobroker/db-objects-file, "^11.1.0" from node_modules/@iobroker/db-objects-jsonl ├─┬ @iobroker/js-controller-adapter@5.0.17 │ ├─┬ @alcalzone/pak@0.8.1 │ │ └── fs-extra@10.1.0 │ └── fs-extra@ deduped invalid: "^11.1.0" from node_modules/iobroker.js-controller, "^11.1.0" from node_modules/@iobroker/db-objects-file, "^11.1.0" from node_modules/@iobroker/db-objects-jsonl, "^11.1.0" from node_modules/@iobroker/js-controller-adapter ├─┬ @iobroker/js-controller-cli@5.0.17 │ └── fs-extra@ deduped invalid: "^11.1.0" from node_modules/iobroker.js-controller, "^11.1.0" from node_modules/@iobroker/db-objects-file, "^11.1.0" from node_modules/@iobroker/db-objects-jsonl, "^11.1.0" from node_modules/@iobroker/js-controller-adapter, "^11.1.0" from node_modules/@iobroker/js-controller-cli ├─┬ @iobroker/js-controller-common-db@5.0.17 │ └── fs-extra@ deduped invalid: "^11.1.0" from node_modules/iobroker.js-controller, "^11.1.0" from node_modules/@iobroker/db-objects-file, "^11.1.0" from node_modules/@iobroker/db-objects-jsonl, "^11.1.0" from node_modules/@iobroker/js-controller-adapter, "^11.1.0" from node_modules/@iobroker/js-controller-cli, "^11.1.0" from node_modules/@iobroker/js-controller-common-db ├─┬ @iobroker/js-controller-common@5.0.17 │ └── fs-extra@ deduped invalid: "^11.1.0" from node_modules/iobroker.js-controller, "^11.1.0" from node_modules/@iobroker/db-objects-file, "^11.1.0" from node_modules/@iobroker/db-objects-jsonl, "^11.1.0" from node_modules/@iobroker/js-controller-adapter, "^11.1.0" from node_modules/@iobroker/js-controller-cli, "^11.1.0" from node_modules/@iobroker/js-controller-common-db, "^11.1.0" from node_modules/@iobroker/js-controller-common └── fs-extra@ invalid: "^11.1.0" from node_modules/iobroker.js-controller, "^11.1.0" from node_modules/@iobroker/db-objects-file, "^11.1.0" from node_modules/@iobroker/db-objects-jsonl, "^11.1.0" from node_modules/@iobroker/js-controller-adapter, "^11.1.0" from node_modules/@iobroker/js-controller-cli, "^11.1.0" from node_modules/@iobroker/js-controller-common-db, "^11.1.0" from node_modules/@iobroker/js-controller-common npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2024-02-10T15_34_53_777Z-debug-0.log pi@iob-slave:/opt/iobroker $ -
@wusa sagte in Slave startet nicht mehr:
Mir ist nicht bewusst, dass ich das Modul/Adapter hinzugefügt hätte.
also nichts aus javascript oder node-red o.ä.
@wusa sagte in Slave startet nicht mehr:
die Ausgabe
deutet dann wohl eher auf den Controller hin, was ich bereits zu Beginn befürchtet hatte.
oder irgendetwas was vor langer Zeit (deswegen total veraltete Version) mal via GitHub installiert wurde
-
Da sind verweise auf eine invalide Version vorhanden.
Sauber sieht das so aus:echad@chet:/opt/iobroker $ npm ls fs-extra iobroker.inst@3.0.0 /opt/iobroker ├─┬ iobroker.backitup@2.10.10 │ └── fs-extra@11.2.0 ├─┬ iobroker.js-controller@5.0.19 │ ├─┬ @iobroker/db-objects-file@5.0.19 │ │ ├─┬ @iobroker/db-base@5.0.19 │ │ │ └── fs-extra@11.2.0 deduped │ │ └── fs-extra@11.2.0 deduped │ ├─┬ @iobroker/db-objects-jsonl@5.0.19 │ │ ├─┬ @alcalzone/jsonl-db@3.1.1 │ │ │ └── fs-extra@10.1.0 │ │ └── fs-extra@11.2.0 deduped │ ├─┬ @iobroker/js-controller-adapter@5.0.19 │ │ ├─┬ @alcalzone/pak@0.8.1 │ │ │ └── fs-extra@10.1.0 │ │ └── fs-extra@11.2.0 deduped │ ├─┬ @iobroker/js-controller-cli@5.0.19 │ │ └── fs-extra@11.2.0 deduped │ ├─┬ @iobroker/js-controller-common-db@5.0.19 │ │ └── fs-extra@11.2.0 deduped │ ├─┬ @iobroker/js-controller-common@5.0.19 │ │ └── fs-extra@11.2.0 deduped │ └── fs-extra@11.2.0 deduped └─┬ iobroker.tuya@3.15.0 └── fs-extra@11.2.0 dedupedDie 'deduped' Module verweisen auf
├─┬ iobroker.backitup@2.10.10 │ └── fs-extra@11.2.0was es aber bei dir nicht (mehr) gibt. Jag da mal ein
cd /opt/iobroker npm prunedrüber
-
Sorry jetzt hat es ein wenig gedauert.
pi@iob-slave:/opt/iobroker $ npm prune added 2 packages, removed 11 packages, and changed 7 packages in 23s 54 packages are looking for funding run `npm fund` for details pi@iob-slave:/opt/iobroker $ -
-
@homoran sagte in Slave startet nicht mehr:
oder irgendetwas was vor langer Zeit (deswegen total veraltete Version) mal via GitHub installiert wurde
Mir fällt ein, dass ich vor einiger Zeit mal auf Beta umgeschaltet hatte, damit ich einen Adapter testen kann, welcher noch nicht im Stable war. Ob das mit einspielt?
Ansonsten bin ich nur Stable unterwegs und versuche auch die Updates zügig zu machen, damit ich aktuell bin.@thomas-braun sagte in Slave startet nicht mehr:
Schaut das jetzt besser aus?
Ja schaut jetzt besser aus. Unter Hosts ist der Slave auch wieder online.
======== Start marking the full check here =========
Skript v.2023-10-10 *** BASE SYSTEM *** Static hostname: iob-slave Icon name: computer Operating System: Debian GNU/Linux 11 (bullseye) Kernel: Linux 6.1.21-v8+ Architecture: arm64 Model : Raspberry Pi 3 Model B Rev 1.2 Docker : false Virtualization : none Kernel : aarch64 Userland : arm64 Systemuptime and Load: 19:28:38 up 6:21, 3 users, load average: 0.49, 0.32, 0.36 CPU threads: 4 *** RASPBERRY THROTTLING *** Current issues: ~ Under-voltage detected ~ Arm frequency capped Previously detected issues: ~ Under-voltage has occurred ~ Arm frequency capping has occurred *** Time and Time Zones *** Local time: Sat 2024-02-10 19:28:38 CET Universal time: Sat 2024-02-10 18:28:38 UTC RTC time: n/a 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: multi-user.target *** MEMORY *** total used free shared buff/cache available Mem: 909M 357M 127M 0.0K 424M 487M Swap: 99M 0B 99M Total: 1.0G 357M 227M 909 M total memory 357 M used memory 506 M active memory 148 M inactive memory 127 M free memory 28 M buffer memory 396 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 252G 6.7G 235G 3% / devtmpfs devtmpfs 325M 0 325M 0% /dev tmpfs tmpfs 455M 0 455M 0% /dev/shm tmpfs tmpfs 182M 716K 182M 1% /run tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock /dev/sda1 vfat 253M 31M 222M 13% /boot tmpfs tmpfs 91M 0 91M 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Sat Feb 10 13:07:04 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 video=Composite-1:720x480@60i vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=tty1 root=PARTUUID=a80191bf-02 rootfstype=ext4 fsck.repair=yes rootwait [Sat Feb 10 13:07:12 2024] EXT4-fs (sda2): mounted filesystem with ordered data mode. Quota mode: none. [Sat Feb 10 13:07:12 2024] VFS: Mounted root (ext4 filesystem) readonly on device 8:2. [Sat Feb 10 13:07:15 2024] EXT4-fs (sda2): re-mounted. Quota mode: none. Show mounted filesystems \(real ones only\): TARGET SOURCE FSTYPE OPTIONS / /dev/sda2 ext4 rw,noatime `-/boot /dev/sda1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,flush,errors=remount-ro Files in neuralgic directories: /var: 4.4G /var/ 3.7G /var/log/journal/19fdaf3f36764551bcb55642e03afc3e 3.7G /var/log/journal 3.7G /var/log 400M /var/cache Archived and active journals take up 3.6G in the file system. /opt/iobroker/backups: 4.0K /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 4.4M /opt/iobroker/iobroker-data/ 1.2M /opt/iobroker/iobroker-data/files 472K /opt/iobroker/iobroker-data/files/discovery.admin 420K /opt/iobroker/iobroker-data/files/backitup.admin 252K /opt/iobroker/iobroker-data/files/admin.admin The five largest files in iobroker-data are: 2.9M /opt/iobroker/iobroker-data/objects.jsonl 340K /opt/iobroker/iobroker-data/states.jsonl 200K /opt/iobroker/iobroker-data/files/discovery.admin/words.js 164K /opt/iobroker/iobroker-data/files/backitup.admin/words.js 120K /opt/iobroker/iobroker-data/files/discovery.admin/index_m.html 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_0c8a15a4093bec11a27d9c957a0af07f-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-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 100 /var/lib/dpkg/status 18.18.2-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.18.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.17.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.16.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.14.2-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.14.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.9.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.1.0-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 12.22.12~dfsg-1~deb11u4 500 500 http://deb.debian.org/debian bullseye/main arm64 Packages 500 http://security.debian.org/debian-security bullseye-security/main arm64 Packages Temp directories causing npm8 problem: 0 No problems detected Errors in npm tree: *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. At least one iobroker host is running. Objects type: jsonl States type: jsonl Core adapters versions js-controller: 5.0.17 admin: 6.12.0 javascript: "javascript" not found Adapters from github: 0 Adapter State + system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.backitup.0 : backitup : iobroker - enabled + system.adapter.chromecast.0 : chromecast : iobroker - enabled system.adapter.devices.0 : devices : iobroker - disabled system.adapter.discovery.0 : discovery : iobroker - disabled + system.adapter.ds18b20.0 : ds18b20 : iob-slave - enabled system.adapter.ical.0 : ical : iobroker - disabled + system.adapter.influxdb.0 : influxdb : iobroker - enabled, port: 8086 + system.adapter.iot.0 : iot : iobroker - enabled + system.adapter.javascript.0 : javascript : iobroker - enabled + system.adapter.mqtt.0 : mqtt : iobroker - enabled, port: 1884, bind: 192.168.111.10 + system.adapter.net-tools.0 : net-tools : iobroker - enabled system.adapter.parser.0 : parser : iobroker - disabled + system.adapter.sayit.0 : sayit : iobroker - enabled + system.adapter.shelly.0 : shelly : iobroker - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.simple-api.0 : simple-api : iobroker - enabled, port: 8087, bind: 0.0.0.0, run as: admin + system.adapter.smartmeter.0 : smartmeter : iob-slave - enabled + system.adapter.sourceanalytix.0 : sourceanalytix : iobroker - enabled + system.adapter.tahoma.0 : tahoma : iob-slave - enabled + system.adapter.tankerkoenig.0 : tankerkoenig : iobroker - enabled + system.adapter.telegram.0 : telegram : iobroker - enabled, port: 8443, bind: 0.0.0.0 system.adapter.trashschedule.0 : trashschedule : iobroker - disabled + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.wled.0 : wled : iobroker - enabled + system.adapter.zigbee.0 : zigbee : iob-slave - enabled, port: /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_0c8a15a4093bec11a27d9c957a0af07f-if00-port0 + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.influxdb.0 : influxdb : iobroker - enabled, port: 8086 + system.adapter.mqtt.0 : mqtt : iobroker - enabled, port: 1884, bind: 192.168.111.10 + system.adapter.shelly.0 : shelly : iobroker - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.simple-api.0 : simple-api : iobroker - enabled, port: 8087, bind: 0.0.0.0, run as: admin + system.adapter.telegram.0 : telegram : iobroker - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.zigbee.0 : zigbee : iob-slave - enabled, port: /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_0c8a15a4093bec11a27d9c957a0af07f-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.16 , installed 6.12.0 [Updatable] Adapter "backitup" : 2.9.8 , installed 2.8.7 [Updatable] Adapter "discovery" : 4.2.0 , installed 4.2.0 Adapter "ds18b20" : 2.0.5 , installed 2.0.5 Controller "js-controller": 5.0.17 , installed 5.0.17 Adapter "smartmeter" : 3.4.0 , installed 3.4.0 Adapter "tahoma" : 0.10.2 , installed 0.10.2 Adapter "zigbee" : 1.10.1 , installed 1.10.1 Objects and States Please stand by - This may take a while Objects: 5082 States: 4442 *** OS-Repositories and Updates *** Hit:1 http://deb.debian.org/debian bullseye InRelease Hit:2 http://deb.debian.org/debian bullseye-updates InRelease Hit:3 http://security.debian.org/debian-security bullseye-security InRelease Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease Hit:5 https://deb.nodesource.com/node_18.x nodistro InRelease Reading package lists... Pending Updates: 18 *** 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:22 0.0.0.0:* LISTEN 0 12725 513/sshd: /usr/sbin tcp6 0 0 :::22 :::* LISTEN 0 12727 513/sshd: /usr/sbin udp 0 0 0.0.0.0:68 0.0.0.0:* 0 14559 599/dhcpcd udp 0 0 0.0.0.0:33446 0.0.0.0:* 108 14468 418/avahi-daemon: r udp 0 0 0.0.0.0:5353 0.0.0.0:* 108 14466 418/avahi-daemon: r udp6 0 0 :::33386 :::* 108 14469 418/avahi-daemon: r udp6 0 0 :::5353 :::* 108 14467 418/avahi-daemon: r *** Log File - Last 25 Lines *** 2024-02-10 19:15:02.772 - info: tahoma.0 (54618) Using stored bearer token 635112b1cca5680435cb 2024-02-10 19:15:08.682 - info: ds18b20.0 (54629) starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.ds18b20, node: v18.19.0, js-controller: 5.0.17 2024-02-10 19:15:09.914 - warn: ds18b20.0 (54629) Error reading sensor 28-0000067cc099: Error: No temperature read 2024-02-10 19:15:11.155 - info: tahoma.0 (54618) eventRegisterID = 199922c5-4c54-4fd2-8a12-54ebed5390a6 2024-02-10 19:15:12.582 - info: zigbee.0 (54607) starting. Version 1.10.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.19.0, js-controller: 5.0.17 2024-02-10 19:15:12.939 - info: zigbee.0 (54607) delete old Backup files. keep only last 10 2024-02-10 19:15:12.967 - info: zigbee.0 (54607) Starting Zigbee npm ... 2024-02-10 19:15:14.263 - info: zigbee.0 (54607) Installed Version: iobroker.zigbee@1.10.1 2024-02-10 19:15:16.996 - warn: zigbee.0 (54607) Extended PAN ID is reversed (expected=28bcc824004b1200, actual=00124b0024c8bc28) 2024-02-10 19:15:19.953 - info: zigbee.0 (54607) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20220219}} 2024-02-10 19:15:19.966 - info: zigbee.0 (54607) Unable to disable LED, unsupported function. 2024-02-10 19:15:20.000 - info: zigbee.0 (54607) --> transmitPower : normal 2024-02-10 19:15:20.033 - info: zigbee.0 (54607) Currently 8 devices are joined: 2024-02-10 19:15:20.244 - info: zigbee.0 (54607) 0x84ba20fffe7aa44c (addr 229): E1812 - IKEA TRADFRI shortcut button (EndDevice) 2024-02-10 19:15:20.259 - info: zigbee.0 (54607) 0x00158d000806884a (addr 22797): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2024-02-10 19:15:20.271 - info: zigbee.0 (54607) 0x00158d0008482cfe (addr 3116): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2024-02-10 19:15:20.280 - info: zigbee.0 (54607) 0x00158d00084831fc (addr 31697): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2024-02-10 19:15:20.300 - info: zigbee.0 (54607) 0x04cd15fffe6a7146 (addr 31352): LED1736G9 - IKEA TRADFRI LED bulb E26/E27 806 lumen, dimmable, white spectrum, clear (Router) 2024-02-10 19:15:20.309 - info: zigbee.0 (54607) 0xb4e3f9fffebe952e (addr 12697): E1603/E1702/E1708 - IKEA TRADFRI control outlet (Router) 2024-02-10 19:15:20.323 - info: zigbee.0 (54607) 0xa4c138eed51355f8 (addr 26613): HG08673 - Lidl Silvercrest smart plug with power monitoring (EU, FR) (Router) 2024-02-10 19:15:20.328 - info: zigbee.0 (54607) 0x003c84fffe18ad0f (addr 2414): E1525/E1745 - IKEA TRADFRI motion sensor (EndDevice) 2024-02-10 19:15:20.331 - info: zigbee.0 (54607) Zigbee started 2024-02-10 19:15:20.545 - info: zigbee.0 (54607) debug devices set to [] 2024-02-10 19:15:46.744 - warn: zigbee.0 (54607) DeviceAvailability:Failed to ping 0xb4e3f9fffebe952e TRADFRI control outlet 2024-02-10 19:21:17.879 - info: zigbee.0 (54607) Device '0x003c84fffe18ad0f' announced itself============ Mark until here for C&P =============
iob diag has finished.
Fällt euch sonst noch irgendwas auf, was bei mir falsch ist?
Jetzt schon mal ein großes DANKE für die Hilfe!
-
@wusa sagte in Slave startet nicht mehr:
Fällt euch sonst noch irgendwas auf, was bei mir falsch ist?
Hau die Updates des Betriebssstem drauf und auch die Adapter auf den letzten Stand bringen.
Und dann ist die Extended PAN-Id im Zigbee-Adapter verdreht.
