Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. ZigBee neue Version 1.8.x

    NEWS

    • ioBroker goes Matter ... Matter Adapter in Stable

    • 15. 05. Wartungsarbeiten am ioBroker Forum

    • Monatsrückblick - April 2025

    ZigBee neue Version 1.8.x

    This topic has been deleted. Only users with topic management privileges can see it.
    • arteck
      arteck Developer Most Active @TT-Tom last edited by

      @tt-tom sagte in ZigBee neue Version 1.8.x:

      2023-07-04 06:20:01.866 - error: zigbee.0 (52314) No converter available for 'E1743' with key 'state'

      installier von GIT und schau nochmal

      T 2 Replies Last reply Reply Quote 0
      • B
        bommel_030 @arteck last edited by

        @arteck
        Danke für den Versuch, daran lag es scheinbar nicht.

        2023-07-04 10:19:26.273  - error: zigbee.0 (31817) Device 0xa4c138db19fc6f09 "A1Z" not described in statesMapping.
2023-07-04 10:19:26.286  - warn: zigbee.0 (31817) setObject info.debugmessages (type=state) property common.role missing!
2023-07-04 10:19:26.513  - error: zigbee.0 (31817) Device 0xa4c138b625d22abb "A1Z" not described in statesMapping.
2023-07-04 10:19:26.515  - error: zigbee.0 (31817) Device 0xa4c13893b02d38f0 "A1Z" not described in statesMapping.
2023-07-04 10:19:26.520  - error: zigbee.0 (31817) Device 0xa4c138415565ab2d "A1Z" not described in statesMapping.
2023-07-04 10:19:26.522  - error: zigbee.0 (31817) Device 0xa4c138e4b34d3f41 "A1Z" not described in statesMapping.
2023-07-04 10:19:27.197  - error: zigbee.0 (31817) Device 0xa4c138499560c8ed "A1Z" not described in statesMapping.
2023-07-04 10:19:27.199  - error: zigbee.0 (31817) Device 0xa4c138d8dee0f468 "A1Z" not described in statesMapping.
2023-07-04 10:19:27.197  - error: zigbee.0 (31817) Device 0xa4c138499560c8ed "A1Z" not described in statesMapping.
2023-07-04 10:19:27.199  - error: zigbee.0 (31817) Device 0xa4c138d8dee0f468 "A1Z" not described in statesMapping.
2023-07-04 10:19:29.133  - warn: zigbee.0 (31817) Object cc86ecfffefa74ac.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-07-04 10:19:29.133  - warn: zigbee.0 (31817) This object will not be created in future versions. Please report this to the developer.
2023-07-04 10:19:29.135  - warn: zigbee.0 (31817) Object b4e3f9fffeb6143a.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-07-04 10:19:29.135  - warn: zigbee.0 (31817) This object will not be created in future versions. Please report this to the developer.
2023-07-04 10:19:29.135  - warn: zigbee.0 (31817) Object cc86ecfffef66b5b.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-07-04 10:19:29.136  - warn: zigbee.0 (31817) This object will not be created in future versions. Please report this to the developer.
2023-07-04 10:19:29.142  - warn: zigbee.0 (31817) Object b4e3f9fffebc1fd5.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-07-04 10:19:29.142  - warn: zigbee.0 (31817) This object will not be created in future versions. Please report this to the developer.
2023-07-04 10:19:29.142  - warn: zigbee.0 (31817) Object 0c4314fffe51aafe.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-07-04 10:19:29.142  - warn: zigbee.0 (31817) This object will not be created in future versions. Please report this to the developer.
2023-07-04 10:19:29.143  - warn: zigbee.0 (31817) Object b4e3f9fffe74f3b3.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-07-04 10:19:29.143  - warn: zigbee.0 (31817) This object will not be created in future versions. Please report this to the developer.
2023-07-04 10:19:29.220  - warn: zigbee.0 (31817) State "zigbee.0.a4c138db19fc6f09.available" has no existing object, this might lead to an error in future versions
2023-07-04 10:19:29.220  - warn: zigbee.0 (31817) State "zigbee.0.a4c138db19fc6f09.available" has no existing object, this might lead to an error in future versions
2023-07-04 10:19:29.220  - warn: zigbee.0 (31817) State "zigbee.0.a4c138db19fc6f09.link_quality" has no existing object, this might lead to an error in future versions
2023-07-04 10:19:29.220  - warn: zigbee.0 (31817) State "zigbee.0.a4c138db19fc6f09.link_quality" has no existing object, this might lead to an error in future versions
2023-07-04 10:19:29.133  - warn: zigbee.0 (31817) Object cc86ecfffefa74ac.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-07-04 10:19:29.133  - warn: zigbee.0 (31817) This object will not be created in future versions. Please report this to the developer.
2023-07-04 10:19:29.135  - warn: zigbee.0 (31817) Object b4e3f9fffeb6143a.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-07-04 10:19:29.135  - warn: zigbee.0 (31817) This object will not be created in future versions. Please report this to the developer.
2023-07-04 10:19:29.135  - warn: zigbee.0 (31817) Object cc86ecfffef66b5b.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-07-04 10:19:29.136  - warn: zigbee.0 (31817) This object will not be created in future versions. Please report this to the developer.
2023-07-04 10:19:29.142  - warn: zigbee.0 (31817) Object b4e3f9fffebc1fd5.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-07-04 10:19:29.142  - warn: zigbee.0 (31817) This object will not be created in future versions. Please report this to the developer.
2023-07-04 10:19:29.142  - warn: zigbee.0 (31817) Object 0c4314fffe51aafe.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-07-04 10:19:29.142  - warn: zigbee.0 (31817) This object will not be created in future versions. Please report this to the developer.
2023-07-04 10:19:29.143  - warn: zigbee.0 (31817) Object b4e3f9fffe74f3b3.power_on_behavior is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-07-04 10:19:29.143  - warn: zigbee.0 (31817) This object will not be created in future versions. Please report this to the developer.
2023-07-04 10:19:29.220  - warn: zigbee.0 (31817) State "zigbee.0.a4c138db19fc6f09.available" has no existing object, this might lead to an error in future versions
2023-07-04 10:19:29.220  - warn: zigbee.0 (31817) State "zigbee.0.a4c138db19fc6f09.available" has no existing object, this might lead to an error in future versions
2023-07-04 10:19:29.220  - warn: zigbee.0 (31817) State "zigbee.0.a4c138db19fc6f09.link_quality" has no existing object, this might lead to an error in future versions


        Jeder Versuch zu schalten wir hiermit quittiert:

        2023-07-04 10:27:13.371  - error: zigbee.0 (31944) No state available for 'A1Z' with key 'state'

        Komischerweise wird bei allen die Verbindungsstärke aktualisiert. Bei einem sind dafür alle Punkte auf der Kachel verschwunden.
        f2ba5180-5cbd-4794-bc33-dcb0bae4bb88-image.png

        arteck 1 Reply Last reply Reply Quote 0
        • arteck
          arteck Developer Most Active @bommel_030 last edited by arteck

          @bommel_030 dreh die kachel mal und poste die Infos
          oder noch besser

          poste mir die shepherd.db

          B 1 Reply Last reply Reply Quote 0
          • B
            bommel_030 @arteck last edited by bommel_030

            @arteck
            c0ea5072-6eaf-4e31-a050-b724eb514f26-image.png

            Mit der 1.8.10 Herdsmann 15.0.15 werden sie als diese Steckdosen erkannt.
            https://www.zigbee2mqtt.io/devices/TS011F_plug_1.html
            Mit der 1.8.12 Herdsmann 15.33.0 bzw. 15.34.0 als
            https://www.zigbee2mqtt.io/devices/A1Z.html

            Vom Bild her ist das letztere eigentlich richtiger.
            shepherd.db

            arteck 1 Reply Last reply Reply Quote 0
            • arteck
              arteck Developer Most Active @bommel_030 last edited by arteck

              @bommel_030 das info brauch ich auch
              8a9e9f61-bc38-4554-97bb-262b4221efd8-grafik.png

              B 1 Reply Last reply Reply Quote 0
              • B
                bommel_030 @arteck last edited by

                @arteck
                Sorry, vorhin vergessen anzuhängen.
                Zigbee 1.8.10
                10.png
                Zigbee 1.8.12
                12.png

                1 Reply Last reply Reply Quote 0
                • T
                  TT-Tom @arteck last edited by TT-Tom

                  @arteck

                  bin seit Sonntag schon auf 1.8.12

                  so oder benutzdefiniert

                  Bildschirmfoto 2023-07-04 um 12.03.28.png

                  B 1 Reply Last reply Reply Quote 0
                  • B
                    bommel_030 @TT-Tom last edited by bommel_030

                    @tt-tom
                    Ja, über die Katze. Versionsnummer wird sich nicht ändern, aber der Inhalt.
                    In
                    /opt/iobroker/node_modules/zigbee-herdsman-converters/package.json
                    sollte dann 15.34.0 als Version stehen.

                    T 1 Reply Last reply Reply Quote 0
                    • T
                      TT-Tom @bommel_030 last edited by

                      @bommel_030

                      okay, ist durch gelaufen, Version ist 15.34.0, kleiner Dreher bei dir bestimmt.

                      @arteck

                      werde das log beobachten, danke erst mal.

                      B 1 Reply Last reply Reply Quote 0
                      • B
                        bommel_030 @TT-Tom last edited by

                        @tt-tom
                        War nur nen Test ob du aufpasst 😉 Habs oben korrigiert.

                        1 Reply Last reply Reply Quote 1
                        • M
                          MP_Trixi @arteck last edited by MP_Trixi

                          @arteck sagte in ZigBee neue Version 1.8.x:

                          für den rest brauche ich die shepherd.db von dir

                          Hier das File
                          shepherd.db

                          Und noch die Device Info falls hilfreich:
                          a10bfe63-3788-47d6-838b-b46daf073490-image.png
                          4d6f6137-8549-40b3-a799-ee77015c3133-image.png

                          arteck 1 Reply Last reply Reply Quote 0
                          • T
                            TT-Tom @arteck last edited by

                            @arteck

                            Guten Morgen,

                            an der Namensauflösung hat sich nichts geändert. Die Meldung hat immer noch das selbe Format.

                            No converter available for 'E1743' with key 'state'
                            arteck 1 Reply Last reply Reply Quote 0
                            • arteck
                              arteck Developer Most Active last edited by

                              für NOUS

                              https://forum.iobroker.net/topic/66714/zigbee-steckdose-nous-a1z-testen

                              1 Reply Last reply Reply Quote 0
                              • arteck
                                arteck Developer Most Active @TT-Tom last edited by

                                @tt-tom was machst du dass die Meldung kommt ?? du versuchts wohl nicht den state manuell zu ändern oder ?

                                T 1 Reply Last reply Reply Quote 0
                                • T
                                  TT-Tom last edited by

                                  @arteck
                                  oh, da muss ich mal genauer hinschauen. Taster und Led-Leiste sind über ein Blockly verbunden, damit ich es in HomeKit einbinden kann. Ich sehe mir das morgen nochmal in Ruhe, da habe ich mehr Zeit.

                                  1 Reply Last reply Reply Quote 0
                                  • T
                                    TT-Tom @arteck last edited by

                                    @arteck

                                    Problem erkannt: ich schreibe wirklich in den State vom Taster. muss mal prüfen, ob ich eine andere Lösung finde.

                                    1 Reply Last reply Reply Quote 0
                                    • arteck
                                      arteck Developer Most Active @MP_Trixi last edited by

                                      @mp_trixi installier mal GIT und schau nochmal

                                      M 1 Reply Last reply Reply Quote 0
                                      • M
                                        MP_Trixi @arteck last edited by

                                        @arteck
                                        hab wie im neuen Nous Post per Github installiert und dann die tuya.js ausgetauscht.

                                        Ein Pairing einer bereits verbunden Tuya erzeugt nun im Log nur:

                                        zigbee.0 2023-07-07 10:24:06.578	info	Zigbee: stop joining
zigbee.0 2023-07-07 10:23:45.337	warn	Device '0xa4c1380afb5051e2' announced itself
zigbee.0 2023-07-07 10:23:05.346	info	Zigbee: allowing new devices to join.
                                        arteck 1 Reply Last reply Reply Quote 0
                                        • arteck
                                          arteck Developer Most Active @MP_Trixi last edited by

                                          @mp_trixi du brauchst nix tauschen... die version auf GIT ist schon so dass der A1Z läuft

                                          M 1 Reply Last reply Reply Quote 0
                                          • M
                                            MP_Trixi @arteck last edited by

                                            @arteck
                                            ok, da ich mir nicht sicher war, hatte ich die Datei nur umbenannt und nicht gelöscht/überschrieben. Hab die Instanz gestoppt, das File das per Katze kam wieder als tuya.js rein und neu gestartet. Jetzt sind auch die richtigen Bilder 🙂

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            894
                                            Online

                                            31.6k
                                            Users

                                            79.5k
                                            Topics

                                            1.3m
                                            Posts

                                            55
                                            385
                                            54660
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo