NEWS
Zigbee Adapter nach Versetzen geht nichts mehr
-
Guten Abend,
Ich habe gestern mein Raspi samt Zigbee Cordinator CC26X2R1 aus meinem Keller in den Netzwerkschrank(Metal) versetzt. Der Cordinator liegt noch zu Testzwecken auf dem Schrank. Ich habe das System mit IObroker stop und linux herunterfahren abgeschaltet. Nach dem Anschließen von Netzwerkkabel, Stromkabel und dem CC26 am selben Port, wurde das System hochgefahren.
Es funktioniert alles. Nur ich bekomme den Zigbee Adapter nicht zum laufen. Er wird zwar grün nur es bekommt kein Gerät erreicht und stürzt ab.
Ich habe die cc26 schon neugeflasht und den Adapter neuinstalliert. Alles ohne erfolg.- Adaptername: Zigbee Adapter
- Adapterversion: 1.10.3
- js-controller Version: 6.0.11
- Admin Version: 7.1.5
- Hardwaresystem: Pi4b
- Arbeitsspeicher: 8GB
- Festplattenart: SSD,
- Betriebssystem: Raspbian GNU/Linux 10.13
- Nodejs-Version: 18.20.4
- NPM-Version: 10.7.0
- Installationsart: Skript oder Manuell ?
- Image, Docker genutzt: Nein
bei Iob Diag kommt folgendes
" *** iob diag is starting up, please wait ***
iob diag needs to be updated. Please execute 'iobroker fix' first."Iobroker Fix läuft ohne Probleme durch.
Auszug aus meinem Log
2024-11-04 21:31:22.386 - info: admin.0 (7517) ==> Connected system.user.admin from ::ffff:192.168.1.43 2024-11-04 21:31:40.430 - silly: yahka.0 (7784) States user redis pmessage ping.0.Iobroker.Hausbus.alive/ping.0.Iobroker.Hausbus.alive:{"val":true,"ack":true,"ts":1730752300427,"q":0,"from":"system.adapter.ping.0","user":"system.user.admin","lc":1726510822358} 2024-11-04 21:31:40.430 - debug: yahka.0 (7784) got a stateChange for [ping.0.Iobroker.Hausbus.alive] 2024-11-04 21:31:40.431 - debug: yahka.0 (7784) change event from ioBroker via [ping.0.Iobroker.Hausbus.alive]{"val":1,"ack":true,"ts":1730752300427,"q":0,"from":"system.adapter.ping.0","user":"system.user.admin","lc":1726510822358} 2024-11-04 21:31:40.431 - debug: yahka.0 (7784) [Steuerung Heizung.LeakDetected] got a change notify event, ioValue: 1 2024-11-04 21:31:40.431 - debug: yahka.0 (7784) script: converting value to homekit: 1 to 0 2024-11-04 21:31:40.432 - debug: yahka.0 (7784) [Steuerung Heizung.LeakDetected] forwarding value from ioBroker (1) to homekit as (0) 2024-11-04 21:31:40.432 - debug: yahka.0 (7784) [Steuerung Heizung.LeakDetected] got a set event, hkValue: 0 2024-11-04 21:31:40.432 - debug: yahka.0 (7784) [Steuerung Heizung.LeakDetected] set was initiated from ioBroker - exiting here 2024-11-04 21:31:48.663 - info: admin.0 (7517) <== Disconnect system.user.admin from ::ffff:192.168.1.43 2024-11-04 21:31:52.381 - info: host.Iobroker "system.adapter.zigbee.0" enabled 2024-11-04 21:31:53.130 - info: host.Iobroker instance system.adapter.zigbee.0 in version "1.10.3" started with pid 16409 2024-11-04 21:31:56.225 - info: admin.0 (7517) ==> Connected system.user.admin from ::ffff:192.168.1.43 2024-11-04 21:31:57.204 - info: admin.0 (7517) <== Disconnect system.user.admin from ::ffff:192.168.1.43 2024-11-04 21:31:59.235 - info: zigbee.0 (16409) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.20.4, js-controller: 6.0.11 2024-11-04 21:31:59.346 - info: zigbee.0 (16409) delete old Backup files. keep only last 10 2024-11-04 21:31:59.348 - info: zigbee.0 (16409) Starting Zigbee npm ... 2024-11-04 21:31:59.765 - info: zigbee.0 (16409) Installed Version: iobroker.zigbee@1.10.3 2024-11-04 21:32:00.548 - info: zigbee.0 (16409) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20240710}} 2024-11-04 21:32:00.556 - info: zigbee.0 (16409) Unable to disable LED, unsupported function. 2024-11-04 21:32:00.578 - info: zigbee.0 (16409) --> transmitPower : high+ 2024-11-04 21:32:00.599 - info: zigbee.0 (16409) Currently 29 devices are joined: 2024-11-04 21:32:00.718 - info: zigbee.0 (16409) 0x00124b0024c22616 (addr 26839): ZBMINI - SONOFF Zigbee two way smart switch (Router) 2024-11-04 21:32:00.724 - info: zigbee.0 (16409) 0x9035eafffebcff11 (addr 64552): HK-LN-DIM-A - LED-Trading ZigBee AC phase-cut dimmer (Router) 2024-11-04 21:32:00.726 - info: zigbee.0 (16409) 0x00124b0024c15733 (addr 52314): ZBMINI - SONOFF Zigbee two way smart switch (Router) 2024-11-04 21:32:00.729 - info: zigbee.0 (16409) 0xa4c13890c4ba3da2 (addr 59326): QS-Zigbee-SEC02-U - TuYa Zigbee 3.0 smart light switch module 2 gang (Router) 2024-11-04 21:32:00.731 - info: zigbee.0 (16409) 0x00124b0024c22525 (addr 830): ZBMINI - SONOFF Zigbee two way smart switch (Router) 2024-11-04 21:32:00.733 - info: zigbee.0 (16409) 0x804b50fffe0bc2d8 (addr 63185): HS1SA - HEIMAN Smoke detector (EndDevice) 2024-11-04 21:32:00.735 - info: zigbee.0 (16409) 0x847127fffefea95e (addr 17208): HS1SA - HEIMAN Smoke detector (EndDevice) 2024-11-04 21:32:00.736 - info: zigbee.0 (16409) 0x804b50fffe1f2a44 (addr 40100): HS1SA - HEIMAN Smoke detector (EndDevice) 2024-11-04 21:32:00.741 - info: zigbee.0 (16409) 0x04cd15fffe6fa638 (addr 33289): LED1949C5 - IKEA TRADFRI bulb E12/E14, white spectrum, candle, opal, 450/470 lm (Router) 2024-11-04 21:32:00.745 - info: zigbee.0 (16409) 0x04cd15fffe76fb1b (addr 20585): LED1949C5 - IKEA TRADFRI bulb E12/E14, white spectrum, candle, opal, 450/470 lm (Router) 2024-11-04 21:32:00.748 - info: zigbee.0 (16409) 0xa4c1386681d51234 (addr 31828): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router) 2024-11-04 21:32:00.750 - info: zigbee.0 (16409) 0xa4c1389455b12347 (addr 56966): TS0203 - TuYa Door sensor (EndDevice) 2024-11-04 21:32:00.754 - info: zigbee.0 (16409) 0xa4c13877140b72c3 (addr 21028): TS0203 - TuYa Door sensor (EndDevice) 2024-11-04 21:32:00.759 - info: zigbee.0 (16409) 0x04cd15fffe37a7b0 (addr 18671): BAC-002-ALZB - TuYa FCU thermostat temperature controller (Router) 2024-11-04 21:32:00.762 - info: zigbee.0 (16409) 0xa4c138f3b6913cc4 (addr 3272): PJ-ZGD01 - TuYa Garage door opener (Router) 2024-11-04 21:32:00.765 - info: zigbee.0 (16409) 0xa4c138993ecf2bc5 (addr 56812): TS0203 - TuYa Door sensor (EndDevice) 2024-11-04 21:32:00.770 - info: zigbee.0 (16409) 0xa4c1385a9568eed8 (addr 13753): TS0203 - TuYa Door sensor (EndDevice) 2024-11-04 21:32:00.775 - info: zigbee.0 (16409) 0xa4c138c9efe5fad7 (addr 16084): ZTH08-E - TuYa Temperature and humidity sensor (EndDevice) 2024-11-04 21:32:00.779 - info: zigbee.0 (16409) 0xa4c138591aba0ecb (addr 46600): TS110E_2gang_1 - TuYa 2 channel dimmer (Router) 2024-11-04 21:32:00.782 - info: zigbee.0 (16409) 0x0c4314fffe1f9619 (addr 26798): ID-UK21FW09 - Iolloi Zigbee LED smart dimmer switch (Router) 2024-11-04 21:32:00.785 - info: zigbee.0 (16409) 0xa4c138691c571663 (addr 21710): PJ-ZGD01 - TuYa Garage door opener (Router) 2024-11-04 21:32:00.786 - info: zigbee.0 (16409) 0xa4c1381e60ceb625 (addr 63996): TS0203 - TuYa Door sensor (EndDevice) 2024-11-04 21:32:00.788 - info: zigbee.0 (16409) 0xa4c13845f806ea6a (addr 47861): TS0201 - TuYa Temperature & humidity sensor with display (EndDevice) 2024-11-04 21:32:00.791 - info: zigbee.0 (16409) 0xa4c1388f54e0454a (addr 65120): PA-44Z - TuYa Photoelectric smoke detector (EndDevice) 2024-11-04 21:32:00.794 - info: zigbee.0 (16409) 0xa4c1387621f5dc5f (addr 5749): PA-44Z - TuYa Photoelectric smoke detector (EndDevice) 2024-11-04 21:32:00.797 - info: zigbee.0 (16409) 0xa4c138d847588b1c (addr 15616): PA-44Z - TuYa Photoelectric smoke detector (EndDevice) 2024-11-04 21:32:00.801 - info: zigbee.0 (16409) 0xa4c138024cc800a4 (addr 51643): PA-44Z - TuYa Photoelectric smoke detector (EndDevice) 2024-11-04 21:32:00.804 - info: zigbee.0 (16409) 0xa4c13824409b30e3 (addr 20378): PA-44Z - TuYa Photoelectric smoke detector (EndDevice) 2024-11-04 21:32:00.806 - info: zigbee.0 (16409) 0x00124b0024c14ab5 (addr 33706): ZBMINI - SONOFF Zigbee two way smart switch (Router) 2024-11-04 21:32:00.807 - info: zigbee.0 (16409) Zigbee started 2024-11-04 21:32:00.968 - info: zigbee.0 (16409) debug devices set to [] 2024-11-04 21:32:01.495 - silly: yahka.0 (7784) States user redis pmessage zigbee.0.a4c138c9efe5fad7.available/zigbee.0.a4c138c9efe5fad7.available:{"val":true,"ack":true,"ts":1730752321468,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1730752321468} 2024-11-04 21:32:01.496 - debug: yahka.0 (7784) got a stateChange for [zigbee.0.a4c138c9efe5fad7.available] 2024-11-04 21:32:01.497 - debug: yahka.0 (7784) change event from ioBroker via [zigbee.0.a4c138c9efe5fad7.available]{"val":1,"ack":true,"ts":1730752321468,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1730752321468} 2024-11-04 21:32:01.497 - debug: yahka.0 (7784) [Raumfühler Küche.StatusActive] got a change notify event, ioValue: 1 2024-11-04 21:32:01.497 - debug: yahka.0 (7784) [Raumfühler Küche.StatusActive] forwarding value from ioBroker (1) to homekit as (1) 2024-11-04 21:32:01.497 - debug: yahka.0 (7784) [Raumfühler Küche.StatusActive] got a set event, hkValue: true 2024-11-04 21:32:01.498 - debug: yahka.0 (7784) [Raumfühler Küche.StatusActive] set was initiated from ioBroker - exiting here 2024-11-04 21:32:01.505 - silly: yahka.0 (7784) States user redis pmessage zigbee.0.a4c13845f806ea6a.available/zigbee.0.a4c13845f806ea6a.available:{"val":true,"ack":true,"ts":1730752321469,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1730752321469} 2024-11-04 21:32:01.506 - debug: yahka.0 (7784) got a stateChange for [zigbee.0.a4c13845f806ea6a.available] 2024-11-04 21:32:01.506 - debug: yahka.0 (7784) change event from ioBroker via [zigbee.0.a4c13845f806ea6a.available]{"val":1,"ack":true,"ts":1730752321469,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1730752321469} 2024-11-04 21:32:01.507 - debug: yahka.0 (7784) [Raumfühler Einliegerwohnung.StatusActive] got a change notify event, ioValue: 1 2024-11-04 21:32:01.507 - debug: yahka.0 (7784) [Raumfühler Einliegerwohnung.StatusActive] forwarding value from ioBroker (1) to homekit as (1) 2024-11-04 21:32:01.507 - debug: yahka.0 (7784) [Raumfühler Einliegerwohnung.StatusActive] got a set event, hkValue: true 2024-11-04 21:32:01.507 - debug: yahka.0 (7784) [Raumfühler Einliegerwohnung.StatusActive] set was initiated from ioBroker - exiting here 2024-11-04 21:32:02.058 - silly: yahka.0 (7784) States user redis pmessage zigbee.0.a4c138c9efe5fad7.available/zigbee.0.a4c138c9efe5fad7.available:{"val":true,"ack":true,"ts":1730752322022,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1730752321468} 2024-11-04 21:32:02.058 - debug: yahka.0 (7784) got a stateChange for [zigbee.0.a4c138c9efe5fad7.available] 2024-11-04 21:32:02.058 - debug: yahka.0 (7784) change event from ioBroker via [zigbee.0.a4c138c9efe5fad7.available]{"val":1,"ack":true,"ts":1730752322022,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1730752321468} 2024-11-04 21:32:02.059 - debug: yahka.0 (7784) [Raumfühler Küche.StatusActive] got a change notify event, ioValue: 1 2024-11-04 21:32:02.059 - debug: yahka.0 (7784) [Raumfühler Küche.StatusActive] forwarding value from ioBroker (1) to homekit as (1) 2024-11-04 21:32:02.059 - debug: yahka.0 (7784) [Raumfühler Küche.StatusActive] got a set event, hkValue: true 2024-11-04 21:32:02.059 - debug: yahka.0 (7784) [Raumfühler Küche.StatusActive] set was initiated from ioBroker - exiting here 2024-11-04 21:32:02.074 - silly: yahka.0 (7784) States user redis pmessage zigbee.0.a4c13845f806ea6a.available/zigbee.0.a4c13845f806ea6a.available:{"val":true,"ack":true,"ts":1730752322026,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1730752321469} 2024-11-04 21:32:02.075 - debug: yahka.0 (7784) got a stateChange for [zigbee.0.a4c13845f806ea6a.available] 2024-11-04 21:32:02.075 - debug: yahka.0 (7784) change event from ioBroker via [zigbee.0.a4c13845f806ea6a.available]{"val":1,"ack":true,"ts":1730752322026,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1730752321469} 2024-11-04 21:32:02.075 - debug: yahka.0 (7784) [Raumfühler Einliegerwohnung.StatusActive] got a change notify event, ioValue: 1 2024-11-04 21:32:02.076 - debug: yahka.0 (7784) [Raumfühler Einliegerwohnung.StatusActive] forwarding value from ioBroker (1) to homekit as (1) 2024-11-04 21:32:02.076 - debug: yahka.0 (7784) [Raumfühler Einliegerwohnung.StatusActive] got a set event, hkValue: true 2024-11-04 21:32:02.076 - debug: yahka.0 (7784) [Raumfühler Einliegerwohnung.StatusActive] set was initiated from ioBroker - exiting here 2024-11-04 21:32:03.085 - warn: zigbee.0 (16409) DeviceAvailability:Failed to ping 0x04cd15fffe37a7b0 TS0601 2024-11-04 21:32:03.275 - warn: zigbee.0 (16409) DeviceAvailability:Failed to ping 0xa4c138f3b6913cc4 TS0601 2024-11-04 21:32:04.722 - warn: zigbee.0 (16409) DeviceAvailability:Failed to ping 0xa4c138691c571663 TS0601 2024-11-04 21:32:11.583 - warn: zigbee.0 (16409) DeviceAvailability:Failed to ping 0xa4c13890c4ba3da2 TS000F 2024-11-04 21:32:11.624 - warn: zigbee.0 (16409) DeviceAvailability:Failed to ping 0x00124b0024c15733 01MINIZB 2024-11-04 21:32:11.672 - warn: zigbee.0 (16409) DeviceAvailability:Failed to ping 0x00124b0024c22525 01MINIZB 2024-11-04 21:32:11.717 - warn: zigbee.0 (16409) DeviceAvailability:Failed to ping 0xa4c1386681d51234 TS011F 2024-11-04 21:32:11.929 - warn: zigbee.0 (16409) DeviceAvailability:Failed to ping 0xa4c138591aba0ecb TS110E 2024-11-04 21:32:12.194 - warn: zigbee.0 (16409) DeviceAvailability:Failed to ping 0x0c4314fffe1f9619 Dimmer-Switch-ZB3.0 2024-11-04 21:32:12.757 - warn: zigbee.0 (16409) DeviceAvailability:Failed to ping 0x00124b0024c14ab5 01MINIZB 2024-11-04 21:32:13.799 - info: hausbusde.0 (7862) temperature sensor status: temperature = 29.06, state = HOT <- 32 Kanal IO Modul (2238).Temperatursensoren_ID1 2024-11-04 21:32:13.811 - silly: yahka.0 (7784) States user redis pmessage hausbusde.0.2238.Temperatursensoren.Temperatursensoren_ID1.temperature/hausbusde.0.2238.Temperatursensoren.Temperatursensoren_ID1.temperature:{"val":29.06,"ack":true,"ts":1730752333806,"q":0,"from":"system.adapter.hausbusde.0","user":"system.user.admin","lc":1730752333806} 2024-11-04 21:32:13.812 - debug: yahka.0 (7784) got a stateChange for [hausbusde.0.2238.Temperatursensoren.Temperatursensoren_ID1.temperature] 2024-11-04 21:32:13.813 - debug: yahka.0 (7784) change event from ioBroker via [hausbusde.0.2238.Temperatursensoren.Temperatursensoren_ID1.temperature]{"val":29.06,"ack":true,"ts":1730752333806,"q":0,"from":"system.adapter.hausbusde.0","user":"system.user.admin","lc":1730752333806} 2024-11-04 21:32:13.813 - debug: yahka.0 (7784) [Vorlauftemperatur.CurrentTemperature] got a change notify event, ioValue: 29.06 2024-11-04 21:32:13.814 - debug: yahka.0 (7784) [Vorlauftemperatur.CurrentTemperature] forwarding value from ioBroker (29.06) to homekit as (29.06) 2024-11-04 21:32:13.814 - debug: yahka.0 (7784) [Vorlauftemperatur.CurrentTemperature] got a set event, hkValue: 29.100000000000023 2024-11-04 21:32:13.814 - debug: yahka.0 (7784) [Vorlauftemperatur.CurrentTemperature] set was initiated from ioBroker - exiting here 2024-11-04 21:32:13.832 - silly: yahka.0 (7784) States user redis pmessage hausbusde.0.2238.Relais.Ausgang_05.on_off/hausbusde.0.2238.Relais.Ausgang_05.on_off:{"val":false,"ack":false,"ts":1730752333810,"q":0,"c":"script.js.common.Heizung.Brenner","from":"system.adapter.javascript.1","user":"system.user.admin","lc":1730750460241} 2024-11-04 21:32:13.834 - info: hausbusde.0 (7862) Call: state=on_off, newValue = false -> 32 Kanal IO Modul (2238).Ausgang_05 2024-11-04 21:32:13.834 - info: hausbusde.0 (7862) relay off offDelay = 0 -> 32 Kanal IO Modul (2238).Ausgang_05 2024-11-04 21:32:13.835 - debug: yahka.0 (7784) got a stateChange for [hausbusde.0.2238.Relais.Ausgang_05.on_off] 2024-11-04 21:32:13.838 - debug: yahka.0 (7784) change event from ioBroker via [hausbusde.0.2238.Relais.Ausgang_05.on_off]{"val":0,"ack":false,"ts":1730752333810,"q":0,"c":"script.js.common.Heizung.Brenner","from":"system.adapter.javascript.1","user":"system.user.admin","lc":1730750460241} 2024-11-04 21:32:13.839 - debug: yahka.0 (7784) [Brenner.On] got a change notify event, ioValue: 0 2024-11-04 21:32:13.839 - debug: yahka.0 (7784) [Brenner.On] forwarding value from ioBroker (0) to homekit as (0) 2024-11-04 21:32:13.841 - debug: yahka.0 (7784) [Brenner.On] got a set event, hkValue: false 2024-11-04 21:32:13.842 - debug: yahka.0 (7784) [Brenner.On] set was initiated from ioBroker - exiting here 2024-11-04 21:32:13.872 - info: hausbusde.0 (7862) relay event evOff <- 32 Kanal IO Modul (2238).Ausgang_05 2024-11-04 21:32:18.233 - info: zigbee.0 (16409) Device '0xa4c138c9efe5fad7' announced itself 2024-11-04 21:32:19.257 - silly: yahka.0 (7784) States user redis pmessage zigbee.0.a4c138c9efe5fad7.available/zigbee.0.a4c138c9efe5fad7.available:{"val":true,"ack":true,"ts":1730752339254,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1730752321468} 2024-11-04 21:32:19.257 - debug: yahka.0 (7784) got a stateChange for [zigbee.0.a4c138c9efe5fad7.available] 2024-11-04 21:32:19.258 - debug: yahka.0 (7784) change event from ioBroker via [zigbee.0.a4c138c9efe5fad7.available]{"val":1,"ack":true,"ts":1730752339254,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1730752321468} 2024-11-04 21:32:19.258 - debug: yahka.0 (7784) [Raumfühler Küche.StatusActive] got a change notify event, ioValue: 1 2024-11-04 21:32:19.258 - debug: yahka.0 (7784) [Raumfühler Küche.StatusActive] forwarding value from ioBroker (1) to homekit as (1) 2024-11-04 21:32:19.258 - debug: yahka.0 (7784) [Raumfühler Küche.StatusActive] got a set event, hkValue: true 2024-11-04 21:32:19.258 - debug: yahka.0 (7784) [Raumfühler Küche.StatusActive] set was initiated from ioBroker - exiting here 2024-11-04 21:32:24.054 - warn: zigbee.0 (16409) DeviceAvailability:Failed to ping 0x9035eafffebcff11 HK-LN-DIM-A 2024-11-04 21:32:24.642 - warn: zigbee.0 (16409) DeviceAvailability:Failed to ping 0x00124b0024c22616 01MINIZB 2024-11-04 21:32:25.665 - warn: zigbee.0 (16409) DeviceAvailability:Failed to ping 0x04cd15fffe6fa638 TRADFRIbulbE14WScandleopal470lm 2024-11-04 21:32:26.475 - warn: zigbee.0 (16409) DeviceAvailability:Failed to ping 0x04cd15fffe76fb1b TRADFRIbulbE14WScandleopal470lm 2024-11-04 21:32:36.124 - info: hausbusde.0 (7862) temperature sensor status: temperature = 47.00, state = HOT <- 32 Kanal IO Modul (2238).Temperatursensoren_ID3 2024-11-04 21:32:36.140 - silly: yahka.0 (7784) States user redis pmessage hausbusde.0.2238.Temperatursensoren.Temperatursensoren_ID3.temperature/hausbusde.0.2238.Temperatursensoren.Temperatursensoren_ID3.temperature:{"val":47,"ack":true,"ts":1730752356135,"q":0,"from":"system.adapter.hausbusde.0","user":"system.user.admin","lc":1730752356135} 2024-11-04 21:32:36.141 - debug: yahka.0 (7784) got a stateChange for [hausbusde.0.2238.Temperatursensoren.Temperatursensoren_ID3.temperature] 2024-11-04 21:32:36.142 - debug: yahka.0 (7784) change event from ioBroker via [hausbusde.0.2238.Temperatursensoren.Temperatursensoren_ID3.temperature]{"val":47,"ack":true,"ts":1730752356135,"q":0,"from":"system.adapter.hausbusde.0","user":"system.user.admin","lc":1730752356135} 2024-11-04 21:32:36.143 - debug: yahka.0 (7784) [Warmwasser Wohnung.CurrentTemperature] got a change notify event, ioValue: 47 2024-11-04 21:32:36.144 - debug: yahka.0 (7784) [Warmwasser Wohnung.CurrentTemperature] forwarding value from ioBroker (47) to homekit as (47) 2024-11-04 21:32:36.144 - debug: yahka.0 (7784) [Warmwasser Wohnung.CurrentTemperature] got a set event, hkValue: 47 2024-11-04 21:32:36.145 - debug: yahka.0 (7784) [Warmwasser Wohnung.CurrentTemperature] set was initiated from ioBroker - exiting here 2024-11-04 21:32:36.157 - info: hausbusde.0 (7862) Call: state=on_off, newValue = true -> 32 Kanal IO Modul (2238).Ausgang_04 2024-11-04 21:32:36.158 - info: hausbusde.0 (7862) relay on duration = 0, onDelay = 0 -> 32 Kanal IO Modul (2238).Ausgang_04 2024-11-04 21:32:36.155 - silly: yahka.0 (7784) States user redis pmessage hausbusde.0.2238.Relais.Ausgang_04.on_off/hausbusde.0.2238.Relais.Ausgang_04.on_off:{"val":true,"ack":false,"ts":1730752356138,"q":0,"c":"script.js.common.Heizung.Haus-Warmwassersteuerung","from":"system.adapter.javascript.1","user":"system.user.admin","lc":1730752356138} 2024-11-04 21:32:36.157 - debug: yahka.0 (7784) got a stateChange for [hausbusde.0.2238.Relais.Ausgang_04.on_off] 2024-11-04 21:32:36.158 - debug: yahka.0 (7784) change event from ioBroker via [hausbusde.0.2238.Relais.Ausgang_04.on_off]{"val":1,"ack":false,"ts":1730752356138,"q":0,"c":"script.js.common.Heizung.Haus-Warmwassersteuerung","from":"system.adapter.javascript.1","user":"system.user.admin","lc":1730752356138} 2024-11-04 21:32:36.158 - debug: yahka.0 (7784) [Warmwasserpumpe Wohnung.On] got a change notify event, ioValue: 1 2024-11-04 21:32:36.159 - debug: yahka.0 (7784) [Warmwasserpumpe Wohnung.On] forwarding value from ioBroker (1) to homekit as (1) 2024-11-04 21:32:36.159 - debug: yahka.0 (7784) [Warmwasserpumpe Wohnung.On] got a set event, hkValue: true 2024-11-04 21:32:36.159 - debug: yahka.0 (7784) [Warmwasserpumpe Wohnung.On] set was initiated from ioBroker - exiting here 2024-11-04 21:32:36.184 - info: hausbusde.0 (7862) relay event evOn <- 32 Kanal IO Modul (2238).Ausgang_04 2024-11-04 21:32:36.192 - silly: yahka.0 (7784) States user redis pmessage hausbusde.0.2238.Relais.Ausgang_01.on_off/hausbusde.0.2238.Relais.Ausgang_01.on_off:{"val":false,"ack":false,"ts":1730752356153,"q":0,"c":"script.js.common.Heizung.Wasserwarmvorrangschaltung","from":"system.adapter.javascript.1","user":"system.user.admin","lc":1730752356153} 2024-11-04 21:32:36.193 - info: hausbusde.0 (7862) Call: state=on_off, newValue = false -> 32 Kanal IO Modul (2238).Ausgang_01 2024-11-04 21:32:36.194 - info: hausbusde.0 (7862) relay off offDelay = 0 -> 32 Kanal IO Modul (2238).Ausgang_01 2024-11-04 21:32:36.193 - debug: yahka.0 (7784) got a stateChange for [hausbusde.0.2238.Relais.Ausgang_01.on_off] 2024-11-04 21:32:36.193 - debug: yahka.0 (7784) change event from ioBroker via [hausbusde.0.2238.Relais.Ausgang_01.on_off]{"val":0,"ack":false,"ts":1730752356153,"q":0,"c":"script.js.common.Heizung.Wasserwarmvorrangschaltung","from":"system.adapter.javascript.1","user":"system.user.admin","lc":1730752356153} 2024-11-04 21:32:36.194 - debug: yahka.0 (7784) [Heizungspumpe Haus.On] got a change notify event, ioValue: 0 2024-11-04 21:32:36.194 - debug: yahka.0 (7784) [Heizungspumpe Haus.On] forwarding value from ioBroker (0) to homekit as (0) 2024-11-04 21:32:36.195 - debug: yahka.0 (7784) [Heizungspumpe Haus.On] got a set event, hkValue: false 2024-11-04 21:32:36.195 - debug: yahka.0 (7784) [Heizungspumpe Haus.On] set was initiated from ioBroker - exiting here 2024-11-04 21:32:36.200 - silly: yahka.0 (7784) States user redis pmessage hausbusde.0.2238.Relais.Ausgang_02.on_off/hausbusde.0.2238.Relais.Ausgang_02.on_off:{"val":false,"ack":false,"ts":1730752356153,"q":0,"c":"script.js.common.Heizung.Wasserwarmvorrangschaltung","from":"system.adapter.javascript.1","user":"system.user.admin","lc":1730752356153} 2024-11-04 21:32:36.201 - info: hausbusde.0 (7862) Call: state=on_off, newValue = false -> 32 Kanal IO Modul (2238).Ausgang_02 2024-11-04 21:32:36.202 - debug: yahka.0 (7784) got a stateChange for [hausbusde.0.2238.Relais.Ausgang_02.on_off] 2024-11-04 21:32:36.201 - info: hausbusde.0 (7862) relay off offDelay = 0 -> 32 Kanal IO Modul (2238).Ausgang_02 2024-11-04 21:32:36.203 - debug: yahka.0 (7784) change event from ioBroker via [hausbusde.0.2238.Relais.Ausgang_02.on_off]{"val":0,"ack":false,"ts":1730752356153,"q":0,"c":"script.js.common.Heizung.Wasserwarmvorrangschaltung","from":"system.adapter.javascript.1","user":"system.user.admin","lc":1730752356153} 2024-11-04 21:32:36.203 - debug: yahka.0 (7784) [Heizungspumpe Wohnung.On] got a change notify event, ioValue: 0 2024-11-04 21:32:36.203 - debug: yahka.0 (7784) [Heizungspumpe Wohnung.On] forwarding value from ioBroker (0) to homekit as (0) 2024-11-04 21:32:36.203 - debug: yahka.0 (7784) [Heizungspumpe Wohnung.On] got a set event, hkValue: false 2024-11-04 21:32:36.203 - debug: yahka.0 (7784) [Heizungspumpe Wohnung.On] set was initiated from ioBroker - exiting here 2024-11-04 21:32:36.204 - info: hausbusde.0 (7862) Call: state=on_off, newValue = true -> 32 Kanal IO Modul (2238).Ausgang_05 2024-11-04 21:32:36.205 - info: hausbusde.0 (7862) relay on duration = 0, onDelay = 0 -> 32 Kanal IO Modul (2238).Ausgang_05 2024-11-04 21:32:36.208 - silly: yahka.0 (7784) States user redis pmessage hausbusde.0.2238.Relais.Ausgang_05.on_off/hausbusde.0.2238.Relais.Ausgang_05.on_off:{"val":true,"ack":false,"ts":1730752356153,"q":0,"c":"script.js.common.Heizung.Brenner","from":"system.adapter.javascript.1","user":"system.user.admin","lc":1730752356153} 2024-11-04 21:32:36.209 - debug: yahka.0 (7784) got a stateChange for [hausbusde.0.2238.Relais.Ausgang_05.on_off] 2024-11-04 21:32:36.209 - debug: yahka.0 (7784) change event from ioBroker via [hausbusde.0.2238.Relais.Ausgang_05.on_off]{"val":1,"ack":false,"ts":1730752356153,"q":0,"c":"script.js.common.Heizung.Brenner","from":"system.adapter.javascript.1","user":"system.user.admin","lc":1730752356153} 2024-11-04 21:32:36.209 - debug: yahka.0 (7784) [Brenner.On] got a change notify event, ioValue: 1 2024-11-04 21:32:36.209 - debug: yahka.0 (7784) [Brenner.On] forwarding value from ioBroker (1) to homekit as (1) 2024-11-04 21:32:36.209 - debug: yahka.0 (7784) [Brenner.On] got a set event, hkValue: true 2024-11-04 21:32:36.210 - debug: yahka.0 (7784) [Brenner.On] set was initiated from ioBroker - exiting here 2024-11-04 21:32:36.214 - info: hausbusde.0 (7862) relay event evOff <- 32 Kanal IO Modul (2238).Ausgang_01 2024-11-04 21:32:36.245 - info: hausbusde.0 (7862) relay event evOff <- 32 Kanal IO Modul (2238).Ausgang_02 2024-11-04 21:32:36.276 - info: hausbusde.0 (7862) relay event evOn <- 32 Kanal IO Modul (2238).Ausgang_05 2024-11-04 21:32:40.395 - error: zigbee.0 (16409) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2024-11-04 21:32:40.470 - silly: yahka.0 (7784) States user redis pmessage ping.0.Iobroker.Hausbus.alive/ping.0.Iobroker.Hausbus.alive:{"val":true,"ack":true,"ts":1730752360468,"q":0,"from":"system.adapter.ping.0","user":"system.user.admin","lc":1726510822358} 2024-11-04 21:32:40.471 - debug: yahka.0 (7784) got a stateChange for [ping.0.Iobroker.Hausbus.alive] 2024-11-04 21:32:40.472 - debug: yahka.0 (7784) change event from ioBroker via [ping.0.Iobroker.Hausbus.alive]{"val":1,"ack":true,"ts":1730752360468,"q":0,"from":"system.adapter.ping.0","user":"system.user.admin","lc":1726510822358} 2024-11-04 21:32:40.472 - debug: yahka.0 (7784) [Steuerung Heizung.LeakDetected] got a change notify event, ioValue: 1 2024-11-04 21:32:40.472 - debug: yahka.0 (7784) script: converting value to homekit: 1 to 0 2024-11-04 21:32:40.473 - debug: yahka.0 (7784) [Steuerung Heizung.LeakDetected] forwarding value from ioBroker (1) to homekit as (0) 2024-11-04 21:32:40.473 - debug: yahka.0 (7784) [Steuerung Heizung.LeakDetected] got a set event, hkValue: 0 2024-11-04 21:32:40.473 - debug: yahka.0 (7784) [Steuerung Heizung.LeakDetected] set was initiated from ioBroker - exiting here 2024-11-04 21:32:40.396 - error: zigbee.0 (16409) unhandled promise rejection: ZCL command 0xa4c138c9efe5fad7/1 manuSpecificTuya.dataQuery({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205)) 2024-11-04 21:32:40.477 - error: zigbee.0 (16409) Error: ZCL command 0xa4c138c9efe5fad7/1 manuSpecificTuya.dataQuery({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205)) at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:411:23) at Queue.execute (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:35:20) at Request.send (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/helpers/request.ts:79:20) at Endpoint.zclCommand (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:756:28) at Endpoint.command (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:587:24) at Object.onEvent (/opt/iobroker/node_modules/zigbee-herdsman-converters/src/lib/tuya.ts:85:13) 2024-11-04 21:32:40.477 - error: zigbee.0 (16409) Exception-Code: 205: ZCL command 0xa4c138c9efe5fad7/1 manuSpecificTuya.dataQuery({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205)) 2024-11-04 21:32:40.506 - info: zigbee.0 (16409) cleaned everything up... 2024-11-04 21:32:40.511 - info: zigbee.0 (16409) Zigbee: disabling joining new devices. 2024-11-04 21:32:40.729 - silly: yahka.0 (7784) States user redis pmessage zigbee.0.a4c138c9efe5fad7.available/zigbee.0.a4c138c9efe5fad7.available:{"val":false,"ack":true,"ts":1730752360709,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1730752360709} 2024-11-04 21:32:40.730 - debug: yahka.0 (7784) got a stateChange for [zigbee.0.a4c138c9efe5fad7.available] 2024-11-04 21:32:40.730 - debug: yahka.0 (7784) change event from ioBroker via [zigbee.0.a4c138c9efe5fad7.available]{"val":0,"ack":true,"ts":1730752360709,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1730752360709} 2024-11-04 21:32:40.730 - debug: yahka.0 (7784) [Raumfühler Küche.StatusActive] got a change notify event, ioValue: 0 2024-11-04 21:32:40.731 - debug: yahka.0 (7784) [Raumfühler Küche.StatusActive] forwarding value from ioBroker (0) to homekit as (0) 2024-11-04 21:32:40.731 - debug: yahka.0 (7784) [Raumfühler Küche.StatusActive] got a set event, hkValue: false 2024-11-04 21:32:40.731 - debug: yahka.0 (7784) [Raumfühler Küche.StatusActive] set was initiated from ioBroker - exiting here 2024-11-04 21:32:40.737 - silly: yahka.0 (7784) States user redis pmessage zigbee.0.a4c13845f806ea6a.available/zigbee.0.a4c13845f806ea6a.available:{"val":false,"ack":true,"ts":1730752360710,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1730752360710} 2024-11-04 21:32:40.738 - debug: yahka.0 (7784) got a stateChange for [zigbee.0.a4c13845f806ea6a.available] 2024-11-04 21:32:40.738 - debug: yahka.0 (7784) change event from ioBroker via [zigbee.0.a4c13845f806ea6a.available]{"val":0,"ack":true,"ts":1730752360710,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1730752360710} 2024-11-04 21:32:40.738 - debug: yahka.0 (7784) [Raumfühler Einliegerwohnung.StatusActive] got a change notify event, ioValue: 0 2024-11-04 21:32:40.739 - debug: yahka.0 (7784) [Raumfühler Einliegerwohnung.StatusActive] forwarding value from ioBroker (0) to homekit as (0) 2024-11-04 21:32:40.739 - debug: yahka.0 (7784) [Raumfühler Einliegerwohnung.StatusActive] got a set event, hkValue: false 2024-11-04 21:32:40.739 - debug: yahka.0 (7784) [Raumfühler Einliegerwohnung.StatusActive] set was initiated from ioBroker - exiting here 2024-11-04 21:32:41.007 - info: zigbee.0 (16409) terminating 2024-11-04 21:32:41.009 - warn: zigbee.0 (16409) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-11-04 21:32:41.615 - error: host.Iobroker Caught by controller[1]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: 2024-11-04 21:32:41.616 - error: host.Iobroker Caught by controller[1]: Error: ZCL command 0xa4c138c9efe5fad7/1 manuSpecificTuya.dataQuery({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205)) 2024-11-04 21:32:41.616 - error: host.Iobroker Caught by controller[1]: at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:411:23) 2024-11-04 21:32:41.617 - error: host.Iobroker Caught by controller[1]: at Queue.execute (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:35:20) 2024-11-04 21:32:41.617 - error: host.Iobroker Caught by controller[1]: at Request.send (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/helpers/request.ts:79:20) 2024-11-04 21:32:41.617 - error: host.Iobroker Caught by controller[1]: at Endpoint.zclCommand (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:756:28) 2024-11-04 21:32:41.617 - error: host.Iobroker Caught by controller[1]: at Endpoint.command (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:587:24) 2024-11-04 21:32:41.617 - error: host.Iobroker Caught by controller[1]: at Object.onEvent (/opt/iobroker/node_modules/zigbee-herdsman-converters/src/lib/tuya.ts:85:13) 2024-11-04 21:32:41.618 - error: host.Iobroker instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-11-04 21:32:41.618 - info: host.Iobroker Restart adapter system.adapter.zigbee.0 because enabled 2024-11-04 21:32:41.618 - warn: host.Iobroker Do not restart adapter system.adapter.zigbee.0 because restart loop detectedLiegt vielleicht auch daran, dass Dein OS tot und schon begraben ist.
Sorry, auch wenns wehtut.
Neu aufsetzen mit 64BIT Bookworm.Edit: vorher noch alles updaten , was möglich ist und dann Backup machen.
-
@strohhut sagte in Zigbee Adapter nach Versetzen geht nichts mehr:
und dem CC26 am selben Port,
und weiss das der ioBroker auch?
wie ist der port denn in der Instanz eingetragen?
@homoran Ausgelesen
ls -l /dev/serial/by-id
insgesamt 0
lrwxrwxrwx 1 root root 13 Nov 2 16:15 usb-Texas_Instruments_XDS110__03.00.00.32__Embed_with_CMSIS-DAP_L1100PDQ-if00 -> ../../ttyACM0
lrwxrwxrwx 1 root root 13 Nov 2 16:15 usb-Texas_Instruments_XDS110__03.00.00.32__Embed_with_CMSIS-DAP_L1100PDQ-if03 -> ../../ttyACM1COM-Anschlüsse: /dev/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.32__Embed_with_CMSIS-DAP_L1100PDQ-if00
-
Liegt vielleicht auch daran, dass Dein OS tot und schon begraben ist.
Sorry, auch wenns wehtut.
Neu aufsetzen mit 64BIT Bookworm.Edit: vorher noch alles updaten , was möglich ist und dann Backup machen.
@haselchen das artet in Arbeit aus. Ich warte noch ein paar Tipps ab, bevor ich das mache.
-
@haselchen das artet in Arbeit aus. Ich warte noch ein paar Tipps ab, bevor ich das mache.
@strohhut sagte in Zigbee Adapter nach Versetzen geht nichts mehr:
@haselchen das artet in Arbeit aus. Ich warte noch ein paar Tipps ab, bevor ich das mache.
wenn iob diag schon nicht läuft, solltest du zu allererst das Fundament sichern.
In einem wackligen Haus wohnt es sich schlecht.und Fehlersuche wird schwer
-
@haselchen das artet in Arbeit aus. Ich warte noch ein paar Tipps ab, bevor ich das mache.
Da werden keine Tipps anderer Art kommen.
Dein System wird eher früher als später überhaupt nicht mehr funktionieren.
Die Arbeit kommt sowieso und Du hast sie Dir nochmal schwerer gemacht indem Du Dein System anscheinend nie auf Stand gehalten hast. -
@strohhut sagte in Zigbee Adapter nach Versetzen geht nichts mehr:
@haselchen das artet in Arbeit aus. Ich warte noch ein paar Tipps ab, bevor ich das mache.
wenn iob diag schon nicht läuft, solltest du zu allererst das Fundament sichern.
In einem wackligen Haus wohnt es sich schlecht.und Fehlersuche wird schwer
-
Da werden keine Tipps anderer Art kommen.
Dein System wird eher früher als später überhaupt nicht mehr funktionieren.
Die Arbeit kommt sowieso und Du hast sie Dir nochmal schwerer gemacht indem Du Dein System anscheinend nie auf Stand gehalten hast.@haselchen als Linuxanfänger war ich der Meinung apt update und upgrade reichen aus.
-
iob diag needs to be updated. Please execute 'iobroker fix' first."
Verwende die Raspbian-Variante von hier:
https://forum.iobroker.net/topic/59549/iob-diag-skript
Ja, dein Betriebssystem: Raspbian GNU/Linux 10.13 ist mausetot.
-
@haselchen als Linuxanfänger war ich der Meinung apt update und upgrade reichen aus.
@strohhut sagte in Zigbee Adapter nach Versetzen geht nichts mehr:
als Linuxanfänger war ich der Meinung apt update und upgrade reichen aus.
...um innerhalb einer major version (bei dir Debian 10) alles aktuell zu halten, ja!
Inzwischen sind wir bei v12, bei der es einen größeren Umbsu gegeben hat, so dass ein Upgrade nicht mehr möglich ist.Backups von allem ziehen
Raspberrypi OS 12 (Bookworm) lite installieten
iobroker installietrn
Backups wieder einspielen!fertig
-
@strohhut sagte in Zigbee Adapter nach Versetzen geht nichts mehr:
als Linuxanfänger war ich der Meinung apt update und upgrade reichen aus.
...um innerhalb einer major version (bei dir Debian 10) alles aktuell zu halten, ja!
Inzwischen sind wir bei v12, bei der es einen größeren Umbsu gegeben hat, so dass ein Upgrade nicht mehr möglich ist.Backups von allem ziehen
Raspberrypi OS 12 (Bookworm) lite installieten
iobroker installietrn
Backups wieder einspielen!fertig
-
@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!
-
@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! -
@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 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] -
@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. -
@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 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 ===