NEWS
SONOFF ZigBee 3.0 USB DONGLE PLUS
- 
					
					
					
					
 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=filein Proxmox 
- 
					
					
					
					
 Und wie sehen die Einstellungen im Adapter aus? 
- 
					
					
					
					
 @thomas-braun 
 com: /dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_1469408ef193eb1180efaa5b3d98b6d1-if00-port0Typ: TI-Z... 
- 
					
					
					
					
 
- 
					
					
					
					
 @hm_krause 
 Die erweiterte PAN-Id sollte anders lauten.
 Kann aber sein, dass dann neugepairt werden muss.
- 
					
					
					
					
 @thomas-braun 
 mit geänerter ID, immer noch:host.iobroker 2021-10-24 12:23:29.249 info Restart adapter system.adapter.zigbee.0 because enabled host.iobroker 2021-10-24 12:23:29.248 error instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION) host.iobroker 2021-10-24 12:23:29.247 error Caught by controller[1]: at processImmediate (internal/timers.js:464:21) host.iobroker 2021-10-24 12:23:29.247 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-24 12:23:29.246 error Caught by controller[1]: at change (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5634:34) host.iobroker 2021-10-24 12:23:29.246 error Caught by controller[1]: at Zigbee.emit (domain.js:475:12) host.iobroker 2021-10-24 12:23:29.246 error Caught by controller[1]: at Zigbee.emit (events.js:412:35) host.iobroker 2021-10-24 12:23:29.245 error Caught by controller[1]: at Developer.onMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/developer.js:46:26) host.iobroker 2021-10-24 12:23:29.245 error Caught by controller[1]: at Developer.sendToZigbee (/opt/iobroker/node_modules/iobroker.zigbee/lib/developer.js:103:49) host.iobroker 2021-10-24 12:23:29.244 error Caught by controller[1]: TypeError: Cannot read property 'getDevice' of undefined host.iobroker 2021-10-24 12:23:29.243 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-24 12:23:28.609 warn Terminated (UNCAUGHT_EXCEPTION): Without reason
- 
					
					
					
					
 @hm_krause 
 Dann fällt mir dazu konkret auch nichts mehr ein.
 Versionen von nodeJS und des Adapters? NodeJS senkrecht installiert?
- 
					
					
					
					
 @thomas-braun said in SONOFF ZigBee 3.0 USB DONGLE PLUS: NodeJS senkrecht installiert? NodeJS senkrecht installiert? 
 ----keine Ahnung----
  
- 
					
					
					
					
 @hm_krause 
 zigbee v 1.6.3
- 
					
					
					
					
 which nodejs node npm && nodejs -v && node -v && npm -v && sudo apt update && apt policy nodejs
- 
					
					
					
					
 @thomas-braun 
 pi@iobroker:~ $ which nodejs node npm && nodejs -v && node -v && npm -v && sudo apt update && apt policy nodejs
 /usr/bin/node
 /usr/bin/npm
- 
					
					
					
					
 sudo ln -s /usr/bin/node /usr/bin/nodejs which nodejs node npm && nodejs -v && node -v && npm -v && sudo apt update && apt policy nodejs
- 
					
					
					
					
 @hm_krause 
 bitte immer alles und in Code Tags angeben, dann sieht das so aus (wenn es richtig ist):jan@Beelink:~$ 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.1 v14.18.1 6.14.15 [sudo] Passwort für jan: OK:1 http://deb.debian.org/debian bullseye InRelease Holen:2 http://deb.debian.org/debian-security bullseye-security InRelease [44,1 kB] Holen:3 http://deb.debian.org/debian bullseye-updates InRelease [39,4 kB] Holen:4 http://deb.debian.org/debian bullseye-backports InRelease [42,1 kB] OK:5 https://deb.nodesource.com/node_14.x bullseye InRelease Es wurden 126 kB in 1 s geholt (100 kB/s). Paketlisten werden gelesen… Fertig Abhängigkeitsbaum wird aufgebaut… Fertig Statusinformationen werden eingelesen… Fertig Alle Pakete sind aktuell. nodejs: Installiert: 14.18.1-deb-1nodesource1 Installationskandidat: 14.18.1-deb-1nodesource1 Versionstabelle: *** 14.18.1-deb-1nodesource1 500 500 https://deb.nodesource.com/node_14.x bullseye/main amd64 Packages 100 /var/lib/dpkg/status 12.22.5~dfsg-2~11u1 500 500 http://deb.debian.org/debian bullseye/main amd64 Packages 500 http://deb.debian.org/debian-security bullseye-security/main amd64 Packages
- 
					
					
					
					
 @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
- 
					
					
					
					
 @jan1 
 ...sorrypi@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
- 
					
					
					
					
 @hm_krause Okay, passst grundsätzlich. Hau die 19 Updates auf das System. 
- 
					
					
					
					
 @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 ...
- 
					
					
					
					
 Reboot gemacht? 
- 
					
					
					
					
 
- 
					
					
					
					
 @hm_krause 
 Dann bin ich raus. Fällt mir nix zu ein.
 
		
	 
		
	 
			
		