Ständiger Client-Verlust im Zigbee-Netzwerk
-
======================= SUMMARY ======================= v.2023-04-16 Operatingsystem: Raspbian GNU/Linux 11 (bullseye) Kernel: 6.1.21-v8+ Installation: Native Timezone: Europe/Berlin (CEST, +0200) User-ID: 1000 X-Server: true Boot Target: graphical.target Pending OS-Updates: 0 Pending iob updates: 0 Nodejs-Installation: /usr/bin/nodejs v16.20.0 /usr/bin/node v16.20.0 /usr/bin/npm 8.19.4 /usr/bin/npx 8.19.4 Recommended versions are nodejs 18.x.y and npm 9.x.y Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 3.8G 1.6G 1.5G 46M 707M 2.5G Swap: 99M 0B 99M Total: 3.9G 1.6G 1.6G Active iob-Instances: 27 Active repo(s): stable ioBroker Core: js-controller 4.0.24 admin 6.3.5 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: + system.adapter.admin.0 : admin : pimaster - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin + system.adapter.web.0 : web : pimaster - enabled, port: 8082, bind: 10.1.1.159, run as: admin Objects: 12193 States: 8995 Size of iob-Database: 29M /opt/iobroker/iobroker-data/objects.jsonl 19M /opt/iobroker/iobroker-data/states.jsonl =================== END OF SUMMARY ==================== -
@puls200 kein Vorwurf nur eine Festellung:
warum hast Du bei der Neuinstallation nicht gleich die empfohlene (akktuelle) NodeJS Version installiert und warum wieder mit Desktop?
Desktop frisst Ressoursen und ist absolut unnötig
-
Du hast recht... ich habe vergessen, die 6 mit der 8 auszutauschen. Hiermit würde ich upgraden, oder?
sudo n 18.16.0Naja und warum wieder mit Deskop? Schon immer greife ich per VNC von meinem Handy oder PC auf den Rasp zu. Ich bin ein nativer Windows-Nutzer und brauche den Desktop. Schon allein eine Datei auf dem Rasp über die Konsole zu verschieben ist zu viel für mich. Da ich mehrere Kameras nutze und diese Bilder ablegen, muss ich manchmal mit dem Dateimanager arbeiten. Unvorstellbar, dass alles über die Konsole zu machen.
-
@puls200 sagte in Ständiger Client-Verlust im Zigbee-Netzwerk:
Hiermit würde ich upgraden, oder?
https://forum.iobroker.net/topic/64032/update-nodejs-best-practise-supported-16-und-18
Diese Anleitung bitte benutzen.
-
@puls200 sagte in Ständiger Client-Verlust im Zigbee-Netzwerk:
Hiermit würde ich upgraden, oder?
Nein, nein, nein! Wie kommt man immer auf
n?
Damit zerlegt ihr die Installation.
Das Herumgefummel mit n erklärt auchNode.js ist absolut falsch installiert... keine Ahnung, wieso, weshalb, warum...
Nämlich genau deswegen.
Und es verbietet sich per VNC auf einen Desktop bei einem Server zuzugreifen. Beschäftige dich mit den 5 Befehlen die man für die Navigation per Kommandozeile durch das Dateisystem braucht.
-
@puls200 sagte in Ständiger Client-Verlust im Zigbee-Netzwerk:
Schon allein eine Datei auf dem Rasp über die Konsole zu verschieben ist zu viel für mich.
mv /pfad/zur/quelle /pfad/zum/zielSchneller und präziser als jedes Mausgeschubse.
Und natürlich Ressourcenfreundlich. -
@thomas-braun OK, habe nun gemäß Deiner Anleitung auf v18.6.0 aktualisiert. Vielen Dank! Problem ist, dass man im Netz sehr, sehr viele Threads oder Infos über zu nutzende Kommandos gibt. Für mich als Laie ist es schwer, "gute" von "bösen" Befehlen zu unterscheiden.
Wenn ich meinen ioBroker komplett neu aufsetze, werde ich mal auf VNC verzichten und nur über SSH den Rasp bedienen oder es zumindest versuchen.
-
Moin!
Ich wollte abschliessend Euch nur mitteilen, dass seit der Installation einer sauberen ioBroker-Installation (mit korrekt-installierten Node.js) alle Clients angezeigt werden und es zu keinem Verbindungsabbruch mehr kommt.
Ich hätte nicht gedacht, dass ein falscher Ordner zu so grossen Problemen führen kann.
Vielen besten Dank an Euch und vor Allem an @Thomas-Braun !!!
Gruss
Puls -
@puls200
kann dir zum Dateiaustausch den bitvise ssh client empfehlen, ist ähnlich wie filezilla zu bedienen. (habe früher immer aufwändig smb fileshare auf dem Pi eingerichtet, seit bitvise nicht mehr).
Gruß AxLED -
ich muss mich anschließen mein Zigbee Modul bringt nach ca 30min immer die Fehlermeldung " You need save and run adapter before pairing!".
ich habe den https://www.amazon.de/dp/B09M475L3R?psc=1&ref=ppx_yo2ov_dt_b_product_details Stick genommen
mein System hab ich auch komplett neu aufgesetzt da ich noch auf Buster war ( hab auch mal eine neue SD Karte genommen da die alte 5 jahre plus alt war )
iob diag sagt
Skript v.2023-04-16 *** BASE SYSTEM *** Model : Raspberry Pi 4 Model B Rev 1.4 Architecture : aarch64 Docker : false Virtualization : none Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye PRETTY_NAME="Debian GNU/Linux 11 (bullseye)" NAME="Debian GNU/Linux" VERSION_ID="11" VERSION="11 (bullseye)" VERSION_CODENAME=bullseye ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" Systemuptime and Load: 21:54:38 up 1 min, 3 users, load average: 3.16, 1.49, 0.56 CPU threads: 4 Raspberry only: throttled=0x0 Other values than 0x0 hint to temperature/voltage problems temp=46.2'C volt=0.9060V *** Time and Time Zones *** Local time: Sat 2023-06-03 21:54:38 CEST Universal time: Sat 2023-06-03 19:54:38 UTC RTC time: n/a Time zone: Europe/Berlin (CEST, +0200) System clock synchronized: yes NTP service: active RTC in local TZ: no *** User and Groups *** leovandavart /home/leovandavart leovandavart adm dialout cdrom sudo audio video plugdev games users input render netdev lpadmin gpio i2c spi iobroker *** X-Server-Setup *** X-Server: true Desktop: Terminal: tty Boot Target: graphical.target *** MEMORY *** total used free shared buff/cache available Mem: 7.8G 1.2G 5.6G 113M 1.0G 6.4G Swap: 99M 0B 99M Total: 7.9G 1.2G 5.7G 7812 M total memory 1169 M used memory 1528 M active memory 403 M inactive memory 5635 M free memory 46 M buffer memory 962 M swap cache 99 M total swap 0 M used swap 99 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 *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/root ext4 29G 7.5G 21G 27% / devtmpfs devtmpfs 3.6G 0 3.6G 0% /dev tmpfs tmpfs 3.9G 5.4M 3.9G 1% /dev/shm tmpfs tmpfs 1.6G 1.2M 1.6G 1% /run tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock /dev/mmcblk0p1 vfat 255M 31M 225M 13% /boot tmpfs tmpfs 782M 20K 782M 1% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Sat Jun 3 21:53:02 2023] 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 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=E4:5F:01:24:3A:AD vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty1 root=PARTUUID=082d92cc-02 rootfstype=ext4 fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles [Sat Jun 3 21:53:03 2023] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Quota mode: none. [Sat Jun 3 21:53:03 2023] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. [Sat Jun 3 21:53:05 2023] EXT4-fs (mmcblk0p2): re-mounted. Quota mode: none. 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,errors=remount-ro Files in neuralgic directories: /var: 694M /var/ 297M /var/cache 285M /var/cache/apt 185M /var/lib 184M /var/cache/apt/archives Archived and active journals take up 88.0M in the file system. /opt/iobroker/backups: 16M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 263M /opt/iobroker/iobroker-data/ 225M /opt/iobroker/iobroker-data/files 51M /opt/iobroker/iobroker-data/files/javascript.admin 48M /opt/iobroker/iobroker-data/files/telegram.admin 42M /opt/iobroker/iobroker-data/files/devices.admin The five largest files in iobroker-data are: 33M /opt/iobroker/iobroker-data/files/devices.admin/static/js/main.10538062.js.map 15M /opt/iobroker/iobroker-data/objects.jsonl 15M /opt/iobroker/iobroker-data/files/telegram.admin/rules/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_d_ts-node_modules_io-1d9f06.44fe4a3f.chunk.js.map 8.2M /opt/iobroker/iobroker-data/files/devices.admin/static/js/main.10538062.js 7.2M /opt/iobroker/iobroker-data/files/telegram.admin/rules/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_d_ts-node_modules_io-1d9f06.44fe4a3f.chunk.js *** NodeJS-Installation *** /usr/bin/nodejs v18.16.0 /usr/bin/node v18.16.0 /usr/bin/npm 9.5.1 /usr/bin/npx 9.5.1 nodejs: Installed: 18.16.0-deb-1nodesource1 Candidate: 18.16.0-deb-1nodesource1 Version table: *** 18.16.0-deb-1nodesource1 500 500 https://deb.nodesource.com/node_18.x bullseye/main arm64 Packages 100 /var/lib/dpkg/status 12.22.12~dfsg-1~deb11u4 500 500 http://security.debian.org/debian-security bullseye-security/main arm64 Packages 12.22.12~dfsg-1~deb11u3 500 500 http://deb.debian.org/debian bullseye/main arm64 Packages Temp directories causing npm8 problem: 0 No problems detected *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl MULTIHOSTSERVICE/enabled: false Core adapters versions js-controller: 4.0.24 admin: 6.3.5 javascript: 6.1.4 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.backitup.0 : backitup : raspberrypi - enabled + system.adapter.discovery.0 : discovery : raspberrypi - enabled system.adapter.habpanel.0 : habpanel : raspberrypi - disabled system.adapter.history.0 : history : raspberrypi - disabled system.adapter.icons-mfd-png.0 : icons-mfd-png : raspberrypi - disabled system.adapter.icons-mfd-svg.0 : icons-mfd-svg : raspberrypi - disabled system.adapter.icons-ultimate-png.0 : icons-ultimate-png : raspberrypi - disabled + system.adapter.javascript.0 : javascript : raspberrypi - enabled system.adapter.smartcontrol.0 : smartcontrol : raspberrypi - disabled system.adapter.vis-colorpicker.0 : vis-colorpicker : raspberrypi - disabled system.adapter.vis-hqwidgets.0 : vis-hqwidgets : 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/ttyACM0 + 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.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.zigbee.0 : zigbee : raspberrypi - enabled, port: /dev/ttyACM0 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.3.5 , installed 6.3.5 Adapter "alexa2" : 3.23.2 , installed 3.23.2 Adapter "backitup" : 2.6.19 , installed 2.6.19 Adapter "discovery" : 3.1.0 , installed 3.1.0 Adapter "habpanel" : 0.5.0 , installed 0.5.0 Adapter "history" : 2.2.4 , installed 2.2.4 Adapter "hs100" : 2.1.2 , installed 2.1.2 Adapter "icons-mfd-png": 1.1.0 , installed 1.1.0 Adapter "icons-mfd-svg": 1.1.0 , installed 1.1.0 Adapter "icons-ultimate-png": 1.0.1, installed 1.0.1 Adapter "javascript" : 6.1.4 , installed 6.1.4 Controller "js-controller": 4.0.24 , installed 4.0.24 Adapter "pi-hole" : 1.3.4 , installed 1.3.4 Adapter "rpi2" : 1.3.2 , installed 1.3.2 Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "smartcontrol" : 1.3.2 , installed 1.3.2 Adapter "socketio" : 4.2.0 , installed 4.2.0 Adapter "tapo" : 0.0.8 , installed 0.0.8 Adapter "telegram" : 1.15.2 , installed 1.15.2 Adapter "vis" : 1.4.16 , installed 1.4.16 Adapter "vis-colorpicker": 1.2.0 , installed 1.2.0 Adapter "vis-hqwidgets": 1.3.0 , installed 1.3.0 Adapter "web" : 4.3.0 , installed 4.3.0 Adapter "ws" : 1.3.0 , installed 1.3.0 Adapter "zigbee" : 1.8.10 , installed 1.8.10 Objects and States Please stand by - This may take a while Objects: 909 States: 629 *** OS-Repositories and Updates *** Hit:1 http://security.debian.org/debian-security bullseye-security InRelease Hit:2 http://deb.debian.org/debian bullseye InRelease Hit:3 http://deb.debian.org/debian bullseye-updates InRelease Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease Hit:5 https://deb.nodesource.com/node_18.x bullseye 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:4711 0.0.0.0:* LISTEN 999 15067 608/pihole-FTL tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 0 15041 571/cupsd tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 13202 572/iobroker.js-con tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 15688 572/iobroker.js-con tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 999 15060 608/pihole-FTL tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 15000 626/sshd: /usr/sbin tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 0 15498 669/lighttpd tcp 0 0 127.0.0.1:8080 0.0.0.0:* LISTEN 1000 19414 2036/electron.js tcp 0 0 0.0.0.0:5900 0.0.0.0:* LISTEN 0 15085 617/vncserver-x11-c tcp6 0 0 :::8081 :::* LISTEN 1001 16793 1111/io.admin.0 tcp6 0 0 :::8082 :::* LISTEN 1001 19366 1884/io.web.0 tcp6 0 0 :::53 :::* LISTEN 999 15062 608/pihole-FTL tcp6 0 0 :::22 :::* LISTEN 0 3928 626/sshd: /usr/sbin tcp6 0 0 :::80 :::* LISTEN 0 15499 669/lighttpd tcp6 0 0 ::1:631 :::* LISTEN 0 15040 571/cupsd tcp6 0 0 ::1:4711 :::* LISTEN 999 15068 608/pihole-FTL tcp6 0 0 :::5900 :::* LISTEN 0 15084 617/vncserver-x11-c udp 0 0 0.0.0.0:5353 0.0.0.0:* 108 14866 387/avahi-daemon: r udp 0 0 0.0.0.0:36561 0.0.0.0:* 108 14868 387/avahi-daemon: r udp 0 0 0.0.0.0:53 0.0.0.0:* 999 15059 608/pihole-FTL udp 0 0 0.0.0.0:68 0.0.0.0:* 0 3980 506/dhcpcd udp 0 0 0.0.0.0:631 0.0.0.0:* 0 15483 647/cups-browsed udp6 0 0 :::5353 :::* 108 14867 387/avahi-daemon: r udp6 0 0 :::54572 :::* 108 14869 387/avahi-daemon: r udp6 0 0 :::53 :::* 999 15061 608/pihole-FTL udp6 0 0 :::546 :::* 0 4024 506/dhcpcd *** Log File - Last 25 Lines *** 2023-06-03 21:53:53.987 - info: zigbee.0 (1370) 0x54ef44100073d0a3 (addr 9082): SRTS-A01 - Xiaomi Aqara Smart Radiator Thermostat E1 (EndDevice) 2023-06-03 21:53:53.989 - info: zigbee.0 (1370) 0x00158d000949d34e (addr 26735): SJCGQ11LM - Xiaomi Aqara water leak sensor (EndDevice) 2023-06-03 21:53:53.992 - info: zigbee.0 (1370) 0x00158d000945bfd3 (addr 17435): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice) 2023-06-03 21:53:53.995 - info: zigbee.0 (1370) 0xa4c138e5451ab6c4 (addr 54302): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router) 2023-06-03 21:53:53.997 - info: zigbee.0 (1370) 0xa4c13871aeaebd22 (addr 53071): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router) 2023-06-03 21:53:54.000 - info: zigbee.0 (1370) 0xa4c1385251eceb96 (addr 11647): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router) 2023-06-03 21:53:54.002 - info: zigbee.0 (1370) 0xf082c0fffe21f773 (addr 16782): LED1924G9 - IKEA TRADFRI bulb E26/E27 CWS 800/806 lumen, dimmable, color, opal white (Router) 2023-06-03 21:53:54.004 - info: zigbee.0 (1370) 0xf082c0fffe6f571c (addr 26282): LED2003G10 - IKEA TRADFRI LED bulb E26/27 1100/1055/1160 lumen, dimmable, white spectrum, opal white (Router) 2023-06-03 21:53:54.007 - info: zigbee.0 (1370) 0x90fd9ffffe8f0d07 (addr 60040): LED1537R6/LED1739R5 - IKEA TRADFRI LED bulb GU10 400 lumen, dimmable, white spectrum (Router) 2023-06-03 21:53:54.009 - info: zigbee.0 (1370) 0x90fd9ffffe908863 (addr 56939): LED1537R6/LED1739R5 - IKEA TRADFRI LED bulb GU10 400 lumen, dimmable, white spectrum (Router) 2023-06-03 21:53:54.012 - info: zigbee.0 (1370) 0x90fd9ffffe8b2539 (addr 60697): LED1537R6/LED1739R5 - IKEA TRADFRI LED bulb GU10 400 lumen, dimmable, white spectrum (Router) 2023-06-03 21:53:54.014 - info: zigbee.0 (1370) 0x90fd9ffffe88a5e1 (addr 37735): LED1537R6/LED1739R5 - IKEA TRADFRI LED bulb GU10 400 lumen, dimmable, white spectrum (Router) 2023-06-03 21:53:54.017 - info: zigbee.0 (1370) 0x90fd9ffffe887bf9 (addr 30946): LED1537R6/LED1739R5 - IKEA TRADFRI LED bulb GU10 400 lumen, dimmable, white spectrum (Router) 2023-06-03 21:53:54.020 - info: zigbee.0 (1370) 0x00178801043c93d5 (addr 8152): 9290012573A - Philips Hue white and color ambiance E26/E27/E14 (Router) 2023-06-03 21:53:54.022 - info: zigbee.0 (1370) 0x00178801045969cc (addr 60289): 9290011370B - Philips Hue white A60 bulb E27 (Router) 2023-06-03 21:53:54.024 - info: zigbee.0 (1370) 0x00178801001f5541 (addr 62234): 7199960PH - Philips Hue Iris (Router) 2023-06-03 21:53:54.027 - info: zigbee.0 (1370) 0x00178801098036fa (addr 3724): 915005733701 - Philips Hue White and color ambiance Play Lightbar (Router) 2023-06-03 21:53:54.031 - info: zigbee.0 (1370) 0x00178801098627f4 (addr 52843): 915005733701 - Philips Hue White and color ambiance Play Lightbar (Router) 2023-06-03 21:53:54.033 - info: zigbee.0 (1370) Zigbee started 2023-06-03 21:54:09.914 - info: web.0 (1884) ==> Connected system.user.admin from ::ffff:192.168.178.219 2023-06-03 21:54:17.426 - info: web.0 (1884) <== Disconnect system.user.admin from ::ffff:192.168.178.219 habpanel.0 2023-06-03 21:54:29.740 - info: web.0 (1884) ==> Connected system.user.admin from ::ffff:192.168.178.219 2023-06-03 21:55:07.608 - info: admin.0 (1111) failed connection to socket.io from ::ffff:192.168.178.41: Passport was not initialized 2023-06-03 21:55:07.641 - info: admin.0 (1111) failed connection to socket.io from ::ffff:192.168.178.41: Passport was not initialized 2023-06-03 21:55:10.397 - info: admin.0 (1111) ==> Connected system.user.admin from ::ffff:192.168.178.41======================= SUMMARY ======================= v.2023-04-16 Operatingsystem: Debian GNU/Linux 11 (bullseye) Kernel: 6.1.21-v8+ Installation: Native Timezone: Europe/Berlin (CEST, +0200) User-ID: 1000 X-Server: true Boot Target: graphical.target Pending OS-Updates: 0 Pending iob updates: 0 Nodejs-Installation: /usr/bin/nodejs v18.16.0 /usr/bin/node v18.16.0 /usr/bin/npm 9.5.1 /usr/bin/npx 9.5.1 Recommended versions are nodejs 18.x.y and npm 9.x.y Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 7.8G 985M 5.8G 113M 1.1G 6.6G Swap: 99M 0B 99M Total: 7.9G 985M 5.9G Active iob-Instances: 7 Active repo(s): stable ioBroker Core: js-controller 4.0.24 admin 6.3.5 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: + system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 909 States: 629 Size of iob-Database: 15M /opt/iobroker/iobroker-data/objects.jsonl 7.1M /opt/iobroker/iobroker-data/states.jsonl =================== END OF SUMMARY ====================Desktop ist an da auf dem selben Pi MagicMirror läuft
Der COM anschlussname is :/dev/ttyACM0
da der Befehl ls -l /dev/serial/by-id nichts findet mit by-path bekomme ich aber die ausgabe das das der richtige COM isleovandavart@raspberrypi:~ $ ls -l /dev/serial/by-path insgesamt 0 lrwxrwxrwx 1 root root 13 3. Jun 21:52 platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.2:1.0 -> ../../ttyACM0 leovandavart@raspberrypi:~ $ ls -l /dev/serial/by-id ls: Zugriff auf '/dev/serial/by-id' nicht möglich: Datei oder Verzeichnis nicht gefunden leovandavart@raspberrypi:~ $ -
@leovandavart könnte auch das hier sein:
https://forum.iobroker.net/topic/65017/zigbee-conbee2-funktioniert-nach-update-nicht-mehr-udev/179
-
@djmarc75 ich lese es mir mal durch
-
@djmarc75 anscheind ihregend was mit udev aber keiner hat wirklich hingeschrieben wie es richtig geht
-
@leovandavart
Doch.
Steht sehr ausführlich im ersten Post.https://forum.iobroker.net/topic/65017/zigbee-conbee2-funktioniert-nach-update-nicht-mehr-udev
-
@leovandavart sagte in Ständiger Client-Verlust im Zigbee-Netzwerk:
aber keiner hat wirklich hingeschrieben wie es richtig geht
oh, das stimmt aber mal so garnicht... in diesem Beitrag wird alles haarklein beschrieben !!
-
@puls200 sagte in Ständiger Client-Verlust im Zigbee-Netzwerk:
habe nun gemäß Deiner Anleitung auf v18.6.0 aktualisiert.
bei einer Neuinstallation von ioBroker auf einem frischen OS wird nodejs automatisch mit der aktuell empfohlenen Version mit installiert.
-
@djmarc75 okay da hat das froum wohl rumgebugt ich war ganz oben und hatte den post nicht gesehen.
ich hab gestern abend alles wie in der anleitung gemacht und es ging bis gerade eben wo ich nachhause gekommen bin und licht einschalten wollte.
2023-06-04 13:27:24.764 - error: zigbee.0 (1555) Adapter disconnected, stopping 2023-06-04 13:27:31.716 - info: web.0 (2007) ==> Connected system.user.admin from ::ffff:192.168.178.219 2023-06-04 13:27:31.718 - info: web.0 (2007) ==> Connected system.user.admin from ::ffff:192.168.178.219 2023-06-04 13:27:31.836 - info: web.0 (2007) ==> Connected system.user.admin from ::ffff:192.168.178.219 2023-06-04 13:27:34.846 - info: zigbee.0 (1555) Try to reconnect. 5 attempts left 2023-06-04 13:27:34.848 - info: zigbee.0 (1555) Starting Zigbee npm ... 2023-06-04 13:27:34.933 - info: zigbee.0 (1555) Installed Version: iobroker.zigbee@1.8.10 2023-06-04 13:27:38.055 - info: zigbee.0 (1555) Coordinator firmware version: {"type":"zStack12","meta":{"transportrev":2,"product":0,"majorrel":2,"minorrel":6,"maintrel":3,"revision":20211115}} 2023-06-04 13:27:38.057 - info: zigbee.0 (1555) Unable to disable LED, unsupported function. 2023-06-04 13:27:38.063 - info: zigbee.0 (1555) --> transmitPower : normal 2023-06-04 13:27:38.081 - info: zigbee.0 (1555) Currently 29 devices are joined: 2023-06-04 13:27:38.114 - info: zigbee.0 (1555) 0x00158d0008ad6052 (addr 16818): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2023-06-04 13:27:38.116 - info: zigbee.0 (1555) 0x00158d0008ce87b3 (addr 18144): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2023-06-04 13:27:38.118 - info: zigbee.0 (1555) 0x00158d0008c9aa6a (addr 35675): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2023-06-04 13:27:38.120 - info: zigbee.0 (1555) 0x00158d0008743027 (addr 24204): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2023-06-04 13:27:38.121 - info: zigbee.0 (1555) 0x00158d0008ce87e9 (addr 60542): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2023-06-04 13:27:38.122 - info: zigbee.0 (1555) 0x00158d0008ad605e (addr 7294): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2023-06-04 13:27:38.123 - info: zigbee.0 (1555) 0x00158d0008838af6 (addr 38939): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2023-06-04 13:27:38.125 - info: zigbee.0 (1555) 0x54ef44100070154e (addr 50946): SRTS-A01 - Xiaomi Aqara Smart Radiator Thermostat E1 (EndDevice) 2023-06-04 13:27:38.126 - info: zigbee.0 (1555) 0x54ef44100073e6eb (addr 7958): SRTS-A01 - Xiaomi Aqara Smart Radiator Thermostat E1 (EndDevice) 2023-06-04 13:27:38.127 - info: zigbee.0 (1555) 0x54ef44100073cf7f (addr 26093): SRTS-A01 - Xiaomi Aqara Smart Radiator Thermostat E1 (EndDevice) 2023-06-04 13:27:38.129 - info: zigbee.0 (1555) 0x54ef44100073e36b (addr 3931): SRTS-A01 - Xiaomi Aqara Smart Radiator Thermostat E1 (EndDevice) 2023-06-04 13:27:38.132 - info: zigbee.0 (1555) 0x54ef44100073d0a3 (addr 9082): SRTS-A01 - Xiaomi Aqara Smart Radiator Thermostat E1 (EndDevice) 2023-06-04 13:27:38.134 - info: zigbee.0 (1555) 0x00158d000949d34e (addr 26735): SJCGQ11LM - Xiaomi Aqara water leak sensor (EndDevice) 2023-06-04 13:27:38.138 - info: zigbee.0 (1555) 0x00158d000945bfd3 (addr 17435): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice) 2023-06-04 13:27:38.140 - info: zigbee.0 (1555) 0xa4c138e5451ab6c4 (addr 54302): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router) 2023-06-04 13:27:38.142 - info: zigbee.0 (1555) 0xa4c13871aeaebd22 (addr 53071): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router) 2023-06-04 13:27:38.145 - info: zigbee.0 (1555) 0xa4c1385251eceb96 (addr 11647): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router) 2023-06-04 13:27:38.146 - info: zigbee.0 (1555) 0xf082c0fffe21f773 (addr 16782): LED1924G9 - IKEA TRADFRI bulb E26/E27 CWS 800/806 lumen, dimmable, color, opal white (Router) 2023-06-04 13:27:38.148 - info: zigbee.0 (1555) 0xf082c0fffe6f571c (addr 26282): LED2003G10 - IKEA TRADFRI LED bulb E26/27 1100/1055/1160 lumen, dimmable, white spectrum, opal white (Router) 2023-06-04 13:27:38.150 - info: zigbee.0 (1555) 0x90fd9ffffe8f0d07 (addr 60040): LED1537R6/LED1739R5 - IKEA TRADFRI LED bulb GU10 400 lumen, dimmable, white spectrum (Router) 2023-06-04 13:27:38.151 - info: zigbee.0 (1555) 0x90fd9ffffe908863 (addr 56939): LED1537R6/LED1739R5 - IKEA TRADFRI LED bulb GU10 400 lumen, dimmable, white spectrum (Router) 2023-06-04 13:27:38.154 - info: zigbee.0 (1555) 0x90fd9ffffe8b2539 (addr 60697): LED1537R6/LED1739R5 - IKEA TRADFRI LED bulb GU10 400 lumen, dimmable, white spectrum (Router) 2023-06-04 13:27:38.155 - info: zigbee.0 (1555) 0x90fd9ffffe88a5e1 (addr 37735): LED1537R6/LED1739R5 - IKEA TRADFRI LED bulb GU10 400 lumen, dimmable, white spectrum (Router) 2023-06-04 13:27:38.156 - info: zigbee.0 (1555) 0x90fd9ffffe887bf9 (addr 30946): LED1537R6/LED1739R5 - IKEA TRADFRI LED bulb GU10 400 lumen, dimmable, white spectrum (Router) 2023-06-04 13:27:38.157 - info: zigbee.0 (1555) 0x00178801043c93d5 (addr 8152): 9290012573A - Philips Hue white and color ambiance E26/E27/E14 (Router) 2023-06-04 13:27:38.158 - info: zigbee.0 (1555) 0x00178801045969cc (addr 60289): 9290011370B - Philips Hue white A60 bulb E27 (Router) 2023-06-04 13:27:38.159 - info: zigbee.0 (1555) 0x00178801001f5541 (addr 62234): 7199960PH - Philips Hue Iris (Router) 2023-06-04 13:27:38.160 - info: zigbee.0 (1555) 0x00178801098036fa (addr 3724): 915005733701 - Philips Hue White and color ambiance Play Lightbar (Router) 2023-06-04 13:27:38.161 - info: zigbee.0 (1555) 0x00178801098627f4 (addr 52843): 915005733701 - Philips Hue White and color ambiance Play Lightbar (Router) 2023-06-04 13:27:38.162 - info: zigbee.0 (1555) Zigbee started 2023-06-04 13:30:28.978 - warn: zigbee.0 (1555) DeviceAvailability:Stopping to ping 0xf082c0fffe21f773 TRADFRI bulb E27 CWS 806lm after 5 ping attempts 2023-06-04 13:30:30.574 - warn: zigbee.0 (1555) DeviceAvailability:Stopping to ping 0xf082c0fffe6f571c TRADFRIbulbE27WSglobeopal1055lm after 5 ping attempts 2023-06-04 13:30:30.590 - warn: zigbee.0 (1555) DeviceAvailability:Stopping to ping 0x90fd9ffffe8f0d07 TRADFRI bulb GU10 WS 400lm after 5 ping attempts 2023-06-04 13:30:30.753 - warn: zigbee.0 (1555) DeviceAvailability:Stopping to ping 0x90fd9ffffe908863 TRADFRI bulb GU10 WS 400lm after 5 ping attempts 2023-06-04 13:30:30.770 - warn: zigbee.0 (1555) DeviceAvailability:Stopping to ping 0x90fd9ffffe8b2539 TRADFRI bulb GU10 WS 400lm after 5 ping attempts 2023-06-04 13:30:30.785 - warn: zigbee.0 (1555) DeviceAvailability:Stopping to ping 0x90fd9ffffe88a5e1 TRADFRI bulb GU10 WS 400lm after 5 ping attempts 2023-06-04 13:30:31.295 - warn: zigbee.0 (1555) DeviceAvailability:Stopping to ping 0x90fd9ffffe887bf9 TRADFRI bulb GU10 WS 400lm after 5 ping attempts 2023-06-04 13:30:37.228 - warn: zigbee.0 (1555) DeviceAvailability:Stopping to ping 0x00178801045969cc LWF001 after 5 ping attempts 2023-06-04 13:36:42.467 - info: web.0 (2007) <== Disconnect system.user.admin from ::ffff:192.168.178.219 vis.0 2023-06-04 13:36:45.941 - info: web.0 (2007) <== Disconnect system.user.admin from ::ffff:192.168.178.219 vis.0 2023-06-04 13:36:51.029 - info: web.0 (2007) <== Disconnect system.user.admin from ::ffff:192.168.178.219 habpanel.0 2023-06-04 13:42:42.317 - info: web.0 (2007) ==> Connected system.user.admin from ::ffff:192.168.178.219 2023-06-04 13:42:42.318 - info: web.0 (2007) ==> Connected system.user.admin from ::ffff:192.168.178.219 2023-06-04 13:42:42.319 - info: web.0 (2007) ==> Connected system.user.admin from ::ffff:192.168.178.219 2023-06-04 13:49:32.952 - info: web.0 (2007) <== Disconnect system.user.admin from ::ffff:192.168.178.219 vis.0 2023-06-04 13:49:40.105 - info: web.0 (2007) <== Disconnect system.user.admin from ::ffff:192.168.178.219 habpanel.0 2023-06-04 13:49:40.337 - info: web.0 (2007) <== Disconnect system.user.admin from ::ffff:192.168.178.219 vis.0 2023-06-04 13:52:09.386 - info: web.0 (2007) ==> Connected system.user.admin from ::ffff:192.168.178.219 2023-06-04 13:52:09.414 - info: web.0 (2007) ==> Connected system.user.admin from ::ffff:192.168.178.219 2023-06-04 13:52:09.434 - info: web.0 (2007) ==> Connected system.user.admin from ::ffff:192.168.178.219 2023-06-04 13:57:08.231 - info: web.0 (2007) <== Disconnect system.user.admin from ::ffff:192.168.178.219 vis.0 2023-06-04 13:57:40.230 - info: web.0 (2007) ==> Connected system.user.admin from ::ffff:192.168.178.219 2023-06-04 13:57:46.764 - info: web.0 (2007) <== Disconnect system.user.admin from ::ffff:192.168.178.219 vis.0 2023-06-04 13:57:53.400 - info: web.0 (2007) ==> Connected system.user.admin from ::ffff:192.168.178.219 2023-06-04 14:06:01.545 - info: web.0 (2007) <== Disconnect system.user.admin from ::ffff:192.168.178.219 vis.0 2023-06-04 14:06:20.199 - info: web.0 (2007) <== Disconnect system.user.admin from ::ffff:192.168.178.219 habpanel.0 2023-06-04 14:06:50.874 - info: web.0 (2007) <== Disconnect system.user.admin from ::ffff:192.168.178.219 vis.0 2023-06-04 14:15:12.506 - info: web.0 (2007) ==> Connected system.user.admin from ::ffff:192.168.178.219 2023-06-04 14:15:12.582 - info: web.0 (2007) ==> Connected system.user.admin from ::ffff:192.168.178.219 2023-06-04 14:15:12.622 - info: web.0 (2007) ==> Connected system.user.admin from ::ffff:192.168.178.219 2023-06-04 14:26:46.642 - info: web.0 (2007) <== Disconnect system.user.admin from ::ffff:192.168.178.219 habpanel.0 2023-06-04 14:26:47.375 - info: web.0 (2007) <== Disconnect system.user.admin from ::ffff:192.168.178.219 vis.0 2023-06-04 14:26:47.378 - info: web.0 (2007) <== Disconnect system.user.admin from ::ffff:192.168.178.219 vis.0 2023-06-04 14:31:37.049 - error: zigbee.0 (1555) Adapter disconnected, stopping 2023-06-04 14:31:37.065 - error: zigbee.0 (1555) Adapter disconnected, stopping 2023-06-04 14:31:38.135 - info: web.0 (2007) ==> Connected system.user.admin from ::ffff:192.168.178.219 2023-06-04 14:31:38.139 - info: web.0 (2007) ==> Connected system.user.admin from ::ffff:192.168.178.219 2023-06-04 14:31:38.140 - info: web.0 (2007) ==> Connected system.user.admin from ::ffff:192.168.178.219 2023-06-04 14:31:47.090 - info: zigbee.0 (1555) Try to reconnect. 5 attempts left 2023-06-04 14:31:47.091 - info: zigbee.0 (1555) Starting Zigbee npm ... 2023-06-04 14:31:47.120 - info: zigbee.0 (1555) Try to reconnect. 4 attempts left 2023-06-04 14:31:47.121 - info: zigbee.0 (1555) Starting Zigbee npm ... 2023-06-04 14:31:47.158 - info: zigbee.0 (1555) Installed Version: iobroker.zigbee@1.8.10 2023-06-04 14:31:47.159 - info: zigbee.0 (1555) Installed Version: iobroker.zigbee@1.8.10 2023-06-04 14:31:47.385 - error: zigbee.0 (1555) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'" 2023-06-04 14:31:47.386 - error: zigbee.0 (1555) Failed to start Zigbee 2023-06-04 14:31:47.391 - error: zigbee.0 (1555) Error herdsman start 2023-06-04 14:31:50.101 - error: zigbee.0 (1555) Starting zigbee-herdsman problem : "Cannot read properties of undefined (reading 'execute')" 2023-06-04 14:31:50.102 - error: zigbee.0 (1555) Failed to start Zigbee 2023-06-04 14:31:50.102 - error: zigbee.0 (1555) Error herdsman start 2023-06-04 14:31:57.396 - info: zigbee.0 (1555) Try to reconnect. 3 attempts left 2023-06-04 14:31:57.397 - info: zigbee.0 (1555) Starting Zigbee npm ... 2023-06-04 14:31:57.445 - info: zigbee.0 (1555) Installed Version: iobroker.zigbee@1.8.10 2023-06-04 14:31:57.643 - error: zigbee.0 (1555) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'" 2023-06-04 14:31:57.645 - error: zigbee.0 (1555) Failed to start Zigbee 2023-06-04 14:31:57.645 - error: zigbee.0 (1555) Error herdsman start 2023-06-04 14:32:00.105 - info: zigbee.0 (1555) Try to reconnect. 2 attempts left 2023-06-04 14:32:00.106 - info: zigbee.0 (1555) Starting Zigbee npm ... 2023-06-04 14:32:00.132 - info: zigbee.0 (1555) Installed Version: iobroker.zigbee@1.8.10 2023-06-04 14:32:00.280 - error: zigbee.0 (1555) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'" 2023-06-04 14:32:00.281 - error: zigbee.0 (1555) Failed to start Zigbee 2023-06-04 14:32:00.281 - error: zigbee.0 (1555) Error herdsman start 2023-06-04 14:32:07.648 - info: zigbee.0 (1555) Try to reconnect. 1 attempts left 2023-06-04 14:32:07.650 - info: zigbee.0 (1555) Starting Zigbee npm ... 2023-06-04 14:32:07.712 - info: zigbee.0 (1555) Installed Version: iobroker.zigbee@1.8.10 2023-06-04 14:32:07.878 - error: zigbee.0 (1555) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'" 2023-06-04 14:32:07.879 - error: zigbee.0 (1555) Failed to start Zigbee 2023-06-04 14:32:07.879 - error: zigbee.0 (1555) Error herdsman start 2023-06-04 14:32:10.283 - info: zigbee.0 (1555) Try to reconnect. 0 attempts left 2023-06-04 14:32:10.284 - info: zigbee.0 (1555) Starting Zigbee npm ... 2023-06-04 14:32:10.309 - info: zigbee.0 (1555) Installed Version: iobroker.zigbee@1.8.10 2023-06-04 14:32:10.446 - error: zigbee.0 (1555) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'" 2023-06-04 14:32:10.447 - error: zigbee.0 (1555) Failed to start Zigbee 2023-06-04 14:32:10.447 - error: zigbee.0 (1555) Error herdsman start 2023-06-04 14:37:47.679 - warn: zigbee.0 (1555) DeviceAvailability:Failed to ping 0x00178801043c93d5 LCT015 2023-06-04 14:37:57.749 - warn: zigbee.0 (1555) DeviceAvailability:Failed to ping 0x00178801001f5541 LLC010 2023-06-04 14:38:01.696 - warn: zigbee.0 (1555) DeviceAvailability:Failed to ping 0x00178801098627f4 440400982841 2023-06-04 14:38:06.699 - warn: zigbee.0 (1555) DeviceAvailability:Failed to ping 0x00178801098036fa 440400982841 2023-06-04 14:38:26.535 - info: web.0 (2007) <== Disconnect system.user.admin from ::ffff:192.168.178.219 habpanel.0 2023-06-04 14:38:26.625 - info: web.0 (2007) <== Disconnect system.user.admin from ::ffff:192.168.178.219 vis.0 2023-06-04 14:38:27.371 - info: web.0 (2007) <== Disconnect system.user.admin from ::ffff:192.168.178.219 vis.0 2023-06-04 14:48:25.591 - info: web.0 (2007) ==> Connected system.user.admin from ::ffff:192.168.178.219 2023-06-04 14:48:25.608 - info: web.0 (2007) ==> Connected system.user.admin from ::ffff:192.168.178.219 2023-06-04 14:48:25.628 - info: web.0 (2007) ==> Connected system.user.admin from ::ffff:192.168.178.219 2023-06-04 14:52:32.272 - warn: zigbee.0 (1555) DeviceAvailability:Stopping to ping 0xa4c1385251eceb96 TS011F after 183 ping attempts 2023-06-04 14:53:10.399 - warn: zigbee.0 (1555) DeviceAvailability:Stopping to ping 0xa4c138e5451ab6c4 TS011F after 293 ping attempts 2023-06-04 14:53:30.916 - warn: zigbee.0 (1555) DeviceAvailability:Stopping to ping 0xa4c13871aeaebd22 TS011F after 153 ping attempts 2023-06-04 14:55:15.635 - info: web.0 (2007) <== Disconnect system.user.admin from ::ffff:192.168.178.219 vis.0 2023-06-04 14:55:25.368 - info: web.0 (2007) <== Disconnect system.user.admin from ::ffff:192.168.178.219 vis.0 2023-06-04 14:55:32.815 - info: web.0 (2007) <== Disconnect system.user.admin from ::ffff:192.168.178.219 habpanel.0 2023-06-04 15:18:30.760 - info: web.0 (2007) ==> Connected system.user.admin from ::ffff:192.168.178.219 2023-06-04 15:18:30.784 - info: web.0 (2007) ==> Connected system.user.admin from ::ffff:192.168.178.219 2023-06-04 15:18:30.810 - info: web.0 (2007) ==> Connected system.user.admin from ::ffff:192.168.178.219 2023-06-04 15:21:18.341 - info: admin.0 (1049) ==> Connected system.user.admin from ::ffff:192.168.178.41 2023-06-04 15:21:20.024 - info: admin.0 (1049) ==> Connected system.user.admin from ::ffff:192.168.178.41 2023-06-04 15:21:20.182 - error: zigbee.0 (1555) getGroups: caught error: TypeError: Cannot read properties of undefined (reading 'getGroups') 2023-06-04 15:21:20.325 - info: zigbee.0 (1555) List of port: [{"path":"/dev/ttyACM0","manufacturer":"Texas Instruments","serialNumber":"__0X00124B001CDCEEC1","pnpId":"usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B001CDCEEC1-if00","vendorId":"0451","productId":"16a8"},{"path":"/dev/ttyAMA0"}] 2023-06-04 15:22:44.112 - info: admin.0 (1049) <== Disconnect system.user.admin from ::ffff:192.168.178.41 2023-06-04 15:22:45.845 - info: admin.0 (1049) ==> Connected system.user.admin from ::ffff:192.168.178.41 2023-06-04 15:22:45.927 - error: zigbee.0 (1555) getGroups: caught error: TypeError: Cannot read properties of undefined (reading 'getGroups') 2023-06-04 15:22:46.112 - info: zigbee.0 (1555) List of port: [{"path":"/dev/ttyACM0","manufacturer":"Texas Instruments","serialNumber":"__0X00124B001CDCEEC1","pnpId":"usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B001CDCEEC1-if00","vendorId":"0451","productId":"16a8"},{"path":"/dev/ttyAMA0"}] 2023-06-04 15:22:47.914 - info: admin.0 (1049) <== Disconnect system.user.admin from ::ffff:192.168.178.41 2023-06-04 15:22:52.042 - info: admin.0 (1049) ==> Connected system.user.admin from ::ffff:192.168.178.41 2023-06-04 15:22:52.104 - error: zigbee.0 (1555) getGroups: caught error: TypeError: Cannot read properties of undefined (reading 'getGroups') 2023-06-04 15:22:52.237 - info: zigbee.0 (1555) List of port: [{"path":"/dev/ttyACM0","manufacturer":"Texas Instruments","serialNumber":"__0X00124B001CDCEEC1","pnpId":"usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B001CDCEEC1-if00","vendorId":"0451","productId":"16a8"},{"path":"/dev/ttyAMA0"}] 2023-06-04 15:23:06.023 - info: admin.0 (1049) <== Disconnect system.user.admin from ::ffff:192.168.178.41 -
@leovandavart sagte in Ständiger Client-Verlust im Zigbee-Netzwerk:
alles wie in der anleitung gemacht
eher nicht, sonst müsste es ja funktionieren
Mach einfach nochmal und zeig dann bitte die Ausgabe von z.B.
apt policy udev -
@djmarc75 said in Ständiger Client-Verlust im Zigbee-Netzwerk:
apt policy udev
leovandavart@raspberrypi:~ $ apt policy udev udev: Installiert: 247.3-7+deb11u3 Installationskandidat: 247.3-7+deb11u3 Versionstabelle: *** 247.3-7+deb11u3 500 500 http://deb.debian.org/debian bullseye-proposed-updates/main arm64 Packages 100 /var/lib/dpkg/status 247.3-7+deb11u2 500 500 http://deb.debian.org/debian bullseye/main arm64 Packages leovandavart@raspberrypi:~ $ -
Und die symlinks in /dev/serial/by-id sind wieder da? Was ist im Adapter eingestellt?
