NEWS
ZigBee nach Update auf js-controller 5.x tot (gelöst)
-
@thomas-braun sagte in ZigBee nach Update auf js-controller 5.x tot:
pi@iobroker2:~ $ apt policy udev > udev: > Installed: 247.3-7+rpi1+deb11u2 > Candidate: 247.3-7+rpi1+deb11u2 > Version table: > *** 247.3-7+rpi1+deb11u2 500 > 500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages > 100 /var/lib/dpkg/status > 247.3-7+deb11u4 500 > 500 http://deb.debian.org/debian bullseye-proposed-updates/main armhf Packages
pi@iobroker2:~ $ find /dev/serial/by-id -mindepth=1 -maxdepth=1 find: unknown predicate `-mindepth=1'
hat der mir den hold rausgenommen ??? Hab apt update && upgrade gemacht.. vor update
-
@thomas-braun sagte in ZigBee nach Update auf js-controller 5.x tot:
find /dev/serial/by-id -mindepth=1 -maxdepth=1
habe nur noch:
pi@iobroker2:/dev/serial/by-path $ ls platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.3:1.0-port0
-
@reutli sagte in ZigBee nach Update auf js-controller 5.x tot:
hat der mir den hold rausgenommen ??? Hab apt update && upgrade gemacht.. vor update
Du hast die defekte Version am Start.
247.3-7+deb11u4
funktioniert. -
@thomas-braun sagte in ZigBee nach Update auf js-controller 5.x tot:
247.3-7+deb11u4
Hast Du mir einen Tipp?
Die Version die ich bisher hatte:sudo apt install udev=247.3-7+deb11u4 libudev1=247.3-7+deb11u4
tut nicht:
pi@iobroker2:/dev $ sudo apt install udev=247.3-7+deb11u4 libudev1=247.3-7+deb11u4 Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: libfuse2 raspinfo Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: libudev-dev The following packages will be DOWNGRADED: libudev1 udev 0 upgraded, 0 newly installed, 2 downgraded, 1 to remove and 0 not upgraded. Need to get 1,602 kB of archives. After this operation, 573 kB disk space will be freed. Do you want to continue? [Y/n] Y Get:1 http://deb.debian.org/debian bullseye-proposed-updates/main armhf udev armhf 247.3-7+deb11u4 [1,440 kB] Get:2 http://deb.debian.org/debian bullseye-proposed-updates/main armhf libudev1 armhf 247.3-7+deb11u4 [162 kB] Fetched 1,602 kB in 1s (3,173 kB/s) (Reading database ... 113609 files and directories currently installed.) Removing libudev-dev:armhf (247.3-7+rpi1+deb11u2) ... dpkg: warning: downgrading udev from 247.3-7+rpi1+deb11u2 to 247.3-7+deb11u4 (Reading database ... 113534 files and directories currently installed.) Preparing to unpack .../udev_247.3-7+deb11u4_armhf.deb ... Unpacking udev (247.3-7+deb11u4) over (247.3-7+rpi1+deb11u2) ... dpkg: warning: downgrading libudev1:armhf from 247.3-7+rpi1+deb11u2 to 247.3-7+deb11u4 Preparing to unpack .../libudev1_247.3-7+deb11u4_armhf.deb ... Unpacking libudev1:armhf (247.3-7+deb11u4) over (247.3-7+rpi1+deb11u2) ... Setting up libudev1:armhf (247.3-7+deb11u4) ... Setting up udev (247.3-7+deb11u4) ... Processing triggers for libc-bin (2.31-13+rpt2+rpi1+deb11u5) ... Processing triggers for man-db (2.9.4-2) ... Processing triggers for initramfs-tools (0.140) ... pi@iobroker2:/dev $ sudo apt-mark hold udev udev set on hold.
zigbee.0 2023-09-20 18:47:20.364 info Installed Version: iobroker.zigbee@1.8.23 zigbee.0 2023-09-20 18:47:20.328 error Error herdsman start zigbee.0 2023-09-20 18:47:20.326 error Failed to start Zigbee zigbee.0 2023-09-20 18:47:20.325 error Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_74290f152e86ec11b5c6641719c2d21c-if00-port0'" zigbee.0 2023-09-20 18:47:20.304 debug Starting zigbee-herdsman... zigbee.0 2023-09-20 18:47:20.291 info Starting Zigbee npm ... zigbee.0 2023-09-20 18:47:20.289 info Try to reconnect. 1 attempts left zigbee.0 2023-09-20 18:47:10.288 info Installed Version: iobroker.zigbee@1.8.23 zigbee.0 2023-09-20 18:47:10.284 error Error herdsman start zigbee.0 2023-09-20 18:47:10.283 error Failed to start Zigbee zigbee.0 2023-09-20 18:47:10.282 error Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_74290f152e86ec11b5c6641719c2d21c-if00-port0'" zigbee.0 2023-09-20 18:47:09.964 debug Starting zigbee-herdsman... zigbee.0 2023-09-20 18:47:09.956 debug Backup /opt/iobroker/iobroker-data/zigbee_0/backup_2023_09_20-18_47_07.tar.gz success zigbee.0 2023-09-20 18:47:09.881 info Starting Zigbee npm ... zigbee.0 2023-09-20 18:47:07.989 info delete old Backup files. keep only last 10 zigbee.0 2023-09-20 18:47:07.917 debug Using zigbee-herdsman with settings: {"network":{"panID":2698,"extendedPanID":[140,253,145,109,51,197,149,147],"channelList":[20],"networkKey":[1,3,5,171,9,11,13,15,0,2,4,6,8,10,12,13]},"databasePath":"/opt/iobroker/iobroker-data/zigbee_0/shepherd.db","backupPath":"/opt/iobroker/iobroker-data/zigbee_0/nvbackup.json","serialPort":{"baudRate":115200,"rtscts":false,"path":"/dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_74290f152e86ec11b5c6641719c2d21c-if00-port0","adapter":"zstack"},"adapter":{"forceStartWithInconsistentAdapterConfiguration":false}} zigbee.0 2023-09-20 18:47:07.873 info starting. Version 1.8.23 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.17.1, js-controller: 5.0.12 zigbee.0 2023-09-20 18:47:06.531 debug Plugin sentry Initialize Plugin (enabled=true) host.iobroker2 2023-09-20 18:47:02.197 info instance system.adapter.zigbee.0 started with pid 1240 host.iobroker2 2023-09-20 18:47:02.182 info Do not restart adapter system.adapter.zigbee.0 because desired by instance host.iobroker2 2023-09-20 18:47:02.181 info instance system.adapter.zigbee.0 terminated by request of the instance itself and will not be restarted, before user restarts it. zigbee.0 2023-09-20 18:47:01.320 info debug devices set to [] zigbee.0 2023-09-20 18:47:01.311 debug UpdateState: Device is deactivated f0d1b800001d5c46 {"type":"device","common":{"name":"Wiga Bulb 1","type":"AC33906","icon":"img/AC33906.png","color":null,"statusStates":{"onlineId":"zigbee.0.f0d1b800001d5c46.available"},"deactivated":true},"native":{"id":"f0d1b800001d5c46"},"from":"system.adapter.zigbee.0","user":"system.user.admin","ts":1694902559413,"_id":"zigbee.0.f0d1b800001d5c46","acl":{"object":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}} zigbee.0 2023-09-20 18:47:01.310 debug UpdateState: Device is deactivated f0d1b800001d5c46 {"type":"device","common":{"name":"Wiga Bulb 1","type":"AC33906","icon":"img/AC33906.png","color":null,"statusStates":{"onlineId":"zigbee.0.f0d1b800001d5c46.available"},"deactivated":true},"native":{"id":"f0d1b800001d5c46"},"from":"system.adapter.zigbee.0","user":"system.user.admin","ts":1694902559413,"_id":"zigbee.0.f0d1b800001d5c46","acl":{"object":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}} zigbee.0 2023-09-20 18:47:01.244 info terminating zigbee.0 2023-09-20 18:47:01.243 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason zigbee.0 2023-09-20 18:47:01.243 debug Plugin sentry destroyed zigbee.0 2023-09-20 18:47:01.242 info terminating zigbee.0 2023-09-20 18:47:01.241 warn Failed to stop zigbee during
-
Udev bzw das gesamte System neu gestartet?
-
jetzt ja (schäm)
zigbee.0 2023-09-20 18:58:36.854 info debug devices set to [] zigbee.0 2023-09-20 18:58:36.848 info deregister device Ping for deactivated device "0xf0d1b800001d5c46" zigbee.0 2023-09-20 18:58:36.594 info Zigbee started zigbee.0 2023-09-20 18:58:36.593 info 0x84fd27fffec235d4 (addr 41502): TS0044 - TuYa Wireless switch with 4 buttons (EndDevice) zigbee.0 2023-09-20 18:58:36.591 info 0xf0d1b800001d5c46 (addr 57366): AC33906 - LEDVANCE SMART+ spot GU10 multicolor RGBW (Router) zigbee.0 2023-09-20 18:58:36.587 info 0x00124b00251302ed (addr 1205): SNZB-02 - SONOFF Temperature and humidity sensor (EndDevice) zigbee.0 2023-09-20 18:58:36.561 info Currently 3 devices are joined: zigbee.0 2023-09-20 18:58:36.549 info --> transmitPower : normal zigbee.0 2023-09-20 18:58:36.529 info Unable to disable LED, unsupported function. zigbee.0 2023-09-20 18:58:36.520 info Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20221226}} zigbee.0 2023-09-20 18:58:35.787 info Installed Version: iobroker.zigbee@1.8.23 zigbee.0 2023-09-20 18:58:35.424 info Starting Zigbee npm ... zigbee.0 2023-09-20 18:58:35.422 info delete old Backup files. keep only last 10 zigbee.0 2023-09-20 18:58:35.303 info starting. Version 1.8.23 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.17.1, js-controller: 5.0.12 host.iobroker2 2023-09-20 18:58:29.612 info instance system.adapter.zigbee.0 started with pid 1076 host.iobroker2 2023-09-20 18:58:27.505 info instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) zigbee.0 2023-09-20 18:58:26.593 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason zigbee.0 2023-09-20 18:58:26.592 debug Plugin sentry destroyed zigbee.0 2023-09-20 18:58:26.590 info terminating zigbee.0 2023-09-20 18:58:26.269 debug UpdateState: Device is deactivated f0d1b800001d5c46 {"type":"device","common":{"name":"Wiga Bulb 1","type":"AC33906","icon":"img/AC33906.png","color":null,"statusStates":{"onlineId":"zigbee.0.f0d1b800001d5c46.available"},"deactivated":true},"native":{"id":"f0d1b800001d5c46"},"from":"system.adapter.zigbee.0","user":"system.user.admin","ts":1695229090512,"_id":"zigbee.0.f0d1b800001d5c46","acl":{"object":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}} zigbee.0 2023-09-20 18:58:26.267 debug UpdateState: Device is deactivated f0d1b800001d5c46 {"type":"device","common":{"name":"Wiga Bulb 1","type":"AC33906","icon":"img/AC33906.png","color":null,"statusStates":{"onlineId":"zigbee.0.f0d1b800001d5c46.available"},"deactivated":true},"native":{"id":"f0d1b800001d5c46"},"from":"system.adapter.zigbee.0","user":"system.user.admin","ts":1695229090512,"_id":"zigbee.0.f0d1b800001d5c46","acl":{"object":1636,"owner":"system.user.admin","ownerGroup":"system.group.administrator"}}
Aber wie der "hold" rausfliegt ist mir immer noch ein Rätsel!
-
@reutli sagte in ZigBee nach Update auf js-controller 5.x tot:
Aber wie der "hold" rausfliegt ist mir immer noch ein Rätsel!
Kann nur jemand mit root-Rechten getan haben...
-
root Rechte habe ich ja immer (temporär), wenn ich 'sudo' mache, aber doch nicht bei
sudo apt update sudo apt upgrade
oder?
Ich verbriefe mich dafür, dass ich sonst auf PI'chen (nach den Erfahrungen) nicht gemacht habe.
Lasse mich aber gerne überführen! Will schließlich wissen, woran es lag.Was ich gemacht habe:
-
Update master und zwei slaves (siehe oben sudo apt update && sudo apt upgrade)
-
master mit js-controller 5.x versorgt
-
slaves mit js-controller 5.x versorgt
-
-
@reutli sagte in ZigBee nach Update auf js-controller 5.x tot:
aber doch nicht bei
sudo führt immer (wenn nicht mittels Optionen anders verwendet) zum root:
echad@chet:~ $ sudo whoami root echad@chet:~ $
-
@thomas-braun sagte in ZigBee nach Update auf js-controller 5.x tot:
sudo führt immer (wenn nicht mittels Optionen anders verwendet) zum root:
da sind wir uns unstrittig einig!
Dennoch habe ich keinen unhold o.ä. ausgeführt.