Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. MQTT Adapter macht Probleme

    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

    MQTT Adapter macht Probleme

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

      Du hast Node 10.9 installiert? Mach mal ein Nodejs- und npm-Downgrade wie hier im Schritt 1 beschrieben:

      viewtopic.php?f=17&t=16119&p=169390#p169390

      32bit Node, wenn Dein OS 32bit ist.

      1 Reply Last reply Reply Quote 0
      • Der_LuLe
        Der_LuLe last edited by

        Ich habs versucht, ist ne 64bit…

        leider keine Besserung, evtl hab ich auch was falsch gemacht :oops:

        beim starten hab ich auch Fehler im Log :

        node-red.0 2018-08-22 11:08:29.804 error Cannot install npm packet: LemPi

        node-red.0 2018-08-22 11:08:29.804 error Cannot install LemPi: 1

        node-red.0 2018-08-22 11:08:29.773 error ERR! A complete log of this run can be found in: npm ERR! C:\WINDOWS\system32\config\systemprofile\AppData\Roaming\npm-cache_logs\2018-08-22T09_08_29_757Z-debug.log

        node-red.0 2018-08-22 11:08:29.773 error npm

        node-red.0 2018-08-22 11:08:29.757 error 404 Not Found: LemPi@latest

        node-red.0 2018-08-22 11:08:29.757 error ERR!

        node-red.0 2018-08-22 11:08:29.757 error

        node-red.0 2018-08-22 11:08:29.757 error npm

        node-red.0 2018-08-22 11:08:29.741 error npm ERR! code E404

        node-red.0 2018-08-22 11:08:25.258 info npm install LemPi --production --prefix "C:\ioBroker\node_modules\iobroker.node-red" --save (System call)

        node-red.0 2018-08-22 11:08:25.258 error Cannot install LemPi: 1

        node-red.0 2018-08-22 11:08:25.227 error ERR! A complete log of this run can be found in: npm ERR! C:\WINDOWS\system32\config\systemprofile\AppData\Roaming\npm-cache_logs\2018-08-22T09_08_25_211Z-debug.log

        node-red.0 2018-08-22 11:08:25.227 error npm

        node-red.0 2018-08-22 11:08:25.227 error npm ERR! 404 Not Found: LemPi@latest

        node-red.0 2018-08-22 11:08:25.211 error ERR! code E404

        node-red.0 2018-08-22 11:08:25.211 error npm

        node-red.0 2018-08-22 11:08:20.665 info npm install LemPi --production --prefix "C:\ioBroker\node_modules\iobroker.node-red" --save (System call)

        node-red.0 2018-08-22 11:08:20.665 error Cannot install LemPi: 1

        node-red.0 2018-08-22 11:08:20.649 error

        node-red.0 2018-08-22 11:08:20.649 error npm ERR! C:\WINDOWS\system32\config\systemprofile\AppData\Roaming\npm-cache_logs\2018-08-22T09_08_20_634Z-debug.log

        node-red.0 2018-08-22 11:08:20.649 error npm ERR! A complete log of this run can be found in:

        node-red.0 2018-08-22 11:08:20.649 error

        node-red.0 2018-08-22 11:08:20.649 error

        node-red.0 2018-08-22 11:08:20.618 error

        node-red.0 2018-08-22 11:08:20.618 error ERR! 404 Not Found: LemPi@latest

        node-red.0 2018-08-22 11:08:20.618 error npm

        node-red.0 2018-08-22 11:08:20.618 error

        node-red.0 2018-08-22 11:08:20.618 error ERR! code E404

        node-red.0 2018-08-22 11:08:20.618 error npm

        Ich hab node.js deinstaliert und von dem Link neu istalliert dann alles wie in derAnleitung, nur dass der der Odner einmal nicht im "C:\Program Files (x86)" sondern im "C:\Program Files" war ist da ein Fehler?

        Danke!!! 😄

        1 Reply Last reply Reply Quote 0
        • Stabilostick
          Stabilostick last edited by

          Du hast eine Nachricht.

          1 Reply Last reply Reply Quote 0
          • Der_LuLe
            Der_LuLe last edited by

            Danke für das Angebot muss jetzt erst mal zur Arbeit, ich versuch es morgen noch mal mit der Anleitung…

            😄

            1 Reply Last reply Reply Quote 0
            • Stabilostick
              Stabilostick last edited by

              Was steht denn in so einer npm-Logdatei?

              1 Reply Last reply Reply Quote 0
              • Der_LuLe
                Der_LuLe last edited by

                wo finde ich die :oops:

                1 Reply Last reply Reply Quote 0
                • Stabilostick
                  Stabilostick last edited by

                  Steht doch oben im Log. ….debug.log

                  1 Reply Last reply Reply Quote 0
                  • Der_LuLe
                    Der_LuLe last edited by

                    So hab grade mal 2 Stunden Zeit gehabt und alles deinstalliert und Ordner gelöscht. Dann nach der Anleitung installiert und es geht immer noch nicht…

                    Leider kein Log mehr in dem Verzeichnis gefunden... hätte ich vorher mal reinschauen sollen.

                    Hier ein Aktuelles Log:

                    mqtt.0 2018-08-26 11:05:42.410 info Client [Steckdose1] connected with secret 1535274342410_3386

                    mqtt.0 2018-08-26 11:05:42.301 info Client [Annas_Lampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:42.192 info Client [Annas_Lampe] connected with secret 1535274342192_994

                    mqtt.0 2018-08-26 11:05:41.692 info Client [Unten] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:41.676 info Client [WonzimmerLampen] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:41.661 info Client [Stehlampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:41.582 info Client [Unten] connected with secret 1535274341582_3525

                    mqtt.0 2018-08-26 11:05:41.567 info Client [WonzimmerLampen] connected with secret 1535274341567_7923

                    mqtt.0 2018-08-26 11:05:41.551 info Client [Stehlampe] connected with secret 1535274341551_5819

                    mqtt.0 2018-08-26 11:05:41.457 info Client [Steckdose1] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:41.348 info Client [Steckdose1] connected with secret 1535274341348_4990

                    mqtt.0 2018-08-26 11:05:41.239 info Client [Annas_Lampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:41.129 info Client [Annas_Lampe] connected with secret 1535274341129_4144

                    mqtt.0 2018-08-26 11:05:40.629 info Client [Unten] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:40.598 info Client [WonzimmerLampen] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:40.598 info Client [Stehlampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:40.504 info Client [Unten] connected with secret 1535274340504_2594

                    mqtt.0 2018-08-26 11:05:40.489 info Client [WonzimmerLampen] connected with secret 1535274340489_7537

                    mqtt.0 2018-08-26 11:05:40.489 info Client [Stehlampe] connected with secret 1535274340489_6350

                    mqtt.0 2018-08-26 11:05:40.395 info Client [Steckdose1] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:40.286 info Client [Steckdose1] connected with secret 1535274340286_5872

                    mqtt.0 2018-08-26 11:05:40.176 info Client [Annas_Lampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:40.067 info Client [Annas_Lampe] connected with secret 1535274340067_2258

                    mqtt.0 2018-08-26 11:05:39.552 info Client [Unten] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:39.536 info Client [WonzimmerLampen] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:39.536 info Client [Stehlampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:39.442 info Client [Unten] connected with secret 1535274339442_7371

                    mqtt.0 2018-08-26 11:05:39.427 info Client [WonzimmerLampen] connected with secret 1535274339427_2184

                    mqtt.0 2018-08-26 11:05:39.427 info Client [Stehlampe] connected with secret 1535274339427_7281

                    mqtt.0 2018-08-26 11:05:39.333 info Client [Steckdose1] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:39.224 info Client [Steckdose1] connected with secret 1535274339224_4984

                    mqtt.0 2018-08-26 11:05:39.114 info Client [Annas_Lampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:39.005 info Client [Annas_Lampe] connected with secret 1535274339005_8991

                    mqtt.0 2018-08-26 11:05:38.474 info Client [Unten] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:38.458 info Client [WonzimmerLampen] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:38.458 info Client [Stehlampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:38.364 info Client [Unten] connected with secret 1535274338349_1234

                    mqtt.0 2018-08-26 11:05:38.349 info Client [WonzimmerLampen] connected with secret 1535274338349_1913

                    mqtt.0 2018-08-26 11:05:38.333 info Client [Stehlampe] connected with secret 1535274338333_5419

                    mqtt.0 2018-08-26 11:05:38.271 info Client [Steckdose1] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:38.161 info Client [Steckdose1] connected with secret 1535274338161_2661

                    mqtt.0 2018-08-26 11:05:38.052 info Client [Annas_Lampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:37.943 info Client [Annas_Lampe] connected with secret 1535274337943_4485

                    mqtt.0 2018-08-26 11:05:37.396 info Client [Unten] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:37.380 info Client [WonzimmerLampen] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:37.380 info Client [Stehlampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:37.286 info Client [Unten] connected with secret 1535274337286_1723

                    mqtt.0 2018-08-26 11:05:37.271 info Client [WonzimmerLampen] connected with secret 1535274337271_6341

                    mqtt.0 2018-08-26 11:05:37.271 info Client [Stehlampe] connected with secret 1535274337271_4668

                    mqtt.0 2018-08-26 11:05:37.208 info Client [Steckdose1] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:37.099 info Client [Steckdose1] connected with secret 1535274337099_9087

                    mqtt.0 2018-08-26 11:05:36.990 info Client [Annas_Lampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:36.880 info Client [Annas_Lampe] connected with secret 1535274336880_4131

                    mqtt.0 2018-08-26 11:05:36.318 info Client [Unten] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:36.318 info Client [WonzimmerLampen] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:36.318 info Client [Stehlampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:36.208 info Client [Unten] connected with secret 1535274336208_3135

                    mqtt.0 2018-08-26 11:05:36.208 info Client [WonzimmerLampen] connected with secret 1535274336208_4719

                    mqtt.0 2018-08-26 11:05:36.208 info Client [Stehlampe] connected with secret 1535274336208_6182

                    mqtt.0 2018-08-26 11:05:36.146 info Client [Steckdose1] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:36.037 info Client [Steckdose1] connected with secret 1535274336037_508

                    mqtt.0 2018-08-26 11:05:35.927 info Client [Annas_Lampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:35.818 info Client [Annas_Lampe] connected with secret 1535274335818_2528

                    mqtt.0 2018-08-26 11:05:35.240 info Client [Unten] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:35.240 info Client [Stehlampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:35.240 info Client [WonzimmerLampen] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:35.131 info Client [Unten] connected with secret 1535274335131_3921

                    mqtt.0 2018-08-26 11:05:35.131 info Client [Stehlampe] connected with secret 1535274335131_4675

                    mqtt.0 2018-08-26 11:05:35.115 info Client [WonzimmerLampen] connected with secret 1535274335115_2373

                    mqtt.0 2018-08-26 11:05:35.084 info Client [Steckdose1] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:34.975 info Client [Steckdose1] connected with secret 1535274334975_8787

                    mqtt.0 2018-08-26 11:05:34.865 info Client [Annas_Lampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:34.756 info Client [Annas_Lampe] connected with secret 1535274334756_1596

                    mqtt.0 2018-08-26 11:05:34.162 info Client [Unten] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:34.162 info Client [Stehlampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:34.162 info Client [WonzimmerLampen] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:34.053 info Client [Unten] connected with secret 1535274334053_5456

                    mqtt.0 2018-08-26 11:05:34.053 info Client [Stehlampe] connected with secret 1535274334053_4067

                    mqtt.0 2018-08-26 11:05:34.053 info Client [WonzimmerLampen] connected with secret 1535274334037_5841

                    mqtt.0 2018-08-26 11:05:34.022 info Client [Steckdose1] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:33.912 info Client [Steckdose1] connected with secret 1535274333912_8022

                    mqtt.0 2018-08-26 11:05:33.803 info Client [Annas_Lampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:33.694 info Client [Annas_Lampe] connected with secret 1535274333694_5238

                    mqtt.0 2018-08-26 11:05:33.100 info Client [Stehlampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:33.100 info Client [Unten] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:33.084 info Client [WonzimmerLampen] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:32.991 info Client [Stehlampe] connected with secret 1535274332991_1658

                    mqtt.0 2018-08-26 11:05:32.991 info Client [Unten] connected with secret 1535274332991_3474

                    mqtt.0 2018-08-26 11:05:32.975 info Client [WonzimmerLampen] connected with secret 1535274332975_4098

                    mqtt.0 2018-08-26 11:05:32.959 info Client [Steckdose1] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:32.850 info Client [Steckdose1] connected with secret 1535274332850_1625

                    mqtt.0 2018-08-26 11:05:32.741 info Client [Annas_Lampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:32.631 info Client [Annas_Lampe] connected with secret 1535274332631_221

                    mqtt.0 2018-08-26 11:05:32.022 info Client [Stehlampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:32.022 info Client [Unten] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:32.007 info Client [WonzimmerLampen] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:32.007 info Client [WonzimmerLampen] publishOnSubscribe send all known states

                    mqtt.0 2018-08-26 11:05:32.007 info Client [WonzimmerLampen] subscribes on "Wohnzimmer/Feuer/cmnd/#" with regex /^mqtt.0.Wohnzimmer.Feuer.cmnd..*/

                    mqtt.0 2018-08-26 11:05:32.007 info Client [WonzimmerLampen] subscribes on "Wohnzimmer/Feuer/cmnd/#" with regex /^Wohnzimmer.Feuer.cmnd..*/

                    mqtt.0 2018-08-26 11:05:31.913 info Client [Stehlampe] connected with secret 1535274331913_1967

                    mqtt.0 2018-08-26 11:05:31.913 info Client [Unten] connected with secret 1535274331913_5205

                    mqtt.0 2018-08-26 11:05:31.913 info Client [WonzimmerLampen] connected with secret 1535274331897_9119

                    mqtt.0 2018-08-26 11:05:31.897 info Client [Steckdose1] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:31.788 info Client [Steckdose1] connected with secret 1535274331788_2018

                    mqtt.0 2018-08-26 11:05:31.678 info Client [Annas_Lampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:31.569 info Client [Annas_Lampe] connected with secret 1535274331569_2705

                    mqtt.0 2018-08-26 11:05:30.944 info Client [Stehlampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:30.944 info Client [Unten] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:30.944 info Client [WonzimmerLampen] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:30.850 info Client [Stehlampe] connected with secret 1535274330835_5092

                    mqtt.0 2018-08-26 11:05:30.850 info Client [Unten] connected with secret 1535274330835_6987

                    mqtt.0 2018-08-26 11:05:30.835 info Client [WonzimmerLampen] connected with secret 1535274330835_7108

                    mqtt.0 2018-08-26 11:05:30.835 info Client [Steckdose1] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:30.726 info Client [Steckdose1] connected with secret 1535274330726_5363

                    mqtt.0 2018-08-26 11:05:30.616 info Client [Annas_Lampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:30.507 info Client [Annas_Lampe] connected with secret 1535274330507_7549

                    mqtt.0 2018-08-26 11:05:29.882 info Client [Unten] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:29.882 info Client [Stehlampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:29.866 info Client [WonzimmerLampen] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:29.773 info Client [Unten] connected with secret 1535274329773_8056

                    mqtt.0 2018-08-26 11:05:29.773 info Client [Stehlampe] connected with secret 1535274329773_9720

                    mqtt.0 2018-08-26 11:05:29.757 info Client [WonzimmerLampen] connected with secret 1535274329757_7690

                    mqtt.0 2018-08-26 11:05:29.757 info Client [Steckdose1] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:29.663 info Client [Steckdose1] connected with secret 1535274329663_860

                    mqtt.0 2018-08-26 11:05:29.554 info Client [Annas_Lampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:29.445 info Client [Annas_Lampe] connected with secret 1535274329445_2552

                    mqtt.0 2018-08-26 11:05:28.820 info Client [Unten] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:28.820 info Client [Stehlampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:28.804 info Client [WonzimmerLampen] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:28.710 info Client [Unten] connected with secret 1535274328695_1957

                    mqtt.0 2018-08-26 11:05:28.710 info Client [Stehlampe] connected with secret 1535274328695_6746

                    mqtt.0 2018-08-26 11:05:28.695 info Client [Steckdose1] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:28.679 info Client [WonzimmerLampen] connected with secret 1535274328679_9824

                    mqtt.0 2018-08-26 11:05:28.585 info Client [Steckdose1] connected with secret 1535274328585_6903

                    mqtt.0 2018-08-26 11:05:28.492 info Client [Annas_Lampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:28.382 info Client [Annas_Lampe] connected with secret 1535274328382_676

                    mqtt.0 2018-08-26 11:05:27.742 info Client [Unten] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:27.726 info Client [Stehlampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:27.726 info Client [WonzimmerLampen] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:27.633 info Client [Unten] connected with secret 1535274327633_8196

                    mqtt.0 2018-08-26 11:05:27.633 info Client [Steckdose1] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:27.617 info Client [Stehlampe] connected with secret 1535274327617_5875

                    mqtt.0 2018-08-26 11:05:27.601 info Client [WonzimmerLampen] connected with secret 1535274327601_846

                    mqtt.0 2018-08-26 11:05:27.523 info Client [Steckdose1] connected with secret 1535274327523_9456

                    mqtt.0 2018-08-26 11:05:27.429 info Client [Annas_Lampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:27.320 info Client [Annas_Lampe] connected with secret 1535274327320_1914

                    mqtt.0 2018-08-26 11:05:26.680 info Client [Unten] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:26.664 info Client [Stehlampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:26.648 info Client [WonzimmerLampen] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:26.570 info Client [Unten] connected with secret 1535274326570_9395

                    mqtt.0 2018-08-26 11:05:26.570 info Client [Steckdose1] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:26.539 info Client [Stehlampe] connected with secret 1535274326539_9161

                    mqtt.0 2018-08-26 11:05:26.539 info Client [WonzimmerLampen] connected with secret 1535274326539_6805

                    mqtt.0 2018-08-26 11:05:26.461 info Client [Steckdose1] connected with secret 1535274326461_2090

                    mqtt.0 2018-08-26 11:05:26.367 info Client [Annas_Lampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:26.258 info Client [Annas_Lampe] connected with secret 1535274326258_5660

                    mqtt.0 2018-08-26 11:05:25.617 info Client [Unten] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:25.571 info Client [Stehlampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:25.571 info Client [WonzimmerLampen] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:25.508 info Client [Unten] connected with secret 1535274325508_6651

                    mqtt.0 2018-08-26 11:05:25.492 info Client [Steckdose1] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:25.492 info Client [Steckdose1] publishOnSubscribe send all known states

                    mqtt.0 2018-08-26 11:05:25.492 info Client [Steckdose1] subscribes on "Sonstige/Steckdose1/cmnd/#" with regex /^mqtt.0.Sonstige.Steckdose1.cmnd..*/

                    mqtt.0 2018-08-26 11:05:25.492 info Client [Steckdose1] subscribes on "Sonstige/Steckdose1/cmnd/#" with regex /^Sonstige.Steckdose1.cmnd..*/

                    mqtt.0 2018-08-26 11:05:25.461 info Client [Stehlampe] connected with secret 1535274325461_5633

                    mqtt.0 2018-08-26 11:05:25.461 info Client [WonzimmerLampen] connected with secret 1535274325461_6852

                    mqtt.0 2018-08-26 11:05:25.399 info Client [Steckdose1] connected with secret 1535274325399_3910

                    mqtt.0 2018-08-26 11:05:25.305 info Client [Annas_Lampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:25.196 info Client [Annas_Lampe] connected with secret 1535274325196_1673

                    mqtt.0 2018-08-26 11:05:24.555 info Client [Unten] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:24.493 info Client [Stehlampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:24.493 info Client [WonzimmerLampen] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:24.430 info Client [Unten] connected with secret 1535274324430_3064

                    mqtt.0 2018-08-26 11:05:24.430 info Client [Steckdose1] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:24.368 info Client [Stehlampe] connected with secret 1535274324368_6894

                    mqtt.0 2018-08-26 11:05:24.368 info Client [WonzimmerLampen] connected with secret 1535274324368_7250

                    mqtt.0 2018-08-26 11:05:24.321 info Client [Steckdose1] connected with secret 1535274324321_5212

                    mqtt.0 2018-08-26 11:05:24.243 info Client [Annas_Lampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:24.133 info Client [Annas_Lampe] connected with secret 1535274324133_9919

                    mqtt.0 2018-08-26 11:05:23.477 info Client [Unten] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:23.415 info Client [Stehlampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:23.415 info Client [WonzimmerLampen] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:23.368 info Client [Unten] connected with secret 1535274323368_381

                    mqtt.0 2018-08-26 11:05:23.368 info Client [Steckdose1] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:23.305 info Client [Stehlampe] connected with secret 1535274323305_8519

                    mqtt.0 2018-08-26 11:05:23.305 info Client [WonzimmerLampen] connected with secret 1535274323305_2688

                    mqtt.0 2018-08-26 11:05:23.243 info Client [Steckdose1] connected with secret 1535274323243_5154

                    mqtt.0 2018-08-26 11:05:23.180 info Client [Annas_Lampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:23.071 info Client [Annas_Lampe] connected with secret 1535274323071_5931

                    mqtt.0 2018-08-26 11:05:22.399 info Client [Unten] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:22.399 info Client [Unten] publishOnSubscribe send all known states

                    mqtt.0 2018-08-26 11:05:22.399 info Client [Unten] subscribes on "Unten/Küche/cmnd/#" with regex /^mqtt.0.Unten.Küche.cmnd..*/

                    mqtt.0 2018-08-26 11:05:22.399 info Client [Unten] subscribes on "Unten/Küche/cmnd/#" with regex /^Unten.Küche.cmnd..*/

                    mqtt.0 2018-08-26 11:05:22.337 info Client [Stehlampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:22.337 info Client [WonzimmerLampen] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:22.290 info Client [Unten] connected with secret 1535274322290_3193

                    mqtt.0 2018-08-26 11:05:22.290 info Client [Steckdose1] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:22.227 info Client [Stehlampe] connected with secret 1535274322227_552

                    mqtt.0 2018-08-26 11:05:22.227 info Client [WonzimmerLampen] connected with secret 1535274322212_6333

                    mqtt.0 2018-08-26 11:05:22.180 info Client [Steckdose1] connected with secret 1535274322165_2426

                    mqtt.0 2018-08-26 11:05:22.118 info Client [Annas_Lampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:22.009 info Client [Annas_Lampe] connected with secret 1535274322009_2174

                    mqtt.0 2018-08-26 11:05:21.337 info Client [Unten] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:21.259 info Client [Stehlampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:21.259 info Client [WonzimmerLampen] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:21.228 info Client [Unten] connected with secret 1535274321228_1540

                    mqtt.0 2018-08-26 11:05:21.212 info Client [Steckdose1] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:21.150 info Client [Stehlampe] connected with secret 1535274321150_8110

                    mqtt.0 2018-08-26 11:05:21.150 info Client [WonzimmerLampen] connected with secret 1535274321150_7557

                    mqtt.0 2018-08-26 11:05:21.103 info Client [Steckdose1] connected with secret 1535274321103_4247

                    mqtt.0 2018-08-26 11:05:21.056 info Client [Annas_Lampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:20.947 info Client [Annas_Lampe] connected with secret 1535274320947_2569

                    mqtt.0 2018-08-26 11:05:20.275 info Client [Unten] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:20.181 info Client [Stehlampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:20.181 info Client [WonzimmerLampen] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:20.166 info Client [Unten] connected with secret 1535274320166_7979

                    mqtt.0 2018-08-26 11:05:20.150 info Client [Steckdose1] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:20.087 info Client [Stehlampe] connected with secret 1535274320087_6460

                    mqtt.0 2018-08-26 11:05:20.072 info Client [WonzimmerLampen] connected with secret 1535274320072_3335

                    mqtt.0 2018-08-26 11:05:20.040 info Client [Steckdose1] connected with secret 1535274320040_5554

                    mqtt.0 2018-08-26 11:05:19.994 info Client [Annas_Lampe] connection closed: Error: Invalid messageId

                    mqtt.0 2018-08-26 11:05:19.884 info Client [Annas_Lampe] connected with secret 1535274319884_8684

                    mqtt.0 2018-08-26 11:03:48.091 info Client [Raspi] connected with secret 1535274228091_5017

                    mqtt.0 2018-08-26 11:03:43.858 info Client [Raspi] connection closed: disconnected

                    mqtt.0 2018-08-26 11:03:02.773 info Client [Raspi] connected with secret 1535274182773_5732

                    mqtt.0 2018-08-26 11:02:37.154 info Client [Unten] publishOnSubscribe send all known states

                    mqtt.0 2018-08-26 11:02:37.154 info Client [Unten] subscribes on "Unten/Küche/cmnd/#" with regex /^mqtt.0.Unten.Küche.cmnd..*/

                    mqtt.0 2018-08-26 11:02:37.154 info Client [Unten] subscribes on "Unten/Küche/cmnd/#" with regex /^Unten.Küche.cmnd..*/

                    mqtt.0 2018-08-26 11:02:37.044 info Client [Unten] connected with secret 1535274157044_2630

                    mqtt.0 2018-08-26 11:02:37.013 info Client [Stehlampe] publishOnSubscribe send all known states

                    mqtt.0 2018-08-26 11:02:37.013 info Client [Stehlampe] subscribes on "Wohnzimmer/Stehlampe/cmnd/#" with regex /^mqtt.0.Wohnzimmer.Stehlampe.cmnd..*/

                    mqtt.0 2018-08-26 11:02:37.013 info Client [Stehlampe] subscribes on "Wohnzimmer/Stehlampe/cmnd/#" with regex /^Wohnzimmer.Stehlampe.cmnd..*/

                    mqtt.0 2018-08-26 11:02:36.966 info Client [Steckdose1] publishOnSubscribe send all known states

                    mqtt.0 2018-08-26 11:02:36.966 info Client [Steckdose1] subscribes on "Sonstige/Steckdose1/cmnd/#" with regex /^mqtt.0.Sonstige.Steckdose1.cmnd..*/

                    mqtt.0 2018-08-26 11:02:36.966 info Client [Steckdose1] subscribes on "Sonstige/Steckdose1/cmnd/#" with regex /^Sonstige.Steckdose1.cmnd..*/

                    mqtt.0 2018-08-26 11:02:36.935 info Client [Annas_Lampe] publishOnSubscribe send all known states

                    mqtt.0 2018-08-26 11:02:36.935 info Client [Annas_Lampe] subscribes on "Annas/Annas_Lampe/cmnd/#" with regex /^mqtt.0.Annas.Annas_Lampe.cmnd..*/

                    mqtt.0 2018-08-26 11:02:36.935 info Client [Annas_Lampe] subscribes on "Annas/Annas_Lampe/cmnd/#" with regex /^Annas.Annas_Lampe.cmnd..*/

                    mqtt.0 2018-08-26 11:02:36.904 info Client [Stehlampe] connected with secret 1535274156904_8120

                    mqtt.0 2018-08-26 11:02:36.888 info Client [WonzimmerLampen] publishOnSubscribe send all known states

                    mqtt.0 2018-08-26 11:02:36.888 info Client [WonzimmerLampen] subscribes on "Wohnzimmer/Feuer/cmnd/#" with regex /^mqtt.0.Wohnzimmer.Feuer.cmnd..*/

                    mqtt.0 2018-08-26 11:02:36.888 info Client [WonzimmerLampen] subscribes on "Wohnzimmer/Feuer/cmnd/#" with regex /^Wohnzimmer.Feuer.cmnd..*/

                    mqtt.0 2018-08-26 11:02:36.825 info Client [Annas_Lampe] connected with secret 1535274156763_4598

                    mqtt.0 2018-08-26 11:02:36.825 info Client [Steckdose1] connected with secret 1535274156763_306

                    mqtt.0 2018-08-26 11:02:36.653 info Client [WonzimmerLampen] connected with secret 1535274156653_3341

                    mqtt.0 2018-08-26 11:02:36.403 info Starting MQTT ' authenticated server on port 1883

                    mqtt.0 2018-08-26 11:02:36.247 info starting. Version 2.0.3 in C:/ioBroker/node_modules/iobroker.mqtt, node: v8.11.4

                    host.Server 2018-08-26 11:02:35.280 info instance system.adapter.mqtt.0 started with pid 1444

                    host.Server 2018-08-26 11:02:32.780 info instance system.adapter.mqtt.0 terminated with code null ()

                    Bei den Events hab ich nix auffälliges gefunden…

                    Was meint der mit "connection closed: Error: Invalid messageId"

                    Wenn ich danach google finde ich nur das hier: viewtopic.php?f=20&t=16349

                    Hat Sonst jemand eine Idee?

                    Danke

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

                      Ich habe das selbe Problem, betrifft nur MQTT Clients. Nach einiger Zeit: "connection closed: Error: Invalid messageId" in den Logs.

                      NPM 6.4.1

                      Node 8.12.0

                      Raspi 3 Image.

                      Edit: Nach einem Reload des MQTT Adapters tut es wieder für einige Zeit.

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

                        das geht vom client aus .. der geht in standby.. welche Tasmota Version hast du drauf ??

                        es gibt eine Einstellung am Client um Energie zu sparen.. die mukt ab und an

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

                          Tasmota v6.2.1

                          Es betrifft allerdings auch EasyESP Geräte mit R120, selbe Meldung.

                          1 Reply Last reply Reply Quote 0
                          • M
                            Mazdaracer121 last edited by

                            Bei mir aktuell genau das gleiche… Gibt's schon Lösungsansatz?

                            1 Reply Last reply Reply Quote 0
                            • N
                              nox last edited by

                              Bei mir das gleiche.

                              Wird der Adapter neu gestartet, ist wieder eine ganze Weile ruhe.

                              1 Reply Last reply Reply Quote 0
                              • P
                                polocup100 last edited by

                                Hallo,

                                ich habe ebanfalls das Problem mit "invalid Message ID"

                                Vorwiegend bei den kürzlich hinzugefügten Sonoffs. Dabei spielt es keine Rolle ob 5.11.1 oder 6.3.0, auch deutsch oder englisch mach Firmwaretechnisch keinen Unterschied.

                                Sleepmode ist auch deaktiviert.

                                Manchmal sind es nur 2, mancmal 4 oder mehr Clients.

                                Ich habe die Fulltopic wie folgt geändert : %topic%/%prefix%/

                                Das sollte aber doch nichts machen oder?

                                Habe erstmal ein Script erstellt, dass bei mehr als 50 "connection" Aktualiesierungen pro Minute, den MQTT Adapter neustartet.

                                Aber das sollte ja kein Dauerzustand sein.

                                Hat schon jemand eine Lösung gefunden?

                                VG Sascha

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

                                  Moin,

                                  ich hänge mich hier mal mit dran, da ich das gleiche Problem habe. Manchmal nach ein paar Tagen, manchmal nach zwei oder drei Wochen zickt der MQTT Adapter rum:

                                  <size size="85">2018-12-28 16:15:27.803 - [32minfo[39m: javascript.0 script.js.common.KatzenhausSensor: [object Object]

                                  2018-12-28 16:20:27.799 - [32minfo[39m: javascript.0 script.js.common.KatzenhausSensor: [object Object]

                                  2018-12-28 16:25:27.808 - [32minfo[39m: javascript.0 script.js.common.KatzenhausSensor: [object Object]

                                  2018-12-28 16:26:19.990 - [32minfo[39m: mqtt.0 Client [Bambus] connection closed: Error: read EHOSTUNREACH

                                  2018-12-28 16:26:23.564 - [32minfo[39m: mqtt.0 Client [Switsch1] connection closed: Error: Invalid messageId

                                  2018-12-28 16:26:24.278 - [32minfo[39m: mqtt.0 Client [Switsch1] connected with secret 1546010784278_6005

                                  2018-12-28 16:26:24.335 - [32minfo[39m: mqtt.0 Client [Switsch1] subscribes on "cmnd/switch1/#" with regex /^cmnd.switch1..*/

                                  2018-12-28 16:26:24.335 - [32minfo[39m: mqtt.0 Client [Switsch1] subscribes on "cmnd/switch1/#" with regex /^mqtt.0.cmnd.switch1..*/

                                  2018-12-28 16:26:24.335 - [32minfo[39m: mqtt.0 Client [Switsch1] publishOnSubscribe send all known states

                                  2018-12-28 16:26:24.380 - [32minfo[39m: mqtt.0 Client [Switsch1] connection closed: Error: Invalid messageId</size>

                                  Nach einem neustart des Adapters ist wieder alles OK. Die MQTT Clients sind überwiegend Sonoff-Tasmota Devices aber auch ein paar selbstgebaute Geräte mit der passenden Arduino ESP Library ( <esp8266wifi.h>& <pubsubclient.h>)

                                  Die liefen aber so wie sie sind sehr lange mit einem Cloud MQTT Broker und Home Automation.

                                  Den MQTT Adapter habe ich auf dem aktuellen stand….das Verhalten hat sich aber auch nicht verändert über die letzen Versionen.

                                  Node v6.14.3

                                  Ist eine Docker Image

                                  ioBroker läuft dort unter einem Alpine Linux 3.4

                                  WAS genau ist die messageID?

                                  Kann man sich anzeigen lassen was er hat/bekommt und was erwartet wird?

                                  Jemand eine Idee, bzw. wie kann ich helfen den "fehler" zu finden?

                                  Gruss</pubsubclient.h></esp8266wifi.h>

                                  1 Reply Last reply Reply Quote 0
                                  • F
                                    Fischler last edited by

                                    Es liegt an den Clients. Im Tasmota-Wiki ist beschrieben wie man die Prefixe richtig verwendet.

                                    https://github.com/arendst/Sonoff-Tasmo … T-Features

                                    MQTT Topic definition

                                    Until version 5.0.5 the MQTT topic was defined rigidly by using the commands Prefix <x>and Topic resulting in a command topic string like cmnd/sonoff/Power.

                                    Starting with version 5.0.5 the MQTT topic is more flexible using command FullTopic and tokens to be placed within the user definable string up to 100 characters in size. The provided tokens are:

                                    %prefix% to be dynamically substituted by one of three prefixes as defined by commands Prefix1 (default: "cmnd"), Prefix2 (default: "stat") and Prefix3 (default: "tele").

                                    %topic% to be dynamically substituted by one of five topics as defined by commands Topic, GroupTopic, ButtonTopic, SwitchTopic and MqttClient.

                                    Using the tokens the following example topics can be made:

                                    FullTopic %prefix%/%topic%/ being the legacy situation up to version 5.0.5

                                    FullTopic tasmota/%topic%/%prefix%/

                                    FullTopic tasmota/bedroom/%topic%/%prefix%/

                                    FullTopic penthouse/bedroom1/bathroom2/%topic%/%prefix%/

                                    To solve possible MQTT topic loops I strongly suggest to use the %prefix% token in all of your FullTopics. It may work without %prefix% as I implemented some validation by forcing the use of a prefix in commands send to the device but status and telemetry do not need a prefix. Just play with it and report strange problems I might solve in the future.

                                    The use of the %topic% token is also mandatory in case you want to use ButtonTopic and/or SwitchTopic. It also provides for grouptopic and fallback topic functionality.

                                    <size size="150">Recommendation: Use both tokens at all time within your FullTopic string</size></x>

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

                                      Hi,

                                      ich benutze Topic und prefix wie angegeben:

                                      ![](</s><ATTACHMENT 4300_mqtt.jpg )[attachment=0]~~MQTT.JPG[/attachment]" />

                                      Sieht man auch im Log, oder meinst du noch was anderes?

                                      Wie gesagt das passiert NICHT nur mit Tasmota Clients.

                                      Gruss~~

                                      1 Reply Last reply Reply Quote 0
                                      • R
                                        romgen last edited by

                                        Ich habe das gleiche Problem mit dem MQTT Adapter, auch mehrfach täglich.

                                        Mein FullTopic ist einfach nur einfach "%prefix%/%topic%", wie auch bei Tasmota vorgegeben.

                                        Ein Neustart des Adapter löst das Problem meistens. Vielleicht kann ich ja selbst helfen.

                                        Leider konnte ich noch nicht herausfinden welche MQTT Message jetzt eigentlich das Problem ist.

                                        Update:

                                        Dank eines alten Post von Bluefox (mit Tipps zum Debuggen) komme ich weiter.

                                        Hier ein output mit debug enabled, trace kommt später:

                                        2018-12-31 01:47:03.286  - info: mqtt.0 Client [DVES_6B3BFF] connected with secret 1546217223283_4092
                                        2018-12-31 01:47:03.290  - debug: mqtt.0 stateChange mqtt.0.info.connection: {"val":"DVES_9C67D9,DVES_6B3BFF","ack":true,"ts":1546217223287,"q":0,"from":"system.adapter.mqtt.0","lc":1546217223287}
                                        2018-12-31 01:47:03.297  - debug: mqtt.0 stateChange mqtt.0.tele.sonoff3.LWT: {"val":"Online","ack":true,"ts":1546217223296,"q":0,"from":"system.adapter.mqtt.0","lc":1546217223296}
                                        2018-12-31 01:47:03.343  - info: mqtt.0 Client [DVES_6B3BFF] subscribes on "cmnd/sonoff3/#" with regex /^cmnd\.sonoff3\..*/
                                        2018-12-31 01:47:03.343  - info: mqtt.0 Client [DVES_6B3BFF] subscribes on "cmnd/sonoff3/#"  with regex /^mqtt\.0\.cmnd\.sonoff3\..*/
                                        2018-12-31 01:47:03.343  - info: mqtt.0 Client [DVES_6B3BFF] publishOnSubscribe send all known states
                                        2018-12-31 01:47:03.343  - info: mqtt.0 Client [DVES_6B3BFF] subscribes on "cmnd/sonoffs/#" with regex /^cmnd\.sonoffs\..*/
                                        2018-12-31 01:47:03.344  - info: mqtt.0 Client [DVES_6B3BFF] subscribes on "cmnd/sonoffs/#"  with regex /^mqtt\.0\.cmnd\.sonoffs\..*/
                                        2018-12-31 01:47:03.344  - info: mqtt.0 Client [DVES_6B3BFF] publishOnSubscribe send all known states
                                        2018-12-31 01:47:03.344  - info: mqtt.0 Client [DVES_6B3BFF] subscribes on "cmnd/DVES_6B3BFF_fb/#" with regex /^cmnd\.DVES_6B3BFF_fb\..*/
                                        2018-12-31 01:47:03.344  - info: mqtt.0 Client [DVES_6B3BFF] subscribes on "cmnd/DVES_6B3BFF_fb/#"  with regex /^mqtt\.0\.cmnd\.DVES_6B3BFF_fb\..*/
                                        2018-12-31 01:47:03.344  - info: mqtt.0 Client [DVES_6B3BFF] publishOnSubscribe send all known states
                                        2018-12-31 01:47:03.344  - debug: mqtt.0 stateChange mqtt.0.cmnd.sonoff3.POWER: {"val":"","ack":true,"ts":1546217223342,"q":0,"from":"system.adapter.mqtt.0","lc":1546211354064}
                                        2018-12-31 01:47:03.371  - debug: mqtt.0 stateChange mqtt.0.stat.sonoff3.RESULT: {"val":"{\"POWER\":\"ON\"}","ack":true,"ts":1546217223370,"q":0,"from":"system.adapter.mqtt.0","lc":1546183229931}
                                        2018-12-31 01:47:03.389  - debug: mqtt.0 Client [DVES_6B3BFF] Resend messages on connect: tele/sonoff1/LWT = [object Object]
                                        2018-12-31 01:47:03.389  - info: mqtt.0 Client [DVES_6B3BFF] connection closed: Error: Invalid messageId
                                        2018-12-31 01:47:03.397  - debug: mqtt.0 stateChange mqtt.0.info.connection: {"val":"DVES_9C67D9","ack":true,"ts":1546217223390,"q":0,"from":"system.adapter.mqtt.0","lc":1546217223390}
                                        2018-12-31 01:47:03.399  - debug: mqtt.0 stateChange mqtt.0.tele.sonoff3.LWT: {"val":"[object Object]","ack":true,"ts":1546217223398,"q":0,"from":"system.adapter.mqtt.0","lc":1546217223398}
                                        2018-12-31 01:47:03.407  - debug: mqtt.0 Client [DVES_6B3BFF] Resend messages on connect: tele/sonoff2/LWT = [object Object]
                                        2018-12-31 01:47:03.417  - debug: mqtt.0 Client [DVES_6B3BFF] Resend messages on connect: tele/sonoff1/LWT = [object Object]
                                        2018-12-31 01:47:03.427  - debug: mqtt.0 Client [DVES_6B3BFF] Resend messages on connect: tele/sonoff2/LWT = [object Object]
                                        

                                        Update2:

                                        Ok, Ich glaube, dass ich den Fehler gefunden habe.

                                        Und zwar kommt iobroker / mqtt nicht damit klar, wenn der client ein LWT message-topic mit einem "object" payload schickt. Im Falle von Tasmota ist der "LWT" = '{"POWER":"ON"}' (bzw OFF).

                                        Für alle interessierten: Ich habe mal einen Bug report aufgemacht. https://github.com/ioBroker/ioBroker.mqtt/issues/31

                                        romgen created this issue in ioBroker/ioBroker.mqtt

                                        closed MQTT Adapter "Invalid messageId" (possible reason inside) #31

                                        1 Reply Last reply Reply Quote 0
                                        • F
                                          Fischler last edited by

                                          Ich habe Tasmota Version 6.4.1 installiert und es läuft mittlerweile ohne Probleme.

                                          Laut dem Debug scheint das Prefix und Topic noch vertauscht zu sein.

                                          > stateChange mqtt.0.cmnd.sonoff3.POWER

                                          richtig wäre allerdings:

                                          > stateChange mqtt.0.sonoff3.cmnd.POWER

                                          Postet doch mal das gesamte "aufgeklappte" Objekt <u>eines</u> Sonoff-Devices und die Infoseite von dem Sonoff-Device Hauptmenü -> Informationen

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

                                            Hi,

                                            Warum soll das eine “richtig” und das andere “falsch” sein?

                                            Laut beschreibung sind beide varianten gültig.

                                            Ich kann mir auch schlecht vorstellen dass das Problem so trivial ist….mein letzter Neustart war am 28.12,

                                            Seitdem läuft wieder alles ohne Problem.....mit 10 mqtt Clients, welche auch benutzt werden.

                                            Es währe spannend zu sehen ob es User gubt die auch cmnd.NAME.Power etc benutzen aber trotzdem keine Probleme haben.

                                            Gruss

                                            Sky

                                            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

                                            419
                                            Online

                                            31.9k
                                            Users

                                            80.1k
                                            Topics

                                            1.3m
                                            Posts

                                            20
                                            39
                                            7764
                                            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