ta2k / iobroker.tapo Goto Github PK
View Code? Open in Web Editor NEWioBroker Adapter for TP-Link Tapo
License: MIT License
ioBroker Adapter for TP-Link Tapo
License: MIT License
Version: stable=0.0.0 (0 days old) => latest=0.3.3 (30 days old)
Installs: stable=0 (0%), latest=195 (11.09%), total=1758
Click to use developer portal
Click to edit
Do not close this issue manually as a new issue will be created if condition for update still exists.
Please drop a comment if any reason exists which blocks updating to version 0.3.3 at this time.
Note: This is an automatically generated message and not personally authored by bluefox!
@mcm1957 for evidence
Describe the bug
Since the firmware update yesterday, my Tapo p110 only gets error 52 in iobroker and cannot connect.
To Reproduce
Happened with the firmware update:
Tapo P110(EU)_V1_1.3.0 Build 230905
Expected behavior
I already thought that there were problems because the firmware also indicated changes to the login security in the changelog
Screenshots & Logfiles
2023-12-01 11:37:21.572 error 52 - Get Device Info failed
Versions:
Adapter:
0.2.0
Additional context
It looks like TP-Link is currently patching all WLAN devices, and it looks like you have to rework the adapter for every device that has the new update!?
Ich finde unter Remote leider keine Möglichkeit die drei einzelnen Steckdosen der mehrfachsteckdose P300 einzeln gezielt zu steuern
Da ich das gleiche Problem hatte wie Michaelnorge habe ich auch die Git Version installiert aber leider ohne Erfolg.
Log:
2023-10-20 08:01:38.447 - info: tapo.0 (671384) 802120E85F462887E08BA37F63F201CA2191F555 Received device info {"manufacturer":"tp-link","model":"Tapo C520WS","firmwareVersion":"1.0.11 Build 230621 Rel.72773n","serialNumber":"e374c4ae","hardwareId":1}
2023-10-20 08:01:38.448 - debug: tapo.0 (671384) {"manufacturer":"tp-link","model":"Tapo C520WS","firmwareVersion":"1.0.11 Build 230621 Rel.72773n","serialNumber":"e374c4ae","hardwareId":1}
2023-10-20 08:01:38.448 - debug: tapo.0 (671384) [C520WS 1.0]
2023-10-20 08:01:38.457 - info: tapo.0 (671384) Initialized 802120E85F462887E08BA37F63F201CA2191F555
2023-10-20 08:01:38.457 - debug: tapo.0 (671384) initResult 802120E85F462887E08BA37F63F201CA2191F555 undefined
2023-10-20 08:01:38.557 - info: tapo.0 (671384) Wait for connections
2023-10-20 08:01:48.559 - debug: tapo.0 (671384) Receive camera status
2023-10-20 08:01:48.561 - debug: tapo.0 (671384) [C520WS 1.0]
2023-10-20 08:01:48.562 - debug: tapo.0 (671384) [C520WS 1.0]
2023-10-20 08:01:48.563 - debug: tapo.0 (671384) [C520WS 1.0]
2023-10-20 08:01:48.735 - debug: tapo.0 (671384) makeTAPOAPIRequest url: https://192.168.10.156/stok=hF3!)OCq!0(yFWX)))(X8hJT4J..NN../ds, json: {"result":{"responses":[{"method":"getAlertConfig","result":{"msg_alarm":{"chn1_msg_alarm_info":{"enabled":"off","light_alarm_enabled":"on","alarm_mode":["sound","light"],"alarm_type":"0","light_type":"1","sound_alarm_enabled":"on","alarm_volume":"high","alarm_duration":"0"}}},"error_code":0},{"method":"getLensMaskConfig","result":{"lens_mask":{"lens_mask_info":{"enabled":"off"}}},"error_code":0},{"method":"getForceWhitelampState","result":{},"error_code":-40210}]},"error_code":0}
2023-10-20 08:01:48.735 - debug: tapo.0 (671384) {"alert":false,"lensMask":false,"forceWhiteLamp":false}
2023-10-20 08:01:48.885 - error: tapo.0 (671384) uncaught exception: callback.call is not a function
2023-10-20 08:01:48.885 - error: tapo.0 (671384) TypeError: callback.call is not a function
at Cam. (/opt/iobroker/node_modules/onvif/lib/events.js:309:14)
at parseSOAPString (/opt/iobroker/node_modules/onvif/lib/utils.js:108:3)
at IncomingMessage. (/opt/iobroker/node_modules/onvif/lib/cam.js:297:4)
at IncomingMessage.emit (node:events:526:35)
at IncomingMessage.emit (node:domain:489:12)
at endReadableNT (node:internal/streams/readable:1359:12)
at processTicksAndRejections (node:internal/process/task_queues:82:21)
2023-10-20 08:01:48.885 - error: tapo.0 (671384) callback.call is not a function
2023-10-20 08:01:48.908 - info: tapo.0 (671384) terminating
2023-10-20 08:01:48.909 - debug: tapo.0 (671384) Plugin sentry destroyed
2023-10-20 08:01:48.909 - warn: tapo.0 (671384) Terminated (UNCAUGHT_EXCEPTION): Without reason
Ich bekomme genau alle 5 Minuten diese Fehlermeldungen im Log:
tapo.0 | 2023-10-07 18:14:43.918 | info | Found 5 devices
-- | -- | -- | --
tapo.0 | 2023-10-07 18:14:43.605 | info | Login succesfull
tapo.0 | 2023-10-07 18:14:42.925 | info | Login tp TAPO App
tapo.0 | 2023-10-07 18:14:42.891 | info | starting. Version 0.0.8 (non-npm: TA2k/ioBroker.tapo#bec54f4bf5d6dbcaf04e8d9e691a75ff1c06e346) in /opt/iobroker/node_modules/iobroker.tapo, node: v18.17.1, js-controller: 5.0.12
host.iobroker-pm | 2023-10-07 18:14:41.899 | info | instance system.adapter.tapo.0 started with pid 2320
host.iobroker-pm | 2023-10-07 18:14:11.787 | info | Restart adapter system.adapter.tapo.0 because enabled
host.iobroker-pm | 2023-10-07 18:14:11.786 | error | instance system.adapter.tapo.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
host.iobroker-pm | 2023-10-07 18:14:11.786 | error | Caught by controller[0]: at processTicksAndRejections (node:internal/process/task_queues:82:21)
host.iobroker-pm | 2023-10-07 18:14:11.786 | error | Caught by controller[0]: at emitErrorCloseNT (node:internal/streams/destroy:116:3)
host.iobroker-pm | 2023-10-07 18:14:11.786 | error | Caught by controller[0]: at emitErrorNT (node:internal/streams/destroy:151:8)
host.iobroker-pm | 2023-10-07 18:14:11.786 | error | Caught by controller[0]: at Socket.emit (node:domain:489:12)
host.iobroker-pm | 2023-10-07 18:14:11.786 | error | Caught by controller[0]: at Socket.emit (node:events:514:28)
host.iobroker-pm | 2023-10-07 18:14:11.786 | error | Caught by controller[0]: at Socket.socketErrorListener (node:_http_client:501:9)
host.iobroker-pm | 2023-10-07 18:14:11.786 | error | Caught by controller[0]: at ClientRequest.emit (node:domain:489:12)
host.iobroker-pm | 2023-10-07 18:14:11.786 | error | Caught by controller[0]: at ClientRequest.emit (node:events:526:35)
host.iobroker-pm | 2023-10-07 18:14:11.786 | error | Caught by controller[0]: at ClientRequest.<anonymous> (/opt/iobroker/node_modules/onvif/lib/cam.js:328:4)
host.iobroker-pm | 2023-10-07 18:14:11.786 | error | Caught by controller[0]: at Cam.<anonymous> (/opt/iobroker/node_modules/onvif/lib/events.js:309:14)
host.iobroker-pm | 2023-10-07 18:14:11.785 | error | Caught by controller[0]: TypeError: callback.call is not a function
tapo.0 | 2023-10-07 18:14:11.698 | warn | Terminated (UNCAUGHT_EXCEPTION): Without reason
tapo.0 | 2023-10-07 18:14:11.698 | info | terminating
tapo.0 | 2023-10-07 18:14:11.686 | error | callback.call is not a function
tapo.0 | 2023-10-07 18:14:11.685 | error | TypeError: callback.call is not a function at Cam.<anonymous> (/opt/iobroker/node_modules/onvif/lib/events.js:309:14) at ClientRequest.<anonymous> (/opt/iobroker/node_modules/onvif/lib/cam.js:328:4) at ClientRequest.emit (node:events:526:35) at ClientRequest.emit (node:domain:489:12) at Socket.socketErrorListener (node:_http_client:501:9) at Socket.emit (node:events:514:28) at Socket.emit (node:domain:489:12) at emitErrorNT (node:internal/streams/destroy:151:8) at emitErrorCloseNT (node:internal/streams/destroy:116:3) at processTicksAndRejections (node:internal/process/task_queues:82:21)
tapo.0 | 2023-10-07 18:14:11.685 | error | uncaught exception: callback.call is not a function
ioBroker läuft auf Proxmox, habe das System heute aufgesetzt aus einem Backup einer Raspberry Installation, somit ist das System auf dem neusten Stand.
Alle anderen Adapter laufen soweit, nur mit TAPO habe ich das Problem.
Die Fehlermeldungen (die alle exakt 5 Minuten erscheinen) sagen mir leider nichts.
Den Updateintervall innerhalb der App habe ich auf 60 Sekunden laufen.
Objekte habe ich gelöscht, auch den Adapter habe ich gelöscht und neu aufgesetzt - alles ohne Erfolg.
Außerdem habe ich testweise alle anderen testweise Adapter deaktiviert, sowie piHole ausgeschaltet.
Ich hatte identische Accounts bei den Apps Tapo und Kasa. Bei einem Update von Tapo sind plötzlich zwei Steckdosen mit in der Liste im Handy erschienen, die allerdings nicht im ioBroker-Log zu sehen waren.
Also habe ich einen komplett neuen Account bei Tapo eingerichtet nur mit den fünf Kameras, aber der Fehler ist immer noch da.
Ich komme einfach nicht dahinter, was der Fehler sein könnte.
Ich habe gerade in mein logfiles die Meldung entdeckt welche alle 10 Sekunden kommt:
Error: Invalid device confirm
Es passiert die ganze Zeit ca alle 10 Sekunden, egal ob ich den Raspberry Pi 4 neu starte, iob fix anwende oder den Adapter neu starte.
Ich habe auch schon die c110, c210, und p110 neu gestartet.
Normalerweise melden sie Geräte sich ganz normal an und funktionieren ganz normal ohne Auffälligkeiten.
Versions:
Ich weiß leider nicht wann das Problem angefangen hat und welches der drei Geräte damit gemeint ist, habe dies durch Zufall entdeckt, in der Tapo App funktionieren alle Geräte normal.
Describe the bug
After a few (2-4?) days of working fine, the adapter no longer turns the light bulbs on/off. Object changes don't do anything.
The error message
322 Error: Request failed with status code 403
starts appearing in the log after each refreshInterval.
After restarting the adapter everything works perfectly fine again. So I assume something happens on startup which also should happen when this error starts appearing. Maybe there is an access token which needs to be refreshed from time to time?
To Reproduce
Steps to reproduce the behavior:
Expected behavior
It should continue working infinitely. But it no longer switches light bulbs and shows "322 Error: Request failed with status code 403"
Screenshots & Logfiles
If applicable, add screenshots and logfiles to help explain your problem.
Versions:
Ist eher ein development request.
Ich benutze zwei C210 und habe mich gefragt ob es möglich wäre, den Adapter so zu erweitern, dass man die gespeicherten Positionen ansteuern könnte?
Hi,
vielen Dank für die Entwicklung des Adapters,
ich hab die Entwicklung im Forum mit verfolgt.
Du hattest da erwähnt, dass es einen Datenpunkt für die Kamera geben soll, wo der integrierte BWM die Bewegung detected.
Hab die Version 0.0.7 installiert und danach die Instanz gestoppt und den Objectbaum gelöscht, Instanz wieder gestartet - leider kein DP dabei.
Version: stable=0.0.8 (370 days old) => latest=0.2.0 (15 days old)
Installs: stable=1356 (80.91%), latest=169 (10.08%), total=1676
Click to use developer portal
Click to edit
Note: This is an automatically generated message and not personally authored by bluefox!
Gentlemen,
zunächst vielen Dank für den reibungslos funktionierenden Adapter! Gerne mal paypal nennen. Das investierte Zeit würde ich gerne mal honorieren!
Besteht die Möglichkeit einen Datenpunkt am. Beispiel von MotionDetected == true/False auch für
Vielen Dank und weiter so!
Grüße MINKI
Kannst Du in den Einstellungen eine Option einbauen, die die Ausgabe von Fehlermeldungen unterdrückt?
Wenn mal eine Dose offline ist, ballern mir die Fehler das Log voll.
Vielleicht sogar gestaffelt - evtl. als ComboBox.
Wenn eine Dose offline ist, würde mir persönlich die erste Meldung reichen.
Das muss nicht zwingend bei jedem Refresh gemeldet werden. Und schon gar nicht so viele Meldungen.
tapo.0 | 2022-12-22 12:37:12.041 | error | 326 Error Code: 9999, Session Timeout 192.168.178.70
tapo.0 | 2022-12-22 12:37:11.978 | error | Error Code: 9999, Session Timeout
tapo.0 | 2022-12-22 12:37:11.924 | error | Error Code: 9999, Session Timeout
tapo.0 | 2022-12-22 12:37:11.856 | error | Error Code: 9999, Session Timeout
tapo.0 | 2022-12-22 12:37:11.803 | error | Error Code: 9999, Session Timeout
tapo.0 | 2022-12-22 12:36:42.101 | error | 326 Error Code: 9999, Session Timeout 192.168.178.70
tapo.0 | 2022-12-22 12:36:42.025 | error | Error Code: 9999, Session Timeout
tapo.0 | 2022-12-22 12:36:41.946 | error | Error Code: 9999, Session Timeout
tapo.0 | 2022-12-22 12:36:41.874 | error | Error Code: 9999, Session Timeout
tapo.0 | 2022-12-22 12:36:41.797 | error | Error Code: 9999, Session Timeout
tapo.0 | 2022-12-22 12:36:31.551 | error | {"error_code":-20571,"msg":"Device is offline"}
News arae for 0.2.1 has syntactically error
Please fix
The current stable verion of this adapter is 0.0.8
Please let us know if this release is fully functional or the adapter ii working only when using newer Release currently not avaialbal at stable repository.
Ich nutze unter Anderem auch eine Innenkamera, die an einer Schaltsteckdose angeschlossen ist und daher nur läuft, wenn niemand zu Hause ist.
Leider spinnt der Adapter rum und schreibt mir alle 10 Sekunden Fehlermeldungen ins Log.
Kann man vielleicht diese Fehlermeldungen nicht als "error" sondern als "warning" ins Log schreiben?
Damit wäre mir schon sehr geholfen.
Alternativ wäre ein Abhaken der vom Adapter gefundenen Geräte super. Dann könnte ich eben diese Kamera aushaken!
Danke :-)
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots & Logfiles
If applicable, add screenshots and logfiles to help explain your problem.
Versions:
Additional context
Add any other context about the problem here.
Ich benutze die neuste Version v0.20 und die Kamera hat die 1.0.27.
Die Kamera ist schon im System drin, aber Stream und Steuerung der Kamera funktionieren nicht !!
tapo.0 | 2024-01-11 04:46:38.210 | info | Wait for connections
-- | -- | -- | --
tapo.0 | 2024-01-11 04:46:38.042 | info | Initialized ++++
tapo.0 | 2024-01-11 04:46:38.023 | 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-11 04:46:37.040 | info | Init device +++ type C225 1.0 with ip 192.168.2.114
tapo.0 | 2024-01-11 04:46:36.806 | info | Found 1 devices
tapo.0 | 2024-01-11 04:46:36.610 | info | Login succesfull
tapo.0 | 2024-01-11 04:46:36.141 | info | Login tp TAPO App
tapo.0 | 2024-01-11 04:46:36.057 | info | starting. Version 0.2.0 (non-npm: TA2k/ioBroker.tapo) in /opt/iobroker/node_modules/iobroker.tapo, node: v18.19.0, js-controller: 5.0.12
host.raspberrypi | 2024-01-11 04:46:35.132 | info | instance system.adapter.tapo.0 started with pid 964
host.raspberrypi | 2024-01-11 04:46:32.603 | info | instance system.adapter.tapo.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
tapo.0 | 2024-01-11 04:46:32.535 | info | terminating
host.raspberrypi | 2024-01-11 04:46:32.073 | info | stopInstance system.adapter.tapo.0 send kill signal
tapo.0 | 2024-01-11 04:46:32.034 | info | Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
tapo.0 | 2024-01-11 04:46:32.033 | info | terminating
tapo.0 | 2024-01-11 04:46:32.033 | info | Got terminate signal TERMINATE_YOURSELF
Ich würde mir im Adapter eine Liste mit den verfügbaren Kameras wünschen, die ich abhaken kann, je nachdem welche Kamera vom Adapter kontrolliert werden soll....
Dear adapter developer,
I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter tapo for common errors and appropiate suggestions to keep this adapter up to date.
Please see the result of the check below.
ERRORS:
WARNINGS:
👍 No suggestions found
Please review issues reported and consider fixing them as soon as appropiate.
Errors reported by repository checker should be fixed as soon as possible. Some of them require a new release to be considered as fixed. Please note that errors reported by checker might be considered as blocking point for future updates at stable repository.
Warnings reported by repository checker should be reviewed. While some warnings can be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.
You may start a new check or force the creation of a new issue at any time by adding the following comment to this issue:
@iobroker-bot recheck
@iobroker-bot recreate
Please note that I (and the server at GitHub) have always plenty of work to do. So it may last up to 30 minutes until you see a reaction. I will drop a comment here as soon as I start processing.
Feel free to contact me (@ioBroker-Bot) if you have any questions or feel that an issue is incorrectly flagged.
And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.
your
ioBroker Check and Service Bot
@mcm1957 for evidence
Last update at Fri, 13 Sep 2024 13:42:43 GMT based on commit a0e9a3b
ioBroker.repochecker 3.0.5
Access right check for adapter tapo returned the following issue:
Bluefox was not found in the collaborators on NPM!.
Please execute in adapter directory: "npm owner add bluefox iobroker.tapo"
Current maintainers are
tomboxi [email protected]
Please fix the above error as soon as possible.
All adapters listed at ioBroker repositories must have 'bluefox' added as maintainer.
Future version updates at the repositories will be suspended until this problem is fixed.
Wieder mal Probleme nach einem Update der Kamera C225 auf die Version 1.0.27. Lensmark funktioniert nur kurz nach Neustart der cam. Die python3 scripts zur positionssteuerung gehen gar nicht mehr.
Version: stable=0.0.8 (333 days old) => latest=0.1.0 (15 days old)
Installs: stable=1393 (87.78%), latest=144 (9.07%), total=1587
Click to use developer portal
Click to edit
Note: This is an automatically generated message and not personally authored by bluefox!
Version: stable=0.0.8 (353 days old) => latest=0.1.1 (15 days old)
Installs: stable=1409 (84.52%), latest=150 (9%), total=1667
Click to use developer portal
Click to edit
Note: This is an automatically generated message and not personally authored by bluefox!
Describe the bug
Ich kann mich seit einigen Tagen nicht mehr einloggen, habe schon GitHub Version installiert.
Es kommt immer ein Login error:
Error: Unable to find token in response, probably your credentials are not valid. Please make sure you set your TAPO Cloud password
Der Adapter wird aber grün aber es werden keine Daten aktualisiert, ich habe aktuell eine p110 und eine c110 und eine c210, bei keinem Gerät aktualisieren sich die datenpunkte.
Error: Unable to find token in response, probably your credentials are not valid. Please make sure you set your TAPO Cloud password
Des weiteren fehlt bei der c210 der Datenpunkt
"lensMask" komplett.
To Reproduce
FW von allen tapo geräten auf den neuesten Stand bringen, tapo Adapter aus dem iobroker App Store oder von GitHub installieren.
Expected behavior
Ich möchte dass meine Steckdose einfach wieder erkannt wird damit ich Alexa Meldungen bekommen kann wenn meine Waschmaschine fertig ist.
Und ich möchte bei Abwesenheit den privatsphärenmodus meiner Kameras automatisch deaktivieren, und bei Anwesenheit automatisch den privaten Modus aktivieren (lensMask)
Screenshots & Logfiles
Error: Unable to find token in response, probably your credentials are not valid. Please make sure you set your TAPO Cloud password
Versions:
Additional context
Wie man auch schon in anderen Threads lesen kann ist wohl eine Änderung der sicherheitsmechanismen in der aktuellen Firmware der Geräte verantwortlich.
Ich hoffe dass man dies wieder gerade biegen kann, und das Tapo sich nicht gegen uns smart home zentralen User wendet.
Dear adapter developer,
I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter tapo for common errors and appropiate suggestions to keep this adapter up to date.
Please see the result of the check below.
ERRORS:
WARNINGS:
👍 No suggestions found
Please review issues reported and consider fixing them as soon as appropiate.
Errors reported by repository checker should be fixed as soon as possible. Some of them require a new release to be considered as fixed. Please note that errors reported by checker might be considered as blocking point for future updates at stable repository.
Warnings reported by repository checker should be reviewed. While some warnings can be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.
You may start a new check or force the creation of a new issue at any time by adding the following comment to this issue:
@iobroker-bot recheck
@iobroker-bot recreate
Please note that I (and the server at GitHub) have always plenty of work to do. So it may last up to 30 minutes until you see a reaction. I will drop a comment here as soon as I start processing.
Feel free to contact me (@ioBroker-Bot) if you have any questions or feel that an issue is incorrectly flagged.
And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.
your
ioBroker Check and Service Bot
@mcm1957 for evidence
Last update at Wed, 11 Sep 2024 04:45:24 GMT
Describe the bug
I have created a VIS visualization of my power "network" using Tapo devices and some other stuff (like solar panels). Doing so, I have noticed that the values from the tapo devices are not current values but outdated. So I have checkd in ioBroker directly, and even there, all values are "old", they never get updated, only when I either restart the Tapo adapter instance or anything, that will then also restart the adapter, although I set a update rate of 60s (I have also tried other values). Within the log, I can't see any error that might be related to this (Tapo adapter has errors for not-connected devices showing like "FetchError: request to https://192.168.0.83/ failed, reason: connect EHOSTUNREACH 192.168.0.83:443"
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Values should get updated according to the set frequency.
Screenshots & Logfiles
If needed, I could provide the logfile via mail.
Versions:
Additional context
Add any other context about the problem here.
ioBroker
Platform linux
OS linux
Architecture arm
CPUs 4
Speed 1500 MHz
Model ARMv7 Processor rev 3 (v7l)
RAM 3.75 GB
System uptime 4 d. 02:18:26
Node.js v18.17.1
time 1694542895815
timeOffset -120
Number of adapters 496
NPM 9.8.1
Disk size 28.98 GB
Disk free 20.9 GB
Uptime 4 d. 02:38:16
Active instances 14
path /opt/iobroker/
Hostname ioBroker
I have a TAPO C200. It reports every movement in the Echo Show, but I can't get it to display the image automatically.
I wanted to implement this in ioBroker. The tapo adapter is now green but there are ongoing error messages
"Error: Unable to find token in response, probably your credentials are not valid. Please make sure you set your TAPO Cloud password"
How can I switch this off? I don't have a cloud.
Furthermore, I can only find static data points from the camera in Objects, none that can be used to communicate with the camera or query the motion detection.
If I read through the forum posts, this should work somehow.
Can anybody give me a hint how to overcome this?
Regards Gerhard from Austria
Translated with DeepL.com (free version)
The main README.md at repository root sould be written in pure english- Of course ist ok to add a README-de.md (or Readmes for other languages. Und ist ok too to add a link insode the main README.md
If you want to prodvide documentation for users those files should be located at doc directory.
And please a omplete changelog to README.md. Users should be able to resd what has changes between 0.0.8 and current release
Version: stable=0.0.8 (435 days old) => latest=0.2.9 (15 days old)
Installs: stable=1353 (74.26%), latest=161 (8.84%), total=1822
Click to use developer portal
Click to edit
Note: This is an automatically generated message and not personally authored by bluefox!
Do not close this issue manually as a new issue will be created if condition for update still exists
@mcm1957 for evidence
ich habe 3 Tapo Steckdosen, die auch offensichtlich erkannt werden, aber die Verbindung kann nicht richtig hergestellt werden.
Hat jemand eine Idee?
tapo.0
2023-11-24 22:00:18.330 info Wait for connections
tapo.0
2023-11-24 22:00:18.301 error 52 - Get Device Info failed
tapo.0
2023-11-24 22:00:18.301 info Initialized 8022B22797E0BC1A67FCCCBE83F418022144ABC0
tapo.0
2023-11-24 22:00:18.300 error 97 Error Code: 1003, undefined 192.168.178.54
tapo.0
2023-11-24 22:00:18.206 info Init device 8022B22797E0BC1A67FCCCBE83F418022144ABC0 type P100 with ip 192.168.178.54
tapo.0
2023-11-24 22:00:17.973 error 52 - Get Device Info failed
tapo.0
2023-11-24 22:00:17.972 info Initialized 80225F1DC2AA3E5C6954AB6DFFB948C22145A6DF
tapo.0
2023-11-24 22:00:17.972 error 97 Error Code: 1003, undefined 192.168.178.53
tapo.0
2023-11-24 22:00:17.892 info Init device 80225F1DC2AA3E5C6954AB6DFFB948C22145A6DF type P100 with ip 192.168.178.53
tapo.0
2023-11-24 22:00:17.624 info Initialized 8022FF6FFCC293445C2AF82A10FB55A9212B1264
tapo.0
2023-11-24 22:00:17.516 info Init device 8022FF6FFCC293445C2AF82A10FB55A9212B1264 type P110 with ip 192.168.178.48
tapo.0
2023-11-24 22:00:17.219 info Found 3 devices
tapo.0
2023-11-24 22:00:16.945 info Login succesfull
tapo.0
2023-11-24 22:00:16.387 info Login tp TAPO App
tapo.0
2023-11-24 22:00:16.328 info starting. Version 0.0.8 in /opt/iobroker/node_modules/iobroker.tapo, node: v18.17.1, js-controller: 5.0.16
tapo.0
2023-11-24 22:00:11.985 info terminating
tapo.0
2023-11-24 22:00:11.482 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
tapo.0
2023-11-24 22:00:11.480 info terminating
tapo.0
2023-11-24 22:00:11.477 info Got terminate signal TERMINATE_YOURSELF
Wenn der Adapter beim Start keine Verbindung zur Cloud herstellen kann, springt er zwar in eine Fehlerbehandlung und loggt den Fehler, der Status der Verbindung wird aber trotzdem auf "true" gesetzt.
this.setState in Zeile 224 wird also immer aufgerufen, egal ob ein Fehler aufgetreten ist oder nicht.
Gruß
Bernd
The alias name and the nickname attributes of a P115 plug are displayed in a Base64 encoded format and therefor not human readable. They should be decoded before written to the attributes.
Describe the bug
I have created a VIS visualization of my power "network" using Tapo devices and some other stuff (like solar panels). Doing so, I have noticed that the values from the tapo devices are not current values but outdated. So I have checkd in ioBroker directly, and even there, all values are "old", they never get updated, only when I either restart the Tapo adapter instance or anything, that will then also restart the adapter, although I set a update rate of 60s (I have also tried other values). Within the log, I can't see any error that might be related to this (Tapo adapter has errors for not-connected devices showing like "FetchError: request to https://192.168.0.83/ failed, reason: connect EHOSTUNREACH 192.168.0.83:443"
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Values should get updated according to the set frequency.
Screenshots & Logfiles
If needed, I could provide the logfile via mail.
Versions:
Additional context
Add any other context about the problem here.
ioBroker
Platform linux
OS linux
Architecture arm
CPUs 4
Speed 1500 MHz
Model ARMv7 Processor rev 3 (v7l)
RAM 3.75 GB
System uptime 4 d. 02:18:26
Node.js v18.17.1
time 1694542895815
timeOffset -120
Number of adapters 496
NPM 9.8.1
Disk size 28.98 GB
Disk free 20.9 GB
Uptime 4 d. 02:38:16
Active instances 14
path /opt/iobroker/
Hostname ioBroker
Ich habe seit einigen Tagen bei einer TAPO C100 das Phänomen das das Objekt "motion Event" nicht mehr schaltet.
Meine Kameras C320WS und C310 sind nicht betroffen.
Beim Starten des Adapters wird die C100 im Log angezeigt und initialisiert, auch sind keine Fehlermeldungen vorhanden (debug).
In der App funktioniert die Kamera normal. Sie zeichnet bei Bewegung Videos auf der SD-Karte auf und ich werde benachrichtigt.
Ich habe die Cam bereits komplett resettet und neu eingebunden, aber ohne Erfolg.
Auch den Benutzernamen und das Passwort der Cam stimmt.
Edit: Die "Remote" unter den Objekten funktioniert (z.B. das setLensMaskConfig)
*Heute gab es ein firmwareupdate auf 1.5.5 Build 20230927 Rel 40646.
Seitdem Fehlerlog 52 - Get Device Info failed
Gerät funktioniert nicht mehr in Iobroker und wird auch nach Reset und neu einbinden in die App nicht mehr gelistet.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.