NEWS
pnpm Fehler
-
Hallo allerseits.
ich wollte gerade den Umstieg auf Zigbee2Mqtt wagen.
Bei der Installation von
npm install -g pnpmkommt folgende Fehlermeldung:
pi@pi4-Master:~ $ npm install -g pnpm npm error code EACCES npm error syscall rename npm error path /usr/lib/node_modules/pnpm npm error dest /usr/lib/node_modules/.pnpm-H0EZVZtB npm error errno -13 npm error Error: EACCES: permission denied, rename '/usr/lib/node_modules/pnpm' -> '/usr/lib/node_modules/.pnpm-H0EZVZtB' npm error at async Object.rename (node:internal/fs/promises:782:10) npm error at async moveFile (/usr/lib/node_modules/npm/node_modules/@npmcli/fs/lib/move-file.js:30:5) npm error at async Promise.allSettled (index 0) npm error at async [reifyPackages] (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:337:11) npm error at async Arborist.reify (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:142:5) npm error at async Install.exec (/usr/lib/node_modules/npm/lib/commands/install.js:149:5) npm error at async Npm.exec (/usr/lib/node_modules/npm/lib/npm.js:208:9) npm error at async module.exports (/usr/lib/node_modules/npm/lib/cli/entry.js:67:5) { npm error errno: -13, npm error code: 'EACCES', npm error syscall: 'rename', npm error path: '/usr/lib/node_modules/pnpm', npm error dest: '/usr/lib/node_modules/.pnpm-H0EZVZtB' npm error } npm error npm error The operation was rejected by your operating system. npm error It is likely you do not have the permissions to access this file as the current user npm error npm error If you believe this might be a permissions issue, please double-check the npm error permissions of the file and its containing directories, or try running npm error the command again as root/Administrator. npm error A complete log of this run can be found in: /home/pi/.npm/_logs/2025-06-22T11_48_20_659Z-debug-0.logA complete log of this run can be found in: /home/pi/.npm/_logs/2025-06-22T11_48_20_659Z-debug-0.log0 verbose cli /usr/bin/node /usr/bin/npm 1 info using npm@10.9.2 2 info using node@v22.16.0 3 silly config load:file:/usr/lib/node_modules/npm/npmrc 4 silly config load:file:/home/pi/.npmrc 5 silly config load:file:/usr/etc/npmrc 6 verbose title npm install pnpm 7 verbose argv "install" "--global" "pnpm" 8 verbose logfile logs-max:10 dir:/home/pi/.npm/_logs/2025-06-22T12_17_32_738Z- 9 verbose logfile /home/pi/.npm/_logs/2025-06-22T12_17_32_738Z-debug-0.log 10 silly packumentCache heap:2197815296 maxSize:549453824 maxEntrySize:274726912 11 silly logfile start cleaning logs, removing 1 files 12 silly logfile done cleaning log files 13 silly idealTree buildDeps 14 silly fetch manifest pnpm@* 15 silly packumentCache full:https://registry.npmjs.org/pnpm cache-miss 16 http fetch GET 200 https://registry.npmjs.org/pnpm 371ms (cache revalidated) 17 silly packumentCache full:https://registry.npmjs.org/pnpm set size:5092597 disposed:false 18 silly placeDep ROOT pnpm@10.12.1 OK for: want: * 19 silly reify mark retired [ '/usr/lib/node_modules/pnpm', '/usr/bin/pnpm', '/usr/bin/pnpx' ] 20 silly reify moves { 20 silly reify '/usr/lib/node_modules/pnpm': '/usr/lib/node_modules/.pnpm-H0EZVZtB', 20 silly reify '/usr/bin/pnpm': '/usr/bin/.pnpm-JTllyBcj', 20 silly reify '/usr/bin/pnpx': '/usr/bin/.pnpx-MALdymCV' 20 silly reify } 21 verbose stack Error: EACCES: permission denied, rename '/usr/lib/node_modules/pnpm' -> '/usr/lib/node_modules/.pnpm-H0EZVZtB' 21 verbose stack at async Object.rename (node:internal/fs/promises:778:10) 21 verbose stack at async moveFile (/usr/lib/node_modules/npm/node_modules/@npmcli/fs/lib/move-file.js:30:5) 21 verbose stack at async Promise.allSettled (index 0) 21 verbose stack at async [reifyPackages] (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:325:11) 21 verbose stack at async Arborist.reify (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:142:5) 21 verbose stack at async Install.exec (/usr/lib/node_modules/npm/lib/commands/install.js:150:5) 21 verbose stack at async Npm.exec (/usr/lib/node_modules/npm/lib/npm.js:207:9) 21 verbose stack at async module.exports (/usr/lib/node_modules/npm/lib/cli/entry.js:74:5) 22 error code EACCES 23 error syscall rename 24 error path /usr/lib/node_modules/pnpm 25 error dest /usr/lib/node_modules/.pnpm-H0EZVZtB 26 error errno -13 27 error Error: EACCES: permission denied, rename '/usr/lib/node_modules/pnpm' -> '/usr/lib/node_modules/.pnpm-H0EZVZtB' 27 error at async Object.rename (node:internal/fs/promises:778:10) 27 error at async moveFile (/usr/lib/node_modules/npm/node_modules/@npmcli/fs/lib/move-file.js:30:5) 27 error at async Promise.allSettled (index 0) 27 error at async [reifyPackages] (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:325:11) 27 error at async Arborist.reify (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:142:5) 27 error at async Install.exec (/usr/lib/node_modules/npm/lib/commands/install.js:150:5) 27 error at async Npm.exec (/usr/lib/node_modules/npm/lib/npm.js:207:9) 27 error at async module.exports (/usr/lib/node_modules/npm/lib/cli/entry.js:74:5) { 27 error errno: -13, 27 error code: 'EACCES', 27 error syscall: 'rename',Was kann ich tun?
Mfg
Tom
Der user 'pi' darf nicht nach /usr/lib/ schreiben, das darf nur root.
nodemodule, die global verfügbar sein sollen muss also der root dort hinlegen.Wird dir aber auch angesagt:
npm error If you believe this might be a permissions issue, please double-check the
npm error permissions of the file and its containing directories, or try running
npm error the command again as root/Administrator.
Also:
sudo npm install -g pnpm -
Der user 'pi' darf nicht nach /usr/lib/ schreiben, das darf nur root.
nodemodule, die global verfügbar sein sollen muss also der root dort hinlegen.Wird dir aber auch angesagt:
npm error If you believe this might be a permissions issue, please double-check the
npm error permissions of the file and its containing directories, or try running
npm error the command again as root/Administrator.
Also:
sudo npm install -g pnpm@thomas-braun Danke, wieder was gelernt...
-
Und schon kommt das nächste Problem.
Zigbee2Mqtt will ums verrecken nicht starten.
pi@pi4-Master:/opt/zigbee2mqtt $ pnpm start > zigbee2mqtt@2.4.0 start /opt/zigbee2mqtt > node index.js Starting Zigbee2MQTT without watchdog. [2025-06-23 16:21:03] info: z2m: Logging to console, file (filename: log.log) [2025-06-23 16:21:04] info: z2m: Starting Zigbee2MQTT version 2.4.0 (commit #bdb94da4) [2025-06-23 16:21:04] info: z2m: Starting zigbee-herdsman (4.1.0) [2025-06-23 16:21:04] info: zh:adapter:discovery: Matched adapter: {"path":"/dev/ttyUSB0","manufacturer":"Itead","serialNumber":"ac315ae1c912ef1184ed6fb8bf9df066","pnpId":"usb-Itead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_V2_ac315ae1c912ef1184ed6fb8bf9df066-if00-port0","vendorId":"10c4","productId":"ea60"} => ember: 4 [2025-06-23 16:21:04] info: zh:ember: Using default stack config. [2025-06-23 16:21:04] info: zh:ember: ======== Ember Adapter Starting ======== [2025-06-23 16:21:04] info: zh:ember:ezsp: ======== EZSP starting ======== [2025-06-23 16:21:04] info: zh:ember:uart:ash: ======== ASH Adapter reset ======== [2025-06-23 16:21:04] info: zh:ember:uart:ash: RTS/CTS config is off, enabling software flow control. [2025-06-23 16:21:04] info: zh:ember:uart:ash: ASH COUNTERS since last clear: [2025-06-23 16:21:04] info: zh:ember:uart:ash: Total frames: RX=0, TX=0 [2025-06-23 16:21:04] info: zh:ember:uart:ash: Cancelled : RX=0, TX=0 [2025-06-23 16:21:04] info: zh:ember:uart:ash: DATA frames : RX=0, TX=0 [2025-06-23 16:21:04] info: zh:ember:uart:ash: DATA bytes : RX=0, TX=0 [2025-06-23 16:21:04] info: zh:ember:uart:ash: Retry frames: RX=0, TX=0 [2025-06-23 16:21:04] info: zh:ember:uart:ash: ACK frames : RX=0, TX=0 [2025-06-23 16:21:04] info: zh:ember:uart:ash: NAK frames : RX=0, TX=0 [2025-06-23 16:21:04] info: zh:ember:uart:ash: nRdy frames : RX=0, TX=0 [2025-06-23 16:21:04] info: zh:ember:uart:ash: CRC errors : RX=0 [2025-06-23 16:21:04] info: zh:ember:uart:ash: Comm errors : RX=0 [2025-06-23 16:21:04] info: zh:ember:uart:ash: Length < minimum: RX=0 [2025-06-23 16:21:04] info: zh:ember:uart:ash: Length > maximum: RX=0 [2025-06-23 16:21:04] info: zh:ember:uart:ash: Bad controls : RX=0 [2025-06-23 16:21:04] info: zh:ember:uart:ash: Bad lengths : RX=0 [2025-06-23 16:21:04] info: zh:ember:uart:ash: Bad ACK numbers : RX=0 [2025-06-23 16:21:04] info: zh:ember:uart:ash: Out of buffers : RX=0 [2025-06-23 16:21:04] info: zh:ember:uart:ash: Retry dupes : RX=0 [2025-06-23 16:21:04] info: zh:ember:uart:ash: Out of sequence : RX=0 [2025-06-23 16:21:04] info: zh:ember:uart:ash: ACK timeouts : RX=0 [2025-06-23 16:21:04] info: zh:ember:uart:ash: ======== ASH stopped ======== [2025-06-23 16:21:04] error: zh:ember:uart:ash: Failed to init port with error Error: Error Resource temporarily unavailable Cannot lock port [2025-06-23 16:21:04] error: z2m: Error while starting zigbee-herdsman [2025-06-23 16:21:04] error: z2m: Failed to start zigbee-herdsman [2025-06-23 16:21:04] error: z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions [2025-06-23 16:21:04] error: z2m: Exiting... [2025-06-23 16:21:04] error: z2m: Error: Failed to start EZSP layer with status=HOST_FATAL_ERROR. at EmberAdapter.initEzsp (/opt/zigbee2mqtt/node_modules/.pnpm/zigbee-herdsman@4.1.0/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:666:19) at EmberAdapter.start (/opt/zigbee2mqtt/node_modules/.pnpm/zigbee-herdsman@4.1.0/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:1548:24) at Controller.start (/opt/zigbee2mqtt/node_modules/.pnpm/zigbee-herdsman@4.1.0/node_modules/zigbee-herdsman/src/controller/controller.ts:133:29) at Zigbee.start (/opt/zigbee2mqtt/lib/zigbee.ts:71:27) at Controller.start (/opt/zigbee2mqtt/lib/controller.ts:102:13) at start (/opt/zigbee2mqtt/index.js:149:5) ELIFECYCLE Command failed with exit code 1.Hier die Config
version: 4 mqtt: base_topic: zigbee2mqtt server: mqtt://localhost:1883 user: xxxxxxxx password: xxxxxxxx serial: port: /dev/ttyUSB0 adapter: ember baudrate: 115200 rtscts: false advanced: log_level: info channel: 11 network_key: - 223 - 25 - 181 - 70 - 48 - 140 - 164 - 218 - 20 - 78 - 112 - 96 - 167 - 137 - 205 - 12 pan_id: 53749 ext_pan_id: - 230 - 19 - 60 - 177 - 44 - 17 - 21 - 12 frontend: enabled: true port: 8080 homeassistant: enabled: falseMuss ich evtl die Porteinstellung ändern?
-
Und schon kommt das nächste Problem.
Zigbee2Mqtt will ums verrecken nicht starten.
pi@pi4-Master:/opt/zigbee2mqtt $ pnpm start > zigbee2mqtt@2.4.0 start /opt/zigbee2mqtt > node index.js Starting Zigbee2MQTT without watchdog. [2025-06-23 16:21:03] info: z2m: Logging to console, file (filename: log.log) [2025-06-23 16:21:04] info: z2m: Starting Zigbee2MQTT version 2.4.0 (commit #bdb94da4) [2025-06-23 16:21:04] info: z2m: Starting zigbee-herdsman (4.1.0) [2025-06-23 16:21:04] info: zh:adapter:discovery: Matched adapter: {"path":"/dev/ttyUSB0","manufacturer":"Itead","serialNumber":"ac315ae1c912ef1184ed6fb8bf9df066","pnpId":"usb-Itead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_V2_ac315ae1c912ef1184ed6fb8bf9df066-if00-port0","vendorId":"10c4","productId":"ea60"} => ember: 4 [2025-06-23 16:21:04] info: zh:ember: Using default stack config. [2025-06-23 16:21:04] info: zh:ember: ======== Ember Adapter Starting ======== [2025-06-23 16:21:04] info: zh:ember:ezsp: ======== EZSP starting ======== [2025-06-23 16:21:04] info: zh:ember:uart:ash: ======== ASH Adapter reset ======== [2025-06-23 16:21:04] info: zh:ember:uart:ash: RTS/CTS config is off, enabling software flow control. [2025-06-23 16:21:04] info: zh:ember:uart:ash: ASH COUNTERS since last clear: [2025-06-23 16:21:04] info: zh:ember:uart:ash: Total frames: RX=0, TX=0 [2025-06-23 16:21:04] info: zh:ember:uart:ash: Cancelled : RX=0, TX=0 [2025-06-23 16:21:04] info: zh:ember:uart:ash: DATA frames : RX=0, TX=0 [2025-06-23 16:21:04] info: zh:ember:uart:ash: DATA bytes : RX=0, TX=0 [2025-06-23 16:21:04] info: zh:ember:uart:ash: Retry frames: RX=0, TX=0 [2025-06-23 16:21:04] info: zh:ember:uart:ash: ACK frames : RX=0, TX=0 [2025-06-23 16:21:04] info: zh:ember:uart:ash: NAK frames : RX=0, TX=0 [2025-06-23 16:21:04] info: zh:ember:uart:ash: nRdy frames : RX=0, TX=0 [2025-06-23 16:21:04] info: zh:ember:uart:ash: CRC errors : RX=0 [2025-06-23 16:21:04] info: zh:ember:uart:ash: Comm errors : RX=0 [2025-06-23 16:21:04] info: zh:ember:uart:ash: Length < minimum: RX=0 [2025-06-23 16:21:04] info: zh:ember:uart:ash: Length > maximum: RX=0 [2025-06-23 16:21:04] info: zh:ember:uart:ash: Bad controls : RX=0 [2025-06-23 16:21:04] info: zh:ember:uart:ash: Bad lengths : RX=0 [2025-06-23 16:21:04] info: zh:ember:uart:ash: Bad ACK numbers : RX=0 [2025-06-23 16:21:04] info: zh:ember:uart:ash: Out of buffers : RX=0 [2025-06-23 16:21:04] info: zh:ember:uart:ash: Retry dupes : RX=0 [2025-06-23 16:21:04] info: zh:ember:uart:ash: Out of sequence : RX=0 [2025-06-23 16:21:04] info: zh:ember:uart:ash: ACK timeouts : RX=0 [2025-06-23 16:21:04] info: zh:ember:uart:ash: ======== ASH stopped ======== [2025-06-23 16:21:04] error: zh:ember:uart:ash: Failed to init port with error Error: Error Resource temporarily unavailable Cannot lock port [2025-06-23 16:21:04] error: z2m: Error while starting zigbee-herdsman [2025-06-23 16:21:04] error: z2m: Failed to start zigbee-herdsman [2025-06-23 16:21:04] error: z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions [2025-06-23 16:21:04] error: z2m: Exiting... [2025-06-23 16:21:04] error: z2m: Error: Failed to start EZSP layer with status=HOST_FATAL_ERROR. at EmberAdapter.initEzsp (/opt/zigbee2mqtt/node_modules/.pnpm/zigbee-herdsman@4.1.0/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:666:19) at EmberAdapter.start (/opt/zigbee2mqtt/node_modules/.pnpm/zigbee-herdsman@4.1.0/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:1548:24) at Controller.start (/opt/zigbee2mqtt/node_modules/.pnpm/zigbee-herdsman@4.1.0/node_modules/zigbee-herdsman/src/controller/controller.ts:133:29) at Zigbee.start (/opt/zigbee2mqtt/lib/zigbee.ts:71:27) at Controller.start (/opt/zigbee2mqtt/lib/controller.ts:102:13) at start (/opt/zigbee2mqtt/index.js:149:5) ELIFECYCLE Command failed with exit code 1.Hier die Config
version: 4 mqtt: base_topic: zigbee2mqtt server: mqtt://localhost:1883 user: xxxxxxxx password: xxxxxxxx serial: port: /dev/ttyUSB0 adapter: ember baudrate: 115200 rtscts: false advanced: log_level: info channel: 11 network_key: - 223 - 25 - 181 - 70 - 48 - 140 - 164 - 218 - 20 - 78 - 112 - 96 - 167 - 137 - 205 - 12 pan_id: 53749 ext_pan_id: - 230 - 19 - 60 - 177 - 44 - 17 - 21 - 12 frontend: enabled: true port: 8080 homeassistant: enabled: falseMuss ich evtl die Porteinstellung ändern?
Bist du sicher, dass die Choose so installiert werden soll?
-
Bist du sicher, dass die Choose so installiert werden soll?
@thomas-braun Asolut nicht.
Ich humpel hald jetz mal ein wenig hin und her.
Ich brauche das Zigbee2Mqtt weil ich einen Feuchtesensor einbinden muss.
Ich hab mich vor einiger zeit schon mal eingelesen, bin aber dann doch beim alten zigbee geblieben.Ich hab mich an die Anleitungen gehalten, die ich gefunden hab. Moquitto läuft schon mal.
-
@thomas-braun Asolut nicht.
Ich humpel hald jetz mal ein wenig hin und her.
Ich brauche das Zigbee2Mqtt weil ich einen Feuchtesensor einbinden muss.
Ich hab mich vor einiger zeit schon mal eingelesen, bin aber dann doch beim alten zigbee geblieben.Ich hab mich an die Anleitungen gehalten, die ich gefunden hab. Moquitto läuft schon mal.
@autodidakt sagte in pnpm Fehler:
Ich brauche das Zigbee2Mqtt weil ich einen Feuchtesensor einbinden muss.
Ich hab mich vor einiger zeit schon mal eingelesen, bin aber dann doch beim alten zigbee gebliebenim zigbee Adapter werkelt auch due zigbee²mqtt Engine!
Wwofü genau benötigst du Z2m?
was geht nicht mit dem Zigbee Adapter?kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.
Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -
-
@autodidakt sagte in pnpm Fehler:
Ich brauche das Zigbee2Mqtt weil ich einen Feuchtesensor einbinden muss.
Ich hab mich vor einiger zeit schon mal eingelesen, bin aber dann doch beim alten zigbee gebliebenim zigbee Adapter werkelt auch due zigbee²mqtt Engine!
Wwofü genau benötigst du Z2m?
was geht nicht mit dem Zigbee Adapter? -
-
Ich hab das wohl falsch verstanden. Ich dacht dafür brauch ich Z2M...
Dummer weise habe ich meinem Sonoff Zigbee 3.0 heute eine neue Firmware verpasst, nun läuft auch der Zigbee Adapter nicht mehr.:face_with_rolling_eyes: -
Ich hab das wohl falsch verstanden. Ich dacht dafür brauch ich Z2M...
Dummer weise habe ich meinem Sonoff Zigbee 3.0 heute eine neue Firmware verpasst, nun läuft auch der Zigbee Adapter nicht mehr.:face_with_rolling_eyes:@autodidakt womit wolltest du den z2m betreiben?
welchen Koordinator hast du denn noch?kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.
Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -
-
@autodidakt womit wolltest du den z2m betreiben?
welchen Koordinator hast du denn noch? -
@homoran Der Sonoff war mein Koordinator, oder täusch ich mich?
Mit dem wollte ich Z2M betreiben.@autodidakt ....und jetzt hast du gar nichts mehr 😞 ?
Dann musdt du den sonoff wiederbeleben oder was anderes kaufen.kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.
Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -
-
@autodidakt ....und jetzt hast du gar nichts mehr 😞 ?
Dann musdt du den sonoff wiederbeleben oder was anderes kaufen.@homoran Ich versuch Ihn grade neu zu flashen. Ist aber nicht ganz einfach in dem ganzen Firmware-Gewirr.
Wenn das nichts wird, muss hald ein neuer her.
-
Hallo nochmal.
Ich habe jetzt einen neuen Stick (Zigbee 3.0 USB Dongle Plus) den Zigbee Adapter V3.0.1 neu installiert und versuche nun meine Geräte neu anzulernen.
Leider kommt immer ein Herdsman Fehler.
zigbee.0 2025-06-25 11:06:24.603 warn ELEVATED:I02 (a0ca) value generated '171' from device ffffb40e060599a0 for 'Link quality' zigbee.0 2025-06-25 11:06:24.602 warn ELEVATED:I02 (a0ca) value generated '171' from device ffffb40e060599a0 for 'Link quality' zigbee.0 2025-06-25 11:06:24.601 warn ELEVATED:I01 (a0ca) message received '{"linkquality":171}' from device ffffb40e060599a0 type 'undefined' zigbee.0 2025-06-25 11:06:24.598 warn ELEVATED:I02 (a0c2) value generated '168' from device ffffb40e060599a0 for 'Link quality' zigbee.0 2025-06-25 11:06:24.597 warn ELEVATED:I02 (a0c2) value generated '168' from device ffffb40e060599a0 for 'Link quality' zigbee.0 2025-06-25 11:06:24.596 warn ELEVATED:I01 (a0c2) message received '{"linkquality":168}' from device ffffb40e060599a0 type 'undefined' zigbee.0 2025-06-25 11:06:24.592 warn ELEVATED:I02 (a0c0) value generated '168' from device ffffb40e060599a0 for 'Link quality' zigbee.0 2025-06-25 11:06:24.592 warn ELEVATED:I02 (a0c0) value generated '168' from device ffffb40e060599a0 for 'Link quality' zigbee.0 2025-06-25 11:06:24.592 warn ELEVATED:I01 (a0c0) message received '{"linkquality":168}' from device ffffb40e060599a0 type 'undefined' zigbee.0 2025-06-25 11:06:24.591 warn ELEVATED:I02 (a0b3) value generated '168' from device ffffb40e060599a0 for 'Link quality' zigbee.0 2025-06-25 11:06:24.590 warn ELEVATED:I02 (a0b3) value generated '168' from device ffffb40e060599a0 for 'Link quality' zigbee.0 2025-06-25 11:06:24.589 warn ELEVATED:I01 (a0b3) message received '{"linkquality":168}' from device ffffb40e060599a0 type 'undefined' zigbee.0 2025-06-25 11:06:24.587 warn ELEVATED:I01 (a0ca) Zigbee Event of Type attributeReport from device 0xffffb40e060599a0, incoming event: {"type":"attributeReport","data":{"batteryPercentageRemaining":200},"linkquality":171,"groupID":0,"cluster":"genPowerCfg","meta":{"zclTransactionSequenceNumber":97,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1} zigbee.0 2025-06-25 11:06:24.578 warn ELEVATED:I01 (a0c2) Zigbee Event of Type attributeReport from device 0xffffb40e060599a0, incoming event: {"type":"attributeReport","data":{"batteryVoltage":15},"linkquality":168,"groupID":0,"cluster":"genPowerCfg","meta":{"zclTransactionSequenceNumber":96,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1} zigbee.0 2025-06-25 11:06:24.576 warn ELEVATED:I01 (a0c0) Zigbee Event of Type attributeReport from device 0xffffb40e060599a0, incoming event: {"type":"attributeReport","data":{"measuredValue":0},"linkquality":168,"groupID":0,"cluster":"msRelativeHumidity","meta":{"zclTransactionSequenceNumber":95,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1} zigbee.0 2025-06-25 11:06:24.565 warn ELEVATED:I01 (a0b3) Zigbee Event of Type attributeReport from device 0xffffb40e060599a0, incoming event: {"type":"attributeReport","data":{"measuredValue":2869},"linkquality":168,"groupID":0,"cluster":"msTemperatureMeasurement","meta":{"zclTransactionSequenceNumber":94,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1} zigbee.0 2025-06-25 11:06:09.592 warn ELEVATED:I02 (661d) value generated '174' from device ffffb40e060599a0 for 'Link quality' zigbee.0 2025-06-25 11:06:09.592 warn ELEVATED:I02 (661d) value generated '174' from device ffffb40e060599a0 for 'Link quality' zigbee.0 2025-06-25 11:06:09.591 warn ELEVATED:I01 (661d) message received '{"linkquality":174}' from device ffffb40e060599a0 type 'undefined' zigbee.0 2025-06-25 11:06:09.578 warn ELEVATED:I02 (6611) value generated '171' from device ffffb40e060599a0 for 'Link quality' zigbee.0 2025-06-25 11:06:09.576 warn ELEVATED:I02 (6611) value generated '171' from device ffffb40e060599a0 for 'Link quality' zigbee.0 2025-06-25 11:06:09.575 warn ELEVATED:I01 (6611) message received '{"linkquality":171}' from device ffffb40e060599a0 type 'undefined' zigbee.0 2025-06-25 11:06:09.574 warn ELEVATED:I02 (660e) value generated '171' from device ffffb40e060599a0 for 'Link quality' zigbee.0 2025-06-25 11:06:09.573 warn ELEVATED:I02 (660e) value generated '171' from device ffffb40e060599a0 for 'Link quality' zigbee.0 2025-06-25 11:06:09.573 warn ELEVATED:I01 (660e) message received '{"linkquality":171}' from device ffffb40e060599a0 type 'undefined' zigbee.0 2025-06-25 11:06:09.566 warn ELEVATED:I01 (661d) Zigbee Event of Type attributeReport from device 0xffffb40e060599a0, incoming event: {"type":"attributeReport","data":{"batteryPercentageRemaining":200},"linkquality":174,"groupID":0,"cluster":"genPowerCfg","meta":{"zclTransactionSequenceNumber":93,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1} zigbee.0 2025-06-25 11:06:09.553 warn ELEVATED:I01 (6611) Zigbee Event of Type attributeReport from device 0xffffb40e060599a0, incoming event: {"type":"attributeReport","data":{"batteryVoltage":15},"linkquality":171,"groupID":0,"cluster":"genPowerCfg","meta":{"zclTransactionSequenceNumber":92,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1} zigbee.0 2025-06-25 11:06:09.551 warn ELEVATED:I01 (660e) Zigbee Event of Type attributeReport from device 0xffffb40e060599a0, incoming event: {"type":"attributeReport","data":{"measuredValue":0},"linkquality":171,"groupID":0,"cluster":"msRelativeHumidity","meta":{"zclTransactionSequenceNumber":91,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1} zigbee.0 2025-06-25 11:06:09.393 warn ELEVATED:I02 (6568) value generated '174' from device ffffb40e060599a0 for 'Link quality' zigbee.0 2025-06-25 11:06:09.392 warn ELEVATED:I02 (6568) value generated '174' from device ffffb40e060599a0 for 'Link quality' zigbee.0 2025-06-25 11:06:09.391 warn ELEVATED:I01 (6568) message received '{"linkquality":174}' from device ffffb40e060599a0 type 'undefined' zigbee.0 2025-06-25 11:06:09.385 warn ELEVATED:I01 (6568) Zigbee Event of Type attributeReport from device 0xffffb40e060599a0, incoming event: {"type":"attributeReport","data":{"measuredValue":2869},"linkquality":174,"groupID":0,"cluster":"msTemperatureMeasurement","meta":{"zclTransactionSequenceNumber":88,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}Irgendwo steckt wohl noch was fest. Gibt es eine Möglichkeit Zigbee komplett mit allem zu entfernen und neu zu beginnen?
Failed to open the network: Error: SRSP - ZDO - mgmtPermitJoinReq after 6000ms at Object.start (/opt/iobroker/node_modules/zigbee-herdsman/dist/utils/waitress.js:47:23) at /opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:263:41 at Queue.execute (/opt/iobroker/node_modules/zigbee-herdsman/dist/utils/queue.js:29:26) at Znp.requestZdo (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:257:27) at func (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:322:32) at Queue.execute (/opt/iobroker/node_modules/zigbee-herdsman/dist/utils/queue.js:29:26) at ZStackAdapter.sendZdoInternal (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:341:60) at ZStackAdapter.sendZdo (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:263:27) at ZStackAdapter.permitJoin (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:176:24) at Controller.permitJoin (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:249:32)Mfg
Tom
Support us
566
Online32.6k
Benutzer82.2k
Themen1.3m
Beiträge