Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

  1. ioBroker Community Home
  2. Deutsch
  3. Tester
  4. Tester für Zigbee Adapter 2.0.x gesucht

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.3k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    2.0k

  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    15
    1
    2.4k

Tester für Zigbee Adapter 2.0.x gesucht

Geplant Angeheftet Gesperrt Verschoben Tester
zigbee 2.0.1
529 Beiträge 51 Kommentatoren 102.6k Aufrufe 43 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • T tom_33

    @asgothian Das ist der ganze Log nach dem die Batt. raus und wieder rein gegeben wurde. Die Link quality hab ich jetzt auf die Schnelle nicht rausgefiltert.

    2025-04-11 17:02:45.713	warn	DeviceConfigure:0x04cf8cdf3c7c87f9 lumi.remote.b486opcn01 Failed to configure. --> ZCL command 0x04cf8cdf3c7c87f9/1 manuSpecificLumi.write({"mode":1}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"manufacturerCode":4447,"writeUndiv":false}) failed (Data request failed with error: 'MAC transaction expired' (240))
    zigbee.0
    	2025-04-11 17:02:02.724	warn	DeviceConfigure:0x04cf8cdf3c7c87f9 lumi.remote.b486opcn01 Failed to configure. --> ZCL command 0x04cf8cdf3c7c87f9/1 manuSpecificLumi.write({"mode":1}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"manufacturerCode":4447,"writeUndiv":false}) failed (Data request failed with error: 'MAC transaction expired' (240))
    zigbee.0
    	2025-04-11 17:01:19.712	warn	ELEVATED:I02 (9cd6) value generated 'true' from device 04cf8cdf3c7c87f9 for 'button_3_single'
    zigbee.0
    	2025-04-11 17:01:19.711	warn	ELEVATED:I02 (9cd6) value generated '"button_3_single"' from device 04cf8cdf3c7c87f9 for 'Triggered action (e.g. a button click)'
    zigbee.0
    	2025-04-11 17:01:19.711	warn	ELEVATED:I01 (9cd6) message received '{"action":"button_3_single"}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
    zigbee.0
    	2025-04-11 17:01:19.709	warn	ELEVATED:I02 (9cd6) value generated '78' from device 04cf8cdf3c7c87f9 for 'Link quality'
    zigbee.0
    	2025-04-11 17:01:19.708	warn	ELEVATED:I01 (9cd6) message received '{"linkquality":78}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
    zigbee.0
    	2025-04-11 17:01:19.703	warn	ELEVATED:I01 (9cd6) Zigbee Event of Type attributeReport from device 0x04cf8cdf3c7c87f9, incoming event: {"type":"attributeReport","data":{"presentValue":1},"linkquality":78,"groupID":0,"cluster":"genMultistateInput","meta":{"zclTransactionSequenceNumber":1,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":3}
    zigbee.0
    	2025-04-11 16:57:44.289	warn	ELEVATED:I02 (533c) value generated '72' from device 04cf8cdf3c7c87f9 for 'Link quality'
    zigbee.0
    	2025-04-11 16:57:44.288	warn	ELEVATED:I01 (533c) message received '{"linkquality":72}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
    zigbee.0
    	2025-04-11 16:57:44.278	warn	ELEVATED:I02 (533b) value generated '72' from device 04cf8cdf3c7c87f9 for 'Link quality'
    zigbee.0
    	2025-04-11 16:57:44.277	warn	ELEVATED:I01 (533b) message received '{"linkquality":72}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
    zigbee.0
    	2025-04-11 16:57:44.277	warn	ELEVATED:I02 (533a) value generated '72' from device 04cf8cdf3c7c87f9 for 'Link quality'
    zigbee.0
    	2025-04-11 16:57:44.277	warn	ELEVATED:I01 (533a) message received '{"linkquality":72}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
    zigbee.0
    	2025-04-11 16:57:44.276	warn	ELEVATED:I02 (5338) value generated '72' from device 04cf8cdf3c7c87f9 for 'Link quality'
    zigbee.0
    	2025-04-11 16:57:44.276	warn	ELEVATED:I01 (5338) message received '{"linkquality":72}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
    zigbee.0
    	2025-04-11 16:57:44.276	warn	ELEVATED:I02 (5337) value generated '72' from device 04cf8cdf3c7c87f9 for 'Link quality'
    zigbee.0
    	2025-04-11 16:57:44.275	warn	ELEVATED:I01 (5337) message received '{"linkquality":72}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
    zigbee.0
    	2025-04-11 16:57:44.275	warn	ELEVATED:I02 (5322) value generated '72' from device 04cf8cdf3c7c87f9 for 'Link quality'
    zigbee.0
    	2025-04-11 16:57:44.274	warn	ELEVATED:I01 (5322) message received '{"linkquality":72}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
    zigbee.0
    	2025-04-11 16:57:44.265	warn	ELEVATED:I02 (5321) value generated '72' from device 04cf8cdf3c7c87f9 for 'Link quality'
    zigbee.0
    	2025-04-11 16:57:44.264	warn	ELEVATED:I01 (5321) message received '{"linkquality":72}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
    zigbee.0
    	2025-04-11 16:57:44.264	warn	ELEVATED:I02 (5320) value generated '72' from device 04cf8cdf3c7c87f9 for 'Link quality'
    zigbee.0
    	2025-04-11 16:57:44.264	warn	ELEVATED:I01 (5320) message received '{"linkquality":72}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
    zigbee.0
    	2025-04-11 16:57:44.263	warn	ELEVATED:I02 (531e) value generated '72' from device 04cf8cdf3c7c87f9 for 'Link quality'
    zigbee.0
    	2025-04-11 16:57:44.263	warn	ELEVATED:I01 (531e) message received '{"linkquality":72}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
    zigbee.0
    	2025-04-11 16:57:44.262	warn	ELEVATED:I02 (5312) value generated '72' from device 04cf8cdf3c7c87f9 for 'Link quality'
    zigbee.0
    	2025-04-11 16:57:44.262	warn	ELEVATED:I01 (5312) message received '{"linkquality":72}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
    zigbee.0
    	2025-04-11 16:57:44.252	warn	ELEVATED:I01 (533c) Zigbee Event of Type commandStep from device 0x04cf8cdf3c7c87f9, incoming event: {"type":"commandStep","data":{"stepmode":1,"stepsize":85,"transtime":7},"linkquality":72,"groupID":0,"cluster":"genLevelCtrl","meta":{"zclTransactionSequenceNumber":0,"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}
    zigbee.0
    	2025-04-11 16:57:44.251	warn	ELEVATED:I01 (533b) Zigbee Event of Type commandStep from device 0x04cf8cdf3c7c87f9, incoming event: {"type":"commandStep","data":{"stepmode":1,"stepsize":85,"transtime":7},"linkquality":72,"groupID":0,"cluster":"genLevelCtrl","meta":{"zclTransactionSequenceNumber":0,"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}
    zigbee.0
    	2025-04-11 16:57:44.250	warn	ELEVATED:I01 (533a) Zigbee Event of Type commandStep from device 0x04cf8cdf3c7c87f9, incoming event: {"type":"commandStep","data":{"stepmode":1,"stepsize":85,"transtime":7},"linkquality":72,"groupID":0,"cluster":"genLevelCtrl","meta":{"zclTransactionSequenceNumber":0,"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}
    zigbee.0
    	2025-04-11 16:57:44.249	warn	ELEVATED:I01 (5338) Zigbee Event of Type commandStep from device 0x04cf8cdf3c7c87f9, incoming event: {"type":"commandStep","data":{"stepmode":1,"stepsize":85,"transtime":7},"linkquality":72,"groupID":0,"cluster":"genLevelCtrl","meta":{"zclTransactionSequenceNumber":0,"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}
    zigbee.0
    	2025-04-11 16:57:44.247	warn	ELEVATED:I01 (5337) Zigbee Event of Type commandStep from device 0x04cf8cdf3c7c87f9, incoming event: {"type":"commandStep","data":{"stepmode":1,"stepsize":85,"transtime":7},"linkquality":72,"groupID":0,"cluster":"genLevelCtrl","meta":{"zclTransactionSequenceNumber":0,"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}
    zigbee.0
    	2025-04-11 16:57:44.237	warn	ELEVATED:I02 (5311) value generated '72' from device 04cf8cdf3c7c87f9 for 'Link quality'
    zigbee.0
    	2025-04-11 16:57:44.236	warn	ELEVATED:I01 (5311) message received '{"linkquality":72}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
    zigbee.0
    	2025-04-11 16:57:44.235	warn	ELEVATED:I02 (530a) value generated '72' from device 04cf8cdf3c7c87f9 for 'Link quality'
    zigbee.0
    	2025-04-11 16:57:44.234	warn	ELEVATED:I01 (530a) message received '{"linkquality":72}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
    zigbee.0
    	2025-04-11 16:57:44.226	warn	ELEVATED:I01 (5322) Zigbee Event of Type commandStep from device 0x04cf8cdf3c7c87f9, incoming event: {"type":"commandStep","data":{"stepmode":1,"stepsize":85,"transtime":7},"linkquality":72,"groupID":0,"cluster":"genLevelCtrl","meta":{"zclTransactionSequenceNumber":0,"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}
    zigbee.0
    	2025-04-11 16:57:44.225	warn	ELEVATED:I01 (5321) Zigbee Event of Type commandStep from device 0x04cf8cdf3c7c87f9, incoming event: {"type":"commandStep","data":{"stepmode":1,"stepsize":85,"transtime":7},"linkquality":72,"groupID":0,"cluster":"genLevelCtrl","meta":{"zclTransactionSequenceNumber":0,"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}
    zigbee.0
    	2025-04-11 16:57:44.224	warn	ELEVATED:I01 (5320) Zigbee Event of Type commandStep from device 0x04cf8cdf3c7c87f9, incoming event: {"type":"commandStep","data":{"stepmode":1,"stepsize":85,"transtime":7},"linkquality":72,"groupID":0,"cluster":"genLevelCtrl","meta":{"zclTransactionSequenceNumber":0,"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}
    zigbee.0
    	2025-04-11 16:57:44.223	warn	ELEVATED:I01 (531e) Zigbee Event of Type commandStep from device 0x04cf8cdf3c7c87f9, incoming event: {"type":"commandStep","data":{"stepmode":1,"stepsize":85,"transtime":7},"linkquality":72,"groupID":0,"cluster":"genLevelCtrl","meta":{"zclTransactionSequenceNumber":0,"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}
    zigbee.0
    	2025-04-11 16:57:44.215	warn	ELEVATED:I02 (5308) value generated '72' from device 04cf8cdf3c7c87f9 for 'Link quality'
    zigbee.0
    	2025-04-11 16:57:44.215	warn	ELEVATED:I01 (5308) message received '{"linkquality":72}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
    zigbee.0
    	2025-04-11 16:57:44.210	warn	ELEVATED:I01 (5312) Zigbee Event of Type commandStep from device 0x04cf8cdf3c7c87f9, incoming event: {"type":"commandStep","data":{"stepmode":1,"stepsize":85,"transtime":7},"linkquality":72,"groupID":0,"cluster":"genLevelCtrl","meta":{"zclTransactionSequenceNumber":0,"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}
    zigbee.0
    	2025-04-11 16:57:44.209	warn	ELEVATED:I01 (5311) Zigbee Event of Type commandStep from device 0x04cf8cdf3c7c87f9, incoming event: {"type":"commandStep","data":{"stepmode":1,"stepsize":85,"transtime":7},"linkquality":72,"groupID":0,"cluster":"genLevelCtrl","meta":{"zclTransactionSequenceNumber":0,"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}
    zigbee.0
    	2025-04-11 16:57:44.202	warn	ELEVATED:I01 (530a) Zigbee Event of Type commandStep from device 0x04cf8cdf3c7c87f9, incoming event: {"type":"commandStep","data":{"stepmode":1,"stepsize":85,"transtime":7},"linkquality":72,"groupID":0,"cluster":"genLevelCtrl","meta":{"zclTransactionSequenceNumber":0,"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}
    zigbee.0
    	2025-04-11 16:57:44.200	warn	ELEVATED:I01 (5308) Zigbee Event of Type commandStep from device 0x04cf8cdf3c7c87f9, incoming event: {"type":"commandStep","data":{"stepmode":1,"stepsize":85,"transtime":7},"linkquality":72,"groupID":0,"cluster":"genLevelCtrl","meta":{"zclTransactionSequenceNumber":0,"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}
    zigbee.0
    	2025-04-11 16:57:44.192	warn	ELEVATED:I02 (52fb) value generated 'true' from device 04cf8cdf3c7c87f9 for 'button_3_single'
    zigbee.0
    	2025-04-11 16:57:44.192	warn	ELEVATED:I02 (52fb) value generated '"button_3_single"' from device 04cf8cdf3c7c87f9 for 'Triggered action (e.g. a button click)'
    zigbee.0
    	2025-04-11 16:57:44.192	warn	ELEVATED:I01 (52fb) message received '{"action":"button_3_single"}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
    zigbee.0
    	2025-04-11 16:57:44.191	warn	ELEVATED:I02 (52fb) value generated '72' from device 04cf8cdf3c7c87f9 for 'Link quality'
    zigbee.0
    	2025-04-11 16:57:44.190	warn	ELEVATED:I01 (52fb) message received '{"linkquality":72}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
    zigbee.0
    	2025-04-11 16:57:44.188	warn	ELEVATED:I01 (52fb) Zigbee Event of Type commandStep from device 0x04cf8cdf3c7c87f9, incoming event: {"type":"commandStep","data":{"stepmode":1,"stepsize":85,"transtime":7},"linkquality":72,"groupID":0,"cluster":"genLevelCtrl","meta":{"zclTransactionSequenceNumber":0,"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}
    

    BTW: So schauts Innen aus:

    Aqara Opple 4 Gang.jpg

    AsgothianA Offline
    AsgothianA Offline
    Asgothian
    Developer
    schrieb am zuletzt editiert von
    #283

    @tom_33 welche knöpfe hast du gedrückt ? Laut Log kommt nur vom Button 3 etwas an.

    A.

    ioBroker auf RPi4 - Hardware soweit wie möglich via Zigbee.
    "Shit don't work" ist keine Fehlermeldung, sondern ein Fluch.

    T 1 Antwort Letzte Antwort
    0
    • AsgothianA Asgothian

      @tom_33 welche knöpfe hast du gedrückt ? Laut Log kommt nur vom Button 3 etwas an.

      A.

      T Offline
      T Offline
      tom_33
      schrieb am zuletzt editiert von
      #284

      @asgothian Oh, sorry! Nochmal mit allen Tasten.

      zigbee.0
      	2025-04-11 17:16:46.651	warn	DeviceConfigure:0x04cf8cdf3c7c87f9 lumi.remote.b486opcn01 Failed to configure. --> ZCL command 0x04cf8cdf3c7c87f9/1 manuSpecificLumi.write({"mode":1}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"manufacturerCode":4447,"writeUndiv":false}) failed (Data request failed with error: 'MAC transaction expired' (240))
      zigbee.0
      	2025-04-11 17:16:03.662	warn	DeviceConfigure:0x04cf8cdf3c7c87f9 lumi.remote.b486opcn01 Failed to configure. --> ZCL command 0x04cf8cdf3c7c87f9/1 manuSpecificLumi.write({"mode":1}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"manufacturerCode":4447,"writeUndiv":false}) failed (Data request failed with error: 'MAC transaction expired' (240))
      javascript.0
      	2025-04-11 17:15:27.753	error	script.js.Meine_Skripte.BA_Volumio: Error: getaddrinfo ENOTFOUND volumio.local at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26) { errno: -3008, code: 'ENOTFOUND', syscall: 'getaddrinfo', hostname: 'volumio.local'}
      zigbee.0
      	2025-04-11 17:15:22.682	warn	ELEVATED:I02 (79b4) value generated 'true' from device 04cf8cdf3c7c87f9 for 'button_4_single'
      zigbee.0
      	2025-04-11 17:15:22.681	warn	ELEVATED:I02 (79b4) value generated '"button_4_single"' from device 04cf8cdf3c7c87f9 for 'Triggered action (e.g. a button click)'
      zigbee.0
      	2025-04-11 17:15:22.681	warn	ELEVATED:I01 (79b4) message received '{"action":"button_4_single"}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
      zigbee.0
      	2025-04-11 17:15:22.680	warn	ELEVATED:I02 (79b4) value generated '81' from device 04cf8cdf3c7c87f9 for 'Link quality'
      zigbee.0
      	2025-04-11 17:15:22.679	warn	ELEVATED:I01 (79b4) message received '{"linkquality":81}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
      zigbee.0
      	2025-04-11 17:15:22.676	warn	ELEVATED:I01 (79b4) Zigbee Event of Type attributeReport from device 0x04cf8cdf3c7c87f9, incoming event: {"type":"attributeReport","data":{"presentValue":1},"linkquality":81,"groupID":0,"cluster":"genMultistateInput","meta":{"zclTransactionSequenceNumber":5,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":4}
      zigbee.0
      	2025-04-11 17:15:21.733	warn	ELEVATED:I02 (7600) value generated 'true' from device 04cf8cdf3c7c87f9 for 'button_3_single'
      zigbee.0
      	2025-04-11 17:15:21.733	warn	ELEVATED:I02 (7600) value generated '"button_3_single"' from device 04cf8cdf3c7c87f9 for 'Triggered action (e.g. a button click)'
      zigbee.0
      	2025-04-11 17:15:21.733	warn	ELEVATED:I01 (7600) message received '{"action":"button_3_single"}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
      zigbee.0
      	2025-04-11 17:15:21.732	warn	ELEVATED:I02 (7600) value generated '111' from device 04cf8cdf3c7c87f9 for 'Link quality'
      zigbee.0
      	2025-04-11 17:15:21.731	warn	ELEVATED:I01 (7600) message received '{"linkquality":111}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
      zigbee.0
      	2025-04-11 17:15:21.728	warn	ELEVATED:I01 (7600) Zigbee Event of Type attributeReport from device 0x04cf8cdf3c7c87f9, incoming event: {"type":"attributeReport","data":{"presentValue":1},"linkquality":111,"groupID":0,"cluster":"genMultistateInput","meta":{"zclTransactionSequenceNumber":4,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":3}
      zigbee.0
      	2025-04-11 17:15:20.824	warn	ELEVATED:I02 (7273) value generated 'true' from device 04cf8cdf3c7c87f9 for 'button_2_single'
      zigbee.0
      	2025-04-11 17:15:20.824	warn	ELEVATED:I02 (7273) value generated '"button_2_single"' from device 04cf8cdf3c7c87f9 for 'Triggered action (e.g. a button click)'
      zigbee.0
      	2025-04-11 17:15:20.824	warn	ELEVATED:I01 (7273) message received '{"action":"button_2_single"}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
      zigbee.0
      	2025-04-11 17:15:20.823	warn	ELEVATED:I02 (7273) value generated '81' from device 04cf8cdf3c7c87f9 for 'Link quality'
      zigbee.0
      	2025-04-11 17:15:20.822	warn	ELEVATED:I01 (7273) message received '{"linkquality":81}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
      zigbee.0
      	2025-04-11 17:15:20.820	warn	ELEVATED:I01 (7273) Zigbee Event of Type attributeReport from device 0x04cf8cdf3c7c87f9, incoming event: {"type":"attributeReport","data":{"presentValue":1},"linkquality":81,"groupID":0,"cluster":"genMultistateInput","meta":{"zclTransactionSequenceNumber":3,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":2}
      zigbee.0
      	2025-04-11 17:15:19.971	warn	ELEVATED:I02 (6f18) value generated 'true' from device 04cf8cdf3c7c87f9 for 'button_1_single'
      zigbee.0
      	2025-04-11 17:15:19.970	warn	ELEVATED:I02 (6f18) value generated '"button_1_single"' from device 04cf8cdf3c7c87f9 for 'Triggered action (e.g. a button click)'
      zigbee.0
      	2025-04-11 17:15:19.970	warn	ELEVATED:I01 (6f18) message received '{"action":"button_1_single"}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
      zigbee.0
      	2025-04-11 17:15:19.968	warn	ELEVATED:I02 (6f18) value generated '69' from device 04cf8cdf3c7c87f9 for 'Link quality'
      zigbee.0
      	2025-04-11 17:15:19.968	warn	ELEVATED:I01 (6f18) message received '{"linkquality":69}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
      zigbee.0
      	2025-04-11 17:15:19.960	warn	ELEVATED:I01 (6f18) Zigbee Event of Type attributeReport from device 0x04cf8cdf3c7c87f9, incoming event: {"type":"attributeReport","data":{"presentValue":1},"linkquality":69,"groupID":0,"cluster":"genMultistateInput","meta":{"zclTransactionSequenceNumber":2,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}
      AsgothianA 1 Antwort Letzte Antwort
      0
      • T tom_33

        @asgothian Oh, sorry! Nochmal mit allen Tasten.

        zigbee.0
        	2025-04-11 17:16:46.651	warn	DeviceConfigure:0x04cf8cdf3c7c87f9 lumi.remote.b486opcn01 Failed to configure. --> ZCL command 0x04cf8cdf3c7c87f9/1 manuSpecificLumi.write({"mode":1}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"manufacturerCode":4447,"writeUndiv":false}) failed (Data request failed with error: 'MAC transaction expired' (240))
        zigbee.0
        	2025-04-11 17:16:03.662	warn	DeviceConfigure:0x04cf8cdf3c7c87f9 lumi.remote.b486opcn01 Failed to configure. --> ZCL command 0x04cf8cdf3c7c87f9/1 manuSpecificLumi.write({"mode":1}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"manufacturerCode":4447,"writeUndiv":false}) failed (Data request failed with error: 'MAC transaction expired' (240))
        javascript.0
        	2025-04-11 17:15:27.753	error	script.js.Meine_Skripte.BA_Volumio: Error: getaddrinfo ENOTFOUND volumio.local at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26) { errno: -3008, code: 'ENOTFOUND', syscall: 'getaddrinfo', hostname: 'volumio.local'}
        zigbee.0
        	2025-04-11 17:15:22.682	warn	ELEVATED:I02 (79b4) value generated 'true' from device 04cf8cdf3c7c87f9 for 'button_4_single'
        zigbee.0
        	2025-04-11 17:15:22.681	warn	ELEVATED:I02 (79b4) value generated '"button_4_single"' from device 04cf8cdf3c7c87f9 for 'Triggered action (e.g. a button click)'
        zigbee.0
        	2025-04-11 17:15:22.681	warn	ELEVATED:I01 (79b4) message received '{"action":"button_4_single"}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
        zigbee.0
        	2025-04-11 17:15:22.680	warn	ELEVATED:I02 (79b4) value generated '81' from device 04cf8cdf3c7c87f9 for 'Link quality'
        zigbee.0
        	2025-04-11 17:15:22.679	warn	ELEVATED:I01 (79b4) message received '{"linkquality":81}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
        zigbee.0
        	2025-04-11 17:15:22.676	warn	ELEVATED:I01 (79b4) Zigbee Event of Type attributeReport from device 0x04cf8cdf3c7c87f9, incoming event: {"type":"attributeReport","data":{"presentValue":1},"linkquality":81,"groupID":0,"cluster":"genMultistateInput","meta":{"zclTransactionSequenceNumber":5,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":4}
        zigbee.0
        	2025-04-11 17:15:21.733	warn	ELEVATED:I02 (7600) value generated 'true' from device 04cf8cdf3c7c87f9 for 'button_3_single'
        zigbee.0
        	2025-04-11 17:15:21.733	warn	ELEVATED:I02 (7600) value generated '"button_3_single"' from device 04cf8cdf3c7c87f9 for 'Triggered action (e.g. a button click)'
        zigbee.0
        	2025-04-11 17:15:21.733	warn	ELEVATED:I01 (7600) message received '{"action":"button_3_single"}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
        zigbee.0
        	2025-04-11 17:15:21.732	warn	ELEVATED:I02 (7600) value generated '111' from device 04cf8cdf3c7c87f9 for 'Link quality'
        zigbee.0
        	2025-04-11 17:15:21.731	warn	ELEVATED:I01 (7600) message received '{"linkquality":111}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
        zigbee.0
        	2025-04-11 17:15:21.728	warn	ELEVATED:I01 (7600) Zigbee Event of Type attributeReport from device 0x04cf8cdf3c7c87f9, incoming event: {"type":"attributeReport","data":{"presentValue":1},"linkquality":111,"groupID":0,"cluster":"genMultistateInput","meta":{"zclTransactionSequenceNumber":4,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":3}
        zigbee.0
        	2025-04-11 17:15:20.824	warn	ELEVATED:I02 (7273) value generated 'true' from device 04cf8cdf3c7c87f9 for 'button_2_single'
        zigbee.0
        	2025-04-11 17:15:20.824	warn	ELEVATED:I02 (7273) value generated '"button_2_single"' from device 04cf8cdf3c7c87f9 for 'Triggered action (e.g. a button click)'
        zigbee.0
        	2025-04-11 17:15:20.824	warn	ELEVATED:I01 (7273) message received '{"action":"button_2_single"}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
        zigbee.0
        	2025-04-11 17:15:20.823	warn	ELEVATED:I02 (7273) value generated '81' from device 04cf8cdf3c7c87f9 for 'Link quality'
        zigbee.0
        	2025-04-11 17:15:20.822	warn	ELEVATED:I01 (7273) message received '{"linkquality":81}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
        zigbee.0
        	2025-04-11 17:15:20.820	warn	ELEVATED:I01 (7273) Zigbee Event of Type attributeReport from device 0x04cf8cdf3c7c87f9, incoming event: {"type":"attributeReport","data":{"presentValue":1},"linkquality":81,"groupID":0,"cluster":"genMultistateInput","meta":{"zclTransactionSequenceNumber":3,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":2}
        zigbee.0
        	2025-04-11 17:15:19.971	warn	ELEVATED:I02 (6f18) value generated 'true' from device 04cf8cdf3c7c87f9 for 'button_1_single'
        zigbee.0
        	2025-04-11 17:15:19.970	warn	ELEVATED:I02 (6f18) value generated '"button_1_single"' from device 04cf8cdf3c7c87f9 for 'Triggered action (e.g. a button click)'
        zigbee.0
        	2025-04-11 17:15:19.970	warn	ELEVATED:I01 (6f18) message received '{"action":"button_1_single"}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
        zigbee.0
        	2025-04-11 17:15:19.968	warn	ELEVATED:I02 (6f18) value generated '69' from device 04cf8cdf3c7c87f9 for 'Link quality'
        zigbee.0
        	2025-04-11 17:15:19.968	warn	ELEVATED:I01 (6f18) message received '{"linkquality":69}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
        zigbee.0
        	2025-04-11 17:15:19.960	warn	ELEVATED:I01 (6f18) Zigbee Event of Type attributeReport from device 0x04cf8cdf3c7c87f9, incoming event: {"type":"attributeReport","data":{"presentValue":1},"linkquality":69,"groupID":0,"cluster":"genMultistateInput","meta":{"zclTransactionSequenceNumber":2,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}
        AsgothianA Offline
        AsgothianA Offline
        Asgothian
        Developer
        schrieb am zuletzt editiert von
        #285

        @tom_33 sagte in Tester für Zigbee Adapter 2.0.x gesucht:

        @asgothian Oh, sorry! Nochmal mit allen Tasten.

        zigbee.0
        	2025-04-11 17:16:46.651	warn	DeviceConfigure:0x04cf8cdf3c7c87f9 lumi.remote.b486opcn01 Failed to configure. --> ZCL command 0x04cf8cdf3c7c87f9/1 manuSpecificLumi.write({"mode":1}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"manufacturerCode":4447,"writeUndiv":false}) failed (Data request failed with error: 'MAC transaction expired' (240))
        zigbee.0
        	2025-04-11 17:16:03.662	warn	DeviceConfigure:0x04cf8cdf3c7c87f9 lumi.remote.b486opcn01 Failed to configure. --> ZCL command 0x04cf8cdf3c7c87f9/1 manuSpecificLumi.write({"mode":1}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"manufacturerCode":4447,"writeUndiv":false}) failed (Data request failed with error: 'MAC transaction expired' (240))
        javascript.0
        	2025-04-11 17:15:27.753	error	script.js.Meine_Skripte.BA_Volumio: Error: getaddrinfo ENOTFOUND volumio.local at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26) { errno: -3008, code: 'ENOTFOUND', syscall: 'getaddrinfo', hostname: 'volumio.local'}
        zigbee.0
        	2025-04-11 17:15:22.682	warn	ELEVATED:I02 (79b4) value generated 'true' from device 04cf8cdf3c7c87f9 for 'button_4_single'
        zigbee.0
        	2025-04-11 17:15:22.681	warn	ELEVATED:I02 (79b4) value generated '"button_4_single"' from device 04cf8cdf3c7c87f9 for 'Triggered action (e.g. a button click)'
        zigbee.0
        	2025-04-11 17:15:22.681	warn	ELEVATED:I01 (79b4) message received '{"action":"button_4_single"}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
        zigbee.0
        	2025-04-11 17:15:22.680	warn	ELEVATED:I02 (79b4) value generated '81' from device 04cf8cdf3c7c87f9 for 'Link quality'
        zigbee.0
        	2025-04-11 17:15:22.679	warn	ELEVATED:I01 (79b4) message received '{"linkquality":81}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
        zigbee.0
        	2025-04-11 17:15:22.676	warn	ELEVATED:I01 (79b4) Zigbee Event of Type attributeReport from device 0x04cf8cdf3c7c87f9, incoming event: {"type":"attributeReport","data":{"presentValue":1},"linkquality":81,"groupID":0,"cluster":"genMultistateInput","meta":{"zclTransactionSequenceNumber":5,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":4}
        zigbee.0
        	2025-04-11 17:15:21.733	warn	ELEVATED:I02 (7600) value generated 'true' from device 04cf8cdf3c7c87f9 for 'button_3_single'
        zigbee.0
        	2025-04-11 17:15:21.733	warn	ELEVATED:I02 (7600) value generated '"button_3_single"' from device 04cf8cdf3c7c87f9 for 'Triggered action (e.g. a button click)'
        zigbee.0
        	2025-04-11 17:15:21.733	warn	ELEVATED:I01 (7600) message received '{"action":"button_3_single"}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
        zigbee.0
        	2025-04-11 17:15:21.732	warn	ELEVATED:I02 (7600) value generated '111' from device 04cf8cdf3c7c87f9 for 'Link quality'
        zigbee.0
        	2025-04-11 17:15:21.731	warn	ELEVATED:I01 (7600) message received '{"linkquality":111}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
        zigbee.0
        	2025-04-11 17:15:21.728	warn	ELEVATED:I01 (7600) Zigbee Event of Type attributeReport from device 0x04cf8cdf3c7c87f9, incoming event: {"type":"attributeReport","data":{"presentValue":1},"linkquality":111,"groupID":0,"cluster":"genMultistateInput","meta":{"zclTransactionSequenceNumber":4,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":3}
        zigbee.0
        	2025-04-11 17:15:20.824	warn	ELEVATED:I02 (7273) value generated 'true' from device 04cf8cdf3c7c87f9 for 'button_2_single'
        zigbee.0
        	2025-04-11 17:15:20.824	warn	ELEVATED:I02 (7273) value generated '"button_2_single"' from device 04cf8cdf3c7c87f9 for 'Triggered action (e.g. a button click)'
        zigbee.0
        	2025-04-11 17:15:20.824	warn	ELEVATED:I01 (7273) message received '{"action":"button_2_single"}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
        zigbee.0
        	2025-04-11 17:15:20.823	warn	ELEVATED:I02 (7273) value generated '81' from device 04cf8cdf3c7c87f9 for 'Link quality'
        zigbee.0
        	2025-04-11 17:15:20.822	warn	ELEVATED:I01 (7273) message received '{"linkquality":81}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
        zigbee.0
        	2025-04-11 17:15:20.820	warn	ELEVATED:I01 (7273) Zigbee Event of Type attributeReport from device 0x04cf8cdf3c7c87f9, incoming event: {"type":"attributeReport","data":{"presentValue":1},"linkquality":81,"groupID":0,"cluster":"genMultistateInput","meta":{"zclTransactionSequenceNumber":3,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":2}
        zigbee.0
        	2025-04-11 17:15:19.971	warn	ELEVATED:I02 (6f18) value generated 'true' from device 04cf8cdf3c7c87f9 for 'button_1_single'
        zigbee.0
        	2025-04-11 17:15:19.970	warn	ELEVATED:I02 (6f18) value generated '"button_1_single"' from device 04cf8cdf3c7c87f9 for 'Triggered action (e.g. a button click)'
        zigbee.0
        	2025-04-11 17:15:19.970	warn	ELEVATED:I01 (6f18) message received '{"action":"button_1_single"}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
        zigbee.0
        	2025-04-11 17:15:19.968	warn	ELEVATED:I02 (6f18) value generated '69' from device 04cf8cdf3c7c87f9 for 'Link quality'
        zigbee.0
        	2025-04-11 17:15:19.968	warn	ELEVATED:I01 (6f18) message received '{"linkquality":69}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
        zigbee.0
        	2025-04-11 17:15:19.960	warn	ELEVATED:I01 (6f18) Zigbee Event of Type attributeReport from device 0x04cf8cdf3c7c87f9, incoming event: {"type":"attributeReport","data":{"presentValue":1},"linkquality":69,"groupID":0,"cluster":"genMultistateInput","meta":{"zclTransactionSequenceNumber":2,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}
        

        Jetzt sollten alle 'single' clicks im ioBroker ankommen. Bitte das gleiche mit den Doubleclick und tripleclick probieren, und besser einen Screenshot vom Debug Interface zeigen. Dabei die Meldungen 'zusammenfassen' lassen.

        A.

        ioBroker auf RPi4 - Hardware soweit wie möglich via Zigbee.
        "Shit don't work" ist keine Fehlermeldung, sondern ein Fluch.

        T 1 Antwort Letzte Antwort
        0
        • AsgothianA Asgothian

          @tom_33 sagte in Tester für Zigbee Adapter 2.0.x gesucht:

          @asgothian Oh, sorry! Nochmal mit allen Tasten.

          zigbee.0
          	2025-04-11 17:16:46.651	warn	DeviceConfigure:0x04cf8cdf3c7c87f9 lumi.remote.b486opcn01 Failed to configure. --> ZCL command 0x04cf8cdf3c7c87f9/1 manuSpecificLumi.write({"mode":1}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"manufacturerCode":4447,"writeUndiv":false}) failed (Data request failed with error: 'MAC transaction expired' (240))
          zigbee.0
          	2025-04-11 17:16:03.662	warn	DeviceConfigure:0x04cf8cdf3c7c87f9 lumi.remote.b486opcn01 Failed to configure. --> ZCL command 0x04cf8cdf3c7c87f9/1 manuSpecificLumi.write({"mode":1}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"manufacturerCode":4447,"writeUndiv":false}) failed (Data request failed with error: 'MAC transaction expired' (240))
          javascript.0
          	2025-04-11 17:15:27.753	error	script.js.Meine_Skripte.BA_Volumio: Error: getaddrinfo ENOTFOUND volumio.local at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26) { errno: -3008, code: 'ENOTFOUND', syscall: 'getaddrinfo', hostname: 'volumio.local'}
          zigbee.0
          	2025-04-11 17:15:22.682	warn	ELEVATED:I02 (79b4) value generated 'true' from device 04cf8cdf3c7c87f9 for 'button_4_single'
          zigbee.0
          	2025-04-11 17:15:22.681	warn	ELEVATED:I02 (79b4) value generated '"button_4_single"' from device 04cf8cdf3c7c87f9 for 'Triggered action (e.g. a button click)'
          zigbee.0
          	2025-04-11 17:15:22.681	warn	ELEVATED:I01 (79b4) message received '{"action":"button_4_single"}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
          zigbee.0
          	2025-04-11 17:15:22.680	warn	ELEVATED:I02 (79b4) value generated '81' from device 04cf8cdf3c7c87f9 for 'Link quality'
          zigbee.0
          	2025-04-11 17:15:22.679	warn	ELEVATED:I01 (79b4) message received '{"linkquality":81}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
          zigbee.0
          	2025-04-11 17:15:22.676	warn	ELEVATED:I01 (79b4) Zigbee Event of Type attributeReport from device 0x04cf8cdf3c7c87f9, incoming event: {"type":"attributeReport","data":{"presentValue":1},"linkquality":81,"groupID":0,"cluster":"genMultistateInput","meta":{"zclTransactionSequenceNumber":5,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":4}
          zigbee.0
          	2025-04-11 17:15:21.733	warn	ELEVATED:I02 (7600) value generated 'true' from device 04cf8cdf3c7c87f9 for 'button_3_single'
          zigbee.0
          	2025-04-11 17:15:21.733	warn	ELEVATED:I02 (7600) value generated '"button_3_single"' from device 04cf8cdf3c7c87f9 for 'Triggered action (e.g. a button click)'
          zigbee.0
          	2025-04-11 17:15:21.733	warn	ELEVATED:I01 (7600) message received '{"action":"button_3_single"}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
          zigbee.0
          	2025-04-11 17:15:21.732	warn	ELEVATED:I02 (7600) value generated '111' from device 04cf8cdf3c7c87f9 for 'Link quality'
          zigbee.0
          	2025-04-11 17:15:21.731	warn	ELEVATED:I01 (7600) message received '{"linkquality":111}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
          zigbee.0
          	2025-04-11 17:15:21.728	warn	ELEVATED:I01 (7600) Zigbee Event of Type attributeReport from device 0x04cf8cdf3c7c87f9, incoming event: {"type":"attributeReport","data":{"presentValue":1},"linkquality":111,"groupID":0,"cluster":"genMultistateInput","meta":{"zclTransactionSequenceNumber":4,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":3}
          zigbee.0
          	2025-04-11 17:15:20.824	warn	ELEVATED:I02 (7273) value generated 'true' from device 04cf8cdf3c7c87f9 for 'button_2_single'
          zigbee.0
          	2025-04-11 17:15:20.824	warn	ELEVATED:I02 (7273) value generated '"button_2_single"' from device 04cf8cdf3c7c87f9 for 'Triggered action (e.g. a button click)'
          zigbee.0
          	2025-04-11 17:15:20.824	warn	ELEVATED:I01 (7273) message received '{"action":"button_2_single"}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
          zigbee.0
          	2025-04-11 17:15:20.823	warn	ELEVATED:I02 (7273) value generated '81' from device 04cf8cdf3c7c87f9 for 'Link quality'
          zigbee.0
          	2025-04-11 17:15:20.822	warn	ELEVATED:I01 (7273) message received '{"linkquality":81}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
          zigbee.0
          	2025-04-11 17:15:20.820	warn	ELEVATED:I01 (7273) Zigbee Event of Type attributeReport from device 0x04cf8cdf3c7c87f9, incoming event: {"type":"attributeReport","data":{"presentValue":1},"linkquality":81,"groupID":0,"cluster":"genMultistateInput","meta":{"zclTransactionSequenceNumber":3,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":2}
          zigbee.0
          	2025-04-11 17:15:19.971	warn	ELEVATED:I02 (6f18) value generated 'true' from device 04cf8cdf3c7c87f9 for 'button_1_single'
          zigbee.0
          	2025-04-11 17:15:19.970	warn	ELEVATED:I02 (6f18) value generated '"button_1_single"' from device 04cf8cdf3c7c87f9 for 'Triggered action (e.g. a button click)'
          zigbee.0
          	2025-04-11 17:15:19.970	warn	ELEVATED:I01 (6f18) message received '{"action":"button_1_single"}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
          zigbee.0
          	2025-04-11 17:15:19.968	warn	ELEVATED:I02 (6f18) value generated '69' from device 04cf8cdf3c7c87f9 for 'Link quality'
          zigbee.0
          	2025-04-11 17:15:19.968	warn	ELEVATED:I01 (6f18) message received '{"linkquality":69}' from device 04cf8cdf3c7c87f9 type 'WXCJKG12LM'
          zigbee.0
          	2025-04-11 17:15:19.960	warn	ELEVATED:I01 (6f18) Zigbee Event of Type attributeReport from device 0x04cf8cdf3c7c87f9, incoming event: {"type":"attributeReport","data":{"presentValue":1},"linkquality":69,"groupID":0,"cluster":"genMultistateInput","meta":{"zclTransactionSequenceNumber":2,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}
          

          Jetzt sollten alle 'single' clicks im ioBroker ankommen. Bitte das gleiche mit den Doubleclick und tripleclick probieren, und besser einen Screenshot vom Debug Interface zeigen. Dabei die Meldungen 'zusammenfassen' lassen.

          A.

          T Offline
          T Offline
          tom_33
          schrieb am zuletzt editiert von tom_33
          #286

          @asgothian Double: Error Fenster:

          0x04cf8cdf3c7c87f9 lumi.remote.b486opcn01 Failed to configure. --> ZCL command 0x04cf8cdf3c7c87f9/1 manuSpecificLumi.write({"mode":1}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"manufacturerCode":4447,"writeUndiv":false}) failed (Data request failed with error: 'MAC transaction expired' (240))
          
          ID	Zigbee Payload	 	State Payload	ID	value	Flags
          5dff	{"type":"attributeReport", "data":{"presentValue":2}, "linkquality":81, "groupID":0, "cluster":"genMultistateInput", "meta":{"zclTransactionSequenceNumber":9, "frameControl":{"frameType":0, "manufacturerSpecific":false, "direction":1, "disableDefaultResponse":true, "reservedBits":0}}, "endpoint_id":4}		{"action":"button_4_double"}	button_4_double	true	SUCCESS
          	{"action":"button_4_double"}	action	button_4_double	SUCCESS
          	{"linkquality":81}	link_quality	81	SUCCESS
          5a30	{"type":"attributeReport", "data":{"presentValue":2}, "linkquality":93, "groupID":0, "cluster":"genMultistateInput", "meta":{"zclTransactionSequenceNumber":8, "frameControl":{"frameType":0, "manufacturerSpecific":false, "direction":1, "disableDefaultResponse":true, "reservedBits":0}}, "endpoint_id":3}		{"action":"button_3_double"}	button_3_double	true	SUCCESS
          	{"action":"button_3_double"}	action	button_3_double	SUCCESS
          	{"linkquality":93}	link_quality	93	SUCCESS
          5634	{"type":"attributeReport", "data":{"presentValue":2}, "linkquality":78, "groupID":0, "cluster":"genMultistateInput", "meta":{"zclTransactionSequenceNumber":7, "frameControl":{"frameType":0, "manufacturerSpecific":false, "direction":1, "disableDefaultResponse":true, "reservedBits":0}}, "endpoint_id":2}		{"action":"button_2_double"}	button_2_double	true	SUCCESS
          	{"action":"button_2_double"}	action	button_2_double	SUCCESS
          	{"linkquality":78}	link_quality	78	SUCCESS
          525b	{"type":"attributeReport", "data":{"presentValue":2}, "linkquality":54, "groupID":0, "cluster":"genMultistateInput", "meta":{"zclTransactionSequenceNumber":6, "frameControl":{"frameType":0, "manufacturerSpecific":false, "direction":1, "disableDefaultResponse":true, "reservedBits":0}}, "endpoint_id":1}		{"action":"button_1_double"}	button_1_double	true	SUCCESS
          	{"action":"button_1_double"}	action	button_1_double	SUCCESS
          	{"linkquality":54}	link_quality	54	SUCCESS
          

          Triple mit der selben Errormeldung im Fenster

          ID	Zigbee Payload	 	State Payload	ID	value	Flags
          13c2	{"type":"attributeReport", "data":{"presentValue":3}, "linkquality":87, "groupID":0, "cluster":"genMultistateInput", "meta":{"zclTransactionSequenceNumber":13, "frameControl":{"frameType":0, "manufacturerSpecific":false, "direction":1, "disableDefaultResponse":true, "reservedBits":0}}, "endpoint_id":4}		{"action":"button_4_triple"}	button_4_triple	true	SUCCESS
          	{"action":"button_4_triple"}	action	button_4_triple	SUCCESS
          	{"linkquality":87}	link_quality	87	SUCCESS
          0f73	{"type":"attributeReport", "data":{"presentValue":3}, "linkquality":81, "groupID":0, "cluster":"genMultistateInput", "meta":{"zclTransactionSequenceNumber":12, "frameControl":{"frameType":0, "manufacturerSpecific":false, "direction":1, "disableDefaultResponse":true, "reservedBits":0}}, "endpoint_id":3}		{"action":"button_3_triple"}	button_3_triple	true	SUCCESS
          	{"action":"button_3_triple"}	action	button_3_triple	SUCCESS
          	{"linkquality":81}	link_quality	81	SUCCESS
          0b07	{"type":"attributeReport", "data":{"presentValue":3}, "linkquality":72, "groupID":0, "cluster":"genMultistateInput", "meta":{"zclTransactionSequenceNumber":11, "frameControl":{"frameType":0, "manufacturerSpecific":false, "direction":1, "disableDefaultResponse":true, "reservedBits":0}}, "endpoint_id":2}		{"action":"button_2_triple"}	button_2_triple	true	SUCCESS
          	{"action":"button_2_triple"}	action	button_2_triple	SUCCESS
          	{"linkquality":72}	link_quality	72	SUCCESS
          0607	{"type":"attributeReport", "data":{"presentValue":3}, "linkquality":87, "groupID":0, "cluster":"genMultistateInput", "meta":{"zclTransactionSequenceNumber":10, "frameControl":{"frameType":0, "manufacturerSpecific":false, "direction":1, "disableDefaultResponse":true, "reservedBits":0}}, "endpoint_id":1}		{"action":"button_1_triple"}	button_1_triple	true	SUCCESS
          	{"action":"button_1_triple"}	action	button_1_triple	SUCCESS
          	{"linkquality":87}	link_quality	87	SUCCESS
          

          Soweit ich das kapiere, kommt alles richtig an. Auch die schaltbaren Geräte reagieren nicht mehr. Und Hold funktioniert wieder!
          Dann war das entfernen der Batterie mit längerem Warten das Ausschlaggebende!? Ich habe schon gestern die Batt. getauscht, aber nicht so lange gewartet.

          Alle abhängigen Scripte wieder Aktiviert und alles läuft! Hurra!!
          Herzlichen Dank für Alles!!!

          1 Antwort Letzte Antwort
          0
          • AsgothianA Asgothian

            @duffy sagte in Tester für Zigbee Adapter 2.0.x gesucht:

            Hallo zusammen,

            ich habe soeben auch mal auf meinen Test Pi den Zigbee Adapter 2.0.5 installiert.
            Hier sind nur 3 Geräte gekoppelt aber ich werde reich mit Warnungen bedacht mit denen ich so gar nichts anfangen kann.

            Das sind die Warnungen:

            0
            90
            
            Log-Größe: 20.6 KB
            Zeit
            	
            zigbee.0
            	2025-04-11 16:28:05.619	warn	ELEVATED:I02 (2ead) value generated '38.03' from device a4c13883edd22a61 for 'Humidity'
            zigbee.0
            	2025-04-11 16:28:05.619	warn	ELEVATED:I01 (2ead) message received '{"humidity":38.03}' from device a4c13883edd22a61 type 'LYWSD03MMC-z'
            zigbee.0
            	2025-04-11 16:28:05.617	warn	ELEVATED:I02 (2ead) value generated '102' from device a4c13883edd22a61 for 'Link quality'
            zigbee.0
            	2025-04-11 16:28:05.617	warn	ELEVATED:I01 (2ead) message received '{"linkquality":102}' from device a4c13883edd22a61 type 'LYWSD03MMC-z'
            zigbee.0
            	2025-04-11 16:28:05.616	warn	ELEVATED:I02 (2ea4) value generated '20.4' from device a4c13883edd22a61 for 'Temperature'
            zigbee.0
            	2025-04-11 16:28:05.615	warn	ELEVATED:I01 (2ea4) message received '{"temperature":20.4}' from device a4c13883edd22a61 type 'LYWSD03MMC-z'
            zigbee.0
            	2025-04-11 16:28:05.614	warn	ELEVATED:I02 (2ea4) value generated '102' from device a4c13883edd22a61 for 'Link quality'
            zigbee.0
            	2025-04-11 16:28:05.612	warn	ELEVATED:I01 (2ea4) message received '{"linkquality":102}' from device a4c13883edd22a61 type 'LYWSD03MMC-z'
            zigbee.0
            	2025-04-11 16:28:05.421	warn	ELEVATED:I01 (2ead) Zigbee Event of Type attributeReport from device 0xa4c13883edd22a61, incoming event: {"type":"attributeReport","data":{"measuredValue":3803},"linkquality":102,"groupID":0,"cluster":"msRelativeHumidity","meta":{"zclTransactionSequenceNumber":67,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}
            zigbee.0
            	2025-04-11 16:28:05.413	warn	ELEVATED:I01 (2ea4) Zigbee Event of Type attributeReport from device 0xa4c13883edd22a61, incoming event: {"type":"attributeReport","data":{"measuredValue":2040},"linkquality":102,"groupID":0,"cluster":"msTemperatureMeasurement","meta":{"zclTransactionSequenceNumber":66,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}
            admin.0
            	2025-04-11 16:28:03.193	info	==> Connected system.user.admin from ::ffff:192.168.178.116
            zigbee.0
            	2025-04-11 16:27:15.319	warn	ELEVATED:I02 (6aed) value generated '38.58' from device a4c13883edd22a61 for 'Humidity'
            zigbee.0
            	2025-04-11 16:27:15.319	warn	ELEVATED:I01 (6aed) message received '{"humidity":38.58}' from device a4c13883edd22a61 type 'LYWSD03MMC-z'
            zigbee.0
            	2025-04-11 16:27:15.317	warn	ELEVATED:I02 (6aed) value generated '98' from device a4c13883edd22a61 for 'Link quality'
            zigbee.0
            	2025-04-11 16:27:15.316	warn	ELEVATED:I01 (6aed) message received '{"linkquality":98}' from device a4c13883edd22a61 type 'LYWSD03MMC-z'
            zigbee.0
            	2025-04-11 16:27:15.310	warn	ELEVATED:I01 (6aed) Zigbee Event of Type attributeReport from device 0xa4c13883edd22a61, incoming event: {"type":"attributeReport","data":{"measuredValue":3858},"linkquality":98,"groupID":0,"cluster":"msRelativeHumidity","meta":{"zclTransactionSequenceNumber":65,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}
            zigbee.0
            	2025-04-11 16:26:35.234	warn	ELEVATED:I02 (ce59) value generated '39.12' from device a4c13883edd22a61 for 'Humidity'
            zigbee.0
            	2025-04-11 16:26:35.234	warn	ELEVATED:I01 (ce59) message received '{"humidity":39.12}' from device a4c13883edd22a61 type 'LYWSD03MMC-z'
            zigbee.0
            	2025-04-11 16:26:35.232	warn	ELEVATED:I02 (ce59) value generated '94' from device a4c13883edd22a61 for 'Link quality'
            zigbee.0
            	2025-04-11 16:26:35.231	warn	ELEVATED:I01 (ce59) message received '{"linkquality":94}' from device a4c13883edd22a61 type 'LYWSD03MMC-z'
            zigbee.0
            	2025-04-11 16:26:35.226	warn	ELEVATED:I01 (ce59) Zigbee Event of Type attributeReport from device 0xa4c13883edd22a61, incoming event: {"type":"attributeReport","data":{"measuredValue":3912},"linkquality":94,"groupID":0,"cluster":"msRelativeHumidity","meta":{"zclTransactionSequenceNumber":64,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}
            zigbee.0
            	2025-04-11 16:26:32.125	warn	ELEVATED:I02 (c235) value generated '72' from device a4c13855231a9ca2 for 'Link quality'
            zigbee.0
            	2025-04-11 16:26:32.125	warn	ELEVATED:I01 (c235) message received '{"linkquality":72}' from device a4c13855231a9ca2 type 'TS0001_fingerbot'
            zigbee.0
            	2025-04-11 16:26:32.123	warn	ELEVATED:NOCONV (c235) No converter available for 'TS0001_fingerbot' 'a4c13855231a9ca2' with cluster 'genBasic' and type 'attributeReport'
            zigbee.0
            	2025-04-11 16:26:32.118	warn	ELEVATED:I01 (c235) Zigbee Event of Type attributeReport from device 0xa4c13855231a9ca2, incoming event: {"type":"attributeReport","data":{"65503":"�n\\/\u0013&o\\/\u0013�o\\/\u0013\u0000\u0000\u0000\u0000\u0011Yp\\/\u0012�p\\/\u0012\u0000\u0000\u0000\u0000\u0011���/\u0012"},"linkquality":72,"groupID":0,"cluster":"genBasic","meta":{"zclTransactionSequenceNumber":183,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":false,"reservedBits":0}},"endpoint_id":1}
            zigbee.0
            	2025-04-11 16:26:31.986	warn	ELEVATED:I02 (c1a4) value generated '69' from device a4c13855231a9ca2 for 'Link quality'
            zigbee.0
            	2025-04-11 16:26:31.985	warn	ELEVATED:I01 (c1a4) message received '{"linkquality":69}' from device a4c13855231a9ca2 type 'TS0001_fingerbot'
            zigbee.0
            	2025-04-11 16:26:31.984	warn	ELEVATED:NOCONV (c1a4) No converter available for 'TS0001_fingerbot' 'a4c13855231a9ca2' with cluster 'genBasic' and type 'attributeReport'
            zigbee.0
            	2025-04-11 16:26:31.972	warn	ELEVATED:I01 (c1a4) Zigbee Event of Type attributeReport from device 0xa4c13855231a9ca2, incoming event: {"type":"attributeReport","data":{"65503":"Q_\\/\u0013T`\\/\u0013�b\\/\u0012�b\\/\u0012\u0000\u0000\u0000\u0000\u0011\u0000\u0000\u0000\u0000\u0011\u0000\u0000\u0000\u0000\u0011\u0000\u0000\u0000\u0000\u0011\u0000\u0000\u0000\u0000\u0011\u001d\u0000\u0000\u0000\u0013Qn\\/\u0012�n\\/\u0013"},"linkquality":69,"groupID":0,"cluster":"genBasic","meta":{"zclTransactionSequenceNumber":182,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":false,"reservedBits":0}},"endpoint_id":1}
            zigbee.0
            	2025-04-11 16:26:25.218	warn	ELEVATED:I02 (a737) value generated '39.78' from device a4c13883edd22a61 for 'Humidity'
            zigbee.0
            	2025-04-11 16:26:25.217	warn	ELEVATED:I01 (a737) message received '{"humidity":39.78}' from device a4c13883edd22a61 type 'LYWSD03MMC-z'
            zigbee.0
            	2025-04-11 16:26:25.215	warn	ELEVATED:I02 (a737) value generated '87' from device a4c13883edd22a61 for 'Link quality'
            zigbee.0
            	2025-04-11 16:26:25.214	warn	ELEVATED:I01 (a737) message received '{"linkquality":87}' from device a4c13883edd22a61 type 'LYWSD03MMC-z'
            zigbee.0
            	2025-04-11 16:26:25.208	warn	ELEVATED:I01 (a737) Zigbee Event of Type attributeReport from device 0xa4c13883edd22a61, incoming event: {"type":"attributeReport","data":{"measuredValue":3978},"linkquality":87,"groupID":0,"cluster":"msRelativeHumidity","meta":{"zclTransactionSequenceNumber":63,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}
            

            Das hier sind die Geräte:

            c7b7da9e-b815-402e-a3c5-71d8f942ed8d-grafik.png

            796c6f6e-26d3-4788-8e42-82f290034cc7-grafik.png

            Da ich was Zigbee betrifft ein echter schisser bin, zumal ich auch nicht wirklich viel Ahnung davon habe, habe ich es erst mal , wie bereits erwähnt, auf dem Tes Pi installiert. Ich will vermeiden bei meinem aktuellen Aktiv System im dunklen zu stehen.

            Kann mir bitte jemand sagen was die Warnungen bedeuten und was ich dagegen tun kann?

            Es grüßt euch Duffy

            click mal auf die grünen bugs auf den Kacheln, dann sind die Meldungen auch weg.

            A.

            DuffyD Online
            DuffyD Online
            Duffy
            schrieb am zuletzt editiert von
            #287

            click mal auf die grünen bugs auf den Kacheln, dann sind die Meldungen auch weg.

            A.

            Danke dir.

            Nix besonderes; iob auf Respberry pi 4 (8GB) mit 32 GB SSD
            Node.js: v22.21.0
            NPM: 10.9.4
            js-controller 7.0.7
            Linux: Trixie

            1 Antwort Letzte Antwort
            0
            • AsgothianA Asgothian

              @schranzer Ich kann dir nicht sagen was du einstellen musst. Dazu hab ich zu wenig Informationen. Da musst du schon deutlich mehr Details liefern.

              A.

              S Offline
              S Offline
              Schranzer
              schrieb am zuletzt editiert von
              #288

              @asgothian Also ich habe wie gesagt den SMLIGHT SLZB-06p10. Dann habe ich auf einem Raspberry Pi 5 den Zigbee Adapter mit der Github Version 3.0.0 installiert (neu). Alles was IoBroker betrifft ist auf dem neusten Stand, da es eine Neuinstallation ist.

              Ich komme auf die Homepage des SMLIGHT SLZB-06p10 und kann dort diese Ip auslesen mit dem Port:tcp://192.168.188.123:6638
              6d8bb110-c056-44d6-871c-4c2e46357765-image.png

              Ich habe verstanden das ich diese ipadresse mit Port in Com Anschluss rein machen muss und dann unten eigentlich die Hardware auswählen muss.
              a0f99500-8bd1-4d2d-bbaa-813b8b3e33b9-image.png

              Der SLZB-06p10 hat glaub ich einen Texas Instrument Chip dementsprechend müsse das so doch passen oder? Weil er findet ihn einfach nicht.
              Brauchst du sonst noch Infos? VG

              AsgothianA 1 Antwort Letzte Antwort
              0
              • S Schranzer

                @asgothian Also ich habe wie gesagt den SMLIGHT SLZB-06p10. Dann habe ich auf einem Raspberry Pi 5 den Zigbee Adapter mit der Github Version 3.0.0 installiert (neu). Alles was IoBroker betrifft ist auf dem neusten Stand, da es eine Neuinstallation ist.

                Ich komme auf die Homepage des SMLIGHT SLZB-06p10 und kann dort diese Ip auslesen mit dem Port:tcp://192.168.188.123:6638
                6d8bb110-c056-44d6-871c-4c2e46357765-image.png

                Ich habe verstanden das ich diese ipadresse mit Port in Com Anschluss rein machen muss und dann unten eigentlich die Hardware auswählen muss.
                a0f99500-8bd1-4d2d-bbaa-813b8b3e33b9-image.png

                Der SLZB-06p10 hat glaub ich einen Texas Instrument Chip dementsprechend müsse das so doch passen oder? Weil er findet ihn einfach nicht.
                Brauchst du sonst noch Infos? VG

                AsgothianA Offline
                AsgothianA Offline
                Asgothian
                Developer
                schrieb am zuletzt editiert von
                #289

                @schranzer sagte in Tester für Zigbee Adapter 2.0.x gesucht:

                Weil er findet ihn einfach nicht.
                Brauchst du sonst noch Infos? VG

                • Was passiert wenn du auf den Button 'test port' clickst. (weiter unten in der Konfiguration ist ein Log-Auszug. Diesen posten
                • Wenn 'test port' erfolgreich ist: Was passiert wenn du auf 'start stop' clickst (auch wieder Log Auszug aus dem Log posten - ggf. warten bis eine endgültige Nachricht kommt.

                A.

                ioBroker auf RPi4 - Hardware soweit wie möglich via Zigbee.
                "Shit don't work" ist keine Fehlermeldung, sondern ein Fluch.

                D S 2 Antworten Letzte Antwort
                0
                • T tom_33

                  @rushmed Ich habe den Taster mehrmals gelöscht und angelernt. Sogar die "Empfänger" resetet. Die bleiben hartnäckig zusammen. Aber ich werde das "Rezept" von asgothian durcharbeiten. Danke

                  D Offline
                  D Offline
                  dimaiv
                  schrieb am zuletzt editiert von dimaiv
                  #290

                  @tom_33
                  Ich habe oben schon geschrieben,
                  bei dem Taster (Opple) Reconfiguration funktioniert nur mit mehrmals klicken auf die Reset Taste, nicht auf eine von vier vorderen.
                  Und es gibt noch ein Datenpunkt Operation Mode. Da muss "Command" stehen.

                  Wichtig: beim Anlernen, nach Interview , Reset Taste weiter klicken bis Meldung kommt: Konfiguration erfolgreich...

                  ioBroker- NUC8i3 / Proxmox / VM
                  Node.js v22.21.0
                  NPM v10.9.4
                  JS controller 7.0.7
                  Admin 7.7.19
                  ZigBee Adapter 3.2.5
                  Zigbee LAN Gateway CC2652P
                  Zigbee Firmware 20250321

                  T 1 Antwort Letzte Antwort
                  0
                  • AsgothianA Asgothian

                    @schranzer sagte in Tester für Zigbee Adapter 2.0.x gesucht:

                    Weil er findet ihn einfach nicht.
                    Brauchst du sonst noch Infos? VG

                    • Was passiert wenn du auf den Button 'test port' clickst. (weiter unten in der Konfiguration ist ein Log-Auszug. Diesen posten
                    • Wenn 'test port' erfolgreich ist: Was passiert wenn du auf 'start stop' clickst (auch wieder Log Auszug aus dem Log posten - ggf. warten bis eine endgültige Nachricht kommt.

                    A.

                    D Offline
                    D Offline
                    dimaiv
                    schrieb am zuletzt editiert von
                    #291

                    @asgothian
                    Zur Info:
                    Ich habe mehrere Opple Taster da, die funktionieren mit 3.0.0 und früheren Versionen einwandfrei.

                    ioBroker- NUC8i3 / Proxmox / VM
                    Node.js v22.21.0
                    NPM v10.9.4
                    JS controller 7.0.7
                    Admin 7.7.19
                    ZigBee Adapter 3.2.5
                    Zigbee LAN Gateway CC2652P
                    Zigbee Firmware 20250321

                    1 Antwort Letzte Antwort
                    3
                    • D dimaiv

                      @tom_33
                      Ich habe oben schon geschrieben,
                      bei dem Taster (Opple) Reconfiguration funktioniert nur mit mehrmals klicken auf die Reset Taste, nicht auf eine von vier vorderen.
                      Und es gibt noch ein Datenpunkt Operation Mode. Da muss "Command" stehen.

                      Wichtig: beim Anlernen, nach Interview , Reset Taste weiter klicken bis Meldung kommt: Konfiguration erfolgreich...

                      T Offline
                      T Offline
                      tom_33
                      schrieb am zuletzt editiert von tom_33
                      #292

                      @dimaiv Vielen Dank für den Tipp. Mein zweiter Opple, welcher genauso alle Zigbees Steckdosen und Lampen gekapert hat, konnte ich mit dem längeren entfernen der Batterie wieder zähmen. Geprüft habe ich ihn, mit der oben angeführten Angaben von asgothian, trotzdem. Von den 1-Taster Aqara wird die Hold Funktion noch nicht ausgewertet. Ich hoffe, dieselbe Prozedur hilft hier auch.

                      Bei "Command" steht bei mir in der Spalte "Wert" nix. In der Spalte "Name" : Operation mode, select "command" to enable bindings (wake up the device before changing modes!)

                      1 Antwort Letzte Antwort
                      0
                      • AsgothianA Asgothian

                        @schranzer sagte in Tester für Zigbee Adapter 2.0.x gesucht:

                        Weil er findet ihn einfach nicht.
                        Brauchst du sonst noch Infos? VG

                        • Was passiert wenn du auf den Button 'test port' clickst. (weiter unten in der Konfiguration ist ein Log-Auszug. Diesen posten
                        • Wenn 'test port' erfolgreich ist: Was passiert wenn du auf 'start stop' clickst (auch wieder Log Auszug aus dem Log posten - ggf. warten bis eine endgültige Nachricht kommt.

                        A.

                        S Offline
                        S Offline
                        Schranzer
                        schrieb am zuletzt editiert von
                        #293

                        @asgothian
                        Zur ersten Frage, das ist die Ausgabe, wenn ich auf Test Port drücke:

                        attempting dns lookup for 192.168.188.123
                        dns lookup for tcp://192.168.188.123:6638 produced 192.168.188.123
                        connected successfully to connect to 192.168.188.123 port 6638
                        

                        Zur zweiten Frage, das ist die Ausgabe, wenn ich auf Start/Stop drücke:

                        overriding zigbee options with:
                        extPanID : b574a814e360b356
                        panID : 820
                        channel : 11
                        port : tcp://192.168.188.123:6638
                        adapterType : zstack
                        baudRate : 115200
                        precfgkey : 01030507090B0D0F00020406080A0C0D
                        flowCTRL : false
                        Starting Adapter npm ...
                        Installed Version: ioBroker/ioBroker.zigbee (Converters 23.25.0 Herdsman 3.5.1)
                        Starting zigbee-herdsman...
                        Unable to obtain herdsman settings
                        Starting zigbee-herdsman problem : Error while opening socket
                        Error herdsman start
                        

                        Viele Grüße

                        AsgothianA 1 Antwort Letzte Antwort
                        0
                        • S Schranzer

                          @asgothian
                          Zur ersten Frage, das ist die Ausgabe, wenn ich auf Test Port drücke:

                          attempting dns lookup for 192.168.188.123
                          dns lookup for tcp://192.168.188.123:6638 produced 192.168.188.123
                          connected successfully to connect to 192.168.188.123 port 6638
                          

                          Zur zweiten Frage, das ist die Ausgabe, wenn ich auf Start/Stop drücke:

                          overriding zigbee options with:
                          extPanID : b574a814e360b356
                          panID : 820
                          channel : 11
                          port : tcp://192.168.188.123:6638
                          adapterType : zstack
                          baudRate : 115200
                          precfgkey : 01030507090B0D0F00020406080A0C0D
                          flowCTRL : false
                          Starting Adapter npm ...
                          Installed Version: ioBroker/ioBroker.zigbee (Converters 23.25.0 Herdsman 3.5.1)
                          Starting zigbee-herdsman...
                          Unable to obtain herdsman settings
                          Starting zigbee-herdsman problem : Error while opening socket
                          Error herdsman start
                          

                          Viele Grüße

                          AsgothianA Offline
                          AsgothianA Offline
                          Asgothian
                          Developer
                          schrieb am zuletzt editiert von
                          #294

                          @schranzer die zigbee Firmware läuft auf deinem Netzwerk Koordinator nicht. Bitte hart zurücksetzen (Strom ab 30 sek. Warten, Strom an und neu versuchen das zigbee subsystem zu starten.

                          A.

                          ioBroker auf RPi4 - Hardware soweit wie möglich via Zigbee.
                          "Shit don't work" ist keine Fehlermeldung, sondern ein Fluch.

                          S 1 Antwort Letzte Antwort
                          0
                          • AsgothianA Asgothian

                            @schranzer die zigbee Firmware läuft auf deinem Netzwerk Koordinator nicht. Bitte hart zurücksetzen (Strom ab 30 sek. Warten, Strom an und neu versuchen das zigbee subsystem zu starten.

                            A.

                            S Offline
                            S Offline
                            Schranzer
                            schrieb am zuletzt editiert von Schranzer
                            #295

                            @asgothian Ich habe das Problem gelöst.
                            Lösungsweg:

                            • Ich habe den SMLIGHT SLZB-06p10 komplett neu aufgesetzt, mit der aller neuesten Dev-Version v2.8.2.dev3 (Diese hat deutlich mehr Einstellung Funktionen als die alte)
                            • Typ: Für den SMLIGHT SLZB-06p10 "Ti" einstellen bei Hardware
                            • PanID: 13410
                            • Channel: 11
                            • COM Anschluss: tcp://EIGENEIP:6638
                            • start Zigbee network automatically Hacken aktiv
                            • flow control Hacken aktiv (bin mir nicht sicher was es macht)

                            Ich habe zuerst den SMLIGHT SLZB-06p10 aufgesetzt das er bereit ist und DANN den Zigbee Adapter eingeschalten (welcher schon fertig konfiguriert war).

                            Und noch mal danke für deine Hilfe :)!

                            c91c6f8c-6376-4856-9239-572ce2979cb5-image.png

                            AsgothianA 1 Antwort Letzte Antwort
                            0
                            • S Schranzer

                              @asgothian Ich habe das Problem gelöst.
                              Lösungsweg:

                              • Ich habe den SMLIGHT SLZB-06p10 komplett neu aufgesetzt, mit der aller neuesten Dev-Version v2.8.2.dev3 (Diese hat deutlich mehr Einstellung Funktionen als die alte)
                              • Typ: Für den SMLIGHT SLZB-06p10 "Ti" einstellen bei Hardware
                              • PanID: 13410
                              • Channel: 11
                              • COM Anschluss: tcp://EIGENEIP:6638
                              • start Zigbee network automatically Hacken aktiv
                              • flow control Hacken aktiv (bin mir nicht sicher was es macht)

                              Ich habe zuerst den SMLIGHT SLZB-06p10 aufgesetzt das er bereit ist und DANN den Zigbee Adapter eingeschalten (welcher schon fertig konfiguriert war).

                              Und noch mal danke für deine Hilfe :)!

                              c91c6f8c-6376-4856-9239-572ce2979cb5-image.png

                              AsgothianA Offline
                              AsgothianA Offline
                              Asgothian
                              Developer
                              schrieb am zuletzt editiert von
                              #296

                              @schranzer sagte in Tester für Zigbee Adapter 2.0.x gesucht:

                              flow control Hacken aktiv (bin mir nicht sicher was es macht)

                              In deinem Fall: Nichts. Dieser Haken ist nur bei USB Kommunikation notwendig.

                              A.

                              ioBroker auf RPi4 - Hardware soweit wie möglich via Zigbee.
                              "Shit don't work" ist keine Fehlermeldung, sondern ein Fluch.

                              1 Antwort Letzte Antwort
                              0
                              • M Offline
                                M Offline
                                martinschm
                                schrieb am zuletzt editiert von martinschm
                                #297

                                Hi,
                                ich hab die Tage auf Zigbee 2 upgedatet.
                                Heute kam erst die Meldung das einige Geräte offline sind, komischerweise alles Geräte mit 230V

                                Und jetzt bekam ich im Adapter erst eine Fehlermeldung als ich das pairing aktivieren wollte und dann das der Adapter ständig abstürzt.

                                Im Log steht das hier

                                zigbee.0
                                2025-04-14 18:52:47.993	info	terminating
                                
                                zigbee.0
                                2025-04-14 18:52:47.953	error	Failed to open the network: TypeError: Cannot read properties of undefined (reading 'permitJoin') at Controller.permitJoin (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:259:35) at ZigbeeController.permitJoin (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:659:33) at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:634:24) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:1037:17)
                                
                                zigbee.0
                                2025-04-14 18:52:47.383	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
                                
                                zigbee.0
                                2025-04-14 18:52:47.381	info	terminating
                                
                                zigbee.0
                                2025-04-14 18:52:47.380	info	Saved local configuration data
                                
                                zigbee.0
                                2025-04-14 18:52:47.378	info	local config saved
                                
                                zigbee.0
                                2025-04-14 18:52:47.376	info	cleaned everything up...
                                
                                zigbee.0
                                2025-04-14 18:52:47.373	error	undefined
                                
                                zigbee.0
                                2025-04-14 18:52:47.372	error	unhandled promise rejection: undefined
                                
                                zigbee.0
                                2025-04-14 18:52:47.372	error	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().
                                
                                zigbee.0
                                2025-04-14 18:52:47.369	error	Starting zigbee-herdsman problem : Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
                                
                                zigbee.0
                                2025-04-14 18:52:47.321	info	Unable to obtain herdsman settings
                                
                                zigbee.0
                                2025-04-14 18:52:20.699	info	Starting Zigbee-Herdsman
                                
                                zigbee.0
                                2025-04-14 18:52:20.696	info	Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.1)
                                
                                zigbee.0
                                2025-04-14 18:52:20.642	info	Starting Adapter npm ...
                                
                                zigbee.0
                                2025-04-14 18:52:20.640	info	--- creating device debug ---
                                
                                zigbee.0
                                2025-04-14 18:52:20.635	info	delete old Backup files. keep only last 10
                                
                                zigbee.0
                                2025-04-14 18:52:20.616	info	--> transmitPower : normal
                                
                                zigbee.0
                                2025-04-14 18:52:20.604	info	init localConfig
                                
                                zigbee.0
                                2025-04-14 18:52:20.565	info	starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.18.1, js-controller: 7.0.6
                                
                                host.smarthome
                                2025-04-14 18:52:15.676	info	instance system.adapter.zigbee.0 in version "2.0.5" started with pid 2760598
                                
                                device-watcher.0
                                2025-04-14 18:52:04.279	info	Instanz-Wachdog:zigbee.0: Instanz deaktiviert
                                
                                host.smarthome
                                2025-04-14 18:51:44.252	info	Restart adapter system.adapter.zigbee.0 because enabled
                                
                                host.smarthome
                                2025-04-14 18:51:44.251	error	instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                                
                                zigbee.0
                                2025-04-14 18:51:43.649	error	unhandled promise rejection: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:633:26) at Socket.emit (node:events:518:28) at TCP.<anonymous> (node:net:343:12)
                                
                                zigbee.0
                                2025-04-14 18:51:43.649	error	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().
                                
                                zigbee.0
                                2025-04-14 18:51:43.649	error	Error: DB closed
                                
                                zigbee.0
                                2025-04-14 18:51:43.649	error	DB closed
                                

                                Bei mir läuft
                                js-controller 7.0.6
                                zigbee 2.0.5
                                Node.js: v20.18.1(20.19.0)
                                NPM: 10.8.2

                                10cc0f6a-6156-4a53-bd8f-b8f408d6f234-image.png

                                AsgothianA 1 Antwort Letzte Antwort
                                0
                                • M martinschm

                                  Hi,
                                  ich hab die Tage auf Zigbee 2 upgedatet.
                                  Heute kam erst die Meldung das einige Geräte offline sind, komischerweise alles Geräte mit 230V

                                  Und jetzt bekam ich im Adapter erst eine Fehlermeldung als ich das pairing aktivieren wollte und dann das der Adapter ständig abstürzt.

                                  Im Log steht das hier

                                  zigbee.0
                                  2025-04-14 18:52:47.993	info	terminating
                                  
                                  zigbee.0
                                  2025-04-14 18:52:47.953	error	Failed to open the network: TypeError: Cannot read properties of undefined (reading 'permitJoin') at Controller.permitJoin (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:259:35) at ZigbeeController.permitJoin (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:659:33) at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:634:24) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:1037:17)
                                  
                                  zigbee.0
                                  2025-04-14 18:52:47.383	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
                                  
                                  zigbee.0
                                  2025-04-14 18:52:47.381	info	terminating
                                  
                                  zigbee.0
                                  2025-04-14 18:52:47.380	info	Saved local configuration data
                                  
                                  zigbee.0
                                  2025-04-14 18:52:47.378	info	local config saved
                                  
                                  zigbee.0
                                  2025-04-14 18:52:47.376	info	cleaned everything up...
                                  
                                  zigbee.0
                                  2025-04-14 18:52:47.373	error	undefined
                                  
                                  zigbee.0
                                  2025-04-14 18:52:47.372	error	unhandled promise rejection: undefined
                                  
                                  zigbee.0
                                  2025-04-14 18:52:47.372	error	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().
                                  
                                  zigbee.0
                                  2025-04-14 18:52:47.369	error	Starting zigbee-herdsman problem : Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
                                  
                                  zigbee.0
                                  2025-04-14 18:52:47.321	info	Unable to obtain herdsman settings
                                  
                                  zigbee.0
                                  2025-04-14 18:52:20.699	info	Starting Zigbee-Herdsman
                                  
                                  zigbee.0
                                  2025-04-14 18:52:20.696	info	Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.1)
                                  
                                  zigbee.0
                                  2025-04-14 18:52:20.642	info	Starting Adapter npm ...
                                  
                                  zigbee.0
                                  2025-04-14 18:52:20.640	info	--- creating device debug ---
                                  
                                  zigbee.0
                                  2025-04-14 18:52:20.635	info	delete old Backup files. keep only last 10
                                  
                                  zigbee.0
                                  2025-04-14 18:52:20.616	info	--> transmitPower : normal
                                  
                                  zigbee.0
                                  2025-04-14 18:52:20.604	info	init localConfig
                                  
                                  zigbee.0
                                  2025-04-14 18:52:20.565	info	starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.18.1, js-controller: 7.0.6
                                  
                                  host.smarthome
                                  2025-04-14 18:52:15.676	info	instance system.adapter.zigbee.0 in version "2.0.5" started with pid 2760598
                                  
                                  device-watcher.0
                                  2025-04-14 18:52:04.279	info	Instanz-Wachdog:zigbee.0: Instanz deaktiviert
                                  
                                  host.smarthome
                                  2025-04-14 18:51:44.252	info	Restart adapter system.adapter.zigbee.0 because enabled
                                  
                                  host.smarthome
                                  2025-04-14 18:51:44.251	error	instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                                  
                                  zigbee.0
                                  2025-04-14 18:51:43.649	error	unhandled promise rejection: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:633:26) at Socket.emit (node:events:518:28) at TCP.<anonymous> (node:net:343:12)
                                  
                                  zigbee.0
                                  2025-04-14 18:51:43.649	error	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().
                                  
                                  zigbee.0
                                  2025-04-14 18:51:43.649	error	Error: DB closed
                                  
                                  zigbee.0
                                  2025-04-14 18:51:43.649	error	DB closed
                                  

                                  Bei mir läuft
                                  js-controller 7.0.6
                                  zigbee 2.0.5
                                  Node.js: v20.18.1(20.19.0)
                                  NPM: 10.8.2

                                  10cc0f6a-6156-4a53-bd8f-b8f408d6f234-image.png

                                  AsgothianA Offline
                                  AsgothianA Offline
                                  Asgothian
                                  Developer
                                  schrieb am zuletzt editiert von Asgothian
                                  #298

                                  @martinschm sagte in Tester für Zigbee Adapter 2.0.x gesucht:

                                  Starting zigbee-herdsman problem : Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)

                                  Du darfst davon ausgehen das der Adapter insgesamt nicht sauber gestartet wurde. Das sieht man oft erst wenn man versucht aktiv mit dem Adapter zu interagieren.

                                  Die weiter oben gepostet Meldung zeigt das der Adapter keine Verbindung zur Firmware auf dem Koordinator herstellen kann. Ich würde als erstes folgendes Empfehlen:

                                  • Adapter anhalten - um sicher zu gehen das er nicht läuft
                                  • Koordinator stromlos machen. Bei USB Koordinatoren: Abziehen 30 Sekunden warten. Anstecken. Bei Netzwerk Koordinatoren: Stromversorgung kappen, 60 Sekunden warten, Stromversorgung wieder herstellen
                                  • Adapter starten
                                  • im Log schauen ob der Adapter erfolgreich gestartet wird.

                                  A.
                                  Nachtrag: Da du anscheinend DDDDDDDDDDDDDDDD als deine PanID hast kann es auch sein das der Adapter nicht startet weil die konfigurierte von der vom ZH benutzten Pan ID abweicht - ob das der Fall ist hängt davon ab von welcher Version du das Update gemacht hast.

                                  ioBroker auf RPi4 - Hardware soweit wie möglich via Zigbee.
                                  "Shit don't work" ist keine Fehlermeldung, sondern ein Fluch.

                                  M 1 Antwort Letzte Antwort
                                  0
                                  • AsgothianA Asgothian

                                    @martinschm sagte in Tester für Zigbee Adapter 2.0.x gesucht:

                                    Starting zigbee-herdsman problem : Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)

                                    Du darfst davon ausgehen das der Adapter insgesamt nicht sauber gestartet wurde. Das sieht man oft erst wenn man versucht aktiv mit dem Adapter zu interagieren.

                                    Die weiter oben gepostet Meldung zeigt das der Adapter keine Verbindung zur Firmware auf dem Koordinator herstellen kann. Ich würde als erstes folgendes Empfehlen:

                                    • Adapter anhalten - um sicher zu gehen das er nicht läuft
                                    • Koordinator stromlos machen. Bei USB Koordinatoren: Abziehen 30 Sekunden warten. Anstecken. Bei Netzwerk Koordinatoren: Stromversorgung kappen, 60 Sekunden warten, Stromversorgung wieder herstellen
                                    • Adapter starten
                                    • im Log schauen ob der Adapter erfolgreich gestartet wird.

                                    A.
                                    Nachtrag: Da du anscheinend DDDDDDDDDDDDDDDD als deine PanID hast kann es auch sein das der Adapter nicht startet weil die konfigurierte von der vom ZH benutzten Pan ID abweicht - ob das der Fall ist hängt davon ab von welcher Version du das Update gemacht hast.

                                    M Offline
                                    M Offline
                                    martinschm
                                    schrieb am zuletzt editiert von martinschm
                                    #299

                                    @asgothian

                                    Hi,

                                    Koordinator stromlos machen hat erstmal geholfen. Die normalen Geräte scheinen sich wieder zu verbinden nur die 230V Geräte machen wohl noch Probleme.

                                    zigbee.0
                                    2025-04-15 13:05:07.531	info	Timeout trying to configure 0x04cf8cdf3c7db935 WXCJKG13LM (starting CoM).
                                    
                                    zigbee.0
                                    2025-04-15 13:04:42.140	info	Timeout trying to configure 0x00158d0004fcf82a HS1SA (starting CoM).
                                    
                                    zigbee.0
                                    2025-04-15 13:04:42.125	info	Handled all devices Queued for configuration.
                                    
                                    zigbee.0
                                    2025-04-15 13:04:37.618	info	Failed to ping 0x385cfbfffe89e560 ZBMINIL2
                                    
                                    zigbee.0
                                    2025-04-15 13:04:37.125	info	Configuring 0x04cf8cdf3c7db935 WXCJKG13LM
                                    
                                    zigbee.0
                                    2025-04-15 13:04:37.125	info	DeviceConfigureQueue configuring 0x04cf8cdf3c7db935 lumi.remote.b686opcn01
                                    
                                    zigbee.0
                                    2025-04-15 13:04:32.333	info	Failed to ping 0x04cd15fffe02d085 TS0121
                                    
                                    zigbee.0
                                    2025-04-15 13:04:32.244	info	Failed to ping 0x04cd15fffe02dd9b TS0121
                                    
                                    zigbee.0
                                    2025-04-15 13:04:32.125	info	Configuring 0x00158d0004fcf82a HS1SA
                                    
                                    zigbee.0
                                    2025-04-15 13:04:32.124	info	DeviceConfigureQueue configuring 0x00158d0004fcf82a SmokeSensor-N-3.0
                                    
                                    zigbee.0
                                    2025-04-15 13:04:31.954	info	Failed to ping 0x04cd15fffe067cd7 TS0121
                                    
                                    zigbee.0
                                    2025-04-15 13:04:30.962	info	Failed to ping 0x842e14fffe35a210 TS0121
                                    
                                    zigbee.0
                                    2025-04-15 13:04:30.256	info	Failed to ping 0x588e81fffedbcfe2 TS0121
                                    
                                    zigbee.0
                                    2025-04-15 13:04:29.853	info	Failed to ping 0x842e14fffe1262bf TS0121
                                    
                                    zigbee.0
                                    2025-04-15 13:04:29.527	info	Failed to ping 0x04cd15fffe02d9f3 TS0121
                                    
                                    zigbee.0
                                    2025-04-15 13:04:28.810	info	Failed to ping 0x385cfbfffe8eb302 ZBMINIL2
                                    
                                    zigbee.0
                                    2025-04-15 13:04:28.549	info	Failed to ping 0x14b457fffe2ea155 TRADFRI bulb E27 WW 806lm
                                    
                                    zigbee.0
                                    2025-04-15 13:04:27.391	info	debug devices set to []
                                    
                                    zigbee.0
                                    2025-04-15 13:04:27.128	info	DeviceConfigure 0x04cf8cdf3c7db935 WXCJKG13LM needed - Device added to Configuration Queue
                                    
                                    zigbee.0
                                    2025-04-15 13:04:27.122	info	DeviceConfigure 0x00158d0004fcf82a HS1SA needed - Device added to Configuration Queue
                                    
                                    zigbee.0
                                    2025-04-15 13:04:27.027	info	Zigbee started
                                    
                                    zigbee.0
                                    2025-04-15 13:04:27.023	info	Currently 70 devices are joined:
                                    zigbee.0
                                    2025-04-15 13:04:26.531	info	0x00158d0004b487d4 (addr 62422): HS1SA - HEIMAN Smoke detector (EndDevice)
                                    
                                    zigbee.0
                                    2025-04-15 13:04:26.498	info	0x00158d00033ad77d (addr 20078): RTCGQ11LM - Aqara Motion sensor (EndDevice)
                                    
                                    zigbee.0
                                    2025-04-15 13:04:26.348	info	Unable to disable LED, unsupported function.
                                    
                                    zigbee.0
                                    2025-04-15 13:04:26.345	info	Zigbee-Herdsman started successfully with Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20200805}}
                                    
                                    zigbee.0
                                    2025-04-15 13:04:22.855	info	Starting Zigbee-Herdsman
                                    
                                    zigbee.0
                                    2025-04-15 13:04:22.853	info	Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.1)
                                    
                                    zigbee.0
                                    2025-04-15 13:04:22.771	info	Starting Adapter npm ...
                                    
                                    zigbee.0
                                    2025-04-15 13:04:22.768	info	--- creating device debug ---
                                    
                                    zigbee.0
                                    2025-04-15 13:04:22.761	info	delete old Backup files. keep only last 10
                                    
                                    zigbee.0
                                    2025-04-15 13:04:22.741	info	--> transmitPower : normal
                                    
                                    zigbee.0
                                    2025-04-15 13:04:22.728	info	init localConfig
                                    
                                    zigbee.0
                                    2025-04-15 13:04:22.691	info	starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.18.1, js-controller: 7.0.6
                                    

                                    Bezüglich der PanID, da weiß ich nicht ob ich da mal was geändert habe.
                                    Ich hab von @1.10.14 to @2.0.5 aktualisiert

                                    M 1 Antwort Letzte Antwort
                                    0
                                    • K KBH10

                                      @asgothian Ja, das denke ich auch. Hätte mir einiges an Arbeit erspart! :-)

                                      Aber egal, dank deiner Hilfe läuft es nun wieder soweit, besten Dank!

                                      R Offline
                                      R Offline
                                      Rene 5
                                      schrieb am zuletzt editiert von Rene 5
                                      #300

                                      @kbh10

                                      Ich habe leider auch ein Problem mit der Version.
                                      Alle meine Geräte waren nicht mehr erreichbar, dann habe ich den Adapter gelöscht und wollte ihn neu installieren.
                                      Jetzt bekomme ich noch nicht mal mehr den Adapter zum laufen.

                                      Meine Daten
                                      Node.js: v20.19.0
                                      NPM: 10.8.2
                                      55745abc-91a1-4a98-929c-44e64d91a082-image.png

                                      Ich hoffe ihr könnt mir helfen.

                                      edit
                                      bekomme den Adapter einfach nicht zum laufen
                                      Bin nach deiner Anleitung vorgegangen

                                      0c4eb5a9-d4a4-4ca7-ba3f-ea664c393fe4-image.png

                                      Viele Grüße

                                      AsgothianA 1 Antwort Letzte Antwort
                                      0
                                      • R Rene 5

                                        @kbh10

                                        Ich habe leider auch ein Problem mit der Version.
                                        Alle meine Geräte waren nicht mehr erreichbar, dann habe ich den Adapter gelöscht und wollte ihn neu installieren.
                                        Jetzt bekomme ich noch nicht mal mehr den Adapter zum laufen.

                                        Meine Daten
                                        Node.js: v20.19.0
                                        NPM: 10.8.2
                                        55745abc-91a1-4a98-929c-44e64d91a082-image.png

                                        Ich hoffe ihr könnt mir helfen.

                                        edit
                                        bekomme den Adapter einfach nicht zum laufen
                                        Bin nach deiner Anleitung vorgegangen

                                        0c4eb5a9-d4a4-4ca7-ba3f-ea664c393fe4-image.png

                                        Viele Grüße

                                        AsgothianA Offline
                                        AsgothianA Offline
                                        Asgothian
                                        Developer
                                        schrieb am zuletzt editiert von
                                        #301

                                        @rene-5 bitte genau dem folgen was ich oben im thread geschrieben hab,

                                        A.

                                        ioBroker auf RPi4 - Hardware soweit wie möglich via Zigbee.
                                        "Shit don't work" ist keine Fehlermeldung, sondern ein Fluch.

                                        1 Antwort Letzte Antwort
                                        0
                                        • F Offline
                                          F Offline
                                          FI_84
                                          schrieb am zuletzt editiert von FI_84
                                          #302
                                          • Adaptername: zigbee
                                          • Adapterversion: 2.0.5
                                          • js-controller Version: 7.0.6
                                          • Admin Version: ...
                                          • Hardwaresystem: Pi4
                                          • Arbeitsspeicher: 4GB
                                          • Festplattenart: SSD
                                          • Betriebssystem: Pi OS Lite
                                          • Nodejs-Version: 20.19.0
                                          • NPM-Version: 10.8.2

                                          Moin.

                                          ich wollte endlich mal mein System aktualisieren. Hatte immer noch Buster im Einsatz :scream: auf einer SD Karte und wollte auch auf eine SSD wechseln.

                                          Also Bookworm auf die SSD geflash, Iob instaliert und alles per Backitup wiederhergestellt....

                                          Funktioniert auch alles bis auf den Zigbee adapter.
                                          Bereits auch wieder gelöscht und manuell installiert. Keine Funktion :anguished:

                                          zigbee.0 2025-04-15 16:20:29.000	info	terminating
                                          zigbee.0 2025-04-15 16:20:28.986	error	Failed to open the network: TypeError: Cannot read properties of undefined (reading 'permitJoin') at Controller.permitJoin (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/controller.ts:315:35) at ZigbeeController.permitJoin (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:659:33) at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:634:24) at processTicksAndRejections (node:internal/process/task_queues:95:5) at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:1037:17)
                                          zigbee.0 2025-04-15 16:20:28.730	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
                                          zigbee.0 2025-04-15 16:20:28.728	info	terminating
                                          zigbee.0 2025-04-15 16:20:28.726	info	Saved local configuration data
                                          zigbee.0 2025-04-15 16:20:28.725	info	local config saved
                                          zigbee.0 2025-04-15 16:20:28.723	info	cleaned everything up...
                                          zigbee.0 2025-04-15 16:20:28.653	error	undefined
                                          zigbee.0 2025-04-15 16:20:28.652	error	unhandled promise rejection: undefined
                                          zigbee.0 2025-04-15 16:20:28.651	error	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().
                                          zigbee.0 2025-04-15 16:20:28.648	error	Starting zigbee-herdsman problem : Error: Operation not supported, cannot set
                                          zigbee.0 2025-04-15 16:20:28.602	info	Unable to obtain herdsman settings
                                          zigbee.0 2025-04-15 16:20:26.770	info	Starting Zigbee-Herdsman
                                          zigbee.0 2025-04-15 16:20:26.768	info	Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.1)
                                          zigbee.0 2025-04-15 16:20:26.692	info	Starting Adapter npm ...
                                          zigbee.0 2025-04-15 16:20:26.690	info	--- creating device debug ---
                                          zigbee.0 2025-04-15 16:20:26.686	info	delete old Backup files. keep only last 10
                                          zigbee.0 2025-04-15 16:20:26.668	info	--> transmitPower : normal
                                          zigbee.0 2025-04-15 16:20:26.656	info	init localConfig
                                          zigbee.0 2025-04-15 16:20:26.617	info	starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.0, js-controller: 7.0.6
                                          

                                          Als Stick hab ich den 12/2020 von @arteck gekaufte "CC2538+CC2592 PA Zigbee Stick/Platine" im Einsatz. Auch nie neu geflash lief immer ohne Probleme.

                                          Danke für Eure Hilfe

                                          Mfg
                                          Fi

                                          AsgothianA 1 Antwort Letzte Antwort
                                          0
                                          Antworten
                                          • In einem neuen Thema antworten
                                          Anmelden zum Antworten
                                          • Älteste zuerst
                                          • Neuste zuerst
                                          • Meiste Stimmen


                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate

                                          561

                                          Online

                                          32.4k

                                          Benutzer

                                          81.4k

                                          Themen

                                          1.3m

                                          Beiträge
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Anmelden

                                          • Du hast noch kein Konto? Registrieren

                                          • Anmelden oder registrieren, um zu suchen
                                          • Erster Beitrag
                                            Letzter Beitrag
                                          0
                                          • Home
                                          • Aktuell
                                          • Tags
                                          • Ungelesen 0
                                          • Kategorien
                                          • Unreplied
                                          • Beliebt
                                          • GitHub
                                          • Docu
                                          • Hilfe