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.5.x

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    ZigBee neue Version 1.5.x

    This topic has been deleted. Only users with topic management privileges can see it.
    • Tom Son
      Tom Son @Asgothian last edited by

      @asgothian Ich dachte du kennst das schon da ja schon mal geschrieben wurde...

      Wenn ich das Pairen starte (habe mal bewusst nur 30sek eingestellt) dann kommt das parallell ins Log:

      zigbee.0	2021-05-02 17:54:16.499	warn	Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left"
zigbee.0	2021-05-02 17:54:16.498	warn	Read-only state "zigbee.0.info.pairingMode" has been written without ack-flag with value "false"
zigbee.0	2021-05-02 17:54:16.497	warn	Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "0"
zigbee.0	2021-05-02 17:54:16.488	info	Zigbee: stop joining
zigbee.0	2021-05-02 17:54:15.495	warn	Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 1"
zigbee.0	2021-05-02 17:54:15.491	warn	Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "1"
zigbee.0	2021-05-02 17:54:14.492	warn	Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 2"
zigbee.0	2021-05-02 17:54:14.489	warn	Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "2"
zigbee.0	2021-05-02 17:54:13.487	warn	Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 3"
zigbee.0	2021-05-02 17:54:13.486	warn	Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "3"
zigbee.0	2021-05-02 17:54:12.491	warn	Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 4"
zigbee.0	2021-05-02 17:54:12.487	warn	Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "4"
zigbee.0	2021-05-02 17:54:11.488	warn	Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 5"
zigbee.0	2021-05-02 17:54:11.485	warn	Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "5"
zigbee.0	2021-05-02 17:54:10.489	warn	Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 6"
zigbee.0	2021-05-02 17:54:10.485	warn	Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "6"
zigbee.0	2021-05-02 17:54:09.488	warn	Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 7"
zigbee.0	2021-05-02 17:54:09.485	warn	Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "7"
zigbee.0	2021-05-02 17:54:08.487	warn	Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 8"
zigbee.0	2021-05-02 17:54:08.485	warn	Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "8"
zigbee.0	2021-05-02 17:54:07.488	warn	Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 9"
zigbee.0	2021-05-02 17:54:07.485	warn	Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "9"
zigbee.0	2021-05-02 17:54:06.484	warn	Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 10"
zigbee.0	2021-05-02 17:54:06.482	warn	Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "10"
zigbee.0	2021-05-02 17:54:05.484	warn	Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 11"
zigbee.0	2021-05-02 17:54:05.482	warn	Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "11"
zigbee.0	2021-05-02 17:54:04.484	warn	Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 12"
zigbee.0	2021-05-02 17:54:04.482	warn	Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "12"
zigbee.0	2021-05-02 17:54:03.485	warn	Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 13"
zigbee.0	2021-05-02 17:54:03.482	warn	Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "13"
zigbee.0	2021-05-02 17:54:02.480	warn	Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 14"
zigbee.0	2021-05-02 17:54:02.479	warn	Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "14"
zigbee.0	2021-05-02 17:54:01.483	warn	Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 15"
zigbee.0	2021-05-02 17:54:01.481	warn	Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "15"
zigbee.0	2021-05-02 17:54:00.480	warn	Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 16"
zigbee.0	2021-05-02 17:54:00.478	warn	Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "16"
zigbee.0	2021-05-02 17:53:59.481	warn	Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 17"
zigbee.0	2021-05-02 17:53:59.478	warn	Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "17"
zigbee.0	2021-05-02 17:53:58.485	warn	Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 18"
zigbee.0	2021-05-02 17:53:58.484	warn	Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "18"
zigbee.0	2021-05-02 17:53:57.478	warn	Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 19"
zigbee.0	2021-05-02 17:53:57.477	warn	Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "19"
zigbee.0	2021-05-02 17:53:56.477	warn	Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 20"
zigbee.0	2021-05-02 17:53:56.476	warn	Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "20"
zigbee.0	2021-05-02 17:53:55.479	warn	Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 21"
zigbee.0	2021-05-02 17:53:55.476	warn	Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "21"
zigbee.0	2021-05-02 17:53:54.480	warn	Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 22"
zigbee.0	2021-05-02 17:53:54.477	warn	Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "22"
zigbee.0	2021-05-02 17:53:53.477	warn	Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 23"
zigbee.0	2021-05-02 17:53:53.474	warn	Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "23"
zigbee.0	2021-05-02 17:53:52.477	warn	Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 24"
zigbee.0	2021-05-02 17:53:52.474	warn	Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "24"
zigbee.0	2021-05-02 17:53:51.477	warn	Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 25"
zigbee.0	2021-05-02 17:53:51.473	warn	Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "25"
zigbee.0	2021-05-02 17:53:50.473	warn	Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 26"
zigbee.0	2021-05-02 17:53:50.472	warn	Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "26"
zigbee.0	2021-05-02 17:53:49.473	warn	Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 27"
zigbee.0	2021-05-02 17:53:49.472	warn	Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "27"
zigbee.0	2021-05-02 17:53:48.475	warn	Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 28"
zigbee.0	2021-05-02 17:53:48.472	warn	Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "28"
zigbee.0	2021-05-02 17:53:47.470	warn	Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 29"
zigbee.0	2021-05-02 17:53:47.468	warn	Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "29"
zigbee.0	2021-05-02 17:53:46.472	warn	Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing time left: 30"
zigbee.0	2021-05-02 17:53:46.470	warn	Read-only state "zigbee.0.info.pairingCountdown" has been written without ack-flag with value "30"
zigbee.0	2021-05-02 17:53:45.215	warn	Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Pairing started "

      Bei mir ist das dann noch so dass er die meisten Geräte 2x oder 3x findet, nach einem reload der Seite sind die aber wieder weg...
      Adapter Version 1.5.3

      nodejs -v && npm -v && iobroker -v :
      v12.22.1
      6.14.12
      3.3.5

      BananaJoe amg_666 Asgothian 3 Replies Last reply Reply Quote 0
      • BananaJoe
        BananaJoe Most Active @Tom Son last edited by BananaJoe

        @tom-son sagte in ZigBee neue Version 1.5.x:

        3.3.5

        Das liegt am js-controller 3.3.x, mit dem 3.2.16 kommt das nicht. Die Meldungen kommen nach dem Upgrade vom js-controller. Das habe ich hier in den letzten Tagen schon bei diversen anderen Adaptern gelesen.
        Die Adapter müssen wohl angepasst werden heißt es,

        1 Reply Last reply Reply Quote 0
        • amg_666
          amg_666 @Tom Son last edited by

          @tom-son hab ich seit 3.3.5 auch bei diversen Adaptern.

          1. Mach ein issue für den betroffenen Adapter auf (oder check ob es schon eins gibt)
          2. Als workaround habe ich bei mir den Loglevel bei betroffenen Adaptern auf "error" gestellt
          1 Reply Last reply Reply Quote 0
          • Asgothian
            Asgothian Developer @Tom Son last edited by

            @tom-son die sind meines Wissens bereits Gefixed

            A.

            1 Reply Last reply Reply Quote 0
            • S
              Steffengr last edited by

              Hallo in die Runde,
              ich möchte gern von meinem Pi mit RaspBee II Steckkarte auf ein Tinkerboard mit LaunchXL-CC1352P-2 und entsprechenden ZigBee Adapter wechseln.
              Das Tinkerbord ist als ioBroker Multihost an meinen Master angebunden. Das LaunchXL ist eingebunden und hat auch eine Verbindung zum ioBroker.

              Ich habe mal die neuste Version des ZigBee Adapter installiert und zwei Geräte angelernt.

              Es werden die Daten entsprechend dargestellt. Wenn ich allerdings auf die Kachel klicke dreht diese sich und man kann kurz (ca. halbe Sekunde) den Inhalt sehen und dann ist die Kachel weiß.

              Gibt es dazu Informationen?

              Nodejs: 12.22.1
              npm: 6.14.12
              ZigBee: 1.5.4

              Danke und Gruß
              Steffen

              2.jpg 1.jpg

              S 1 Reply Last reply Reply Quote 0
              • S
                Steffengr @Steffengr last edited by Steffengr

                @steffengr sagte in ZigBee neue Version 1.5.x:

                Hallo in die Runde,
                ich möchte gern von meinem Pi mit RaspBee II Steckkarte auf ein Tinkerboard mit LaunchXL-CC1352P-2 und entsprechenden ZigBee Adapter wechseln.
                Das Tinkerbord ist als ioBroker Multihost an meinen Master angebunden. Das LaunchXL ist eingebunden und hat auch eine Verbindung zum ioBroker.

                Ich habe mal die neuste Version des ZigBee Adapter installiert und zwei Geräte angelernt.

                Es werden die Daten entsprechend dargestellt. Wenn ich allerdings auf die Kachel klicke dreht diese sich und man kann kurz (ca. halbe Sekunde) den Inhalt sehen und dann ist die Kachel weiß.

                Gibt es dazu Informationen?

                Nodejs: 12.22.1
                npm: 6.14.12
                ZigBee: 1.5.4

                Danke und Gruß
                Steffen

                2.jpg 1.jpg

                Es liegt an Safari.
                Wann werden die Zustände für die Batterien aktualisiert?

                Danke und Gruß
                Steffen

                Asgothian 1 Reply Last reply Reply Quote 0
                • Asgothian
                  Asgothian Developer @Steffengr last edited by

                  @steffengr sagte in ZigBee neue Version 1.5.x:

                  Wann werden die Zustände für die Batterien aktualisiert?

                  Wenn das Gerät eine Nachricht mit dem Batteriestand schickt.

                  A.

                  1 Reply Last reply Reply Quote 0
                  • B
                    BigMike71 last edited by BigMike71

                    kann man den nichts machen bei meinem Problem mit dem Rauchmelder Frient (Develco) SMSZB-120?
                    sieht Post vom 21.04.2021 Post

                    Neuschwansteini 1 Reply Last reply Reply Quote 0
                    • Neuschwansteini
                      Neuschwansteini @BigMike71 last edited by

                      @bigmike71
                      Hier auch...

                      1 Reply Last reply Reply Quote 0
                      • D
                        disaster123 last edited by

                        @Asgothian seit 1.5.X bekomme ich sehr oft folgenden Fehler:

                        zigbee.0	2021-05-06 16:20:06.076	error	(448) Error: Error while opening serialport 'Error: Error: Input/output error setting custom baud rate of 38400' at Driver.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/deco
zigbee.0	2021-05-06 16:20:06.076	error	(448) Failed to start Zigbee

                        dann folgt:

                        zigbee.0	2021-05-06 16:20:30.683	error	(448) Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'
zigbee.0	2021-05-06 16:20:30.683	error	(448) Error: Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port' at Driver.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/deconz/d
zigbee.0	2021-05-06 16:20:30.683	error	(448) unhandled promise rejection: Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'
zigbee.0	2021-05-06 16:20:30.682	error	(448) 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().

                        und danach startet er in der Regel mit 1.4.4 habe ich das nie gesehen.

                        Asgothian 1 Reply Last reply Reply Quote 0
                        • Asgothian
                          Asgothian Developer @disaster123 last edited by

                          @disaster123
                          Was für Hardware hast du ?

                          D 2 Replies Last reply Reply Quote 0
                          • D
                            disaster123 @Asgothian last edited by

                            @asgothian conbee 2 usb Stick via qemu / kvm in eine vm und von da in einen docker container mit iobroker

                            1 Reply Last reply Reply Quote 0
                            • D
                              disaster123 @Asgothian last edited by

                              @asgothian seit heute morgen sieht es alle 2 Stunden so aus:

                              zigbee.0	2021-05-07 09:13:07.484	error	(6485) Error while opening serialport 'Error: Error: No such device or address, cannot open /dev/ttyACM1'
zigbee.0	2021-05-07 09:13:07.484	error	at /opt/iobroker/node_modules/@serialport/stream/lib/index.js:242:12
zigbee.0	2021-05-07 09:13:07.484	error	at SerialPort._error (/opt/iobroker/node_modules/@serialport/stream/lib/index.js:198:14)
zigbee.0	2021-05-07 09:13:07.484	error	at SerialPort.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/deconz/driver/driver.js:158:45)
zigbee.0	2021-05-07 09:13:07.484	error	at __awaiter (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/deconz/driver/driver.js:4:12)
zigbee.0	2021-05-07 09:13:07.484	error	at new Promise (<anonymous>)
zigbee.0	2021-05-07 09:13:07.484	error	at /opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/deconz/driver/driver.js:8:71
zigbee.0	2021-05-07 09:13:07.484	error	at Generator.next (<anonymous>)
zigbee.0	2021-05-07 09:13:07.484	error	at Driver.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/deconz/driver/driver.js:160:28)
zigbee.0	2021-05-07 09:13:07.484	error	(6485) Error: Error while opening serialport 'Error: Error: No such device or address, cannot open /dev/ttyACM1'
zigbee.0	2021-05-07 09:13:07.484	error	(6485) unhandled promise rejection: Error while opening serialport 'Error: Error: No such device or address, cannot open /dev/ttyACM1'
zigbee.0	2021-05-07 09:13:07.482	error	(6485) 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().
                              Asgothian arteck 2 Replies Last reply Reply Quote -1
                              • Tom Son
                                Tom Son last edited by

                                Langsam frustiert mich das ganze, jetzt mache ich das doofe js update schon zum dritten mal und immer sind alle Geräte in der Zigbee Instanz weg 😞 Muss dann alle wieder koppeln.... Gibt es da keine bessere Lösung?

                                Ich glaube ich gehe zurück auf stable 😞 😞

                                crunchip amg_666 L 3 Replies Last reply Reply Quote 0
                                • crunchip
                                  crunchip Forum Testing Most Active @Tom Son last edited by crunchip

                                  @tom-son sagte in ZigBee neue Version 1.5.x:

                                  js update

                                  welches?

                                  @tom-son sagte in ZigBee neue Version 1.5.x:

                                  Gibt es da keine bessere Lösung

                                  nach dem Fehler suchen (log) , oder die shepherd.dp aus dem backup einspielen, dann müssten die Sensoren wieder da sein, ohne neu anzulernen

                                  Tom Son 1 Reply Last reply Reply Quote 0
                                  • amg_666
                                    amg_666 @Tom Son last edited by

                                    @tom-son Hm, also bei mir läuft das alles stabil,
                                    Node.js: v14.16.1, NPM: 6.14.12 und iobroker 3.3.8
                                    admin 5.0.15 und zigbee 1.5.5
                                    Das ganze läuft als VM unter Debian auf einem intel nuc mit proxmox
                                    Einzig nerviger Punkt ist, dass der zigbee unter "Netzwerkkarte" alle Geräte als nicht verbunden und rot darstellt, das dauert dann zwischen 5 und vielleicht 20 Sekunden und dann stimmt die Karte auch.
                                    KEINE "Verluste" von Geräten, KEINE Funktionseinschränkungen

                                    Horst Böttcher 1 Reply Last reply Reply Quote 0
                                    • Horst Böttcher
                                      Horst Böttcher @amg_666 last edited by

                                      Hallo der Adapter bleibt bei mir gelb
                                      und nix geht mehr

                                      Aus den log

                                      
zigbee.0	2021-05-07 21:55:23.893	error	(6335) getGroups: caught error: TypeError: Cannot read property 'getGroups' of undefined
                                      Asgothian 1 Reply Last reply Reply Quote 0
                                      • L
                                        luie @Tom Son last edited by luie

                                        @tom-son sagte in ZigBee neue Version 1.5.x:

                                        js update

                                        Wie gehst du vor?

                                        Bei mir lief das update auf js-controller 3.3.8 ohne Probleme. Ich musste nur nach dem reboot des raspi den zigbee-Adapter 1x stoppen und dann wieder starten.

                                        Horst Böttcher Tom Son 2 Replies Last reply Reply Quote 0
                                        • Horst Böttcher
                                          Horst Böttcher @luie last edited by Horst Böttcher

                                          @luie 22a1974365cb36b48070903929177156.png

                                          für leicht ist was falsch gelaufen

                                          JS update nach anleitung

                                          1 Reply Last reply Reply Quote 0
                                          • Asgothian
                                            Asgothian Developer @disaster123 last edited by

                                            @disaster123 da passt etwas mit der Weiterleitung der seriellen Schnittstelle nicht. Die Meldung

                                            No such device or address...

                                            Ist da recht eindeutig.

                                            A.

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            891
                                            Online

                                            31.8k
                                            Users

                                            79.9k
                                            Topics

                                            1.3m
                                            Posts

                                            72
                                            579
                                            111202
                                            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