Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor
  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum
donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. Tuya stürzt ab bei fehlendem Gerät

NEWS

  • Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨
    BluefoxB
    Bluefox
    16
    1
    1.4k
  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    13
    1
    819
  • Weihnachtsangebot 2025! 🎄
    BluefoxB
    Bluefox
    25
    1
    2.1k

Tuya stürzt ab bei fehlendem Gerät

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
13 Beiträge 4 Kommentatoren 1.3k Aufrufe 4 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • Old_EngineerO Offline
    Old_EngineerO Offline
    Old_Engineer
    schrieb am zuletzt editiert von
    #1

    Ich habe seit Monaten ein Problem mit dem Tuya Adapter, er stürzt kurz nach dem Start ab. Mittlerweile konnte ich den Fehler einkreisen. Immer dann, wenn die Steckdose mit der IP-Adresse 192.168.1.187 nicht aktiv ist, kommt es zum Absturz. Andere nicht aktive Steckdosen führen nicht zu diesem Fehler, obwohl es sich bei allen um den gleichen Typ mit gleicher Firmware handelt (Gosund SP111). Die Steckdosen gehören zur Weihnachtsbeleuchtung und sind nun außer Betrieb.

    host.raspberrypi4
    2022-03-10 09:27:54.231 error instance system.adapter.tuya.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
    host.raspberrypi4
    2022-03-10 09:27:54.230 error Caught by controller[1]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1159:16)
    host.raspberrypi4
    2022-03-10 09:27:54.230 error Caught by controller[1]: Error: connect EHOSTUNREACH 192.168.1.187:6668
    host.raspberrypi4
    2022-03-10 09:27:54.229 error Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:

    tuya.0
    2022-03-10 09:27:53.518 warn Terminated (UNCAUGHT_EXCEPTION): Without reason

    tuya.0
    2022-03-10 09:27:52.492 error Exception-Code: EHOSTUNREACH: connect EHOSTUNREACH 192.168.1.187:6668

    tuya.0
    2022-03-10 09:27:52.492 error Error: connect EHOSTUNREACH 192.168.1.187:6668 at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1159:16)

    tuya.0
    2022-03-10 09:27:52.491 error unhandled promise rejection: connect EHOSTUNREACH 192.168.1.187:6668

    tuya.0
    2022-03-10 09:27:52.491 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

    tuya.0
    2022-03-10 09:27:10.789 warn 104380002462ab34d91c: Error on Reconnectconnection timed out

    arteckA Old_EngineerO 2 Antworten Letzte Antwort
    0
    • Old_EngineerO Old_Engineer

      Ich habe seit Monaten ein Problem mit dem Tuya Adapter, er stürzt kurz nach dem Start ab. Mittlerweile konnte ich den Fehler einkreisen. Immer dann, wenn die Steckdose mit der IP-Adresse 192.168.1.187 nicht aktiv ist, kommt es zum Absturz. Andere nicht aktive Steckdosen führen nicht zu diesem Fehler, obwohl es sich bei allen um den gleichen Typ mit gleicher Firmware handelt (Gosund SP111). Die Steckdosen gehören zur Weihnachtsbeleuchtung und sind nun außer Betrieb.

      host.raspberrypi4
      2022-03-10 09:27:54.231 error instance system.adapter.tuya.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
      host.raspberrypi4
      2022-03-10 09:27:54.230 error Caught by controller[1]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1159:16)
      host.raspberrypi4
      2022-03-10 09:27:54.230 error Caught by controller[1]: Error: connect EHOSTUNREACH 192.168.1.187:6668
      host.raspberrypi4
      2022-03-10 09:27:54.229 error Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:

      tuya.0
      2022-03-10 09:27:53.518 warn Terminated (UNCAUGHT_EXCEPTION): Without reason

      tuya.0
      2022-03-10 09:27:52.492 error Exception-Code: EHOSTUNREACH: connect EHOSTUNREACH 192.168.1.187:6668

      tuya.0
      2022-03-10 09:27:52.492 error Error: connect EHOSTUNREACH 192.168.1.187:6668 at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1159:16)

      tuya.0
      2022-03-10 09:27:52.491 error unhandled promise rejection: connect EHOSTUNREACH 192.168.1.187:6668

      tuya.0
      2022-03-10 09:27:52.491 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

      tuya.0
      2022-03-10 09:27:10.789 warn 104380002462ab34d91c: Error on Reconnectconnection timed out

      arteckA Offline
      arteckA Offline
      arteck
      Developer Most Active
      schrieb am zuletzt editiert von
      #2

      @old_engineer log bitte in den code tag0399617b-cd24-498b-a592-0773f35b92aa-grafik.png

      zigbee hab ich, zwave auch, nuc's genauso und HA auch

      1 Antwort Letzte Antwort
      0
      • Old_EngineerO Old_Engineer

        Ich habe seit Monaten ein Problem mit dem Tuya Adapter, er stürzt kurz nach dem Start ab. Mittlerweile konnte ich den Fehler einkreisen. Immer dann, wenn die Steckdose mit der IP-Adresse 192.168.1.187 nicht aktiv ist, kommt es zum Absturz. Andere nicht aktive Steckdosen führen nicht zu diesem Fehler, obwohl es sich bei allen um den gleichen Typ mit gleicher Firmware handelt (Gosund SP111). Die Steckdosen gehören zur Weihnachtsbeleuchtung und sind nun außer Betrieb.

        host.raspberrypi4
        2022-03-10 09:27:54.231 error instance system.adapter.tuya.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
        host.raspberrypi4
        2022-03-10 09:27:54.230 error Caught by controller[1]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1159:16)
        host.raspberrypi4
        2022-03-10 09:27:54.230 error Caught by controller[1]: Error: connect EHOSTUNREACH 192.168.1.187:6668
        host.raspberrypi4
        2022-03-10 09:27:54.229 error Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:

        tuya.0
        2022-03-10 09:27:53.518 warn Terminated (UNCAUGHT_EXCEPTION): Without reason

        tuya.0
        2022-03-10 09:27:52.492 error Exception-Code: EHOSTUNREACH: connect EHOSTUNREACH 192.168.1.187:6668

        tuya.0
        2022-03-10 09:27:52.492 error Error: connect EHOSTUNREACH 192.168.1.187:6668 at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1159:16)

        tuya.0
        2022-03-10 09:27:52.491 error unhandled promise rejection: connect EHOSTUNREACH 192.168.1.187:6668

        tuya.0
        2022-03-10 09:27:52.491 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

        tuya.0
        2022-03-10 09:27:10.789 warn 104380002462ab34d91c: Error on Reconnectconnection timed out

        Old_EngineerO Offline
        Old_EngineerO Offline
        Old_Engineer
        schrieb am zuletzt editiert von
        #3

        OK, habe das jetzt mal in den Code-Tag gesetzt

        host.raspberrypi4
2022-03-10 09:27:54.231 error instance system.adapter.tuya.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
host.raspberrypi4
2022-03-10 09:27:54.230 error Caught by controller[1]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1159:16)
host.raspberrypi4
2022-03-10 09:27:54.230 error Caught by controller[1]: Error: connect EHOSTUNREACH 192.168.1.187:6668
host.raspberrypi4
2022-03-10 09:27:54.229 error Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:

tuya.0
2022-03-10 09:27:53.518 warn Terminated (UNCAUGHT_EXCEPTION): Without reason

tuya.0
2022-03-10 09:27:52.492 error Exception-Code: EHOSTUNREACH: connect EHOSTUNREACH 192.168.1.187:6668

tuya.0
2022-03-10 09:27:52.492 error Error: connect EHOSTUNREACH 192.168.1.187:6668 at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1159:16)

tuya.0
2022-03-10 09:27:52.491 error unhandled promise rejection: connect EHOSTUNREACH 192.168.1.187:6668

tuya.0
2022-03-10 09:27:52.491 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

tuya.0
2022-03-10 09:27:10.789 warn 104380002462ab34d91c: Error on Reconnectconnection timed out
        O 1 Antwort Letzte Antwort
        0
        • Old_EngineerO Old_Engineer

          OK, habe das jetzt mal in den Code-Tag gesetzt

          host.raspberrypi4
2022-03-10 09:27:54.231 error instance system.adapter.tuya.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
host.raspberrypi4
2022-03-10 09:27:54.230 error Caught by controller[1]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1159:16)
host.raspberrypi4
2022-03-10 09:27:54.230 error Caught by controller[1]: Error: connect EHOSTUNREACH 192.168.1.187:6668
host.raspberrypi4
2022-03-10 09:27:54.229 error Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:

tuya.0
2022-03-10 09:27:53.518 warn Terminated (UNCAUGHT_EXCEPTION): Without reason

tuya.0
2022-03-10 09:27:52.492 error Exception-Code: EHOSTUNREACH: connect EHOSTUNREACH 192.168.1.187:6668

tuya.0
2022-03-10 09:27:52.492 error Error: connect EHOSTUNREACH 192.168.1.187:6668 at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1159:16)

tuya.0
2022-03-10 09:27:52.491 error unhandled promise rejection: connect EHOSTUNREACH 192.168.1.187:6668

tuya.0
2022-03-10 09:27:52.491 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

tuya.0
2022-03-10 09:27:10.789 warn 104380002462ab34d91c: Error on Reconnectconnection timed out
          O Offline
          O Offline
          oFbEQnpoLKKl6mbY5e13
          schrieb am zuletzt editiert von oFbEQnpoLKKl6mbY5e13
          #4

          @old_engineer

          Da wirst du vermutlich mehr Meldungen liefern müssen (Adapter auf Debug stellen und Absturz erneut provozieren), damit der Entwickler ( @apollon77 ) damit etwas anfangen kann.

          1 Antwort Letzte Antwort
          0
          • apollon77A Offline
            apollon77A Offline
            apollon77
            schrieb am zuletzt editiert von
            #5

            Die wichtigste Info fehlt: Welche Tuya Adapter Version? Ja frühere Versionen hatten mal solche Probleme das eine nicht funktionierende Verbindung (in dem Fall EHOSTRUNREACH - Gerät nicht im WLAN). Aktuelle Versionen sollten das aber nicht haben

            Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

            • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
            • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
            Old_EngineerO 2 Antworten Letzte Antwort
            0
            • apollon77A apollon77

              Die wichtigste Info fehlt: Welche Tuya Adapter Version? Ja frühere Versionen hatten mal solche Probleme das eine nicht funktionierende Verbindung (in dem Fall EHOSTRUNREACH - Gerät nicht im WLAN). Aktuelle Versionen sollten das aber nicht haben

              Old_EngineerO Offline
              Old_EngineerO Offline
              Old_Engineer
              schrieb am zuletzt editiert von
              #6

              @apollon77

              Adapter hat die Version 3.6.15 - also aktuell.
              Momentan helfe ich mir damit, das ich den Stecker in Betrieb habe.
              Werde das mit dem LOG machen.

              1 Antwort Letzte Antwort
              0
              • apollon77A apollon77

                Die wichtigste Info fehlt: Welche Tuya Adapter Version? Ja frühere Versionen hatten mal solche Probleme das eine nicht funktionierende Verbindung (in dem Fall EHOSTRUNREACH - Gerät nicht im WLAN). Aktuelle Versionen sollten das aber nicht haben

                Old_EngineerO Offline
                Old_EngineerO Offline
                Old_Engineer
                schrieb am zuletzt editiert von
                #7

                @apollon77

                2022-03-10 19:06:19.026  - info: mqtt.0 (22211) send2Server tuya.0.104380002462ab34d91c.1[tuya/0/104380002462ab34d91c/1]
2022-03-10 19:06:20.049  - info: mqtt.0 (22211) send2Server tuya.0.104380002462ab34d91c.1[tuya/0/104380002462ab34d91c/1]
2022-03-10 19:06:31.291  - warn: tuya.0 (5334) 16388024cc50e3c900ff: Error on Reconnectconnect EHOSTUNREACH 192.168.1.192:6668
2022-03-10 19:06:31.293  - warn: tuya.0 (5334) 10438000d8f15ba4d78a: Error on Reconnectconnect EHOSTUNREACH 192.168.1.136:6668
2022-03-10 19:06:31.295  - warn: tuya.0 (5334) bf3ef04bae932fbba2rzoo: Error on Reconnectconnect EHOSTUNREACH 192.168.1.123:6668
2022-03-10 19:06:31.371  - warn: tuya.0 (5334) 050407552462ab207646: Error on Reconnectconnect EHOSTUNREACH 192.168.1.145:6668
2022-03-10 19:06:31.373  - warn: tuya.0 (5334) 050407552462ab2f903b: Error on Reconnectconnect EHOSTUNREACH 192.168.1.166:6668
2022-03-10 19:06:31.375  - warn: tuya.0 (5334) 104380002cf432b5cbc7: Error on Reconnectconnect EHOSTUNREACH 192.168.1.189:6668
2022-03-10 19:06:31.451  - warn: tuya.0 (5334) 050407552462ab207451: Error on Reconnectconnect EHOSTUNREACH 192.168.1.174:6668
2022-03-10 19:06:52.811  - error: tuya.0 (5334) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2022-03-10 19:06:52.812  - error: tuya.0 (5334) unhandled promise rejection: connect EHOSTUNREACH 192.168.1.187:6668
2022-03-10 19:06:52.812  - error: tuya.0 (5334) Error: connect EHOSTUNREACH 192.168.1.187:6668
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1159:16)
2022-03-10 19:06:52.813  - error: tuya.0 (5334) Exception-Code: EHOSTUNREACH: connect EHOSTUNREACH 192.168.1.187:6668
2022-03-10 19:06:53.857  - warn: tuya.0 (5334) Terminated (UNCAUGHT_EXCEPTION): Without reason
2022-03-10 19:06:54.585  - error: host.raspberrypi4 Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2022-03-10 19:06:54.586  - error: host.raspberrypi4 Caught by controller[1]: Error: connect EHOSTUNREACH 192.168.1.187:6668
2022-03-10 19:06:54.587  - error: host.raspberrypi4 Caught by controller[1]:     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1159:16)
2022-03-10 19:06:54.587  - error: host.raspberrypi4 instance system.adapter.tuya.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2022-03-10 19:06:54.588  - info: host.raspberrypi4 Restart adapter system.adapter.tuya.0 because enabled
                apollon77A 1 Antwort Letzte Antwort
                0
                • Old_EngineerO Old_Engineer

                  @apollon77

                  2022-03-10 19:06:19.026  - info: mqtt.0 (22211) send2Server tuya.0.104380002462ab34d91c.1[tuya/0/104380002462ab34d91c/1]
2022-03-10 19:06:20.049  - info: mqtt.0 (22211) send2Server tuya.0.104380002462ab34d91c.1[tuya/0/104380002462ab34d91c/1]
2022-03-10 19:06:31.291  - warn: tuya.0 (5334) 16388024cc50e3c900ff: Error on Reconnectconnect EHOSTUNREACH 192.168.1.192:6668
2022-03-10 19:06:31.293  - warn: tuya.0 (5334) 10438000d8f15ba4d78a: Error on Reconnectconnect EHOSTUNREACH 192.168.1.136:6668
2022-03-10 19:06:31.295  - warn: tuya.0 (5334) bf3ef04bae932fbba2rzoo: Error on Reconnectconnect EHOSTUNREACH 192.168.1.123:6668
2022-03-10 19:06:31.371  - warn: tuya.0 (5334) 050407552462ab207646: Error on Reconnectconnect EHOSTUNREACH 192.168.1.145:6668
2022-03-10 19:06:31.373  - warn: tuya.0 (5334) 050407552462ab2f903b: Error on Reconnectconnect EHOSTUNREACH 192.168.1.166:6668
2022-03-10 19:06:31.375  - warn: tuya.0 (5334) 104380002cf432b5cbc7: Error on Reconnectconnect EHOSTUNREACH 192.168.1.189:6668
2022-03-10 19:06:31.451  - warn: tuya.0 (5334) 050407552462ab207451: Error on Reconnectconnect EHOSTUNREACH 192.168.1.174:6668
2022-03-10 19:06:52.811  - error: tuya.0 (5334) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2022-03-10 19:06:52.812  - error: tuya.0 (5334) unhandled promise rejection: connect EHOSTUNREACH 192.168.1.187:6668
2022-03-10 19:06:52.812  - error: tuya.0 (5334) Error: connect EHOSTUNREACH 192.168.1.187:6668
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1159:16)
2022-03-10 19:06:52.813  - error: tuya.0 (5334) Exception-Code: EHOSTUNREACH: connect EHOSTUNREACH 192.168.1.187:6668
2022-03-10 19:06:53.857  - warn: tuya.0 (5334) Terminated (UNCAUGHT_EXCEPTION): Without reason
2022-03-10 19:06:54.585  - error: host.raspberrypi4 Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2022-03-10 19:06:54.586  - error: host.raspberrypi4 Caught by controller[1]: Error: connect EHOSTUNREACH 192.168.1.187:6668
2022-03-10 19:06:54.587  - error: host.raspberrypi4 Caught by controller[1]:     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1159:16)
2022-03-10 19:06:54.587  - error: host.raspberrypi4 instance system.adapter.tuya.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2022-03-10 19:06:54.588  - info: host.raspberrypi4 Restart adapter system.adapter.tuya.0 because enabled
                  apollon77A Offline
                  apollon77A Offline
                  apollon77
                  schrieb am zuletzt editiert von
                  #8

                  @old_engineer bitte damit ein github issue anlegen. Muss ich ansehen. Aber effektiv ist das Gerät aus oder generell nicht Im wlan.

                  Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                  • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                  • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                  Old_EngineerO 2 Antworten Letzte Antwort
                  0
                  • apollon77A apollon77

                    @old_engineer bitte damit ein github issue anlegen. Muss ich ansehen. Aber effektiv ist das Gerät aus oder generell nicht Im wlan.

                    Old_EngineerO Offline
                    Old_EngineerO Offline
                    Old_Engineer
                    schrieb am zuletzt editiert von
                    #9

                    @apollon77

                    jetzt mit Debug bis Absturz

                    2022-03-10 19:32:00.170  - debug: tuya.0 (6071) stateChange tuya.0.104380002462ab34d91c.1 {"val":true,"ack":false,"ts":1646937120159,"q":0,"c":"script.js.common.IP-Adressen","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1646936224528}
2022-03-10 19:32:00.172  - debug: tuya.0 (6071) 104380002462ab34d91c onChange triggered for 1 and value true
2022-03-10 19:32:00.179  - debug: tuya.0 (6071) stateChange tuya.0.14047754c44f33b6df9b.3 {"val":true,"ack":false,"ts":1646937120159,"q":0,"c":"script.js.common.IP-Adressen","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1646933460797}
2022-03-10 19:32:00.180  - debug: tuya.0 (6071) 14047754c44f33b6df9b onChange triggered for 3 and value true
2022-03-10 19:32:00.227  - debug: tuya.0 (6071) 14047754c44f33b6df9b: Received data: {"3":true}
2022-03-10 19:32:00.228  - debug: tuya.0 (6071) 14047754c44f33b6df9b.3: set value true via 14047754c44f33b6df9b
2022-03-10 19:32:00.240  - debug: tuya.0 (6071) stateChange tuya.0.14047754c44f33b6df9b.3 {"val":true,"ack":true,"ts":1646937120234,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1646933460797}
2022-03-10 19:32:02.231  - debug: tuya.0 (6071) 14047754c44f33b6df9b request data via get ...
2022-03-10 19:32:02.249  - debug: tuya.0 (6071) 14047754c44f33b6df9b: Received data: {"1":true,"2":false,"3":true,"4":false,"5":false,"9":0,"10":0,"11":0,"12":0,"13":0}
2022-03-10 19:32:02.266  - debug: tuya.0 (6071) stateChange tuya.0.14047754c44f33b6df9b.1 {"val":true,"ack":true,"ts":1646937122254,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1601648957384}
2022-03-10 19:32:02.267  - debug: tuya.0 (6071) stateChange tuya.0.14047754c44f33b6df9b.2 {"val":false,"ack":true,"ts":1646937122254,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1631567034966}
2022-03-10 19:32:02.267  - debug: tuya.0 (6071) stateChange tuya.0.14047754c44f33b6df9b.3 {"val":true,"ack":true,"ts":1646937122255,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1646933460797}
2022-03-10 19:32:02.268  - debug: tuya.0 (6071) stateChange tuya.0.14047754c44f33b6df9b.4 {"val":false,"ack":true,"ts":1646937122255,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1645548408657}
2022-03-10 19:32:02.268  - debug: tuya.0 (6071) stateChange tuya.0.14047754c44f33b6df9b.5 {"val":false,"ack":true,"ts":1646937122255,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1638098272490}
2022-03-10 19:32:02.269  - debug: tuya.0 (6071) stateChange tuya.0.14047754c44f33b6df9b.9 {"val":0,"ack":true,"ts":1646937122255,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1580310621468}
2022-03-10 19:32:02.269  - debug: tuya.0 (6071) stateChange tuya.0.14047754c44f33b6df9b.10 {"val":0,"ack":true,"ts":1646937122259,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1580310621468}
2022-03-10 19:32:02.272  - debug: tuya.0 (6071) stateChange tuya.0.14047754c44f33b6df9b.11 {"val":0,"ack":true,"ts":1646937122260,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1580310621468}
2022-03-10 19:32:02.272  - debug: tuya.0 (6071) stateChange tuya.0.14047754c44f33b6df9b.12 {"val":0,"ack":true,"ts":1646937122260,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1580310621468}
2022-03-10 19:32:02.273  - debug: tuya.0 (6071) stateChange tuya.0.14047754c44f33b6df9b.13 {"val":0,"ack":true,"ts":1646937122261,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1580310621468}
2022-03-10 19:32:03.290  - debug: tuya.0 (6071) 104380002462ab34d91c: Error from device (1): App still open on your mobile phone? Error: Error from socket: connect EHOSTUNREACH 192.168.1.187:6668
2022-03-10 19:32:05.179  - debug: tuya.0 (6071) 104380002462ab34d91c: Error from device (2): App still open on your mobile phone? Timeout waiting for status response from device id: 104380002462ab34d91c
2022-03-10 19:32:05.180  - debug: tuya.0 (6071) 104380002462ab34d91c.1: set value true via 104380002462ab34d91c
2022-03-10 19:32:06.410  - debug: tuya.0 (6071) 104380002462ab34d91c: Error from device (3): App still open on your mobile phone? Error: Error from socket: connect EHOSTUNREACH 192.168.1.187:6668
2022-03-10 19:32:08.392  - debug: tuya.0 (6071) 14047754c44f33b6df9b: Disconnected from device
2022-03-10 19:32:08.402  - debug: tuya.0 (6071) stateChange tuya.0.14047754c44f33b6df9b.online {"val":false,"ack":true,"ts":1646937128398,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1646937128398}
2022-03-10 19:32:09.530  - debug: tuya.0 (6071) 104380002462ab34d91c: Error from device (4): App still open on your mobile phone? Error: Error from socket: connect EHOSTUNREACH 192.168.1.187:6668
2022-03-10 19:32:12.570  - debug: tuya.0 (6071) 050407552462ab207451: Error from device (1): App still open on your mobile phone? Error: Error from socket: connect EHOSTUNREACH 192.168.1.174:6668
2022-03-10 19:32:12.571  - warn: tuya.0 (6071) 050407552462ab207451: Error on Reconnectconnect EHOSTUNREACH 192.168.1.174:6668
2022-03-10 19:32:12.650  - debug: tuya.0 (6071) 104380002cf432b5cbc7: Error from device (1): App still open on your mobile phone? Error: Error from socket: connect EHOSTUNREACH 192.168.1.189:6668
2022-03-10 19:32:12.651  - warn: tuya.0 (6071) 104380002cf432b5cbc7: Error on Reconnectconnect EHOSTUNREACH 192.168.1.189:6668
2022-03-10 19:32:12.652  - debug: tuya.0 (6071) 10438000d8f15ba4d78a: Error from device (1): App still open on your mobile phone? Error: Error from socket: connect EHOSTUNREACH 192.168.1.136:6668
2022-03-10 19:32:12.653  - warn: tuya.0 (6071) 10438000d8f15ba4d78a: Error on Reconnectconnect EHOSTUNREACH 192.168.1.136:6668
2022-03-10 19:32:12.654  - debug: tuya.0 (6071) 050407552462ab207646: Error from device (1): App still open on your mobile phone? Error: Error from socket: connect EHOSTUNREACH 192.168.1.145:6668
2022-03-10 19:32:12.655  - warn: tuya.0 (6071) 050407552462ab207646: Error on Reconnectconnect EHOSTUNREACH 192.168.1.145:6668
2022-03-10 19:32:12.730  - debug: tuya.0 (6071) 16388024cc50e3c900ff: Error from device (1): App still open on your mobile phone? Error: Error from socket: connect EHOSTUNREACH 192.168.1.192:6668
2022-03-10 19:32:12.731  - warn: tuya.0 (6071) 16388024cc50e3c900ff: Error on Reconnectconnect EHOSTUNREACH 192.168.1.192:6668
2022-03-10 19:32:12.732  - debug: tuya.0 (6071) bf3ef04bae932fbba2rzoo: Error from device (1): App still open on your mobile phone? Error: Error from socket: connect EHOSTUNREACH 192.168.1.123:6668
2022-03-10 19:32:12.732  - warn: tuya.0 (6071) bf3ef04bae932fbba2rzoo: Error on Reconnectconnect EHOSTUNREACH 192.168.1.123:6668
2022-03-10 19:32:12.740  - debug: tuya.0 (6071) 050407552462ab2f903b: Error from device (1): App still open on your mobile phone? Error: Error from socket: connect EHOSTUNREACH 192.168.1.166:6668
2022-03-10 19:32:12.741  - warn: tuya.0 (6071) 050407552462ab2f903b: Error on Reconnectconnect EHOSTUNREACH 192.168.1.166:6668
2022-03-10 19:32:15.341  - debug: tuya.0 (6071) Discovered encrypted device and store for later usage: 192.168.1.190:49154 - 000055aa0000000000000013000000ac00000000d09766676f3369eb10b5e9f132fd802a7d222da318604e6e88f34e0967c7912da18ebe37c7236a532f3900f430862fa6c58a66a24a2ca7fbd9561247cafb8c834cb2e96c0a7f1e413baed18d2f9ce89dd98a2083cc863e53249cdfed5ec93122b4b2bbeece5882c45b23697e1daac6fc5c48bde787568f13670cf30c6f92ffa70280ea7371bd425875c843df05523c7b768ffc6ab334859566b8db83b5bc22158a63b88e0000aa55
2022-03-10 19:32:15.343  - debug: tuya.0 (6071) 104380002462ab34d91c: Try to initialize encrypted device with received UDP messages (#IPs: 1): version=3.3, key=1f77cec895c95c6b
2022-03-10 19:32:15.344  - info: tuya.0 (6071) 104380002462ab34d91c: None of the discovered devices matches :-(
2022-03-10 19:32:16.650  - debug: tuya.0 (6071) 104380002462ab34d91c: Error from device (5): App still open on your mobile phone? Error: Error from socket: connect EHOSTUNREACH 192.168.1.187:6668
2022-03-10 19:32:23.897  - debug: tuya.0 (6071) stateChange tuya.0.104380002462ab34d91c.1 {"val":false,"ack":false,"ts":1646937143895,"q":0,"from":"system.adapter.web.0","user":"system.user.admin","lc":1646937143895}
2022-03-10 19:32:23.898  - info: mqtt.0 (22211) send2Server tuya.0.104380002462ab34d91c.1[tuya/0/104380002462ab34d91c/1]
2022-03-10 19:32:23.897  - debug: tuya.0 (6071) 104380002462ab34d91c onChange triggered for 1 and value false
2022-03-10 19:32:23.898  - debug: tuya.0 (6071) 104380002462ab34d91c Device communication not initialized ...
2022-03-10 19:32:24.576  - info: mqtt.0 (22211) send2Server tuya.0.104380002462ab34d91c.1[tuya/0/104380002462ab34d91c/1]
2022-03-10 19:32:24.576  - debug: tuya.0 (6071) stateChange tuya.0.104380002462ab34d91c.1 {"val":true,"ack":false,"ts":1646937144575,"q":0,"from":"system.adapter.web.0","user":"system.user.admin","lc":1646937144575}
2022-03-10 19:32:24.577  - debug: tuya.0 (6071) 104380002462ab34d91c onChange triggered for 1 and value true
2022-03-10 19:32:24.578  - debug: tuya.0 (6071) 104380002462ab34d91c Device communication not initialized ...
2022-03-10 19:32:27.770  - debug: tuya.0 (6071) 104380002462ab34d91c: Error from device (6): App still open on your mobile phone? Error: Error from socket: connect EHOSTUNREACH 192.168.1.187:6668
2022-03-10 19:32:36.386  - debug: tuya.0 (6071) 16388024cc50e3c8fca7 request data via get ...
2022-03-10 19:32:36.392  - debug: tuya.0 (6071) 16388024cc50e3c8fca7: Received data: {"1":true,"11":0}
2022-03-10 19:32:36.401  - debug: tuya.0 (6071) 87874800dc4f22ecc671 request data via get ...
2022-03-10 19:32:36.403  - debug: tuya.0 (6071) stateChange tuya.0.16388024cc50e3c8fca7.1 {"val":true,"ack":true,"ts":1646937156396,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1646933162293}
2022-03-10 19:32:36.405  - debug: tuya.0 (6071) stateChange tuya.0.16388024cc50e3c8fca7.11 {"val":0,"ack":true,"ts":1646937156397,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1579625391061}
2022-03-10 19:32:36.406  - debug: tuya.0 (6071) 5871138310521c4f1c8f request data via get ...
2022-03-10 19:32:36.408  - debug: tuya.0 (6071) 87874800dc4f22ecc671: Received data: {"1":false,"2":0}
2022-03-10 19:32:36.421  - debug: tuya.0 (6071) 5871138310521c4f1c8f: Received data: {"20":false,"21":"colour","22":820,"23":270,"24":"016503e803e8","25":"07282802000003e803e800000000282802007803e803e80000000028280200f003e803e800000000282802003d03e803e80000000028280200ae03e803e800000000282802011303e803e800000000","26":0}
2022-03-10 19:32:36.423  - debug: tuya.0 (6071) stateChange tuya.0.87874800dc4f22ecc671.1 {"val":false,"ack":true,"ts":1646937156416,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1646855566898}
2022-03-10 19:32:36.423  - debug: tuya.0 (6071) stateChange tuya.0.87874800dc4f22ecc671.2 {"val":0,"ack":true,"ts":1646937156416,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1562273422180}
2022-03-10 19:32:36.451  - debug: tuya.0 (6071) stateChange tuya.0.5871138310521c4f1c8f.20 {"val":false,"ack":true,"ts":1646937156431,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1646002374767}
2022-03-10 19:32:36.452  - debug: tuya.0 (6071) stateChange tuya.0.5871138310521c4f1c8f.21 {"val":1,"ack":true,"ts":1646937156432,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1641845779938}
2022-03-10 19:32:36.453  - debug: tuya.0 (6071) stateChange tuya.0.5871138310521c4f1c8f.22 {"val":820,"ack":true,"ts":1646937156432,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1641845776711}
2022-03-10 19:32:36.453  - debug: tuya.0 (6071) stateChange tuya.0.5871138310521c4f1c8f.23 {"val":270,"ack":true,"ts":1646937156432,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1641845776722}
2022-03-10 19:32:36.454  - debug: tuya.0 (6071) stateChange tuya.0.5871138310521c4f1c8f.24 {"val":"016503e803e8","ack":true,"ts":1646937156438,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1646002366639}
2022-03-10 19:32:36.454  - debug: tuya.0 (6071) stateChange tuya.0.5871138310521c4f1c8f.25 {"val":"07282802000003e803e800000000282802007803e803e80000000028280200f003e803e800000000282802003d03e803e80000000028280200ae03e803e800000000282802011303e803e800000000","ack":true,"ts":1646937156438,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1640389822616}
2022-03-10 19:32:36.460  - debug: tuya.0 (6071) 87874800dc4f22ee973d request data via get ...
2022-03-10 19:32:36.462  - debug: tuya.0 (6071) 4446311768c63ae253f2 request data via get ...
2022-03-10 19:32:36.463  - debug: tuya.0 (6071) 16388024cc50e3c8f006 request data via get ...
2022-03-10 19:32:36.465  - debug: tuya.0 (6071) stateChange tuya.0.5871138310521c4f1c8f.26 {"val":0,"ack":true,"ts":1646937156444,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1636793144221}
2022-03-10 19:32:36.468  - debug: tuya.0 (6071) 4446311768c63ae253f2: Received data: {"1":"3"}
2022-03-10 19:32:36.474  - debug: tuya.0 (6071) 45007282dc4f22734986 request data via get ...
2022-03-10 19:32:36.478  - debug: tuya.0 (6071) 5871138310521c49bb03 request data via get ...
2022-03-10 19:32:36.480  - debug: tuya.0 (6071) stateChange tuya.0.4446311768c63ae253f2.1 {"val":3,"ack":true,"ts":1646937156473,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1646935134510}
2022-03-10 19:32:36.492  - debug: tuya.0 (6071) 16388024cc50e3c8f006: Received data: {"1":true,"11":0}
2022-03-10 19:32:36.494  - debug: tuya.0 (6071) 16388024cc50e3c90117 request data via get ...
2022-03-10 19:32:36.496  - debug: tuya.0 (6071) 5871138310521c49bb03: Received data: {"20":false,"21":"colour","22":820,"23":220,"24":"016503e701f6","25":"030e0d0000000000000001f401f4","26":0}
2022-03-10 19:32:36.499  - debug: tuya.0 (6071) 87874800dc4f22ee973d: Received data: {"1":true,"2":0}
2022-03-10 19:32:36.505  - debug: tuya.0 (6071) 45007282dc4f22734986: Received data: {"1":"2"}
2022-03-10 19:32:36.508  - debug: tuya.0 (6071) 16388024cc50e3c90117: Received data: {"1":true,"11":0}
2022-03-10 19:32:36.515  - debug: tuya.0 (6071) 16388024cc50e3c8f20a request data via get ...
2022-03-10 19:32:36.523  - debug: tuya.0 (6071) 16388024cc50e3c8f20a: Received data: {"1":false,"11":0}
2022-03-10 19:32:36.542  - debug: tuya.0 (6071) 87874800dc4f22ec3531 request data via get ...
2022-03-10 19:32:36.547  - debug: tuya.0 (6071) stateChange tuya.0.16388024cc50e3c8f006.1 {"val":true,"ack":true,"ts":1646937156507,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1646933134846}
2022-03-10 19:32:36.548  - debug: tuya.0 (6071) stateChange tuya.0.16388024cc50e3c8f006.11 {"val":0,"ack":true,"ts":1646937156518,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1612718417248}
2022-03-10 19:32:36.549  - debug: tuya.0 (6071) stateChange tuya.0.5871138310521c49bb03.20 {"val":false,"ack":true,"ts":1646937156519,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1646002210964}
2022-03-10 19:32:36.549  - debug: tuya.0 (6071) stateChange tuya.0.5871138310521c49bb03.21 {"val":1,"ack":true,"ts":1646937156519,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1641854007840}
2022-03-10 19:32:36.550  - debug: tuya.0 (6071) stateChange tuya.0.5871138310521c49bb03.22 {"val":820,"ack":true,"ts":1646937156520,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1641853992049}
2022-03-10 19:32:36.550  - debug: tuya.0 (6071) stateChange tuya.0.5871138310521c49bb03.23 {"val":220,"ack":true,"ts":1646937156520,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1641853992057}
2022-03-10 19:32:36.551  - debug: tuya.0 (6071) stateChange tuya.0.5871138310521c49bb03.24 {"val":"016503e701f6","ack":true,"ts":1646937156520,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1646002051979}
2022-03-10 19:32:36.552  - debug: tuya.0 (6071) stateChange tuya.0.5871138310521c49bb03.25 {"val":"030e0d0000000000000001f401f4","ack":true,"ts":1646937156521,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1639867287585}
2022-03-10 19:32:36.552  - debug: tuya.0 (6071) stateChange tuya.0.5871138310521c49bb03.26 {"val":0,"ack":true,"ts":1646937156521,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1636793144197}
2022-03-10 19:32:36.553  - debug: tuya.0 (6071) stateChange tuya.0.87874800dc4f22ee973d.1 {"val":true,"ack":true,"ts":1646937156521,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1646933162317}
2022-03-10 19:32:36.567  - debug: tuya.0 (6071) stateChange tuya.0.87874800dc4f22ee973d.2 {"val":0,"ack":true,"ts":1646937156535,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1562273422376}
2022-03-10 19:32:36.568  - debug: tuya.0 (6071) stateChange tuya.0.45007282dc4f22734986.1 {"val":2,"ack":true,"ts":1646937156535,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1646936746466}
2022-03-10 19:32:36.569  - debug: tuya.0 (6071) stateChange tuya.0.16388024cc50e3c90117.1 {"val":true,"ack":true,"ts":1646937156536,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1646933135041}
2022-03-10 19:32:36.569  - debug: tuya.0 (6071) stateChange tuya.0.16388024cc50e3c90117.11 {"val":0,"ack":true,"ts":1646937156546,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1562273421933}
2022-03-10 19:32:36.570  - debug: tuya.0 (6071) stateChange tuya.0.16388024cc50e3c8f20a.1 {"val":false,"ack":true,"ts":1646937156547,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1646900794580}
2022-03-10 19:32:36.576  - debug: tuya.0 (6071) stateChange tuya.0.16388024cc50e3c8f20a.11 {"val":0,"ack":true,"ts":1646937156557,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1567705540464}
2022-03-10 19:32:36.587  - debug: tuya.0 (6071) 87874800dc4f22ec3531: Received data: {"1":false,"2":0}
2022-03-10 19:32:36.600  - debug: tuya.0 (6071) stateChange tuya.0.87874800dc4f22ec3531.1 {"val":false,"ack":true,"ts":1646937156592,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1646936340116}
2022-03-10 19:32:36.601  - debug: tuya.0 (6071) stateChange tuya.0.87874800dc4f22ec3531.2 {"val":0,"ack":true,"ts":1646937156596,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1562273424554}
2022-03-10 19:32:38.398  - debug: tuya.0 (6071) 14047754c44f33b6df9b: Connected to device
2022-03-10 19:32:38.403  - debug: tuya.0 (6071) stateChange tuya.0.14047754c44f33b6df9b.online {"val":true,"ack":true,"ts":1646937158401,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1646937158401}
2022-03-10 19:32:38.417  - debug: tuya.0 (6071) 14047754c44f33b6df9b: Received data: {"1":true,"2":false,"3":true,"4":false,"5":false,"9":0,"10":0,"11":0,"12":0,"13":0}
2022-03-10 19:32:38.430  - debug: tuya.0 (6071) stateChange tuya.0.14047754c44f33b6df9b.1 {"val":true,"ack":true,"ts":1646937158421,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1601648957384}
2022-03-10 19:32:38.432  - debug: tuya.0 (6071) stateChange tuya.0.14047754c44f33b6df9b.2 {"val":false,"ack":true,"ts":1646937158422,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1631567034966}
2022-03-10 19:32:38.432  - debug: tuya.0 (6071) stateChange tuya.0.14047754c44f33b6df9b.3 {"val":true,"ack":true,"ts":1646937158422,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1646933460797}
2022-03-10 19:32:38.433  - debug: tuya.0 (6071) stateChange tuya.0.14047754c44f33b6df9b.4 {"val":false,"ack":true,"ts":1646937158422,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1645548408657}
2022-03-10 19:32:38.433  - debug: tuya.0 (6071) stateChange tuya.0.14047754c44f33b6df9b.5 {"val":false,"ack":true,"ts":1646937158423,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1638098272490}
2022-03-10 19:32:38.434  - debug: tuya.0 (6071) stateChange tuya.0.14047754c44f33b6df9b.9 {"val":0,"ack":true,"ts":1646937158424,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1580310621468}
2022-03-10 19:32:38.438  - debug: tuya.0 (6071) stateChange tuya.0.14047754c44f33b6df9b.10 {"val":0,"ack":true,"ts":1646937158426,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1580310621468}
2022-03-10 19:32:38.439  - debug: tuya.0 (6071) stateChange tuya.0.14047754c44f33b6df9b.11 {"val":0,"ack":true,"ts":1646937158427,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1580310621468}
2022-03-10 19:32:38.440  - debug: tuya.0 (6071) stateChange tuya.0.14047754c44f33b6df9b.12 {"val":0,"ack":true,"ts":1646937158427,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1580310621468}
2022-03-10 19:32:38.440  - debug: tuya.0 (6071) stateChange tuya.0.14047754c44f33b6df9b.13 {"val":0,"ack":true,"ts":1646937158427,"q":0,"from":"system.adapter.tuya.0","user":"system.user.admin","lc":1580310621468}
2022-03-10 19:32:45.700  - debug: tuya.0 (6071) 050407552462ab207451: Error from device (2): App still open on your mobile phone? Error: Error from socket: connect EHOSTUNREACH 192.168.1.174:6668
2022-03-10 19:32:45.702  - warn: tuya.0 (6071) 050407552462ab207451: Error on Reconnectconnect EHOSTUNREACH 192.168.1.174:6668
2022-03-10 19:32:45.770  - debug: tuya.0 (6071) 050407552462ab207646: Error from device (2): App still open on your mobile phone? Error: Error from socket: connect EHOSTUNREACH 192.168.1.145:6668
2022-03-10 19:32:45.771  - warn: tuya.0 (6071) 050407552462ab207646: Error on Reconnectconnect EHOSTUNREACH 192.168.1.145:6668
2022-03-10 19:32:45.773  - debug: tuya.0 (6071) 10438000d8f15ba4d78a: Error from device (2): App still open on your mobile phone? Error: Error from socket: connect EHOSTUNREACH 192.168.1.136:6668
2022-03-10 19:32:45.774  - warn: tuya.0 (6071) 10438000d8f15ba4d78a: Error on Reconnectconnect EHOSTUNREACH 192.168.1.136:6668
2022-03-10 19:32:45.781  - debug: tuya.0 (6071) 104380002cf432b5cbc7: Error from device (2): App still open on your mobile phone? Error: Error from socket: connect EHOSTUNREACH 192.168.1.189:6668
2022-03-10 19:32:45.782  - warn: tuya.0 (6071) 104380002cf432b5cbc7: Error on Reconnectconnect EHOSTUNREACH 192.168.1.189:6668
2022-03-10 19:32:45.850  - debug: tuya.0 (6071) 050407552462ab2f903b: Error from device (2): App still open on your mobile phone? Error: Error from socket: connect EHOSTUNREACH 192.168.1.166:6668
2022-03-10 19:32:45.851  - warn: tuya.0 (6071) 050407552462ab2f903b: Error on Reconnectconnect EHOSTUNREACH 192.168.1.166:6668
2022-03-10 19:32:45.853  - debug: tuya.0 (6071) bf3ef04bae932fbba2rzoo: Error from device (2): App still open on your mobile phone? Error: Error from socket: connect EHOSTUNREACH 192.168.1.123:6668
2022-03-10 19:32:45.854  - warn: tuya.0 (6071) bf3ef04bae932fbba2rzoo: Error on Reconnectconnect EHOSTUNREACH 192.168.1.123:6668
2022-03-10 19:32:45.855  - debug: tuya.0 (6071) 16388024cc50e3c900ff: Error from device (2): App still open on your mobile phone? Error: Error from socket: connect EHOSTUNREACH 192.168.1.192:6668
2022-03-10 19:32:45.856  - warn: tuya.0 (6071) 16388024cc50e3c900ff: Error on Reconnectconnect EHOSTUNREACH 192.168.1.192:6668
2022-03-10 19:32:46.890  - debug: tuya.0 (6071) 104380002462ab34d91c: Error from device (7): App still open on your mobile phone? Error: Error from socket: connect EHOSTUNREACH 192.168.1.187:6668
2022-03-10 19:32:46.893  - error: tuya.0 (6071) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2022-03-10 19:32:46.894  - error: tuya.0 (6071) unhandled promise rejection: connect EHOSTUNREACH 192.168.1.187:6668
2022-03-10 19:32:46.895  - error: tuya.0 (6071) Error: connect EHOSTUNREACH 192.168.1.187:6668
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1159:16)
2022-03-10 19:32:46.895  - error: tuya.0 (6071) Exception-Code: EHOSTUNREACH: connect EHOSTUNREACH 192.168.1.187:6668
2022-03-10 19:32:46.933  - debug: tuya.0 (6071) 14047754c44f33b6df9b: Disconnected from device
2022-03-10 19:32:46.935  - debug: tuya.0 (6071) 16388024cc50e3c8f006: Disconnected from device
2022-03-10 19:32:46.936  - debug: tuya.0 (6071) 16388024cc50e3c8f20a: Disconnected from device
2022-03-10 19:32:46.937  - debug: tuya.0 (6071) 16388024cc50e3c8fca7: Disconnected from device
2022-03-10 19:32:46.938  - debug: tuya.0 (6071) 16388024cc50e3c90117: Disconnected from device
2022-03-10 19:32:46.939  - debug: tuya.0 (6071) 4446311768c63ae253f2: Disconnected from device
2022-03-10 19:32:46.940  - debug: tuya.0 (6071) 45007282dc4f22734986: Disconnected from device
2022-03-10 19:32:46.941  - debug: tuya.0 (6071) 87874800dc4f22ec3531: Disconnected from device
2022-03-10 19:32:46.942  - debug: tuya.0 (6071) 87874800dc4f22ecc671: Disconnected from device
2022-03-10 19:32:46.943  - debug: tuya.0 (6071) 87874800dc4f22ee973d: Disconnected from device
2022-03-10 19:32:46.944  - debug: tuya.0 (6071) 5871138310521c49bb03: Disconnected from device
2022-03-10 19:32:46.945  - debug: tuya.0 (6071) 5871138310521c4f1c8f: Disconnected from device
2022-03-10 19:32:46.987  - debug: tuya.0 (6071) connected set to false
2022-03-10 19:32:47.947  - debug: tuya.0 (6071) Plugin sentry destroyed
2022-03-10 19:32:47.948  - warn: tuya.0 (6071) Terminated (UNCAUGHT_EXCEPTION): Without reason
2022-03-10 19:32:48.678  - error: host.raspberrypi4 Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2022-03-10 19:32:48.679  - error: host.raspberrypi4 Caught by controller[1]: Error: connect EHOSTUNREACH 192.168.1.187:6668
2022-03-10 19:32:48.682  - error: host.raspberrypi4 Caught by controller[1]:     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1159:16)
2022-03-10 19:32:48.682  - error: host.raspberrypi4 instance system.adapter.tuya.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2022-03-10 19:32:48.684  - info: host.raspberrypi4 Restart adapter system.adapter.tuya.0 because enabled
                    1 Antwort Letzte Antwort
                    0
                    • apollon77A apollon77

                      @old_engineer bitte damit ein github issue anlegen. Muss ich ansehen. Aber effektiv ist das Gerät aus oder generell nicht Im wlan.

                      Old_EngineerO Offline
                      Old_EngineerO Offline
                      Old_Engineer
                      schrieb am zuletzt editiert von
                      #10

                      @apollon77

                      Ja, das Gerät ist nicht im WLAN, wie andere Steckdosen der Weihnachtsbeleuchtung auch. Aber nur dieses Gerät erzeugt reproduzierbar den Fehler.

                      Mein Workaround ist, den Stecker im WLAN aktiv zu halten.

                      Werde ein Issue auf Github öffnen.

                      apollon77A 1 Antwort Letzte Antwort
                      0
                      • Old_EngineerO Old_Engineer

                        @apollon77

                        Ja, das Gerät ist nicht im WLAN, wie andere Steckdosen der Weihnachtsbeleuchtung auch. Aber nur dieses Gerät erzeugt reproduzierbar den Fehler.

                        Mein Workaround ist, den Stecker im WLAN aktiv zu halten.

                        Werde ein Issue auf Github öffnen.

                        apollon77A Offline
                        apollon77A Offline
                        apollon77
                        schrieb am zuletzt editiert von
                        #11

                        @old_engineer Welches Gerät( die ID) ists denn genau wenn Du weisst welches?

                        Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                        • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                        • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                        1 Antwort Letzte Antwort
                        0
                        • apollon77A Offline
                          apollon77A Offline
                          apollon77
                          schrieb am zuletzt editiert von
                          #12

                          Ich glaub in dem GitHub issue hab ich die Tage gepostet: Bitte 3.7.2 versuchen :-)

                          Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                          • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                          • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                          Old_EngineerO 1 Antwort Letzte Antwort
                          0
                          • apollon77A apollon77

                            Ich glaub in dem GitHub issue hab ich die Tage gepostet: Bitte 3.7.2 versuchen :-)

                            Old_EngineerO Offline
                            Old_EngineerO Offline
                            Old_Engineer
                            schrieb am zuletzt editiert von
                            #13

                            @apollon77 Probiere ich gleich aus 😀

                            1 Antwort Letzte Antwort
                            0
                            Antworten
                            • In einem neuen Thema antworten
                            Anmelden zum Antworten
                            • Älteste zuerst
                            • Neuste zuerst
                            • Meiste Stimmen

                            Support us

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

                            696

                            Online

                            32.6k

                            Benutzer

                            82.0k

                            Themen

                            1.3m

                            Beiträge
                            Community
                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                            ioBroker Community 2014-2025
                            logo
                            • Anmelden
                            • Du hast noch kein Konto? Registrieren
                            • Anmelden oder registrieren, um zu suchen
                            • Erster Beitrag
                              Letzter Beitrag
                            0
                            • Home
                            • Aktuell
                            • Tags
                            • Ungelesen 0
                            • Kategorien
                            • Unreplied
                            • Beliebt
                            • GitHub
                            • Docu
                            • Hilfe