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

  1. ioBroker Community Home
  2. Deutsch
  3. Tester
  4. Test Adapter TP-Link Tapo

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.4k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    2.0k

  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    15
    1
    2.5k

Test Adapter TP-Link Tapo

Geplant Angeheftet Gesperrt Verschoben Tester
772 Beiträge 112 Kommentatoren 259.6k Aufrufe 101 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.
  • metaxaM metaxa

    Ich habe hier vor mir eine neue C520WS Camera, komme mit dem Tapo Adapter nicht wirklich auf gleich. Schreibt mir das LOG mit Fehlermeldungen voll und die Instanz wird wieder rot.

    Eine Mail mit einem FMA Code habe ich nicht bekommen, die Mail wegen Anmeldung von einem iOS/ioBroker jedoch schon. Im Log steht auch nix von einem FMA Code.

    Die Kamera wurde offensichtlich einmal gefunden, da etliche Datenpunkte angelegt wurden. Leider gibt es keinen DP "move to position" oder so etwas, gefühlt kann ich keinen einzigen DP steuern.

    In diesem Thread lese ich immmer etwas von diesem HomeAssistent. Dann könnte ich mit dem HomeAssistent Adapter die Kamera über iO steuern. VIS bediene ich über Motioneye, ich bräuchte nur die Schwenkfunktion bzw. das aktive Anfahren gespeicherter Positionen.

    Weiß jemand ob sich die Kamera im HomeAssistent einbinden und steuern läßt?

    LG, mxa

    T Offline
    T Offline
    tombox
    schrieb am zuletzt editiert von
    #346

    @metaxa Genaue Logs wären gut und du kannst auch den onvis adapter probieren

    metaxaM Walter WhiteW 2 Antworten Letzte Antwort
    0
    • T tombox

      @metaxa Genaue Logs wären gut und du kannst auch den onvis adapter probieren

      metaxaM Offline
      metaxaM Offline
      metaxa
      schrieb am zuletzt editiert von
      #347

      @tombox sagte in Test Adapter TP-Link Tapo:

      Genaue Logs wären gut

      Sehr gerne, ich suche sie raus! Bitte mein Post ist keine Kritik an deinem Adapter, ich hatte nur die Hoffnung .......

      metaxaM 1 Antwort Letzte Antwort
      0
      • T tombox

        @metaxa Genaue Logs wären gut und du kannst auch den onvis adapter probieren

        Walter WhiteW Offline
        Walter WhiteW Offline
        Walter White
        schrieb am zuletzt editiert von Walter White
        #348

        @tombox Werden die Steckdosen ohne diesen fix nicht mehr laufen?
        Screenshot_2024-01-09-23-18-09-950_com.android.chrome-edit.jpg
        Gibt es kein Plan b auf GitHub wenn jemand plötzlich nicht mehr ist?

        T 1 Antwort Letzte Antwort
        0
        • metaxaM metaxa

          @tombox sagte in Test Adapter TP-Link Tapo:

          Genaue Logs wären gut

          Sehr gerne, ich suche sie raus! Bitte mein Post ist keine Kritik an deinem Adapter, ich hatte nur die Hoffnung .......

          metaxaM Offline
          metaxaM Offline
          metaxa
          schrieb am zuletzt editiert von metaxa
          #349

          @tombox sagte in Test Adapter TP-Link Tapo:

          @metaxa Genaue Logs wären gut und du kannst auch den onvis adapter probieren

          Hier das Log. Im ersen Anlauf mit dem freigegebenen Konto der neuen CAM, dann die beiden IP Adressen der andern Cam´s manuell eingetragen (jeweils ein anderes freigegebenes Konto). Was mir noch fehlen würde, EIN freigegebenes Konto für alle Cams.

          2024-01-08 18:56:28.919 - info: host.iOProduktiv instance system.adapter.tapo.0 started with pid 113047
          2024-01-08 18:56:29.913 - info: tapo.0 (113047) starting. Version 0.2.0 (non-npm: TA2k/ioBroker.tapo#f22d791b9b422d6fd3abe8a2f9f7382a7988c965) in /opt/iobroker/node_modules/iobroker.tapo, node: v18.18.2, js-controller: 5.0.17
          2024-01-08 18:56:29.927 - error: tapo.0 (113047) Please set username and password in the instance settings
          2024-01-08 19:02:30.919 - info: host.iOProduktiv stopInstance system.adapter.tapo.0 (force=false, process=true)
          2024-01-08 19:02:30.921 - info: tapo.0 (113047) Got terminate signal TERMINATE_YOURSELF
          2024-01-08 19:02:30.922 - info: tapo.0 (113047) terminating
          2024-01-08 19:02:30.922 - info: tapo.0 (113047) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
          2024-01-08 19:02:30.993 - info: host.iOProduktiv stopInstance system.adapter.tapo.0 send kill signal
          2024-01-08 19:02:31.423 - info: tapo.0 (113047) terminating
          2024-01-08 19:02:31.520 - info: host.iOProduktiv instance system.adapter.tapo.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
          2024-01-08 19:02:34.099 - info: host.iOProduktiv instance system.adapter.tapo.0 started with pid 128175
          2024-01-08 19:02:35.050 - info: tapo.0 (128175) starting. Version 0.2.0 (non-npm: TA2k/ioBroker.tapo#f22d791b9b422d6fd3abe8a2f9f7382a7988c965) in /opt/iobroker/node_modules/iobroker.tapo, node: v18.18.2, js-controller: 5.0.17
          2024-01-08 19:02:35.123 - info: tapo.0 (128175) Login tp TAPO App
          2024-01-08 19:02:35.504 - info: tapo.0 (128175) Login succesfull
          2024-01-08 19:02:35.740 - info: tapo.0 (128175) Found 3 devices
          2024-01-08 19:02:36.239 - error: tapo.0 (128175) {"error_code":-20571,"msg":"Device is offline"}
          2024-01-08 19:02:36.245 - warn: tapo.0 (128175) No IP found for 8021CDA220ADD1EE6A8E7E7D0F7DFE861E649CA0 put the device online or set the ip state manually
          2024-01-08 19:02:36.488 - info: tapo.0 (128175) Init device 80219D887A52D32D03212C4C2DE37E4D21EC8028 type C520WS 1.0 with ip 192.168.0.220
          2024-01-08 19:02:36.631 - info: tapo.0 (128175) 80219D887A52D32D03212C4C2DE37E4D21EC8028 Received device info {"manufacturer":"tp-link","model":"Tapo C520WS","firmwareVersion":"1.1.4 Build 230922 Rel.57957n","serialNumber":"31d87f97","hardwareId":1}
          2024-01-08 19:02:36.700 - info: tapo.0 (128175) Initialized 80219D887A52D32D03212C4C2DE37E4D21EC8028
          2024-01-08 19:02:37.151 - error: tapo.0 (128175) {"error_code":-20571,"msg":"Device is offline"}
          2024-01-08 19:02:37.203 - warn: tapo.0 (128175) No IP found for 8021314EFB57E17626EC16DBDB2A31A51E64292E put the device online or set the ip state manually
          2024-01-08 19:02:37.257 - info: tapo.0 (128175) Wait for connections
          2024-01-08 19:02:47.318 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:02:57.321 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:03:07.321 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:03:17.322 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:03:27.322 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:03:37.322 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:03:47.322 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:03:57.323 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:04:07.323 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:04:17.323 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:04:27.324 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:04:37.324 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:04:47.323 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:04:57.323 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:05:17.323 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:05:27.324 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:05:37.324 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:05:47.326 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:05:57.326 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:06:07.326 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:06:17.325 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:06:27.325 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:06:37.325 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:06:47.326 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:06:57.328 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:07:07.329 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:07:17.330 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:07:27.330 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:07:37.330 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:07:47.332 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:07:57.332 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:08:07.334 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:08:17.334 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:08:27.335 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:08:37.336 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:08:47.337 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:08:57.339 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:09:07.340 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:09:17.340 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:09:27.341 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:09:37.342 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:09:47.343 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:09:57.345 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:10:07.345 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:10:17.347 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:10:27.347 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:10:37.348 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:10:47.348 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:10:57.349 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:11:07.351 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:11:17.351 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:11:20.962 - error: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:11:27.351 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:11:30.895 - error: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:11:37.353 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:11:42.277 - error: tapo.0 (128175) Device 80219D887A52D32D03212C4C2DE37E4D21EC8028 has no command refresh
          2024-01-08 19:11:47.353 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:11:52.485 - error: tapo.0 (128175) Device 80219D887A52D32D03212C4C2DE37E4D21EC8028 has no command refresh
          2024-01-08 19:11:57.355 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:12:07.355 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:12:17.356 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:12:27.357 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:12:37.358 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:12:42.876 - error: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:12:47.359 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:12:52.128 - error: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:12:57.361 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:13:07.361 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:13:17.363 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:13:27.363 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:13:37.363 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:13:47.363 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:13:57.364 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:14:07.364 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:14:17.365 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:14:27.365 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:14:37.365 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:14:47.367 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:14:57.368 - warn: tapo.0 (128175) Error: Unknown password encryption method
          2024-01-08 19:22:40.707 - error: tapo.0 (176846) {"error_code":-20571,"msg":"Device is offline"}
          2024-01-08 19:22:40.709 - warn: tapo.0 (176846) No IP found for 8021CDA220ADD1EE6A8E7E7D0F7DFE861E649CA0 put the device online or set the ip state manually
          2024-01-08 19:22:40.941 - info: tapo.0 (176846) Init device 80219D887A52D32D03212C4C2DE37E4D21EC8028 type C520WS 1.0 with ip 192.168.0.220
          2024-01-08 19:22:41.072 - info: tapo.0 (176846) 80219D887A52D32D03212C4C2DE37E4D21EC8028 Received device info {"manufacturer":"tp-link","model":"Tapo C520WS","firmwareVersion":"1.1.4 Build 230922 Rel.57957n","serialNumber":"31d87f97","hardwareId":1}
          2024-01-08 19:22:41.076 - info: tapo.0 (176846) Initialized 80219D887A52D32D03212C4C2DE37E4D21EC8028
          2024-01-08 19:22:41.153 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
          2024-01-08 19:22:41.503 - error: tapo.0 (176846) {"error_code":-20571,"msg":"Device is offline"}
          2024-01-08 19:22:41.508 - warn: tapo.0 (176846) No IP found for 8021314EFB57E17626EC16DBDB2A31A51E64292E put the device online or set the ip state manually
          2024-01-08 19:22:41.688 - info: tapo.0 (176846) Wait for connections
          2024-01-08 19:22:41.802 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
          2024-01-08 19:22:42.980 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
          2024-01-08 19:22:43.998 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
          2024-01-08 19:22:45.380 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
          2024-01-08 19:22:48.993 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
          2024-01-08 19:22:49.182 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
          2024-01-08 19:22:50.216 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
          2024-01-08 19:22:50.380 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
          2024-01-08 19:22:51.773 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:22:51.993 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
          2024-01-08 19:22:53.384 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
          2024-01-08 19:22:55.223 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
          2024-01-08 19:22:56.578 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
          2024-01-08 19:23:00.218 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
          2024-01-08 19:23:00.980 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
          2024-01-08 19:23:01.774 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:23:02.748 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
          2024-01-08 19:23:11.738 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
          2024-01-08 19:23:11.774 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:23:15.214 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
          2024-01-08 19:23:17.381 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
          2024-01-08 19:23:19.216 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
          2024-01-08 19:23:19.736 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
          2024-01-08 19:23:21.774 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:23:25.396 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
          2024-01-08 19:23:26.181 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
          2024-01-08 19:23:27.398 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
          2024-01-08 19:23:31.774 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:23:35.578 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
          2024-01-08 19:23:38.753 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
          2024-01-08 19:23:38.979 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
          2024-01-08 19:23:41.773 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:23:44.927 - info: admin.0 (631) ==> Connected system.user.admin from ::ffff:192.168.0.132
          2024-01-08 19:23:46.406 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
          2024-01-08 19:23:49.580 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
          2024-01-08 19:23:51.774 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:23:52.004 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
          2024-01-08 19:23:55.380 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
          2024-01-08 19:23:56.766 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
          2024-01-08 19:24:00.577 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
          2024-01-08 19:24:01.775 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:24:02.998 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
          2024-01-08 19:24:04.736 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
          2024-01-08 19:24:05.993 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
          2024-01-08 19:24:06.379 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
          2024-01-08 19:24:09.747 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
          2024-01-08 19:24:10.582 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
          2024-01-08 19:24:11.775 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:24:12.393 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
          2024-01-08 19:24:13.180 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
          2024-01-08 19:24:15.754 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
          2024-01-08 19:24:18.382 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
          2024-01-08 19:24:19.747 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
          2024-01-08 19:24:19.979 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
          2024-01-08 19:24:21.774 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:24:25.018 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
          2024-01-08 19:24:31.775 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:24:41.775 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:24:51.775 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:45:11.851 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:45:21.851 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:45:31.852 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:45:41.854 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:45:51.856 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:46:01.856 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:46:11.858 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:46:21.859 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:46:31.859 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:46:41.860 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:46:51.861 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:47:01.862 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:47:11.864 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:47:21.864 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:47:31.865 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:47:41.866 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:47:51.867 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:48:01.868 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:48:11.869 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:48:21.869 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:48:31.871 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:48:41.872 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:48:51.873 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:49:01.874 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:49:11.875 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:49:21.876 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:49:31.876 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:49:41.877 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:49:51.877 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:50:01.878 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:50:11.879 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:50:21.879 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:50:31.879 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:50:41.881 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:50:51.880 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:51:01.881 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:51:11.882 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:51:21.882 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:51:31.884 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:51:41.884 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:51:51.884 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:52:01.885 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:52:11.886 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:52:21.887 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:52:31.888 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:52:41.888 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:52:51.889 - warn: tapo.0 (176846) Error: Unknown password encryption method
          2024-01-08 19:52:56.427 - info: host.iOProduktiv stopInstance system.adapter.tapo.0 (force=false, process=true)
          2024-01-08 19:52:56.430 - info: tapo.0 (176846) Got terminate signal TERMINATE_YOURSELF
          2024-01-08 19:52:56.430 - info: tapo.0 (176846) terminating
          2024-01-08 19:52:56.431 - info: tapo.0 (176846) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
          2024-01-08 19:52:56.497 - info: host.iOProduktiv stopInstance system.adapter.tapo.0 send kill signal
          2024-01-08 19:52:56.932 - info: tapo.0 (176846) terminating
          2024-01-08 19:52:57.033 - info: host.iOProduktiv instance system.adapter.tapo.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
          2024-01-08 19:52:59.598 - info: host.iOProduktiv instance system.adapter.tapo.0 started with pid 250673
          2024-01-08 19:53:00.507 - info: tapo.0 (250673) starting. Version 0.2.0 (non-npm: TA2k/ioBroker.tapo#f22d791b9b422d6fd3abe8a2f9f7382a7988c965) in /opt/iobroker/node_modules/iobroker.tapo, node: v18.18.2, js-controller: 5.0.17
          2024-01-08 19:53:00.531 - info: tapo.0 (250673) Login tp TAPO App
          2024-01-08 19:53:01.060 - info: tapo.0 (250673) Login succesfull
          2024-01-08 19:53:01.274 - info: tapo.0 (250673) Found 3 devices
          2024-01-08 19:53:01.686 - error: tapo.0 (250673) {"error_code":-20571,"msg":"Device is offline"}
          2024-01-08 19:53:01.687 - info: tapo.0 (250673) Init device 8021CDA220ADD1EE6A8E7E7D0F7DFE861E649CA0 type C310 with ip
          192.168.0.110
          2024-01-08 19:53:01.716 - error: tapo.0 (250673) uncaught exception: Invalid character in header content ["Host"]
          2024-01-08 19:53:01.716 - error: tapo.0 (250673) TypeError: Invalid character in header content ["Host"]
          at ClientRequest.setHeader (node:_http_outgoing:651:3)
          at new ClientRequest (node:_http_client:311:12)
          at Object.request (node:http:100:10)
          at Object.wrappedMethod [as request] (/opt/iobroker/node_modules/@sentry/src/integrations/http.ts:283:1)
          at Cam._requestPart2 (/opt/iobroker/node_modules/onvif/lib/cam.js:276:20)
          at /opt/iobroker/node_modules/onvif/lib/cam.js:247:23
          at Parser. (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:308:18)
          at Parser.emit (node:events:517:28)
          at Parser.emit (node:domain:489:12)
          at SAXParser.onclosetag (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:266:26)
          2024-01-08 19:53:01.716 - error: tapo.0 (250673) Exception-Code: ERR_INVALID_CHAR: Invalid character in header content ["Host"]
          2024-01-08 19:53:01.723 - info: tapo.0 (250673) terminating
          2024-01-08 19:53:01.723 - warn: tapo.0 (250673) Terminated (UNCAUGHT_EXCEPTION): Without reason
          2024-01-08 19:53:01.839 - error: host.iOProduktiv Caught by controller[0]: TypeError: Invalid character in header content ["Host"]
          2024-01-08 19:53:01.839 - error: host.iOProduktiv Caught by controller[0]: at ClientRequest.setHeader (node:_http_outgoing:651:3)
          2024-01-08 19:53:01.839 - error: host.iOProduktiv Caught by controller[0]: at new ClientRequest (node:_http_client:311:12)
          2024-01-08 19:53:01.839 - error: host.iOProduktiv Caught by controller[0]: at Object.request (node:http:100:10)
          2024-01-08 19:53:01.839 - error: host.iOProduktiv Caught by controller[0]: at Object.wrappedMethod [as request] (/opt/iobroker/node_modules/@sentry/src/integrations/http.ts:283:1)
          2024-01-08 19:53:01.839 - error: host.iOProduktiv Caught by controller[0]: at Cam._requestPart2 (/opt/iobroker/node_modules/onvif/lib/cam.js:276:20)
          2024-01-08 19:53:01.839 - error: host.iOProduktiv Caught by controller[0]: at /opt/iobroker/node_modules/onvif/lib/cam.js:247:23
          2024-01-08 19:53:01.839 - error: host.iOProduktiv Caught by controller[0]: at Parser. (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:308:18)
          2024-01-08 19:53:01.839 - error: host.iOProduktiv Caught by controller[0]: at Parser.emit (node:events:517:28)
          2024-01-08 19:53:01.839 - error: host.iOProduktiv Caught by controller[0]: at Parser.emit (node:domain:489:12)
          2024-01-08 19:53:01.839 - error: host.iOProduktiv Caught by controller[0]: at SAXParser.onclosetag (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:266:26) {
          2024-01-08 19:53:01.839 - error: host.iOProduktiv Caught by controller[0]: code: 'ERR_INVALID_CHAR'
          2024-01-08 19:53:01.839 - error: host.iOProduktiv Caught by controller[0]: }
          2024-01-08 19:53:01.839 - error: host.iOProduktiv instance system.adapter.tapo.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
          2024-01-08 19:53:01.839 - info: host.iOProduktiv Restart adapter system.adapter.tapo.0 because enabled
          2024-01-08 19:53:31.964 - info: host.iOProduktiv instance system.adapter.tapo.0 started with pid 251883
          2024-01-08 19:53:32.871 - info: tapo.0 (251883) starting. Version 0.2.0 (non-npm: TA2k/ioBroker.tapo#f22d791b9b422d6fd3abe8a2f9f7382a7988c965) in /opt/iobroker/node_modules/iobroker.tapo, node: v18.18.2, js-controller: 5.0.17
          2024-01-08 19:53:32.895 - info: tapo.0 (251883) Login tp TAPO App
          2024-01-08 19:53:33.349 - info: tapo.0 (251883) Login succesfull
          2024-01-08 19:53:33.548 - info: tapo.0 (251883) Found 3 devices
          2024-01-08 19:53:33.944 - error: tapo.0 (251883) {"error_code":-20571,"msg":"Device is offline"}
          2024-01-08 19:53:33.946 - info: tapo.0 (251883) Init device 8021CDA220ADD1EE6A8E7E7D0F7DFE861E649CA0 type C310 with ip
          192.168.0.110
          2024-01-08 19:53:33.975 - error: tapo.0 (251883) uncaught exception: Invalid character in header content ["Host"]
          2024-01-08 19:53:33.975 - error: tapo.0 (251883) TypeError: Invalid character in header content ["Host"]
          at ClientRequest.setHeader (node:_http_outgoing:651:3)
          at new ClientRequest (node:_http_client:311:12)
          at Object.request (node:http:100:10)
          at Object.wrappedMethod [as request] (/opt/iobroker/node_modules/@sentry/src/integrations/http.ts:283:1)
          at Cam._requestPart2 (/opt/iobroker/node_modules/onvif/lib/cam.js:276:20)
          at /opt/iobroker/node_modules/onvif/lib/cam.js:247:23
          at Parser. (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:308:18)
          at Parser.emit (node:events:517:28)
          at Parser.emit (node:domain:489:12)
          at SAXParser.onclosetag (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:266:26)
          2024-01-08 19:53:33.975 - error: tapo.0 (251883) Exception-Code: ERR_INVALID_CHAR: Invalid character in header content ["Host"]
          2024-01-08 19:53:33.986 - info: tapo.0 (251883) terminating
          2024-01-08 19:53:33.986 - warn: tapo.0 (251883) Terminated (UNCAUGHT_EXCEPTION): Without reason
          2024-01-08 19:53:34.123 - error: host.iOProduktiv Caught by controller[0]: TypeError: Invalid character in header content ["Host"]
          2024-01-08 19:53:34.124 - error: host.iOProduktiv Caught by controller[0]: at ClientRequest.setHeader (node:_http_outgoing:651:3)
          2024-01-08 19:53:34.124 - error: host.iOProduktiv Caught by controller[0]: at new ClientRequest (node:_http_client:311:12)
          2024-01-08 19:53:34.124 - error: host.iOProduktiv Caught by controller[0]: at Object.request (node:http:100:10)
          2024-01-08 19:53:34.124 - error: host.iOProduktiv Caught by controller[0]: at Object.wrappedMethod [as request] (/opt/iobroker/node_modules/@sentry/src/integrations/http.ts:283:1)
          2024-01-08 19:53:34.124 - error: host.iOProduktiv Caught by controller[0]: at Cam._requestPart2 (/opt/iobroker/node_modules/onvif/lib/cam.js:276:20)
          2024-01-08 19:53:34.124 - error: host.iOProduktiv Caught by controller[0]: at /opt/iobroker/node_modules/onvif/lib/cam.js:247:23
          2024-01-08 19:53:34.124 - error: host.iOProduktiv Caught by controller[0]: at Parser. (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:308:18)
          2024-01-08 19:53:34.124 - error: host.iOProduktiv Caught by controller[0]: at Parser.emit (node:events:517:28)
          2024-01-08 19:53:34.124 - error: host.iOProduktiv Caught by controller[0]: at Parser.emit (node:domain:489:12)
          2024-01-08 19:53:34.124 - error: host.iOProduktiv Caught by controller[0]: at SAXParser.onclosetag (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:266:26) {
          2024-01-08 19:53:34.124 - error: host.iOProduktiv Caught by controller[0]: code: 'ERR_INVALID_CHAR'
          2024-01-08 19:53:34.124 - error: host.iOProduktiv Caught by controller[0]: }
          2024-01-08 19:53:34.124 - error: host.iOProduktiv instance system.adapter.tapo.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
          2024-01-08 19:53:34.124 - info: host.iOProduktiv Restart adapter system.adapter.tapo.0 because enabled
          2024-01-08 19:54:04.286 - info: host.iOProduktiv instance system.adapter.tapo.0 started with pid 253103
          2024-01-08 19:54:05.186 - info: tapo.0 (253103) starting. Version 0.2.0 (non-npm: TA2k/ioBroker.tapo#f22d791b9b422d6fd3abe8a2f9f7382a7988c965) in /opt/iobroker/node_modules/iobroker.tapo, node: v18.18.2, js-controller: 5.0.17
          2024-01-08 19:54:05.208 - info: tapo.0 (253103) Login tp TAPO App
          2024-01-08 19:54:05.685 - info: tapo.0 (253103) Login succesfull
          2024-01-08 19:54:05.915 - info: tapo.0 (253103) Found 3 devices
          2024-01-08 19:54:06.352 - error: tapo.0 (253103) {"error_code":-20571,"msg":"Device is offline"}
          2024-01-08 19:54:06.354 - info: tapo.0 (253103) Init device 8021CDA220ADD1EE6A8E7E7D0F7DFE861E649CA0 type C310 with ip
          192.168.0.110
          2024-01-08 19:54:06.385 - error: tapo.0 (253103) uncaught exception: Invalid character in header content ["Host"]
          2024-01-08 19:54:06.385 - error: tapo.0 (253103) TypeError: Invalid character in header content ["Host"]
          at ClientRequest.setHeader (node:_http_outgoing:651:3)
          at new ClientRequest (node:_http_client:311:12)
          at Object.request (node:http:100:10)
          at Object.wrappedMethod [as request] (/opt/iobroker/node_modules/@sentry/src/integrations/http.ts:283:1)
          at Cam._requestPart2 (/opt/iobroker/node_modules/onvif/lib/cam.js:276:20)
          at /opt/iobroker/node_modules/onvif/lib/cam.js:247:23
          at Parser. (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:308:18)
          at Parser.emit (node:events:517:28)
          at Parser.emit (node:domain:489:12)
          at SAXParser.onclosetag (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:266:26)
          2024-01-08 19:54:06.385 - error: tapo.0 (253103) Exception-Code: ERR_INVALID_CHAR: Invalid character in header content ["Host"]
          2024-01-08 19:54:06.394 - info: tapo.0 (253103) terminating
          2024-01-08 19:54:06.394 - warn: tapo.0 (253103) Terminated (UNCAUGHT_EXCEPTION): Without reason
          2024-01-08 19:54:06.514 - error: host.iOProduktiv Caught by controller[0]: TypeError: Invalid character in header content ["Host"]
          2024-01-08 19:54:06.514 - error: host.iOProduktiv Caught by controller[0]: at ClientRequest.setHeader (node:_http_outgoing:651:3)
          2024-01-08 19:54:06.514 - error: host.iOProduktiv Caught by controller[0]: at new ClientRequest (node:_http_client:311:12)
          2024-01-08 19:54:06.514 - error: host.iOProduktiv Caught by controller[0]: at Object.request (node:http:100:10)
          2024-01-08 19:54:06.514 - error: host.iOProduktiv Caught by controller[0]: at Object.wrappedMethod [as request] (/opt/iobroker/node_modules/@sentry/src/integrations/http.ts:283:1)
          2024-01-08 19:54:06.514 - error: host.iOProduktiv Caught by controller[0]: at Cam._requestPart2 (/opt/iobroker/node_modules/onvif/lib/cam.js:276:20)
          2024-01-08 19:54:06.514 - error: host.iOProduktiv Caught by controller[0]: at /opt/iobroker/node_modules/onvif/lib/cam.js:247:23
          2024-01-08 19:54:06.515 - error: host.iOProduktiv Caught by controller[0]: at Parser. (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:308:18)
          2024-01-08 19:54:06.515 - error: host.iOProduktiv Caught by controller[0]: at Parser.emit (node:events:517:28)
          2024-01-08 19:54:06.515 - error: host.iOProduktiv Caught by controller[0]: at Parser.emit (node:domain:489:12)
          2024-01-08 19:54:06.515 - error: host.iOProduktiv Caught by controller[0]: at SAXParser.onclosetag (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:266:26) {
          2024-01-08 19:54:06.515 - error: host.iOProduktiv Caught by controller[0]: code: 'ERR_INVALID_CHAR'
          2024-01-08 19:54:06.515 - error: host.iOProduktiv Caught by controller[0]: }
          2024-01-08 19:54:06.515 - error: host.iOProduktiv instance system.adapter.tapo.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
          2024-01-08 19:54:06.515 - info: host.iOProduktiv Restart adapter system.adapter.tapo.0 because enabled
          2024-01-08 19:54:36.621 - info: host.iOProduktiv instance system.adapter.tapo.0 started with pid 254814
          2024-01-08 19:54:37.530 - info: tapo.0 (254814) starting. Version 0.2.0 (non-npm: TA2k/ioBroker.tapo#f22d791b9b422d6fd3abe8a2f9f7382a7988c965) in /opt/iobroker/node_modules/iobroker.tapo, node: v18.18.2, js-controller: 5.0.17
          2024-01-08 19:54:37.554 - info: tapo.0 (254814) Login tp TAPO App
          2024-01-08 19:54:38.140 - info: tapo.0 (254814) Login succesfull
          2024-01-08 19:54:38.442 - info: tapo.0 (254814) Found 3 devices
          2024-01-08 19:54:38.880 - error: tapo.0 (254814) {"error_code":-20571,"msg":"Device is offline"}
          2024-01-08 19:54:38.882 - info: tapo.0 (254814) Init device 8021CDA220ADD1EE6A8E7E7D0F7DFE861E649CA0 type C310 with ip
          192.168.0.110
          2024-01-08 19:54:38.908 - error: tapo.0 (254814) uncaught exception: Invalid character in header content ["Host"]
          2024-01-08 19:54:38.909 - error: tapo.0 (254814) TypeError: Invalid character in header content ["Host"]
          at ClientRequest.setHeader (node:_http_outgoing:651:3)
          at new ClientRequest (node:_http_client:311:12)
          at Object.request (node:http:100:10)
          at Object.wrappedMethod [as request] (/opt/iobroker/node_modules/@sentry/src/integrations/http.ts:283:1)
          at Cam._requestPart2 (/opt/iobroker/node_modules/onvif/lib/cam.js:276:20)
          at /opt/iobroker/node_modules/onvif/lib/cam.js:247:23
          at Parser. (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:308:18)
          at Parser.emit (node:events:517:28)
          at Parser.emit (node:domain:489:12)
          at SAXParser.onclosetag (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:266:26)
          2024-01-08 19:54:38.909 - error: tapo.0 (254814) Exception-Code: ERR_INVALID_CHAR: Invalid character in header content ["Host"]
          2024-01-08 19:54:38.916 - info: tapo.0 (254814) terminating
          2024-01-08 19:54:38.916 - warn: tapo.0 (254814) Terminated (UNCAUGHT_EXCEPTION): Without reason
          2024-01-08 19:54:39.037 - error: host.iOProduktiv Caught by controller[0]: TypeError: Invalid character in header content ["Host"]
          2024-01-08 19:54:39.037 - error: host.iOProduktiv Caught by controller[0]: at ClientRequest.setHeader (node:_http_outgoing:651:3)
          2024-01-08 19:54:39.037 - error: host.iOProduktiv Caught by controller[0]: at new ClientRequest (node:_http_client:311:12)
          2024-01-08 19:54:39.037 - error: host.iOProduktiv Caught by controller[0]: at Object.request (node:http:100:10)
          2024-01-08 19:54:39.037 - error: host.iOProduktiv Caught by controller[0]: at Object.wrappedMethod [as request] (/opt/iobroker/node_modules/@sentry/src/integrations/http.ts:283:1)
          2024-01-08 19:54:39.037 - error: host.iOProduktiv Caught by controller[0]: at Cam._requestPart2 (/opt/iobroker/node_modules/onvif/lib/cam.js:276:20)
          2024-01-08 19:54:39.037 - error: host.iOProduktiv Caught by controller[0]: at /opt/iobroker/node_modules/onvif/lib/cam.js:247:23
          2024-01-08 19:54:39.037 - error: host.iOProduktiv Caught by controller[0]: at Parser. (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:308:18)
          2024-01-08 19:54:39.037 - error: host.iOProduktiv Caught by controller[0]: at Parser.emit (node:events:517:28)
          2024-01-08 19:54:39.037 - error: host.iOProduktiv Caught by controller[0]: at Parser.emit (node:domain:489:12)
          2024-01-08 19:54:39.037 - error: host.iOProduktiv Caught by controller[0]: at SAXParser.onclosetag (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:266:26) {
          2024-01-08 19:54:39.037 - error: host.iOProduktiv Caught by controller[0]: code: 'ERR_INVALID_CHAR'
          2024-01-08 19:54:39.037 - error: host.iOProduktiv Caught by controller[0]: }
          2024-01-08 19:54:39.037 - error: host.iOProduktiv instance system.adapter.tapo.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
          2024-01-08 19:54:39.037 - info: host.iOProduktiv Restart adapter system.adapter.tapo.0 because enabled
          2024-01-08 19:55:00.023 - info: host.iOProduktiv instance system.adapter.ical.0 started with pid 255316
          2024-01-08 19:55:09.150 - info: host.iOProduktiv instance system.adapter.tapo.0 started with pid 256045
          2024-01-08 19:55:09.990 - info: tapo.0 (256045) starting. Version 0.2.0 (non-npm: TA2k/ioBroker.tapo#f22d791b9b422d6fd3abe8a2f9f7382a7988c965) in /opt/iobroker/node_modules/iobroker.tapo, node: v18.18.2, js-controller: 5.0.17
          2024-01-08 19:55:10.015 - info: tapo.0 (256045) Login tp TAPO App
          2024-01-08 19:55:10.501 - info: tapo.0 (256045) Login succesfull
          2024-01-08 19:55:10.742 - info: tapo.0 (256045) Found 3 devices
          2024-01-08 19:55:11.136 - error: tapo.0 (256045) {"error_code":-20571,"msg":"Device is offline"}
          2024-01-08 19:55:11.137 - info: tapo.0 (256045) Init device 8021CDA220ADD1EE6A8E7E7D0F7DFE861E649CA0 type C310 with ip
          192.168.0.110
          2024-01-08 19:55:11.166 - error: tapo.0 (256045) uncaught exception: Invalid character in header content ["Host"]
          2024-01-08 19:55:11.166 - error: tapo.0 (256045) TypeError: Invalid character in header content ["Host"]
          at ClientRequest.setHeader (node:_http_outgoing:651:3)
          at new ClientRequest (node:_http_client:311:12)
          at Object.request (node:http:100:10)
          at Object.wrappedMethod [as request] (/opt/iobroker/node_modules/@sentry/src/integrations/http.ts:283:1)
          at Cam._requestPart2 (/opt/iobroker/node_modules/onvif/lib/cam.js:276:20)
          at /opt/iobroker/node_modules/onvif/lib/cam.js:247:23
          at Parser. (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:308:18)
          at Parser.emit (node:events:517:28)
          at Parser.emit (node:domain:489:12)
          at SAXParser.onclosetag (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:266:26)
          2024-01-08 19:55:11.166 - error: tapo.0 (256045) Exception-Code: ERR_INVALID_CHAR: Invalid character in header content ["Host"]
          2024-01-08 19:55:11.174 - info: tapo.0 (256045) terminating
          2024-01-08 19:55:11.174 - warn: tapo.0 (256045) Terminated (UNCAUGHT_EXCEPTION): Without reason
          2024-01-08 19:55:11.303 - error: host.iOProduktiv Caught by controller[0]: TypeError: Invalid character in header content ["Host"]
          2024-01-08 19:55:11.303 - error: host.iOProduktiv Caught by controller[0]: at ClientRequest.setHeader (node:_http_outgoing:651:3)
          2024-01-08 19:55:11.303 - error: host.iOProduktiv Caught by controller[0]: at new ClientRequest (node:_http_client:311:12)
          2024-01-08 19:55:11.303 - error: host.iOProduktiv Caught by controller[0]: at Object.request (node:http:100:10)
          2024-01-08 19:55:11.303 - error: host.iOProduktiv Caught by controller[0]: at Object.wrappedMethod [as request] (/opt/iobroker/node_modules/@sentry/src/integrations/http.ts:283:1)
          2024-01-08 19:55:11.303 - error: host.iOProduktiv Caught by controller[0]: at Cam._requestPart2 (/opt/iobroker/node_modules/onvif/lib/cam.js:276:20)
          2024-01-08 19:55:11.303 - error: host.iOProduktiv Caught by controller[0]: at /opt/iobroker/node_modules/onvif/lib/cam.js:247:23
          2024-01-08 19:55:11.303 - error: host.iOProduktiv Caught by controller[0]: at Parser. (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:308:18)
          2024-01-08 19:55:11.303 - error: host.iOProduktiv Caught by controller[0]: at Parser.emit (node:events:517:28)
          2024-01-08 19:55:11.303 - error: host.iOProduktiv Caught by controller[0]: at Parser.emit (node:domain:489:12)
          2024-01-08 19:55:11.303 - error: host.iOProduktiv Caught by controller[0]: at SAXParser.onclosetag (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:266:26) {
          2024-01-08 19:55:11.304 - error: host.iOProduktiv Caught by controller[0]: code: 'ERR_INVALID_CHAR'
          2024-01-08 19:55:11.304 - error: host.iOProduktiv Caught by controller[0]: }
          2024-01-08 19:55:11.304 - error: host.iOProduktiv instance system.adapter.tapo.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
          2024-01-08 19:55:11.304 - info: host.iOProduktiv Restart adapter system.adapter.tapo.0 because enabled
          2024-01-08 19:55:41.457 - info: host.iOProduktiv instance system.adapter.tapo.0 started with pid 257259
          2024-01-08 19:55:42.245 - info: tapo.0 (257259) starting. Version 0.2.0 (non-npm: TA2k/ioBroker.tapo#f22d791b9b422d6fd3abe8a2f9f7382a7988c965) in /opt/iobroker/node_modules/iobroker.tapo, node: v18.18.2, js-controller: 5.0.17
          2024-01-08 19:55:42.268 - info: tapo.0 (257259) Login tp TAPO App
          2024-01-08 19:55:42.726 - info: tapo.0 (257259) Login succesfull
          2024-01-08 19:55:42.944 - info: tapo.0 (257259) Found 3 devices
          2024-01-08 19:55:43.394 - error: tapo.0 (257259) {"error_code":-20571,"msg":"Device is offline"}
          2024-01-08 19:55:43.396 - info: tapo.0 (257259) Init device 8021CDA220ADD1EE6A8E7E7D0F7DFE861E649CA0 type C310 with ip
          192.168.0.110
          2024-01-08 19:55:43.424 - error: tapo.0 (257259) uncaught exception: Invalid character in header content ["Host"]
          2024-01-08 19:55:43.425 - error: tapo.0 (257259) TypeError: Invalid character in header content ["Host"]
          at ClientRequest.setHeader (node:_http_outgoing:651:3)
          at new ClientRequest (node:_http_client:311:12)
          at Object.request (node:http:100:10)
          at Object.wrappedMethod [as request] (/opt/iobroker/node_modules/@sentry/src/integrations/http.ts:283:1)
          at Cam._requestPart2 (/opt/iobroker/node_modules/onvif/lib/cam.js:276:20)
          at /opt/iobroker/node_modules/onvif/lib/cam.js:247:23
          at Parser. (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:308:18)
          at Parser.emit (node:events:517:28)
          at Parser.emit (node:domain:489:12)
          at SAXParser.onclosetag (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:266:26)
          2024-01-08 19:55:43.425 - error: tapo.0 (257259) Exception-Code: ERR_INVALID_CHAR: Invalid character in header content ["Host"]
          2024-01-08 19:55:43.432 - info: tapo.0 (257259) terminating
          2024-01-08 19:55:43.433 - warn: tapo.0 (257259) Terminated (UNCAUGHT_EXCEPTION): Without reason
          2024-01-08 19:55:43.556 - error: host.iOProduktiv Caught by controller[0]: TypeError: Invalid character in header content ["Host"]
          2024-01-08 19:55:43.556 - error: host.iOProduktiv Caught by controller[0]: at ClientRequest.setHeader (node:_http_outgoing:651:3)
          2024-01-08 19:55:43.556 - error: host.iOProduktiv Caught by controller[0]: at new ClientRequest (node:_http_client:311:12)
          2024-01-08 19:55:43.556 - error: host.iOProduktiv Caught by controller[0]: at Object.request (node:http:100:10)
          2024-01-08 19:55:43.556 - error: host.iOProduktiv Caught by controller[0]: at Object.wrappedMethod [as request] (/opt/iobroker/node_modules/@sentry/src/integrations/http.ts:283:1)
          2024-01-08 19:55:43.556 - error: host.iOProduktiv Caught by controller[0]: at Cam._requestPart2 (/opt/iobroker/node_modules/onvif/lib/cam.js:276:20)
          2024-01-08 19:55:43.556 - error: host.iOProduktiv Caught by controller[0]: at /opt/iobroker/node_modules/onvif/lib/cam.js:247:23
          2024-01-08 19:55:43.556 - error: host.iOProduktiv Caught by controller[0]: at Parser. (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:308:18)
          2024-01-08 19:55:43.556 - error: host.iOProduktiv Caught by controller[0]: at Parser.emit (node:events:517:28)
          2024-01-08 19:55:43.556 - error: host.iOProduktiv Caught by controller[0]: at Parser.emit (node:domain:489:12)
          2024-01-08 19:55:43.556 - error: host.iOProduktiv Caught by controller[0]: at SAXParser.onclosetag (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:266:26) {
          2024-01-08 19:55:43.556 - error: host.iOProduktiv Caught by controller[0]: code: 'ERR_INVALID_CHAR'
          2024-01-08 19:55:43.556 - error: host.iOProduktiv Caught by controller[0]: }
          2024-01-08 19:55:43.556 - error: host.iOProduktiv instance system.adapter.tapo.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
          2024-01-08 19:55:43.556 - info: host.iOProduktiv Restart adapter system.adapter.tapo.0 because enabled
          2024-01-08 19:55:48.775 - info: host.iOProduktiv "system.adapter.tapo.0" disabled
          2024-01-08 19:56:14.442 - error: tapo.0 (258480) adapter disabled
          2024-01-08 19:56:14.489 - warn: tapo.0 (258480) Terminated (NO_ADAPTER_CONFIG_FOUND): Without reason
          2024-01-08 19:56:15.093 - error: host.iOProduktiv instance system.adapter.tapo.0 terminated with code 3 (NO_ADAPTER_CONFIG_FOUND)
          2024-01-08 19:56:15.093 - info: host.iOProduktiv Do not restart adapter system.adapter.tapo.0 because disabled or deleted
          2024-01-08 19:56:39.588 - info: admin.0 (631) <== Disconnect system.user.admin from ::ffff:192.168.0.132 admin
          2024-01-08 19:56:40.869 - info: admin.0 (631) ==> Connected system.user.admin from ::ffff:192.168.0.132
          

          Onvis schaue ich mir paralell einmal an, andernfalls schicke ich die Cam retour nach A......zonien.

          Danke für deine Arbeit!!!!!

          T 1 Antwort Letzte Antwort
          0
          • Walter WhiteW Walter White

            @tombox Werden die Steckdosen ohne diesen fix nicht mehr laufen?
            Screenshot_2024-01-09-23-18-09-950_com.android.chrome-edit.jpg
            Gibt es kein Plan b auf GitHub wenn jemand plötzlich nicht mehr ist?

            T Offline
            T Offline
            tombox
            schrieb am zuletzt editiert von
            #350

            @walter-white Das ist korrekt ich habe keine Steckdosen kann es nicht implementieren muss also auf Homebridge warten
            oder halt auf home Assistent wechseln

            Walter WhiteW 1 Antwort Letzte Antwort
            1
            • metaxaM metaxa

              @tombox sagte in Test Adapter TP-Link Tapo:

              @metaxa Genaue Logs wären gut und du kannst auch den onvis adapter probieren

              Hier das Log. Im ersen Anlauf mit dem freigegebenen Konto der neuen CAM, dann die beiden IP Adressen der andern Cam´s manuell eingetragen (jeweils ein anderes freigegebenes Konto). Was mir noch fehlen würde, EIN freigegebenes Konto für alle Cams.

              2024-01-08 18:56:28.919 - info: host.iOProduktiv instance system.adapter.tapo.0 started with pid 113047
              2024-01-08 18:56:29.913 - info: tapo.0 (113047) starting. Version 0.2.0 (non-npm: TA2k/ioBroker.tapo#f22d791b9b422d6fd3abe8a2f9f7382a7988c965) in /opt/iobroker/node_modules/iobroker.tapo, node: v18.18.2, js-controller: 5.0.17
              2024-01-08 18:56:29.927 - error: tapo.0 (113047) Please set username and password in the instance settings
              2024-01-08 19:02:30.919 - info: host.iOProduktiv stopInstance system.adapter.tapo.0 (force=false, process=true)
              2024-01-08 19:02:30.921 - info: tapo.0 (113047) Got terminate signal TERMINATE_YOURSELF
              2024-01-08 19:02:30.922 - info: tapo.0 (113047) terminating
              2024-01-08 19:02:30.922 - info: tapo.0 (113047) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
              2024-01-08 19:02:30.993 - info: host.iOProduktiv stopInstance system.adapter.tapo.0 send kill signal
              2024-01-08 19:02:31.423 - info: tapo.0 (113047) terminating
              2024-01-08 19:02:31.520 - info: host.iOProduktiv instance system.adapter.tapo.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
              2024-01-08 19:02:34.099 - info: host.iOProduktiv instance system.adapter.tapo.0 started with pid 128175
              2024-01-08 19:02:35.050 - info: tapo.0 (128175) starting. Version 0.2.0 (non-npm: TA2k/ioBroker.tapo#f22d791b9b422d6fd3abe8a2f9f7382a7988c965) in /opt/iobroker/node_modules/iobroker.tapo, node: v18.18.2, js-controller: 5.0.17
              2024-01-08 19:02:35.123 - info: tapo.0 (128175) Login tp TAPO App
              2024-01-08 19:02:35.504 - info: tapo.0 (128175) Login succesfull
              2024-01-08 19:02:35.740 - info: tapo.0 (128175) Found 3 devices
              2024-01-08 19:02:36.239 - error: tapo.0 (128175) {"error_code":-20571,"msg":"Device is offline"}
              2024-01-08 19:02:36.245 - warn: tapo.0 (128175) No IP found for 8021CDA220ADD1EE6A8E7E7D0F7DFE861E649CA0 put the device online or set the ip state manually
              2024-01-08 19:02:36.488 - info: tapo.0 (128175) Init device 80219D887A52D32D03212C4C2DE37E4D21EC8028 type C520WS 1.0 with ip 192.168.0.220
              2024-01-08 19:02:36.631 - info: tapo.0 (128175) 80219D887A52D32D03212C4C2DE37E4D21EC8028 Received device info {"manufacturer":"tp-link","model":"Tapo C520WS","firmwareVersion":"1.1.4 Build 230922 Rel.57957n","serialNumber":"31d87f97","hardwareId":1}
              2024-01-08 19:02:36.700 - info: tapo.0 (128175) Initialized 80219D887A52D32D03212C4C2DE37E4D21EC8028
              2024-01-08 19:02:37.151 - error: tapo.0 (128175) {"error_code":-20571,"msg":"Device is offline"}
              2024-01-08 19:02:37.203 - warn: tapo.0 (128175) No IP found for 8021314EFB57E17626EC16DBDB2A31A51E64292E put the device online or set the ip state manually
              2024-01-08 19:02:37.257 - info: tapo.0 (128175) Wait for connections
              2024-01-08 19:02:47.318 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:02:57.321 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:03:07.321 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:03:17.322 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:03:27.322 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:03:37.322 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:03:47.322 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:03:57.323 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:04:07.323 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:04:17.323 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:04:27.324 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:04:37.324 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:04:47.323 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:04:57.323 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:05:17.323 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:05:27.324 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:05:37.324 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:05:47.326 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:05:57.326 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:06:07.326 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:06:17.325 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:06:27.325 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:06:37.325 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:06:47.326 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:06:57.328 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:07:07.329 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:07:17.330 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:07:27.330 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:07:37.330 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:07:47.332 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:07:57.332 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:08:07.334 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:08:17.334 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:08:27.335 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:08:37.336 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:08:47.337 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:08:57.339 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:09:07.340 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:09:17.340 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:09:27.341 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:09:37.342 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:09:47.343 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:09:57.345 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:10:07.345 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:10:17.347 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:10:27.347 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:10:37.348 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:10:47.348 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:10:57.349 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:11:07.351 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:11:17.351 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:11:20.962 - error: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:11:27.351 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:11:30.895 - error: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:11:37.353 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:11:42.277 - error: tapo.0 (128175) Device 80219D887A52D32D03212C4C2DE37E4D21EC8028 has no command refresh
              2024-01-08 19:11:47.353 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:11:52.485 - error: tapo.0 (128175) Device 80219D887A52D32D03212C4C2DE37E4D21EC8028 has no command refresh
              2024-01-08 19:11:57.355 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:12:07.355 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:12:17.356 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:12:27.357 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:12:37.358 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:12:42.876 - error: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:12:47.359 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:12:52.128 - error: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:12:57.361 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:13:07.361 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:13:17.363 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:13:27.363 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:13:37.363 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:13:47.363 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:13:57.364 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:14:07.364 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:14:17.365 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:14:27.365 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:14:37.365 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:14:47.367 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:14:57.368 - warn: tapo.0 (128175) Error: Unknown password encryption method
              2024-01-08 19:22:40.707 - error: tapo.0 (176846) {"error_code":-20571,"msg":"Device is offline"}
              2024-01-08 19:22:40.709 - warn: tapo.0 (176846) No IP found for 8021CDA220ADD1EE6A8E7E7D0F7DFE861E649CA0 put the device online or set the ip state manually
              2024-01-08 19:22:40.941 - info: tapo.0 (176846) Init device 80219D887A52D32D03212C4C2DE37E4D21EC8028 type C520WS 1.0 with ip 192.168.0.220
              2024-01-08 19:22:41.072 - info: tapo.0 (176846) 80219D887A52D32D03212C4C2DE37E4D21EC8028 Received device info {"manufacturer":"tp-link","model":"Tapo C520WS","firmwareVersion":"1.1.4 Build 230922 Rel.57957n","serialNumber":"31d87f97","hardwareId":1}
              2024-01-08 19:22:41.076 - info: tapo.0 (176846) Initialized 80219D887A52D32D03212C4C2DE37E4D21EC8028
              2024-01-08 19:22:41.153 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
              2024-01-08 19:22:41.503 - error: tapo.0 (176846) {"error_code":-20571,"msg":"Device is offline"}
              2024-01-08 19:22:41.508 - warn: tapo.0 (176846) No IP found for 8021314EFB57E17626EC16DBDB2A31A51E64292E put the device online or set the ip state manually
              2024-01-08 19:22:41.688 - info: tapo.0 (176846) Wait for connections
              2024-01-08 19:22:41.802 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
              2024-01-08 19:22:42.980 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
              2024-01-08 19:22:43.998 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
              2024-01-08 19:22:45.380 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
              2024-01-08 19:22:48.993 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
              2024-01-08 19:22:49.182 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
              2024-01-08 19:22:50.216 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
              2024-01-08 19:22:50.380 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
              2024-01-08 19:22:51.773 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:22:51.993 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
              2024-01-08 19:22:53.384 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
              2024-01-08 19:22:55.223 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
              2024-01-08 19:22:56.578 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
              2024-01-08 19:23:00.218 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
              2024-01-08 19:23:00.980 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
              2024-01-08 19:23:01.774 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:23:02.748 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
              2024-01-08 19:23:11.738 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
              2024-01-08 19:23:11.774 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:23:15.214 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
              2024-01-08 19:23:17.381 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
              2024-01-08 19:23:19.216 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
              2024-01-08 19:23:19.736 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
              2024-01-08 19:23:21.774 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:23:25.396 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
              2024-01-08 19:23:26.181 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
              2024-01-08 19:23:27.398 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
              2024-01-08 19:23:31.774 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:23:35.578 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
              2024-01-08 19:23:38.753 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
              2024-01-08 19:23:38.979 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
              2024-01-08 19:23:41.773 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:23:44.927 - info: admin.0 (631) ==> Connected system.user.admin from ::ffff:192.168.0.132
              2024-01-08 19:23:46.406 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
              2024-01-08 19:23:49.580 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
              2024-01-08 19:23:51.774 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:23:52.004 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
              2024-01-08 19:23:55.380 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
              2024-01-08 19:23:56.766 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
              2024-01-08 19:24:00.577 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
              2024-01-08 19:24:01.775 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:24:02.998 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
              2024-01-08 19:24:04.736 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
              2024-01-08 19:24:05.993 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
              2024-01-08 19:24:06.379 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
              2024-01-08 19:24:09.747 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
              2024-01-08 19:24:10.582 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
              2024-01-08 19:24:11.775 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:24:12.393 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
              2024-01-08 19:24:13.180 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
              2024-01-08 19:24:15.754 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
              2024-01-08 19:24:18.382 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
              2024-01-08 19:24:19.747 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
              2024-01-08 19:24:19.979 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" true
              2024-01-08 19:24:21.774 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:24:25.018 - info: tapo.0 (176846) [C520WS 1.0] "Motion detected" false
              2024-01-08 19:24:31.775 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:24:41.775 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:24:51.775 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:45:11.851 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:45:21.851 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:45:31.852 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:45:41.854 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:45:51.856 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:46:01.856 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:46:11.858 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:46:21.859 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:46:31.859 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:46:41.860 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:46:51.861 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:47:01.862 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:47:11.864 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:47:21.864 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:47:31.865 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:47:41.866 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:47:51.867 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:48:01.868 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:48:11.869 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:48:21.869 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:48:31.871 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:48:41.872 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:48:51.873 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:49:01.874 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:49:11.875 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:49:21.876 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:49:31.876 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:49:41.877 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:49:51.877 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:50:01.878 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:50:11.879 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:50:21.879 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:50:31.879 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:50:41.881 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:50:51.880 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:51:01.881 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:51:11.882 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:51:21.882 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:51:31.884 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:51:41.884 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:51:51.884 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:52:01.885 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:52:11.886 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:52:21.887 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:52:31.888 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:52:41.888 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:52:51.889 - warn: tapo.0 (176846) Error: Unknown password encryption method
              2024-01-08 19:52:56.427 - info: host.iOProduktiv stopInstance system.adapter.tapo.0 (force=false, process=true)
              2024-01-08 19:52:56.430 - info: tapo.0 (176846) Got terminate signal TERMINATE_YOURSELF
              2024-01-08 19:52:56.430 - info: tapo.0 (176846) terminating
              2024-01-08 19:52:56.431 - info: tapo.0 (176846) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
              2024-01-08 19:52:56.497 - info: host.iOProduktiv stopInstance system.adapter.tapo.0 send kill signal
              2024-01-08 19:52:56.932 - info: tapo.0 (176846) terminating
              2024-01-08 19:52:57.033 - info: host.iOProduktiv instance system.adapter.tapo.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
              2024-01-08 19:52:59.598 - info: host.iOProduktiv instance system.adapter.tapo.0 started with pid 250673
              2024-01-08 19:53:00.507 - info: tapo.0 (250673) starting. Version 0.2.0 (non-npm: TA2k/ioBroker.tapo#f22d791b9b422d6fd3abe8a2f9f7382a7988c965) in /opt/iobroker/node_modules/iobroker.tapo, node: v18.18.2, js-controller: 5.0.17
              2024-01-08 19:53:00.531 - info: tapo.0 (250673) Login tp TAPO App
              2024-01-08 19:53:01.060 - info: tapo.0 (250673) Login succesfull
              2024-01-08 19:53:01.274 - info: tapo.0 (250673) Found 3 devices
              2024-01-08 19:53:01.686 - error: tapo.0 (250673) {"error_code":-20571,"msg":"Device is offline"}
              2024-01-08 19:53:01.687 - info: tapo.0 (250673) Init device 8021CDA220ADD1EE6A8E7E7D0F7DFE861E649CA0 type C310 with ip
              192.168.0.110
              2024-01-08 19:53:01.716 - error: tapo.0 (250673) uncaught exception: Invalid character in header content ["Host"]
              2024-01-08 19:53:01.716 - error: tapo.0 (250673) TypeError: Invalid character in header content ["Host"]
              at ClientRequest.setHeader (node:_http_outgoing:651:3)
              at new ClientRequest (node:_http_client:311:12)
              at Object.request (node:http:100:10)
              at Object.wrappedMethod [as request] (/opt/iobroker/node_modules/@sentry/src/integrations/http.ts:283:1)
              at Cam._requestPart2 (/opt/iobroker/node_modules/onvif/lib/cam.js:276:20)
              at /opt/iobroker/node_modules/onvif/lib/cam.js:247:23
              at Parser. (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:308:18)
              at Parser.emit (node:events:517:28)
              at Parser.emit (node:domain:489:12)
              at SAXParser.onclosetag (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:266:26)
              2024-01-08 19:53:01.716 - error: tapo.0 (250673) Exception-Code: ERR_INVALID_CHAR: Invalid character in header content ["Host"]
              2024-01-08 19:53:01.723 - info: tapo.0 (250673) terminating
              2024-01-08 19:53:01.723 - warn: tapo.0 (250673) Terminated (UNCAUGHT_EXCEPTION): Without reason
              2024-01-08 19:53:01.839 - error: host.iOProduktiv Caught by controller[0]: TypeError: Invalid character in header content ["Host"]
              2024-01-08 19:53:01.839 - error: host.iOProduktiv Caught by controller[0]: at ClientRequest.setHeader (node:_http_outgoing:651:3)
              2024-01-08 19:53:01.839 - error: host.iOProduktiv Caught by controller[0]: at new ClientRequest (node:_http_client:311:12)
              2024-01-08 19:53:01.839 - error: host.iOProduktiv Caught by controller[0]: at Object.request (node:http:100:10)
              2024-01-08 19:53:01.839 - error: host.iOProduktiv Caught by controller[0]: at Object.wrappedMethod [as request] (/opt/iobroker/node_modules/@sentry/src/integrations/http.ts:283:1)
              2024-01-08 19:53:01.839 - error: host.iOProduktiv Caught by controller[0]: at Cam._requestPart2 (/opt/iobroker/node_modules/onvif/lib/cam.js:276:20)
              2024-01-08 19:53:01.839 - error: host.iOProduktiv Caught by controller[0]: at /opt/iobroker/node_modules/onvif/lib/cam.js:247:23
              2024-01-08 19:53:01.839 - error: host.iOProduktiv Caught by controller[0]: at Parser. (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:308:18)
              2024-01-08 19:53:01.839 - error: host.iOProduktiv Caught by controller[0]: at Parser.emit (node:events:517:28)
              2024-01-08 19:53:01.839 - error: host.iOProduktiv Caught by controller[0]: at Parser.emit (node:domain:489:12)
              2024-01-08 19:53:01.839 - error: host.iOProduktiv Caught by controller[0]: at SAXParser.onclosetag (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:266:26) {
              2024-01-08 19:53:01.839 - error: host.iOProduktiv Caught by controller[0]: code: 'ERR_INVALID_CHAR'
              2024-01-08 19:53:01.839 - error: host.iOProduktiv Caught by controller[0]: }
              2024-01-08 19:53:01.839 - error: host.iOProduktiv instance system.adapter.tapo.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
              2024-01-08 19:53:01.839 - info: host.iOProduktiv Restart adapter system.adapter.tapo.0 because enabled
              2024-01-08 19:53:31.964 - info: host.iOProduktiv instance system.adapter.tapo.0 started with pid 251883
              2024-01-08 19:53:32.871 - info: tapo.0 (251883) starting. Version 0.2.0 (non-npm: TA2k/ioBroker.tapo#f22d791b9b422d6fd3abe8a2f9f7382a7988c965) in /opt/iobroker/node_modules/iobroker.tapo, node: v18.18.2, js-controller: 5.0.17
              2024-01-08 19:53:32.895 - info: tapo.0 (251883) Login tp TAPO App
              2024-01-08 19:53:33.349 - info: tapo.0 (251883) Login succesfull
              2024-01-08 19:53:33.548 - info: tapo.0 (251883) Found 3 devices
              2024-01-08 19:53:33.944 - error: tapo.0 (251883) {"error_code":-20571,"msg":"Device is offline"}
              2024-01-08 19:53:33.946 - info: tapo.0 (251883) Init device 8021CDA220ADD1EE6A8E7E7D0F7DFE861E649CA0 type C310 with ip
              192.168.0.110
              2024-01-08 19:53:33.975 - error: tapo.0 (251883) uncaught exception: Invalid character in header content ["Host"]
              2024-01-08 19:53:33.975 - error: tapo.0 (251883) TypeError: Invalid character in header content ["Host"]
              at ClientRequest.setHeader (node:_http_outgoing:651:3)
              at new ClientRequest (node:_http_client:311:12)
              at Object.request (node:http:100:10)
              at Object.wrappedMethod [as request] (/opt/iobroker/node_modules/@sentry/src/integrations/http.ts:283:1)
              at Cam._requestPart2 (/opt/iobroker/node_modules/onvif/lib/cam.js:276:20)
              at /opt/iobroker/node_modules/onvif/lib/cam.js:247:23
              at Parser. (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:308:18)
              at Parser.emit (node:events:517:28)
              at Parser.emit (node:domain:489:12)
              at SAXParser.onclosetag (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:266:26)
              2024-01-08 19:53:33.975 - error: tapo.0 (251883) Exception-Code: ERR_INVALID_CHAR: Invalid character in header content ["Host"]
              2024-01-08 19:53:33.986 - info: tapo.0 (251883) terminating
              2024-01-08 19:53:33.986 - warn: tapo.0 (251883) Terminated (UNCAUGHT_EXCEPTION): Without reason
              2024-01-08 19:53:34.123 - error: host.iOProduktiv Caught by controller[0]: TypeError: Invalid character in header content ["Host"]
              2024-01-08 19:53:34.124 - error: host.iOProduktiv Caught by controller[0]: at ClientRequest.setHeader (node:_http_outgoing:651:3)
              2024-01-08 19:53:34.124 - error: host.iOProduktiv Caught by controller[0]: at new ClientRequest (node:_http_client:311:12)
              2024-01-08 19:53:34.124 - error: host.iOProduktiv Caught by controller[0]: at Object.request (node:http:100:10)
              2024-01-08 19:53:34.124 - error: host.iOProduktiv Caught by controller[0]: at Object.wrappedMethod [as request] (/opt/iobroker/node_modules/@sentry/src/integrations/http.ts:283:1)
              2024-01-08 19:53:34.124 - error: host.iOProduktiv Caught by controller[0]: at Cam._requestPart2 (/opt/iobroker/node_modules/onvif/lib/cam.js:276:20)
              2024-01-08 19:53:34.124 - error: host.iOProduktiv Caught by controller[0]: at /opt/iobroker/node_modules/onvif/lib/cam.js:247:23
              2024-01-08 19:53:34.124 - error: host.iOProduktiv Caught by controller[0]: at Parser. (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:308:18)
              2024-01-08 19:53:34.124 - error: host.iOProduktiv Caught by controller[0]: at Parser.emit (node:events:517:28)
              2024-01-08 19:53:34.124 - error: host.iOProduktiv Caught by controller[0]: at Parser.emit (node:domain:489:12)
              2024-01-08 19:53:34.124 - error: host.iOProduktiv Caught by controller[0]: at SAXParser.onclosetag (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:266:26) {
              2024-01-08 19:53:34.124 - error: host.iOProduktiv Caught by controller[0]: code: 'ERR_INVALID_CHAR'
              2024-01-08 19:53:34.124 - error: host.iOProduktiv Caught by controller[0]: }
              2024-01-08 19:53:34.124 - error: host.iOProduktiv instance system.adapter.tapo.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
              2024-01-08 19:53:34.124 - info: host.iOProduktiv Restart adapter system.adapter.tapo.0 because enabled
              2024-01-08 19:54:04.286 - info: host.iOProduktiv instance system.adapter.tapo.0 started with pid 253103
              2024-01-08 19:54:05.186 - info: tapo.0 (253103) starting. Version 0.2.0 (non-npm: TA2k/ioBroker.tapo#f22d791b9b422d6fd3abe8a2f9f7382a7988c965) in /opt/iobroker/node_modules/iobroker.tapo, node: v18.18.2, js-controller: 5.0.17
              2024-01-08 19:54:05.208 - info: tapo.0 (253103) Login tp TAPO App
              2024-01-08 19:54:05.685 - info: tapo.0 (253103) Login succesfull
              2024-01-08 19:54:05.915 - info: tapo.0 (253103) Found 3 devices
              2024-01-08 19:54:06.352 - error: tapo.0 (253103) {"error_code":-20571,"msg":"Device is offline"}
              2024-01-08 19:54:06.354 - info: tapo.0 (253103) Init device 8021CDA220ADD1EE6A8E7E7D0F7DFE861E649CA0 type C310 with ip
              192.168.0.110
              2024-01-08 19:54:06.385 - error: tapo.0 (253103) uncaught exception: Invalid character in header content ["Host"]
              2024-01-08 19:54:06.385 - error: tapo.0 (253103) TypeError: Invalid character in header content ["Host"]
              at ClientRequest.setHeader (node:_http_outgoing:651:3)
              at new ClientRequest (node:_http_client:311:12)
              at Object.request (node:http:100:10)
              at Object.wrappedMethod [as request] (/opt/iobroker/node_modules/@sentry/src/integrations/http.ts:283:1)
              at Cam._requestPart2 (/opt/iobroker/node_modules/onvif/lib/cam.js:276:20)
              at /opt/iobroker/node_modules/onvif/lib/cam.js:247:23
              at Parser. (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:308:18)
              at Parser.emit (node:events:517:28)
              at Parser.emit (node:domain:489:12)
              at SAXParser.onclosetag (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:266:26)
              2024-01-08 19:54:06.385 - error: tapo.0 (253103) Exception-Code: ERR_INVALID_CHAR: Invalid character in header content ["Host"]
              2024-01-08 19:54:06.394 - info: tapo.0 (253103) terminating
              2024-01-08 19:54:06.394 - warn: tapo.0 (253103) Terminated (UNCAUGHT_EXCEPTION): Without reason
              2024-01-08 19:54:06.514 - error: host.iOProduktiv Caught by controller[0]: TypeError: Invalid character in header content ["Host"]
              2024-01-08 19:54:06.514 - error: host.iOProduktiv Caught by controller[0]: at ClientRequest.setHeader (node:_http_outgoing:651:3)
              2024-01-08 19:54:06.514 - error: host.iOProduktiv Caught by controller[0]: at new ClientRequest (node:_http_client:311:12)
              2024-01-08 19:54:06.514 - error: host.iOProduktiv Caught by controller[0]: at Object.request (node:http:100:10)
              2024-01-08 19:54:06.514 - error: host.iOProduktiv Caught by controller[0]: at Object.wrappedMethod [as request] (/opt/iobroker/node_modules/@sentry/src/integrations/http.ts:283:1)
              2024-01-08 19:54:06.514 - error: host.iOProduktiv Caught by controller[0]: at Cam._requestPart2 (/opt/iobroker/node_modules/onvif/lib/cam.js:276:20)
              2024-01-08 19:54:06.514 - error: host.iOProduktiv Caught by controller[0]: at /opt/iobroker/node_modules/onvif/lib/cam.js:247:23
              2024-01-08 19:54:06.515 - error: host.iOProduktiv Caught by controller[0]: at Parser. (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:308:18)
              2024-01-08 19:54:06.515 - error: host.iOProduktiv Caught by controller[0]: at Parser.emit (node:events:517:28)
              2024-01-08 19:54:06.515 - error: host.iOProduktiv Caught by controller[0]: at Parser.emit (node:domain:489:12)
              2024-01-08 19:54:06.515 - error: host.iOProduktiv Caught by controller[0]: at SAXParser.onclosetag (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:266:26) {
              2024-01-08 19:54:06.515 - error: host.iOProduktiv Caught by controller[0]: code: 'ERR_INVALID_CHAR'
              2024-01-08 19:54:06.515 - error: host.iOProduktiv Caught by controller[0]: }
              2024-01-08 19:54:06.515 - error: host.iOProduktiv instance system.adapter.tapo.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
              2024-01-08 19:54:06.515 - info: host.iOProduktiv Restart adapter system.adapter.tapo.0 because enabled
              2024-01-08 19:54:36.621 - info: host.iOProduktiv instance system.adapter.tapo.0 started with pid 254814
              2024-01-08 19:54:37.530 - info: tapo.0 (254814) starting. Version 0.2.0 (non-npm: TA2k/ioBroker.tapo#f22d791b9b422d6fd3abe8a2f9f7382a7988c965) in /opt/iobroker/node_modules/iobroker.tapo, node: v18.18.2, js-controller: 5.0.17
              2024-01-08 19:54:37.554 - info: tapo.0 (254814) Login tp TAPO App
              2024-01-08 19:54:38.140 - info: tapo.0 (254814) Login succesfull
              2024-01-08 19:54:38.442 - info: tapo.0 (254814) Found 3 devices
              2024-01-08 19:54:38.880 - error: tapo.0 (254814) {"error_code":-20571,"msg":"Device is offline"}
              2024-01-08 19:54:38.882 - info: tapo.0 (254814) Init device 8021CDA220ADD1EE6A8E7E7D0F7DFE861E649CA0 type C310 with ip
              192.168.0.110
              2024-01-08 19:54:38.908 - error: tapo.0 (254814) uncaught exception: Invalid character in header content ["Host"]
              2024-01-08 19:54:38.909 - error: tapo.0 (254814) TypeError: Invalid character in header content ["Host"]
              at ClientRequest.setHeader (node:_http_outgoing:651:3)
              at new ClientRequest (node:_http_client:311:12)
              at Object.request (node:http:100:10)
              at Object.wrappedMethod [as request] (/opt/iobroker/node_modules/@sentry/src/integrations/http.ts:283:1)
              at Cam._requestPart2 (/opt/iobroker/node_modules/onvif/lib/cam.js:276:20)
              at /opt/iobroker/node_modules/onvif/lib/cam.js:247:23
              at Parser. (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:308:18)
              at Parser.emit (node:events:517:28)
              at Parser.emit (node:domain:489:12)
              at SAXParser.onclosetag (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:266:26)
              2024-01-08 19:54:38.909 - error: tapo.0 (254814) Exception-Code: ERR_INVALID_CHAR: Invalid character in header content ["Host"]
              2024-01-08 19:54:38.916 - info: tapo.0 (254814) terminating
              2024-01-08 19:54:38.916 - warn: tapo.0 (254814) Terminated (UNCAUGHT_EXCEPTION): Without reason
              2024-01-08 19:54:39.037 - error: host.iOProduktiv Caught by controller[0]: TypeError: Invalid character in header content ["Host"]
              2024-01-08 19:54:39.037 - error: host.iOProduktiv Caught by controller[0]: at ClientRequest.setHeader (node:_http_outgoing:651:3)
              2024-01-08 19:54:39.037 - error: host.iOProduktiv Caught by controller[0]: at new ClientRequest (node:_http_client:311:12)
              2024-01-08 19:54:39.037 - error: host.iOProduktiv Caught by controller[0]: at Object.request (node:http:100:10)
              2024-01-08 19:54:39.037 - error: host.iOProduktiv Caught by controller[0]: at Object.wrappedMethod [as request] (/opt/iobroker/node_modules/@sentry/src/integrations/http.ts:283:1)
              2024-01-08 19:54:39.037 - error: host.iOProduktiv Caught by controller[0]: at Cam._requestPart2 (/opt/iobroker/node_modules/onvif/lib/cam.js:276:20)
              2024-01-08 19:54:39.037 - error: host.iOProduktiv Caught by controller[0]: at /opt/iobroker/node_modules/onvif/lib/cam.js:247:23
              2024-01-08 19:54:39.037 - error: host.iOProduktiv Caught by controller[0]: at Parser. (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:308:18)
              2024-01-08 19:54:39.037 - error: host.iOProduktiv Caught by controller[0]: at Parser.emit (node:events:517:28)
              2024-01-08 19:54:39.037 - error: host.iOProduktiv Caught by controller[0]: at Parser.emit (node:domain:489:12)
              2024-01-08 19:54:39.037 - error: host.iOProduktiv Caught by controller[0]: at SAXParser.onclosetag (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:266:26) {
              2024-01-08 19:54:39.037 - error: host.iOProduktiv Caught by controller[0]: code: 'ERR_INVALID_CHAR'
              2024-01-08 19:54:39.037 - error: host.iOProduktiv Caught by controller[0]: }
              2024-01-08 19:54:39.037 - error: host.iOProduktiv instance system.adapter.tapo.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
              2024-01-08 19:54:39.037 - info: host.iOProduktiv Restart adapter system.adapter.tapo.0 because enabled
              2024-01-08 19:55:00.023 - info: host.iOProduktiv instance system.adapter.ical.0 started with pid 255316
              2024-01-08 19:55:09.150 - info: host.iOProduktiv instance system.adapter.tapo.0 started with pid 256045
              2024-01-08 19:55:09.990 - info: tapo.0 (256045) starting. Version 0.2.0 (non-npm: TA2k/ioBroker.tapo#f22d791b9b422d6fd3abe8a2f9f7382a7988c965) in /opt/iobroker/node_modules/iobroker.tapo, node: v18.18.2, js-controller: 5.0.17
              2024-01-08 19:55:10.015 - info: tapo.0 (256045) Login tp TAPO App
              2024-01-08 19:55:10.501 - info: tapo.0 (256045) Login succesfull
              2024-01-08 19:55:10.742 - info: tapo.0 (256045) Found 3 devices
              2024-01-08 19:55:11.136 - error: tapo.0 (256045) {"error_code":-20571,"msg":"Device is offline"}
              2024-01-08 19:55:11.137 - info: tapo.0 (256045) Init device 8021CDA220ADD1EE6A8E7E7D0F7DFE861E649CA0 type C310 with ip
              192.168.0.110
              2024-01-08 19:55:11.166 - error: tapo.0 (256045) uncaught exception: Invalid character in header content ["Host"]
              2024-01-08 19:55:11.166 - error: tapo.0 (256045) TypeError: Invalid character in header content ["Host"]
              at ClientRequest.setHeader (node:_http_outgoing:651:3)
              at new ClientRequest (node:_http_client:311:12)
              at Object.request (node:http:100:10)
              at Object.wrappedMethod [as request] (/opt/iobroker/node_modules/@sentry/src/integrations/http.ts:283:1)
              at Cam._requestPart2 (/opt/iobroker/node_modules/onvif/lib/cam.js:276:20)
              at /opt/iobroker/node_modules/onvif/lib/cam.js:247:23
              at Parser. (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:308:18)
              at Parser.emit (node:events:517:28)
              at Parser.emit (node:domain:489:12)
              at SAXParser.onclosetag (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:266:26)
              2024-01-08 19:55:11.166 - error: tapo.0 (256045) Exception-Code: ERR_INVALID_CHAR: Invalid character in header content ["Host"]
              2024-01-08 19:55:11.174 - info: tapo.0 (256045) terminating
              2024-01-08 19:55:11.174 - warn: tapo.0 (256045) Terminated (UNCAUGHT_EXCEPTION): Without reason
              2024-01-08 19:55:11.303 - error: host.iOProduktiv Caught by controller[0]: TypeError: Invalid character in header content ["Host"]
              2024-01-08 19:55:11.303 - error: host.iOProduktiv Caught by controller[0]: at ClientRequest.setHeader (node:_http_outgoing:651:3)
              2024-01-08 19:55:11.303 - error: host.iOProduktiv Caught by controller[0]: at new ClientRequest (node:_http_client:311:12)
              2024-01-08 19:55:11.303 - error: host.iOProduktiv Caught by controller[0]: at Object.request (node:http:100:10)
              2024-01-08 19:55:11.303 - error: host.iOProduktiv Caught by controller[0]: at Object.wrappedMethod [as request] (/opt/iobroker/node_modules/@sentry/src/integrations/http.ts:283:1)
              2024-01-08 19:55:11.303 - error: host.iOProduktiv Caught by controller[0]: at Cam._requestPart2 (/opt/iobroker/node_modules/onvif/lib/cam.js:276:20)
              2024-01-08 19:55:11.303 - error: host.iOProduktiv Caught by controller[0]: at /opt/iobroker/node_modules/onvif/lib/cam.js:247:23
              2024-01-08 19:55:11.303 - error: host.iOProduktiv Caught by controller[0]: at Parser. (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:308:18)
              2024-01-08 19:55:11.303 - error: host.iOProduktiv Caught by controller[0]: at Parser.emit (node:events:517:28)
              2024-01-08 19:55:11.303 - error: host.iOProduktiv Caught by controller[0]: at Parser.emit (node:domain:489:12)
              2024-01-08 19:55:11.303 - error: host.iOProduktiv Caught by controller[0]: at SAXParser.onclosetag (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:266:26) {
              2024-01-08 19:55:11.304 - error: host.iOProduktiv Caught by controller[0]: code: 'ERR_INVALID_CHAR'
              2024-01-08 19:55:11.304 - error: host.iOProduktiv Caught by controller[0]: }
              2024-01-08 19:55:11.304 - error: host.iOProduktiv instance system.adapter.tapo.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
              2024-01-08 19:55:11.304 - info: host.iOProduktiv Restart adapter system.adapter.tapo.0 because enabled
              2024-01-08 19:55:41.457 - info: host.iOProduktiv instance system.adapter.tapo.0 started with pid 257259
              2024-01-08 19:55:42.245 - info: tapo.0 (257259) starting. Version 0.2.0 (non-npm: TA2k/ioBroker.tapo#f22d791b9b422d6fd3abe8a2f9f7382a7988c965) in /opt/iobroker/node_modules/iobroker.tapo, node: v18.18.2, js-controller: 5.0.17
              2024-01-08 19:55:42.268 - info: tapo.0 (257259) Login tp TAPO App
              2024-01-08 19:55:42.726 - info: tapo.0 (257259) Login succesfull
              2024-01-08 19:55:42.944 - info: tapo.0 (257259) Found 3 devices
              2024-01-08 19:55:43.394 - error: tapo.0 (257259) {"error_code":-20571,"msg":"Device is offline"}
              2024-01-08 19:55:43.396 - info: tapo.0 (257259) Init device 8021CDA220ADD1EE6A8E7E7D0F7DFE861E649CA0 type C310 with ip
              192.168.0.110
              2024-01-08 19:55:43.424 - error: tapo.0 (257259) uncaught exception: Invalid character in header content ["Host"]
              2024-01-08 19:55:43.425 - error: tapo.0 (257259) TypeError: Invalid character in header content ["Host"]
              at ClientRequest.setHeader (node:_http_outgoing:651:3)
              at new ClientRequest (node:_http_client:311:12)
              at Object.request (node:http:100:10)
              at Object.wrappedMethod [as request] (/opt/iobroker/node_modules/@sentry/src/integrations/http.ts:283:1)
              at Cam._requestPart2 (/opt/iobroker/node_modules/onvif/lib/cam.js:276:20)
              at /opt/iobroker/node_modules/onvif/lib/cam.js:247:23
              at Parser. (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:308:18)
              at Parser.emit (node:events:517:28)
              at Parser.emit (node:domain:489:12)
              at SAXParser.onclosetag (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:266:26)
              2024-01-08 19:55:43.425 - error: tapo.0 (257259) Exception-Code: ERR_INVALID_CHAR: Invalid character in header content ["Host"]
              2024-01-08 19:55:43.432 - info: tapo.0 (257259) terminating
              2024-01-08 19:55:43.433 - warn: tapo.0 (257259) Terminated (UNCAUGHT_EXCEPTION): Without reason
              2024-01-08 19:55:43.556 - error: host.iOProduktiv Caught by controller[0]: TypeError: Invalid character in header content ["Host"]
              2024-01-08 19:55:43.556 - error: host.iOProduktiv Caught by controller[0]: at ClientRequest.setHeader (node:_http_outgoing:651:3)
              2024-01-08 19:55:43.556 - error: host.iOProduktiv Caught by controller[0]: at new ClientRequest (node:_http_client:311:12)
              2024-01-08 19:55:43.556 - error: host.iOProduktiv Caught by controller[0]: at Object.request (node:http:100:10)
              2024-01-08 19:55:43.556 - error: host.iOProduktiv Caught by controller[0]: at Object.wrappedMethod [as request] (/opt/iobroker/node_modules/@sentry/src/integrations/http.ts:283:1)
              2024-01-08 19:55:43.556 - error: host.iOProduktiv Caught by controller[0]: at Cam._requestPart2 (/opt/iobroker/node_modules/onvif/lib/cam.js:276:20)
              2024-01-08 19:55:43.556 - error: host.iOProduktiv Caught by controller[0]: at /opt/iobroker/node_modules/onvif/lib/cam.js:247:23
              2024-01-08 19:55:43.556 - error: host.iOProduktiv Caught by controller[0]: at Parser. (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:308:18)
              2024-01-08 19:55:43.556 - error: host.iOProduktiv Caught by controller[0]: at Parser.emit (node:events:517:28)
              2024-01-08 19:55:43.556 - error: host.iOProduktiv Caught by controller[0]: at Parser.emit (node:domain:489:12)
              2024-01-08 19:55:43.556 - error: host.iOProduktiv Caught by controller[0]: at SAXParser.onclosetag (/opt/iobroker/node_modules/onvif/node_modules/xml2js/lib/parser.js:266:26) {
              2024-01-08 19:55:43.556 - error: host.iOProduktiv Caught by controller[0]: code: 'ERR_INVALID_CHAR'
              2024-01-08 19:55:43.556 - error: host.iOProduktiv Caught by controller[0]: }
              2024-01-08 19:55:43.556 - error: host.iOProduktiv instance system.adapter.tapo.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
              2024-01-08 19:55:43.556 - info: host.iOProduktiv Restart adapter system.adapter.tapo.0 because enabled
              2024-01-08 19:55:48.775 - info: host.iOProduktiv "system.adapter.tapo.0" disabled
              2024-01-08 19:56:14.442 - error: tapo.0 (258480) adapter disabled
              2024-01-08 19:56:14.489 - warn: tapo.0 (258480) Terminated (NO_ADAPTER_CONFIG_FOUND): Without reason
              2024-01-08 19:56:15.093 - error: host.iOProduktiv instance system.adapter.tapo.0 terminated with code 3 (NO_ADAPTER_CONFIG_FOUND)
              2024-01-08 19:56:15.093 - info: host.iOProduktiv Do not restart adapter system.adapter.tapo.0 because disabled or deleted
              2024-01-08 19:56:39.588 - info: admin.0 (631) <== Disconnect system.user.admin from ::ffff:192.168.0.132 admin
              2024-01-08 19:56:40.869 - info: admin.0 (631) ==> Connected system.user.admin from ::ffff:192.168.0.132
              

              Onvis schaue ich mir paralell einmal an, andernfalls schicke ich die Cam retour nach A......zonien.

              Danke für deine Arbeit!!!!!

              T Offline
              T Offline
              tombox
              schrieb am zuletzt editiert von
              #351

              @metaxa Die C520WS 1.0 with ip 192.168.0.220 sieht gut au und erkennt sogar Bewegung aber die C310 ohne ip sorgt dafür das der adapter abstürzt

              1 Antwort Letzte Antwort
              0
              • metaxaM Offline
                metaxaM Offline
                metaxa
                schrieb am zuletzt editiert von metaxa
                #352

                Servus @tombox!

                Ich habe danach die IP Adressen eingetragen, aber das brachte die Instanz zum permanenten Absturz.

                Ohne eingetragenen IP Adressen für die beiden anderen Cam´s blieb die Instanz am Leben.

                Welche DP bei der C520WS wären denn für "bewege dich zu Pos xx" zuständig?

                T 1 Antwort Letzte Antwort
                0
                • metaxaM metaxa

                  Servus @tombox!

                  Ich habe danach die IP Adressen eingetragen, aber das brachte die Instanz zum permanenten Absturz.

                  Ohne eingetragenen IP Adressen für die beiden anderen Cam´s blieb die Instanz am Leben.

                  Welche DP bei der C520WS wären denn für "bewege dich zu Pos xx" zuständig?

                  T Offline
                  T Offline
                  tombox
                  schrieb am zuletzt editiert von tombox
                  #353

                  @metaxa ein log von dem abstürzen wäre noch gut

                  tapo adapter unterstützt kein Ptz kontrolle
                  hier die Diskussion
                  https://github.com/kopiro/homebridge-tapo-camera/issues/55

                  onvif adapter kann gotoPreset für vordefinierte Presets

                  metaxaM 1 Antwort Letzte Antwort
                  0
                  • T tombox

                    @metaxa ein log von dem abstürzen wäre noch gut

                    tapo adapter unterstützt kein Ptz kontrolle
                    hier die Diskussion
                    https://github.com/kopiro/homebridge-tapo-camera/issues/55

                    onvif adapter kann gotoPreset für vordefinierte Presets

                    metaxaM Offline
                    metaxaM Offline
                    metaxa
                    schrieb am zuletzt editiert von
                    #354

                    @tombox sagte in Test Adapter TP-Link Tapo:

                    abstürzen wäre noch gut
                    tapo adapter unterstützt kein Ptz kontrolle

                    Sollte alles im zusammen geschnittenen Protokoll drinnen sein. Eventuell ist "abstürzen" mein falscher Ausdruck. Die Instanz wird grün, schreibt einen Haufen Fehlermeldungen und geht wieder auf rot. Das wiederholt sich paar mal. Ich habe ihn dann deaktiviert.

                    @tombox sagte in Test Adapter TP-Link Tapo:

                    onvif adapter kann gotoPreset für vordefinierte Presets

                    ok, danke! Dann versuche ich es mit dem onvif Adapter, ich brauche vom iO ja nur das PTZ.

                    T 1 Antwort Letzte Antwort
                    0
                    • metaxaM metaxa

                      @tombox sagte in Test Adapter TP-Link Tapo:

                      abstürzen wäre noch gut
                      tapo adapter unterstützt kein Ptz kontrolle

                      Sollte alles im zusammen geschnittenen Protokoll drinnen sein. Eventuell ist "abstürzen" mein falscher Ausdruck. Die Instanz wird grün, schreibt einen Haufen Fehlermeldungen und geht wieder auf rot. Das wiederholt sich paar mal. Ich habe ihn dann deaktiviert.

                      @tombox sagte in Test Adapter TP-Link Tapo:

                      onvif adapter kann gotoPreset für vordefinierte Presets

                      ok, danke! Dann versuche ich es mit dem onvif Adapter, ich brauche vom iO ja nur das PTZ.

                      T Offline
                      T Offline
                      tombox
                      schrieb am zuletzt editiert von
                      #355

                      @metaxa das Protokoll zeigt nur Fehler mit der c310 ohne ip . das ist in der GitHub version behoben

                      metaxaM 1 Antwort Letzte Antwort
                      0
                      • T tombox

                        @walter-white Das ist korrekt ich habe keine Steckdosen kann es nicht implementieren muss also auf Homebridge warten
                        oder halt auf home Assistent wechseln

                        Walter WhiteW Offline
                        Walter WhiteW Offline
                        Walter White
                        schrieb am zuletzt editiert von
                        #356

                        @tombox das ist ärgerlich, denn es steht alles bereit für Merge, kann wegen wahrscheinlichen todesfall(?) nicht irgendein github Admin das Update freigeben?

                        M T 2 Antworten Letzte Antwort
                        0
                        • Walter WhiteW Walter White

                          @tombox das ist ärgerlich, denn es steht alles bereit für Merge, kann wegen wahrscheinlichen todesfall(?) nicht irgendein github Admin das Update freigeben?

                          M Online
                          M Online
                          ManiacKill
                          schrieb am zuletzt editiert von ManiacKill
                          #357

                          @walter-white

                          tapo.0
                          2024-01-10 17:10:42.070	info	Wait for connections
                          tapo.0
                          2024-01-10 17:10:41.919	info	Initialized 
                          tapo.0
                          2024-01-10 17:10:41.909	info	 Received device info {"manufacturer":"tp-link","model":"Tapo C225","firmwareVersion":"1.0.27 Build 231107 Rel.69776n","serialNumber":"a1eda66e","hardwareId":1}
                          tapo.0
                          2024-01-10 17:10:41.728	info	Init device  type C225 1.0 with ip 192.168.2.114
                          tapo.0
                          2024-01-10 17:10:41.476	info	Found 1 devices
                          tapo.0
                          2024-01-10 17:10:41.278	info	Login succesfull
                          tapo.0
                          2024-01-10 17:10:40.837	info	Login tp TAPO App
                          

                          nach dem info Wait for connections kommt nix mehr ist das richtig ?

                          Danke

                          1 Antwort Letzte Antwort
                          0
                          • Walter WhiteW Walter White

                            @tombox das ist ärgerlich, denn es steht alles bereit für Merge, kann wegen wahrscheinlichen todesfall(?) nicht irgendein github Admin das Update freigeben?

                            T Offline
                            T Offline
                            tombox
                            schrieb am zuletzt editiert von
                            #358

                            @walter-white wie schon geschrieben dieser PR wird schon in Homebridge eingesetzt und ist seit zwei Monaten in iobroker aber es nach dem letzten update von tp link funktioniert der auch nicht mehr

                            M 1 Antwort Letzte Antwort
                            0
                            • T tombox

                              @walter-white wie schon geschrieben dieser PR wird schon in Homebridge eingesetzt und ist seit zwei Monaten in iobroker aber es nach dem letzten update von tp link funktioniert der auch nicht mehr

                              M Online
                              M Online
                              ManiacKill
                              schrieb am zuletzt editiert von
                              #359

                              @tombox

                              
                              tapo.0
                              2024-01-10 17:59:57.716	warn	Error: Unknown password encryption method
                              

                              Ich bekomme einfach nicht die Kamera richtig rein, funktioniert das zurzeit sowieso nicht ?

                              1 Antwort Letzte Antwort
                              0
                              • T tombox

                                @metaxa das Protokoll zeigt nur Fehler mit der c310 ohne ip . das ist in der GitHub version behoben

                                metaxaM Offline
                                metaxaM Offline
                                metaxa
                                schrieb am zuletzt editiert von metaxa
                                #360

                                @tombox sagte in Test Adapter TP-Link Tapo:

                                @metaxa das Protokoll zeigt nur Fehler mit der c310 ohne ip . das ist in der GitHub version behoben

                                ich hatte mit diesem Link aus dem 1. Post installiert. Nur bitte beschäftige nicht weiter mit meinen "Problemen", ich will über iO nur steuern können. Da nennst du onvif als eventuelle Lösung.

                                Danke!

                                EDIT: Mit onvif funktioniert die Steuerung ausreichend! Danke für deinen TIPP!

                                M T 2 Antworten Letzte Antwort
                                0
                                • metaxaM metaxa

                                  @tombox sagte in Test Adapter TP-Link Tapo:

                                  @metaxa das Protokoll zeigt nur Fehler mit der c310 ohne ip . das ist in der GitHub version behoben

                                  ich hatte mit diesem Link aus dem 1. Post installiert. Nur bitte beschäftige nicht weiter mit meinen "Problemen", ich will über iO nur steuern können. Da nennst du onvif als eventuelle Lösung.

                                  Danke!

                                  EDIT: Mit onvif funktioniert die Steuerung ausreichend! Danke für deinen TIPP!

                                  M Online
                                  M Online
                                  ManiacKill
                                  schrieb am zuletzt editiert von
                                  #361

                                  @metaxa

                                  Hi gibt es in einem Adapter ein Steuerkreuz für die Kamera Bewegung. Kann leider keins finden ! So wie ein Analog Stick !

                                  metaxaM 1 Antwort Letzte Antwort
                                  0
                                  • metaxaM metaxa

                                    @tombox sagte in Test Adapter TP-Link Tapo:

                                    @metaxa das Protokoll zeigt nur Fehler mit der c310 ohne ip . das ist in der GitHub version behoben

                                    ich hatte mit diesem Link aus dem 1. Post installiert. Nur bitte beschäftige nicht weiter mit meinen "Problemen", ich will über iO nur steuern können. Da nennst du onvif als eventuelle Lösung.

                                    Danke!

                                    EDIT: Mit onvif funktioniert die Steuerung ausreichend! Danke für deinen TIPP!

                                    T Offline
                                    T Offline
                                    tombox
                                    schrieb am zuletzt editiert von
                                    #362

                                    @metaxa die GitHub version von tapp kann auch die Kamera bewegen

                                    T metaxaM 2 Antworten Letzte Antwort
                                    1
                                    • T tombox

                                      @metaxa die GitHub version von tapp kann auch die Kamera bewegen

                                      T Offline
                                      T Offline
                                      tombox
                                      schrieb am zuletzt editiert von
                                      #363

                                      Die v0.2.1 kann jetzt auch Kamera Bewegung ein debug log für das P100 problem wäre auch hilfreich
                                      einfach via mail tombox2020@gmail.com

                                      1 Antwort Letzte Antwort
                                      0
                                      • T tombox

                                        @metaxa die GitHub version von tapp kann auch die Kamera bewegen

                                        metaxaM Offline
                                        metaxaM Offline
                                        metaxa
                                        schrieb am zuletzt editiert von metaxa
                                        #364

                                        @tombox Servus und Danke!

                                        Ich habe jetzt über Github upgegradet auf 0.2.2.

                                        Folgendes finde ich beim Neustart im Log

                                        
                                        tapo.0
                                        2024-01-12 12:06:12.091	warn	Error: Unknown password encryption method
                                        
                                        tapo.0
                                        2024-01-12 12:06:02.091	warn	Error: Unknown password encryption method
                                        
                                        tapo.0
                                        2024-01-12 12:05:52.090	warn	Error: Unknown password encryption method
                                        
                                        tapo.0
                                        2024-01-12 12:05:42.088	warn	Error: Unknown password encryption method
                                        
                                        tapo.0
                                        2024-01-12 12:05:32.087	warn	Error: Unknown password encryption method
                                        
                                        tapo.0
                                        2024-01-12 12:05:22.087	warn	Error: Unknown password encryption method
                                        
                                        tapo.0
                                        2024-01-12 12:05:12.085	warn	Error: Unknown password encryption method
                                        
                                        tapo.0
                                        2024-01-12 12:05:02.085	warn	Error: Unknown password encryption method
                                        
                                        tapo.0
                                        2024-01-12 12:04:52.084	warn	Error: Unknown password encryption method
                                        
                                        tapo.0
                                        2024-01-12 12:04:42.082	warn	Error: Unknown password encryption method
                                        
                                        tapo.0
                                        2024-01-12 12:04:32.081	warn	Error: Unknown password encryption method
                                        
                                        tapo.0
                                        2024-01-12 12:04:32.001	info	Start first Update
                                        
                                        tapo.0
                                        2024-01-12 12:04:21.999	info	Wait for connections for non camera devices
                                        
                                        tapo.0
                                        2024-01-12 12:04:21.980	warn	No IP found for 8021314EFB57E17626EC16DBDB2A31A51E64292E put the device online or set the ip state manually
                                        
                                        tapo.0
                                        2024-01-12 12:04:21.976	error	{"error_code":-20571,"msg":"Device is offline"}
                                        
                                        tapo.0
                                        2024-01-12 12:04:21.575	info	Initialized 80219D887A52D32D03212C4C2DE37E4D21EC8028
                                        
                                        tapo.0
                                        2024-01-12 12:04:21.520	info	80219D887A52D32D03212C4C2DE37E4D21EC8028 Received device info {"manufacturer":"tp-link","model":"Tapo C520WS","firmwareVersion":"1.1.4 Build 230922 Rel.57957n","serialNumber":"31d87f97","hardwareId":1}
                                        
                                        tapo.0
                                        2024-01-12 12:04:21.451	info	Init device 80219D887A52D32D03212C4C2DE37E4D21EC8028 type C520WS 1.0 with ip 192.168.0.220
                                        
                                        tapo.0
                                        2024-01-12 12:04:21.244	warn	No IP found for 8021CDA220ADD1EE6A8E7E7D0F7DFE861E649CA0 put the device online or set the ip state manually
                                        
                                        tapo.0
                                        2024-01-12 12:04:21.241	error	{"error_code":-20571,"msg":"Device is offline"}
                                        
                                        tapo.0
                                        2024-01-12 12:04:20.828	info	Found 3 devices
                                        
                                        tapo.0
                                        2024-01-12 12:04:20.623	info	Login succesfull
                                        
                                        tapo.0
                                        2024-01-12 12:04:20.275	info	Login tp TAPO App
                                        
                                        tapo.0
                                        2024-01-12 12:04:20.203	info	starting. Version 0.2.2 (non-npm: TA2k/ioBroker.tapo#e1cf6255f471f8e3271408e7f2cb0c82fc7049c0) in /opt/iobroker/node_modules/iobroker.tapo, node: v18.18.2, js-controller: 5.0.17
                                        

                                        Wie soll das Steuern funktionieren?
                                        121dbcbf-9782-4ae8-b912-02798a5fcf6d-image.png
                                        Egal welche Werte ich eingebe, die Cam bewegt sich nicht.

                                        Edit: Mit dem onvif funktioniert das recht gut:
                                        55f5e1f4-aa77-4d02-a76f-f3ca11480ccb-image.png

                                        H T 2 Antworten Letzte Antwort
                                        0
                                        • metaxaM metaxa

                                          @tombox Servus und Danke!

                                          Ich habe jetzt über Github upgegradet auf 0.2.2.

                                          Folgendes finde ich beim Neustart im Log

                                          
                                          tapo.0
                                          2024-01-12 12:06:12.091	warn	Error: Unknown password encryption method
                                          
                                          tapo.0
                                          2024-01-12 12:06:02.091	warn	Error: Unknown password encryption method
                                          
                                          tapo.0
                                          2024-01-12 12:05:52.090	warn	Error: Unknown password encryption method
                                          
                                          tapo.0
                                          2024-01-12 12:05:42.088	warn	Error: Unknown password encryption method
                                          
                                          tapo.0
                                          2024-01-12 12:05:32.087	warn	Error: Unknown password encryption method
                                          
                                          tapo.0
                                          2024-01-12 12:05:22.087	warn	Error: Unknown password encryption method
                                          
                                          tapo.0
                                          2024-01-12 12:05:12.085	warn	Error: Unknown password encryption method
                                          
                                          tapo.0
                                          2024-01-12 12:05:02.085	warn	Error: Unknown password encryption method
                                          
                                          tapo.0
                                          2024-01-12 12:04:52.084	warn	Error: Unknown password encryption method
                                          
                                          tapo.0
                                          2024-01-12 12:04:42.082	warn	Error: Unknown password encryption method
                                          
                                          tapo.0
                                          2024-01-12 12:04:32.081	warn	Error: Unknown password encryption method
                                          
                                          tapo.0
                                          2024-01-12 12:04:32.001	info	Start first Update
                                          
                                          tapo.0
                                          2024-01-12 12:04:21.999	info	Wait for connections for non camera devices
                                          
                                          tapo.0
                                          2024-01-12 12:04:21.980	warn	No IP found for 8021314EFB57E17626EC16DBDB2A31A51E64292E put the device online or set the ip state manually
                                          
                                          tapo.0
                                          2024-01-12 12:04:21.976	error	{"error_code":-20571,"msg":"Device is offline"}
                                          
                                          tapo.0
                                          2024-01-12 12:04:21.575	info	Initialized 80219D887A52D32D03212C4C2DE37E4D21EC8028
                                          
                                          tapo.0
                                          2024-01-12 12:04:21.520	info	80219D887A52D32D03212C4C2DE37E4D21EC8028 Received device info {"manufacturer":"tp-link","model":"Tapo C520WS","firmwareVersion":"1.1.4 Build 230922 Rel.57957n","serialNumber":"31d87f97","hardwareId":1}
                                          
                                          tapo.0
                                          2024-01-12 12:04:21.451	info	Init device 80219D887A52D32D03212C4C2DE37E4D21EC8028 type C520WS 1.0 with ip 192.168.0.220
                                          
                                          tapo.0
                                          2024-01-12 12:04:21.244	warn	No IP found for 8021CDA220ADD1EE6A8E7E7D0F7DFE861E649CA0 put the device online or set the ip state manually
                                          
                                          tapo.0
                                          2024-01-12 12:04:21.241	error	{"error_code":-20571,"msg":"Device is offline"}
                                          
                                          tapo.0
                                          2024-01-12 12:04:20.828	info	Found 3 devices
                                          
                                          tapo.0
                                          2024-01-12 12:04:20.623	info	Login succesfull
                                          
                                          tapo.0
                                          2024-01-12 12:04:20.275	info	Login tp TAPO App
                                          
                                          tapo.0
                                          2024-01-12 12:04:20.203	info	starting. Version 0.2.2 (non-npm: TA2k/ioBroker.tapo#e1cf6255f471f8e3271408e7f2cb0c82fc7049c0) in /opt/iobroker/node_modules/iobroker.tapo, node: v18.18.2, js-controller: 5.0.17
                                          

                                          Wie soll das Steuern funktionieren?
                                          121dbcbf-9782-4ae8-b912-02798a5fcf6d-image.png
                                          Egal welche Werte ich eingebe, die Cam bewegt sich nicht.

                                          Edit: Mit dem onvif funktioniert das recht gut:
                                          55f5e1f4-aa77-4d02-a76f-f3ca11480ccb-image.png

                                          H Offline
                                          H Offline
                                          HeliosFan
                                          schrieb am zuletzt editiert von HeliosFan
                                          #365

                                          Hallo liebe Community,

                                          mit Spannung verfolge ich die Beiträge in diesem Thread.
                                          Ich selbst habe die TP-Link Tapo C 212 Kamera und wäre sehr an einer Steuerung über den ioBroker interessiert.

                                          Vorgestellt habe ich mir das so:

                                          Alarmanlage aus: --> Kamera aus.
                                          Alarmanlage ein: --> Kamera ein, Bewegungserkennung ein, Aufzeichnung bei erkannter Bewegung ein.

                                          Die Alarmanlage basiert auf HMIP Komponenten in Verbindung mit einer CCU 3. ( Dies zur Info ).

                                          Daher meine Frage: Funktioniert der TP-Link Tapo Adapter mittlerweilen 100%ig oder nicht ?

                                          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

                                          854

                                          Online

                                          32.4k

                                          Benutzer

                                          81.4k

                                          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