UNSOLVED Probleme mit Zigbee / Generator.next / ZStackAdapter / 2252
-
@Asgothian
Es scheint geholfen zu haben, den Stick in einen anderen USB Port zu stecken! Gibt es eine Erklärung dafür? Vorher war er zusammen (je Port ein Gerät) mit meiner externen Festplatte in einem der USB 3 Porst, nun alleine in einem der zwei USB 2 Ports. -
@Jona Fein,
-
Leider muss ich den Thread wiederbeleben. Die Probleme sind weiterhin vorhanden. Zwar ist der Neustart jetzt kein Problem mehr, weil ich jetzt einen USB2 anstatt USB3 Port nutze, aber nachdem mal etwas läuft, kann man sich schon bald wieder auf diese Fehler einstellen.
2020-09-28 11:06:27.718 - error: zigbee.0 (1740) Error on send command to 0x00158d0002e34b33. Error: Error: Command 0x00158d0002e34b33/2 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (SREQ '--> AF - dataRequest - {"dstaddr":13765,"destendpoint":2,"srcendpoint":1,"clusterid":6,"transid":49,"options":0,"radius":30,"len":3,"data":{"type":"Buffer","data":[1,24,0]}}' failed with status '(0x02: INVALID_PARAM)' (expected '(0x00: SUCCESS)')) at Znp. (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:291:27) at Generator.next () at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:24:58) 2020-09-28 11:06:30.480 - error: zigbee.0 (1740) Error on send command to 0x00158d0002e34b33. Error: Error: Command 0x00158d0002e34b33/2 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (SREQ '--> AF - dataRequest - {"dstaddr":13765,"destendpoint":2,"srcendpoint":1,"clusterid":6,"transid":50,"options":0,"radius":30,"len":3,"data":{"type":"Buffer","data":[1,25,1]}}' failed with status '(0x02: INVALID_PARAM)' (expected '(0x00: SUCCESS)')) at Znp. (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:291:27) at Generator.next () at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:24:58) 2020-09-28 11:06:49.663 - error: zigbee.0 (1740) Error on send command to 0x00158d0002f8d5b4. Error: Error: Command 0x00158d0002f8d5b4/2 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (SREQ '--> AF - dataRequest - {"dstaddr":5944,"destendpoint":2,"srcendpoint":1,"clusterid":6,"transid":51,"options":0,"radius":30,"len":3,"data":{"type":"Buffer","data":[1,26,0]}}' failed with status '(0x02: INVALID_PARAM)' (expected '(0x00: SUCCESS)')) at Znp. (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:291:27) at Generator.next () at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:24:58) 2020-09-28 11:06:59.248 - error: zigbee.0 (1740) Error on send command to 0x00158d0002f8d76c. Error: Error: Command 0x00158d0002f8d76c/2 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (SREQ '--> AF - dataRequest - {"dstaddr":28411,"destendpoint":2,"srcendpoint":1,"clusterid":6,"transid":53,"options":0,"radius":30,"len":3,"data":{"type":"Buffer","data":[1,28,1]}}' failed with status '(0x02: INVALID_PARAM)' (expected '(0x00: SUCCESS)')) at Znp. (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:291:27) at Generator.next () at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:24:58)Es ist wirklich wahnsinnig ärgerlich, da so nichts zuverlässig funktioniert. Meistens passiert nach einem Befehl nichts, manchmal wird der Befehl doch überraschend nach fünf bis zehn Sekunden ausgeführt. Ich habe viel in diesem Forum nach solchen Fehlern gesucht, aber nie einen Thread mit Lösung gefunden. Wenn ich etwas bei diesen tausenden Möglichkeiten übersehen haben sollte, gerne einfach einen Link zum Beitrag setzen. Ohne Hilfe komme ich hier aber nicht weiter.
-
which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nodejs -
/usr/bin/nodejs v10.21.0 /usr/local/bin/node v12.13.0 /usr/local/bin/npm 6.14.2 nodejs: Installed: 10.21.0~dfsg-1~deb10u1+rpi1 Candidate: 10.21.0~dfsg-1~deb10u1+rpi1 Version table: *** 10.21.0~dfsg-1~deb10u1+rpi1 500 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages 100 /var/lib/dpkg/status -
@Jona
Node ist falsch installiert.
Korrigier es:https://forum.iobroker.net/topic/35090/howto-nodejs-installation-und-upgrades-unter-debian/3
-
@Thomas-Braun Hab ich nun gemacht, bekomme über meine Quelle aber nur v10.
/usr/bin/nodejs v10.21.0 /usr/bin/node v10.21.0 /usr/bin/npm 5.8.0 nodejs: Installed: 10.21.0~dfsg-1~deb10u1+rpi1 Candidate: 10.21.0~dfsg-1~deb10u1+rpi1 Version table: *** 10.21.0~dfsg-1~deb10u1+rpi1 500 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages 100 /var/lib/dpkg/status -
@Jona
Dann leg die Quellen richtig an. Steht auch in der Anleitung. Im ersten Eintrag. -
@Jona sagte in Probleme mit Zigbee / Generator.next / ZStackAdapter / 2252:
Ohne Hilfe komme ich hier aber nicht weiter.
Ich muss leider ein paar Fragen stellen bevor ich da richtig aktiv werden kann:
- Was fuer einen Koordinator (zigbee-Stick) setzt du ein - immer noch den cc2531 ?
- Wie viele Zigbee Geräte hat Dein Netz ?
- Welche Geräte sind betroffen ? Aus dem Log kann ich nur erkennen das es sich anscheinend um Geräte eines Herstellers handelt, nicht aber welche
- Reagieren die Geräte, sprich ist nur die Antwort nicht wie erwartet, oder reagieren die Geräte nicht (Das Log zeigt eindeutig Schaltversuche - da wird etwas an oder abgeschaltet)
- Sollte es sich bei den Geräten um Osram Steckdosen handeln bräuchte ich auch deren Firmware Version. Ich hatte mit meinen mit einer alten Firmware Probleme.
A.
-
@Thomas-Braun Nun ist das zwar so, wie Du es in deinem Blog-Post beschrieben hast, jetzt sind aber mein Zigbee und BLE Adapter dauerhaft auf rot.
/usr/bin/nodejs v12.18.4 /usr/bin/node v12.18.4 /usr/bin/npm 6.14.6 nodejs: Installed: 12.18.4-1nodesource1 Candidate: 12.18.4-1nodesource1 Version table: *** 12.18.4-1nodesource1 500 500 https://deb.nodesource.com/node_12.x buster/main armhf Packages 100 /var/lib/dpkg/status 10.21.0~dfsg-1~deb10u1+rpi1 500 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages2020-09-28 12:46:37.967 - info: host.raspberrypi Restart adapter system.adapter.zigbee.0 because enabled 2020-09-28 12:47:07.996 - info: host.raspberrypi instance system.adapter.zigbee.0 started with pid 4776 2020-09-28 12:47:08.554 - error: host.raspberrypi Caught by controller[0]: /opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/node_modules/bindings/bindings.js:121 2020-09-28 12:47:08.554 - error: host.raspberrypi Caught by controller[0]: throw e; 2020-09-28 12:47:08.554 - error: host.raspberrypi Caught by controller[0]: ^ 2020-09-28 12:47:08.554 - error: host.raspberrypi Caught by controller[0]: Error: libnode.so.64: cannot open shared object file: No such file or directory 2020-09-28 12:47:08.555 - error: host.raspberrypi Caught by controller[0]: at Object.Module._extensions..node (internal/modules/cjs/loader.js:1187:18) 2020-09-28 12:47:08.555 - error: host.raspberrypi Caught by controller[0]: at Module.load (internal/modules/cjs/loader.js:985:32) 2020-09-28 12:47:08.555 - error: host.raspberrypi Caught by controller[0]: at Function.Module._load (internal/modules/cjs/loader.js:878:14) 2020-09-28 12:47:08.555 - error: host.raspberrypi Caught by controller[0]: at Module.require (internal/modules/cjs/loader.js:1025:19) 2020-09-28 12:47:08.555 - error: host.raspberrypi Caught by controller[0]: at require (internal/modules/cjs/helpers.js:72:18) 2020-09-28 12:47:08.555 - error: host.raspberrypi Caught by controller[0]: at bindings (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/node_modules/bindings/bindings.js:112:48) 2020-09-28 12:47:08.556 - error: host.raspberrypi Caught by controller[0]: at Object. (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/lib/linux.js:2:36) 2020-09-28 12:47:08.556 - error: host.raspberrypi Caught by controller[0]: at Module._compile (internal/modules/cjs/loader.js:1137:30) 2020-09-28 12:47:08.556 - error: host.raspberrypi Caught by controller[0]: at Object.Module._extensions..js (internal/modules/cjs/loader.js:1157:10) 2020-09-28 12:47:08.556 - error: host.raspberrypi Caught by controller[0]: at Module.load (internal/modules/cjs/loader.js:985:32) 2020-09-28 12:47:08.556 - error: host.raspberrypi instance system.adapter.zigbee.0 terminated with code 1 (JS_CONTROLLER_STOPPED) -
iobroker stop iobroker fix iobroker start -
@Thomas-Braun Schon gemacht, keine Besserung.
-
-
Genau, ich nutze weiterhin den cc2531.
-
Ich nutze derzeit 24 Geräte über Zigbee. Auch OSRAM Steckdosen sind betroffen!
-
Wenn etwas nicht geht, sind alle betroffen (Lichtschalter, Lampen, Steckdosen, etc.)
-
Die Geräte reagieren nicht. Ich kann nachvollziehen, dass der Befehl im Objekt geändert wird.
-
Dazu (OSRAM Firmware) höre ich gerne deine Erfahrung!
-
-
Error: libnode.so.64: cannot open shared object file: No such file or directoryDas ist eine 64bit-Library. Da ist bei dir noch irgendwas anderes krumm. Denn Raspbian OS ist eigentlich 32bit.
sudo apt remove node-*apt policy libnode64 -
@Thomas-Braun Hierdurch ist leider mein gesamtes Smarthome lahm gelegt, weil Bluetooth Low Energy und Zigbee meine einzigen beiden Bindestellen nach außen sind. Hast Du eine Idee, wie ich das reparieren kann?
-
@Jona
Da scheint mir noch unnötiger Kram drauf zu sein.sudo apt remove node-* sudo apt remove libnode* -
@Thomas-Braun Komischer Weise sucht er beim ersten noch nach Version 10.
~ $ sudo apt remove node-* Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package node-v10.16.0-linux-armv7l E: Couldn't find any package by glob 'node-v10.16.0-linux-armv7l' E: Couldn't find any package by regex 'node-v10.16.0-linux-armv7l' ~ $ sudo apt remove libnode* Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'libnodeletlib-dev' for glob 'libnode*' Note, selecting 'libnodeletlib1d' for glob 'libnode*' Note, selecting 'libnodelet-topic-tools-dev' for glob 'libnode*' Note, selecting 'libnodeletlib-tools' for glob 'libnode*' Note, selecting 'libnode64-dev' for glob 'libnode*' Note, selecting 'libnode-dev' for glob 'libnode*' Note, selecting 'libnode64' for glob 'libnode*' Note, selecting 'libnodelet-dev' for glob 'libnode*' Package 'libnode64-dev' is not installed, so not removed Package 'libnode-dev' is not installed, so not removed Package 'libnode64' is not installed, so not removed Package 'libnodelet-dev' is not installed, so not removed Package 'libnodelet-topic-tools-dev' is not installed, so not removed Package 'libnodeletlib-dev' is not installed, so not removed Package 'libnodeletlib-tools' is not installed, so not removed Package 'libnodeletlib1d' is not installed, so not removed The following packages were automatically installed and are no longer required: gyp libc-ares2 libgfortran3 libgmime-2.6-0 libjs-inherits libjs-is-typedarray libllvm8 libmicrodns0 libncurses5 libuv1 libuv1-dev libva-wayland2 node-abbrev node-ajv node-ansi node-ansi-align node-ansi-regex node-ansi-styles node-ansistyles node-aproba node-archy node-are-we-there-yet node-asn1 node-assert-plus node-asynckit node-aws-sign2 node-aws4 node-balanced-match node-bcrypt-pbkdf node-bluebird node-boxen node-brace-expansion node-builtin-modules node-builtins node-cacache node-call-limit node-camelcase node-caseless node-chalk node-chownr node-cli-boxes node-cliui node-clone node-co node-color-convert node-color-name node-combined-stream node-concat-map node-concat-stream node-config-chain node-console-control-strings node-copy-concurrently node-core-util-is node-cross-spawn node-cyclist node-dashdash node-decamelize node-decompress-response node-deep-extend node-defaults node-delayed-stream node-delegates node-detect-indent node-detect-newline node-duplexer3 node-duplexify node-ecc-jsbn node-editor node-encoding node-end-of-stream node-errno node-escape-string-regexp node-execa node-extend node-extsprintf node-find-up node-flush-write-stream node-forever-agent node-form-data node-from2 node-fs-vacuum node-fs-write-stream-atomic node-fs.realpath node-gauge node-get-caller-file node-get-stream node-getpass node-glob node-got node-graceful-fs node-har-schema node-har-validator node-has-flag node-has-symbol-support-x node-has-to-string-tag-x node-has-unicode node-hosted-git-info node-http-signature node-iconv-lite node-iferr node-import-lazy node-imurmurhash node-inflight node-inherits node-ini node-invert-kv node-is-builtin-module node-is-npm node-is-object node-is-plain-obj node-is-retry-allowed node-is-stream node-is-typedarray node-isarray node-isexe node-isstream node-isurl node-jsbn node-json-parse-better-errors node-json-schema node-json-stable-stringify node-json-stringify-safe node-jsonify node-jsonparse node-jsonstream node-jsprim node-latest-version node-lazy-property node-lcid node-libnpx node-locate-path node-lockfile node-lowercase-keys node-lru-cache node-mem node-mime-types node-mimic-fn node-mimic-response node-minimatch node-minimist node-mississippi node-mkdirp node-move-concurrently node-mute-stream node-node-uuid node-nopt node-normalize-package-data node-npm-package-arg node-npm-run-path node-npmlog node-oauth-sign node-object-assign node-once node-opener node-os-locale node-osenv node-p-cancelable node-p-finally node-p-limit node-p-locate node-p-timeout node-package-json node-parallel-transform node-path-exists node-path-is-absolute node-path-is-inside node-performance-now node-prepend-http node-process-nextick-args node-promise-inflight node-promzard node-proto-list node-prr node-pump node-pumpify node-punycode node-qs node-qw node-rc node-read node-read-package-json node-readable-stream node-registry-auth-token node-registry-url node-request node-require-directory node-require-main-filename node-resolve-from node-retry node-rimraf node-run-queue node-safe-buffer node-semver node-semver-diff node-set-blocking node-sha node-shebang-command node-shebang-regex node-signal-exit node-slash node-slide node-sorted-object node-spdx-correct node-spdx-expression-parse node-spdx-license-ids node-sshpk node-ssri node-stream-each node-stream-iterate node-stream-shift node-string-decoder node-string-width node-strip-ansi node-strip-eof node-strip-json-comments node-supports-color node-tar node-term-size node-text-table node-through node-through2 node-timed-out node-tough-cookie node-tunnel-agent node-tweetnacl node-typedarray node-uid-number node-unique-filename node-unpipe node-url-parse-lax node-url-to-options node-util-deprecate node-uuid node-validate-npm-package-license node-validate-npm-package-name node-verror node-wcwidth.js node-which node-which-module node-wide-align node-widest-line node-wrap-ansi node-wrappy node-write-file-atomic node-xdg-basedir node-xtend node-y18n node-yallist node-yargs node-yargs-parser nodejs-doc rpi-eeprom-images Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. -
@Jona
Das ist alles alter Kram.sudo apt autoremove sudo rebootDann würde ich nodejs noch mal drüber bügeln:
iobroker stop sudo apt install nodejs --reinstall iobroker start -
@Thomas-Braun Zwischendurch erst einmal danke für deine Mühe und Hilfe.
Leider sind die beiden Adapter noch immer auf rot.
Der Fehler-Log sieht so aus:2020-09-28 13:21:00.300 - info: host.raspberrypi Restart adapter system.adapter.zigbee.0 because enabled 2020-09-28 13:21:30.328 - info: host.raspberrypi instance system.adapter.zigbee.0 started with pid 2930 2020-09-28 13:21:30.954 - error: host.raspberrypi Caught by controller[0]: /opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/node_modules/bindings/bindings.js:121 2020-09-28 13:21:30.954 - error: host.raspberrypi Caught by controller[0]: throw e; 2020-09-28 13:21:30.955 - error: host.raspberrypi Caught by controller[0]: ^ 2020-09-28 13:21:30.955 - error: host.raspberrypi Caught by controller[0]: Error: libnode.so.64: cannot open shared object file: No such file or directory 2020-09-28 13:21:30.955 - error: host.raspberrypi Caught by controller[0]: at Object.Module._extensions..node (internal/modules/cjs/loader.js:1187:18) 2020-09-28 13:21:30.955 - error: host.raspberrypi Caught by controller[0]: at Module.load (internal/modules/cjs/loader.js:985:32) 2020-09-28 13:21:30.955 - error: host.raspberrypi Caught by controller[0]: at Function.Module._load (internal/modules/cjs/loader.js:878:14) 2020-09-28 13:21:30.956 - error: host.raspberrypi Caught by controller[0]: at Module.require (internal/modules/cjs/loader.js:1025:19) 2020-09-28 13:21:30.956 - error: host.raspberrypi Caught by controller[0]: at require (internal/modules/cjs/helpers.js:72:18) 2020-09-28 13:21:30.956 - error: host.raspberrypi Caught by controller[0]: at bindings (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/node_modules/bindings/bindings.js:112:48) 2020-09-28 13:21:30.956 - error: host.raspberrypi Caught by controller[0]: at Object. (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/lib/linux.js:2:36) 2020-09-28 13:21:30.956 - error: host.raspberrypi Caught by controller[0]: at Module._compile (internal/modules/cjs/loader.js:1137:30) 2020-09-28 13:21:30.957 - error: host.raspberrypi Caught by controller[0]: at Object.Module._extensions..js (internal/modules/cjs/loader.js:1157:10) 2020-09-28 13:21:30.957 - error: host.raspberrypi Caught by controller[0]: at Module.load (internal/modules/cjs/loader.js:985:32) 2020-09-28 13:21:30.957 - error: host.raspberrypi instance system.adapter.zigbee.0 terminated with code 1 (JS_CONTROLLER_STOPPED) -
sudo apt update sudo apt upgradeapt policy node-*Gut möglich, dass man dann noch einen npm rebuild hinterherwerfen muss, wenn die Pakete sauber sind.
