Zigbee Adapter nach Versetzen geht nichts mehr
-
@strohhut sagte in Zigbee Adapter nach Versetzen geht nichts mehr:
Reicht fürs Backup der Backitup adapter?
Ja!
bei korrekter Konfiguration!@strohhut sagte in Zigbee Adapter nach Versetzen geht nichts mehr:
das ist was für Wochenende
dauert etwa 1-2h
Tipp: nimm eine neue SD-Karte. Dann hast du noch die alte als Backupaber mach erstmal das iob fiag mit der Raspi-Variante!
-
@homoran das habe ich schon gemacht. Der lief fehlerfrei durch.
Ich habe eine ssd im Raspi. Ich hatte überlegt, das ganze mit einer sd-Karte neuaufzusetzen und als Backup die Platte zu behalten.
Das wäre aber doppelte Arbeit. -
@strohhut sagte in Zigbee Adapter nach Versetzen geht nichts mehr:
Der lief fehlerfrei durch.
das heisst was?
Immer alles zeigen! -
@strohhut wie Homoran schon schrieb, alles zeigen. Wieder zurück auf SD-Karte würde ich keinesfalls mehr machen. In meinen Augen ein Rückschritt, den du nach geraumer Zeit bereuen wirst.
Ro75.
-
@ro75 sagte in Zigbee Adapter nach Versetzen geht nichts mehr:
Wieder zurück auf SD-Karte würde ich keinesfalls mehr machen. In meinen Augen ein Rückschritt,
[OT]
bin vom NUC mit SSD auf Pi5 mit 256GB SD zurück.
Hab in 10 Jahren mit SD und massiven Schreibvorgängen produktiv und auf bis zu 6 Testsystemen noch nie Probleme gehabt.
in 4 Jahren mit SSD 2x Totalausfall
[/OT] -
@homoran so Ich habe das Backup mit Neuaufsetzen von Linux durchgeführt.
Es läuft wiederBesten Dank euch.
Das einzige was aktuelle noch nicht will ist Java Script Adapter.
Der Adapter ist grün. Aber in jedem Script steht Instanz ist deaktiviert. -
@strohhut ok habs gefunden Javascript instanz hatte die Nummer 0 und ich hatte wohl die Nummer 1.
Lösung neue Instanz mit passender Nummer anlegen. -
@strohhut ich dreh durch. Seit Dienstag fängt es ohne Veränderung an zu zicken. Erst fehlten bei ein paar Geräten die Verbindung. Nach Neustart von Iobroker ging es wieder bis gestern. Weder findet er bekannte Geräte noch kann ich Geräte neuanlernen.
Kann es sein das mein Coordinator defekt ist?
Wie teste ich das am besten?iob diag geht ja jetzt
iob diag ========== Start marking the full check here =========== ```bash Script v.2024-10-19 *** BASE SYSTEM *** Static hostname: raspberrypi Icon name: computer Operating System: Debian GNU/Linux 12 (bookworm) Kernel: Linux 6.6.51+rpt-rpi-v8 Architecture: arm64 OS is similar to: Model : Raspberry Pi 4 Model B Rev 1.4 Docker : false Virtualization : none Kernel : aarch64 Userland : 64 bit Systemuptime and Load: 21:07:30 up 4:46, 2 users, load average: 0.54, 0.74, 0.54 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: Fri 2024-11-22 21:07:30 CET Universal time: Fri 2024-11-22 20:07:30 UTC RTC time: n/a 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: 8.2G 1.3G 6.3G 1.3M 794M 6.9G Swap: 209M 0B 209M Total: 8.4G 1.3G 6.5G Active iob-Instances: 16 7808 M total memory 1206 M used memory 1153 M active memory 495 M inactive memory 5968 M free memory 101 M buffer memory 656 M swap cache 199 M total swap 0 M used swap 199 M free swap *** top - Table Of Processes *** top - 21:07:31 up 4:46, 2 users, load average: 0.54, 0.74, 0.54 Tasks: 181 total, 1 running, 180 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 25.0 sy, 0.0 ni, 75.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 7809.0 total, 5967.2 free, 1207.3 used, 757.6 buff/cache MiB Swap: 200.0 total, 200.0 free, 0.0 used. 6601.6 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 3.6G 0 3.6G 0% /dev tmpfs tmpfs 781M 1.2M 780M 1% /run /dev/sda2 ext4 235G 5.2G 218G 3% / tmpfs tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs tmpfs 5.0M 16K 5.0M 1% /run/lock /dev/sda1 vfat 510M 64M 447M 13% /boot/firmware tmpfs tmpfs 781M 0 781M 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Fri Nov 22 16:21:13 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 smsc95xx.macaddr=E4:5F:01:47:30:46 vc_mem.mem_base=0x3eb00000 vc_mem.mem_size=0x3ff00000 console=ttyS0,115200 console=tty1 root=PARTUUID=212ef529-02 rootfstype=ext4 fsck.repair=yes rootwait [Fri Nov 22 16:21:16 2024] EXT4-fs (sda2): mounted filesystem 3b445224-0aeb-4897-9108-009ed4211fb4 ro with ordered data mode. Quota mode: none. [Fri Nov 22 16:21:17 2024] EXT4-fs (sda2): re-mounted 3b445224-0aeb-4897-9108-009ed4211fb4 r/w. Quota mode: none. Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/sda2 ext4 rw,noatime `-/boot/firmware /dev/sda1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 682M /var/ 206M /var/cache 200M /var/cache/apt 163M /var/lib 134M /var/lib/apt/lists Archived and active journals take up 112.0M in the file system. /opt/iobroker/backups: 43M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 882M /opt/iobroker/iobroker-data/ 744M /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 9.9M /opt/iobroker/iobroker-data/objects.jsonl 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 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-Texas_Instruments_XDS110__03.00.00.32__Embed_with_CMSIS-DAP_L1100PDQ-if03 /dev/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.32__Embed_with_CMSIS-DAP_L1100PDQ-if00 Your zigbee.0 COM-Port is matching 'by-id'. Very good! *** NodeJS-Installation *** /usr/bin/nodejs v20.18.1 /usr/bin/node v20.18.1 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.29.4 nodejs: Installed: 20.18.1-1nodesource1 Candidate: 20.18.1-1nodesource1 Version table: *** 20.18.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 100 /var/lib/dpkg/status 20.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.15.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.13.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.12.2-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.12.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.11.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.8.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.6.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.5.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.3.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.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 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: raspberrypi raspberrypi (version: 6.0.11, hostname: raspberrypi , alive, uptime: 423) Core adapters versions js-controller: 6.0.11 admin: 7.1.5 javascript: 8.8.3 nodejs modules from github: 0 Adapter State + system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin + system.adapter.backitup.0 : backitup : raspberrypi - enabled system.adapter.cloud.0 : cloud : raspberrypi - disabled system.adapter.daswetter.0 : daswetter : raspberrypi - enabled + system.adapter.device-watcher.0 : device-watcher : raspberrypi - enabled + system.adapter.discovery.0 : discovery : raspberrypi - enabled + system.adapter.email.0 : email : raspberrypi - enabled system.adapter.flot.0 : flot : raspberrypi - disabled + system.adapter.hausbus_de.0 : hausbus_de : raspberrypi - enabled + system.adapter.history.0 : history : raspberrypi - enabled + system.adapter.javascript.1 : javascript : raspberrypi - enabled + system.adapter.ping.0 : ping : raspberrypi - enabled + system.adapter.terminal.0 : terminal : raspberrypi - enabled, port: 8088, bind: 0.0.0.0, run as: admin + system.adapter.tr-064.0 : tr-064 : raspberrypi - enabled + system.adapter.tuya.0 : tuya : raspberrypi - enabled + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.yahka.0 : yahka : raspberrypi - enabled + system.adapter.zigbee.0 : zigbee : raspberrypi - enabled, port: /dev/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.32__Embed_with_CMSIS-DAP_L1100PDQ-if00 + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin + system.adapter.terminal.0 : terminal : raspberrypi - enabled, port: 8088, 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/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.32__Embed_with_CMSIS-DAP_L1100PDQ-if00 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 "backitup" : 3.0.25 , installed 3.0.25 Adapter "cloud" : 5.0.1 , installed 5.0.1 Adapter "daswetter" : 3.1.16 , installed 3.1.16 Adapter "device-watcher": 2.12.1 , installed 2.12.1 Adapter "discovery" : 5.0.0 , installed 5.0.0 Adapter "email" : 1.3.1 , installed 1.3.1 Adapter "flot" : 1.12.0 , installed 1.12.0 Adapter "hausbus_de" : 1.4.11 , installed 1.4.11 Adapter "history" : 3.0.1 , installed 3.0.1 Adapter "javascript" : 8.8.3 , installed 8.8.3 Controller "js-controller": 6.0.11 , installed 6.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 "terminal" : 1.0.0 , installed 1.0.0 Adapter "tr-064" : 4.3.0 , installed 4.3.0 Adapter "tuya" : 3.16.0 , installed 3.16.0 Adapter "web" : 6.2.5 , installed 6.2.5 Adapter "ws" : 2.6.2 , installed 2.6.2 Adapter "yahka" : 1.0.3 , installed 1.0.3 Adapter "zigbee" : 1.10.3 , installed 1.10.3 Objects and States Please stand by - This may take a while Objects: 5013 States: 4329 *** OS-Repositories and Updates *** Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://archive.raspberrypi.com/debian bookworm InRelease Hit:3 http://deb.debian.org/debian-security bookworm-security InRelease Hit:4 http://deb.debian.org/debian bookworm-updates InRelease Hit:5 https://deb.nodesource.com/node_20.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:42617 0.0.0.0:* LISTEN 1001 48932 5446/io.yahka.0 tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 47609 5158/iobroker.js-co tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 47614 5158/iobroker.js-co tcp 0 0 0.0.0.0:41121 0.0.0.0:* LISTEN 1001 49886 5446/io.yahka.0 tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 6560 654/sshd: /usr/sbin tcp6 0 0 :::8082 :::* LISTEN 1001 49863 5427/io.web.0 tcp6 0 0 :::8081 :::* LISTEN 1001 49444 5176/io.admin.0 tcp6 0 0 :::8088 :::* LISTEN 1001 50551 5412/io.terminal.0 tcp6 0 0 :::22 :::* LISTEN 0 6562 654/sshd: /usr/sbin udp 0 0 192.168.1.118:5353 0.0.0.0:* 1001 49643 5308/io.tr-064.0 udp 0 0 0.0.0.0:5353 0.0.0.0:* 104 1712 496/avahi-daemon: r udp 0 0 0.0.0.0:5855 0.0.0.0:* 1001 47963 5462/io.hausbus_de. udp 0 0 0.0.0.0:59625 0.0.0.0:* 104 1714 496/avahi-daemon: r udp 0 0 0.0.0.0:6666 0.0.0.0:* 1001 49710 5338/io.tuya.0 udp 0 0 0.0.0.0:6667 0.0.0.0:* 1001 49711 5338/io.tuya.0 udp6 0 0 fe80::2999:6bbc:b0c:546 :::* 0 1842 607/NetworkManager udp6 0 0 :::5353 :::* 104 1713 496/avahi-daemon: r udp6 0 0 :::42734 :::* 104 1715 496/avahi-daemon: r *** Log File - Last 25 Lines *** 2024-11-22 21:05:08.989 - info: hausbus_de.0 (5462) relay event evOff <- 32 Kanal IO Modul (2238).Ausgang_05, moduleType=11 2024-11-22 21:06:40.095 - info: hausbus_de.0 (5462) temperature sensor status: temperature = 41.69, state = HOT <- 32 Kanal IO Modul (2238).Temperatursensoren_ID1, moduleType=11 2024-11-22 21:06:40.101 - silly: yahka.0 (5446) States user redis pmessage hausbus_de.0.2238.Temperatursensoren.Temperatursensoren_ID1.temperature/hausbus_de.0.2238.Temperatursensoren.Temperatursensoren_ID1.temperature:{"val":41.69,"ack":true,"ts":1732306000099,"q":0,"from":"system.adapter.hausbus_de.0","user":"system.user.admin","lc":1732306000099} 2024-11-22 21:06:40.102 - debug: yahka.0 (5446) got a stateChange for [hausbus_de.0.2238.Temperatursensoren.Temperatursensoren_ID1.temperature] 2024-11-22 21:06:40.103 - debug: yahka.0 (5446) change event from ioBroker via [hausbus_de.0.2238.Temperatursensoren.Temperatursensoren_ID1.temperature]{"val":41.69,"ack":true,"ts":1732306000099,"q":0,"from":"system.adapter.hausbus_de.0","user":"system.user.admin","lc":1732306000099} 2024-11-22 21:06:40.103 - debug: yahka.0 (5446) [Vorlauftemperatur.CurrentTemperature] got a change notify event, ioValue: 41.69 2024-11-22 21:06:40.103 - debug: yahka.0 (5446) [Vorlauftemperatur.CurrentTemperature] forwarding value from ioBroker (41.69) to homekit as (41.69) 2024-11-22 21:06:40.103 - debug: yahka.0 (5446) [Vorlauftemperatur.CurrentTemperature] got a set event, hkValue: 41.700000000000045 2024-11-22 21:06:40.104 - debug: yahka.0 (5446) [Vorlauftemperatur.CurrentTemperature] set was initiated from ioBroker - exiting here 2024-11-22 21:08:01.169 - info: hausbus_de.0 (5462) temperature sensor status: temperature = 40.56, state = HOT <- 32 Kanal IO Modul (2238).Temperatursensoren_ID1, moduleType=11 2024-11-22 21:08:01.176 - silly: yahka.0 (5446) States user redis pmessage hausbus_de.0.2238.Temperatursensoren.Temperatursensoren_ID1.temperature/hausbus_de.0.2238.Temperatursensoren.Temperatursensoren_ID1.temperature:{"val":40.56,"ack":true,"ts":1732306081174,"q":0,"from":"system.adapter.hausbus_de.0","user":"system.user.admin","lc":1732306081174} 2024-11-22 21:08:01.177 - debug: yahka.0 (5446) got a stateChange for [hausbus_de.0.2238.Temperatursensoren.Temperatursensoren_ID1.temperature] 2024-11-22 21:08:01.178 - debug: yahka.0 (5446) change event from ioBroker via [hausbus_de.0.2238.Temperatursensoren.Temperatursensoren_ID1.temperature]{"val":40.56,"ack":true,"ts":1732306081174,"q":0,"from":"system.adapter.hausbus_de.0","user":"system.user.admin","lc":1732306081174} 2024-11-22 21:08:01.178 - debug: yahka.0 (5446) [Vorlauftemperatur.CurrentTemperature] got a change notify event, ioValue: 40.56 2024-11-22 21:08:01.179 - debug: yahka.0 (5446) [Vorlauftemperatur.CurrentTemperature] forwarding value from ioBroker (40.56) to homekit as (40.56) 2024-11-22 21:08:01.179 - debug: yahka.0 (5446) [Vorlauftemperatur.CurrentTemperature] got a set event, hkValue: 40.60000000000002 2024-11-22 21:08:01.180 - debug: yahka.0 (5446) [Vorlauftemperatur.CurrentTemperature] set was initiated from ioBroker - exiting here 2024-11-22 21:08:11.304 - info: hausbus_de.0 (5462) temperature sensor status: temperature = 47.75, state = HOT <- 32 Kanal IO Modul (2238).Temperatursensoren_ID3, moduleType=11 2024-11-22 21:08:11.310 - silly: yahka.0 (5446) States user redis pmessage hausbus_de.0.2238.Temperatursensoren.Temperatursensoren_ID3.temperature/hausbus_de.0.2238.Temperatursensoren.Temperatursensoren_ID3.temperature:{"val":47.75,"ack":true,"ts":1732306091308,"q":0,"from":"system.adapter.hausbus_de.0","user":"system.user.admin","lc":1732306091308} 2024-11-22 21:08:11.312 - debug: yahka.0 (5446) got a stateChange for [hausbus_de.0.2238.Temperatursensoren.Temperatursensoren_ID3.temperature] 2024-11-22 21:08:11.314 - debug: yahka.0 (5446) change event from ioBroker via [hausbus_de.0.2238.Temperatursensoren.Temperatursensoren_ID3.temperature]{"val":47.75,"ack":true,"ts":1732306091308,"q":0,"from":"system.adapter.hausbus_de.0","user":"system.user.admin","lc":1732306091308} 2024-11-22 21:08:11.314 - debug: yahka.0 (5446) [Warmwasser Haus.CurrentTemperature] got a change notify event, ioValue: 47.75 2024-11-22 21:08:11.315 - debug: yahka.0 (5446) [Warmwasser Haus.CurrentTemperature] forwarding value from ioBroker (47.75) to homekit as (47.75) 2024-11-22 21:08:11.315 - debug: yahka.0 (5446) [Warmwasser Haus.CurrentTemperature] got a set event, hkValue: 47.80000000000001 2024-11-22 21:08:11.315 - debug: yahka.0 (5446) [Warmwasser Haus.CurrentTemperature] set was initiated from ioBroker - exiting here============ Mark until here for C&P =============
iob diag has finished.
summary ======================= SUMMARY ======================= v.2024-10-19 Static hostname: raspberrypi Icon name: computer Operating System: Debian GNU/Linux 12 (bookworm) Kernel: Linux 6.6.51+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: 0 Nodejs-Installation: /usr/bin/nodejs v20.18.1 /usr/bin/node v20.18.1 /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: 8.2G 1.3G 6.2G 1.3M 795M 6.9G Swap: 209M 0B 209M Total: 8.4G 1.3G 6.4G Active iob-Instances: 16 Upgrade policy: none ioBroker Core: js-controller 6.0.11 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 : raspberrypi - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 5013 States: 4329 Size of iob-Database: 9.9M /opt/iobroker/iobroker-data/objects.jsonl 2.0M /opt/iobroker/iobroker-data/states.jsonl Operating System is the current Debian stable version codenamed 'bookworm'! =================== END OF SUMMARY ======================= Mark text until here for copying ===
-
@strohhut Wie ist der Kanal für Zigbee und WLAN 2,4GHz bei dir?
Ro75.
-
@strohhut wie ist die ssd angebunden ? USB 3 ?
A.
-
@ro75 zigbee 11
Wlan 13
möglichst weit getrennt -
@asgothian USB 3
-
@strohhut häng die ssd mal an usb2 und schau dann noch mal. Usb3 kann Störungen im 2.4 GHz Band machen,
A.
-
@asgothian das wird schwierig. Die SSD ist mit dem Raspi in einem Gehäuse festverbaut.
Störung würde mich auch wundern. Es lief 1,5 Jahre mit dem Gehäuse.
Mein Coordinator ist per USB-Kabel angeschlossen und sitzt außerhalb vom Netzwerkschrank. -
@asgothian ok jetzt hängt die Coordinator mitten im Raum an der Lampe und es geht. Die USB 3.0 Platten scheinen wirklick das Problem zu sein.
