Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Hardware
    4. SONOFF ZigBee 3.0 USB DONGLE PLUS

    NEWS

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    SONOFF ZigBee 3.0 USB DONGLE PLUS

    This topic has been deleted. Only users with topic management privileges can see it.
    • H
      hm_krause @Thomas Braun last edited by

      @thomas-braun ```
      pi@iobroker:~ $ which nodejs node npm && nodejs -v && node -v && npm -v && sudo apt update && apt policy nodejs
      /usr/bin/nodejs
      /usr/bin/node
      /usr/bin/npm
      v14.18.0
      v14.18.0
      6.14.15
      OK:1 http://archive.raspberrypi.org/debian buster InRelease
      OK:2 http://raspbian.raspberrypi.org/raspbian buster InRelease
      OK:3 https://deb.nodesource.com/node_14.x buster InRelease
      Paketlisten werden gelesen... Fertig
      Abhängigkeitsbaum wird aufgebaut.
      Statusinformationen werden eingelesen.... Fertig
      Aktualisierung für 19 Pakete verfügbar. Führen Sie »apt list --upgradable« aus, um sie anzuzeigen.
      nodejs:
      Installiert: 14.18.0-deb-1nodesource1
      Installationskandidat: 14.18.1-deb-1nodesource1
      Versionstabelle:
      14.18.1-deb-1nodesource1 500
      500 https://deb.nodesource.com/node_14.x buster/main armhf Packages
      *** 14.18.0-deb-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:~ $ which nodejs node npm && nodejs -v && node -v && npm -v && sudo apt update && apt policy nodejs
      /usr/bin/nodejs
      /usr/bin/node
      /usr/bin/npm
      v14.18.0
      v14.18.0
      6.14.15
      OK:1 http://raspbian.raspberrypi.org/raspbian buster InRelease
      OK:2 http://archive.raspberrypi.org/debian buster InRelease
      OK:3 https://deb.nodesource.com/node_14.x buster InRelease
      Paketlisten werden gelesen... Fertig
      Abhängigkeitsbaum wird aufgebaut.
      Statusinformationen werden eingelesen.... Fertig
      Aktualisierung für 19 Pakete verfügbar. Führen Sie »apt list --upgradable« aus, um sie anzuzeigen.
      nodejs:
      Installiert: 14.18.0-deb-1nodesource1
      Installationskandidat: 14.18.1-deb-1nodesource1
      Versionstabelle:
      14.18.1-deb-1nodesource1 500
      500 https://deb.nodesource.com/node_14.x buster/main armhf Packages
      *** 14.18.0-deb-1nodesource1 100
      100 /var/lib/dpkg/status
      10.24.0~dfsg-1~deb10u1 500
      500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages

      1 Reply Last reply Reply Quote 0
      • H
        hm_krause @Jan1 last edited by

        @jan1
        ...sorry

        pi@iobroker:~ $ which nodejs node npm && nodejs -v && node -v && npm -v && sudo                                                                        apt update && apt policy nodejs
/usr/bin/nodejs
/usr/bin/node
/usr/bin/npm
v14.18.0
v14.18.0
6.14.15
OK:1 http://archive.raspberrypi.org/debian buster InRelease
OK:2 http://raspbian.raspberrypi.org/raspbian buster InRelease
OK:3 https://deb.nodesource.com/node_14.x buster InRelease
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Aktualisierung für 19 Pakete verfügbar. Führen Sie »apt list --upgradable« aus, um sie anzuzeigen.
nodejs:
  Installiert:           14.18.0-deb-1nodesource1
  Installationskandidat: 14.18.1-deb-1nodesource1
  Versionstabelle:
     14.18.1-deb-1nodesource1 500
        500 https://deb.nodesource.com/node_14.x buster/main armhf Packages
 *** 14.18.0-deb-1nodesource1 100
        100 /var/lib/dpkg/status
     10.24.0~dfsg-1~deb10u1 500
        500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
        Thomas Braun 1 Reply Last reply Reply Quote 0
        • Thomas Braun
          Thomas Braun Most Active @hm_krause last edited by

          @hm_krause Okay, passst grundsätzlich. Hau die 19 Updates auf das System.

          H 1 Reply Last reply Reply Quote 0
          • H
            hm_krause @Thomas Braun last edited by

            @thomas-braun
            Updates durchgeführt, aber:

            zigbee.0
	2021-10-24 13:06:10.609	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
zigbee.0
	2021-10-24 13:06:10.607	info	terminating
zigbee.0
	2021-10-24 13:06:10.109	info	Zigbee: disabling joining new devices.
zigbee.0
	2021-10-24 13:06:10.106	info	cleaned everything up...
zigbee.0
	2021-10-24 13:06:10.097	error	Cannot read property 'getDevice' of undefined
zigbee.0
	2021-10-24 13:06:10.096	error	TypeError: Cannot read property 'getDevice' of undefined at Developer.sendToZigbee (/opt/iobroker/node_modules/iobroker.zigbee/lib/developer.js:103:49) at Developer.onMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/developer.js:46:26) at Zigbee.emit (events.js:412:35) at Zigbee.emit (domain.js:475:12) at change (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5634:34) at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-states-redis/lib/states/statesInRedisClient.js:232:37) at processImmediate (internal/timers.js:464:21)
zigbee.0
	2021-10-24 13:06:10.094	error	unhandled promise rejection: Cannot read property 'getDevice' of undefined
zigbee.0
	2021-10-24 13:06:10.094	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-10-24 13:06:09.714	error	Cannot read property 'getDevice' of undefined
zigbee.0
	2021-10-24 13:06:09.713	error	TypeError: Cannot read property 'getDevice' of undefined at Developer.sendToZigbee (/opt/iobroker/node_modules/iobroker.zigbee/lib/developer.js:103:49) at Developer.onMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/developer.js:46:26) at Zigbee.emit (events.js:412:35) at Zigbee.emit (domain.js:475:12) at change (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5634:34) at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-states-redis/lib/states/statesInRedisClient.js:232:37) at processImmediate (internal/timers.js:464:21)
zigbee.0
	2021-10-24 13:06:09.698	error	unhandled promise rejection: Cannot read property 'getDevice' of undefined
zigbee.0
	2021-10-24 13:06:09.697	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-10-24 13:06:04.251	info	Installed Version: iobroker.zigbee@1.6.3
zigbee.0
	2021-10-24 13:06:03.782	info	Starting Zigbee npm ...
            Thomas Braun 1 Reply Last reply Reply Quote 0
            • Thomas Braun
              Thomas Braun Most Active @hm_krause last edited by

              @hm_krause

              Reboot gemacht?

              H 1 Reply Last reply Reply Quote 0
              • H
                hm_krause @Thomas Braun last edited by

                @thomas-braun
                Ja

                Thomas Braun 1 Reply Last reply Reply Quote 0
                • Thomas Braun
                  Thomas Braun Most Active @hm_krause last edited by

                  @hm_krause
                  Dann bin ich raus. Fällt mir nix zu ein.

                  H 1 Reply Last reply Reply Quote 0
                  • H
                    hm_krause @Thomas Braun last edited by

                    @thomas-braun
                    Danke und ein schönes Wochenende...

                    J 1 Reply Last reply Reply Quote 0
                    • J
                      Jan1 @hm_krause last edited by

                      @hm_krause
                      Da ist auch nix mit Container oder VM im Spiel?

                      H 1 Reply Last reply Reply Quote 0
                      • H
                        hm_krause @Jan1 last edited by

                        @jan1
                        nein, nur der iobroker allein auf dem raspi

                        J Thomas Braun 2 Replies Last reply Reply Quote 0
                        • J
                          Jan1 @hm_krause last edited by

                          @hm_krause
                          Hm, dann weiß ich auch nicht weiter.
                          Hast nix am Stick gefummelt, nur so wie er ist angesteckt und den Pfad angepasst?

                          H 1 Reply Last reply Reply Quote 0
                          • Thomas Braun
                            Thomas Braun Most Active @hm_krause last edited by

                            @hm_krause

                            Cannot read property 'getDevice' of undefined

                            Warum kann das da nicht gelesen werden frage ich mich.
                            Mal den Fixer ausgeführt?

                            iobroker stop
iobroker fix
iobroker start
                            H 2 Replies Last reply Reply Quote 0
                            • H
                              hm_krause @Jan1 last edited by

                              @jan1
                              genau, nur angesteckt

                              @Thomas-Braun
                              teste ich morgen nochmal, habe jetzt den conbee 2 wieder dran

                              1 Reply Last reply Reply Quote 0
                              • JLeg
                                JLeg @m0skit0 last edited by

                                @m0skit0 sagte in SONOFF ZigBee 3.0 USB DONGLE PLUS:

                                @arteck

                                lxc.cgroup2.devices.allow: c 188:0 rwm
lxc.mount.entry: /dev/bus/usb/001/014 dev/bus/usb/001/014 none bind,optional,create=>
lxc.mount.entry: /dev/ttyUSB1 /dev/ttyUSB1 none bind,optional,create=file

                                in Proxmox

                                bei mir läuft iobroker auch im LXC unter Proxmox - das klappt bei mir aber nicht ohne eine passende udev-rule, die nach einem Reboot die Rechte für's USB-Device setzt.
                                Ob's an den Rechten liegt, kann man testen indem man mal nachschaut, wie die aktuellen Rechte aussehen, und/oder z.B. mal einen "chmod 666 /dev/ttyUSB1" auf dem Proxmox-Node probiert...

                                Thomas Braun M 2 Replies Last reply Reply Quote 0
                                • Thomas Braun
                                  Thomas Braun Most Active @JLeg last edited by

                                  @jleg
                                  Auch unter Proxmox sollte man nicht auf /dev/ttyUSBx gehen sondern auf den by-id-Link.
                                  Die user müssen in der passenden Gruppe sein, dann passt das auch. 'dialout' ist das in der Regel.
                                  Standardrechte sind jedenfalls:

                                  echad@chet:~ $ ls -la /dev/ttyUSB0
crw-rw---- 1 root dialout 188, 0 24. Okt 18:20 /dev/ttyUSB0
                                  JLeg 1 Reply Last reply Reply Quote 0
                                  • JLeg
                                    JLeg @Thomas Braun last edited by

                                    @thomas-braun sagte in SONOFF ZigBee 3.0 USB DONGLE PLUS:

                                    @jleg
                                    Auch unter Proxmox sollte man nicht auf /dev/ttyUSBx gehen sondern auf den by-id-Link.

                                    jaja - ich hatte das Device lediglich an das des TO angepasst. Meines heisst anders, alles gut...

                                    1 Reply Last reply Reply Quote 0
                                    • B
                                      bibabuz @Jan1 last edited by

                                      @jan1 Vielen Dank für deine Tipps. Stick läuft super bei mir 👍

                                      1 Reply Last reply Reply Quote 0
                                      • M
                                        m0skit0 @JLeg last edited by

                                        @jleg
                                        @Thomas-Braun

                                        jetzt wird es leider für mich zu kompliziert, ich bin Linux Anfänger.
                                        Aber vlt. kann mir ja einer von euch beiden, mal eine Hilfestellung geben wie ich das von euch vorgeschlagene umsetzen kann.

                                        Wäre sehr dankbar

                                        lg
                                        m0skit0

                                        JLeg 1 Reply Last reply Reply Quote 0
                                        • H
                                          hm_krause @Thomas Braun last edited by hm_krause

                                          @thomas-braun
                                          Fix ausgeführt aber die Fehler sind gleich:

                                          host.iobroker
	2021-10-25 16:54:56.534	info	Restart adapter system.adapter.zigbee.0 because enabled
host.iobroker
	2021-10-25 16:54:56.533	error	instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
host.iobroker
	2021-10-25 16:54:56.532	error	Caught by controller[1]: at processImmediate (internal/timers.js:464:21)
host.iobroker
	2021-10-25 16:54:56.532	error	Caught by controller[1]: at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-states-redis/lib/states/statesInRedisClient.js:232:37)
host.iobroker
	2021-10-25 16:54:56.531	error	Caught by controller[1]: at change (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5634:34)
host.iobroker
	2021-10-25 16:54:56.531	error	Caught by controller[1]: at Zigbee.emit (domain.js:475:12)
host.iobroker
	2021-10-25 16:54:56.531	error	Caught by controller[1]: at Zigbee.emit (events.js:412:35)
host.iobroker
	2021-10-25 16:54:56.530	error	Caught by controller[1]: at Developer.onMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/developer.js:46:26)
host.iobroker
	2021-10-25 16:54:56.530	error	Caught by controller[1]: at Developer.sendToZigbee (/opt/iobroker/node_modules/iobroker.zigbee/lib/developer.js:103:49)
host.iobroker
	2021-10-25 16:54:56.529	error	Caught by controller[1]: TypeError: Cannot read property 'getDevice' of undefined
host.iobroker
	2021-10-25 16:54:56.528	error	Caught by controller[0]: 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(). The promise rejected with the reason:
zigbee.0
	2021-10-25 16:54:55.934	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
                                          1 Reply Last reply Reply Quote 0
                                          • H
                                            hm_krause @Thomas Braun last edited by

                                            @thomas-braun
                                            das kommt noch vorher:

                                            zigbee.0
	2021-10-25 16:54:55.932	info	terminating
zigbee.0
	2021-10-25 16:54:55.931	warn	Failed to stop zigbee during startup
zigbee.0
	2021-10-25 16:54:55.781	info	Zigbee: disabling joining new devices.
zigbee.0
	2021-10-25 16:54:55.767	info	cleaned everything up...
zigbee.0
	2021-10-25 16:54:55.753	error	Cannot read property 'getDevice' of undefined
zigbee.0
	2021-10-25 16:54:55.751	error	TypeError: Cannot read property 'getDevice' of undefined at Developer.sendToZigbee (/opt/iobroker/node_modules/iobroker.zigbee/lib/developer.js:103:49) at Developer.onMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/developer.js:46:26) at Zigbee.emit (events.js:412:35) at Zigbee.emit (domain.js:475:12) at change (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5634:34) at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-states-redis/lib/states/statesInRedisClient.js:232:37) at processImmediate (internal/timers.js:464:21)
zigbee.0
	2021-10-25 16:54:55.722	error	unhandled promise rejection: Cannot read property 'getDevice' of undefined
zigbee.0
	2021-10-25 16:54:55.721	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-10-25 16:54:50.203	info	Installed Version: iobroker.zigbee@1.6.3
zigbee.0
	2021-10-25 16:54:50.042	error	Error herdsman start
zigbee.0
	2021-10-25 16:54:50.041	error	Failed to start Zigbee
zigbee.0
	2021-10-25 16:54:50.040	error	Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: No such file or directory, cannot open com: /dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_1469408ef193eb1180efaa5b3d98b6d1-if00-port0'"
zigbee.0
	2021-10-25 16:54:49.750	info	Starting Zigbee npm ...
zigbee.0
	2021-10-25 16:54:49.647	info	starting. Version 1.6.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v14.18.1, js-controller: 3.3.18
                                            Thomas Braun 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            1.0k
                                            Online

                                            31.7k
                                            Users

                                            79.7k
                                            Topics

                                            1.3m
                                            Posts

                                            sonoff zigbee
                                            50
                                            435
                                            95674
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo