OMG! Es kann so einfach sein. DANKE @arteck !!!! Die Baudrate war das Problem.
Latest posts made by Squelsh
-
RE: Gelöst: Zigbee: Cannot lock port nach Update auf 1.10.14posted in Error/Bug
-
RE: Gelöst: Zigbee: Cannot lock port nach Update auf 1.10.14posted in Error/Bug
Danke für eure Zeit. Hab die ConBee Firmware geflashed und noch mal alles neu gestartet. Leider sieht es noch genau so aus:
pi@smartie:~ $ iob logs 2025-01-05 12:07:10.650 - error: host.smartie cannot call visUtils: Not exists 2025-01-05 12:07:20.246 - info: host.smartie "system.adapter.zigbee.1" enabled 2025-01-05 12:07:20.668 - info: host.smartie instance system.adapter.zigbee.1 in version "1.10.14" started with pid 41757 2025-01-05 12:07:25.355 - debug: zigbee.1 (41757) Redis Objects: Use Redis connection: 127.0.0.1:9001 2025-01-05 12:07:25.389 - debug: zigbee.1 (41757) Objects client ready ... initialize now 2025-01-05 12:07:25.393 - debug: zigbee.1 (41757) Objects create System PubSub Client 2025-01-05 12:07:25.394 - debug: zigbee.1 (41757) Objects create User PubSub Client 2025-01-05 12:07:25.426 - debug: zigbee.1 (41757) Objects client initialize lua scripts 2025-01-05 12:07:25.435 - debug: zigbee.1 (41757) Objects connected to redis: 127.0.0.1:9001 2025-01-05 12:07:25.467 - debug: zigbee.1 (41757) Redis States: Use Redis connection: 127.0.0.1:9000 2025-01-05 12:07:25.478 - debug: zigbee.1 (41757) States create System PubSub Client 2025-01-05 12:07:25.479 - debug: zigbee.1 (41757) States create User PubSub Client 2025-01-05 12:07:25.534 - debug: zigbee.1 (41757) States connected to redis: 127.0.0.1:9000 2025-01-05 12:07:25.577 - debug: zigbee.1 (41757) Plugin sentry Initialize Plugin (enabled=true) 2025-01-05 12:07:26.134 - info: zigbee.1 (41757) starting. Version 1.10.14 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.20.5, js-controller: 7.0.6 2025-01-05 12:07:26.168 - debug: zigbee.1 (41757) Using zigbee-herdsman with settings: {"network":{"panID":4576,"extendedPanID":[38,170,60,17,254,47,117,131],"channelList":[11],"networkKey":[1,3,5,7,9,11,13,15,0,2,4,6,8,10,12,13]},"databasePath":"/opt/iobroker/iobroker-data/zigbee_1/shepherd.db","backupPath":"/opt/iobroker/iobroker-data/zigbee_1/nvbackup.json","serialPort":{"baudRate":115200,"rtscts":false,"path":"/dev/serial/by-id/usb-FTDI_FT230X_Basic_UART_DO00KJDU-if00-port0","adapter":"deconz"},"adapter":{"forceStartWithInconsistentAdapterConfiguration":false},"legacy":false} 2025-01-05 12:07:26.259 - info: zigbee.1 (41757) delete old Backup files. keep only last 10 2025-01-05 12:07:26.262 - info: zigbee.1 (41757) Starting Zigbee npm ... 2025-01-05 12:07:26.310 - debug: zigbee.1 (41757) Starting zigbee-herdsman... 2025-01-05 12:07:26.673 - debug: zigbee.1 (41757) Backup /opt/iobroker/iobroker-data/zigbee_1/backup_2025_01_05-12_07_26.tar.gz success 2025-01-05 12:07:26.689 - info: zigbee.1 (41757) Installed Version: iobroker.zigbee@1.10.14 2025-01-05 12:07:37.363 - error: zigbee.1 (41757) Starting zigbee-herdsman problem : "TIMEOUT" 2025-01-05 12:07:37.364 - error: zigbee.1 (41757) Failed to start Zigbee 2025-01-05 12:07:37.365 - error: zigbee.1 (41757) Error herdsman start 2025-01-05 12:07:47.369 - info: zigbee.1 (41757) Try to reconnect. 1 attempts left 2025-01-05 12:07:47.371 - info: zigbee.1 (41757) Starting Zigbee npm ... 2025-01-05 12:07:47.377 - debug: zigbee.1 (41757) Starting zigbee-herdsman... 2025-01-05 12:07:47.391 - info: zigbee.1 (41757) Installed Version: iobroker.zigbee@1.10.14 2025-01-05 12:07:47.573 - error: zigbee.1 (41757) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'" 2025-01-05 12:07:47.574 - error: zigbee.1 (41757) Failed to start Zigbee 2025-01-05 12:07:47.574 - error: zigbee.1 (41757) Error herdsman start -
RE: Gelöst: Zigbee: Cannot lock port nach Update auf 1.10.14posted in Error/Bug
Hi @asgothian
Hier der Log nach 60 Sek:
2025-01-05 11:29:11.270 - info: admin.0 (1023) ==> Connected system.user.admin from ::ffff:192.168.1.218 2025-01-05 11:29:29.675 - info: admin.0 (1023) <== Disconnect system.user.admin from ::ffff:192.168.1.218 2025-01-05 11:29:36.733 - info: host.smartie "system.adapter.zigbee.1" enabled 2025-01-05 11:29:37.312 - info: host.smartie instance system.adapter.zigbee.1 in version "1.10.14" started with pid 39739 2025-01-05 11:29:41.894 - debug: zigbee.1 (39739) Redis Objects: Use Redis connection: 127.0.0.1:9001 2025-01-05 11:29:41.942 - debug: zigbee.1 (39739) Objects client ready ... initialize now 2025-01-05 11:29:41.945 - debug: zigbee.1 (39739) Objects create System PubSub Client 2025-01-05 11:29:41.946 - debug: zigbee.1 (39739) Objects create User PubSub Client 2025-01-05 11:29:41.979 - debug: zigbee.1 (39739) Objects client initialize lua scripts 2025-01-05 11:29:41.989 - debug: zigbee.1 (39739) Objects connected to redis: 127.0.0.1:9001 2025-01-05 11:29:42.021 - debug: zigbee.1 (39739) Redis States: Use Redis connection: 127.0.0.1:9000 2025-01-05 11:29:42.033 - debug: zigbee.1 (39739) States create System PubSub Client 2025-01-05 11:29:42.034 - debug: zigbee.1 (39739) States create User PubSub Client 2025-01-05 11:29:42.090 - debug: zigbee.1 (39739) States connected to redis: 127.0.0.1:9000 2025-01-05 11:29:42.134 - debug: zigbee.1 (39739) Plugin sentry Initialize Plugin (enabled=true) 2025-01-05 11:29:42.765 - info: zigbee.1 (39739) starting. Version 1.10.14 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.20.5, js-controller: 7.0.6 2025-01-05 11:29:42.801 - debug: zigbee.1 (39739) Using zigbee-herdsman with settings: {"network":{"panID":4576,"extendedPanID":[38,170,60,17,254,47,117,131],"channelList":[11],"networkKey":[1,3,5,7,9,11,13,15,0,2,4,6,8,10,12,13]},"databasePath":"/opt/iobroker/iobroker-data/zigbee_1/shepherd.db","backupPath":"/opt/iobroker/iobroker-data/zigbee_1/nvbackup.json","serialPort":{"baudRate":115200,"rtscts":false,"path":"/dev/serial/by-id/usb-FTDI_FT230X_Basic_UART_DO00KJDU-if00-port0","adapter":"deconz"},"adapter":{"forceStartWithInconsistentAdapterConfiguration":false},"legacy":false} 2025-01-05 11:29:42.892 - info: zigbee.1 (39739) delete old Backup files. keep only last 10 2025-01-05 11:29:42.895 - info: zigbee.1 (39739) Starting Zigbee npm ... 2025-01-05 11:29:42.944 - debug: zigbee.1 (39739) Starting zigbee-herdsman... 2025-01-05 11:29:43.310 - debug: zigbee.1 (39739) Backup /opt/iobroker/iobroker-data/zigbee_1/backup_2025_01_05-11_29_42.tar.gz success 2025-01-05 11:29:43.326 - info: zigbee.1 (39739) Installed Version: iobroker.zigbee@1.10.14 2025-01-05 11:29:54.067 - error: zigbee.1 (39739) Starting zigbee-herdsman problem : "TIMEOUT" 2025-01-05 11:29:54.069 - error: zigbee.1 (39739) Failed to start Zigbee 2025-01-05 11:29:54.069 - error: zigbee.1 (39739) Error herdsman start 2025-01-05 11:30:04.074 - info: zigbee.1 (39739) Try to reconnect. 1 attempts left 2025-01-05 11:30:04.077 - info: zigbee.1 (39739) Starting Zigbee npm ... 2025-01-05 11:30:04.092 - debug: zigbee.1 (39739) Starting zigbee-herdsman... 2025-01-05 11:30:04.121 - info: zigbee.1 (39739) Installed Version: iobroker.zigbee@1.10.14 2025-01-05 11:30:04.354 - error: zigbee.1 (39739) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'" 2025-01-05 11:30:04.354 - error: zigbee.1 (39739) Failed to start Zigbee 2025-01-05 11:30:04.355 - error: zigbee.1 (39739) Error herdsman start 2025-01-05 11:32:13.436 - info: host.smartie "system.adapter.zigbee.1" disabled 2025-01-05 11:32:13.438 - info: host.smartie stopInstance system.adapter.zigbee.1 (force=false, process=true) 2025-01-05 11:32:13.451 - info: zigbee.1 (39739) Got terminate signal TERMINATE_YOURSELF 2025-01-05 11:32:13.527 - info: host.smartie stopInstance system.adapter.zigbee.1 send kill signal 2025-01-05 11:32:13.455 - info: zigbee.1 (39739) cleaned everything up... 2025-01-05 11:32:13.470 - info: zigbee.1 (39739) Zigbee: disabling joining new devices. 2025-01-05 11:32:13.471 - debug: zigbee.1 (39739) DeviceAvailability:Publish available for 0x00158d000325fb49 = false 2025-01-05 11:32:13.494 - debug: zigbee.1 (39739) DeviceAvailability:Publish LQ for 0x00158d000325fb49 = 0 2025-01-05 11:32:13.512 - debug: zigbee.1 (39739) DeviceAvailability:Publish available for 0x00158d0003030406 = false 2025-01-05 11:32:13.516 - debug: zigbee.1 (39739) DeviceAvailability:Publish LQ for 0x00158d0003030406 = 0 2025-01-05 11:32:13.522 - debug: zigbee.1 (39739) DeviceAvailability:Publish available for 0x00158d0003456504 = false 2025-01-05 11:32:13.526 - debug: zigbee.1 (39739) DeviceAvailability:Publish LQ for 0x00158d0003456504 = 0 2025-01-05 11:32:13.534 - debug: zigbee.1 (39739) DeviceAvailability:Publish available for 0x00158d000323c835 = false 2025-01-05 11:32:13.538 - debug: zigbee.1 (39739) DeviceAvailability:Publish LQ for 0x00158d000323c835 = 0 2025-01-05 11:32:13.544 - debug: zigbee.1 (39739) DeviceAvailability:Publish available for 0x00158d000303d8f9 = false 2025-01-05 11:32:13.548 - debug: zigbee.1 (39739) DeviceAvailability:Publish LQ for 0x00158d000303d8f9 = 0 2025-01-05 11:32:13.553 - debug: zigbee.1 (39739) DeviceAvailability:Publish available for 0x00158d00035c1631 = false 2025-01-05 11:32:13.558 - debug: zigbee.1 (39739) DeviceAvailability:Publish LQ for 0x00158d00035c1631 = 0 2025-01-05 11:32:13.564 - debug: zigbee.1 (39739) DeviceAvailability:Publish available for 0x00158d00034d4c81 = false 2025-01-05 11:32:13.568 - debug: zigbee.1 (39739) DeviceAvailability:Publish LQ for 0x00158d00034d4c81 = 0 2025-01-05 11:32:13.573 - debug: zigbee.1 (39739) DeviceAvailability:Publish available for 0x00158d000303d7db = false 2025-01-05 11:32:13.577 - debug: zigbee.1 (39739) DeviceAvailability:Publish LQ for 0x00158d000303d7db = 0 2025-01-05 11:32:13.581 - debug: zigbee.1 (39739) DeviceAvailability:Publish available for 0x00158d00034d4981 = false 2025-01-05 11:32:13.586 - debug: zigbee.1 (39739) DeviceAvailability:Publish LQ for 0x00158d00034d4981 = 0 2025-01-05 11:32:13.590 - debug: zigbee.1 (39739) DeviceAvailability:Publish available for 0x00158d00035c0114 = false 2025-01-05 11:32:13.594 - debug: zigbee.1 (39739) DeviceAvailability:Publish LQ for 0x00158d00035c0114 = 0 2025-01-05 11:32:13.598 - debug: zigbee.1 (39739) DeviceAvailability:Publish available for 0x00158d00034d4896 = false 2025-01-05 11:32:13.602 - debug: zigbee.1 (39739) DeviceAvailability:Publish LQ for 0x00158d00034d4896 = 0 2025-01-05 11:32:13.626 - info: zigbee.1 (39739) terminating 2025-01-05 11:32:13.627 - debug: zigbee.1 (39739) Plugin sentry destroyed 2025-01-05 11:32:13.627 - info: zigbee.1 (39739) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2025-01-05 11:32:13.716 - info: zigbee.1 (39739) debug devices set to [] 2025-01-05 11:32:13.956 - info: zigbee.1 (39739) terminating 2025-01-05 11:32:14.209 - info: host.smartie instance system.adapter.zigbee.1 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) -
RE: Gelöst: Zigbee: Cannot lock port nach Update auf 1.10.14posted in Error/Bug
@arteck Mal ganz allgemein: Riesen Dank für deine Arbeit an dem Zigbee-Connector!!! Und nein, ich erwarte sicher nicht, dass OpenSource Entwickler ihre Zeit in Hardware stecken, die ur-alt ist. Aber wenn das Ding nicht mehr supported wird, dann könntest du es ja vielleicht auf eine Art Blacklist schreiben, so dass die Fehlermeldung eindeutig ist.
-
RE: Gelöst: Zigbee: Cannot lock port nach Update auf 1.10.14posted in Error/Bug
@arteck Wenn's hilft, sehr gerne :))
Nein, im Ernst: Vielleicht kannst du mir ja sagen, wie ich weiter debuggen kann. Ich habe einiges an Linux Erfahrung, aber Null Erfahrung mit node Projekten. Die Meldung deute ich so, dass irgend ein anderes Programm das Device nutzt. Aber ich finde nichts...
-
RE: Gelöst: Zigbee: Cannot lock port nach Update auf 1.10.14posted in Error/Bug
@martinp Hi Martin, danke fürs Checken! Tatsächlich hatte mich das auch verwundert, aber der alte ConBee (1?) wird tatsächlich noch als generisches FTDI Device identifiziert.
Habe das gerade mit der Deconz Software auf meinem Linux-PC nachgepüft. Dort wird der selbe Treiber geladen und Deconz kann wunderbar mit dem Stick interagieren.
Bei der zweiten Instanz kann der by-id Pfad tatsächlich nicht genutzt werden, weil da Zigbee via LAN genutzt wird.@David-G Danke David für die lsof Ausgabe. Schon mal gut zu wissen, dass das normal ist.
==> Ich mach mal einen Issue beim Zigbee Adapter auf.
Nebenher habe ich mal einen neuen Sonoff 3 USB Stick bestellt. Evtl ist der Deconz inzwischen einfach zu alt.
-
Gelöst: Zigbee: Cannot lock port nach Update auf 1.10.14posted in Error/Bug
Hallo zusammen,
nachdem ich nach einem Update seit 4 Stunden versuche, mein Zigbee wieder ans Laufen zu bekommen, muss ich nun doch aufgeben und hier posten. Ich habe schon viele auf den ersten Blick vergleichbare Threads gelesen, aber meistens war eine Fehlkonfiguration des Zigbee Devices oder ein Unterschied zwischen Config und Backup das Problem. Das ist es bei mir laut Log aber nicht.
Offensichtlicher Fehler ist:
2025-01-05 00:50:15.793 - error: zigbee.1 (1659) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'"Das Device passt:
pi@smartie:/dev/serial/by-id $ ls -l total 0 lrwxrwxrwx 1 root root 13 Jan 5 00:48 usb-FTDI_FT230X_Basic_UART_DO00KJDU-if00-port0 -> ../../ttyUSB0Meine erste Vermutung war, dass ein anderer Prozess das Device locked, aber lsof sagt, dass nur iobroker etwas damit tut:
pi@smartie:~ $ sudo lsof | grep ttyUSB io.zigbee 1659 iobroker 26uW CHR 188,0 0t0 642 /dev/ttyUSB0 io.zigbee 1659 1660 node iobroker 26uW CHR 188,0 0t0 642 /dev/ttyUSB0 io.zigbee 1659 1661 node iobroker 26uW CHR 188,0 0t0 642 /dev/ttyUSB0 io.zigbee 1659 1662 node iobroker 26uW CHR 188,0 0t0 642 /dev/ttyUSB0 io.zigbee 1659 1663 node iobroker 26uW CHR 188,0 0t0 642 /dev/ttyUSB0 io.zigbee 1659 1664 node iobroker 26uW CHR 188,0 0t0 642 /dev/ttyUSB0 io.zigbee 1659 1665 node iobroker 26uW CHR 188,0 0t0 642 /dev/ttyUSB0 io.zigbee 1659 1780 node iobroker 26uW CHR 188,0 0t0 642 /dev/ttyUSB0 io.zigbee 1659 1781 node iobroker 26uW CHR 188,0 0t0 642 /dev/ttyUSB0 io.zigbee 1659 1782 node iobroker 26uW CHR 188,0 0t0 642 /dev/ttyUSB0 io.zigbee 1659 1783 node iobroker 26uW CHR 188,0 0t0 642 /dev/ttyUSB0Ich verstehe allerdings nicht, warum so viele Threads von io.zigbee auf das Device zugreifen müssen?
Hier enden dann allerdings meine Ideen.
Achso: Der Zigbee USB Stick ist ein Ur-alter ConBee der bisher super lief. Den hatte ich auch schon mehrmals aus/eingestöpselt und den RasPi auch mehrfach neu gestartet. Die zweite Zigbee Instanz nutzt ein Mqtt-Zigbee-Device. Die läuft problemlos. Habe sie nur gerade zu Debug-Zwecken ausgeschaltet.==> Wie kann ich hier tiefer graben und die Ursache finden? Scheinen ja doch ein paar Leute mit dem neuen Zigbee 1.10.13 bzw 1.10.14 probleme zu haben...
Danke vielmals im Voraus für Ideen!!
Hier noch die Diag-Ausgaben von iob:
- Adaptername: Zigbee
- Adapterversion: 1.10.14
- Hardwaresystem: Pi4
- Arbeitsspeicher: 8GB
Script v.2024-10-19 *** BASE SYSTEM *** Static hostname: smartie Icon name: computer Operating System: Debian GNU/Linux 12 (bookworm) Kernel: Linux 6.6.62+rpt-rpi-v8 Architecture: arm64 OS is similar to: Model : Raspberry Pi 4 Model B Rev 1.1 Docker : false Virtualization : none Kernel : aarch64 Userland : 64 bit Systemuptime and Load: 01:13:19 up 24 min, 2 users, load average: 0.56, 0.31, 0.41 CPU threads: 4 *** LIFE CYCLE STATUS *** Operating System is the current Debian stable version codenamed 'bookworm'! *** RASPBERRY THROTTLING *** Current issues: No throttling issues detected. Previously detected issues: No throttling issues detected. *** TIME AND TIMEZONES *** Local time: Sun 2025-01-05 01:13:19 CET Universal time: Sun 2025-01-05 00:13:19 UTC RTC time: Sun 2025-01-05 00:13:19 Time zone: Europe/Berlin (CET, +0100) System clock synchronized: yes NTP service: active RTC in local TZ: no *** Users and Groups *** User that called 'iob diag': pi HOME=/home/pi GROUPS=pi adm dialout cdrom sudo audio video plugdev games users input render netdev gpio i2c spi iobroker User that is running 'js-controller': iobroker HOME=/home/iobroker GROUPS=iobroker tty dialout audio video plugdev bluetooth gpio i2c *** DISPLAY-SERVER SETUP *** Display-Server: false Desktop: Terminal: tty *** MEMORY *** total used free shared buff/cache available Mem: 4.0G 1.7G 1.6G 1.3M 770M 2.3G Swap: 209M 0B 209M Total: 4.2G 1.7G 1.8G Active iob-Instances: 20 3791 M total memory 1628 M used memory 1659 M active memory 458 M inactive memory 1505 M free memory 70 M buffer memory 664 M swap cache 199 M total swap 0 M used swap 199 M free swap *** top - Table Of Processes *** top - 01:13:19 up 24 min, 2 users, load average: 0.56, 0.31, 0.41 Tasks: 190 total, 1 running, 189 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 20.0 sy, 0.0 ni, 80.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 3791.9 total, 1505.4 free, 1628.5 used, 734.9 buff/cache MiB Swap: 200.0 total, 200.0 free, 0.0 used. 2163.4 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. *** DMESG CRITICAL ERRORS *** No critical errors detected *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on udev devtmpfs 1.6G 0 1.6G 0% /dev tmpfs tmpfs 380M 1.3M 378M 1% /run /dev/mmcblk0p2 ext4 29G 9.4G 18G 35% / tmpfs tmpfs 1.9G 0 1.9G 0% /dev/shm tmpfs tmpfs 5.0M 20K 5.0M 1% /run/lock /dev/mmcblk0p1 vfat 510M 65M 446M 13% /boot/firmware tmpfs tmpfs 380M 0 380M 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Sun Jan 5 00:48:37 2025] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_headphones=0 cgroup_disable=memory numa_policy=interleave snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 genet.eee=N smsc95xx.macaddr=DC:A6:32:30:E4:09 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyAMA0,115200 console=tty1 root=PARTUUID=11058781-02 rootfstype=ext4 fsck.repair=yes rootwait cfg80211.ieee80211_regdom=DE [Sun Jan 5 00:48:39 2025] EXT4-fs (mmcblk0p2): mounted filesystem 6835594d-a5f3-459f-a244-318060e7e0ab ro with ordered data mode. Quota mode: none. [Sun Jan 5 00:48:40 2025] EXT4-fs (mmcblk0p2): re-mounted 6835594d-a5f3-459f-a244-318060e7e0ab r/w. Quota mode: none. Show mounted filesystems: 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: 3.9G /var/ 2.9G /var/log/journal/00d04d83b6454ea89fb4e65cc049b75e 2.9G /var/log/journal 2.9G /var/log 574M /var/cache Archived and active journals take up 2.8G in the file system. /opt/iobroker/backups: 350M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 833M /opt/iobroker/iobroker-data/ 782M /opt/iobroker/iobroker-data/files 617M /opt/iobroker/iobroker-data/files/javascript.admin 560M /opt/iobroker/iobroker-data/files/javascript.admin/static 558M /opt/iobroker/iobroker-data/files/javascript.admin/static/js The five largest files in iobroker-data are: 24M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.135279a0.js.map 12M /opt/iobroker/iobroker-data/files/backitup.admin/static/js/main.bd24114f.js 8.7M /opt/iobroker/iobroker-data/files/javascript.admin/static/js/838.0aa41cb0.chunk.js.map 8.6M /opt/iobroker/iobroker-data/files/javascript.admin/static/js/310.89a60ae1.chunk.js.map 8.5M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.135279a0.js USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': /dev/serial/by-id/usb-FTDI_FT230X_Basic_UART_DO00KJDU-if00-port0 HINT: Your zigbee.0 COM-Port is NOT matching 'by-id'. Please check your setting: tcp Your zigBee.1 COM-Port is matching 'by-id'. Very good! *** NodeJS-Installation *** /usr/bin/nodejs v18.20.5 /usr/bin/node v18.20.5 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.29.4 nodejs: Installed: 18.20.5-1nodesource1 Candidate: 18.20.5-1nodesource1 Version table: *** 18.20.5-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 100 /var/lib/dpkg/status 18.20.4-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.20.3-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.20.2-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.20.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.20.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.19.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.19.0+dfsg-6~deb12u2 500 500 http://deb.debian.org/debian bookworm/main arm64 Packages 18.19.0+dfsg-6~deb12u1 500 500 http://deb.debian.org/debian-security bookworm-security/main arm64 Packages 18.19.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.18.2-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.18.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.18.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.17.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.17.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.16.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.16.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.15.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.14.2-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.14.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.14.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.13.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.12.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.11.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.10.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.9.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.9.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.8.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.7.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.6.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.5.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.4.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.3.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.2.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.1.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.0.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Hosts: smartie smartie (version: 7.0.6, hostname: smartie , alive, uptime: 1476) Core adapters versions js-controller: 7.0.6 admin: 7.1.5 javascript: 8.8.3 nodejs modules from github: 0 Adapter State + system.adapter.admin.0 : admin : smartie - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.alias-manager.0 : alias-manager : smartie - enabled + system.adapter.backitup.0 : backitup : smartie - enabled + system.adapter.discovery.0 : discovery : smartie - enabled + system.adapter.history.0 : history : smartie - enabled + system.adapter.hm-rega.0 : hm-rega : smartie - enabled + system.adapter.hm-rpc.0 : hm-rpc : smartie - enabled, port: 0 + system.adapter.hm-rpc.1 : hm-rpc : smartie - enabled, port: 0 + system.adapter.hm-rpc.2 : hm-rpc : smartie - enabled, port: 0 + system.adapter.iqontrol.0 : iqontrol : smartie - enabled + system.adapter.jarvis.0 : jarvis : smartie - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.javascript.0 : javascript : smartie - enabled + system.adapter.mpd.0 : mpd : smartie - enabled, port: 6600 + system.adapter.mqtt.0 : mqtt : smartie - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.mqtt.1 : mqtt : smartie - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.net-tools.0 : net-tools : smartie - enabled system.adapter.ping.0 : ping : smartie - disabled + system.adapter.telegram-menu.0 : telegram-menu : smartie - enabled + system.adapter.telegram.0 : telegram : smartie - enabled, port: 8443, bind: 0.0.0.0 system.adapter.vis.0 : vis : smartie - enabled + system.adapter.web.0 : web : smartie - enabled, port: 8082, bind: 0.0.0.0, run as: admin system.adapter.zigbee.0 : zigbee : smartie - disabled, port: tcp://192.168.1.130:6638 + system.adapter.zigbee.1 : zigbee : smartie - enabled, port: /dev/serial/by-id/usb-FTDI_FT230X_Basic_UART_DO00KJDU-if00-port0 + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : smartie - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.hm-rpc.0 : hm-rpc : smartie - enabled, port: 0 + system.adapter.hm-rpc.1 : hm-rpc : smartie - enabled, port: 0 + system.adapter.hm-rpc.2 : hm-rpc : smartie - enabled, port: 0 + system.adapter.jarvis.0 : jarvis : smartie - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.mpd.0 : mpd : smartie - enabled, port: 6600 + system.adapter.mqtt.0 : mqtt : smartie - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.mqtt.1 : mqtt : smartie - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.telegram.0 : telegram : smartie - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.web.0 : web : smartie - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.zigbee.1 : zigbee : smartie - enabled, port: /dev/serial/by-id/usb-FTDI_FT230X_Basic_UART_DO00KJDU-if00-port0 ioBroker-Repositories ┌─────────┬──────────┬─────────────────────────────────────────────────────────┬──────────────┐ │ (index) │ name │ url │ auto upgrade │ ├─────────┼──────────┼─────────────────────────────────────────────────────────┼──────────────┤ │ 0 │ 'stable' │ 'http://download.iobroker.net/sources-dist.json' │ false │ │ 1 │ 'beta' │ 'http://download.iobroker.net/sources-dist-latest.json' │ false │ └─────────┴──────────┴─────────────────────────────────────────────────────────┴──────────────┘ Active repo(s): stable Upgrade policy: none Installed ioBroker-Instances Used repository: stable Adapter "admin" : 7.1.5 , installed 7.1.5 Adapter "alias-manager": 2.0.0 , installed 1.2.6 [Updatable] Adapter "backitup" : 3.0.25 , installed 3.0.25 Adapter "discovery" : 5.0.0 , installed 5.0.0 Adapter "history" : 3.0.1 , installed 3.0.1 Adapter "hm-rega" : 5.1.0 , installed 5.1.0 Adapter "hm-rpc" : 2.0.2 , installed 2.0.2 Adapter "iqontrol" : 3.0.0 , installed 2.3.0 [Updatable] Adapter "jarvis" : 3.1.8 , installed 3.1.8 Adapter "javascript" : 8.8.3 , installed 8.8.3 Controller "js-controller": 7.0.6 , installed 7.0.6 Adapter "mpd" : 2.2.0 , installed 2.2.0 Adapter "mqtt" : 6.1.2 , installed 6.1.2 Adapter "net-tools" : 1.0.11 , installed 1.0.11 Adapter "ping" : 1.6.2 , installed 1.6.2 Adapter "simple-api" : 2.8.0 , installed 2.8.0 Adapter "socketio" : 6.7.1 , installed 6.7.1 Adapter "telegram" : 3.9.0 , installed 3.9.0 Adapter "telegram-menu": 2.1.7 , installed 2.1.7 Adapter "vis" : 1.5.6 , installed 1.5.6 Adapter "web" : 6.2.5 , installed 6.2.5 Adapter "ws" : 2.6.2 , installed 2.6.2 Adapter "zigbee" : 1.10.14 , installed 1.10.14 Objects and States Please stand by - This may take a while Objects: 1980 States: 1429 *** OS-Repositories and Updates *** W: http://giteduberger.fr/rpimonitor/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details. 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://giteduberger.fr rpimonitor/ InRelease Hit:5 https://apt.debmatic.de/debmatic stable InRelease Hit:6 http://archive.raspberrypi.com/debian bookworm InRelease Hit:7 https://deb.nodesource.com/node_18.x nodistro InRelease Reading package lists... W: http://giteduberger.fr/rpimonitor/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details. 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:8888 0.0.0.0:* LISTEN 0 2902 765/perl tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 740 718/iobroker.js-con tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 732 718/iobroker.js-con tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 5846 728/sshd: /usr/sbin tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 0 2967 850/lighttpd tcp 0 0 0.0.0.0:8400 0.0.0.0:* LISTEN 1001 9155 2043/io.jarvis.0 tcp 0 0 127.0.0.1:2002 0.0.0.0:* LISTEN 1001 7560 1462/io.hm-rpc.0 tcp 0 0 127.0.0.1:2011 0.0.0.0:* LISTEN 1001 7009 1549/io.hm-rpc.1 tcp 0 0 0.0.0.0:1883 0.0.0.0:* LISTEN 1001 9649 1585/io.mqtt.0 tcp 0 0 0.0.0.0:8181 0.0.0.0:* LISTEN 0 2968 850/lighttpd tcp 0 0 0.0.0.0:8183 0.0.0.0:* LISTEN 0 7070 1742/ReGaHss.normal tcp 0 0 0.0.0.0:1999 0.0.0.0:* LISTEN 0 2970 850/lighttpd tcp 0 0 0.0.0.0:2010 0.0.0.0:* LISTEN 0 2972 850/lighttpd tcp 0 0 0.0.0.0:2000 0.0.0.0:* LISTEN 0 2978 850/lighttpd tcp 0 0 0.0.0.0:2001 0.0.0.0:* LISTEN 0 2976 850/lighttpd tcp 0 0 0.0.0.0:9292 0.0.0.0:* LISTEN 0 2974 850/lighttpd tcp 0 0 0.0.0.0:31999 0.0.0.0:* LISTEN 0 10532 1742/ReGaHss.normal tcp 0 0 127.0.0.1:9294 0.0.0.0:* LISTEN 1001 9709 1713/io.hm-rpc.2 tcp 0 0 0.0.0.0:32001 0.0.0.0:* LISTEN 0 6767 1182/rfd tcp 0 0 127.0.0.1:30080 0.0.0.0:* LISTEN 0 7216 1115/lighttpd tcp6 0 0 :::22 :::* LISTEN 0 5848 728/sshd: /usr/sbin tcp6 0 0 :::80 :::* LISTEN 0 2966 850/lighttpd tcp6 0 0 :::39292 :::* LISTEN 0 7022 1246/java tcp6 0 0 :::8081 :::* LISTEN 1001 8460 1023/io.admin.0 tcp6 0 0 :::8082 :::* LISTEN 1001 11588 1860/io.web.0 tcp6 0 0 :::8181 :::* LISTEN 0 2969 850/lighttpd tcp6 0 0 :::1999 :::* LISTEN 0 2971 850/lighttpd tcp6 0 0 :::2010 :::* LISTEN 0 2973 850/lighttpd tcp6 0 0 :::2000 :::* LISTEN 0 2979 850/lighttpd tcp6 0 0 :::2001 :::* LISTEN 0 2977 850/lighttpd tcp6 0 0 :::9292 :::* LISTEN 0 2975 850/lighttpd tcp6 0 0 :::9293 :::* LISTEN 0 6993 1246/java tcp6 0 0 :::32010 :::* LISTEN 0 7584 1246/java udp 0 0 0.0.0.0:41803 0.0.0.0:* 104 611 548/avahi-daemon: r udp 0 0 0.0.0.0:5353 0.0.0.0:* 104 609 548/avahi-daemon: r udp 0 0 0.0.0.0:1900 0.0.0.0:* 0 3067 1076/ssdpd udp 0 0 127.0.0.1:1998 0.0.0.0:* 0 7071 1742/ReGaHss.normal udp 0 0 127.0.0.1:8182 0.0.0.0:* 0 6730 1117/hss_led udp 0 0 0.0.0.0:43438 0.0.0.0:* 0 7563 1246/java udp 0 0 0.0.0.0:43439 0.0.0.0:* 0 3057 1068/eq3configd udp6 0 0 fe80::4755:7018:ab2:546 :::* 0 3005 654/NetworkManager udp6 0 0 :::45921 :::* 0 6874 1246/java udp6 0 0 :::5353 :::* 104 610 548/avahi-daemon: r udp6 0 0 :::57457 :::* 104 612 548/avahi-daemon: r *** Log File - Last 25 Lines *** 2025-01-05 01:11:56.083 - debug: zigbee.1 (6233) Objects create User PubSub Client 2025-01-05 01:11:56.117 - debug: zigbee.1 (6233) Objects client initialize lua scripts 2025-01-05 01:11:56.126 - debug: zigbee.1 (6233) Objects connected to redis: 127.0.0.1:9001 2025-01-05 01:11:56.159 - debug: zigbee.1 (6233) Redis States: Use Redis connection: 127.0.0.1:9000 2025-01-05 01:11:56.170 - debug: zigbee.1 (6233) States create System PubSub Client 2025-01-05 01:11:56.172 - debug: zigbee.1 (6233) States create User PubSub Client 2025-01-05 01:11:56.230 - debug: zigbee.1 (6233) States connected to redis: 127.0.0.1:9000 2025-01-05 01:11:56.273 - debug: zigbee.1 (6233) Plugin sentry Initialize Plugin (enabled=true) 2025-01-05 01:11:56.885 - info: zigbee.1 (6233) starting. Version 1.10.14 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.20.5, js-controller: 7.0.6 2025-01-05 01:11:56.918 - debug: zigbee.1 (6233) Using zigbee-herdsman with settings: {"network":{"panID":4576,"extendedPanID":[38,170,60,17,254,47,117,131],"channelList":[11],"networkKey":[1,3,5,7,9,11,13,15,0,2,4,6,8,10,12,13]},"databasePath":"/opt/iobroker/iobroker-data/zigbee_1/shepherd.db","backupPath":"/opt/iobroker/iobroker-data/zigbee_1/nvbackup.json","serialPort":{"baudRate":115200,"rtscts":false,"path":"/dev/serial/by-id/usb-FTDI_FT230X_Basic_UART_DO00KJDU-if00-port0","adapter":"deconz"},"adapter":{"forceStartWithInconsistentAdapterConfiguration":true},"legacy":false} 2025-01-05 01:11:57.011 - info: zigbee.1 (6233) delete old Backup files. keep only last 10 2025-01-05 01:11:57.013 - info: zigbee.1 (6233) Starting Zigbee npm ... 2025-01-05 01:11:57.062 - debug: zigbee.1 (6233) Starting zigbee-herdsman... 2025-01-05 01:11:57.437 - debug: zigbee.1 (6233) Backup /opt/iobroker/iobroker-data/zigbee_1/backup_2025_01_05-01_11_56.tar.gz success 2025-01-05 01:11:57.454 - info: zigbee.1 (6233) Installed Version: iobroker.zigbee@1.10.14 2025-01-05 01:12:08.135 - error: zigbee.1 (6233) Starting zigbee-herdsman problem : "TIMEOUT" 2025-01-05 01:12:08.137 - error: zigbee.1 (6233) Failed to start Zigbee 2025-01-05 01:12:08.137 - error: zigbee.1 (6233) Error herdsman start 2025-01-05 01:12:18.143 - info: zigbee.1 (6233) Try to reconnect. 1 attempts left 2025-01-05 01:12:18.146 - info: zigbee.1 (6233) Starting Zigbee npm ... 2025-01-05 01:12:18.166 - debug: zigbee.1 (6233) Starting zigbee-herdsman... 2025-01-05 01:12:18.193 - info: zigbee.1 (6233) Installed Version: iobroker.zigbee@1.10.14 2025-01-05 01:12:18.380 - error: zigbee.1 (6233) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'" 2025-01-05 01:12:18.380 - error: zigbee.1 (6233) Failed to start Zigbee 2025-01-05 01:12:18.381 - error: zigbee.1 (6233) Error herdsman start======================= SUMMARY ======================= v.2024-10-19 Static hostname: smartie Icon name: computer Operating System: Debian GNU/Linux 12 (bookworm) Kernel: Linux 6.6.62+rpt-rpi-v8 Architecture: arm64 Installation: native Kernel: aarch64 Userland: 64 bit Timezone: Europe/Berlin (CET, +0100) User-ID: 1000 Display-Server: false Boot Target: multi-user.target Pending OS-Updates: 0 Pending iob updates: 2 Nodejs-Installation: /usr/bin/nodejs v18.20.5 /usr/bin/node v18.20.5 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.29.4 Recommended versions are nodejs 20.18.1 and npm 10.8.2 nodeJS installation is correct MEMORY: total used free shared buff/cache available Mem: 4.0G 1.6G 1.7G 1.3M 735M 2.3G Swap: 209M 0B 209M Total: 4.2G 1.6G 1.9G Active iob-Instances: 7 Upgrade policy: none ioBroker Core: js-controller 7.0.6 admin 7.1.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 : smartie - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.web.0 : web : smartie - enabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 1980 States: 1433 Size of iob-Database: 6.7M /opt/iobroker/iobroker-data/objects.jsonl 1.4M /opt/iobroker/iobroker-data/states.jsonl Operating System is the current Debian stable version codenamed 'bookworm'! =================== END OF SUMMARY ==================== -
RE: Ikea Repeater an Zigbee Stickposted in ioBroker Allgemein
@amandus99 Hab damit auch ewig rum probiert, aber mit dem IKEA Repeater wollten sich weder meine Osram Steckdosen noch meine Xiaomi Sensoren verbinden. Habs aufgegeben und bin auf einen ConBee Stick umgestiegen. Der hat mehr Reichweite als mein voriger cc2531Stick. Die Osram Dosen als Repeater sind auch nur mäßig gut...
-
RE: [Gelöst] HomematicIP Thermostat heizt trotz Fenstersensorposted in Hardware
@amg_666 Danke für den Hinweis. Aber mein Script setzt keine Temperaturen. Einzig und alleine der Fenster-Status wird gesetzt.
-
RE: [Gelöst] HomematicIP Thermostat heizt trotz Fenstersensorposted in Hardware
Falls hier jemand in Zukunft das selbe Problem hat: Bei mir hat es jetzt geholfen, die eigene temperaturabhängige Fenster-Auf-Erkennung der Thermostate auszuschalten. Das geht in via CCU in den Einstellungen der Homematic IP Thermostate.
