Zigbee Adapter Error Send Command failed with no error code
-
@stefan-3 sagte in Zigbee Adapter Error Send Command failed with no error code:
zur Systempflege deutlich mehr gehört als "nur" die ioBroker Adapter, Node JS usw. zu aktualisieren.
Ja, das Betriebssystem gehört da natürlich auch dazu.
Dein jetziges haste offenbar nie angepackt. Aber da ohnehin nur eine Neuinstallation von Raspberry OS 12 sinnvoll ist kannst du das ja dann dort gleich richtig machen. -
@thomas-braun Ja, bei etwas nachdenken ist es natürlich klar, dass das OS auch aktualisiert gehört. Ok, Dank Deiner Anleitung
https://forum.iobroker.net/topic/47213/upgrade-von-debian-10-buster-auf-11-bullseye
hab ich das nun gemacht. Hat etwas gedauert, da ich erst lernen musste, dass man beim Upgrade keine Version auslassen darf 10>12 geht nicht, 10>11>12 schon. Warnings zu Schlüsseln konnte ich eben auch noch bereinigen.
Das Verhalten des Zigbee-Devices ist jedoch unverändert geblieben
Zusatzinfo: Jetziges Ergebnis von iob diag:
Skript v.2023-10-10 *** BASE SYSTEM *** Static hostname: raspberrypi Icon name: computer Operating System: Raspbian GNU/Linux 12 (bookworm) Kernel: Linux 5.10.103-v7+ Architecture: arm Model : Raspberry Pi 3 Model B Rev 1.2 Docker : false Virtualization : none Kernel : armv7l Userland : armhf Systemuptime and Load: 17:26:53 up 12 min, 2 users, load average: 0.49, 0.66, 0.69 CPU threads: 4 *** RASPBERRY THROTTLING *** Current issues: ~ Under-voltage detected ~ Arm frequency capped Previously detected issues: ~ Under-voltage has occurred ~ Arm frequency capping has occurred *** Time and Time Zones *** Local time: Thu 2024-02-29 17:26:54 CET Universal time: Thu 2024-02-29 16:26:54 UTC RTC time: n/a Time zone: Europe/Berlin (CET, +0100) System clock synchronized: yes NTP service: active RTC in local TZ: no *** User and Groups *** pi /home/pi pi adm dialout cdrom sudo audio video plugdev games users input netdev gpio i2c spi iobroker *** X-Server-Setup *** X-Server: false Desktop: Terminal: tty Boot Target: graphical.target *** MEMORY *** total used free shared buff/cache available Mem: 968M 688M 135M 819K 199M 279M Swap: 104M 1.8M 103M Total: 1.1G 689M 238M 923 M total memory 656 M used memory 112 M active memory 628 M inactive memory 128 M free memory 33 M buffer memory 156 M swap cache 99 M total swap 1 M used swap 98 M free swap Raspberry only: oom events: 0 lifetime oom required: 0 Mbytes total time in oom handler: 0 ms max time spent in oom handler: 0 ms *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/root ext4 29G 6.2G 22G 23% / devtmpfs devtmpfs 430M 0 430M 0% /dev tmpfs tmpfs 462M 0 462M 0% /dev/shm tmpfs tmpfs 185M 900K 184M 1% /run tmpfs tmpfs 5.0M 8.0K 5.0M 1% /run/lock /dev/mmcblk0p1 vfat 253M 49M 204M 20% /boot tmpfs tmpfs 93M 0 93M 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Thu Feb 29 17:14:27 2024] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=tty1 root=PARTUUID=738a4d67-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait [Thu Feb 29 17:14:30 2024] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) [Thu Feb 29 17:14:30 2024] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. [Thu Feb 29 17:14:34 2024] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null) Show mounted filesystems \(real ones only\): TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime `-/boot /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,flush,errors=remount-ro Files in neuralgic directories: /var: 840M /var/ 508M /var/cache 502M /var/cache/apt 429M /var/cache/apt/archives 121M /var/log Archived and active journals take up 116.1M in the file system. /opt/iobroker/backups: 342M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 284M /opt/iobroker/iobroker-data/ 154M /opt/iobroker/iobroker-data/files 57M /opt/iobroker/iobroker-data/files/javascript.admin 56M /opt/iobroker/iobroker-data/sonosCache 52M /opt/iobroker/iobroker-data/backup-objects The five largest files in iobroker-data are: 22M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.c05ba1d3.js.map 15M /opt/iobroker/iobroker-data/objects.jsonl 8.5M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.1797d034.js 8.3M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.c05ba1d3.js 7.0M /opt/iobroker/iobroker-data/files/javascript.admin/static/js/675.d0c8b930.chunk.js.map USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/* in your adapter setups, please always prefer the links 'by-id': /dev/serial/by-id/usb-Silicon_Labs_Sonoff_Zigbee_3.0_USB_Dongle_Plus_0001-if00-port0 *** NodeJS-Installation *** /usr/bin/nodejs v18.19.1 /usr/bin/node v18.19.1 /usr/bin/npm 10.2.4 /usr/bin/npx 10.2.4 /usr/bin/corepack 0.22.0 nodejs: Installed: 18.19.1-1nodesource1 Candidate: 18.19.1-1nodesource1 Version table: *** 18.19.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 100 /var/lib/dpkg/status 18.19.0+dfsg-6~deb12u1+rpi1 500 500 http://raspbian.raspberrypi.org/raspbian bookworm/main armhf Packages 18.19.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.18.2-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.18.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.18.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.17.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.17.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.16.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.16.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.15.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.14.2-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.14.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.14.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.13.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.12.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.11.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.10.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.9.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.9.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.8.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.7.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.6.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.5.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.4.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.3.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.2.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.1.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.0.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages Temp directories causing npm8 problem: 0 No problems detected Errors in npm tree: *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Core adapters versions js-controller: 5.0.19 admin: 6.13.16 javascript: 7.8.0 Adapters from github: 0 Adapter State + system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.alexa2.0 : alexa2 : raspberrypi - enabled + system.adapter.backitup.0 : backitup : raspberrypi - enabled + system.adapter.discovery.0 : discovery : raspberrypi - enabled system.adapter.feiertage.0 : feiertage : raspberrypi - enabled + system.adapter.fhem.0 : fhem : raspberrypi - enabled, port: 7072 + system.adapter.history.0 : history : raspberrypi - enabled + system.adapter.iot.0 : iot : raspberrypi - enabled + system.adapter.javascript.0 : javascript : raspberrypi - enabled system.adapter.solarmanpv.0 : solarmanpv : raspberrypi - enabled + system.adapter.sonos.0 : sonos : raspberrypi - enabled system.adapter.vis-materialdesign.0 : vis-materialdesign : raspberrypi - enabled system.adapter.vis.0 : vis : raspberrypi - enabled + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.zigbee.0 : zigbee : raspberrypi - enabled, port: /dev/serial/by-id/usb-Silicon_Labs_Sonoff_Zigbee_3.0_USB_Dongle_Plus_0001-if00-port0 + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.fhem.0 : fhem : raspberrypi - enabled, port: 7072 + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.zigbee.0 : zigbee : raspberrypi - enabled, port: /dev/serial/by-id/usb-Silicon_Labs_Sonoff_Zigbee_3.0_USB_Dongle_Plus_0001-if00-port0 ioBroker-Repositories stable : http://download.iobroker.net/sources-dist.json beta : http://download.iobroker.net/sources-dist-latest.json Active repo(s): stable Installed ioBroker-Instances Used repository: stable Adapter "admin" : 6.13.16 , installed 6.13.16 Adapter "alexa2" : 3.26.4 , installed 3.26.4 Adapter "backitup" : 2.10.11 , installed 2.10.11 Adapter "discovery" : 4.2.0 , installed 4.2.0 Adapter "feiertage" : 1.1.4 , installed 1.1.4 Adapter "fhem" : 2.0.5 , installed 2.0.5 Adapter "history" : 3.0.1 , installed 3.0.1 Adapter "iot" : 2.0.11 , installed 2.0.11 Adapter "javascript" : 7.8.0 , installed 7.8.0 Controller "js-controller": 5.0.19 , installed 5.0.19 Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "socketio" : 6.6.0 , installed 6.6.0 Adapter "solarmanpv" : 0.5.1 , installed 0.5.1 Adapter "sonos" : 3.0.0 , installed 3.0.0 Adapter "vis" : 1.5.4 , installed 1.5.4 Adapter "vis-materialdesign": 0.5.9, installed 0.5.9 Adapter "web" : 6.2.3 , installed 6.2.3 Adapter "ws" : 2.5.10 , installed 2.5.10 Adapter "zigbee" : 1.10.1 , installed 1.10.1 Objects and States Please stand by - This may take a while Objects: 3941 States: 3188 *** OS-Repositories and Updates *** Hit:1 http://raspbian.raspberrypi.org/raspbian bookworm InRelease Hit:2 http://archive.raspberrypi.org/debian bookworm InRelease Hit:3 https://deb.nodesource.com/node_18.x nodistro InRelease Reading package lists... Pending Updates: 0 *** Listening Ports *** Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 11140 520/iobroker.js-con tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 11132 520/iobroker.js-con tcp 0 0 0.0.0.0:8083 0.0.0.0:* LISTEN 999 12841 554/perl tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 10209 530/sshd: /usr/sbin tcp 0 0 0.0.0.0:7072 0.0.0.0:* LISTEN 999 11079 554/perl tcp6 0 0 :::3500 :::* LISTEN 1001 14381 815/io.sonos.0 tcp6 0 0 :::8081 :::* LISTEN 1001 13165 744/io.admin.0 tcp6 0 0 :::8082 :::* LISTEN 1001 14461 860/io.web.0 tcp6 0 0 :::22 :::* LISTEN 0 10211 530/sshd: /usr/sbin udp 0 0 0.0.0.0:44719 0.0.0.0:* 108 12706 392/avahi-daemon: r udp 0 0 0.0.0.0:5353 0.0.0.0:* 108 12704 392/avahi-daemon: r udp6 0 0 :::5353 :::* 108 12705 392/avahi-daemon: r udp6 0 0 :::57324 :::* 108 12707 392/avahi-daemon: r udp6 0 0 fe80::44b6:fd9c:e78:546 :::* 0 11106 485/NetworkManager *** Log File - Last 25 Lines *** 2024-02-29 17:26:34.827 - info: fhem.0 (807) stateChange (out): fhem.0.info.Commands.sendFHEM | set fhem.0.alive on-for-timer 360 > set fhem.0.alive on-for-timer 360 2024-02-29 17:26:53.202 - debug: alexa2.0 (841) Alexa-Remote HTTP2-PUSH: Send Ping 2024-02-29 17:27:36.057 - debug: alexa2.0 (841) Alexa-Remote HTTP2-PUSH: Command PUSH_VOLUME_CHANGE: { "dopplerId": { "deviceSerialNumber": "eadccfe01e7041dfa172440af551a1f1", "deviceType": "A2OSP3UA4VC85F" }, "volumeSetting": 12, "isMuted": false, "destinationUserId": "A2O924TIIYR785" } 2024-02-29 17:27:36.065 - debug: alexa2.0 (841) Alexa-Push-Connection Device Volume change for eadccfe01e7041dfa172440af551a1f1 -> 12/false 2024-02-29 17:27:36.100 - debug: alexa2.0 (841) State changed alexa2.0.Echo-Devices.eadccfe01e7041dfa172440af551a1f1.Player.volume: {"val":12,"ack":true,"ts":1709224056085,"q":0,"from":"system.adapter.alexa2.0","user":"system.user.admin","lc":1707271718009} 2024-02-29 17:27:36.104 - debug: alexa2.0 (841) State changed alexa2.0.Echo-Devices.eadccfe01e7041dfa172440af551a1f1.Player.muted: {"val":false,"ack":true,"ts":1709224056090,"q":0,"from":"system.adapter.alexa2.0","user":"system.user.admin","lc":1698525987675} 2024-02-29 17:29:18.671 - info: admin.0 (744) <== Disconnect system.user.admin from ::ffff:192.168.123.71 2024-02-29 17:29:22.934 - info: admin.0 (744) ==> Connected system.user.admin from ::ffff:192.168.123.71 2024-02-29 17:29:53.203 - debug: alexa2.0 (841) Alexa-Remote HTTP2-PUSH: Send Ping 2024-02-29 17:30:00.416 - info: host.raspberrypi instance system.adapter.solarmanpv.0 started with pid 1381 2024-02-29 17:30:08.241 - info: solarmanpv.0 (1381) starting. Version 0.5.1 in /opt/iobroker/node_modules/iobroker.solarmanpv, node: v18.19.1, js-controller: 5.0.19 2024-02-29 17:30:11.537 - info: solarmanpv.0 (1381) State value to set for "solarmanpv.0.3104772.221753192.DEV_TYP1" has to be type "number" but received type "string" 2024-02-29 17:30:11.660 - info: solarmanpv.0 (1381) State value to set for "solarmanpv.0.3104772.221753192.COMM_PTC_v1" has to be type "string" but received type "number" 2024-02-29 17:30:11.724 - info: solarmanpv.0 (1381) State value to set for "solarmanpv.0.3104772.221753192.HWv1" has to be type "string" but received type "number" 2024-02-29 17:30:12.490 - info: solarmanpv.0 (1381) State value to set for "solarmanpv.0.3104772.221753192.NOP" has to be type "number" but received type "string" 2024-02-29 17:30:13.413 - info: solarmanpv.0 (1381) Terminated (ADAPTER_REQUESTED_TERMINATION): Everything done. Going to terminate till next schedule 2024-02-29 17:30:14.086 - info: host.raspberrypi instance system.adapter.solarmanpv.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) -
@stefan-3 sagte in Zigbee Adapter Error Send Command failed with no error code:
@thomas-braun Ja, bei etwas nachdenken ist es natürlich klar, dass das OS auch aktualisiert gehört. Ok, Dank Deiner Anleitung
https://forum.iobroker.net/topic/47213/upgrade-von-debian-10-buster-auf-11-bullseye
hab ich das nun gemacht. Hat etwas gedauert, da ich erst lernen musste, dass man beim Upgrade keine Version auslassen darf 10>12Wieso Aktualisierung, es wurde doch die einzigrichtige Neuinstallation empfohlen?
-
@meister-mopper Nach dem Hinweis, dass das OS veraltet ist, hab ich mich schlau gemacht wie ich das ändern kann. Dabei bin ich auf die Anleitung von Thomas gestoßen und hab die umgesetzt. Erst nach -aus meiner Sicht- erfolgreicher Umsetzung hab ich Thomas Hinweis gelesen, dass er eine Neuinstallation empfiehlt. Es gibt auch etliche Stimmen im Netz die ein Upgrade einer Neuinstallation klar bevorzugen. Was denn nun? Ist denn der Weg über das Upgrade wirklich so falsch?
-
@stefan-3 sagte in Zigbee Adapter Error Send Command failed with no error code:
Ist denn der Weg über das Upgrade wirklich so falsch?
es ist nicht falsch.. aber wenns dein System steinuralt ist (buster) .. dann JA .neuinstallieren ist besser..
wenn du von einer Version zur anderen gehts dann ... NÖ..
es bleibt jedem selbst überlassen... -
@stefan-3 sagte in Zigbee Adapter Error Send Command failed with no error code:
Was denn nun? Ist denn der Weg über das Upgrade wirklich so falsch?
Im Fall von Bookworm auf einem Raspberry ja.
Bei dir ist das Bootlayout jetzt falsch, es wird der Bullseye-Kernel geladen. Und du bist immer noch auf einem 32Bit-System.
Aus diesen beiden Gründen ist eine Neuinstallation der einzig sinnvolle Weg.Davon abgesehen scheinst du ein Thema mit der Stromversorgung zu haben.
-
@thomas-braun Ok. Vielen Dank für die Rückmeldungen und die Erklärungen. Neuinstallation ist bereits in Arbeit.
-
@thomas-braun Ok, hab nun wie besprochen eine Neuinstallation durchgeführt. Zu meinem Erstaunen kam wieder die Warning
W: http://raspbian.raspberrypi.com/raspbian/dists/bookworm/InRelease: Schlüssel ist im veralteten Schlüsselbund trusted.gpg gespeichert (/etc/apt/trusted.gpg), siehe den Abschnitt MISSBILLIGUNG in apt-key(8) für Details.welche ich mit:
sudo cp /etc/apt/trusted.gpg /etc/apt/trusted.gpg.dbeseitigt habe. Wie auch immer. Das Zigbee Verhalten ist leider unverändert:
Hat jemand Ideen, wie wir das Zigbee-Problem eingrenzen bzw. beheben können?
Zusatzinfo: Jetziges Ergebnis von iob diag:
Skript v.2023-10-10 *** BASE SYSTEM *** Static hostname: raspberrypi Icon name: computer Operating System: Raspbian GNU/Linux 12 (bookworm) Kernel: Linux 6.1.0-rpi8-rpi-v7 Architecture: arm Model : Raspberry Pi 3 Model B Rev 1.2 Docker : false Virtualization : none Kernel : armv7l Userland : armhf Systemuptime and Load: 13:18:00 up 10 min, 2 users, load average: 1.01, 1.50, 1.00 CPU threads: 4 *** RASPBERRY THROTTLING *** Current issues: ~ Under-voltage detected ~ Arm frequency capped Previously detected issues: ~ Under-voltage has occurred ~ Arm frequency capping has occurred *** Time and Time Zones *** Local time: Sat 2024-03-02 13:18:01 CET Universal time: Sat 2024-03-02 12:18:01 UTC RTC time: n/a Time zone: Europe/Berlin (CET, +0100) System clock synchronized: yes NTP service: active RTC in local TZ: no *** User and Groups *** pi /home/pi pi adm dialout cdrom sudo audio video plugdev games users input render netdev gpio i2c spi iobroker *** X-Server-Setup *** X-Server: false Desktop: Terminal: tty Boot Target: multi-user.target *** MEMORY *** total used free shared buff/cache available Mem: 966M 613M 87M 24K 326M 353M Swap: 104M 90M 14M Total: 1.1G 703M 102M 921 M total memory 584 M used memory 473 M active memory 291 M inactive memory 83 M free memory 4 M buffer memory 306 M swap cache 99 M total swap 86 M used swap 13 M free swap Raspberry only: oom events: 0 lifetime oom required: 0 Mbytes total time in oom handler: 0 ms max time spent in oom handler: 0 ms *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION * bthelper@hci0.service loaded failed failed Raspberry Pi bluetooth helper LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type. 1 loaded units listed. *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on udev devtmpfs 328M 0 328M 0% /dev tmpfs tmpfs 93M 1004K 92M 2% /run /dev/mmcblk0p2 ext4 29G 4.1G 24G 15% / tmpfs tmpfs 461M 0 461M 0% /dev/shm tmpfs tmpfs 5.0M 12K 5.0M 1% /run/lock /dev/mmcblk0p1 vfat 510M 93M 418M 19% /boot/firmware tmpfs tmpfs 93M 0 93M 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Sat Mar 2 13:07:34 2024] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty1 root=PARTUUID=e512d429-02 rootfstype=ext4 fsck.repair=yes rootwait [Sat Mar 2 13:07:39 2024] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Quota mode: none. [Sat Mar 2 13:07:42 2024] EXT4-fs (mmcblk0p2): re-mounted. Quota mode: none. Show mounted filesystems \(real ones only\): TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime `-/boot/firmware /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 802M /var/ 409M /var/cache 403M /var/cache/apt 328M /var/cache/apt/archives 181M /var/log/journal/228ff7ae2646439a99e8d4b0a8e6fc59 Archived and active journals take up 180.0M in the file system. /opt/iobroker/backups: 32M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 198M /opt/iobroker/iobroker-data/ 185M /opt/iobroker/iobroker-data/files 57M /opt/iobroker/iobroker-data/files/javascript.admin 43M /opt/iobroker/iobroker-data/files/iot.admin 42M /opt/iobroker/iobroker-data/files/iot.admin/static/js The five largest files in iobroker-data are: 33M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.1797d034.js.map 22M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.c05ba1d3.js.map 11M /opt/iobroker/iobroker-data/objects.jsonl 8.5M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.1797d034.js 8.3M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.c05ba1d3.js USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/* in your adapter setups, please always prefer the links 'by-id': /dev/serial/by-id/usb-Silicon_Labs_Sonoff_Zigbee_3.0_USB_Dongle_Plus_0001-if00-port0 *** NodeJS-Installation *** /usr/bin/nodejs v18.19.1 /usr/bin/node v18.19.1 /usr/bin/npm 10.2.4 /usr/bin/npx 10.2.4 /usr/bin/corepack 0.22.0 nodejs: Installed: 18.19.1-1nodesource1 Candidate: 18.19.1-1nodesource1 Version table: *** 18.19.1-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 100 /var/lib/dpkg/status 18.19.0+dfsg-6~deb12u1+rpi1 500 500 http://raspbian.raspberrypi.com/raspbian bookworm/main armhf Packages 18.19.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.18.2-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.18.1-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.18.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.17.1-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.17.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.16.1-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.16.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.15.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.14.2-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.14.1-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.14.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.13.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.12.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.11.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.10.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.9.1-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.9.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.8.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.7.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.6.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.5.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.4.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.3.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.2.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.1.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.0.0-1nodesource1 600 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages Temp directories causing npm8 problem: 0 No problems detected Errors in npm tree: *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Core adapters versions js-controller: 5.0.19 admin: 6.13.16 javascript: 7.8.0 Adapters from github: 0 Adapter State + system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.alexa2.0 : alexa2 : raspberrypi - enabled + system.adapter.backitup.0 : backitup : raspberrypi - enabled + system.adapter.discovery.0 : discovery : raspberrypi - enabled system.adapter.feiertage.0 : feiertage : raspberrypi - enabled + system.adapter.fhem.0 : fhem : raspberrypi - enabled, port: 7072 + system.adapter.history.0 : history : raspberrypi - enabled + system.adapter.iot.0 : iot : raspberrypi - enabled + system.adapter.javascript.0 : javascript : raspberrypi - enabled system.adapter.solarmanpv.0 : solarmanpv : raspberrypi - enabled + system.adapter.sonos.0 : sonos : raspberrypi - enabled system.adapter.vis-materialdesign.0 : vis-materialdesign : raspberrypi - disabled system.adapter.vis.0 : vis : raspberrypi - enabled + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.zigbee.0 : zigbee : raspberrypi - enabled, port: /dev/serial/by-id/usb-Silicon_Labs_Sonoff_Zigbee_3.0_USB_Dongle_Plus_0001-if00-port0 + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.fhem.0 : fhem : raspberrypi - enabled, port: 7072 + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.zigbee.0 : zigbee : raspberrypi - enabled, port: /dev/serial/by-id/usb-Silicon_Labs_Sonoff_Zigbee_3.0_USB_Dongle_Plus_0001-if00-port0 ioBroker-Repositories stable : http://download.iobroker.net/sources-dist.json beta : http://download.iobroker.net/sources-dist-latest.json Active repo(s): stable Installed ioBroker-Instances Used repository: stable Adapter "admin" : 6.13.16 , installed 6.13.16 Adapter "alexa2" : 3.26.4 , installed 3.26.4 Adapter "backitup" : 2.10.11 , installed 2.10.11 Adapter "discovery" : 4.2.0 , installed 4.2.0 Adapter "feiertage" : 1.1.4 , installed 1.1.4 Adapter "fhem" : 2.0.5 , installed 2.0.5 Adapter "history" : 3.0.1 , installed 3.0.1 Adapter "iot" : 2.0.11 , installed 2.0.11 Adapter "javascript" : 7.8.0 , installed 7.8.0 Controller "js-controller": 5.0.19 , installed 5.0.19 Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "socketio" : 6.6.0 , installed 6.6.0 Adapter "solarmanpv" : 0.5.1 , installed 0.5.1 Adapter "sonos" : 3.0.0 , installed 3.0.0 Adapter "vis" : 1.5.4 , installed 1.5.4 Adapter "vis-materialdesign": 0.5.9, installed 0.5.9 Adapter "web" : 6.2.3 , installed 6.2.3 Adapter "ws" : 2.5.10 , installed 2.5.10 Adapter "zigbee" : 1.10.1 , installed 1.10.1 Objects and States Please stand by - This may take a while Objects: 3677 States: 2942 *** OS-Repositories and Updates *** Hit:1 http://raspbian.raspberrypi.com/raspbian bookworm InRelease Hit:2 http://archive.raspberrypi.com/debian bookworm InRelease Hit:3 https://deb.nodesource.com/node_18.x nodistro InRelease Reading package lists... Pending Updates: 0 *** Listening Ports *** Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 0.0.0.0:8083 0.0.0.0:* LISTEN 999 15452 720/perl tcp 0 0 0.0.0.0:7072 0.0.0.0:* LISTEN 999 12272 720/perl tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 13962 617/iobroker.js-con tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 13969 617/iobroker.js-con tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 15376 646/sshd: /usr/sbin tcp6 0 0 :::8082 :::* LISTEN 1001 14270 919/io.web.0 tcp6 0 0 :::8081 :::* LISTEN 1001 14062 739/io.admin.0 tcp6 0 0 :::3500 :::* LISTEN 1001 15671 820/io.sonos.0 tcp6 0 0 :::22 :::* LISTEN 0 15378 646/sshd: /usr/sbin udp 0 0 0.0.0.0:49197 0.0.0.0:* 104 13736 474/avahi-daemon: r udp 0 0 0.0.0.0:5353 0.0.0.0:* 104 13734 474/avahi-daemon: r udp6 0 0 fe80::69a4:1255:6fd:546 :::* 0 15445 552/NetworkManager udp6 0 0 :::54321 :::* 104 13737 474/avahi-daemon: r udp6 0 0 :::5353 :::* 104 13735 474/avahi-daemon: r *** Log File - Last 25 Lines *** 2024-03-02 13:10:29.820 - info: alexa2.0 (790) Subscribing to states... 2024-03-02 13:10:33.369 - info: alexa2.0 (790) Alexa-Push-Connection (macDms = true) established. Disable Polling 2024-03-02 13:10:49.106 - info: alexa2.0 (790) Initialization Done ... 2024-03-02 13:12:00.112 - info: host.raspberrypi instance system.adapter.solarmanpv.0 started with pid 1052 2024-03-02 13:12:06.847 - info: solarmanpv.0 (1052) starting. Version 0.5.1 in /opt/iobroker/node_modules/iobroker.solarmanpv, node: v18.19.1, js-controller: 5.0.19 2024-03-02 13:12:11.677 - info: solarmanpv.0 (1052) State value to set for "solarmanpv.0.3104772.221753192.DEV_TYP1" has to be type "number" but received type "string" 2024-03-02 13:12:11.776 - info: solarmanpv.0 (1052) State value to set for "solarmanpv.0.3104772.221753192.COMM_PTC_v1" has to be type "string" but received type "number" 2024-03-02 13:12:11.840 - info: solarmanpv.0 (1052) State value to set for "solarmanpv.0.3104772.221753192.HWv1" has to be type "string" but received type "number" 2024-03-02 13:12:12.441 - info: solarmanpv.0 (1052) State value to set for "solarmanpv.0.3104772.221753192.NOP" has to be type "number" but received type "string" 2024-03-02 13:12:13.299 - info: solarmanpv.0 (1052) Terminated (ADAPTER_REQUESTED_TERMINATION): Everything done. Going to terminate till next schedule 2024-03-02 13:12:13.885 - info: host.raspberrypi instance system.adapter.solarmanpv.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2024-03-02 13:14:22.112 - info: fhem.0 (805) stateChange (out): fhem.0.info.Commands.sendFHEM | set fhem.0.alive on-for-timer 360 > set fhem.0.alive on-for-timer 360 2024-03-02 13:16:50.479 - warn: sonos.0 (820) State "sonos.0.root.192_168_123_29.queue_html" has no existing object, this might lead to an error in future versions 2024-03-02 13:18:00.131 - info: host.raspberrypi instance system.adapter.solarmanpv.0 started with pid 1852 2024-03-02 13:18:07.654 - info: solarmanpv.0 (1852) starting. Version 0.5.1 in /opt/iobroker/node_modules/iobroker.solarmanpv, node: v18.19.1, js-controller: 5.0.19 2024-03-02 13:18:11.914 - info: solarmanpv.0 (1852) State value to set for "solarmanpv.0.3104772.221753192.DEV_TYP1" has to be type "number" but received type "string" 2024-03-02 13:18:12.023 - info: solarmanpv.0 (1852) State value to set for "solarmanpv.0.3104772.221753192.COMM_PTC_v1" has to be type "string" but received type "number" 2024-03-02 13:18:12.117 - info: solarmanpv.0 (1852) State value to set for "solarmanpv.0.3104772.221753192.HWv1" has to be type "string" but received type "number" 2024-03-02 13:18:12.871 - info: solarmanpv.0 (1852) State value to set for "solarmanpv.0.3104772.221753192.NOP" has to be type "number" but received type "string" 2024-03-02 13:18:13.794 - info: solarmanpv.0 (1852) Terminated (ADAPTER_REQUESTED_TERMINATION): Everything done. Going to terminate till next schedule 2024-03-02 13:18:14.430 - info: host.raspberrypi instance system.adapter.solarmanpv.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2024-03-02 13:19:22.113 - info: fhem.0 (805) stateChange (out): fhem.0.info.Commands.sendFHEM | set fhem.0.alive on-for-timer 360 > set fhem.0.alive on-for-timer 360 -
@stefan-3 Die Raspi3 Versorgung hab ich übrigens auch überprüft: USB Kabel um ca. 50cm gekürzt und dann an der Lötstelle gemessen: +4,95V, von der USB Spec +5V-5%=+4,75V also deutlich entfernt, selbst wenn dann noch einige mV über das restliche Kabel und den Pi3 USB Stecker abfallen.
-
@stefan-3 Der Raspi ist halt empfindlich und möchte gerne 5-5,1V um stabil zu laufen. Du bist unter 5V, also reicht ihm das halt nicht immer.
Die originalen Netzteile liefern bei ihrer maximalen Belastbarkeit immer noch 5V.Gruss, Jürgen
-
Warum hast du denn da noch eine 32bit-Installation laufen? Ich hatte ja bei Neuinstallation auch direkt 64bit genommen.
-
@thomas-braun Ich versuche das ganze Wochenende schon Debian V12 64Bit auf dem Raspi3 zu installieren, habe aber Schwierigkeiten mit den Schlüsseln. Bei der iob Installation wird gemeldet:
pi@raspberrypi:~ $ curl -sSLf https://iobroker.net/install.sh | bash - library: loaded Library version=2024-01-04 ========================================================================== Welcome to the ioBroker installer! Installer version: 2024-01-04 You might need to enter your password a couple of times. ========================================================================== ========================================================================== Installing prerequisites (1/4) ========================================================================== Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://deb.debian.org/debian-security bookworm-security InRelease Hit:3 http://deb.debian.org/debian bookworm-updates InRelease Hit:4 http://archive.raspberrypi.com/debian bookworm InRelease Err:4 http://archive.raspberrypi.com/debian bookworm InRelease The following signatures couldn't be verified because the public key is not av ailable: NO_PUBKEY 82B129927FA3303E Reading package lists... Done W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://archive.raspberrypi.com/debian bookworm InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 82B129927FA3303E W: Failed to fetch http://archive.raspberrypi.com/debian/dists/bookworm/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 82B129927FA3303E W: Some index files failed to download. They have been ignored, or old ones used instead.Und bei der FHEM Installation ähnlich:
pi@raspberrypi:~ $ sudo wget -qO - https://debian.fhem.de/archive.key | apt-key add - Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)). E: This command can only be used by root. pi@raspberrypi:~ $ sudo echo "deb http://debian.fhem.de/nightly/ /" >> /etc/apt/sources.list -bash: /etc/apt/sources.list: Permission denied pi@raspberrypi:~ $ sudo apt update Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://deb.debian.org/debian-security bookworm-security InRelease Get:3 http://deb.debian.org/debian bookworm-updates InRelease [55.4 kB] Hit:4 https://deb.nodesource.com/node_18.x nodistro InRelease Hit:5 http://archive.raspberrypi.com/debian bookworm InRelease Err:5 http://archive.raspberrypi.com/debian bookworm InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 82B129927FA3303E Fetched 55.4 kB in 3s (21.0 kB/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://archive.raspberrypi.com/debian bookworm InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 82B129927FA3303E W: Failed to fetch http://archive.raspberrypi.com/debian/dists/bookworm/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 82B129927FA3303E W: Some index files failed to download. They have been ignored, or old ones used instead. pi@raspberrypi:~ $ sudo apt install fhem Reading package lists... Done Building dependency tree... Done Reading state information... Done fhem is already the newest version (6.0.). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. -
Der key für debian muss bei einer Installation gleich mitkommen.
Und bei fhem wird das alte Verfahren via apt-key verwendet. Geht aber auf einem Bookworm nicht mehr.
Warum verwendest du keine aktuelle Anleitung? Da ist es richtig: -
@thomas-braun a) Zu "Der key ... muss gleich mitkommen": Ich hab das Image über Raspberry Pi Imager aufgespielt. Und dennoch erhalte ich bei der iob Installation die Fehlermeldung. Ich weiß ehrlich gesagt nicht, was ich da hätte anders machen sollen.
b) Zu "aktuelle FHEM Anleitung": Dass apt-key mit Bookworm nicht mehr geht, war mir nicht bewusst. Die Seite https://debian.fhem.de/ habe ich sehr wohl ausprobiert. Die FHEM Installation mittels apt funktioniert jedoch nicht. Ergebnis:pi@raspberrypi:~ $ wget -O- https://debian.fhem.de/archive.key | gpg --dearmor | sudo tee /usr/share/keyrings/debianfhemde-archive-keyring.gpg --2024-03-04 22:39:16-- https://debian.fhem.de/archive.key Resolving debian.fhem.de (debian.fhem.de)... 2600:9000:21f3:d200:15:107d:a980:93 a1, 2600:9000:21f3:ce00:15:107d:a980:93a1, 2600:9000:21f3:8600:15:107d:a980:93a1 , ... Connecting to debian.fhem.de (debian.fhem.de)|2600:9000:21f3:d200:15:107d:a980:9 3a1|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 2428 (2.4K) [application/pgp-keys] Saving to: ‘STDOUT’ - 100%[===================>] 2.37K --.-KB/s in 0.001s 2024-03-04 22:39:16 (4.07 MB/s) - written to stdout [2428/2428] ▒▒e<▒ ▒p▒aWT▒-▒▒▒T▒v1▒yq▒RG▒▒▒▒}▒▒▒#1/Z▒▒W▒s▒f\▒▒Q▒;▒Z▒z8W▒▒y▒S,x▒+▒Y ZG ▒▒▒^▒▒ut▒B▒▒H%▒▒▒`J]b▒h▒WU*6▒▒▒▒"▒*▒Sx▒▒}#▒G▒▒o+▒ڎ▒▒s▒ϼ▒▒Ò▒▒6▒O▒0▒$▒▒V0▒▒▒▒F▒N#▒ u▒▒▒▒▒▒▒▒D*0.▒M▒▒A▒▒▒%▒▒ ▒a▒B?▒▒▒.| ▒▒ؙO▒▒ѺR▒▒▒xd▒}▒OY▒▒LϚ▒s▒̵̗▒(▒▒▒▒▒▒ѭW▒\v▒^▒▒▒W>▒ۥ▒H▒▒lD9i▒.$▒_▒▒~K?▒6N▒ ▒▒M4c▒#▒▒k▒▒>▒%▒▒▒k▒▒5▒ZU1sE▒▒Jc'+▒ betateilchen▒▒ >!1▒▒H▒Y▒▒/▒▒F▒▒q0Ie<▒ g ▒ ▒F▒▒q0I▒▒ ▒c▒▒F▒oC9▒ϲ▒B▒▒M;▒▒▒K▒3▒-Ro▒/!▒▒lv▒▒#,*a`J▒▒▒Y~9=-~▒u▒m֛▒▒ >uR▒W▒▒q▒Q▒▒Iv▒՝zw,rVi▒!➼▒▒m<▒▒`2▒▒▒e ▒`▒M▒▒]▒▒q▒ۧ▒"▒w`.0▒o@▒wF▒2n▒a▒S▒P▒)▒rq▒▒▒1 K9▒V▒ã6o▒▒S▒I ▒▒\▒>u▒#▒&-▒ئ▒▒EB▒ ▒:▒▒s▒pb ▒L▒.▒+▒;ڥ▒▒p▒9▒▒▒▒c.▒▒?▒e▒▒k▒▒9O▒▒%5Y▒"P▒k.▒.▒▒=▒k▒▒▒m9▒▒6▒.▒=▒g▒▒j#T▒B▒▒▒R I▒۴<(0▒[▒y<Y▒▒"▒RJ▒▒/Hd▒▒▒Zӕ▒T▒▒e<▒ ▒▒▒▒▒▒b▒▒ ▒▒F▒▒by▒▒h▒8▒▒m▒EaJ▒▒ȁ▒▒Ǐ▒▒▒▒▒ӣ5▒fY▒`▒,9▒▒X{▒▒z▒CU▒▒▒6▒▒x1▒o▒_u9▒▒▒▒?▒& ▒W▒▒y▒P▒▒H▒▒ܺ▒▒v$k▒▒▒p,n~▒#▒▒`Ɠϳf▒F2Vm▒$]_I▒▒▒▒M▒$▒jw▒▒▒n YYfׅ▒g▒▒▒▒Q▒▒s▒▒4▒▒vY▒▒v▒ k▒▒c?▒▒b0▒j▒=n▒▒'▒▒=▒▒▒▒▒=g▒p▒&Ў*▒fl߭▒B/k=▒g l▒ֲF▒$▒▒▒▒▒▒zB{▒▒6▒,^▒▒gM▒5▒w▒▒z▒z▒▒`▒ ▒U+Kom▒▒ &!1▒▒H▒Y▒▒/▒▒F▒▒q0Ie<▒ g ▒F▒▒q0Iw4 ▒9▒d▒Ox▒▒▒y▒▒ ▒▒S▒▒<y▒G▒▒▒▒KV▒{▒;▒▒\▒▒!▒q[▒[n▒▒JM|X64jJ▒V▒_;0▒▒5 ▒*Z d'▒i1`▒;8f i▒aH8▒|/+▒▒▒R▒▒,▒s▒i|M▒▒&▒▒bl▒ǀ+h% ▒b▒▒▒$▒N:<▒'▒/▒ۅ▒▒\`▒B=▒4▒7▒^9▒6)▒▒%Bo&▒▒N▒[: ▒▒+▒t▒"+¶▒sӉ▒W (▒%Z▒▒▒b▒▒▒H▒s▒H3/▒▒ ▒b▒▒qI▒6u▒K▒X p▒9lC▒Q˯▒p▒▒▒▒▒▒|▒▒▒^#▒▒▒▒▒▒P▒ש▒▒ɨ▒ͥb#▒+▒A▒ ▒Ҽ▒▒۹▒=▒?▒d:▒▒B▒H▒▒▒▒`cF3▒}▒,jpi@rasp pi@raspberrypi:~ $ PuTTYPuTTYPuTTYPuTTYPuTTYPuTTYPuTTYPuTTYPuTTYPuTTYDie manuelle FHEM Installation funktioniert hingegen.
sudo apt -y install perl-base libdevice-serialport-perl libwww-perl libio-socket-ssl-perl libcgi-pm-perl libjson-perl sqlite3 libdbd-sqlite3-perl libtext-diff-perl libtimedate-perl libmail-imapclient-perl libgd-graph-perl libtext-csv-perl libxml-simple-perl liblist-moreutils-perl fonts-liberation libimage-librsvg-perl libgd-text-perl libsocket6-perl libio-socket-inet6-perl libmime-base64-perl libimage-info-perl libusb-1.0-0-dev libnet-server-perl libreadonly-perl sudo apt -y install libdate-manip-perl libhtml-treebuilder-xpath-perl libmojolicious-perl libxml-bare-perl libauthen-oath-perl libconvert-base32-perl libmodule-pluggable-perl libnet-bonjour-perl libcrypt-urandom-perl nodejs npm libnet-dbus-perl wget http://fhem.de/fhem-6.3.deb sudo dpkg -i fhem-6.3.debOk, somit wäre die FHEM Installation gelöst, gleichwohl ich nicht verstehe, warum es mit dem key-Befehl nicht geht. Die Ausgabe auf STDOUT=Bildschirm ist doch Quatsch, oder? Aber wohin soll der key?
Wenn ich hingegen iob versuche zu installieren, meckert er wegen den Schlüsseln und bleibt bei der Installation bei Schritt 3/4 hängen (keine Fehlermeldung, nichts, nach 20 Minuten immernoch nichts). Hilft nur noch hart ausschalten. Danach geht die Installation etwas weiter, bleibt aber dann bei einem späteren Installationspunkt hängen. Im dritten Anlauf geht die Installationsroutine dann durch. Eine vertrauenswürdige Installation sieht aber anders aus. -
Zu a): Ist so... Keine Ahnung was du da wie installiert hast.
Zu b):Nachdem ich der Anleitung gefolgt bin:
thomas@roamer:~$ apt policy fhem fhem: Installiert: (keine) Installationskandidat: 6.3.28591 Versionstabelle: 6.3.28591 500 500 https://debian.fhem.de/nightly Packages 6.2.28436 500 500 https://debian.fhem.de/nightly PackagesLeg das ordentlich über das Repo an und nicht am Paketmanager vorbei:
wget -O- https://debian.fhem.de/archive.key | gpg --dearmor | sudo tee /usr/share/keyrings/debianfhemde-archive-keyring.gpg > /dev/null echo "deb [signed-by=/usr/share/keyrings/debianfhemde-archive-keyring.gpg] https://debian.fhem.de/nightly/ /" | sudo tee /etc/apt/sources.list.d/fhem.list sudo apt update sudo apt install fhem -
@stefan-3 sagte in Zigbee Adapter Error Send Command failed with no error code:
Hilft nur noch hart ausschalten.
Strg-C ist dein Freund... Oder Strg-Alt-Entfernen...
Oder der Linux-Affengriff...Aber NIE, NIE, NIE einfach per Stromexekution wegknallen.
-
Leg das ordentlich über das Repo an
Das hatte ich ja probiert, aber bereits bei
wget -O- https://debian.fhem.de/archive.key | gpg --dearmor | sudo tee /usr/share/keyrings/debianfhemde-archive-keyring.gpgwird nur Schrott am Bildschirm ausgegeben und das spätere "apt install fhem" schlägt dann fehl. Ich kann heute Abend aber gerne die komplette Abfolge posten.
-
@stefan-3 sagte in Zigbee Adapter Error Send Command failed with no error code:
wird nur Schrott am Bildschirm ausgegeben
Das ist kein Schrott, das ist der entpackte key...
Ich hatte dir aber oben Befehle gegeben, die das sauberer darstellen. -
@thomas-braun Ok, ich stelle eben fest, dass Du die Installationsanleitung von https://debian.fhem.de/ abgewandelt hast, so dass der Schlüssel nicht mehr auf dem Bildschirm ausgegeben wird. Also nochmal komplett von Null. Raspi Imager Screenshots. Zur Info: Bei Modell auswählen = Raspi 3 wird Bookworm nicht angezeigt, sondern nur Bullseye 32 oder 64bit. Ich lasse Modell daher frei, um Bookworm überhaupt auswählen zu können:
Dann
sudo apt update && sudo apt full-upgrade sudo rebootDanach die FEHM Installation:
pi@raspberrypi:~ $ wget -O- https://debian.fhem.de/archive.key | gpg --dearmor | sudo tee /usr/share/keyrings/debianfhemde-archive-keyring.gpg > /dev/null --2024-03-06 23:15:31-- https://debian.fhem.de/archive.key Resolving debian.fhem.de (debian.fhem.de)... 2600:9000:21f3:1c00:15:107d:a980:93a1, 2600:9000:21f3:8200:15:107d:a980:93a1, 2600:9000:21f3:e200:15:107d:a980:93a1, ... Connecting to debian.fhem.de (debian.fhem.de)|2600:9000:21f3:1c00:15:107d:a980:93a1|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 2428 (2.4K) [application/pgp-keys] Saving to: ‘STDOUT’ - 100%[====================================================================================================>] 2.37K --.-KB/s in 0s 2024-03-06 23:15:31 (41.2 MB/s) - written to stdout [2428/2428] pi@raspberrypi:~ $ echo "deb [signed-by=/usr/share/keyrings/debianfhemde-archive-keyring.gpg] https://debian.fhem.de/nightly/ /" | tee /etc/apt/sources.list.d/fhem.list tee: /etc/apt/sources.list.d/fhem.list: Permission denied deb [signed-by=/usr/share/keyrings/debianfhemde-archive-keyring.gpg] https://debian.fhem.de/nightly/ / pi@raspberrypi:~ $ sudo apt update Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://deb.debian.org/debian-security bookworm-security InRelease Hit:3 http://deb.debian.org/debian bookworm-updates InRelease Hit:4 http://archive.raspberrypi.com/debian bookworm InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. pi@raspberrypi:~ $ sudo apt install fhem Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Unable to locate package fhem -
Da war noch ein Fehlerchen drin.
echo "deb [signed-by=/usr/share/keyrings/debianfhemde-archive-keyring.gpg] https://debian.fhem.de/nightly/ /" | sudo tee /etc/apt/sources.list.d/fhem.list sudo apt update sudo apt install fhemsollte funktionieren.
