Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. [Adapter] Sonoff- Tasmota

    NEWS

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    [Adapter] Sonoff- Tasmota

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

      @DrFirebird:

      @ noxx

      bei mir liefert der DS18B20 überhaupt keine Daten … auch nicht auf der Tasmota Konsole.

      Der DHT22 wiederum, funktioniert einwandfrei.

      Eine Idee, was ich falsch mache ?

      tele/sonoff/SENSOR = {"Time":"2017-10-06T20:18:50", "DHT22":{"Temperature":23.2, "Humidity":59.9}, "TempUnit":"C"}
      ```` `  
      

      evtl…..Den DTH22 was auch bei Dir funktioniert, steckst Du auf VCC,GND und GPIO14

      Ein DS18B20 braucht zwischen VCC und Datenteiltnung ein 4k7 Ohm, und den hast Du nicht eingebaut, richtig? :mrgreen:

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

        @ Bluefox

        Danke für das Hinzufügen des ESP.

        Habe mir den Code dafür angesehen blicke da aber leider nicht mehr so ganz durch.

        Ich habe aber die Vermutung das wir mit dem ESP Probleme bekommen könnten.

        Ich vermute das du hier nach BM280 oder Pressure oder Humidity suchst?

        Ich habe mal ein Bild angehangen. Diese Namen sind frei wählbar. Wenn einer diese anders nennt wird es wohl nicht mehr funktionieren.

        Falls du im Bezug auf den ESP Interesse an mehr Daten hast ich hätte noch viel viel mehr Sensoren dafür da. Wenn meine Vermutung oben zutrifft wäre es dann nicht sinnvoll einen neuen Adapter zu machen? Dann könnte ich für meine ganzen Sachen ne Doku schreiben.
        2343_esp.png

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

          @DrFirebird:

          @ noxx

          bei mir liefert der DS18B20 überhaupt keine Daten … auch nicht auf der Tasmota Konsole.

          Der DHT22 wiederum, funktioniert einwandfrei.

          Eine Idee, was ich falsch mache ?

          tele/sonoff/SENSOR = {"Time":"2017-10-06T20:18:50", "DHT22":{"Temperature":23.2, "Humidity":59.9}, "TempUnit":"C"}
          ```` `  
          

          Wie knopers1 schon schrieb, der Widerstand fehlt vermutlich, ohne dem kommt nix

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

            Schade. Port ändern hat nichts gebracht. Bekomme keine stabile Verbindung hin.

            sonoff.0	2017-10-07 13:22:48.057	debug	Client [DVES_077E54] pingreq
            sonoff.0	2017-10-07 13:22:48.032	debug	Client [DVES_077E9B] pingreq
            sonoff.0	2017-10-07 13:22:43.986	debug	stateChange sonoff.0.DVES_077E54.POWER: {"val":true,"ack":true,"ts":1507375363978,"q":0,"from":"system.adapter.sonoff.0","lc":1507375254245}
            sonoff.0	2017-10-07 13:22:43.981	debug	stateChange sonoff.0.DVES_077E54.RSSI: {"val":36,"ack":true,"ts":1507375363976,"q":0,"from":"system.adapter.sonoff.0","lc":1507375051487}
            sonoff.0	2017-10-07 13:22:43.978	debug	stateChange sonoff.0.DVES_077E54.Vcc: {"val":3.156,"ack":true,"ts":1507375363971,"q":0,"from":"system.adapter.sonoff.0","lc":1507375051478}
            sonoff.0	2017-10-07 13:22:43.972	debug	[DVES_077E54] Received: tele/sonoff03/STATE = {"Time":"2017-10-07T12:22:43", "Uptime":17, "Vcc":3.156, "POWER":"ON", "Wifi":{"AP":1, "SSID":"XXXXXX", "RSSI":36, "APMac":"F2:9F:C2:F7:XX:XX"}}
            sonoff.0	2017-10-07 13:22:35.185	debug	stateChange sonoff.0.DVES_077E9B.POWER: {"val":false,"ack":true,"ts":1507375355164,"q":0,"from":"system.adapter.sonoff.0","lc":1507321006509}
            sonoff.0	2017-10-07 13:22:35.185	debug	stateChange sonoff.0.DVES_077E9B.RSSI: {"val":64,"ack":true,"ts":1507375355164,"q":0,"from":"system.adapter.sonoff.0","lc":1507375355164}
            sonoff.0	2017-10-07 13:22:35.183	debug	stateChange sonoff.0.DVES_077E9B.Vcc: {"val":3.213,"ack":true,"ts":1507375355161,"q":0,"from":"system.adapter.sonoff.0","lc":1507375355161}
            sonoff.0	2017-10-07 13:22:35.156	debug	[DVES_077E9B] Received: tele/sonoff_Zirkulation/STATE = {"Time":"2017-10-07T12:22:35", "Uptime":17, "Vcc":3.213, "POWER":"OFF", "Wifi":{"AP":1, "SSID":"XXXXXXX", "RSSI":64, "APMac":"F2:9F:C2:F7:XX:XX
            sonoff.0	2017-10-07 13:22:33.796	debug	Client [DVES_077E54] pingreq
            sonoff.0	2017-10-07 13:22:32.985	debug	Client [DVES_077E9B] pingreq
            sonoff.0	2017-10-07 13:22:18.056	debug	Client [DVES_077E54] pingreq
            sonoff.0	2017-10-07 13:22:17.985	debug	Client [DVES_077E9B] pingreq
            sonoff.0	2017-10-07 13:22:03.093	debug	Client [DVES_077E54] pingreq
            sonoff.0	2017-10-07 13:22:03.088	debug	Client [DVES_077E9B] pingreq
            sonoff.0	2017-10-07 13:21:47.955	debug	stateChange sonoff.0.DVES_077E54.alive: {"val":true,"ack":true,"ts":1507375307948,"q":0,"from":"system.adapter.sonoff.0","lc":1507375307946}
            sonoff.0	2017-10-07 13:21:47.953	debug	stateChange sonoff.0.DVES_077E54.alive: {"val":true,"ack":true,"ts":1507375307946,"q":0,"from":"system.adapter.sonoff.0","lc":1507375307946}
            sonoff.0	2017-10-07 13:21:47.941	debug	[DVES_077E54] Received: cmnd/sonoff03/POWER =
            sonoff.0	2017-10-07 13:21:45.387	debug	stateChange sonoff.0.info.connection: {"val":"DVES_077E9B,DVES_077E54","ack":true,"ts":1507375305378,"q":0,"from":"system.adapter.sonoff.0","lc":1507375305378}
            sonoff.0	2017-10-07 13:21:45.380	info	Client [DVES_077E54] connected
            sonoff.0	2017-10-07 13:21:44.420	debug	[DVES_077E9B] Received: cmnd/sonoff_Zirkulation/POWER =
            sonoff.0	2017-10-07 13:21:43.050	debug	stateChange sonoff.0.DVES_077E9B.alive: {"val":true,"ack":true,"ts":1507375303042,"q":0,"from":"system.adapter.sonoff.0","lc":1507375303042}
            sonoff.0	2017-10-07 13:21:42.799	debug	stateChange sonoff.0.info.connection: {"val":"DVES_077E9B","ack":true,"ts":1507375302792,"q":0,"from":"system.adapter.sonoff.0","lc":1507375302792}
            sonoff.0	2017-10-07 13:21:42.666	info	Client [DVES_077E9B] connected
            sonoff.0	2017-10-07 13:21:30.134	debug	stateChange sonoff.0.DVES_077E54.alive: {"val":false,"ack":true,"ts":1507375290129,"q":0,"from":"system.adapter.sonoff.0","lc":1507375290129}
            sonoff.0	2017-10-07 13:21:30.134	debug	stateChange sonoff.0.DVES_077E9B.alive: {"val":false,"ack":true,"ts":1507375290127,"q":0,"from":"system.adapter.sonoff.0","lc":1507375290127}
            sonoff.0	2017-10-07 13:21:30.118	debug	stateChange sonoff.0.info.connection: {"val":"","ack":true,"ts":1507375290112,"q":0,"from":"system.adapter.sonoff.0","lc":1507375286454}
            sonoff.0	2017-10-07 13:21:30.096	info	Starting MQTT authenticated server on port 1885
            sonoff.0	2017-10-07 13:21:29.973	info	starting. Version 0.2.0 in /opt/iobroker/node_modules/iobroker.sonoff, node: v6.11.4
            sonoff.0	2017-10-07 13:21:29.931	debug	statesDB connected
            sonoff.0	2017-10-07 13:21:29.886	debug	objectDB connected
            sonoff.0	2017-10-07 13:21:26.459	info	terminating
            sonoff.0	2017-10-07 13:21:26.451	info	Client [DVES_077E54] closed
            sonoff.0	2017-10-07 13:21:26.451	info	Client [DVES_077E9B] closed
            sonoff.0	2017-10-07 13:21:26.450	warn	Client error [DVES_077E54]: Error: Invalid messageId
            sonoff.0	2017-10-07 13:21:26.449	info	Client [DVES_077E54] closed
            sonoff.0	2017-10-07 12:51:39.983	info	Client [DVES_077E54] connected
            sonoff.0	2017-10-07 12:51:38.168	info	Client [DVES_077E54] closed
            sonoff.0	2017-10-07 12:44:44.842	warn	Client error [DVES_077E54]: Error: Invalid messageId
            sonoff.0	2017-10-07 12:44:44.841	info	Client [DVES_077E54] closed
            sonoff.0	2017-10-07 12:44:37.707	info	Client [DVES_077E54] connected
            

            Edit: habe noch eine Änderung vorgenommen. Unter Configure MQTT habe ich Client ID geändert und zwar in die vom sonoff… vorher stand da eine andere:
            1146_unbenannt.jpg
            Edit2: hat nur 30min gehalten. Der eine hat sich wieder verabschiedet mit:

            sonoff.0	2017-10-07 13:59:18.646	warn	Client error [DVES_077E54]: Error: Invalid messageId
            
            1 Reply Last reply Reply Quote 0
            • D
              DrFirebird last edited by

              @knopers1

              @noxx

              Das wars !!!

              Kaum macht man es richtig, schon funktionierts 😄

              Vielen Dank

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

                @ lobomau

                äußerst komisch habe mehrere seit Tagen laufen und keine Probleme. Hast du die neueste Firmware drauf?

                Hast du mal probiert die Sonoff anders zu benennen? Meine heißen aktuell SonoffPOW1

                Hast du noch irgendwas spezielles eingestellt?

                Steht in der Sonoff Console was drin?

                1 Reply Last reply Reply Quote 0
                • K
                  knopers1 last edited by

                  @lomobau

                  meine Konfig sieht so aus… Läuft auch stabil!
                  1526_unbenannt1.png
                  1526_unbenann2.png

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

                    Können alle Geräte gleiches topic "sonoff" haben? Habe ich jetzt mal so eingestellt.

                    Wie ist euer rssi-Wert? Mein sonoff, der die Verbindung verliert hat einen Wert um 30 rum, der andere 58.

                    Nun habe ich den Geräten sinnvolle Namen gegeben:

                    Zirkulation,Licht_Gartenhaus	true	sonoff.0	2017-10-08 11:07:32.694	
                    Zirkulation	true	sonoff.0	2017-10-08 11:07:09.084	
                    Zirkulation,Licht_Gartenhaus	true	sonoff.0	2017-10-08 11:04:58.072	
                    Zirkulation	true	sonoff.0	2017-10-08 11:03:26.537	
                    Zirkulation,Licht_Gartenhaus	true	sonoff.0	2017-10-08 10:58:10.882	
                    Zirkulation	true	sonoff.0	2017-10-08 10:58:05.518	
                    Zirkulation,Licht_Gartenhaus	true	sonoff.0	2017-10-08 10:57:38.614	
                    Zirkulation	true	sonoff.0	2017-10-08 10:55:59.779	
                    Zirkulation,Licht_Gartenhaus	true	sonoff.0	2017-10-08 10:55:13.978	
                    Zirkulation	true	sonoff.0	2017-10-08 10:53:47.212	
                    Zirkulation,Licht_Gartenhaus	true	sonoff.0	2017-10-08 10:53:41.337	
                    Zirkulation	true	sonoff.0	2017-10-08 10:51:52.198	
                    Zirkulation,Licht_Gartenhaus	true	sonoff.0	2017-10-08 10:51:45.947	
                    Zirkulation	true	sonoff.0	2017-10-08 10:50:49.806	
                    
                    1 Reply Last reply Reply Quote 0
                    • K
                      knopers1 last edited by

                      @lobomau:

                      Können alle Geräte gleiches topic "sonoff" haben?

                      Wie ist euer rssi-Wert? `

                      meine habens… zumindest drei von 4 Geräten... RSSI Werte je nach Abstand zum Router zwischen 68-88%.

                      Mit 30% bist Du relativ weit vom Router mit dem Teil. Das könnte natürlich das Problem sein, dass die Verbindung flöten geht. Stell die Teile näher zum Router hin und beobachte paar Std. Dann kennst Du die Antwort.

                      1 Reply Last reply Reply Quote 0
                      • H
                        high_voltage last edited by

                        Hallo,

                        vielleicht könnte mir jemand verraten wie ich diese Daten (gelb markiert) im Minutentakt oder in Echtzeit akutell bekommen kann?

                        ! 3686_sonoff2.png

                        Vielen Dank und viele Grüße

                        P.S. sorry für die vielen Fragen bin noch Beginner … 🙂

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

                          nun hatte ich die Meldungen auch einmal:

                          sonoff.0	2017-10-09 08:03:12.467	info	Client [Sonoff4ch] connected
                          sonoff.0	2017-10-09 08:03:12.451	info	Client [SonoffPOW] connected
                          sonoff.0	2017-10-09 08:03:10.911	warn	Client error [SonoffPOW]: Error: Invalid messageId
                          sonoff.0	2017-10-09 08:03:10.909	info	Client [SonoffPOW] closed
                          sonoff.0	2017-10-09 08:03:10.496	warn	Client error [Sonoff4ch]: Error: Invalid messageId
                          sonoff.0	2017-10-09 08:03:10.494	info	Client [Sonoff4ch] closed
                          
                          1 Reply Last reply Reply Quote 0
                          • lobomau
                            lobomau last edited by

                            @knopers1:

                            @lobomau:

                            Können alle Geräte gleiches topic "sonoff" haben?

                            Wie ist euer rssi-Wert? `

                            meine habens… zumindest drei von 4 Geräten... RSSI Werte je nach Abstand zum Router zwischen 68-88%.

                            Mit 30% bist Du relativ weit vom Router mit dem Teil. Das könnte natürlich das Problem sein, dass die Verbindung flöten geht. Stell die Teile näher zum Router hin und beobachte paar Std. Dann kennst Du die Antwort. `
                            Zur Abwechslung hat sich nun der mit dem besseren rssi-Wert verabschiedet. Die hängen auch beide ständig am wlan. Ich glaube daran liegt es nicht.

                            Licht_Gartenhaus	true	sonoff.0	2017-10-09 10:29:29.994	
                            Zirkulation,Licht_Gartenhaus	true	sonoff.0	2017-10-08 20:58:42.382	
                            Zirkulation	true	sonoff.0	2017-10-08 20:58:41.958	
                            true	sonoff.0	2017-10-08 20:58:28.460	
                            Zirkulation,Licht_Gartenhaus	true	sonoff.0	2017-10-08 11:19:55.883	
                            Zirkulation	true	sonoff.0	2017-10-08 11:11:17.152	
                            Zirkulation	true	sonoff.0	2017-10-08 11:08:50.354
                            
                            1 Reply Last reply Reply Quote 0
                            • Bluefox
                              Bluefox last edited by

                              @kmxak:

                              nun hatte ich die Meldungen auch einmal:

                              sonoff.0	2017-10-09 08:03:12.467	info	Client [Sonoff4ch] connected
                              sonoff.0	2017-10-09 08:03:12.451	info	Client [SonoffPOW] connected
                              sonoff.0	2017-10-09 08:03:10.911	warn	Client error [SonoffPOW]: Error: Invalid messageId
                              sonoff.0	2017-10-09 08:03:10.909	info	Client [SonoffPOW] closed
                              sonoff.0	2017-10-09 08:03:10.496	warn	Client error [Sonoff4ch]: Error: Invalid messageId
                              sonoff.0	2017-10-09 08:03:10.494	info	Client [Sonoff4ch] closed
                              ```` `  
                              

                              Es gibt diese Datei:

                              ... node_modules/mqtt-packet/writeToStream.js
                              

                              entwider in /opt/iobroker oder in /opt/iobroker/node_modules/iobroker.sonoff

                              Kannst du folgende Zeilen verändern um raus zu finden, wo Fehler vorkommt?

                              https://github.com/mqttjs/mqtt-packet/b … am.js#L270

                              https://github.com/mqttjs/mqtt-packet/b ... am.js#L303

                              https://github.com/mqttjs/mqtt-packet/b ... am.js#L327

                              https://github.com/mqttjs/mqtt-packet/b ... am.js#L389

                              https://github.com/mqttjs/mqtt-packet/b ... am.js#L429

                              Auf

                              stream.emit('error', new Error('Invalid messageId ' + __line))
                              
                              1 Reply Last reply Reply Quote 0
                              • kmxak
                                kmxak Most Active last edited by

                                nachdem ich die datei geändert habe und den adapter 2 mal neugestartet habe kamen erste meldungen:

                                ! ````
                                host.ioBroker 2017-10-09 13:00:27.890 info instance system.adapter.sonoff.0 started with pid 4118
                                host.ioBroker 2017-10-09 13:00:25.507 info instance system.adapter.sonoff.0 terminated with code 0 (OK)
                                Caught 2017-10-09 13:00:25.507 error by controller[1]: at Connection.Writable.write (/opt/iobroker/node_modules/readable-stream/lib/_stream_writable.js:241:11)
                                Caught 2017-10-09 13:00:25.507 error by controller[1]: at writeOrBuffer (/opt/iobroker/node_modules/readable-stream/lib/_stream_writable.js:302:5)
                                Caught 2017-10-09 13:00:25.506 error by controller[1]: at doWrite (/opt/iobroker/node_modules/readable-stream/lib/_stream_writable.js:313:64)
                                Caught 2017-10-09 13:00:25.506 error by controller[1]: at Connection.Duplexify._write (/opt/iobroker/node_modules/duplexify/index.js:201:22)
                                Caught 2017-10-09 13:00:25.506 error by controller[1]: at Writable.write (_stream_writable.js:243:11)
                                Caught 2017-10-09 13:00:25.506 error by controller[1]: at writeOrBuffer (_stream_writable.js:317:5)
                                Caught 2017-10-09 13:00:25.506 error by controller[1]: at doWrite (_stream_writable.js:331:12)
                                Caught 2017-10-09 13:00:25.505 error by controller[1]: at Writable.write [as _write] (/opt/iobroker/node_modules/mqtt-connection/lib/writeToStream.js:10:9)
                                Caught 2017-10-09 13:00:25.505 error by controller[1]: at generate (/opt/iobroker/node_modules/mqtt-packet/writeToStream.js:33:14)
                                Caught 2017-10-09 13:00:25.505 error by controller[1]: at publish (/opt/iobroker/node_modules/mqtt-packet/writeToStream.js:270:59)
                                Caught 2017-10-09 13:00:25.505 error by controller[1]: ReferenceError: __line is not defined
                                Caught 2017-10-09 13:00:25.505 error by controller[0]: at Connection.Writable.write (/opt/iobroker/node_modules/readable-stream/lib/_stream_writable.js:241:11)
                                Caught 2017-10-09 13:00:25.505 error by controller[0]: at writeOrBuffer (/opt/iobroker/node_modules/readable-stream/lib/_stream_writable.js:302:5)
                                Caught 2017-10-09 13:00:25.505 error by controller[0]: at doWrite (/opt/iobroker/node_modules/readable-stream/lib/_stream_writable.js:313:64)
                                Caught 2017-10-09 13:00:25.504 error by controller[0]: at Connection.Duplexify._write (/opt/iobroker/node_modules/duplexify/index.js:201:22)
                                Caught 2017-10-09 13:00:25.504 error by controller[0]: at Writable.write (_stream_writable.js:243:11)
                                Caught 2017-10-09 13:00:25.504 error by controller[0]: at writeOrBuffer (_stream_writable.js:317:5)
                                Caught 2017-10-09 13:00:25.504 error by controller[0]: at doWrite (_stream_writable.js:331:12)
                                Caught 2017-10-09 13:00:25.504 error by controller[0]: at Writable.write [as _write] (/opt/iobroker/node_modules/mqtt-connection/lib/writeToStream.js:10:9)
                                Caught 2017-10-09 13:00:25.504 error by controller[0]: at generate (/opt/iobroker/node_modules/mqtt-packet/writeToStream.js:33:14)
                                Caught 2017-10-09 13:00:25.503 error by controller[0]: at publish (/opt/iobroker/node_modules/mqtt-packet/writeToStream.js:270:59)
                                Caught 2017-10-09 13:00:25.503 error by controller[0]: ReferenceError: __line is not defined
                                sonoff.0 2017-10-09 13:00:25.480 info terminating
                                sonoff.0 2017-10-09 13:00:25.466 error at Connection.Writable.write (/opt/iobroker/node_modules/readable-stream/lib/_stream_writable.js:241:11)
                                sonoff.0 2017-10-09 13:00:25.466 error at writeOrBuffer (/opt/iobroker/node_modules/readable-stream/lib/_stream_writable.js:302:5)
                                sonoff.0 2017-10-09 13:00:25.466 error at doWrite (/opt/iobroker/node_modules/readable-stream/lib/_stream_writable.js:313:64)
                                sonoff.0 2017-10-09 13:00:25.466 error at Connection.Duplexify._write (/opt/iobroker/node_modules/duplexify/index.js:201:22)
                                sonoff.0 2017-10-09 13:00:25.466 error at Writable.write (_stream_writable.js:243:11)
                                sonoff.0 2017-10-09 13:00:25.466 error at writeOrBuffer (_stream_writable.js:317:5)
                                sonoff.0 2017-10-09 13:00:25.466 error at doWrite (_stream_writable.js:331:12)
                                sonoff.0 2017-10-09 13:00:25.466 error at Writable.write [as _write] (/opt/iobroker/node_modules/mqtt-connection/lib/writeToStream.js:10:9)
                                sonoff.0 2017-10-09 13:00:25.466 error at generate (/opt/iobroker/node_modules/mqtt-packet/writeToStream.js:33:14)
                                sonoff.0 2017-10-09 13:00:25.466 error at publish (/opt/iobroker/node_modules/mqtt-packet/writeToStream.js:270:59)
                                sonoff.0 2017-10-09 13:00:25.466 error ReferenceError: __line is not defined
                                sonoff.0 2017-10-09 13:00:25.466 error uncaught exception: __line is not defined
                                sonoff.0 2017-10-09 13:00:25.465 info Client [SonoffPOW] closed
                                sonoff.0 2017-10-09 13:00:25.464 info Client [Sonoff4ch] closed
                                sonoff.0 2017-10-09 13:00:25.463 warn Client error [ESPClient5]: Error: This socket is closed
                                sonoff.0 2017-10-09 13:00:25.458 info Client [ESPClient5] closed
                                sonoff.0 2017-10-09 13:00:25.458 error at Connection.Writable.write (/opt/iobroker/node_modules/readable-stream/lib/_stream_writable.js:241:11)
                                sonoff.0 2017-10-09 13:00:25.458 error at writeOrBuffer (/opt/iobroker/node_modules/readable-stream/lib/_stream_writable.js:302:5)
                                sonoff.0 2017-10-09 13:00:25.458 error at doWrite (/opt/iobroker/node_modules/readable-stream/lib/_stream_writable.js:313:64)
                                sonoff.0 2017-10-09 13:00:25.458 error at Connection.Duplexify._write (/opt/iobroker/node_modules/duplexify/index.js:201:22)
                                sonoff.0 2017-10-09 13:00:25.458 error at Writable.write (_stream_writable.js:243:11)
                                sonoff.0 2017-10-09 13:00:25.458 error at writeOrBuffer (_stream_writable.js:317:5)
                                sonoff.0 2017-10-09 13:00:25.458 error at doWrite (_stream_writable.js:331:12)
                                sonoff.0 2017-10-09 13:00:25.458 error at Writable.write [as _write] (/opt/iobroker/node_modules/mqtt-connection/lib/writeToStream.js:10:9)
                                sonoff.0 2017-10-09 13:00:25.458 error at generate (/opt/iobroker/node_modules/mqtt-packet/writeToStream.js:33:14)
                                sonoff.0 2017-10-09 13:00:25.458 error at publish (/opt/iobroker/node_modules/mqtt-packet/writeToStream.js:270:59)
                                sonoff.0 2017-10-09 13:00:25.458 error ReferenceError: __line is not defined
                                sonoff.0 2017-10-09 13:00:25.458 error uncaught exception: __line is not defined
                                sonoff.0 2017-10-09 13:00:25.427 info Client [Sonoff4ch] closed

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

                                  Hallo

                                  Wird der Sonoff S20 auch unterstützt ?

                                  Gruß

                                  Gesendet von iPad mit Tapatalk Pro

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

                                    @kmxak:

                                    nachdem ich die datei geändert habe und den adapter 2 mal neugestartet habe kamen erste meldungen:

                                    ! host.ioBroker 2017-10-09 13:00:27.890 info instance system.adapter.sonoff.0 started with pid 4118 host.ioBroker 2017-10-09 13:00:25.507 info instance system.adapter.sonoff.0 terminated with code 0 (OK) Caught 2017-10-09 13:00:25.507 error by controller[1]: at Connection.Writable.write (/opt/iobroker/node_modules/readable-stream/lib/_stream_writable.js:241:11) Caught 2017-10-09 13:00:25.507 error by controller[1]: at writeOrBuffer (/opt/iobroker/node_modules/readable-stream/lib/_stream_writable.js:302:5) Caught 2017-10-09 13:00:25.506 error by controller[1]: at doWrite (/opt/iobroker/node_modules/readable-stream/lib/_stream_writable.js:313:64) Caught 2017-10-09 13:00:25.506 error by controller[1]: at Connection.Duplexify._write (/opt/iobroker/node_modules/duplexify/index.js:201:22) Caught 2017-10-09 13:00:25.506 error by controller[1]: at Writable.write (_stream_writable.js:243:11) Caught 2017-10-09 13:00:25.506 error by controller[1]: at writeOrBuffer (_stream_writable.js:317:5) Caught 2017-10-09 13:00:25.506 error by controller[1]: at doWrite (_stream_writable.js:331:12) Caught 2017-10-09 13:00:25.505 error by controller[1]: at Writable.write [as _write] (/opt/iobroker/node_modules/mqtt-connection/lib/writeToStream.js:10:9) Caught 2017-10-09 13:00:25.505 error by controller[1]: at generate (/opt/iobroker/node_modules/mqtt-packet/writeToStream.js:33:14) Caught 2017-10-09 13:00:25.505 error by controller[1]: at publish (/opt/iobroker/node_modules/mqtt-packet/writeToStream.js:270:59) Caught 2017-10-09 13:00:25.505 error by controller[1]: ReferenceError: __line is not defined Caught 2017-10-09 13:00:25.505 error by controller[0]: at Connection.Writable.write (/opt/iobroker/node_modules/readable-stream/lib/_stream_writable.js:241:11) Caught 2017-10-09 13:00:25.505 error by controller[0]: at writeOrBuffer (/opt/iobroker/node_modules/readable-stream/lib/_stream_writable.js:302:5) Caught 2017-10-09 13:00:25.505 error by controller[0]: at doWrite (/opt/iobroker/node_modules/readable-stream/lib/_stream_writable.js:313:64) Caught 2017-10-09 13:00:25.504 error by controller[0]: at Connection.Duplexify._write (/opt/iobroker/node_modules/duplexify/index.js:201:22) Caught 2017-10-09 13:00:25.504 error by controller[0]: at Writable.write (_stream_writable.js:243:11) Caught 2017-10-09 13:00:25.504 error by controller[0]: at writeOrBuffer (_stream_writable.js:317:5) Caught 2017-10-09 13:00:25.504 error by controller[0]: at doWrite (_stream_writable.js:331:12) Caught 2017-10-09 13:00:25.504 error by controller[0]: at Writable.write [as _write] (/opt/iobroker/node_modules/mqtt-connection/lib/writeToStream.js:10:9) Caught 2017-10-09 13:00:25.504 error by controller[0]: at generate (/opt/iobroker/node_modules/mqtt-packet/writeToStream.js:33:14) Caught 2017-10-09 13:00:25.503 error by controller[0]: at publish (/opt/iobroker/node_modules/mqtt-packet/writeToStream.js:270:59) Caught 2017-10-09 13:00:25.503 error by controller[0]: ReferenceError: __line is not defined sonoff.0 2017-10-09 13:00:25.480 info terminating sonoff.0 2017-10-09 13:00:25.466 error at Connection.Writable.write (/opt/iobroker/node_modules/readable-stream/lib/_stream_writable.js:241:11) sonoff.0 2017-10-09 13:00:25.466 error at writeOrBuffer (/opt/iobroker/node_modules/readable-stream/lib/_stream_writable.js:302:5) sonoff.0 2017-10-09 13:00:25.466 error at doWrite (/opt/iobroker/node_modules/readable-stream/lib/_stream_writable.js:313:64) sonoff.0 2017-10-09 13:00:25.466 error at Connection.Duplexify._write (/opt/iobroker/node_modules/duplexify/index.js:201:22) sonoff.0 2017-10-09 13:00:25.466 error at Writable.write (_stream_writable.js:243:11) sonoff.0 2017-10-09 13:00:25.466 error at writeOrBuffer (_stream_writable.js:317:5) sonoff.0 2017-10-09 13:00:25.466 error at doWrite (_stream_writable.js:331:12) sonoff.0 2017-10-09 13:00:25.466 error at Writable.write [as _write] (/opt/iobroker/node_modules/mqtt-connection/lib/writeToStream.js:10:9) sonoff.0 2017-10-09 13:00:25.466 error at generate (/opt/iobroker/node_modules/mqtt-packet/writeToStream.js:33:14) sonoff.0 2017-10-09 13:00:25.466 error at publish (/opt/iobroker/node_modules/mqtt-packet/writeToStream.js:270:59) sonoff.0 2017-10-09 13:00:25.466 error ReferenceError: __line is not defined sonoff.0 2017-10-09 13:00:25.466 error uncaught exception: __line is not defined sonoff.0 2017-10-09 13:00:25.465 info Client [SonoffPOW] closed sonoff.0 2017-10-09 13:00:25.464 info Client [Sonoff4ch] closed sonoff.0 2017-10-09 13:00:25.463 warn Client error [ESPClient5]: Error: This socket is closed sonoff.0 2017-10-09 13:00:25.458 info Client [ESPClient5] closed sonoff.0 2017-10-09 13:00:25.458 error at Connection.Writable.write (/opt/iobroker/node_modules/readable-stream/lib/_stream_writable.js:241:11) sonoff.0 2017-10-09 13:00:25.458 error at writeOrBuffer (/opt/iobroker/node_modules/readable-stream/lib/_stream_writable.js:302:5) sonoff.0 2017-10-09 13:00:25.458 error at doWrite (/opt/iobroker/node_modules/readable-stream/lib/_stream_writable.js:313:64) sonoff.0 2017-10-09 13:00:25.458 error at Connection.Duplexify._write (/opt/iobroker/node_modules/duplexify/index.js:201:22) sonoff.0 2017-10-09 13:00:25.458 error at Writable.write (_stream_writable.js:243:11) sonoff.0 2017-10-09 13:00:25.458 error at writeOrBuffer (_stream_writable.js:317:5) sonoff.0 2017-10-09 13:00:25.458 error at doWrite (_stream_writable.js:331:12) sonoff.0 2017-10-09 13:00:25.458 error at Writable.write [as _write] (/opt/iobroker/node_modules/mqtt-connection/lib/writeToStream.js:10:9) sonoff.0 2017-10-09 13:00:25.458 error at generate (/opt/iobroker/node_modules/mqtt-packet/writeToStream.js:33:14) sonoff.0 2017-10-09 13:00:25.458 error at publish (/opt/iobroker/node_modules/mqtt-packet/writeToStream.js:270:59) sonoff.0 2017-10-09 13:00:25.458 error ReferenceError: __line is not defined sonoff.0 2017-10-09 13:00:25.458 error uncaught exception: __line is not defined sonoff.0 2017-10-09 13:00:25.427 info Client [Sonoff4ch] closed `
                                    Ist vermutlich alte node.js Version.

                                    dann ersetze __line mit unterschiedlichen Buchstaben: A, B, C,… so dass du die unterscheiden kannst.

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

                                      @chucky666:

                                      Hallo

                                      Wird der Sonoff S20 auch unterstützt ?

                                      Gruß

                                      Gesendet von iPad mit Tapatalk Pro `
                                      Keine Ahnung. Hast du probiert oder fragst du?

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

                                        Ich frage , wollte mir eine testweise bestellen

                                        Gesendet von iPad mit Tapatalk Pro

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

                                          @Bluefox:

                                          Ist vermutlich alte node.js Version.

                                          dann ersetze __line mit unterschiedlichen Buchstaben: A, B, C,… so dass du die unterscheiden kannst. `

                                          wo soll ich was ersetzen?`

                                          Die node.js ist aktuell:

                                          root@ioBroker:/home/alex# node -v
                                          v6.11.4
                                          root@ioBroker:/home/alex# nodejs -v
                                          v6.11.4
                                          
                                          
                                          1 Reply Last reply Reply Quote 0
                                          • Bluefox
                                            Bluefox last edited by

                                            @kmxak:

                                            @Bluefox:

                                            Ist vermutlich alte node.js Version.

                                            dann ersetze __line mit unterschiedlichen Buchstaben: A, B, C,… so dass du die unterscheiden kannst. `

                                            wo soll ich was ersetzen?`

                                            Die node.js ist aktuell:

                                            root@ioBroker:/home/alex# node -v
                                            v6.11.4
                                            root@ioBroker:/home/alex# nodejs -v
                                            v6.11.4
                                            
                                            ```` `  
                                            
                                            stream.emit('error', new Error('Invalid messageId ' + __line))
                                            

                                            =>

                                            stream.emit('error', new Error('Invalid messageId A'))
                                            
                                            stream.emit('error', new Error('Invalid messageId B'))
                                            
                                            stream.emit('error', new Error('Invalid messageId C'))
                                            
                                            stream.emit('error', new Error('Invalid messageId ...'))
                                            
                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            526
                                            Online

                                            31.7k
                                            Users

                                            79.6k
                                            Topics

                                            1.3m
                                            Posts

                                            75
                                            720
                                            189254
                                            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