Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. laufend die Warnungen "unknown message ID"

    NEWS

    • Neues Video über Aliase, virtuelle Geräte und Kategorien

    • Wir empfehlen: Node.js 22.x

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    laufend die Warnungen "unknown message ID"

    This topic has been deleted. Only users with topic management privileges can see it.
    • Cinimod
      Cinimod Most Active last edited by

      Hallo freunde,
      ich bekomme laufend diese Warnungen, meist sind es zwei oder drei Geräte, immer wieder mal.

      Ich habe immer noch keine Idee was das soll, vielleicht kann mir jemand nen Tip geben ?!

      Auf den beiden hier aufgeführten Geräten ist Tasmota am laufen.

      
sonoff.0
2022-11-25 19:44:04.519	warn	Client [Shelly-RGBW2-2] Received puback for unknown message ID: 20536

sonoff.0
2022-11-25 19:44:04.513	warn	Client [Shelly-RGBW2-2] Received pubrel on Shelly-RGBW2-2 for unknown messageId 25890

sonoff.0
2022-11-25 19:44:04.513	warn	Client [Shelly-RGBW2-2] Received pubrel on Shelly-RGBW2-2 for unknown messageId 29285

sonoff.0
2022-11-25 19:44:04.512	warn	Client [Shelly-RGBW2-2] Received pubcomp for unknown message ID: 28533

sonoff.0
2022-11-25 19:44:04.511	warn	Client [Shelly-RGBW2-2] Received pubcomp for unknown message ID: 8279

sonoff.0
2022-11-25 19:44:04.511	warn	Client [Shelly-RGBW2-2] Received pubcomp for unknown message ID: 25378

sonoff.0
2022-11-25 19:44:04.511	warn	Client [Shelly-RGBW2-2] Received pubrec on Shelly-RGBW2-2 for unknown messageId 21589

sonoff.0
2022-11-25 19:44:04.509	warn	Client [Shelly-RGBW2-2] Received pubcomp for unknown message ID: 26990

sonoff.0
2022-11-25 19:44:04.509	warn	Client [Shelly-RGBW2-2] Received pubrel on Shelly-RGBW2-2 for unknown messageId 28528

sonoff.0
2022-11-25 19:44:04.508	warn	Client [Shelly-RGBW2-2] Received puback for unknown message ID: 11298

sonoff.0
2022-11-25 19:44:04.519	warn	Client [Shelly-RGBW2-2] Received puback for unknown message ID: 20536

sonoff.0
2022-11-25 19:44:04.513	warn	Client [Shelly-RGBW2-2] Received pubrel on Shelly-RGBW2-2 for unknown messageId 25890

sonoff.0
2022-11-25 19:44:04.513	warn	Client [Shelly-RGBW2-2] Received pubrel on Shelly-RGBW2-2 for unknown messageId 29285

sonoff.0
2022-11-25 19:44:04.512	warn	Client [Shelly-RGBW2-2] Received pubcomp for unknown message ID: 28533

sonoff.0
2022-11-25 19:44:04.511	warn	Client [Shelly-RGBW2-2] Received pubcomp for unknown message ID: 8279

sonoff.0
2022-11-25 19:44:04.511	warn	Client [Shelly-RGBW2-2] Received pubcomp for unknown message ID: 25378

sonoff.0
2022-11-25 19:44:04.511	warn	Client [Shelly-RGBW2-2] Received pubrec on Shelly-RGBW2-2 for unknown messageId 21589

sonoff.0
2022-11-25 19:44:04.509	warn	Client [Shelly-RGBW2-2] Received pubcomp for unknown message ID: 26990

sonoff.0
2022-11-25 19:44:04.509	warn	Client [Shelly-RGBW2-2] Received pubrel on Shelly-RGBW2-2 for unknown messageId 28528

sonoff.0
2022-11-25 19:44:04.508	warn	Client [Shelly-RGBW2-2] Received puback for unknown message ID: 11298

sonoff.0
2022-11-25 19:44:04.519	warn	Client [Shelly-RGBW2-2] Received puback for unknown message ID: 20536

sonoff.0
2022-11-25 19:44:04.513	warn	Client [Shelly-RGBW2-2] Received pubrel on Shelly-RGBW2-2 for unknown messageId 25890

sonoff.0
2022-11-25 19:44:04.513	warn	Client [Shelly-RGBW2-2] Received pubrel on Shelly-RGBW2-2 for unknown messageId 29285

sonoff.0
2022-11-25 19:44:04.512	warn	Client [Shelly-RGBW2-2] Received pubcomp for unknown message ID: 28533

sonoff.0
2022-11-25 19:44:04.511	warn	Client [Shelly-RGBW2-2] Received pubcomp for unknown message ID: 8279

sonoff.0
2022-11-25 19:44:04.511	warn	Client [Shelly-RGBW2-2] Received pubcomp for unknown message ID: 25378

sonoff.0
2022-11-25 19:44:04.511	warn	Client [Shelly-RGBW2-2] Received pubrec on Shelly-RGBW2-2 for unknown messageId 21589

sonoff.0
2022-11-25 19:44:04.509	warn	Client [Shelly-RGBW2-2] Received pubcomp for unknown message ID: 26990

sonoff.0
2022-11-25 19:44:04.509	warn	Client [Shelly-RGBW2-2] Received pubrel on Shelly-RGBW2-2 for unknown messageId 28528

sonoff.0
2022-11-25 19:44:04.508	warn	Client [Shelly-RGBW2-2] Received puback for unknown message ID: 11298

sonoff.0
2022-11-25 19:44:04.519	warn	Client [Shelly-RGBW2-2] Received puback for unknown message ID: 20536

sonoff.0
2022-11-25 19:44:04.513	warn	Client [Shelly-RGBW2-2] Received pubrel on Shelly-RGBW2-2 for unknown messageId 25890

sonoff.0
2022-11-25 19:44:04.513	warn	Client [Shelly-RGBW2-2] Received pubrel on Shelly-RGBW2-2 for unknown messageId 29285

sonoff.0
2022-11-25 19:44:04.512	warn	Client [Shelly-RGBW2-2] Received pubcomp for unknown message ID: 28533

sonoff.0
2022-11-25 19:44:04.511	warn	Client [Shelly-RGBW2-2] Received pubcomp for unknown message ID: 8279

sonoff.0
2022-11-25 19:44:04.511	warn	Client [Shelly-RGBW2-2] Received pubcomp for unknown message ID: 25378

sonoff.0
2022-11-25 19:44:04.511	warn	Client [Shelly-RGBW2-2] Received pubrec on Shelly-RGBW2-2 for unknown messageId 21589

sonoff.0
2022-11-25 19:44:04.509	warn	Client [Shelly-RGBW2-2] Received pubcomp for unknown message ID: 26990

sonoff.0
2022-11-25 19:44:04.509	warn	Client [Shelly-RGBW2-2] Received pubrel on Shelly-RGBW2-2 for unknown messageId 28528

sonoff.0
2022-11-25 19:44:04.508	warn	Client [Shelly-RGBW2-2] Received puback for unknown message ID: 11298

sonoff.0
2022-11-25 19:44:04.519	warn	Client [Shelly-RGBW2-2] Received puback for unknown message ID: 20536

sonoff.0
2022-11-25 19:44:04.513	warn	Client [Shelly-RGBW2-2] Received pubrel on Shelly-RGBW2-2 for unknown messageId 25890

sonoff.0
2022-11-25 19:44:04.513	warn	Client [Shelly-RGBW2-2] Received pubrel on Shelly-RGBW2-2 for unknown messageId 29285

sonoff.0
2022-11-25 19:44:04.512	warn	Client [Shelly-RGBW2-2] Received pubcomp for unknown message ID: 28533

sonoff.0
2022-11-25 19:44:04.511	warn	Client [Shelly-RGBW2-2] Received pubcomp for unknown message ID: 8279

sonoff.0
2022-11-25 19:44:04.511	warn	Client [Shelly-RGBW2-2] Received pubcomp for unknown message ID: 25378

sonoff.0
2022-11-25 19:44:04.511	warn	Client [Shelly-RGBW2-2] Received pubrec on Shelly-RGBW2-2 for unknown messageId 21589

sonoff.0
2022-11-25 19:44:04.509	warn	Client [Shelly-RGBW2-2] Received pubcomp for unknown message ID: 26990

sonoff.0
2022-11-25 19:44:04.509	warn	Client [Shelly-RGBW2-2] Received pubrel on Shelly-RGBW2-2 for unknown messageId 28528

sonoff.0
2022-11-25 19:44:04.508	warn	Client [Shelly-RGBW2-2] Received puback for unknown message ID: 11298

sonoff.0
2022-11-25 19:44:04.519	warn	Client [Shelly-RGBW2-2] Received puback for unknown message ID: 20536

sonoff.0
2022-11-25 19:44:04.513	warn	Client [Shelly-RGBW2-2] Received pubrel on Shelly-RGBW2-2 for unknown messageId 25890

sonoff.0
2022-11-25 19:44:04.513	warn	Client [Shelly-RGBW2-2] Received pubrel on Shelly-RGBW2-2 for unknown messageId 29285

sonoff.0
2022-11-25 19:44:04.512	warn	Client [Shelly-RGBW2-2] Received pubcomp for unknown message ID: 28533

sonoff.0
2022-11-25 19:44:04.511	warn	Client [Shelly-RGBW2-2] Received pubcomp for unknown message ID: 8279

sonoff.0
2022-11-25 19:44:04.511	warn	Client [Shelly-RGBW2-2] Received pubcomp for unknown message ID: 25378

sonoff.0
2022-11-25 19:44:04.511	warn	Client [Shelly-RGBW2-2] Received pubrec on Shelly-RGBW2-2 for unknown messageId 21589

sonoff.0
2022-11-25 19:44:04.509	warn	Client [Shelly-RGBW2-2] Received pubcomp for unknown message ID: 26990

sonoff.0
2022-11-25 19:44:04.509	warn	Client [Shelly-RGBW2-2] Received pubrel on Shelly-RGBW2-2 for unknown messageId 28528

sonoff.0
2022-11-25 19:44:04.508	warn	Client [Shelly-RGBW2-2] Received puback for unknown message ID: 11298

sonoff.0
2022-11-25 18:51:38.551	warn	Client [Blitzwolf-SHP6-2] Received pubrel on Blitzwolf-SHP6-2 for unknown messageId 25953

sonoff.0
2022-11-25 18:51:38.551	warn	Client [Blitzwolf-SHP6-2] Received pubrel on Blitzwolf-SHP6-2 for unknown messageId 14882

sonoff.0
2022-11-25 18:51:38.550	warn	Client [Blitzwolf-SHP6-2] Received pubrec on Blitzwolf-SHP6-2 for unknown messageId 21297

sonoff.0
2022-11-25 18:51:38.550	warn	Client [Blitzwolf-SHP6-2] Received pubrec on Blitzwolf-SHP6-2 for unknown messageId 29793

sonoff.0
2022-11-25 18:50:18.580	warn	Client [Shelly-RGBW2-2] Received pubcomp for unknown message ID: 24946

sonoff.0
2022-11-25 18:50:18.579	warn	Client [Shelly-RGBW2-2] Received pubrel on Shelly-RGBW2-2 for unknown messageId 8762

sonoff.0
2022-11-25 18:50:18.579	warn	Client [Shelly-RGBW2-2] Received pubrel on Shelly-RGBW2-2 for unknown messageId 24937

sonoff.0
2022-11-25 18:50:18.578	warn	Client [Shelly-RGBW2-2] Received pubrel on Shelly-RGBW2-2 for unknown messageId 26979

sonoff.0
2022-11-25 18:51:38.551	warn	Client [Blitzwolf-SHP6-2] Received pubrel on Blitzwolf-SHP6-2 for unknown messageId 25953

sonoff.0
2022-11-25 18:51:38.551	warn	Client [Blitzwolf-SHP6-2] Received pubrel on Blitzwolf-SHP6-2 for unknown messageId 14882

sonoff.0
2022-11-25 18:51:38.550	warn	Client [Blitzwolf-SHP6-2] Received pubrec on Blitzwolf-SHP6-2 for unknown messageId 21297

sonoff.0
2022-11-25 18:51:38.550	warn	Client [Blitzwolf-SHP6-2] Received pubrec on Blitzwolf-SHP6-2 for unknown messageId 29793

sonoff.0
2022-11-25 18:50:18.580	warn	Client [Shelly-RGBW2-2] Received pubcomp for unknown message ID: 24946

sonoff.0
2022-11-25 18:50:18.579	warn	Client [Shelly-RGBW2-2] Received pubrel on Shelly-RGBW2-2 for unknown messageId 8762

sonoff.0
2022-11-25 18:50:18.579	warn	Client [Shelly-RGBW2-2] Received pubrel on Shelly-RGBW2-2 for unknown messageId 24937

sonoff.0
2022-11-25 18:50:18.578	warn	Client [Shelly-RGBW2-2] Received pubrel on Shelly-RGBW2-2 for unknown messageId 26979
      haselchen 1 Reply Last reply Reply Quote 0
      • mickym
        mickym Most Active last edited by

        Tja wahrscheinlich liegt es am sonoff - der halt kein mqtt Broker ist und irgendwas nicht interpretieren kann.

        Cinimod 1 Reply Last reply Reply Quote 0
        • haselchen
          haselchen Most Active @Cinimod last edited by

          @cinimod

          Wie ist dein Netzwerk aufgebaut ?
          Shellys und Iobroker in verschiedenen Netzen?
          Repeater im Spiel?

          Cinimod 1 Reply Last reply Reply Quote 0
          • Cinimod
            Cinimod Most Active @mickym last edited by

            @mickym

            Daran dachte ich auch die ganze zeit, aber ich hab ja noch einige mehr Geräte im Sonoff Adapter verbunden, mit der gleichen konfig. und Tasmota. Es sind immer die selben zwei oder drei Geräte wo die Warnungen kommen.

            mickym 1 Reply Last reply Reply Quote 0
            • Cinimod
              Cinimod Most Active @haselchen last edited by

              @haselchen

              Es ist alles im Selben Netzwerk, nen Repeater habe ich allerdings auch, jedoch sind diese beiden Geräte in unmittelbarer nähre des Routers und auch direkt mit diesem verbunden, hab ich gerade geprüft.

              1 Reply Last reply Reply Quote 0
              • mickym
                mickym Most Active @Cinimod last edited by

                @cinimod sagte in laufend die Warnungen "unknown message ID":

                @mickym

                Daran dachte ich auch die ganze zeit, aber ich hab ja noch einige mehr Geräte im Sonoff Adapter verbunden, mit der gleichen konfig. und Tasmota. Es sind immer die selben zwei oder drei Geräte wo die Warnungen kommen.

                Na ja - das meine ich ja - das ist halt das Problem dieser Adapter. Es ist ja nicht so, dass die Geräte gar nicht funktionieren. Nur sobald die halt Meldungen von sich geben, mit den der Adapter nichts anfangen kann, dann hast halt ein Problem.

                Theoretisch kannst ja über mqtt die beiden Geräte direkt steuern (halt anderer port).

                Cinimod 1 Reply Last reply Reply Quote 0
                • Cinimod
                  Cinimod Most Active @mickym last edited by Cinimod

                  @mickym

                  Das heißt aber auch, das ich die Warnungen getrost ignorieren kann? Die Daten die ich brauche bekomme ich ja ...

                  Oder schaue ich das ich alle auf den Mqtt broker umbaue, und den ganzen Alias kram umschreibe ?

                  mickym crunchip 2 Replies Last reply Reply Quote 0
                  • mickym
                    mickym Most Active @Cinimod last edited by

                    @cinimod Das weiß ich nicht, ob Du die Meldungen ignorieren kannst. Du kannst ja auch die Entwickler des sonoff-Adapters ansprechen. Vielleicht auch den Adapter in debug Mode schalten. Vielleicht erkennt man dann ja welche originäre Nachricht diesen Fehler erzeugt. Vielleicht kann man ja auch durch eine Konfigurationsänderung die Meinung vermeiden.

                    Ich persönlich bin kein Freund von Adaptern, die halt nur wegen der Interpretation oder weil man mit JSON Strings nicht umgehen kann, das in einzelne Datenpunkte auflöst. Ich habe nur 3 Tasmota Geräte - die ich aber nur mit mqtt steuere.

                    Also versuche halt erst mal über den debug Mode herauszufinden, was die Meldung erzeugt und vielleicht kann der Adapterentwickler damit was anfangen.

                    1 Reply Last reply Reply Quote 0
                    • crunchip
                      crunchip Forum Testing Most Active @Cinimod last edited by

                      @cinimod solch Meldungen hab ich auch hin und wieder, denke das hängt mit dem Netzwerk zusammen.
                      Als ich damals mehrere Cam's per Wlan laufen hatte(Fritzbox) kamen auch vermehrt solch Meldungen.

                      Mittlerweile hab ich auf unifi umgestellt, Cam's laufen überwiegend per Lan,
                      allerdings bekomm ich trotzdem hin und wieder diese Meldungen, sobald ich TasmoAdmin aufrufe.

                      Cinimod 1 Reply Last reply Reply Quote 0
                      • Cinimod
                        Cinimod Most Active @crunchip last edited by Cinimod

                        @crunchip

                        TasmotaAdmin ist ein gutes Stichwort.

                        Wenn ich es mir recht überlege sehe ich das immer nur wenn ich auf der TasmotaAdmin Oberfläche war.
                        Ich glaube, ich könnte sogar sagen das ich genau diese Geräte über TA aufgerufen habe, wenn ich es mir recht überlege. Werde das direkt ausprobieren.

                        Wir kommen der Sache näher.

                        EDIT: Ich konnte das so NICHT reproduzieren, leider auch Fehlanzeige.

                        crunchip haselchen 2 Replies Last reply Reply Quote 0
                        • crunchip
                          crunchip Forum Testing Most Active @Cinimod last edited by

                          @cinimod sagte in laufend die Warnungen "unknown message ID":

                          Ich konnte das so NICHT reproduzieren

                          das nicht immer, aber bei mir tritt das eben nur auf, wenn

                          @cinimod sagte in laufend die Warnungen "unknown message ID":

                          ich auf der TasmotaAdmin Oberfläche war

                          1 Reply Last reply Reply Quote 0
                          • haselchen
                            haselchen Most Active @Cinimod last edited by

                            @cinimod

                            Kann aber zu 100% @crunchip Aussage zustimmen.
                            Deswegen hatte ich nach dem Netzwerk gefragt.
                            Ich hatte ebenso TasmoAdmin in Gebrauch und bekam genau diese Meldungen.
                            TasmoAdmin gelöscht, Meldungen weg.
                            Diese Kombi scheint wohl mal so überhaupt nicht zu harmonieren.

                            crunchip 1 Reply Last reply Reply Quote 0
                            • crunchip
                              crunchip Forum Testing Most Active @haselchen last edited by

                              @haselchen tasmo admin läuft nach wie vor, hin und wieder brauch ichs ja, allerdings kommen die Meldungen wirklich nur, wenn ich die Gui aufrufen, ansonsten nicht

                              haselchen 1 Reply Last reply Reply Quote 0
                              • haselchen
                                haselchen Most Active @crunchip last edited by

                                @crunchip

                                Stimmt, genau dann hatte ich das auch.
                                Vielleicht hilft das dem TE weiter.

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

                                Support us

                                ioBroker
                                Community Adapters
                                Donate
                                FAQ Cloud / IOT
                                HowTo: Node.js-Update
                                HowTo: Backup/Restore
                                Downloads
                                BLOG

                                855
                                Online

                                32.0k
                                Users

                                80.5k
                                Topics

                                1.3m
                                Posts

                                4
                                14
                                1482
                                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