Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. Test Adapter iobroker.Zigbee 1.10.10

    NEWS

    • ioBroker 10-Jahres Community Treffen - ein kleiner ReCap

    • Tester für Responsive Initiative gesucht

    • 50€: Mach mit bei einer Smarthome Studie mit ioBroker!

    Test Adapter iobroker.Zigbee 1.10.10

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

      @ritter sagte in Test Adapter iobroker.Zigbee 1.10.10:

      @asgothian
      Hallo, hab die Version mal installiert. Man kann dann keine Geräte mehr bedienen. Wenn man aber z.B. eine Funksteckdose von Hand bedient, dann sieht man auf der Adapter Kachel auch den Schalter wie er ein und aus geht, umgekehrt geht es nicht. Ich habe ca. 5 Minuten nach dem Start gewartet ob sich etwas bedienen lässt.

      Optisch kann man bei den Einstellungen nicht mehr die IP vom Gateway eintragen da es verdeckt ist vom blauen Balken der zu hoch ist, das bleibt auch beim downgrade so.

      Screenshot 2024-10-17 222955.png

      Gateway:
      type:zStack3x0
      version:2-1.2.7.1.
      revision:20240710

      Bitte folgendes testen:

      • von Hand ein Upload des Adapters durchführen (auf der Konsole: iobroker upload zigbee)
      • Leere den cache und versuch nochmal die Geräte zu steuern / einzustellen.

      Bei mir funktioniert es ohne Probleme

      Bitte folgende Information mit liefern:

      • JSController version
      • Admin version
      • betroffene Geräte die sich nicht steuern lassen
      • Browser mit dem es nicht geht.

      A.
      Nachtrag: Das downgrade ging mit oder ohne Nutzung der Sicherheitskopie ?

      R 1 Reply Last reply Reply Quote 0
      • R
        Ritter @Asgothian last edited by

        @asgothian cache leeren hatte ich schon probiert, upload vorher über den admin gemacht, jetzt noch mal über die Konsole.

        Admin: v7.2.6
        JSController version 7.0.0
        Browser Chrome: Version 129.0.6668.101
        Geräte: Osram Steckdose, Lidl Funksteckdose, IKEA Lampen E27, Müller TINT Lampen, EGLO Lampe, Hornbach E14 Kerzen

        Das downgrade auf 1.10.3 ging ohne Sicherung, auf 1.10.9 ging nicht da war dann immer noch 1.10.10 da.

        Die Darstellung ist nur falsch wenn man auf Instanzen und dann Zigbee geht, nicht aber links direkt auf Zigbee drückt hier ist es richtig, da gibt es aber keine Einstellungen.

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

          @ritter Ich kann das verhalten nicht nachvollziehen. Allerdings bekomme ich die Chrome version nicht installiert, ich habe mit der version 130.0.6723.59 getestet - ohne Auffälligkeiten auch bei einigen der von Dir genannten Gerätearten die ich im Netz habe. Bleiben noch ein paar Fragen:

          • Desktop oder Mobile version des Browsers (und kannst du mit der jeweils anderen testen)
          • Node JS Version ?

          A.

          Nachtrag: Warum ist die Admin Version 7.2.6 von NPM installiert (an Stelle der stable 7.1.5 ?

          Nachtrag 2: Ich konnte nachweisen das der Fehler durch code-Anpassungen am Admin auftritt - egal mit welcher zigbee Adapter version tritt dieser Fehler ab 7.2.6 auf, da der Admin den HTML Code des Adapters übersteuert. Code-anpassungen am Zigbee Adapter sind da nicht beteiligt.
          Kannst du testen ob der Fehler bei Dir auch durch Installation des Admin aus dem Stable Repository behoben ist ?

          A.

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

            Vielen Dank an @apollon77 und @simatec - der Fehler im Konfigurationsinterface sollte behoben sein. Zumindest kann ich den bei mir nicht mehr nachstellen.

            @ritter kannst du das bitte nochmal testen, i.e. nochmal die aktuelle 1.10.10 von GitHub installieren ? Dann sollte das Problem auch mit dem Admin 7.2.6 weg sein.

            A.

            R 1 Reply Last reply Reply Quote 1
            • R
              Ritter @Asgothian last edited by Ritter

              @asgothian Hallo, die Darstellung ist mit dem update jetzt richtig. Geräte kann ich aber immer noch nicht bedienen.
              Was auch ist, wenn man auf Koppeln drückt kommt nur Pairing started, aber es zählen die Prozente nicht herunter.
              Man sieht aber das die Geräte Empfang haben.
              Node Version v20.17.0

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

                @ritter sagte in Test Adapter iobroker.Zigbee 1.10.10:

                Geräte kann ich aber immer noch nicht bedienen.

                Dieses betrifft auch nur die Konfiguration, or ist dieses auch auf dem Tab der Fall ?

                Was ist mit Steuern aus den Objekten heraus ? Geht das ?

                R 1 Reply Last reply Reply Quote 0
                • R
                  Ritter @Asgothian last edited by

                  @asgothian Nein, weder von VIS oder von einem Blockly aus.

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

                    @ritter sagte in Test Adapter iobroker.Zigbee 1.10.10:

                    @asgothian Nein, weder von VIS oder von einem Blockly aus.

                    Gibt es Meldungen im Log wenn du versuchst etwas zu steuern ?

                    Bitte an einem Test-Objekt (am besten eine Leuchte mit mehreren ansteuerbaren Datenpunkten) welches sich nicht steuern lässt die folgenden Schritte durchführen:

                    • Objekt IEEE identifizieren
                    • die letzten 8 Stellen der IEEE in den State zigbee.0.info.debugmessages eintragen
                    • versuchen das Objekt zu schalten
                    • im Log nach Warn Meldungen nach diesem Vorbild suchen
                    • im Log nach Fehlermeldungen im Umfeld dieser Warnmeldungen suchen

                    A.

                    R ilovegym 2 Replies Last reply Reply Quote 0
                    • R
                      Ritter @Asgothian last edited by Ritter

                      @asgothian Hallo, bin leider erst jetzt dazugekommen.
                      Reicht dir das mit ELEVATED gefilterte oder brauchst du das ganze log?
                      Eine IKEA E27 Lampe mit weißtönen.

                      zigbee.0
2024-10-19 19:05:34.943	warn	ELEVATED Change state 'brightness' at device 0x943469fffe55fc9e type 'LED2003G10'

zigbee.0
2024-10-19 19:05:34.884	warn	ELEVATED: User stateChange zigbee.0.943469fffe55fc9e.brightness {"val":100,"ack":false,"ts":1729357534876,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1729357534876}

zigbee.0
2024-10-19 19:05:34.083	warn	ELEVATED Change state 'brightness' at device 0x943469fffe55fc9e type 'LED2003G10'

zigbee.0
2024-10-19 19:05:34.026	warn	ELEVATED: User stateChange zigbee.0.943469fffe55fc9e.brightness {"val":13,"ack":false,"ts":1729357534017,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1729357534017}

zigbee.0
2024-10-19 19:05:33.042	warn	ELEVATED Change state 'brightness' at device 0x943469fffe55fc9e type 'LED2003G10'

zigbee.0
2024-10-19 19:05:32.990	warn	ELEVATED: User stateChange zigbee.0.943469fffe55fc9e.brightness {"val":87,"ack":false,"ts":1729357532988,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1729357532988}

zigbee.0
2024-10-19 19:05:31.278	warn	ELEVATED Change state 'colortemp' at device 0x943469fffe55fc9e type 'LED2003G10'

zigbee.0
2024-10-19 19:05:31.231	warn	ELEVATED: User stateChange zigbee.0.943469fffe55fc9e.colortemp {"val":221,"ack":false,"ts":1729357531229,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1729357531229}

zigbee.0
2024-10-19 19:05:28.349	warn	ELEVATED Change state 'state' at device 0x943469fffe55fc9e type 'LED2003G10'

zigbee.0
2024-10-19 19:05:28.278	warn	ELEVATED: User stateChange zigbee.0.943469fffe55fc9e.state {"val":true,"ack":false,"ts":1729357528269,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1729357528269}

zigbee.0
2024-10-19 19:05:25.494	warn	ELEVATED Change state 'state' at device 0x943469fffe55fc9e type 'LED2003G10'

zigbee.0
2024-10-19 19:05:25.448	warn	ELEVATED: User stateChange zigbee.0.943469fffe55fc9e.state {"val":false,"ack":false,"ts":1729357525446,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1729357525446}

zigbee.0
2024-10-19 19:05:23.255	warn	ELEVATED Change state 'colortemp' at device 0x943469fffe55fc9e type 'LED2003G10'

zigbee.0
2024-10-19 19:05:23.198	warn	ELEVATED: User stateChange zigbee.0.943469fffe55fc9e.colortemp {"val":500,"ack":false,"ts":1729357523190,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1729357523190}

zigbee.0
2024-10-19 19:05:19.526	warn	ELEVATED Change state 'colortemp' at device 0x943469fffe55fc9e type 'LED2003G10'

zigbee.0
2024-10-19 19:05:19.480	warn	ELEVATED: User stateChange zigbee.0.943469fffe55fc9e.colortemp {"val":156,"ack":false,"ts":1729357519478,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1729357519478}

zigbee.0
2024-10-19 19:05:16.680	warn	ELEVATED Change state 'brightness' at device 0x943469fffe55fc9e type 'LED2003G10'

zigbee.0
2024-10-19 19:05:16.623	warn	ELEVATED: User stateChange zigbee.0.943469fffe55fc9e.brightness {"val":11,"ack":false,"ts":1729357516621,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1729357516621}

zigbee.0
2024-10-19 19:05:16.175	warn	ELEVATED Change state 'brightness' at device 0x943469fffe55fc9e type 'LED2003G10'

zigbee.0
2024-10-19 19:05:16.119	warn	ELEVATED: User stateChange zigbee.0.943469fffe55fc9e.brightness {"val":30,"ack":false,"ts":1729357516110,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1729357516110}

                      Zigbee 1.txt

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

                        @ritter sagte in Test Adapter iobroker.Zigbee 1.10.10:

                        @asgothian Hallo, bin leider erst jetzt dazugekommen.
                        Reicht dir das mit ELEVATED gefilterte oder brauchst du das ganze log?
                        Eine IKEA E27 Lampe mit weißtönen.

                        zigbee.0
2024-10-19 19:05:34.943	warn	ELEVATED Change state 'brightness' at device 0x943469fffe55fc9e type 'LED2003G10'

zigbee.0
2024-10-19 19:05:34.884	warn	ELEVATED: User stateChange zigbee.0.943469fffe55fc9e.brightness {"val":100,"ack":false,"ts":1729357534876,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1729357534876}

zigbee.0
2024-10-19 19:05:34.083	warn	ELEVATED Change state 'brightness' at device 0x943469fffe55fc9e type 'LED2003G10'

zigbee.0
2024-10-19 19:05:34.026	warn	ELEVATED: User stateChange zigbee.0.943469fffe55fc9e.brightness {"val":13,"ack":false,"ts":1729357534017,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1729357534017}

zigbee.0
2024-10-19 19:05:33.042	warn	ELEVATED Change state 'brightness' at device 0x943469fffe55fc9e type 'LED2003G10'

zigbee.0
2024-10-19 19:05:32.990	warn	ELEVATED: User stateChange zigbee.0.943469fffe55fc9e.brightness {"val":87,"ack":false,"ts":1729357532988,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1729357532988}

zigbee.0
2024-10-19 19:05:31.278	warn	ELEVATED Change state 'colortemp' at device 0x943469fffe55fc9e type 'LED2003G10'

zigbee.0
2024-10-19 19:05:31.231	warn	ELEVATED: User stateChange zigbee.0.943469fffe55fc9e.colortemp {"val":221,"ack":false,"ts":1729357531229,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1729357531229}

zigbee.0
2024-10-19 19:05:28.349	warn	ELEVATED Change state 'state' at device 0x943469fffe55fc9e type 'LED2003G10'

zigbee.0
2024-10-19 19:05:28.278	warn	ELEVATED: User stateChange zigbee.0.943469fffe55fc9e.state {"val":true,"ack":false,"ts":1729357528269,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1729357528269}

zigbee.0
2024-10-19 19:05:25.494	warn	ELEVATED Change state 'state' at device 0x943469fffe55fc9e type 'LED2003G10'

zigbee.0
2024-10-19 19:05:25.448	warn	ELEVATED: User stateChange zigbee.0.943469fffe55fc9e.state {"val":false,"ack":false,"ts":1729357525446,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1729357525446}

zigbee.0
2024-10-19 19:05:23.255	warn	ELEVATED Change state 'colortemp' at device 0x943469fffe55fc9e type 'LED2003G10'

zigbee.0
2024-10-19 19:05:23.198	warn	ELEVATED: User stateChange zigbee.0.943469fffe55fc9e.colortemp {"val":500,"ack":false,"ts":1729357523190,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1729357523190}

zigbee.0
2024-10-19 19:05:19.526	warn	ELEVATED Change state 'colortemp' at device 0x943469fffe55fc9e type 'LED2003G10'

zigbee.0
2024-10-19 19:05:19.480	warn	ELEVATED: User stateChange zigbee.0.943469fffe55fc9e.colortemp {"val":156,"ack":false,"ts":1729357519478,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1729357519478}

zigbee.0
2024-10-19 19:05:16.680	warn	ELEVATED Change state 'brightness' at device 0x943469fffe55fc9e type 'LED2003G10'

zigbee.0
2024-10-19 19:05:16.623	warn	ELEVATED: User stateChange zigbee.0.943469fffe55fc9e.brightness {"val":11,"ack":false,"ts":1729357516621,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1729357516621}

zigbee.0
2024-10-19 19:05:16.175	warn	ELEVATED Change state 'brightness' at device 0x943469fffe55fc9e type 'LED2003G10'

zigbee.0
2024-10-19 19:05:16.119	warn	ELEVATED: User stateChange zigbee.0.943469fffe55fc9e.brightness {"val":30,"ack":false,"ts":1729357516110,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1729357516110}

                        Zigbee 1.txt

                        bitte lass den nochmal laufen, aber ohne das der Adapter im Debug läuft - da sind viel zu viele Nachrichten um da die Fehlermeldungen zu finden - so sie denn existieren.

                        Die Elevated Meldungen sind auf jeden Fall auffällig - mir fehlt da was.

                        A.

                        R 1 Reply Last reply Reply Quote 0
                        • R
                          Ritter @Asgothian last edited by Ritter

                          @asgothian Reicht info aus?

                          zigbee.0
2024-10-19 21:24:10.569	warn	ELEVATED Change state 'state' at device 0x943469fffe55fc9e type 'LED2003G10'

zigbee.0
2024-10-19 21:24:10.518	warn	ELEVATED: User stateChange zigbee.0.943469fffe55fc9e.state {"val":true,"ack":false,"ts":1729365850512,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1729365850512}

zigbee.0
2024-10-19 21:24:03.414	warn	ELEVATED Change state 'colortemp' at device 0x943469fffe55fc9e type 'LED2003G10'

zigbee.0
2024-10-19 21:24:03.330	warn	ELEVATED: User stateChange zigbee.0.943469fffe55fc9e.colortemp {"val":435,"ack":false,"ts":1729365843320,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1729365843320}

zigbee.0
2024-10-19 21:24:02.999	warn	ELEVATED Change state 'colortemp' at device 0x943469fffe55fc9e type 'LED2003G10'

zigbee.0
2024-10-19 21:24:02.913	warn	ELEVATED: User stateChange zigbee.0.943469fffe55fc9e.colortemp {"val":390,"ack":false,"ts":1729365842904,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1729365842904}

zigbee.0
2024-10-19 21:24:02.043	warn	ELEVATED Change state 'brightness' at device 0x943469fffe55fc9e type 'LED2003G10'

zigbee.0
2024-10-19 21:24:01.988	warn	ELEVATED: User stateChange zigbee.0.943469fffe55fc9e.brightness {"val":83,"ack":false,"ts":1729365841979,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1729365841979}

zigbee.0
2024-10-19 21:24:01.475	warn	ELEVATED Change state 'brightness' at device 0x943469fffe55fc9e type 'LED2003G10'

zigbee.0
2024-10-19 21:24:01.411	warn	ELEVATED: User stateChange zigbee.0.943469fffe55fc9e.brightness {"val":54,"ack":false,"ts":1729365841401,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1729365841401}

zigbee.0
2024-10-19 21:23:32.981	warn	ELEVATED Change state 'state' at device 0x943469fffe55fc9e type 'LED2003G10'

zigbee.0
2024-10-19 21:23:32.890	warn	ELEVATED: User stateChange zigbee.0.943469fffe55fc9e.state {"val":false,"ack":false,"ts":1729365812887,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1729365812887}

zigbee.0
2024-10-19 21:23:30.769	warn	ELEVATED Change state 'state' at device 0x943469fffe55fc9e type 'LED2003G10'

zigbee.0
2024-10-19 21:23:30.703	warn	ELEVATED: User stateChange zigbee.0.943469fffe55fc9e.state {"val":true,"ack":false,"ts":1729365810701,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1729365810701}

zigbee.0
2024-10-19 21:23:27.532	warn	ELEVATED Change state 'state' at device 0x943469fffe55fc9e type 'LED2003G10'

zigbee.0
2024-10-19 21:23:27.465	warn	ELEVATED: User stateChange zigbee.0.943469fffe55fc9e.state {"val":false,"ack":false,"ts":1729365807463,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1729365807463}

zigbee.0
2024-10-19 21:23:17.406	warn	ELEVATED Change state 'brightness' at device 0x943469fffe55fc9e type 'LED2003G10'

zigbee.0
2024-10-19 21:23:17.358	warn	ELEVATED: User stateChange zigbee.0.943469fffe55fc9e.brightness {"val":11,"ack":false,"ts":1729365797356,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1729365797356}

zigbee.0
2024-10-19 21:23:14.583	warn	ELEVATED Change state 'colortemp' at device 0x943469fffe55fc9e type 'LED2003G10'

zigbee.0
2024-10-19 21:23:14.524	warn	ELEVATED: User stateChange zigbee.0.943469fffe55fc9e.colortemp {"val":150,"ack":false,"ts":1729365794515,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1729365794515}

zigbee.0
2024-10-19 21:23:13.283	warn	ELEVATED Change state 'colortemp' at device 0x943469fffe55fc9e type 'LED2003G10'

zigbee.0
2024-10-19 21:23:13.226	warn	ELEVATED: User stateChange zigbee.0.943469fffe55fc9e.colortemp {"val":228,"ack":false,"ts":1729365793217,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1729365793217}

zigbee.0
2024-10-19 21:23:11.507	warn	ELEVATED Change state 'brightness' at device 0x943469fffe55fc9e type 'LED2003G10'

zigbee.0
2024-10-19 21:23:11.454	warn	ELEVATED: User stateChange zigbee.0.943469fffe55fc9e.brightness {"val":100,"ack":false,"ts":1729365791448,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1729365791448}

zigbee.0
2024-10-19 21:21:43.544	info	List of port: [{"path":"/dev/ttyS0","vendorId":"8086","productId":"9d27"},{"path":"/dev/ttyS1"},{"path":"/dev/ttyS2"},{"path":"/dev/ttyS3"}]

zigbee.0
2024-10-19 21:20:38.809	warn	ELEVATED Change state 'colortemp' at device 0x943469fffe55fc9e type 'LED2003G10'

zigbee.0
2024-10-19 21:20:38.749	warn	ELEVATED: User stateChange zigbee.0.943469fffe55fc9e.colortemp {"val":344,"ack":false,"ts":1729365638740,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1729365638740}

zigbee.0
2024-10-19 21:20:37.275	warn	ELEVATED Change state 'brightness' at device 0x943469fffe55fc9e type 'LED2003G10'

zigbee.0
2024-10-19 21:20:37.191	warn	ELEVATED: User stateChange zigbee.0.943469fffe55fc9e.brightness {"val":46,"ack":false,"ts":1729365637186,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1729365637186}

zigbee.0
2024-10-19 21:20:36.857	warn	ELEVATED Change state 'brightness' at device 0x943469fffe55fc9e type 'LED2003G10'

zigbee.0
2024-10-19 21:20:36.808	warn	ELEVATED: User stateChange zigbee.0.943469fffe55fc9e.brightness {"val":30,"ack":false,"ts":1729365636805,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1729365636805}

zigbee.0
2024-10-19 21:19:40.163	warn	ELEVATED publishToState: value generated '76' from device 943469fffe55fc9e for 'Link quality'

zigbee.0
2024-10-19 21:19:40.163	warn	ELEVATED publishToState: message received '{"linkquality":76}' from device 943469fffe55fc9e type 'LED2003G10'

zigbee.0
2024-10-19 21:19:37.174	warn	ELEVATED publishToState: value generated '76' from device 943469fffe55fc9e for 'Link quality'

zigbee.0
2024-10-19 21:19:37.173	warn	ELEVATED publishToState: message received '{"linkquality":76}' from device 943469fffe55fc9e type 'LED2003G10'

zigbee.0
2024-10-19 21:19:34.173	warn	ELEVATED publishToState: value generated '76' from device 943469fffe55fc9e for 'Link quality'

zigbee.0
2024-10-19 21:19:34.172	warn	ELEVATED publishToState: message received '{"linkquality":76}' from device 943469fffe55fc9e type 'LED2003G10'

zigbee.0
2024-10-19 21:19:31.157	warn	ELEVATED publishToState: value generated '76' from device 943469fffe55fc9e for 'Link quality'

zigbee.0
2024-10-19 21:19:31.156	warn	ELEVATED publishToState: message received '{"linkquality":76}' from device 943469fffe55fc9e type 'LED2003G10'

zigbee.0
2024-10-19 21:19:28.203	warn	ELEVATED publishToState: value generated '76' from device 943469fffe55fc9e for 'Link quality'

zigbee.0
2024-10-19 21:19:28.202	warn	ELEVATED publishToState: message received '{"linkquality":76}' from device 943469fffe55fc9e type 'LED2003G10'

                          Das passiert nach einem Neustart:

                          Zigbee Neustart.txt

                          Asgothian 1 Reply Last reply Reply Quote 0
                          • ilovegym
                            ilovegym Forum Testing last edited by ilovegym

                            @asgothian

                            Hi,
                            hier mit der aktuellen 1.10.10:
                            Edit: Docker V10, js-controller 7.00

                            
host.iobroker
2024-10-19 22:29:09.887	info	Restart adapter system.adapter.zigbee.0 because enabled

host.iobroker
2024-10-19 22:29:09.887	error	instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)

host.iobroker
2024-10-19 22:29:09.887	error	Caught by controller[2]: at Controller.onZclPayload (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/controller.ts:844:26)

host.iobroker
2024-10-19 22:29:09.887	error	Caught by controller[2]: at Controller.identifyUnknownDevice (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/controller.ts:543:26)

host.iobroker
2024-10-19 22:29:09.887	error	Caught by controller[2]: at ZStackAdapter.sendZdo (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:311:16)

host.iobroker
2024-10-19 22:29:09.887	error	Caught by controller[2]: at Queue.execute (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:36:20)

host.iobroker
2024-10-19 22:29:09.887	error	Caught by controller[2]: at processTicksAndRejections (node:internal/process/task_queues:95:5)

host.iobroker
2024-10-19 22:29:09.887	error	Caught by controller[2]: at /opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:403:47

host.iobroker
2024-10-19 22:29:09.887	error	Caught by controller[2]: at Object.start (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/waitress.ts:59:23)

host.iobroker
2024-10-19 22:29:09.886	error	Caught by controller[2]: Error: AREQ - ZDO - ieeeAddrRsp after 10000ms

host.iobroker
2024-10-19 22:29:09.886	error	Caught by controller[1]: 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(). The promise rejected with the reason:

zigbee.0
2024-10-19 22:29:09.343	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

zigbee.0
2024-10-19 22:29:09.342	info	terminating

zigbee.0
2024-10-19 22:29:05.740	info	Zigbee: disabling joining new devices.

zigbee.0
2024-10-19 22:29:05.738	info	cleaned everything up...

zigbee.0
2024-10-19 22:29:05.733	error	AREQ - ZDO - ieeeAddrRsp after 10000ms

zigbee.0
2024-10-19 22:29:05.732	error	Error: AREQ - ZDO - ieeeAddrRsp after 10000ms at Object.start (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/waitress.ts:59:23) at /opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:403:47 at processTicksAndRejections (node:internal/process/task_queues:95:5) at Queue.execute (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:36:20) at ZStackAdapter.sendZdo (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:311:16) at Controller.identifyUnknownDevice (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/controller.ts:543:26) at Controller.onZclPayload (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/controller.ts:844:26)

zigbee.0
2024-10-19 22:29:05.720	error	unhandled promise rejection: AREQ - ZDO - ieeeAddrRsp after 10000ms

zigbee.0
2024-10-19 22:29:05.719	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

influxdb.0
2024-10-19 22:28:59.059	info	Store 1001 buffered influxDB history points
                            Asgothian 1 Reply Last reply Reply Quote 0
                            • Asgothian
                              Asgothian Developer @ilovegym last edited by

                              @ilovegym sagte in Test Adapter iobroker.Zigbee 1.10.10:

                              hier mit der aktuellen 1.10.10:
                              Edit: Docker V10, js-controller 7.00

                              • Welche Koordinator Hardware
                              • Welche Firmware auf dem Koordinator ?
                              ilovegym 1 Reply Last reply Reply Quote 0
                              • ilovegym
                                ilovegym Forum Testing @Asgothian last edited by

                                @asgothian

                                cc26x2r1
                                965b0fda-32e2-4a2f-884e-91663a843fa3-A7D1AC31-13D3-4B64-9EF6-408D86712A52_1_201_a.jpeg

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

                                  Bitte installiert die aktuelle Version. Ich habe noch eine Anpassung durchgeführt.

                                  A.

                                  R 1 Reply Last reply Reply Quote 0
                                  • R
                                    Ritter @Asgothian last edited by

                                    @asgothian Leider keine Änderung.

                                    1 Reply Last reply Reply Quote 0
                                    • ilovegym
                                      ilovegym Forum Testing @Asgothian last edited by

                                      @asgothian

                                      hmm etwas besser, aber es kommen keine Werte an..
                                      startet jetzt, dann kommt empty object...

                                      host.iobroker
2024-10-20 00:12:06.413	info	Restart adapter system.adapter.zigbee.0 because enabled

host.iobroker
2024-10-20 00:12:06.412	error	instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)

host.iobroker
2024-10-20 00:12:06.412	error	Caught by controller[4]: at Immediate.<anonymous> (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:383:37)

host.iobroker
2024-10-20 00:12:06.412	error	Caught by controller[4]: at change (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:10907:34)

host.iobroker
2024-10-20 00:12:06.412	error	Caught by controller[4]: at Zigbee.emit (node:domain:488:12)

host.iobroker
2024-10-20 00:12:06.412	error	Caught by controller[4]: at Zigbee.emit (node:events:531:35)

host.iobroker
2024-10-20 00:12:06.412	error	Caught by controller[4]: at Zigbee.<anonymous> (/opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:16:48)

host.iobroker
2024-10-20 00:12:06.412	error	Caught by controller[4]: at Commands.onMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:84:34)

host.iobroker
2024-10-20 00:12:06.412	error	Caught by controller[4]: at Commands.getChannels (/opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:513:52)

host.iobroker
2024-10-20 00:12:06.411	error	Caught by controller[4]: at ZigbeeController.getChannelsEnergy (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1020:41)

host.iobroker
2024-10-20 00:12:06.411	error	Caught by controller[4]: at Znp.request (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:276:34)

host.iobroker
2024-10-20 00:12:06.411	error	Caught by controller[4]: at Function.createRequest (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/zpiObject.ts:57:19)

host.iobroker
2024-10-20 00:12:06.411	error	Caught by controller[4]: Error: Command request 'mgmtNwkUpdateReq' from subsystem '5' not found

host.iobroker
2024-10-20 00:12:06.411	error	Caught by controller[4]: 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(). The promise rejected with the reason:

host.iobroker
2024-10-20 00:12:06.411	error	Caught by controller[3]: TICMeter: Exposes: No endpoint

host.iobroker
2024-10-20 00:12:06.411	error	Caught by controller[2]: zhc:lixee: Not able to detect the current tarif. Not filtering any expose...

host.iobroker
2024-10-20 00:12:06.411	error	Caught by controller[1]: zhc:lixee: Was not able to detect the Linky energy_phase. Default to single_phase

host.iobroker
2024-10-20 00:12:06.410	error	Caught by controller[0]: zhc:lixee: Was not able to detect the Linky linky_mode. Default to historique

zigbee.0
2024-10-20 00:12:05.852	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

zigbee.0
2024-10-20 00:12:05.851	info	terminating

zigbee.0
2024-10-20 00:12:05.028	info	Zigbee: disabling joining new devices.

zigbee.0
2024-10-20 00:12:05.026	info	cleaned everything up...

zigbee.0
2024-10-20 00:12:05.021	error	Command request 'mgmtNwkUpdateReq' from subsystem '5' not found

zigbee.0
2024-10-20 00:12:05.021	error	Error: Command request 'mgmtNwkUpdateReq' from subsystem '5' not found at Function.createRequest (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/zpiObject.ts:57:19) at Znp.request (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:276:34) at ZigbeeController.getChannelsEnergy (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1020:41) at Commands.getChannels (/opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:513:52) at Commands.onMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:84:34) at Zigbee.<anonymous> (/opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:16:48) at Zigbee.emit (node:events:531:35) at Zigbee.emit (node:domain:488:12) at change (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:10907:34) at Immediate.<anonymous> (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:383:37)

zigbee.0
2024-10-20 00:12:04.924	error	unhandled promise rejection: Command request 'mgmtNwkUpdateReq' from subsystem '5' not found

zigbee.0
2024-10-20 00:12:04.924	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

tuya.0
2024-10-20 00:12:04.867	info	bfd7260934b09826b5fki4: Error on Reconnect (7): connection timed out

tuya.0
2024-10-20 00:12:03.019	info	bfeeaa29ccb41608a6wp8h: Error on Reconnect (5): connection timed out

tuya.0
2024-10-20 00:12:01.801	info	bf173c5af3445d8de5ayds: Error on Reconnect (1): connection timed out

zigbee.0
2024-10-20 00:12:00.459	error	empty object!

sonoff.0
2024-10-20 00:11:59.670	info	Client [USBSwitch15] connected with secret 1729375919669_1883

zigbee.0
2024-10-20 00:11:59.227	error	empty object!

zigbee.0
2024-10-20 00:11:59.218	error	empty object!

zigbee.0
2024-10-20 00:11:59.179	error	empty object!

zigbee.0
2024-10-20 00:11:59.168	error	empty object!

zigbee.0
2024-10-20 00:11:59.116	error	empty object!

zigbee.0
2024-10-20 00:11:59.102	error	empty object!

zigbee.0
2024-10-20 00:11:59.098	error	empty object!

zigbee.0
2024-10-20 00:11:59.067	error	empty object!

zigbee.0
2024-10-20 00:11:59.023	error	empty object!

zigbee.0
2024-10-20 00:11:59.013	error	empty object!

zigbee.0
2024-10-20 00:11:58.980	error	empty object!

zigbee.0
2024-10-20 00:11:58.975	error	empty object!

zigbee.0
2024-10-20 00:11:58.929	error	empty object!

zigbee.0
2024-10-20 00:11:58.917	info	List of port: [{"path":"/dev/ttyS0"},{"path":"/dev/ttyS1"},{"path":"/dev/ttyS2"},{"path":"/dev/ttyS3"}]

zigbee.0
2024-10-20 00:11:58.864	error	empty object!

zigbee.0
2024-10-20 00:11:58.860	error	empty object!

zigbee.0
2024-10-20 00:11:58.829	error	empty object!
                                      Asgothian 1 Reply Last reply Reply Quote 0
                                      • Asgothian
                                        Asgothian Developer @ilovegym last edited by Asgothian

                                        @ilovegym sagte in Test Adapter iobroker.Zigbee 1.10.10:

                                        hmm etwas besser, aber es kommen keine Werte an..
                                        startet jetzt, dann kommt empty object...

                                        Kannst du beschreiben was du genau getan hast ?

                                        Bei mir läuft der Adapter prinzipiell so, allerdings kann ich den hier geposteten Fehler erzwingen.

                                        • Wie entsteht der Fehler bei Dir ?
                                        • was passiert wenn du versuchst Zigbee-Geräte zu steuern ? Gibt es Fehlermeldungen im Log ?
                                        • Wie sieht die Kommunikation mit einem Gerät bei Dir aus, wenn du wie @ritter ein Gerät für die Debug-Messages einträgst (Anleitung dazu weiter oben) ?

                                        A.

                                        ilovegym 1 Reply Last reply Reply Quote 0
                                        • ilovegym
                                          ilovegym Forum Testing @Asgothian last edited by

                                          @asgothian

                                          frag nich.. ich hatte ja diese Testversion 1.10.9 aus deinem Repo die ganze Zeit laufen, lief auch zu 98% gut.
                                          Jetzt startet der Zigbee gar nicht mehr, immer mit diesem Fehler, gerade von Git geladen:

                                          zigbee.0
2024-10-20 10:21:09.494	error	Error herdsman start

zigbee.0
2024-10-20 10:21:09.494	error	Failed to start Zigbee

zigbee.0
2024-10-20 10:21:09.493	error	Starting zigbee-herdsman problem : "network commissioning timed out - most likely network with the same panId or extendedPanId already exists nearby (Error: AREQ - ZDO - stateChangeInd after 60000ms\n at Object.start (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/waitress.ts:59:23)\n at ZnpAdapterManager.beginCommissioning (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/manager.ts:370:31)\n at processTicksAndRejections (node:internal/process/task_queues:95:5)\n at ZnpAdapterManager.start (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/manager.ts:91:21)\n at ZStackAdapter.start (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:158:16)\n at Controller.start (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/controller.ts:137:29)\n at ZigbeeController.start (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:131:13)\n at Zigbee.doConnect (/opt/iobroker/node_modules/iobroker.zigbee/main.js:316:13))"
                                          ilovegym 1 Reply Last reply Reply Quote 0
                                          • ilovegym
                                            ilovegym Forum Testing @ilovegym last edited by

                                            @ilovegym

                                            gerade nochmal Adapter gestoppt, den TI power-resetted, in den Einstellungen des Adapters gesehen, dass bei Sendeleistung Sendeleistung stand, also anstatt normal, high usw. stand da Sendeleistung Sendeleistung drin..
                                            Hab jetzt mal auf normal gestellt.. und der Adapter startet...

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            1.0k
                                            Online

                                            30.5k
                                            Users

                                            76.7k
                                            Topics

                                            1.2m
                                            Posts

                                            14
                                            129
                                            3748
                                            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