Tester gesucht: Zigbee 3.4.7
-
Ich versuche mal die Fragen zu beantworten, hier die Koordinator Kachel mit der 3.4.3
type:ZStack3x0 version:2-1.2.7.1. revision:20210708 port:/dev/serial/by-id/usb-Silicon_Labs_Sonoff_Zigbee_3.0_USB_Dongle_Plus_0001-if00-port0 channel:11 type:ZStack3x0 version:2-1.2.7.1. revision:20210708 port:/dev/serial/by-id/usb-Silicon_Labs_Sonoff_Zigbee_3.0_USB_Dongle_Plus_0001-if00-port0 channel:11Und hier die Debug Meldungen
Zigbee-Adapter GerĂ€te Netzwerkkarte Binding Debug Debug information by device Schlafzimmer TS0044_1 (ID: 0xa4c13881cc14bf1f Model: Schlafzimmer TS0044_1) Incoming messages ID Zigbee Payload State Payload ID value Flags {"type":"commandTuyaAction", "data":{"value":0, "data":{"type":"Buffer", "data":[]}}, "linkquality":57, "groupID":0, "cluster":"genOnOff", "meta":{"rawData":{"type":"Buffer", "data":[1, 131, 253, 0]}, "zclTransactionSequenceNumber":131, "frameControl":{"frameType":1, "manufacturerSpecific":false, "direction":0, "disableDefaultResponse":false, "reservedBits":0}}, "endpoint_id":3} {"action":"3_single"} 4_hold undefined SUCCESS {"action":"3_single"} 4_double undefined SUCCESS {"action":"3_single"} 4_single undefined SUCCESS {"action":"3_single"} 3_hold undefined SUCCESS {"action":"3_single"} 3_double undefined SUCCESS {"action":"3_single"} 3_single true SUCCESS {"action":"3_single"} 2_hold undefined SUCCESS {"action":"3_single"} 2_double undefined SUCCESS {"action":"3_single"} 2_single undefined SUCCESS {"action":"3_single"} 1_hold undefined SUCCESS {"action":"3_single"} 1_double undefined SUCCESS {"action":"3_single"} 1_single undefined SUCCESS {"action":"3_single"} action 3_single SUCCESS {"linkquality":57} link_quality 57 SUCCESS {"type":"commandTuyaAction", "data":{"value":0, "data":{"type":"Buffer", "data":[]}}, "linkquality":60, "groupID":0, "cluster":"genOnOff", "meta":{"rawData":{"type":"Buffer", "data":[1, 130, 253, 0]}, "zclTransactionSequenceNumber":130, "frameControl":{"frameType":1, "manufacturerSpecific":false, "direction":0, "disableDefaultResponse":false, "reservedBits":0}}, "endpoint_id":2} {"action":"2_single"} 4_hold undefined SUCCESS {"action":"2_single"} 4_double undefined SUCCESS {"action":"2_single"} 4_single undefined SUCCESS {"action":"2_single"} 3_hold undefined SUCCESS {"action":"2_single"} 3_double undefined SUCCESS {"action":"2_single"} 3_single undefined SUCCESS {"action":"2_single"} 2_hold undefined SUCCESS {"action":"2_single"} 2_double undefined SUCCESS {"action":"2_single"} 2_single true SUCCESS {"action":"2_single"} 1_hold undefined SUCCESS {"action":"2_single"} 1_double undefined SUCCESS {"action":"2_single"} 1_single undefined SUCCESS {"action":"2_single"} action 2_single SUCCESS {"linkquality":60} link_quality 60 SUCCESS {"type":"commandTuyaAction", "data":{"value":0, "data":{"type":"Buffer", "data":[]}}, "linkquality":60, "groupID":0, "cluster":"genOnOff", "meta":{"rawData":{"type":"Buffer", "data":[1, 129, 253, 0]}, "zclTransactionSequenceNumber":129, "frameControl":{"frameType":1, "manufacturerSpecific":false, "direction":0, "disableDefaultResponse":false, "reservedBits":0}}, "endpoint_id":1} {"action":"1_single"} 4_hold undefined SUCCESS {"action":"1_single"} 4_double undefined SUCCESS {"action":"1_single"} 4_single undefined SUCCESS {"action":"1_single"} 3_hold undefined SUCCESS {"action":"1_single"} 3_double undefined SUCCESS {"action":"1_single"} 3_single undefined SUCCESS {"action":"1_single"} 2_hold undefined SUCCESS {"action":"1_single"} 2_double undefined SUCCESS {"action":"1_single"} 2_single undefined SUCCESS {"action":"1_single"} 1_hold undefined SUCCESS {"action":"1_single"} 1_double undefined SUCCESS {"action":"1_single"} 1_single true SUCCESS {"action":"1_single"} action 1_single SUCCESS {"linkquality":60} link_quality 60 SUCCESS {"available":true} available true SUCCESSWenn das so passt wĂŒrde ich das selbe nochmal mit der 3.4.4 machen, sag bitte kurz Bescheid.
-
Hier die Kachel mit der 3.4.4 Zigbee Coordinator Ieee:0x00124b0029dc10c2 Adapter:3.4.4 Installed:iobroker.zigbee@3.4.4 Herdsman:10.0.8 Converters:26.51.1 Zigbee Coordinator type:ZStack3x0 version:2-1.2.7.1. revision:20210708 port:/dev/serial/by-id/usb-Silicon_Labs_Sonoff_Zigbee_3.0_USB_Dongle_Plus_0001-if00-port0 channel:11Schlafzimmer TS0044_1 (ID: 0xa4c13881cc14bf1f Model: Schlafzimmer TS0044_1) Incoming messages ID Zigbee Payload State Payload ID value Flags {"type":"commandTuyaAction", "data":{"value":0, "data":{"type":"Buffer", "data":[]}}, "linkquality":66, "groupID":0, "cluster":"genOnOff", "meta":{"rawData":{"type":"Buffer", "data":[1, 138, 253, 0]}, "zclTransactionSequenceNumber":138, "frameControl":{"frameType":1, "manufacturerSpecific":false, "direction":0, "disableDefaultResponse":false, "reservedBits":0}}, "endpoint_id":2} {"action":"2_single"} 1_single undefined SUCCESS, error: ESTATE {"action":"2_single"} action 2_single SUCCESS, error: ESTATE {"linkquality":66} link_quality 66 SUCCESS, error: ESTATE {"type":"commandTuyaAction", "data":{"value":0, "data":{"type":"Buffer", "data":[]}}, "linkquality":63, "groupID":0, "cluster":"genOnOff", "meta":{"rawData":{"type":"Buffer", "data":[1, 137, 253, 0]}, "zclTransactionSequenceNumber":137, "frameControl":{"frameType":1, "manufacturerSpecific":false, "direction":0, "disableDefaultResponse":false, "reservedBits":0}}, "endpoint_id":4} {"action":"4_single"} 1_single undefined SUCCESS, error: ESTATE {"action":"4_single"} action 4_single SUCCESS, error: ESTATE {"linkquality":63} link_quality 63 SUCCESS, error: ESTATE {"type":"commandTuyaAction", "data":{"value":0, "data":{"type":"Buffer", "data":[]}}, "linkquality":63, "groupID":0, "cluster":"genOnOff", "meta":{"rawData":{"type":"Buffer", "data":[1, 136, 253, 0]}, "zclTransactionSequenceNumber":136, "frameControl":{"frameType":1, "manufacturerSpecific":false, "direction":0, "disableDefaultResponse":false, "reservedBits":0}}, "endpoint_id":3} {"action":"3_single"} 1_single undefined SUCCESS, error: ESTATE {"action":"3_single"} action 3_single SUCCESS, error: ESTATE {"linkquality":63} link_quality 63 SUCCESS, error: ESTATE {"type":"commandTuyaAction", "data":{"value":0, "data":{"type":"Buffer", "data":[]}}, "linkquality":63, "groupID":0, "cluster":"genOnOff", "meta":{"rawData":{"type":"Buffer", "data":[1, 135, 253, 0]}, "zclTransactionSequenceNumber":135, "frameControl":{"frameType":1, "manufacturerSpecific":false, "direction":0, "disableDefaultResponse":false, "reservedBits":0}}, "endpoint_id":2} {"action":"2_single"} 1_single undefined SUCCESS, error: ESTATE {"action":"2_single"} action 2_single SUCCESS, error: ESTATE {"linkquality":63} link_quality 63 SUCCESS, error: ESTATE {"type":"commandTuyaAction", "data":{"value":0, "data":{"type":"Buffer", "data":[]}}, "linkquality":63, "groupID":0, "cluster":"genOnOff", "meta":{"rawData":{"type":"Buffer", "data":[1, 134, 253, 0]}, "zclTransactionSequenceNumber":134, "frameControl":{"frameType":1, "manufacturerSpecific":false, "direction":0, "disableDefaultResponse":false, "reservedBits":0}}, "endpoint_id":1} {"action":"1_single"} 1_double undefined SUCCESS, error: ESTATE {"action":"1_single"} 1_single true SUCCESS, error: ESTATE {"action":"1_single"} action 1_single SUCCESS, error: ESTATE {"linkquality":63} link_quality 63 SUCCESS, error: ESTATE {"type":"commandTuyaAction", "data":{"value":0, "data":{"type":"Buffer", "data":[]}}, "linkquality":63, "groupID":0, "cluster":"genOnOff", "meta":{"rawData":{"type":"Buffer", "data":[1, 133, 253, 0]}, "zclTransactionSequenceNumber":133, "frameControl":{"frameType":1, "manufacturerSpecific":false, "direction":0, "disableDefaultResponse":false, "reservedBits":0}}, "endpoint_id":1} {"action":"1_single"} 1_double undefined SUCCESS, error: ESTATE {"action":"1_single"} 1_single true SUCCESS, error: ESTATE {"action":"1_single"} action 1_single SUCCESS, error: ESTATE {"linkquality":63} link_quality 63 SUCCESS, error: ESTATE {"available":true} available true SUCCESS, error: ESTATEIch hoffe das sind die Infos die du brauchst.
-
leider nein. Der Text aus dem Debug info ist nie das was ich brauche. Ich brauche immer die Log ausschnitte die kommen wenn man auf diesen button clickt:
ioBroker auf RPi4 - Hardware soweit wie möglich via Zigbee.
"Shit don't work" ist keine Fehlermeldung, sondern ein Fluch. -
@Asgothian habe ich jetzt mal gesetzt, dann sind die Kacheln unterschiedlich hoch.
-
leider nein. Der Text aus dem Debug info ist nie das was ich brauche. Ich brauche immer die Log ausschnitte die kommen wenn man auf diesen button clickt:
@Asgothian ok
I01: Zigbee Event of Type commandTuyaAction from device 0xa4c13881cc14bf1f, incoming event: {"type":"commandTuyaAction","data":{"value":0,"data":{"type":"Buffer","data":[]}},"linkquality":66,"groupID":0,"cluster":"genOnOff","meta":{"rawData":{"type":"Buffer","data":[1,145,253,0]},"zclTransactionSequenceNumber":145,"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":false,"reservedBits":0}},"endpoint_id":4} I04: value generated '66' from device a4c13881cc14bf1f for 'Link quality' I02: 1 converter available for '_TZ3000_mh9px7cq' 'a4c13881cc14bf1f' with cluster 'genOnOff' and type 'commandTuyaAction' I02.1a: converter 1 : Cluster genOnOff I02.0b: data: {"value":0,"data":{"type":"Buffer","data":[]}} options: {} meta:{"deviceIEEE":"0xa4c13881cc14bf1f","logger":"StatesController","state":{"state":""}} result:{"action":"4_single"} I02.1c: candidates: [{"action":"4_single"}] => payload {"action":"4_single"} I03: message received '{"action":"4_single"}' from device a4c13881cc14bf1f type '_TZ3000_mh9px7cq' I04-1: value generated '"4_single"' from device a4c13881cc14bf1f for 'Triggered action (e.g. a button click)' I04-2: value 'undefined' from device a4c13881cc14bf1f via getter for '1_single (ID 1_single with property action) ESTATE: unable to enumerate states of a4c13881cc14bf1f for payload {"action":"4_single"}, TypeError (Cannot read properties of undefined (reading 'key')). `` `` I01: Zigbee Event of Type commandTuyaAction from device 0xa4c13881cc14bf1f, incoming event: {"type":"commandTuyaAction","data":{"value":0,"data":{"type":"Buffer","data":[]}},"linkquality":66,"groupID":0,"cluster":"genOnOff","meta":{"rawData":{"type":"Buffer","data":[1,144,253,0]},"zclTransactionSequenceNumber":144,"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":false,"reservedBits":0}},"endpoint_id":3} I04: value generated '66' from device a4c13881cc14bf1f for 'Link quality' I02: 1 converter available for '_TZ3000_mh9px7cq' 'a4c13881cc14bf1f' with cluster 'genOnOff' and type 'commandTuyaAction' I02.1a: converter 1 : Cluster genOnOff I02.0b: data: {"value":0,"data":{"type":"Buffer","data":[]}} options: {} meta:{"deviceIEEE":"0xa4c13881cc14bf1f","logger":"StatesController","state":{"state":""}} result:{"action":"3_single"} I02.1c: candidates: [{"action":"3_single"}] => payload {"action":"3_single"} I03: message received '{"action":"3_single"}' from device a4c13881cc14bf1f type '_TZ3000_mh9px7cq' I04-1: value generated '"3_single"' from device a4c13881cc14bf1f for 'Triggered action (e.g. a button click)' I04-2: value 'undefined' from device a4c13881cc14bf1f via getter for '1_single (ID 1_single with property action) ESTATE: unable to enumerate states of a4c13881cc14bf1f for payload {"action":"3_single"}, TypeError (Cannot read properties of undefined (reading 'key')). `` `` I01: Zigbee Event of Type commandTuyaAction from device 0xa4c13881cc14bf1f, incoming event: {"type":"commandTuyaAction","data":{"value":0,"data":{"type":"Buffer","data":[]}},"linkquality":66,"groupID":0,"cluster":"genOnOff","meta":{"rawData":{"type":"Buffer","data":[1,143,253,0]},"zclTransactionSequenceNumber":143,"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":false,"reservedBits":0}},"endpoint_id":2} I04: value generated '66' from device a4c13881cc14bf1f for 'Link quality' I02: 1 converter available for '_TZ3000_mh9px7cq' 'a4c13881cc14bf1f' with cluster 'genOnOff' and type 'commandTuyaAction' I02.1a: converter 1 : Cluster genOnOff I02.0b: data: {"value":0,"data":{"type":"Buffer","data":[]}} options: {} meta:{"deviceIEEE":"0xa4c13881cc14bf1f","logger":"StatesController","state":{"state":""}} result:{"action":"2_single"} I02.1c: candidates: [{"action":"2_single"}] => payload {"action":"2_single"} I03: message received '{"action":"2_single"}' from device a4c13881cc14bf1f type '_TZ3000_mh9px7cq' I04-1: value generated '"2_single"' from device a4c13881cc14bf1f for 'Triggered action (e.g. a button click)' I04-2: value 'undefined' from device a4c13881cc14bf1f via getter for '1_single (ID 1_single with property action) ESTATE: unable to enumerate states of a4c13881cc14bf1f for payload {"action":"2_single"}, TypeError (Cannot read properties of undefined (reading 'key')). `` Passt das, oder brauchst du noch mehr?Es gibt nicht Gutes. AuĂer man tut es. Erich KĂ€stner
-
Die 3.4.4 ist raus:
- umstellung auf ZH10
- ZHC 26.51.xx
- Bugfixes bei Bindings
- Usability fĂŒr Bindings erhöht
- breitere Scrollbars in Kacheln
Angenommen die Fernbedienung A ist mit dem GerĂ€t B via 'Binding' verbunden. Solange der Adapter die TastendrĂŒcke von A mit bekommt versucht er, 500 ms nach dem Auslösen von A die entsrpechenden Cluster von B auszulesen. Bisher ausschliesslich fĂŒr:
genOnOff- sprich An/Aus von Lampen, Steckdosen, etc.genLevelCtrl- sprich Helligkeit von LampenlightingColorCtrl- Farbeinstellung von Lampen.
Was in der 3.4.5 noch kommt ist eine vergleichbare Funktion von Gruppen. Warum sollte das fĂŒr jeden Nutzer von Zigbee interessant sein ?
- Bindings erlauben es, Leuchten und Steckdosen mit einer Fernbedienung zu schalten auch wenn der Adapter nicht lÀuft.
- Bisher war es dann zumeist so das der Adapter die StatusÀnderung nicht mit bekommt und deswegen auch nicht anzeigt. Genau das ist jetzt der Fall, wenn auch mit etwas Verzögerung.
- Sobald das auch mit Gruppen sauber arbeitet wird das Zigbee-System nochmal Stabiler fĂŒr unbedarfte Benutzer - es sollte den WAF deutlich erhöhen.
A.
Nachtrag: Known Bugs: Es scheint noch Anzeigeprobleme bei den Bindings zu geben - bindings auf 2. / 3. Endpunkt eines GerÀtes werden nicht sauber angezeigt, sind aber vorhanden.
- breitere Scrollbars in Kacheln
Welche breit hast du gewĂ€hlt? Sie sind bei mir wieder genauso breit wie vorher. Und sind die Ănderungen an deinen GerĂ€t dann angekommen ( ohne webkit )?
-
@Asgothian ok
I01: Zigbee Event of Type commandTuyaAction from device 0xa4c13881cc14bf1f, incoming event: {"type":"commandTuyaAction","data":{"value":0,"data":{"type":"Buffer","data":[]}},"linkquality":66,"groupID":0,"cluster":"genOnOff","meta":{"rawData":{"type":"Buffer","data":[1,145,253,0]},"zclTransactionSequenceNumber":145,"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":false,"reservedBits":0}},"endpoint_id":4} I04: value generated '66' from device a4c13881cc14bf1f for 'Link quality' I02: 1 converter available for '_TZ3000_mh9px7cq' 'a4c13881cc14bf1f' with cluster 'genOnOff' and type 'commandTuyaAction' I02.1a: converter 1 : Cluster genOnOff I02.0b: data: {"value":0,"data":{"type":"Buffer","data":[]}} options: {} meta:{"deviceIEEE":"0xa4c13881cc14bf1f","logger":"StatesController","state":{"state":""}} result:{"action":"4_single"} I02.1c: candidates: [{"action":"4_single"}] => payload {"action":"4_single"} I03: message received '{"action":"4_single"}' from device a4c13881cc14bf1f type '_TZ3000_mh9px7cq' I04-1: value generated '"4_single"' from device a4c13881cc14bf1f for 'Triggered action (e.g. a button click)' I04-2: value 'undefined' from device a4c13881cc14bf1f via getter for '1_single (ID 1_single with property action) ESTATE: unable to enumerate states of a4c13881cc14bf1f for payload {"action":"4_single"}, TypeError (Cannot read properties of undefined (reading 'key')). `` `` I01: Zigbee Event of Type commandTuyaAction from device 0xa4c13881cc14bf1f, incoming event: {"type":"commandTuyaAction","data":{"value":0,"data":{"type":"Buffer","data":[]}},"linkquality":66,"groupID":0,"cluster":"genOnOff","meta":{"rawData":{"type":"Buffer","data":[1,144,253,0]},"zclTransactionSequenceNumber":144,"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":false,"reservedBits":0}},"endpoint_id":3} I04: value generated '66' from device a4c13881cc14bf1f for 'Link quality' I02: 1 converter available for '_TZ3000_mh9px7cq' 'a4c13881cc14bf1f' with cluster 'genOnOff' and type 'commandTuyaAction' I02.1a: converter 1 : Cluster genOnOff I02.0b: data: {"value":0,"data":{"type":"Buffer","data":[]}} options: {} meta:{"deviceIEEE":"0xa4c13881cc14bf1f","logger":"StatesController","state":{"state":""}} result:{"action":"3_single"} I02.1c: candidates: [{"action":"3_single"}] => payload {"action":"3_single"} I03: message received '{"action":"3_single"}' from device a4c13881cc14bf1f type '_TZ3000_mh9px7cq' I04-1: value generated '"3_single"' from device a4c13881cc14bf1f for 'Triggered action (e.g. a button click)' I04-2: value 'undefined' from device a4c13881cc14bf1f via getter for '1_single (ID 1_single with property action) ESTATE: unable to enumerate states of a4c13881cc14bf1f for payload {"action":"3_single"}, TypeError (Cannot read properties of undefined (reading 'key')). `` `` I01: Zigbee Event of Type commandTuyaAction from device 0xa4c13881cc14bf1f, incoming event: {"type":"commandTuyaAction","data":{"value":0,"data":{"type":"Buffer","data":[]}},"linkquality":66,"groupID":0,"cluster":"genOnOff","meta":{"rawData":{"type":"Buffer","data":[1,143,253,0]},"zclTransactionSequenceNumber":143,"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":false,"reservedBits":0}},"endpoint_id":2} I04: value generated '66' from device a4c13881cc14bf1f for 'Link quality' I02: 1 converter available for '_TZ3000_mh9px7cq' 'a4c13881cc14bf1f' with cluster 'genOnOff' and type 'commandTuyaAction' I02.1a: converter 1 : Cluster genOnOff I02.0b: data: {"value":0,"data":{"type":"Buffer","data":[]}} options: {} meta:{"deviceIEEE":"0xa4c13881cc14bf1f","logger":"StatesController","state":{"state":""}} result:{"action":"2_single"} I02.1c: candidates: [{"action":"2_single"}] => payload {"action":"2_single"} I03: message received '{"action":"2_single"}' from device a4c13881cc14bf1f type '_TZ3000_mh9px7cq' I04-1: value generated '"2_single"' from device a4c13881cc14bf1f for 'Triggered action (e.g. a button click)' I04-2: value 'undefined' from device a4c13881cc14bf1f via getter for '1_single (ID 1_single with property action) ESTATE: unable to enumerate states of a4c13881cc14bf1f for payload {"action":"2_single"}, TypeError (Cannot read properties of undefined (reading 'key')). `` Passt das, oder brauchst du noch mehr?@Winni Kannst du mal bitte auf deinem System von Hand patchen:
- in der Datei /opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js
- die Zeile 1260 von
if (publishResult.key)aufif (publishResult?.key)wechseln - den adapter neu starten
A.
ioBroker auf RPi4 - Hardware soweit wie möglich via Zigbee.
"Shit don't work" ist keine Fehlermeldung, sondern ein Fluch. -
@Winni Kannst du mal bitte auf deinem System von Hand patchen:
- in der Datei /opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js
- die Zeile 1260 von
if (publishResult.key)aufif (publishResult?.key)wechseln - den adapter neu starten
A.
@Asgothian Volltreffer funktioniert. Super, vielen Dank. đ
-
Habs installiert und lÀuft
-
3.4.5 ist raus. mit bugfix fĂŒr Winni und breiteren Webkit toolbars.
A.
LĂ€uft ohne Probleme, vielen Dank.
Herzliche GrĂŒĂe
Fabio -
Seit 3.3.5 funktioniert der 4 fach Switch nicht mehr.
Bin wieder zurĂŒck auf die 3.3.5, da funktionieren wieder alle Buttons.
-
Gute Frage .
Könnte die 3.4.4 gewesen sein.
Ich mach nochmal nen Update und schau mal.Edit: @asgothian geht mit der 3.4.5 wieder. Top und Danke.
-
Hallo @asgothian
Ich nutze 3.4.5 und es gibt viele warnings im Log:zigbee.0 2026-05-22 06:55:58.099 warn reading 0x00178801099dd468-EP-11-CL-8 zigbee.0 2026-05-22 06:55:58.097 warn reading 0x00178801099dd468-EP-11-CL-6 zigbee.0 2026-05-22 06:55:48.180 warn reading 0x00178801099dd468-EP-11-CL-8 zigbee.0 2026-05-22 06:55:48.178 warn reading 0x00178801099dd468-EP-11-CL-6 zigbee.0 2026-05-22 06:55:38.263 warn reading 0x00178801099dd468-EP-11-CL-8 zigbee.0 2026-05-22 06:55:38.261 warn reading 0x00178801099dd468-EP-11-CL-6 zigbee.0 2026-05-22 06:55:28.351 warn reading 0x00178801099dd468-EP-11-CL-8 zigbee.0 2026-05-22 06:55:28.350 warn reading 0x00178801099dd468-EP-11-CL-6 zigbee.0 2026-05-22 06:55:18.448 warn reading 0x00178801099dd468-EP-11-CL-8 zigbee.0 2026-05-22 06:55:18.447 warn reading 0x00178801099dd468-EP-11-CL-6Wie kann ich das fixen? Bzw. ist es ein Bug?
-
Aktuell kannst du das nur fixen indem du den Adapter selber patchst. Die Meldungen kommen weil du ein 'Binding' benutzt, und der Adapter von dem gebundenen Device die relevanten States versucht auszulesen. Der entsprechende Code (
/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js, Zeile 1415ff) ist im Spoiler hinterlegt. Es ist hinreichend, die Zeilen die mitthis.warnbeginnen auszukommentieren (mit//)Wobei ich durchaus ĂŒberrascht bin das du diese Meldung alle 10 Sekunden bekommst. Kannst du bitte mal einen Screenshot vom Bindings Tab posten ?
-
Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.
Hast du es satt, bei jedem Besuch durch die gleichen BeitrĂ€ge zu scrollen? Wenn du dich fĂŒr ein Konto anmeldest, kommst du immer genau dorthin zurĂŒck, wo du zuvor warst, und kannst dich ĂŒber neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und BeitrĂ€ge positiv bewerten, um anderen Community-Mitgliedern deine WertschĂ€tzung zu zeigen.
Mit deinem Input könnte dieser Beitrag noch besser werden đ
Registrieren AnmeldenSupport us
553
Online32.9k
Benutzer83.2k
Themen1.3m
BeitrÀge