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

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Entwicklung
  4. ZigBee neue/unbekannte Geräte - ab 1.3.0

NEWS

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    11
    1
    483

  • Weihnachtsangebot 2025! 🎄
    BluefoxB
    Bluefox
    24
    1
    1.6k

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

ZigBee neue/unbekannte Geräte - ab 1.3.0

Geplant Angeheftet Gesperrt Verschoben Entwicklung
zigbeeneuer adapterconverterherdsman
231 Beiträge 50 Kommentatoren 38.0k Aufrufe 51 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.
  • R Offline
    R Offline
    RS
    schrieb am zuletzt editiert von
    #195

    Hallo hätte eine bitte,
    wäre es möglich diese Lampe von HUE hinzuzufügenKachel.JPG Informationen.JPG

    https://www.amazon.de/Philips-Hue-Erweiterung-warmweißes-kompatibel/dp/B0152WXI0E/ref=sr_1_13?adgrpid=72789819002&dchild=1&gclid=EAIaIQobChMIjP77zpmZ7QIVUud3Ch2DVAwiEAAYASAAEgJscPD_BwE&hvadid=352756286125&hvdev=c&hvlocphy=9042250&hvnetw=g&hvqmt=b&hvrand=2324547971509752261&hvtargid=kwd-299530017350&hydadcr=13860_1725593&keywords=philips+hue+e27&qid=1606152887&sr=8-13&tag=googhydr08-21

    ich hoffe die Infos sind ok so.

    MfG

    RS

    R 1 Antwort Letzte Antwort
    0
    • Holger EtzelH Offline
      Holger EtzelH Offline
      Holger Etzel
      schrieb am zuletzt editiert von
      #196

      Hallo,
      ich hätte mal wieder einen Schalter.
      Vielleicht kann sich jemand dem Schalter annehmen und hinzufügen.
      Danke schon mal im voraus.

      Unbenannt.PNG

      Unbenannt1.PNG

      1 Antwort Letzte Antwort
      0
      • R RS

        Hallo hätte eine bitte,
        wäre es möglich diese Lampe von HUE hinzuzufügenKachel.JPG Informationen.JPG

        https://www.amazon.de/Philips-Hue-Erweiterung-warmweißes-kompatibel/dp/B0152WXI0E/ref=sr_1_13?adgrpid=72789819002&dchild=1&gclid=EAIaIQobChMIjP77zpmZ7QIVUud3Ch2DVAwiEAAYASAAEgJscPD_BwE&hvadid=352756286125&hvdev=c&hvlocphy=9042250&hvnetw=g&hvqmt=b&hvrand=2324547971509752261&hvtargid=kwd-299530017350&hydadcr=13860_1725593&keywords=philips+hue+e27&qid=1606152887&sr=8-13&tag=googhydr08-21

        ich hoffe die Infos sind ok so.

        MfG

        RS

        R Offline
        R Offline
        RS
        schrieb am zuletzt editiert von
        #197

        @RS
        mit der Version 1.3.9dev funktioniert es jetzt.

        Trotzdem Danke

        arteckA 1 Antwort Letzte Antwort
        0
        • R RS

          @RS
          mit der Version 1.3.9dev funktioniert es jetzt.

          Trotzdem Danke

          arteckA Offline
          arteckA Offline
          arteck
          Developer Most Active
          schrieb am zuletzt editiert von arteck
          #198

          @RS du hast eine alpha Version isntalliert... mal so ganz neben bei..da geht vielles aber noch nicht alles

          https://forum.iobroker.net/topic/38971/zigbee-neue-version-1-3-1dev-auf-git

          zigbee hab ich, zwave auch, nuc's genauso und HA auch

          1 Antwort Letzte Antwort
          0
          • arteckA arteck

            @Newan ist

            toniT Offline
            toniT Offline
            toni
            schrieb am zuletzt editiert von
            #199

            @arteck erstmal Danke für die Hilfe der Aqara Wall Switch ist jetzt drin! Jedoch funktioniert das "click event" nicht. Vielleicht kannst du auch dieses Problem noch lösen?
            Zur Info: Ich konnte den switch nur über den CC2531 Stick, jedoch nicht über den Conbee 2 verbinden (Zigbee2MQTT, V.: 1.3.1)

            Bildschirmfoto 2020-11-24 um 20.02.57.png

            Ohne Titel.jpg

            1 Antwort Letzte Antwort
            0
            • H Offline
              H Offline
              Holgee
              schrieb am zuletzt editiert von
              #200

              Servus,

              gerade eben habe ich auf gut Glück einen Viessmann ViCare Heizkörper-Thermostat "Model ZK03840" ausprobiert, der mir aber leider nicht korrekt in der 1.3.9dev erkannt wurde. Über zigbee2mqtt solle er angeblich laufen.

              Model ZK03840

              bcf6d7ca-2939-427d-83cd-4209ccabe53d-image.png

              d001db3a-1577-4f44-b891-059787205dcb-image.png

              5c956234-44d6-40fd-931e-7ba0162f293b-image.png

              Kopplungsfortschritt:

              Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
              Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
              Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
              Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
              Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
              Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
              Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
              Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
              Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
              Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
              Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
              Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
              Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
              Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
              Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
              Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
              Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
              Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
              Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
              Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
              Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
              Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
              Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
              Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
              Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
              Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
              New device joined '0x90fd9ffffe4a5ee3' model ZK03840
              Interview successful: {"friendly_name":"0x90fd9ffffe4a5ee3","model":"ZK03840","vendor":"Viessmann","description":"ViCare radiator thermostat valve","supported":true}
              Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
              Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
              Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
              Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
              Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
              Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
              Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
              Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
              Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
              Device '0x90fd9ffffe4a5ee3' announced itself
              Interview started: 0x90fd9ffffe4a5ee3
              Pairing started
              

              Wäre cool, den in ioBroker nutzen zu können :sunglasses:

              Grüße
              Holger

              arteckA 1 Antwort Letzte Antwort
              0
              • H Holgee

                Servus,

                gerade eben habe ich auf gut Glück einen Viessmann ViCare Heizkörper-Thermostat "Model ZK03840" ausprobiert, der mir aber leider nicht korrekt in der 1.3.9dev erkannt wurde. Über zigbee2mqtt solle er angeblich laufen.

                Model ZK03840

                bcf6d7ca-2939-427d-83cd-4209ccabe53d-image.png

                d001db3a-1577-4f44-b891-059787205dcb-image.png

                5c956234-44d6-40fd-931e-7ba0162f293b-image.png

                Kopplungsfortschritt:

                Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
                Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
                Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
                Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
                Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
                Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
                Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
                Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
                Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
                Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
                Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
                Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
                Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
                Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
                Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
                Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
                Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
                Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
                Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
                Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
                Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
                Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
                Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
                Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
                Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
                Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
                New device joined '0x90fd9ffffe4a5ee3' model ZK03840
                Interview successful: {"friendly_name":"0x90fd9ffffe4a5ee3","model":"ZK03840","vendor":"Viessmann","description":"ViCare radiator thermostat valve","supported":true}
                Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
                Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
                Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
                Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
                Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
                Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
                Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
                Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
                Error: Device 0x90fd9ffffe4a5ee3 "ZK03840" not described in statesMapping.. undefined
                Device '0x90fd9ffffe4a5ee3' announced itself
                Interview started: 0x90fd9ffffe4a5ee3
                Pairing started
                

                Wäre cool, den in ioBroker nutzen zu können :sunglasses:

                Grüße
                Holger

                arteckA Offline
                arteckA Offline
                arteck
                Developer Most Active
                schrieb am zuletzt editiert von
                #201

                @Holgee der ist zwar drin aber nich nicht zu ende ausgeprägt..das wird dauern

                zigbee hab ich, zwave auch, nuc's genauso und HA auch

                Holger EtzelH 1 Antwort Letzte Antwort
                0
                • arteckA arteck

                  @Holgee der ist zwar drin aber nich nicht zu ende ausgeprägt..das wird dauern

                  Holger EtzelH Offline
                  Holger EtzelH Offline
                  Holger Etzel
                  schrieb am zuletzt editiert von
                  #202

                  @arteck
                  Ich habe aber immer ein Pech

                  AsgothianA 1 Antwort Letzte Antwort
                  0
                  • Holger EtzelH Holger Etzel

                    @arteck
                    Ich habe aber immer ein Pech

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

                    @Holgee

                    Wir können zusammen versuchen die fehlenden Teile in Gang zu bekommen - entweder per discord + anydesk, oder Du sendest mir einen Thermostat als Arbeitsobjekt und ich schick den zurück wenn ich durch bin.

                    Das wäre der 4. Thermostat für mich.

                    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
                      MartyBr
                      schrieb am zuletzt editiert von MartyBr
                      #204

                      Hallo,

                      ich habe hier 4 NeoSmart Plugs.

                      Hersteller: immax
                      Typ: 07048L

                      Edit 13:46 Uhr
                      Zigbee Adapter 1.3.1

                      f09e1c28-1d09-4c98-9f10-d21c4e95b055-image.png

                      c9c82593-dae8-401e-a08a-55a6cd6837de-image.png

                      code_text
                      zigbee.0	2020-11-27 13:27:42.262	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 13:27:36.685	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 13:27:36.231	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 13:27:36.231	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 13:27:36.230	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 13:27:36.116	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 13:27:36.115	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 13:27:36.115	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 13:27:35.707	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 13:27:35.570	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 13:27:35.454	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 13:27:35.335	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 13:27:35.220	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 13:27:35.109	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 13:27:34.987	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 13:27:34.871	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 13:27:34.759	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 13:27:34.613	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 13:27:11.275	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 13:27:10.856	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 13:27:10.856	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 13:27:10.856	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 13:27:10.736	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 13:27:10.736	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 13:27:10.736	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 13:27:10.286	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 13:27:10.170	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 13:27:10.055	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 13:27:09.940	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 13:27:09.825	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 13:27:09.709	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 13:27:09.588	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 13:27:09.476	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 13:27:09.362	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 13:27:09.238	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 13:27:09.233	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      
                      
                      

                      Werden weitere Daten benötigt? Muss der Adapter im Debug Modus laufen?

                      Edit 17:25 Uhr
                      Start Adapter im Debug Modus:

                      zigbee.0	2020-11-27 17:24:52.646	debug	(28071) No converter available for 'RB 250 C' with cluster 'genOta' and type 'commandQueryNextImageRequest'
                      zigbee.0	2020-11-27 17:24:52.645	debug	(28071) Type commandQueryNextImageRequest device {"type":"device","device":{"ID":3,"_type":"Router","_ieeeAddr":"0x14b457fffe2be766","_networkAddress":53069,"_manufacturerID":4454,"_endpoints":[{"ID":
                      zigbee.0	2020-11-27 17:24:52.645	debug	(28071) Received Zigbee message from '0x14b457fffe2be766', type 'commandQueryNextImageRequest', cluster 'genOta', data '{"fieldControl":0,"manufacturerCode":4454,"imageType":281,"fileVersion":27730795
                      zigbee.0	2020-11-27 17:24:52.645	debug	(28071) handleMessage. {"type":"commandQueryNextImageRequest","device":{"ID":3,"_type":"Router","_ieeeAddr":"0x14b457fffe2be766","_networkAddress":53069,"_manufacturerID":4454,"_endpoints":[{"ID":1,"p
                      zigbee.0	2020-11-27 17:24:49.615	debug	(28071) No converter available for 'RB 250 C' with cluster 'genOta' and type 'commandQueryNextImageRequest'
                      zigbee.0	2020-11-27 17:24:49.613	debug	(28071) Type commandQueryNextImageRequest device {"type":"device","device":{"ID":3,"_type":"Router","_ieeeAddr":"0x14b457fffe2be766","_networkAddress":53069,"_manufacturerID":4454,"_endpoints":[{"ID":
                      zigbee.0	2020-11-27 17:24:49.612	debug	(28071) Received Zigbee message from '0x14b457fffe2be766', type 'commandQueryNextImageRequest', cluster 'genOta', data '{"fieldControl":0,"manufacturerCode":4454,"imageType":281,"fileVersion":27730795
                      zigbee.0	2020-11-27 17:24:49.612	debug	(28071) handleMessage. {"type":"commandQueryNextImageRequest","device":{"ID":3,"_type":"Router","_ieeeAddr":"0x14b457fffe2be766","_networkAddress":53069,"_manufacturerID":4454,"_endpoints":[{"ID":1,"p
                      zigbee.0	2020-11-27 17:24:46.580	debug	(28071) No converter available for 'RB 250 C' with cluster 'genOta' and type 'commandQueryNextImageRequest'
                      zigbee.0	2020-11-27 17:24:46.579	debug	(28071) Type commandQueryNextImageRequest device {"type":"device","device":{"ID":3,"_type":"Router","_ieeeAddr":"0x14b457fffe2be766","_networkAddress":53069,"_manufacturerID":4454,"_endpoints":[{"ID":
                      zigbee.0	2020-11-27 17:24:46.579	debug	(28071) Received Zigbee message from '0x14b457fffe2be766', type 'commandQueryNextImageRequest', cluster 'genOta', data '{"fieldControl":0,"manufacturerCode":4454,"imageType":281,"fileVersion":27730795
                      zigbee.0	2020-11-27 17:24:46.578	debug	(28071) handleMessage. {"type":"commandQueryNextImageRequest","device":{"ID":3,"_type":"Router","_ieeeAddr":"0x14b457fffe2be766","_networkAddress":53069,"_manufacturerID":4454,"_endpoints":[{"ID":1,"p
                      zigbee.0	2020-11-27 17:24:43.548	debug	(28071) No converter available for 'RB 250 C' with cluster 'genOta' and type 'commandQueryNextImageRequest'
                      zigbee.0	2020-11-27 17:24:43.546	debug	(28071) Type commandQueryNextImageRequest device {"type":"device","device":{"ID":3,"_type":"Router","_ieeeAddr":"0x14b457fffe2be766","_networkAddress":53069,"_manufacturerID":4454,"_endpoints":[{"ID":
                      zigbee.0	2020-11-27 17:24:43.546	debug	(28071) Received Zigbee message from '0x14b457fffe2be766', type 'commandQueryNextImageRequest', cluster 'genOta', data '{"fieldControl":0,"manufacturerCode":4454,"imageType":281,"fileVersion":27730795
                      zigbee.0	2020-11-27 17:24:43.545	debug	(28071) handleMessage. {"type":"commandQueryNextImageRequest","device":{"ID":3,"_type":"Router","_ieeeAddr":"0x14b457fffe2be766","_networkAddress":53069,"_manufacturerID":4454,"_endpoints":[{"ID":1,"p
                      zigbee.0	2020-11-27 17:24:40.507	debug	(28071) No converter available for 'RB 250 C' with cluster 'genOta' and type 'commandQueryNextImageRequest'
                      zigbee.0	2020-11-27 17:24:40.505	debug	(28071) Type commandQueryNextImageRequest device {"type":"device","device":{"ID":3,"_type":"Router","_ieeeAddr":"0x14b457fffe2be766","_networkAddress":53069,"_manufacturerID":4454,"_endpoints":[{"ID":
                      zigbee.0	2020-11-27 17:24:40.504	debug	(28071) Received Zigbee message from '0x14b457fffe2be766', type 'commandQueryNextImageRequest', cluster 'genOta', data '{"fieldControl":0,"manufacturerCode":4454,"imageType":281,"fileVersion":27730795
                      zigbee.0	2020-11-27 17:24:40.504	debug	(28071) handleMessage. {"type":"commandQueryNextImageRequest","device":{"ID":3,"_type":"Router","_ieeeAddr":"0x14b457fffe2be766","_networkAddress":53069,"_manufacturerID":4454,"_endpoints":[{"ID":1,"p
                      zigbee.0	2020-11-27 17:24:07.156	error	(28071) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 17:24:07.156	debug	(28071) Publish available for 0xccccccfffeeaa411 = true
                      zigbee.0	2020-11-27 17:24:07.156	debug	(28071) Publish available for 0x14b457fffe2be766 = true
                      zigbee.0	2020-11-27 17:24:07.151	debug	(28071) Publish available for 0x00158d0004186d23 = true
                      zigbee.0	2020-11-27 17:24:06.222	error	(28071) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 17:24:06.157	info	(28071) Zigbee started
                      zigbee.0	2020-11-27 17:24:06.156	info	(28071) 0xccccccfffeeaa411 (addr 10186): 07048L - Immax NEO SMART plug (Router)
                      zigbee.0	2020-11-27 17:24:06.156	debug	(28071) New device event: {"type":"device","device":{"ID":4,"_type":"Router","_ieeeAddr":"0xccccccfffeeaa411","_networkAddress":10186,"_manufacturerID":4151,"_endpoints":[{"ID":1,"profileID":260,"devi
                      zigbee.0	2020-11-27 17:24:06.156	info	(28071) 0x14b457fffe2be766 (addr 53069): RB 250 C - Innr E14 bulb RGBW (Router)
                      zigbee.0	2020-11-27 17:24:06.155	debug	(28071) New device event: {"type":"device","device":{"ID":3,"_type":"Router","_ieeeAddr":"0x14b457fffe2be766","_networkAddress":53069,"_manufacturerID":4454,"_endpoints":[{"ID":1,"profileID":260,"devi
                      zigbee.0	2020-11-27 17:24:06.154	info	(28071) 0x00158d0004186d23 (addr 11972): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
                      zigbee.0	2020-11-27 17:24:06.152	debug	(28071) New device event: {"type":"device","device":{"ID":2,"_type":"EndDevice","_ieeeAddr":"0x00158d0004186d23","_networkAddress":11972,"_manufacturerID":4151,"_endpoints":[{"ID":1,"profileID":260,"d
                      zigbee.0	2020-11-27 17:24:06.150	debug	(28071) DeviceConfigure 0xccccccfffeeaa411 Plug-230V-ZB3.0 not needed
                      zigbee.0	2020-11-27 17:24:06.150	debug	(28071) DeviceConfigure 0x14b457fffe2be766 RB 250 C not needed
                      zigbee.0	2020-11-27 17:24:06.150	debug	(28071) DeviceConfigure 0x00158d0004186d23 lumi.weather not needed
                      zigbee.0	2020-11-27 17:24:06.150	error	(28071) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 17:24:06.150	debug	(28071) Publish available for 0xccccccfffeeaa411 = true
                      zigbee.0	2020-11-27 17:24:06.149	debug	(28071) Publish available for 0x14b457fffe2be766 = true
                      zigbee.0	2020-11-27 17:24:06.149	debug	(28071) Publish available for 0x00158d0004186d23 = true
                      zigbee.0	2020-11-27 17:24:06.149	info	(28071) Currently 3 devices are joined:
                      zigbee.0	2020-11-27 17:24:06.144	info	(28071) --> transmitPower : high
                      zigbee.0	2020-11-27 17:24:06.144	info	(28071) Unable to disable LED, unsupported function.
                      zigbee.0	2020-11-27 17:24:06.144	info	(28071) Disable LED
                      zigbee.0	2020-11-27 17:24:06.144	debug	(28071) Zigbee network parameters: {"panID":6756,"extendedPanID":"0xddddddddddddddde","channel":11}
                      zigbee.0	2020-11-27 17:24:06.139	info	(28071) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20200925}}
                      zigbee.0	2020-11-27 17:24:06.138	debug	(28071) zigbee-herdsman started
                      zigbee.0	2020-11-27 17:24:05.740	debug	(28071) system.adapter.admin.0: logging true
                      zigbee.0	2020-11-27 17:24:04.251	debug	(28071) Backup /opt/iobroker/iobroker-data/zigbee_0/backup_2020_11_27-17_24_04.tar.gz success
                      zigbee.0	2020-11-27 17:24:04.199	debug	(28071) Starting zigbee-herdsman...
                      zigbee.0	2020-11-27 17:24:04.199	info	(28071) Starting Zigbee npm ...
                      zigbee.0	2020-11-27 17:24:04.181	debug	(28071) Using zigbee-herdsman with settings: {"network":{"panID":6756,"extendedPanID":[222,221,221,221,221,221,221,221],"channelList":[11],"networkKey":[1,3,5,7,9,11,13,15,0,2,4,6,8,10,12,13]},"datab
                      zigbee.0	2020-11-27 17:24:04.170	info	(28071) starting. Version 1.3.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.19.1, js-controller: 3.1.6
                      zigbee.0	2020-11-27 17:24:03.198	debug	(28071) statesDB connected
                      zigbee.0	2020-11-27 17:24:03.197	debug	(28071) States connected to redis: 127.0.0.1:6379
                      zigbee.0	2020-11-27 17:24:03.195	debug	(28071) States create System PubSub Client
                      zigbee.0	2020-11-27 17:24:03.194	debug	(28071) States create User PubSub Client
                      zigbee.0	2020-11-27 17:24:03.193	debug	(28071) Redis States: Use Redis connection: 127.0.0.1:6379
                      zigbee.0	2020-11-27 17:24:03.192	debug	(28071) objectDB connected
                      zigbee.0	2020-11-27 17:24:03.190	debug	(28071) Objects connected to redis: 0.0.0.0:9001
                      zigbee.0	2020-11-27 17:24:03.177	debug	(28071) Objects client initialize lua scripts
                      zigbee.0	2020-11-27 17:24:03.177	debug	(28071) Objects create User PubSub Client
                      zigbee.0	2020-11-27 17:24:03.177	debug	(28071) Objects create System PubSub Client
                      zigbee.0	2020-11-27 17:24:03.176	debug	(28071) Objects client ready ... initialize now
                      zigbee.0	2020-11-27 17:24:03.159	debug	(28071) Redis Objects: Use Redis connection: 0.0.0.0:9001
                      zigbee.0	2020-11-27 17:23:59.796	error	(28055) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 17:23:33.334	error	(28055) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 17:23:32.392	error	(28055) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 17:23:32.331	error	(28055) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 17:23:21.247	error	(28016) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 17:19:16.051	error	(28016) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 17:19:13.026	error	(28016) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 17:19:10.002	error	(28016) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 17:19:06.969	error	(28016) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 17:19:03.956	error	(28016) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 17:16:43.654	error	(28016) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 17:16:42.720	error	(28016) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 17:16:42.650	error	(28016) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 17:16:36.392	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 17:13:54.250	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 17:08:54.158	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 17:08:51.133	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 17:08:48.108	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 17:08:45.077	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 17:08:42.059	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 17:04:21.209	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:59:21.099	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:58:32.259	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:58:29.234	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:58:26.210	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:58:23.184	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:58:20.159	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:58:10.552	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:53:10.461	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:48:10.366	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:48:07.342	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:48:04.317	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:48:01.283	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:47:58.267	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:47:48.656	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:42:48.563	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:37:48.470	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:37:45.444	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:37:42.419	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:37:39.385	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:37:36.372	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:34:07.066	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:29:06.974	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:29:01.062	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:29:01.061	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:29:01.061	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:28:44.719	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:28:44.719	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:28:44.719	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:27:26.571	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:27:23.545	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:27:20.523	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:27:17.499	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:27:14.473	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:27:04.869	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:22:04.777	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:17:04.683	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:17:01.657	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:16:58.635	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:16:55.600	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:16:52.589	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      zigbee.0	2020-11-27 16:16:42.972	error	(1488) Device 0xccccccfffeeaa411 "07048L" not described in statesMapping.
                      

                      Gruß
                      Martin


                      Intel NUCs mit Proxmox / Iobroker als VM unter Debian
                      Raspeberry mit USB Leseköpfen für Smartmeter
                      Homematic und Homematic IP

                      1 Antwort Letzte Antwort
                      0
                      • H Offline
                        H Offline
                        Holgee
                        schrieb am zuletzt editiert von
                        #205

                        Servus,

                        @Asgothian: kein Problem, schicke ich Dir gerne zu, wenn Du mir Deine Adresse schreibst.

                        Ich hätte da gleich noch einen Kandidaten:

                        Heizkörperthermostat Saswell SEA802-Zigbee:
                        Saswell SEA802-Zigbee

                        Der wird zwar dem Anschein nach problemlos eingebunden,
                        d598d21f-1c19-4f01-87dd-09a379d1d35e-image.png
                        2e01f0fa-2aec-4598-95b8-dccbf1fdddbe-image.png

                        liefert aber leider keine verwertbaren Datenpunkte.
                        e9bf85fc-8a36-4abb-828f-404ea4ede5da-image.png.

                        Vielleicht lässt sich da ja auch gleich noch etwas optimieren ;-)

                        Grüße
                        Holger

                        1 Antwort Letzte Antwort
                        1
                        • M Offline
                          M Offline
                          MartyBr
                          schrieb am zuletzt editiert von
                          #206

                          @arteck
                          Ich habe Log-Dateien in dem Beitrag eingefügt.

                          https://forum.iobroker.net/topic/37453/zigbee-neue-unbekannte-geräte-ab-1-3-0/204

                          Gruß
                          Martin


                          Intel NUCs mit Proxmox / Iobroker als VM unter Debian
                          Raspeberry mit USB Leseköpfen für Smartmeter
                          Homematic und Homematic IP

                          I 1 Antwort Letzte Antwort
                          0
                          • M MartyBr

                            @arteck
                            Ich habe Log-Dateien in dem Beitrag eingefügt.

                            https://forum.iobroker.net/topic/37453/zigbee-neue-unbekannte-geräte-ab-1-3-0/204

                            I Offline
                            I Offline
                            io_laurent
                            schrieb am zuletzt editiert von io_laurent
                            #207

                            @MartyBr hast du die 1.3.1 von GIT installiert? Wenn nicht, dann versuch das mal, ich hab die Plugs nämlich auch und bei mir laufen die mit der GIT-Version.

                            M 1 Antwort Letzte Antwort
                            0
                            • I io_laurent

                              @MartyBr hast du die 1.3.1 von GIT installiert? Wenn nicht, dann versuch das mal, ich hab die Plugs nämlich auch und bei mir laufen die mit der GIT-Version.

                              M Offline
                              M Offline
                              MartyBr
                              schrieb am zuletzt editiert von
                              #208

                              @io_laurent
                              Danke für die Info. Ich habe jetzt auch die Git 1.3.9 installiert. Damit funktionieren die Plugs.

                              Gruß
                              Martin


                              Intel NUCs mit Proxmox / Iobroker als VM unter Debian
                              Raspeberry mit USB Leseköpfen für Smartmeter
                              Homematic und Homematic IP

                              1 Antwort Letzte Antwort
                              0
                              • J Offline
                                J Offline
                                Jan1
                                schrieb am zuletzt editiert von
                                #209

                                Habe mir ein Danalock zugelegt und eigentlich darauf gehofft, hier eine automatische Verriegelung über den IOBroker realisieren zu können. Leider wird das Schloss zwar erkannt, lässt aber keinerlei Steuerung zu. Hier mal die Infos aus dem Adapter:
                                eaaacfa6-62fb-44fa-882f-249bcf8a8ff3-grafik.png

                                Erstellte DPs:
                                f457a636-0a14-4fc2-8f9d-49a6fd876efc-grafik.png

                                Adapter Version ist 1.3.1.

                                AsgothianA 1 Antwort Letzte Antwort
                                0
                                • J Jan1

                                  Habe mir ein Danalock zugelegt und eigentlich darauf gehofft, hier eine automatische Verriegelung über den IOBroker realisieren zu können. Leider wird das Schloss zwar erkannt, lässt aber keinerlei Steuerung zu. Hier mal die Infos aus dem Adapter:
                                  eaaacfa6-62fb-44fa-882f-249bcf8a8ff3-grafik.png

                                  Erstellte DPs:
                                  f457a636-0a14-4fc2-8f9d-49a6fd876efc-grafik.png

                                  Adapter Version ist 1.3.1.

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

                                  @Jan1 Setz den Adapter mal ins debug und poste alle Meldungen aus dem Log die mit dem danalock zu tun haben. Ich gehe davon aus das du Verbindungsprobleme hast.

                                  A.

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

                                  J 1 Antwort Letzte Antwort
                                  0
                                  • arteckA arteck

                                    BITTE HIER NUR UNBEKANNTE GERÄTE REIN

                                    was wir brauchen ist

                                    am besten so eine Kachel nachdem man das Gerät angelernt hat (das geht immer)
                                    338ff8f8-c527-4107-8cd7-39d2322be960-grafik.png

                                    und ein Link zu dem Gerät

                                    wichtig ist es muss ein FRAGEZEICHEN Icon dazu geben UND eine genaue richtige Bezeichnung..
                                    nur so können wir mit der Informationen was anfangen

                                    wenn da ein UNDEFINED steht müsst ihr so lange das Device anlernen bis es einen Namen/Bezeichnung preisgibt

                                    eine Beschreibung was das Gerät kann währe auch hilfreich und ein Bild


                                    wichtig:
                                    Bitte unbedingt drauf achten die die genutzte Firmware auch aktuell ist..

                                    wie bekomme ich die Info :
                                    im Log nach adapter Start

                                    zigbee.0	2020-01-09 09:22:54.893	info	Starting Zigbee...
                                    

                                    steht

                                    zigbee.0	2020-01-09 09:22:58.553	info	Coordinator firmware version: {"type":"zStack12","meta":{"transportrev":2,"product":0,"majorrel":2,"minorrel":6,"maintrel":3,"revision":20180815}}
                                    

                                    die revision ist die Firmware als Datum

                                    revision":20180815
                                    

                                    hier im Beispiel vom 20180815 also sehr alt... Bitte nur mit neuer Firmware arbeiten (sollte von mitte 2019 sein)

                                    S Offline
                                    S Offline
                                    Spucki
                                    schrieb am zuletzt editiert von
                                    #211

                                    @arteck

                                    QS-Zigbee-D02-TRIAC-LN

                                    4fa80ac3-10a2-4d3a-a822-d49eb7fe45c0-image.png

                                    3ad3ede6-cb14-4a00-af10-7506cadce534-image.png

                                    Wie kann man den hinzufügen?

                                    VG

                                    Spucki

                                    S 1 Antwort Letzte Antwort
                                    0
                                    • AsgothianA Asgothian

                                      @Jan1 Setz den Adapter mal ins debug und poste alle Meldungen aus dem Log die mit dem danalock zu tun haben. Ich gehe davon aus das du Verbindungsprobleme hast.

                                      A.

                                      J Offline
                                      J Offline
                                      Jan1
                                      schrieb am zuletzt editiert von
                                      #212

                                      @Asgothian
                                      einmal zu und auf über die APP, was auch sofort in den Objekten angezeigt wurde:

                                      zigbee.0	2020-11-28 14:08:31.655	debug	(440024) system.adapter.admin.0: logging true
                                      zigbee.0	2020-11-28 14:08:21.888	debug	(440024) Publish {"state":"UNLOCK","lock_state":"unlocked"}
                                      zigbee.0	2020-11-28 14:08:21.887	debug	(440024) Publish {"action":"unlock","action_user":65535,"action_source":1,"action_source_name":"rf"}
                                      zigbee.0	2020-11-28 14:08:21.883	debug	(440024) Type attributeReport device {"type":"device","device":{"ID":21,"_type":"EndDevice","_ieeeAddr":"0x000b57fffe59d1f6","_networkAddress":55668,"_manufacturerID":4444,"_endpoints":[{"ID":1,"prof
                                      zigbee.0	2020-11-28 14:08:21.882	debug	(440024) Received Zigbee message from '0x000b57fffe59d1f6', type 'attributeReport', cluster 'closuresDoorLock', data '{"lockState":2}' from endpoint 1 with groupID 0
                                      zigbee.0	2020-11-28 14:08:21.881	debug	(440024) handleMessage. {"type":"attributeReport","device":{"ID":21,"_type":"EndDevice","_ieeeAddr":"0x000b57fffe59d1f6","_networkAddress":55668,"_manufacturerID":4444,"_endpoints":[{"ID":1,"profileI
                                      zigbee.0	2020-11-28 14:08:21.874	debug	(440024) Type commandOperationEventNotification device {"type":"device","device":{"ID":21,"_type":"EndDevice","_ieeeAddr":"0x000b57fffe59d1f6","_networkAddress":55668,"_manufacturerID":4444,"_endpoin
                                      zigbee.0	2020-11-28 14:08:21.873	debug	(440024) Received Zigbee message from '0x000b57fffe59d1f6', type 'commandOperationEventNotification', cluster 'closuresDoorLock', data '{"opereventsrc":1,"opereventcode":2,"userid":65535,"pin":0,"zig
                                      zigbee.0	2020-11-28 14:08:21.866	debug	(440024) handleMessage. {"type":"commandOperationEventNotification","device":{"ID":21,"_type":"EndDevice","_ieeeAddr":"0x000b57fffe59d1f6","_networkAddress":55668,"_manufacturerID":4444,"_endpoints":
                                      zigbee.0	2020-11-28 14:08:08.058	debug	(440024) Publish {"state":"LOCK","lock_state":"locked"}
                                      zigbee.0	2020-11-28 14:08:08.057	debug	(440024) Publish {"action":"lock","action_user":65535,"action_source":1,"action_source_name":"rf"}
                                      zigbee.0	2020-11-28 14:08:08.051	debug	(440024) Type attributeReport device {"type":"device","device":{"ID":21,"_type":"EndDevice","_ieeeAddr":"0x000b57fffe59d1f6","_networkAddress":55668,"_manufacturerID":4444,"_endpoints":[{"ID":1,"prof
                                      zigbee.0	2020-11-28 14:08:08.050	debug	(440024) Received Zigbee message from '0x000b57fffe59d1f6', type 'attributeReport', cluster 'closuresDoorLock', data '{"lockState":1}' from endpoint 1 with groupID 0
                                      zigbee.0	2020-11-28 14:08:08.048	debug	(440024) handleMessage. {"type":"attributeReport","device":{"ID":21,"_type":"EndDevice","_ieeeAddr":"0x000b57fffe59d1f6","_networkAddress":55668,"_manufacturerID":4444,"_endpoints":[{"ID":1,"profileI
                                      zigbee.0	2020-11-28 14:08:08.043	debug	(440024) Type commandOperationEventNotification device {"type":"device","device":{"ID":21,"_type":"EndDevice","_ieeeAddr":"0x000b57fffe59d1f6","_networkAddress":55668,"_manufacturerID":4444,"_endpoin
                                      zigbee.0	2020-11-28 14:08:08.042	debug	(440024) Received Zigbee message from '0x000b57fffe59d1f6', type 'commandOperationEventNotification', cluster 'closuresDoorLock', data '{"opereventsrc":1,"opereventcode":1,"userid":65535,"pin":0,"zig
                                      zigbee.0	2020-11-28 14:08:08.038	debug	(440024) handleMessage. {"type":"commandOperationEventNotification","device":{"ID":21,"_type":"EndDevice","_ieeeAddr":"0x000b57fffe59d1f6","_networkAddress":55668,"_manufacturerID":4444,"_endpoints":
                                      zigbee.0	2020-11-28 14:07:38.866	debug	(440024) Publish {"occupancy":false}
                                      zigbee.0	2020-11-28 14:07:28.863	debug	(440024) Publish {"occupancy":true}
                                      zigbee.0	2020-11-28 14:07:28.861	debug	(440024) Publish {"illuminance":60,"illuminance_lux":60}
                                      zigbee.0	2020-11-28 14:07:28.856	debug	(440024) Type attributeReport device {"type":"device","device":{"ID":9,"_type":"EndDevice","_ieeeAddr":"0x00158d00030a3270","_networkAddress":27111,"_manufacturerID":4151,"_endpoints":[{"ID":1,"profi
                                      zigbee.0	2020-11-28 14:07:28.855	debug	(440024) Received Zigbee message from '0x00158d00030a3270', type 'attributeReport', cluster 'msOccupancySensing', data '{"occupancy":1}' from endpoint 1 with groupID 0
                                      zigbee.0	2020-11-28 14:07:28.854	debug	(440024) handleMessage. {"type":"attributeReport","device":{"ID":9,"_type":"EndDevice","_ieeeAddr":"0x00158d00030a3270","_networkAddress":27111,"_manufacturerID":4151,"_endpoints":[{"ID
                                      

                                      Bei Verbindungsproblemen dürfte so schnell nicht der Status gewechselt werden zumal das Schloss vom CC1352P_2 gerade mal 3m ohne Hindernisse im Weg entfernt ist.

                                      AsgothianA 1 Antwort Letzte Antwort
                                      0
                                      • J Jan1

                                        @Asgothian
                                        einmal zu und auf über die APP, was auch sofort in den Objekten angezeigt wurde:

                                        zigbee.0	2020-11-28 14:08:31.655	debug	(440024) system.adapter.admin.0: logging true
                                        zigbee.0	2020-11-28 14:08:21.888	debug	(440024) Publish {"state":"UNLOCK","lock_state":"unlocked"}
                                        zigbee.0	2020-11-28 14:08:21.887	debug	(440024) Publish {"action":"unlock","action_user":65535,"action_source":1,"action_source_name":"rf"}
                                        zigbee.0	2020-11-28 14:08:21.883	debug	(440024) Type attributeReport device {"type":"device","device":{"ID":21,"_type":"EndDevice","_ieeeAddr":"0x000b57fffe59d1f6","_networkAddress":55668,"_manufacturerID":4444,"_endpoints":[{"ID":1,"prof
                                        zigbee.0	2020-11-28 14:08:21.882	debug	(440024) Received Zigbee message from '0x000b57fffe59d1f6', type 'attributeReport', cluster 'closuresDoorLock', data '{"lockState":2}' from endpoint 1 with groupID 0
                                        zigbee.0	2020-11-28 14:08:21.881	debug	(440024) handleMessage. {"type":"attributeReport","device":{"ID":21,"_type":"EndDevice","_ieeeAddr":"0x000b57fffe59d1f6","_networkAddress":55668,"_manufacturerID":4444,"_endpoints":[{"ID":1,"profileI
                                        zigbee.0	2020-11-28 14:08:21.874	debug	(440024) Type commandOperationEventNotification device {"type":"device","device":{"ID":21,"_type":"EndDevice","_ieeeAddr":"0x000b57fffe59d1f6","_networkAddress":55668,"_manufacturerID":4444,"_endpoin
                                        zigbee.0	2020-11-28 14:08:21.873	debug	(440024) Received Zigbee message from '0x000b57fffe59d1f6', type 'commandOperationEventNotification', cluster 'closuresDoorLock', data '{"opereventsrc":1,"opereventcode":2,"userid":65535,"pin":0,"zig
                                        zigbee.0	2020-11-28 14:08:21.866	debug	(440024) handleMessage. {"type":"commandOperationEventNotification","device":{"ID":21,"_type":"EndDevice","_ieeeAddr":"0x000b57fffe59d1f6","_networkAddress":55668,"_manufacturerID":4444,"_endpoints":
                                        zigbee.0	2020-11-28 14:08:08.058	debug	(440024) Publish {"state":"LOCK","lock_state":"locked"}
                                        zigbee.0	2020-11-28 14:08:08.057	debug	(440024) Publish {"action":"lock","action_user":65535,"action_source":1,"action_source_name":"rf"}
                                        zigbee.0	2020-11-28 14:08:08.051	debug	(440024) Type attributeReport device {"type":"device","device":{"ID":21,"_type":"EndDevice","_ieeeAddr":"0x000b57fffe59d1f6","_networkAddress":55668,"_manufacturerID":4444,"_endpoints":[{"ID":1,"prof
                                        zigbee.0	2020-11-28 14:08:08.050	debug	(440024) Received Zigbee message from '0x000b57fffe59d1f6', type 'attributeReport', cluster 'closuresDoorLock', data '{"lockState":1}' from endpoint 1 with groupID 0
                                        zigbee.0	2020-11-28 14:08:08.048	debug	(440024) handleMessage. {"type":"attributeReport","device":{"ID":21,"_type":"EndDevice","_ieeeAddr":"0x000b57fffe59d1f6","_networkAddress":55668,"_manufacturerID":4444,"_endpoints":[{"ID":1,"profileI
                                        zigbee.0	2020-11-28 14:08:08.043	debug	(440024) Type commandOperationEventNotification device {"type":"device","device":{"ID":21,"_type":"EndDevice","_ieeeAddr":"0x000b57fffe59d1f6","_networkAddress":55668,"_manufacturerID":4444,"_endpoin
                                        zigbee.0	2020-11-28 14:08:08.042	debug	(440024) Received Zigbee message from '0x000b57fffe59d1f6', type 'commandOperationEventNotification', cluster 'closuresDoorLock', data '{"opereventsrc":1,"opereventcode":1,"userid":65535,"pin":0,"zig
                                        zigbee.0	2020-11-28 14:08:08.038	debug	(440024) handleMessage. {"type":"commandOperationEventNotification","device":{"ID":21,"_type":"EndDevice","_ieeeAddr":"0x000b57fffe59d1f6","_networkAddress":55668,"_manufacturerID":4444,"_endpoints":
                                        zigbee.0	2020-11-28 14:07:38.866	debug	(440024) Publish {"occupancy":false}
                                        zigbee.0	2020-11-28 14:07:28.863	debug	(440024) Publish {"occupancy":true}
                                        zigbee.0	2020-11-28 14:07:28.861	debug	(440024) Publish {"illuminance":60,"illuminance_lux":60}
                                        zigbee.0	2020-11-28 14:07:28.856	debug	(440024) Type attributeReport device {"type":"device","device":{"ID":9,"_type":"EndDevice","_ieeeAddr":"0x00158d00030a3270","_networkAddress":27111,"_manufacturerID":4151,"_endpoints":[{"ID":1,"profi
                                        zigbee.0	2020-11-28 14:07:28.855	debug	(440024) Received Zigbee message from '0x00158d00030a3270', type 'attributeReport', cluster 'msOccupancySensing', data '{"occupancy":1}' from endpoint 1 with groupID 0
                                        zigbee.0	2020-11-28 14:07:28.854	debug	(440024) handleMessage. {"type":"attributeReport","device":{"ID":9,"_type":"EndDevice","_ieeeAddr":"0x00158d00030a3270","_networkAddress":27111,"_manufacturerID":4151,"_endpoints":[{"ID
                                        

                                        Bei Verbindungsproblemen dürfte so schnell nicht der Status gewechselt werden zumal das Schloss vom CC1352P_2 gerade mal 3m ohne Hindernisse im Weg entfernt ist.

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

                                        @Jan1 bitte poste mal die kompletten Zeilen, nicht nur den Teil den der Admin anzeigt.

                                        A.

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

                                        J 1 Antwort Letzte Antwort
                                        0
                                        • S Spucki

                                          @arteck

                                          QS-Zigbee-D02-TRIAC-LN

                                          4fa80ac3-10a2-4d3a-a822-d49eb7fe45c0-image.png

                                          3ad3ede6-cb14-4a00-af10-7506cadce534-image.png

                                          Wie kann man den hinzufügen?

                                          VG

                                          Spucki

                                          S Offline
                                          S Offline
                                          Spucki
                                          schrieb am zuletzt editiert von
                                          #214

                                          Habe soebend die 1.3.9dev instralliert, da ist er drin :---)))))

                                          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

                                          575

                                          Online

                                          32.5k

                                          Benutzer

                                          81.8k

                                          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