NEWS
Zigbee Adapter funktioniert nicht
Zigbee Adapter funktioniert nicht
ioBroker Allgemein
99
Posts
6
Posters
8.1k
Views
4
Watching
-
@thomas-braun sagte in Zigbee Adapter funktioniert nicht:
sudo apt update apt policy nodejs
Ein Schritt weiter, aber bleibt bei v10
pi@ioBroker-RasPi4:~ $ sudo apt update OK:1 http://phoscon.de/apt/deconz buster InRelease OK:2 http://raspbian.raspberrypi.org/raspbian buster InRelease OK:3 http://archive.raspberrypi.org/debian buster InRelease OK:4 https://deb.nodesource.com/node_12.x buster InRelease Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen.... Fertig Aktualisierung für 1 Paket verfügbar. Führen Sie »apt list --upgradable« aus, um es anzuzeigen. pi@ioBroker-RasPi4:~ $ apt policy nodejs nodejs: Installiert: 10.24.1-1nodesource1 Installationskandidat: 12.22.6-deb-1nodesource1 Versionstabelle: 12.22.6-deb-1nodesource1 500 500 https://deb.nodesource.com/node_12.x buster/main armhf Packages *** 10.24.1-1nodesource1 100 100 /var/lib/dpkg/status 10.24.0~dfsg-1~deb10u1 500 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages pi@ioBroker-RasPi4:~ $ -
@thomas-braun sagte in Zigbee Adapter funktioniert nicht:
sudo apt update apt policy nodejs
Ein Schritt weiter, aber bleibt bei v10
pi@ioBroker-RasPi4:~ $ sudo apt update OK:1 http://phoscon.de/apt/deconz buster InRelease OK:2 http://raspbian.raspberrypi.org/raspbian buster InRelease OK:3 http://archive.raspberrypi.org/debian buster InRelease OK:4 https://deb.nodesource.com/node_12.x buster InRelease Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen.... Fertig Aktualisierung für 1 Paket verfügbar. Führen Sie »apt list --upgradable« aus, um es anzuzeigen. pi@ioBroker-RasPi4:~ $ apt policy nodejs nodejs: Installiert: 10.24.1-1nodesource1 Installationskandidat: 12.22.6-deb-1nodesource1 Versionstabelle: 12.22.6-deb-1nodesource1 500 500 https://deb.nodesource.com/node_12.x buster/main armhf Packages *** 10.24.1-1nodesource1 100 100 /var/lib/dpkg/status 10.24.0~dfsg-1~deb10u1 500 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages pi@ioBroker-RasPi4:~ $ -
-
@thomas-braun Halleluja, danke!
pi@ioBroker-RasPi4:~ $ node -v v12.22.6Das muss einfacher werden, um die "breite Masse" zu erreichen!
@loverz sagte in Zigbee Adapter funktioniert nicht:
Das muss einfach werden, um die "breite Masse" zu erreichen!
Ist es doch?!?
Ja, die alte Leier... Linux muss dies, Linux muss das.
Ist es nur meist bereits.
Die meisten nutzen Linux ja bereits in zig Geräten, die zuhause so rumstehen. -
@loverz sagte in Zigbee Adapter funktioniert nicht:
Das muss einfach werden, um die "breite Masse" zu erreichen!
Ist es doch?!?
Ja, die alte Leier... Linux muss dies, Linux muss das.
Ist es nur meist bereits.
Die meisten nutzen Linux ja bereits in zig Geräten, die zuhause so rumstehen. -
@thomas-braun also ich kann von mir behaupten, dass ich mich gut mit PCs auskenne. Die breite Masse benötigt ein Nodejs Update per iobroker Weboberfläche. Meine Meinung
@loverz sagte in Zigbee Adapter funktioniert nicht:
Die breite Masse benötigt ein Nodejs Update per iobroker Weboberfläche.
Bitte bloß nicht.
-
@loverz sagte in Zigbee Adapter funktioniert nicht:
Die breite Masse benötigt ein Nodejs Update per iobroker Weboberfläche.
Bitte bloß nicht.
-
@thomas-braun wieso nicht?
Ein klick, wer will und fertig.Am besten ein zweiter Klick zum downgrade, wenn etwas nicht funktioniert, wie bei mir nun. Der YAHKA Adapter bleibt rot und spuckt zig Fehler aus...
Weil der iobroker nicht für das Paketmanagement deiner Distribution zuständig ist und auch nicht sein soll.
Ist das jetzt alles senkrecht im System?
which nodejs node npm && nodejs -v && node -v && npm -v && sudo apt update && sudo apt update && apt policy nodejs -
Weil der iobroker nicht für das Paketmanagement deiner Distribution zuständig ist und auch nicht sein soll.
Ist das jetzt alles senkrecht im System?
which nodejs node npm && nodejs -v && node -v && npm -v && sudo apt update && sudo apt update && apt policy nodejs@thomas-braun denke schon, bin nur jetzt unterwegs zu meinem Kumpel. Muss dort auch upgraden…
-
Weil der iobroker nicht für das Paketmanagement deiner Distribution zuständig ist und auch nicht sein soll.
Ist das jetzt alles senkrecht im System?
which nodejs node npm && nodejs -v && node -v && npm -v && sudo apt update && sudo apt update && apt policy nodejs -
@thomas-braun alles tacko nun, hab es beim zweiten System auch upgedatet.
Du solltest den Befehl
sudo apt upgradenach
sudo apt updatein deiner Anleitung ergänzen, ohne den geht es nämlich nicht...
Steht zwar drin, ist aber auch Grundwissen. Bzw. sollte es sein.
Sein per apt verwaltetes System hält man immer mit dem Zweisatz aus Update & Upgrade auf Stand.
-
Steht zwar drin, ist aber auch Grundwissen. Bzw. sollte es sein.
Sein per apt verwaltetes System hält man immer mit dem Zweisatz aus Update & Upgrade auf Stand.
-
@thomas-braun steht nicht drin, zumindest nicht unten wo man es ausführen muss:
Grundwissen ist vieles, für die, die kein Grundwissen haben (wie ich) benötigt es halt Anleitungen
Das Grundwissen wird doch schon viel weiter oben aufgefrischt:
Wenn bereits eine Version von nodejs über den obigen Weg installiert wurde kann man Updates innerhalb der jeweiligen Version von nodejs mit
sudo apt update sudo apt upgradevornehmen. In einem wird dann auch der Rest vom System aktualisiert.
-
Das Grundwissen wird doch schon viel weiter oben aufgefrischt:
Wenn bereits eine Version von nodejs über den obigen Weg installiert wurde kann man Updates innerhalb der jeweiligen Version von nodejs mit
sudo apt update sudo apt upgradevornehmen. In einem wird dann auch der Rest vom System aktualisiert.
@thomas-braun ich hatte direkt mit Update angefangen, weil nodejs ja schon vorher installiert war und da fehlte der Befehl.
Wie auch immer, ich weiß es nun, wenn du meinst, die anderen brauchen es nicht, dann lass es weg, ist ja deine Anleitung. -
@thomas-braun ich hatte direkt mit Update angefangen, weil nodejs ja schon vorher installiert war und da fehlte der Befehl.
Wie auch immer, ich weiß es nun, wenn du meinst, die anderen brauchen es nicht, dann lass es weg, ist ja deine Anleitung.Hast du noch nie dein System aktualisiert?
Das geht halt immer über den Zweisatz. -
Hast du noch nie dein System aktualisiert?
Das geht halt immer über den Zweisatz. -
@thomas-braun doch, aber hab die Befehle aus dem Netz kopiert.
Wie gesagt: Dieses Terminal Zeugs ist sowas von 90er
@loverz sagte in Zigbee Adapter funktioniert nicht:
Dieses Terminal Zeugs ist sowas von 90er
Quatsch.
-
@loverz sagte in Zigbee Adapter funktioniert nicht:
Dieses Terminal Zeugs ist sowas von 90er
Quatsch.
na ich lese mal mit ... da mein zigbee stick auch nach x versuchen seine funktion verweigert ... alle updates gefahren und auch der ( instable ) admin 5 läuft ....
happy hacking
PS. - habe leider den fehler gemacht den update-wünschen des systems zu folgen ... radar ist auch mehr als tot ( doch das gehört hier nicht hin )
-
@loverz sagte in Zigbee Adapter funktioniert nicht:
Dieses Terminal Zeugs ist sowas von 90er
Quatsch.
@thomas-braun hab nun mit Nodejs v12.x nochmal das pairing versucht.
Vielleicht kann sich hier jemand, der viel Ahnung von der Materie hat mal mein log ansehen.
Das log zeigt meinen verzweifelten Versuch 2 einfache Philips Hue GU10 Lampen in den Zigbee Adapter zu bekommen.
Dabei stürzt der Adapter gefühlt wahllos ab und macht was er will...zigbee.0 2021-09-25 20:38:04.093 info Zigbee started zigbee.0 2021-09-25 20:38:04.090 info 0x00178801084efafb (addr 41680): 929001953301 - Philips Hue white ambiance GU10 with Bluetooth (Router) zigbee.0 2021-09-25 20:38:04.080 info 0x00158d000446180c (addr 52440): WSDCGQ01LM - Xiaomi MiJia temperature & humidity sensor (EndDevice) zigbee.0 2021-09-25 20:38:04.044 info Currently 2 devices are joined: zigbee.0 2021-09-25 20:38:04.022 info --> transmitPower : high zigbee.0 2021-09-25 20:38:03.998 info Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20210901}} zigbee.0 2021-09-25 20:38:01.784 info Installed Version: iobroker.zigbee@1.5.6 zigbee.0 2021-09-25 20:38:00.929 info Starting Zigbee npm ... zigbee.0 2021-09-25 20:38:00.622 info starting. Version 1.5.6 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.22.6, js-controller: 3.3.18 zigbee.0 2021-09-25 20:37:21.086 info terminating with timeout zigbee.0 2021-09-25 20:37:20.076 warn Terminated (UNCAUGHT_EXCEPTION): Without reason zigbee.0 2021-09-25 20:37:20.074 info terminating zigbee.0 2021-09-25 20:37:19.576 info Zigbee: disabling joining new devices. zigbee.0 2021-09-25 20:37:19.571 info cleaned everything up... zigbee.0 2021-09-25 20:37:19.560 error Error Not exists zigbee.0 2021-09-25 20:37:19.559 error ReplyError: Error Not exists at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14) zigbee.0 2021-09-25 20:37:19.558 error unhandled promise rejection: Error Not exists zigbee.0 2021-09-25 20:37:19.557 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). zigbee.0 2021-09-25 20:37:19.555 error Error Not exists zigbee.0 2021-09-25 20:37:19.554 error ReplyError: Error Not exists at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14) zigbee.0 2021-09-25 20:37:19.553 error unhandled promise rejection: Error Not exists zigbee.0 2021-09-25 20:37:19.552 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). zigbee.0 2021-09-25 20:37:19.550 error Error Not exists zigbee.0 2021-09-25 20:37:19.549 error ReplyError: Error Not exists at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14) zigbee.0 2021-09-25 20:37:19.547 error unhandled promise rejection: Error Not exists zigbee.0 2021-09-25 20:37:19.546 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). zigbee.0 2021-09-25 20:37:19.544 error Error Not exists zigbee.0 2021-09-25 20:37:19.543 error ReplyError: Error Not exists at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14) zigbee.0 2021-09-25 20:37:19.542 error unhandled promise rejection: Error Not exists zigbee.0 2021-09-25 20:37:19.540 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). zigbee.0 2021-09-25 20:37:19.538 error Error Not exists zigbee.0 2021-09-25 20:37:19.537 error ReplyError: Error Not exists at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14) zigbee.0 2021-09-25 20:37:19.536 error unhandled promise rejection: Error Not exists zigbee.0 2021-09-25 20:37:19.535 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). zigbee.0 2021-09-25 20:37:19.533 error Error Not exists zigbee.0 2021-09-25 20:37:19.532 error ReplyError: Error Not exists at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14) zigbee.0 2021-09-25 20:37:19.531 error unhandled promise rejection: Error Not exists zigbee.0 2021-09-25 20:37:19.530 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). zigbee.0 2021-09-25 20:37:19.528 error Error Not exists zigbee.0 2021-09-25 20:37:19.527 error ReplyError: Error Not exists at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14) zigbee.0 2021-09-25 20:37:19.512 error unhandled promise rejection: Error Not exists zigbee.0 2021-09-25 20:37:19.510 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). zigbee.0 2021-09-25 20:37:19.508 error Error Not exists zigbee.0 2021-09-25 20:37:19.507 error ReplyError: Error Not exists at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14) zigbee.0 2021-09-25 20:37:19.501 error unhandled promise rejection: Error Not exists zigbee.0 2021-09-25 20:37:19.499 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). zigbee.0 2021-09-25 20:37:19.497 error Error Not exists zigbee.0 2021-09-25 20:37:19.496 error ReplyError: Error Not exists at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14) zigbee.0 2021-09-25 20:37:19.495 error unhandled promise rejection: Error Not exists zigbee.0 2021-09-25 20:37:19.493 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). zigbee.0 2021-09-25 20:37:19.457 error Error Not exists zigbee.0 2021-09-25 20:37:19.456 error ReplyError: Error Not exists at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14) zigbee.0 2021-09-25 20:37:19.453 error unhandled promise rejection: Error Not exists zigbee.0 2021-09-25 20:37:19.452 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). zigbee.0 2021-09-25 20:37:16.401 info DeviceConfigure successful 0x00178801084efc74 LTG002 zigbee.0 2021-09-25 20:37:16.307 info Configuring 0x00178801084efc74 LTG002 zigbee.0 2021-09-25 20:37:16.302 info Device '0x00178801084efc74' is supported, identified as: Philips Hue white ambiance GU10 with Bluetooth (929001953301) zigbee.0 2021-09-25 20:37:16.300 info Successfully interviewed '0x00178801084efc74', device has succesfully been paired zigbee.0 2021-09-25 20:37:02.764 warn Device '0x00178801084efc74' announced itself zigbee.0 2021-09-25 20:37:02.752 info Starting interview of '0x00178801084efc74' zigbee.0 2021-09-25 20:36:26.351 info Zigbee: allowing new devices to join. zigbee.0 2021-09-25 20:35:35.669 info Zigbee started zigbee.0 2021-09-25 20:35:35.667 info 0x00178801084efafb (addr 41680): 929001953301 - Philips Hue white ambiance GU10 with Bluetooth (Router) zigbee.0 2021-09-25 20:35:35.659 info 0x00158d000446180c (addr 52440): WSDCGQ01LM - Xiaomi MiJia temperature & humidity sensor (EndDevice) zigbee.0 2021-09-25 20:35:35.630 info Currently 2 devices are joined: zigbee.0 2021-09-25 20:35:35.615 info --> transmitPower : high zigbee.0 2021-09-25 20:35:35.595 info Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20210901}} zigbee.0 2021-09-25 20:35:33.324 info Installed Version: iobroker.zigbee@1.5.6 zigbee.0 2021-09-25 20:35:32.510 info Starting Zigbee npm ... zigbee.0 2021-09-25 20:35:32.242 info starting. Version 1.5.6 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.22.6, js-controller: 3.3.18 zigbee.0 2021-09-25 20:34:51.802 info terminating with timeout zigbee.0 2021-09-25 20:34:50.902 error Failed to stop zigbee (Error: Cannot backup - adapter not commissioned at AdapterBackup.<anonymous> (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/adapter-backup.js:99:23) at Generator.next (<anonymous>) at fulfilled (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/adapter-backup.js:24:58)) zigbee.0 2021-09-25 20:34:50.800 warn Terminated (UNCAUGHT_EXCEPTION): Without reason zigbee.0 2021-09-25 20:34:50.797 info terminating zigbee.0 2021-09-25 20:34:50.371 error Error Not exists zigbee.0 2021-09-25 20:34:50.370 error ReplyError: Error Not exists at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14) zigbee.0 2021-09-25 20:34:50.369 error unhandled promise rejection: Error Not exists zigbee.0 2021-09-25 20:34:50.368 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). zigbee.0 2021-09-25 20:34:50.365 error Error Not exists zigbee.0 2021-09-25 20:34:50.360 error ReplyError: Error Not exists at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14) zigbee.0 2021-09-25 20:34:50.359 error unhandled promise rejection: Error Not exists zigbee.0 2021-09-25 20:34:50.355 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). zigbee.0 2021-09-25 20:34:50.353 error Error Not exists zigbee.0 2021-09-25 20:34:50.352 error ReplyError: Error Not exists at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14) zigbee.0 2021-09-25 20:34:50.350 error unhandled promise rejection: Error Not exists zigbee.0 2021-09-25 20:34:50.349 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). zigbee.0 2021-09-25 20:34:50.299 info Zigbee: disabling joining new devices. zigbee.0 2021-09-25 20:34:50.294 info cleaned everything up... zigbee.0 2021-09-25 20:34:50.286 error Error Not exists zigbee.0 2021-09-25 20:34:50.284 error ReplyError: Error Not exists at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14) zigbee.0 2021-09-25 20:34:50.283 error unhandled promise rejection: Error Not exists zigbee.0 2021-09-25 20:34:50.282 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). zigbee.0 2021-09-25 20:34:50.281 error Error Not exists zigbee.0 2021-09-25 20:34:50.280 error ReplyError: Error Not exists at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14) zigbee.0 2021-09-25 20:34:50.278 error unhandled promise rejection: Error Not exists zigbee.0 2021-09-25 20:34:50.277 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). zigbee.0 2021-09-25 20:34:50.275 error Error Not exists zigbee.0 2021-09-25 20:34:50.274 error ReplyError: Error Not exists at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14) zigbee.0 2021-09-25 20:34:50.273 error unhandled promise rejection: Error Not exists zigbee.0 2021-09-25 20:34:50.272 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). zigbee.0 2021-09-25 20:34:50.271 error Error Not exists zigbee.0 2021-09-25 20:34:50.270 error ReplyError: Error Not exists at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14) zigbee.0 2021-09-25 20:34:50.268 error unhandled promise rejection: Error Not exists zigbee.0 2021-09-25 20:34:50.267 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). zigbee.0 2021-09-25 20:34:50.266 error Error Not exists zigbee.0 2021-09-25 20:34:50.264 error ReplyError: Error Not exists at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14) zigbee.0 2021-09-25 20:34:50.263 error unhandled promise rejection: Error Not exists zigbee.0 2021-09-25 20:34:50.262 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). zigbee.0 2021-09-25 20:34:50.259 error Error Not exists zigbee.0 2021-09-25 20:34:50.258 error ReplyError: Error Not exists at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14) zigbee.0 2021-09-25 20:34:50.257 error unhandled promise rejection: Error Not exists zigbee.0 2021-09-25 20:34:50.255 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). zigbee.0 2021-09-25 20:34:41.723 info DeviceConfigure successful 0x00178801084efc74 LTG002 zigbee.0 2021-09-25 20:34:41.527 info Configuring 0x00178801084efc74 LTG002 zigbee.0 2021-09-25 20:34:41.524 info Device '0x00178801084efc74' is supported, identified as: Philips Hue white ambiance GU10 with Bluetooth (929001953301) zigbee.0 2021-09-25 20:34:41.522 info Successfully interviewed '0x00178801084efc74', device has succesfully been paired zigbee.0 2021-09-25 20:34:33.985 warn Device '0x00178801084efc74' announced itself zigbee.0 2021-09-25 20:34:17.285 info Starting interview of '0x00178801084efc74' zigbee.0 2021-09-25 20:33:47.550 error Failed to interview '0x00178801084efc74', device has not succesfully been paired. undefined zigbee.0 2021-09-25 20:33:38.412 info DeviceConfigure successful 0x00178801084efc74 LTG002 zigbee.0 2021-09-25 20:33:38.187 info Configuring 0x00178801084efc74 LTG002 zigbee.0 2021-09-25 20:33:38.181 info Device '0x00178801084efc74' is supported, identified as: Philips Hue white ambiance GU10 with Bluetooth (929001953301) zigbee.0 2021-09-25 20:33:38.180 info Successfully interviewed '0x00178801084efc74', device has succesfully been paired zigbee.0 2021-09-25 20:33:26.667 warn Device '0x00178801084efc74' announced itself zigbee.0 2021-09-25 20:32:50.830 info Starting interview of '0x00178801084efc74' zigbee.0 2021-09-25 20:31:56.841 warn Device '0x00178801084efc74' announced itself zigbee.0 2021-09-25 20:31:29.267 info Starting interview of '0x00178801084efc74' zigbee.0 2021-09-25 20:31:23.818 info Zigbee: allowing new devices to join. zigbee.0 2021-09-25 20:30:43.886 info State value to set for "zigbee.0.00178801084efafb.colortemp" has to be type "number" but received type "string" zigbee.0 2021-09-25 20:30:43.849 info State value to set for "zigbee.0.00178801084efafb.colortemp" has to be type "number" but received type "string" zigbee.0 2021-09-25 20:30:43.805 info State value to set for "zigbee.0.00178801084efafb.brightness" has to be type "number" but received type "string" zigbee.0 2021-09-25 20:30:36.683 info State value to set for "zigbee.0.00178801084efafb.colortemp" has to be type "number" but received type "string" zigbee.0 2021-09-25 20:30:33.165 info State value to set for "zigbee.0.00178801084efafb.colortemp" has to be type "number" but received type "string" zigbee.0 2021-09-25 20:30:30.702 info State value to set for "zigbee.0.00178801084efafb.brightness" has to be type "number" but received type "string" zigbee.0 2021-09-25 20:30:28.119 info State value to set for "zigbee.0.00178801084efafb.colortemp" has to be type "number" but received type "string" zigbee.0 2021-09-25 20:30:28.027 info State value to set for "zigbee.0.00178801084efafb.colortemp" has to be type "number" but received type "string" zigbee.0 2021-09-25 20:30:21.404 info State value to set for "zigbee.0.00178801084efafb.brightness" has to be type "number" but received type "string" zigbee.0 2021-09-25 20:30:21.332 info State value to set for "zigbee.0.00178801084efafb.brightness" has to be type "number" but received type "string" zigbee.0 2021-09-25 20:30:16.679 error Send command to 0x00178801084efafb failed with no error code (undefined) zigbee.0 2021-09-25 20:30:16.643 info State value to set for "zigbee.0.00178801084efafb.brightness" has to be type "number" but received type "string" zigbee.0 2021-09-25 20:30:14.509 info State value to set for "zigbee.0.00178801084efafb.brightness" has to be type "number" but received type "string" zigbee.0 2021-09-25 20:30:14.418 info State value to set for "zigbee.0.00178801084efafb.brightness" has to be type "number" but received type "string" zigbee.0 2021-09-25 20:30:12.792 error Send command to 0x00178801084efafb failed with no error code (undefined) zigbee.0 2021-09-25 20:30:12.610 info State value to set for "zigbee.0.00178801084efafb.brightness" has to be type "number" but received type "string" zigbee.0 2021-09-25 20:30:09.522 info State value to set for "zigbee.0.00178801084efafb.brightness" has to be type "number" but received type "string" zigbee.0 2021-09-25 20:30:09.432 info State value to set for "zigbee.0.00178801084efafb.brightness" has to be type "number" but received type "string" zigbee.0 2021-09-25 20:30:06.147 info State value to set for "zigbee.0.00178801084efafb.brightness" has to be type "number" but received type "string" zigbee.0 2021-09-25 20:30:04.713 info State value to set for "zigbee.0.00178801084efafb.brightness" has to be type "number" but received type "string" zigbee.0 2021-09-25 20:30:02.158 info State value to set for "zigbee.0.00178801084efafb.brightness" has to be type "number" but received type "string" zigbee.0 2021-09-25 20:30:01.987 info State value to set for "zigbee.0.00178801084efafb.brightness" has to be type "number" but received type "string" zigbee.0 2021-09-25 20:29:57.296 info State value to set for "zigbee.0.00178801084efafb.colortemp" has to be type "number" but received type "string" zigbee.0 2021-09-25 20:29:57.155 info State value to set for "zigbee.0.00178801084efafb.colortemp" has to be type "number" but received type "string" zigbee.0 2021-09-25 20:29:25.271 error Device 0x00178801084efc74 "undefined" not described in statesMapping. zigbee.0 2021-09-25 20:29:24.580 info Zigbee started zigbee.0 2021-09-25 20:29:24.578 info 0x00178801084efc74 (addr 45654): Not supported (model undefined)(Unknown) zigbee.0 2021-09-25 20:29:24.577 info 0x00178801084efafb (addr 41680): 929001953301 - Philips Hue white ambiance GU10 with Bluetooth (Router) zigbee.0 2021-09-25 20:29:24.569 info 0x00158d000446180c (addr 52440): WSDCGQ01LM - Xiaomi MiJia temperature & humidity sensor (EndDevice) zigbee.0 2021-09-25 20:29:24.538 info Currently 3 devices are joined: zigbee.0 2021-09-25 20:29:24.520 info --> transmitPower : high zigbee.0 2021-09-25 20:29:24.500 info Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20210901}} zigbee.0 2021-09-25 20:29:22.213 info Installed Version: iobroker.zigbee@1.5.6 zigbee.0 2021-09-25 20:29:21.528 info Starting Zigbee npm ... zigbee.0 2021-09-25 20:29:21.266 info starting. Version 1.5.6 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.22.6, js-controller: 3.3.18 zigbee.0 2021-09-25 20:29:10.052 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason zigbee.0 2021-09-25 20:29:10.049 info terminating zigbee.0 2021-09-25 20:29:09.552 info Zigbee: disabling joining new devices. zigbee.0 2021-09-25 20:29:09.547 info cleaned everything up... zigbee.0 2021-09-25 20:29:09.544 info Got terminate signal TERMINATE_YOURSELF zigbee.0 2021-09-25 20:28:55.329 error Send command to 0x00178801084efafb failed with no error code (undefined) zigbee.0 2021-09-25 20:28:55.303 info State value to set for "zigbee.0.00178801084efafb.brightness" has to be type "number" but received type "string" zigbee.0 2021-09-25 20:28:47.605 info State value to set for "zigbee.0.00178801084efafb.brightness" has to be type "number" but received type "string" zigbee.0 2021-09-25 20:28:47.504 info State value to set for "zigbee.0.00178801084efafb.brightness" has to be type "number" but received type "string" zigbee.0 2021-09-25 20:28:43.202 info State value to set for "zigbee.0.00178801084efafb.colortemp" has to be type "number" but received type "string" zigbee.0 2021-09-25 20:28:43.041 info State value to set for "zigbee.0.00178801084efafb.colortemp" has to be type "number" but received type "string" zigbee.0 2021-09-25 20:28:40.828 info State value to set for "zigbee.0.00178801084efafb.colortemp" has to be type "number" but received type "string" zigbee.0 2021-09-25 20:28:40.656 info State value to set for "zigbee.0.00178801084efafb.colortemp" has to be type "number" but received type "string" zigbee.0 2021-09-25 20:28:34.882 error Send command to 0x00178801084efafb failed with no error code (undefined) zigbee.0 2021-09-25 20:28:34.812 info State value to set for "zigbee.0.00178801084efafb.brightness" has to be type "number" but received type "string" zigbee.0 2021-09-25 20:28:31.882 info State value to set for "zigbee.0.00178801084efafb.brightness" has to be type "number" but received type "string" zigbee.0 2021-09-25 20:28:31.723 info State value to set for "zigbee.0.00178801084efafb.brightness" has to be type "number" but received type "string" zigbee.0 2021-09-25 20:27:58.120 warn Blocked interview for 'undefined' because the network is closed zigbee.0 2021-09-25 20:27:53.923 info DeviceConfigure successful 0x00178801084efafb LTG002 zigbee.0 2021-09-25 20:27:53.740 info Configuring 0x00178801084efafb LTG002 zigbee.0 2021-09-25 20:27:53.737 info Device '0x00178801084efafb' is supported, identified as: Philips Hue white ambiance GU10 with Bluetooth (929001953301) zigbee.0 2021-09-25 20:27:53.735 info Successfully interviewed '0x00178801084efafb', device has succesfully been paired zigbee.0 2021-09-25 20:27:43.206 warn Failed to ping 0x00178801084efafb undefined zigbee.0 2021-09-25 20:27:43.001 warn Device '0x00178801084efafb' announced itself zigbee.0 2021-09-25 20:27:42.921 info Zigbee: stop joining zigbee.0 2021-09-25 20:27:42.487 info Starting interview of '0x00178801084efafb' zigbee.0 2021-09-25 20:26:47.018 info DeviceConfigure successful 0x00178801084efc74 LTG002 zigbee.0 2021-09-25 20:26:46.814 info Configuring 0x00178801084efc74 LTG002 zigbee.0 2021-09-25 20:26:46.811 info Device '0x00178801084efc74' is supported, identified as: Philips Hue white ambiance GU10 with Bluetooth (929001953301) zigbee.0 2021-09-25 20:26:46.810 info Successfully interviewed '0x00178801084efc74', device has succesfully been paired zigbee.0 2021-09-25 20:26:32.534 warn Device '0x00178801084efc74' announced itself zigbee.0 2021-09-25 20:26:32.492 info Starting interview of '0x00178801084efc74' zigbee.0 2021-09-25 20:26:13.183 info DeviceConfigure successful 0x00178801084efc74 LTG002 zigbee.0 2021-09-25 20:26:12.947 info Configuring 0x00178801084efc74 LTG002 zigbee.0 2021-09-25 20:26:12.931 info Device '0x00178801084efc74' is supported, identified as: Philips Hue white ambiance GU10 with Bluetooth (929001953301) zigbee.0 2021-09-25 20:26:12.930 info Successfully interviewed '0x00178801084efc74', device has succesfully been paired zigbee.0 2021-09-25 20:25:58.586 warn Device '0x00178801084efc74' announced itself zigbee.0 2021-09-25 20:25:58.539 info Starting interview of '0x00178801084efc74' zigbee.0 2021-09-25 20:25:41.583 info Zigbee: allowing new devices to join. zigbee.0 2021-09-25 20:24:07.999 warn Stopping to ping 0x00178801084f2e5a LTG002 after 4 ping attempts zigbee.0 2021-09-25 19:52:51.320 warn Device '0x00178801084f2e5a' announced itself zigbee.0 2021-09-25 19:42:46.077 warn Device '0x00178801084f2e5a' announced itselfInteressant dabei ist vor allem, dass er die gleiche Leuchte mehrfach erfolgreich koppelt, aber dennoch nichts im Adapter erscheint. Bzw. gerade gesehen, dass die Lampe kurz im Adapter als Bild zu sehen ist und dann wieder verschwindet...
zigbee.0 2021-09-25 20:51:33.745 info DeviceConfigure successful 0x00178801084efc74 LTG002 zigbee.0 2021-09-25 20:51:33.507 info Configuring 0x00178801084efc74 LTG002 zigbee.0 2021-09-25 20:51:33.503 info Device '0x00178801084efc74' is supported, identified as: Philips Hue white ambiance GU10 with Bluetooth (929001953301) zigbee.0 2021-09-25 20:51:33.502 info Successfully interviewed '0x00178801084efc74', device has succesfully been paired zigbee.0 2021-09-25 20:51:22.313 warn Device '0x00178801084efc74' announced itself zigbee.0 2021-09-25 20:51:22.237 info Starting interview of '0x00178801084efc74' zigbee.0 2021-09-25 20:50:44.248 info DeviceConfigure successful 0x00178801084efc74 LTG002 zigbee.0 2021-09-25 20:50:44.046 info Configuring 0x00178801084efc74 LTG002 zigbee.0 2021-09-25 20:50:44.041 info Device '0x00178801084efc74' is supported, identified as: Philips Hue white ambiance GU10 with Bluetooth (929001953301) zigbee.0 2021-09-25 20:50:44.039 info Successfully interviewed '0x00178801084efc74', device has succesfully been paired zigbee.0 2021-09-25 20:50:39.702 info Starting interview of '0x00178801084efc74' zigbee.0 2021-09-25 20:50:16.075 info Zigbee: allowing new devices to join. zigbee.0 2021-09-25 20:49:44.662 info Zigbee started
75
Online32.4k
Users81.3k
Topics1.3m
Posts