Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. Test Adapter TP-Link Tapo

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    Test Adapter TP-Link Tapo

    This topic has been deleted. Only users with topic management privileges can see it.
    • G
      Gabe @tombox last edited by Gabe

      @tombox jupp Verbindung ist da und alle Daten von der Kamera erkennt er

      T 1 Reply Last reply Reply Quote 0
      • T
        tombox @Gabe last edited by

        @gabe Du könntest noch im log level debug das Kommando setzen

        G 2 Replies Last reply Reply Quote 0
        • G
          Gabe @tombox last edited by Gabe

          @tombox ich habe das eben im Log gefunden

          tapo.0 2022-11-19 15:43:14.850 info Wait for connections
          tapo.0 2022-11-19 15:43:14.822 error 52 - Get Device Info failed
          tapo.0 2022-11-19 15:43:14.821 info Initialized XXX
          tapo.0 2022-11-19 15:43:14.819 error 111 Error: connect ECONNREFUSED XXX: 80
          tapo.0 2022-11-19 15:43:13.778 info Init XXX type C320WS with ip XX
          tapo.0 2022-11-19 15:43:13.560 info Found 1 devices
          tapo.0 2022-11-19 15:43:13.431 info Login succesfull
          tapo.0 2022-11-19 15:43:13.560 info Found 1 devices
          tapo.0 2022-11-19 15:43:13.431 info Login succesfull
          tapo.0 2022-11-19 15:43:13.040 info Login tp TAPO App

          Sieht so aus, als würde er sich nicht richtig connecten oder?

          1 Reply Last reply Reply Quote 0
          • G
            Gabe @tombox last edited by

            @tombox kann es sein, dass man für die Kamera den Kameraccount benötigt siehe Tapo Phyton Script

            1 Reply Last reply Reply Quote 0
            • T
              tombox last edited by

              @gabe das ist eigentlich nur das stream Passwort wenn man den stream abfragen will. aber ich werde es nochmal umbauen müssen dazu bräuchte ich nochmal Zugang @Horst-Böttcher kann ja nochmal bescheid sagen wenn er zeit hat

              G 1 Reply Last reply Reply Quote 0
              • G
                Gabe @tombox last edited by

                @tombox ok super danke.Dann gedulde ich mich mal

                T 1 Reply Last reply Reply Quote 0
                • T
                  tombox @Gabe last edited by

                  @gabe @Horst-Böttcher bitte jetzt nochmal testen wie es sich mit einer camera verhält

                  G 1 Reply Last reply Reply Quote 0
                  • G
                    Gabe @tombox last edited by

                    @tombox Alarmanlage und Privatsphäre geht bei mir. Danke schonmal!!!

                    Was mir aufgefallen ist, wenn ich in der App die beiden Punkte ändere, ändert er sie nicht in den Datenpunkten (wenn es überhaupt geht)

                    T 1 Reply Last reply Reply Quote 0
                    • T
                      tombox @Gabe last edited by

                      @gabe
                      kannst du bitte checken ob bei motion detection im iobroker ein log Eintrag kommt
                      unter der tapo.0.id... sollte der aktuelle status von alarm und so sein

                      G 1 Reply Last reply Reply Quote 0
                      • G
                        Gabe @tombox last edited by Gabe

                        @tombox meinst du das?

                        tapo.0 2022-11-21 20:05:23.264 info false

                        Das bekomme ich aber immer egal ob true oder false

                        Ansonsten finde ich auch bei den Datenpunkten, kein Motion Detection oder so.

                        Im Log ist mir das auch aufgefallen

                        tapo.0
                        2022-11-21 20:49:06.340 error Error: ONVIF SOAP Fault: Authority failure

                        T 1 Reply Last reply Reply Quote 0
                        • T
                          tombox @Gabe last edited by

                          @gabe stell mal das log level auf debug und schicke mir den log per privat Nachricht

                          P 1 Reply Last reply Reply Quote 0
                          • P
                            pfahlenbauer @tombox last edited by

                            @tombox Ich habe ähnliche Probleme mit meinen Kamera's. Ich würde gerne die Strahler der Kameras (C320WS) ein- und ausschalten. Aber mir scheint auch es gibt Verbindungsprobleme. Auch wenn ich in der Tapo App Änderungen vornehme (z.B. Leuchtstärke), so ändert sich das iobroker Object "set brightness" nicht.

                            Hier aus meinem Log:

                            
                            tapo.0
                            2022-11-22 17:01:42.209	info	Wait for connections
                            
                            tapo.0
                            2022-11-22 17:01:42.163	error	52 - Get Device Info failed
                            
                            tapo.0
                            2022-11-22 17:01:42.162	info	Initialized 80217D4F5XXXXXXXXXXXX
                            
                            tapo.0
                            2022-11-22 17:01:42.161	error	111 Error: connect ECONNREFUSED 192.168.178.110:80
                            
                            tapo.0
                            2022-11-22 17:01:41.946	info	Unknown device type C320WS init as P100
                            
                            tapo.0
                            2022-11-22 17:01:41.945	info	Init device 80217D4F5XXXXXXXXXXXXXXX type C320WS with ip 192.168.178.110
                            
                            tapo.0
                            2022-11-22 17:01:41.744	error	52 - Get Device Info failed
                            
                            tapo.0
                            2022-11-22 17:01:41.743	info	Initialized 8021AE79E9XXXXXXXXXXXXXXX
                            
                            tapo.0
                            2022-11-22 17:01:41.742	error	111 Error: connect ECONNREFUSED 192.168.178.113:80
                            
                            tapo.0
                            2022-11-22 17:01:41.542	info	Unknown device type C320WS init as P100
                            
                            tapo.0
                            2022-11-22 17:01:41.541	info	Init device 8021AE79XXXXXXXXXXXXXXXXX type C320WS with ip 192.168.178.113
                            
                            tapo.0
                            2022-11-22 17:01:41.366	error	52 - Get Device Info failed
                            
                            tapo.0
                            2022-11-22 17:01:41.366	info	Initialized 80214550BEEXXXXXXXXXXXXXXXX
                            
                            tapo.0
                            2022-11-22 17:01:41.363	error	111 Error: connect ECONNREFUSED 192.168.178.109:80
                            
                            tapo.0
                            2022-11-22 17:01:41.238	info	Unknown device type C210 init as P100
                            
                            tapo.0
                            2022-11-22 17:01:41.237	info	Init device 80214550BEEXXXXXXXXXXXXXXXX type C210 with ip 192.168.178.109
                            
                            tapo.0
                            2022-11-22 17:01:41.011	info	Found 3 devices
                            
                            tapo.0
                            2022-11-22 17:01:40.797	info	Login succesfull
                            
                            tapo.0
                            2022-11-22 17:01:40.214	info	Login tp TAPO App
                            
                            tapo.0
                            2022-11-22 17:01:40.153	info	starting. Version 0.0.6 in /opt/iobroker/node_modules/iobroker.tapo, node: v14.20.0, js-controller: 4.0.23
                            
                            T 1 Reply Last reply Reply Quote 0
                            • T
                              tombox @pfahlenbauer last edited by

                              @pfahlenbauer du musst die GitHub version installieren das man die strahler schalten kann habe ich noch nicht gesehen

                              P 1 Reply Last reply Reply Quote 0
                              • P
                                pfahlenbauer @tombox last edited by

                                @tombox Habe nun von GitHub installiert und bekomme den gleichen ONVIV SOAP faultwie @Gabe

                                
                                tapo.0
                                2022-11-22 19:57:44.080	info	Wait for connections
                                
                                tapo.0
                                2022-11-22 19:57:44.050	error	Error: ONVIF SOAP Fault: Authority failure
                                
                                tapo.0
                                2022-11-22 19:57:43.952	info	Init device 80217D4F53XXXXXXXXXXXXXXXXXXXXXXXX type C320WS with ip 192.168.178.110
                                
                                tapo.0
                                2022-11-22 19:57:43.687	error	Error: ONVIF SOAP Fault: Authority failure
                                
                                tapo.0
                                2022-11-22 19:57:43.574	info	Init device 8021AE79E9CC0XXXXXXXXXXXXXXXX type C320WS with ip 192.168.178.113
                                
                                tapo.0
                                2022-11-22 19:57:43.336	error	Error: ONVIF SOAP Fault: Authority failure
                                
                                tapo.0
                                2022-11-22 19:57:43.189	info	Init device 80214550BEEXXXXXXXXXXXXXXXXXXXXX type C210 with ip 192.168.178.109
                                
                                tapo.0
                                2022-11-22 19:57:42.921	info	Found 3 devices
                                
                                tapo.0
                                2022-11-22 19:57:42.718	info	Login succesfull
                                
                                tapo.0
                                2022-11-22 19:57:42.260	info	Login tp TAPO App
                                
                                tapo.0
                                2022-11-22 19:57:42.196	info	starting. Version 0.0.6 (non-npm: TA2k/ioBroker.tapo#99bdbd2e2ba1bed5a907e1569e293924d49aef97) in /opt/iobroker/node_modules/iobroker.tapo, node: v14.20.0, js-controller: 4.0.23
                                
                                T 1 Reply Last reply Reply Quote 0
                                • T
                                  tombox @pfahlenbauer last edited by

                                  @pfahlenbauer ich habe noch eine version gebaut bei dem man den stream user eintragen kann was man anscheinend für die motion detection benötigt. für den strahler bräuchte ich Zugang zu einer Kamera um zu sehen welcher Befehl genau abgesetzt wird

                                  P 1 Reply Last reply Reply Quote 0
                                  • P
                                    pfahlenbauer @tombox last edited by

                                    @tombox Danke. Zugang zu meiner Kamera kann ich Dir geben. Schicke ich Dir per PN

                                    Gruß
                                    pfahlenbauer

                                    1 Reply Last reply Reply Quote 0
                                    • mrbungle64
                                      mrbungle64 Developer @tombox last edited by

                                      @tombox

                                      Hallo zusammen,
                                      ich erreiche inzwischen recht schnell das "API rate limit".

                                      ...
                                      2022-11-23 21:30:14.067  - error: tapo.0 (480412) {"error_code":0,"result":{"lockedMinutes":30,"errorCode":"-20004","errorMsg":"API rate limit exceeded"}}
                                      2022-11-23 21:42:14.014  - error: tapo.0 (480804) {"error_code":0,"result":{"lockedMinutes":30,"errorCode":"-20004","errorMsg":"API rate limit exceeded"}}
                                      2022-11-23 21:59:28.199  - error: tapo.0 (481091) {"error_code":0,"result":{"lockedMinutes":30,"errorCode":"-20004","errorMsg":"API rate limit exceeded"}}
                                      

                                      Frage 1) Habt Ihr das auch schon gehabt?
                                      Frage 2) Welches Update-Intervall habt Ihr eingestellt?

                                      Ich hatte zuerst 10 Sekunden eingestellt - bis heute dann 15 Sekunden (bei 3 Tapo P115 Schaltsteckdosen)

                                      T 1 Reply Last reply Reply Quote 0
                                      • T
                                        tombox @mrbungle64 last edited by

                                        @mrbungle64 Eigenartig das sind ja lokale api warum ist da ein rate limit drauf

                                        mrbungle64 1 Reply Last reply Reply Quote 0
                                        • mrbungle64
                                          mrbungle64 Developer @tombox last edited by mrbungle64

                                          @tombox sagte in Test Adapter TP-Link Tapo:

                                          @mrbungle64 Eigenartig das sind ja lokale api warum ist da ein rate limit drauf

                                          Ich denke, dass das im Zusammenhang mit diesen Fehlern auftritt:

                                          2022-11-23 21:09:00.027  - info: tapo.0 (479641) Scheduled restart.
                                          2022-11-23 21:09:00.053  - info: tapo.0 (479641) terminating
                                          2022-11-23 21:09:00.056  - info: tapo.0 (479641) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                          2022-11-23 21:09:00.569  - warn: tapo.0 (479641) get state error: Connection is closed.
                                          2022-11-23 21:09:00.581  - error: tapo.0 (479641) Cannot check object existence of "tapo.0.8022xxxDD97.past7d04.04": DB closed
                                          2022-11-23 21:09:00.583  - warn: tapo.0 (479641) Could not perform strict object check of state tapo.0.8022xxxDD97.past7d04.03: DB closed
                                          2022-11-23 21:09:00.584  - warn: tapo.0 (479641) get state error: Connection is closed.
                                          2022-11-23 21:09:00.587  - error: tapo.0 (479641) Error: Could not check object existence of tapo.0.8022xxxDD97.past7d04.04: Cannot check object existence of "tapo.0.8022xxxDD97.past7d04.04": DB closed
                                          2022-11-23 21:09:00.592  - error: tapo.0 (479641) Cannot check object existence of "tapo.0.8022xxxDD97.past7d04.05": Connection is closed.
                                          2022-11-23 21:09:00.595  - warn: tapo.0 (479641) Could not perform strict object check of state tapo.0.8022xxxDD97.past7d04.04: DB closed
                                          2022-11-23 21:09:00.597  - warn: tapo.0 (479641) get state error: Connection is closed.
                                          2022-11-23 21:09:00.598  - error: tapo.0 (479641) Error: Could not check object existence of tapo.0.8022xxxDD97.past7d04.05: Cannot check object existence of "tapo.0.8022xxxDD97.past7d04.05": Connection is closed.
                                          2022-11-23 21:09:00.602  - error: tapo.0 (479641) Cannot check object existence of "tapo.0.8022xxxDD97.past7d04.06": Connection is closed.
                                          2022-11-23 21:09:00.604  - warn: tapo.0 (479641) Could not perform strict object check of state tapo.0.8022xxxDD97.past7d04.05: DB closed
                                          2022-11-23 21:09:00.605  - warn: tapo.0 (479641) get state error: Connection is closed.
                                          2022-11-23 21:09:00.606  - error: tapo.0 (479641) Error: Could not check object existence of tapo.0.8022xxxDD97.past7d04.06: Cannot check object existence of "tapo.0.8022xxxDD97.past7d04.06": Connection is closed.
                                          2022-11-23 21:09:01.287  - info: host.raspberrypi-3 instance system.adapter.tapo.0 scheduled normal terminated and will be restarted on schedule.
                                          2022-11-23 21:09:01.290  - info: host.raspberrypi-3 Restart adapter system.adapter.tapo.0 because enabled
                                          2022-11-23 21:09:02.882  - info: host.raspberrypi-3 instance system.adapter.tapo.0 started with pid 479711
                                          2022-11-23 21:09:07.324  - info: tapo.0 (479711) starting. Version 0.0.6 (non-npm: TA2k/ioBroker.tapo#5869cef8f69a857a6c4970d13573d0a5edcba1d6) in /opt/iobroker/node_modules/iobroker.tapo, node: v16.18.1, js-controller: 4.0.23
                                          2022-11-23 21:09:07.737  - info: tapo.0 (479711) Login tp TAPO App
                                          2022-11-23 21:09:08.262  - info: tapo.0 (479711) Login succesfull
                                          2022-11-23 21:09:08.492  - info: tapo.0 (479711) Found 3 devices
                                          2022-11-23 21:09:08.861  - info: tapo.0 (479711) Init device 8022xxxCF04 type P115 with ip 192.168.0.115
                                          2022-11-23 21:09:08.961  - info: tapo.0 (479711) Initialized 8022xxxCF04
                                          2022-11-23 21:09:09.253  - info: tapo.0 (479711) Init device 8022xxxDD97 type P115 with ip 192.168.0.117
                                          2022-11-23 21:09:09.355  - info: tapo.0 (479711) Initialized 8022xxxDD97
                                          2022-11-23 21:09:09.716  - info: tapo.0 (479711) Init device 8022xxx4523 type P115 with ip 192.168.0.116
                                          2022-11-23 21:09:09.818  - info: tapo.0 (479711) Initialized 8022xxx4523
                                          2022-11-23 21:09:09.991  - info: tapo.0 (479711) Wait for connections
                                          2022-11-23 21:10:00.052  - info: tapo.0 (479711) Scheduled restart.
                                          2022-11-23 21:10:00.170  - info: tapo.0 (479711) terminating
                                          2022-11-23 21:10:00.175  - info: tapo.0 (479711) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                          2022-11-23 21:10:00.702  - warn: tapo.0 (479711) get state error: Connection is closed.
                                          2022-11-23 21:10:00.713  - error: tapo.0 (479711) Cannot check object existence of "tapo.0.8022xxxDD97.past7d06.04": DB closed
                                          2022-11-23 21:10:00.716  - warn: tapo.0 (479711) Could not perform strict object check of state tapo.0.8022xxxDD97.past7d06.03: DB closed
                                          2022-11-23 21:10:00.718  - warn: tapo.0 (479711) get state error: Connection is closed.
                                          2022-11-23 21:10:00.720  - error: tapo.0 (479711) Error: Could not check object existence of tapo.0.8022xxxDD97.past7d06.04: Cannot check object existence of "tapo.0.8022xxxDD97.past7d06.04": DB closed
                                          2022-11-23 21:10:00.726  - error: tapo.0 (479711) Cannot check object existence of "tapo.0.8022xxxDD97.past7d06.05": Connection is closed.
                                          2022-11-23 21:10:00.728  - warn: tapo.0 (479711) Could not perform strict object check of state tapo.0.8022xxxDD97.past7d06.04: DB closed
                                          2022-11-23 21:10:00.729  - warn: tapo.0 (479711) get state error: Connection is closed.
                                          2022-11-23 21:10:00.730  - error: tapo.0 (479711) Error: Could not check object existence of tapo.0.8022xxxDD97.past7d06.05: Cannot check object existence of "tapo.0.8022xxxDD97.past7d06.05": Connection is closed.
                                          2022-11-23 21:10:00.735  - error: tapo.0 (479711) Cannot check object existence of "tapo.0.8022xxxDD97.past7d06.06": Connection is closed.
                                          2022-11-23 21:10:00.737  - warn: tapo.0 (479711) Could not perform strict object check of state tapo.0.8022xxxDD97.past7d06.05: DB closed
                                          2022-11-23 21:10:00.738  - warn: tapo.0 (479711) get state error: Connection is closed.
                                          2022-11-23 21:10:00.740  - error: tapo.0 (479711) Error: Could not check object existence of tapo.0.8022xxxDD97.past7d06.06: Cannot check object existence of "tapo.0.8022xxxDD97.past7d06.06": Connection is closed.
                                          2022-11-23 21:10:01.408  - info: host.raspberrypi-3 instance system.adapter.tapo.0 scheduled normal terminated and will be restarted on schedule.
                                          2022-11-23 21:10:01.409  - info: host.raspberrypi-3 Restart adapter system.adapter.tapo.0 because enabled
                                          2022-11-23 21:10:03.445  - info: host.raspberrypi-3 instance system.adapter.tapo.0 started with pid 479768
                                          2022-11-23 21:10:08.789  - info: tapo.0 (479768) starting. Version 0.0.6 (non-npm: TA2k/ioBroker.tapo#5869cef8f69a857a6c4970d13573d0a5edcba1d6) in /opt/iobroker/node_modules/iobroker.tapo, node: v16.18.1, js-controller: 4.0.23
                                          2022-11-23 21:10:09.164  - info: tapo.0 (479768) Login tp TAPO App
                                          2022-11-23 21:10:09.565  - error: tapo.0 (479768) Login failed
                                          2022-11-23 21:10:09.569  - error: tapo.0 (479768) {"error_code":0,"result":{"lockedMinutes":30,"errorCode":"-20004","errorMsg":"API rate limit exceeded"}}
                                          

                                          Das tritt mehrmals am Tag auf und die Instanz startet dann immer neu.

                                          Zur Info: das hier ist mit der GitHub Version. Die hatte ich installiert, weil genau das auch schon vorher mit der npm-Version aufgetreten ist.

                                          T 1 Reply Last reply Reply Quote 0
                                          • T
                                            tombox @mrbungle64 last edited by

                                            @mrbungle64 Ja anscheinend wird der adapter jede minute neugestartet

                                            mrbungle64 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            601
                                            Online

                                            31.7k
                                            Users

                                            79.8k
                                            Topics

                                            1.3m
                                            Posts

                                            109
                                            750
                                            177007
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo