Test Adapter TP-Link Tapo
-
H Homoran verschob dieses Thema von Tester am
-
H Homoran verschob dieses Thema von ...nicht in offiziellem Repo am
-
Hallo, ich habe einen Button S200B über den Hub H100 angeschlossen und würde Eingaben über den Button gerne erfassen, nur finde ich beim Hub keine Parameter dafür? Der Button scheint bei den Objekten gar nicht auf, da er wohl kein Gerät im Sinne einer eigenen IP Adresse ist. Danke!
-
Bin ein bissl verwirrt, weil dieses Skript hier Fehler schmeißt. Ist womöglich was falsch mit dem "device connected" objekt?
2.6.2026, 19:59:28.838 [error]: javascript.0 (240231) script.js.common.tmp: getState has been called with id of type "number" but expects a string 2.6.2026, 19:59:28.840 [error]: javascript.0 (240231) script.js.common.tmp: Error: TypeError: Cannot read properties of undefined (reading 'val') 2.6.2026, 19:59:28.840 [error]: javascript.0 (240231) script.js.common.tmp: at Object.<anonymous> (script.js.common.tmp:9:75) 2.6.2026, 19:59:28.840 [error]: javascript.0 (240231) script.js.common.tmp: at Object.callback (/opt/iobroker/node_modules/iobroker.javascript/src/lib/sandbox.ts:1774:38) 2.6.2026, 19:59:28.841 [error]: javascript.0 (240231) script.js.common.tmp: at JavaScript.onStateChange (/opt/iobroker/node_modules/iobroker.javascript/src/main.ts:808:25) 2.6.2026, 19:59:28.841 [error]: javascript.0 (240231) script.js.common.tmp: at JavaScript.emit (node:events:509:28) 2.6.2026, 19:59:28.841 [error]: javascript.0 (240231) script.js.common.tmp: at JavaScript.emit (node:domain:489:12) 2.6.2026, 19:59:28.841 [error]: javascript.0 (240231) script.js.common.tmp: at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:11138:53) 2.6.2026, 19:59:28.841 [error]: javascript.0 (240231) script.js.common.tmp: at processImmediate (node:internal/timers:504:21) 2.6.2026, 19:59:35.537 [error]: javascript.0 (240231) script.js.common.tmp: getState has been called with id of type "number" but expects a string 2.6.2026, 19:59:35.538 [error]: javascript.0 (240231) script.js.common.tmp: Error: TypeError: Cannot read properties of undefined (reading 'val') 2.6.2026, 19:59:35.538 [error]: javascript.0 (240231) script.js.common.tmp: at Object.<anonymous> (script.js.common.tmp:21:29) 2.6.2026, 19:59:35.538 [error]: javascript.0 (240231) script.js.common.tmp: at Object.callback (/opt/iobroker/node_modules/iobroker.javascript/src/lib/sandbox.ts:1774:38) 2.6.2026, 19:59:35.538 [error]: javascript.0 (240231) script.js.common.tmp: at JavaScript.onStateChange (/opt/iobroker/node_modules/iobroker.javascript/src/main.ts:808:25) 2.6.2026, 19:59:35.539 [error]: javascript.0 (240231) script.js.common.tmp: at JavaScript.emit (node:events:509:28) 2.6.2026, 19:59:35.539 [error]: javascript.0 (240231) script.js.common.tmp: at JavaScript.emit (node:domain:489:12) 2.6.2026, 19:59:35.539 [error]: javascript.0 (240231) script.js.common.tmp: at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:11138:53) 2.6.2026, 19:59:35.539 [error]: javascript.0 (240231) script.js.common.tmp: at processImmediate (node:internal/timers:504:21) -
Bin ein bissl verwirrt, weil dieses Skript hier Fehler schmeißt. Ist womöglich was falsch mit dem "device connected" objekt?
2.6.2026, 19:59:28.838 [error]: javascript.0 (240231) script.js.common.tmp: getState has been called with id of type "number" but expects a string 2.6.2026, 19:59:28.840 [error]: javascript.0 (240231) script.js.common.tmp: Error: TypeError: Cannot read properties of undefined (reading 'val') 2.6.2026, 19:59:28.840 [error]: javascript.0 (240231) script.js.common.tmp: at Object.<anonymous> (script.js.common.tmp:9:75) 2.6.2026, 19:59:28.840 [error]: javascript.0 (240231) script.js.common.tmp: at Object.callback (/opt/iobroker/node_modules/iobroker.javascript/src/lib/sandbox.ts:1774:38) 2.6.2026, 19:59:28.841 [error]: javascript.0 (240231) script.js.common.tmp: at JavaScript.onStateChange (/opt/iobroker/node_modules/iobroker.javascript/src/main.ts:808:25) 2.6.2026, 19:59:28.841 [error]: javascript.0 (240231) script.js.common.tmp: at JavaScript.emit (node:events:509:28) 2.6.2026, 19:59:28.841 [error]: javascript.0 (240231) script.js.common.tmp: at JavaScript.emit (node:domain:489:12) 2.6.2026, 19:59:28.841 [error]: javascript.0 (240231) script.js.common.tmp: at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:11138:53) 2.6.2026, 19:59:28.841 [error]: javascript.0 (240231) script.js.common.tmp: at processImmediate (node:internal/timers:504:21) 2.6.2026, 19:59:35.537 [error]: javascript.0 (240231) script.js.common.tmp: getState has been called with id of type "number" but expects a string 2.6.2026, 19:59:35.538 [error]: javascript.0 (240231) script.js.common.tmp: Error: TypeError: Cannot read properties of undefined (reading 'val') 2.6.2026, 19:59:35.538 [error]: javascript.0 (240231) script.js.common.tmp: at Object.<anonymous> (script.js.common.tmp:21:29) 2.6.2026, 19:59:35.538 [error]: javascript.0 (240231) script.js.common.tmp: at Object.callback (/opt/iobroker/node_modules/iobroker.javascript/src/lib/sandbox.ts:1774:38) 2.6.2026, 19:59:35.538 [error]: javascript.0 (240231) script.js.common.tmp: at JavaScript.onStateChange (/opt/iobroker/node_modules/iobroker.javascript/src/main.ts:808:25) 2.6.2026, 19:59:35.539 [error]: javascript.0 (240231) script.js.common.tmp: at JavaScript.emit (node:events:509:28) 2.6.2026, 19:59:35.539 [error]: javascript.0 (240231) script.js.common.tmp: at JavaScript.emit (node:domain:489:12) 2.6.2026, 19:59:35.539 [error]: javascript.0 (240231) script.js.common.tmp: at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:11138:53) 2.6.2026, 19:59:35.539 [error]: javascript.0 (240231) script.js.common.tmp: at processImmediate (node:internal/timers:504:21) -
Bin auch gerade über "issue #98 V0.5.4 Kamera MoveToPreset ohne Funktion" gestolpert. es handelt sich um eine c210, 1.0, Fw 1.5.2.
Erstellen und anfahren von presets in der App klappt. Im iobroker über tapo.0.xxx.remote.moveToPreset klappt es nicht. tapo.0.xxx.remote.deletePreset funktioniert aber.
Im Log heißt es dazu: tapo.0 2026-06-07 17:12:50.227 info moveToPreset was set to : 2 for device xxx was successful: false -
Ich erleide seit kurzem eine Flut von diesen hier .. habe aber weder Einstellungen in der App verändert noch finde ich einen falsch gesetzte Einstellung.
tapo.0 2026-06-28 18:30:58.268 error Invalid device confirm. Please activate 3rd Patry support in the TP App under TP Labor -> 3rd Party Control tapo.0 2026-06-28 18:30:58.268 error STOK not found -
Der Adapter findet keine devices, in der App habe ich zwei HS100 Steckdosen und eine D235 Doorbell.
Wo ist der Fehler?2026-06-29 16:06:23.851 - info: tapo.0 (284068) starting. Version 0.5.4 in /opt/iobroker/node_modules/iobroker.tapo, node: v22.23.1, js-controller: 7.2.2
2026-06-29 16:06:23.862 - info: tapo.0 (284068) Login tp TAPO App
2026-06-29 16:06:24.371 - info: tapo.0 (284068) Login succesfull
2026-06-29 16:06:24.542 - info: tapo.0 (284068) Found 0 devices
2026-06-29 16:06:24.544 - info: tapo.0 (284068) Wait for connections for non camera devices
2026-06-29 16:06:34.545 - info: tapo.0 (284068) Start first Update -
Ich erleide seit kurzem eine Flut von diesen hier .. habe aber weder Einstellungen in der App verändert noch finde ich einen falsch gesetzte Einstellung.
tapo.0 2026-06-28 18:30:58.268 error Invalid device confirm. Please activate 3rd Patry support in the TP App under TP Labor -> 3rd Party Control tapo.0 2026-06-28 18:30:58.268 error STOK not foundIch erleide seit kurzem eine Flut von diesen hier .. habe aber weder Einstellungen in der App verändert noch finde ich einen falsch gesetzte Einstellung.
Dasselbe bei mir seit 2 Tagen. Ich habe 2 TAPO C200 Kameras eingebunden, das lief bislang problemlos, jetzt kommen alle 10 Sek die Fehlermeldungen im Log:
tapo.0 2026-07-27 12:16:30.277 error STOK not found tapo.0 2026-07-27 12:16:30.277 error Invalid device confirm. Please activate 3rd Patry support in the TP App under TP Labor -> 3rd Party Control tapo.0 2026-07-27 12:16:21.186 error STOK not found tapo.0 2026-07-27 12:16:21.185 error Invalid device confirm. Please activate 3rd Patry support in the TP App under TP Labor -> 3rd Party Control tapo.0 2026-07-27 12:16:10.199 error STOK not found tapo.0 2026-07-27 12:16:10.199 error Invalid device confirm. Please activate 3rd Patry support in the TP App under TP Labor -> 3rd Party Control tapo.0 2026-07-27 12:16:00.110 error STOK not found tapo.0 2026-07-27 12:16:00.110 error Invalid device confirm. Please activate 3rd Patry support in the TP App under TP Labor -> 3rd Party Control tapo.0 2026-07-27 12:15:50.557 error STOK not found tapo.0 2026-07-27 12:15:50.557 error Invalid device confirm. Please activate 3rd Patry support in the TP App under TP Labor -> 3rd Party Control tapo.0 2026-07-27 12:15:40.683 error STOK not found tapo.0 2026-07-27 12:15:40.682 error Invalid device confirm. Please activate 3rd Patry support in the TP App under TP Labor -> 3rd Party ControlZugangsdaten wurden nicht geändert und habe ich auch nochmal geprüft, das sollte alles passen. Bei Adapterneustart erkennt er auch die Kameras:
tapo.0 2026-07-27 12:18:28.559 info Reconnected to undefined tapo.0 2026-07-27 12:18:26.744 error STOK not found tapo.0 2026-07-27 12:18:26.742 error Invalid device confirm. Please activate 3rd Patry support in the TP App under TP Labor -> 3rd Party Control tapo.0 2026-07-27 12:18:22.453 info Start first Update tapo.0 2026-07-27 12:18:12.452 info Wait for connections for non camera devices tapo.0 2026-07-27 12:18:12.372 info Initialized 8021177FE691053725B91B53B48D81742565882D tapo.0 2026-07-27 12:18:12.352 info 8021177FE691053725B91B53B48D81742565882D Received device info {"manufacturer":"tp-link","model":"Tapo C200C","firmwareVersion":"1.3.5 Build 260228 Rel.36932n","serialNumber":"7461efc9","hardwareId":5} tapo.0 2026-07-27 12:18:11.594 info UDP discovery for 192.168.70.25: port=80 https=true encrypt=undefined lv=undefined mac=20-E1-5D-C8-EF-C9 tapo.0 2026-07-27 12:18:11.472 info Init device 8021177FE691053725B91B53B48D81742565882D type C200C 5.0 with ip 192.168.70.25 tapo.0 2026-07-27 12:18:11.229 info Initialized 8021199657BDC56CDD727D81E2791DB22565346F tapo.0 2026-07-27 12:18:11.216 info 8021199657BDC56CDD727D81E2791DB22565346F Received device info {"manufacturer":"tp-link","model":"Tapo C200C","firmwareVersion":"1.4.4 Build 260527 Rel.28339n","serialNumber":"7461f21d","hardwareId":5} tapo.0 2026-07-27 12:18:10.969 info UDP discovery for 192.168.10.166: port=80 https=true encrypt=undefined lv=undefined mac=20-E1-5D-C8-F2-1D tapo.0 2026-07-27 12:18:10.775 info Init device 8021199657BDC56CDD727D81E2791DB22565346F type C200C 5.0 with ip 192.168.10.166 tapo.0 2026-07-27 12:18:10.481 info Found 2 devices tapo.0 2026-07-27 12:18:10.292 info Login succesfull tapo.0 2026-07-27 12:18:09.945 info Login tp TAPO App tapo.0 2026-07-27 12:18:09.853 info starting. Version 0.5.5 in /opt/iobroker/node_modules/iobroker.tapo, node: v22.23.1, js-controller: 7.2.2 host.iobroker 2026-07-27 12:18:05.793 info instance system.adapter.tapo.0 in version "0.5.5" started with pid 954877 host.iobroker 2026-07-27 12:18:02.034 info instance system.adapter.tapo.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) tapo.0 2026-07-27 12:18:01.847 info terminatingBeta-Repo,
tapo Adapter 0.5.5,
nodejs 22.23.1,
npm 10.9.8,
js-controller 7.2.2
Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.
Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.
Mit deinem Input könnte dieser Beitrag noch besser werden 💗
Registrieren AnmeldenSupport us
452
Online33.0k
Benutzer83.5k
Themen1.3m
Beiträge