-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
❗❗❗Invalid cloud password on firmware build 230921 and higher #551
Comments
I am using the iOS app and everything is working fine. My camera is a Tapo C110 with Firmware Version 1.3.11 Build 231117 Rel. 47346n(5553) and as of today is not working. // image removed. |
@reypm have you opened and used the app just before it stopped working or only after? |
@JurajNyiri Yes, everything is working as expected and nothing has changed on my end with the app, I do keep my iOS apps up to date most of the time, not sure when the Tapo app did update to the latest |
This comment was marked as duplicate.
This comment was marked as duplicate.
Operating System: Android pytapo output is: "Exception: Invalid authentication data" I'm really hoping tp-link is calling you soon ;) |
@JurajNyiri I am using this other custom component repository as well and today I noticed it disconnected some of my Tapo devices, upon research some people reported issues in their issues and the problem was fixed with version 3.1.0. I updated the component today and is working fine, I am using the very same creds I am using with your component, you can maybe take something from there or just take a look
|
@petretiandrea any idea if this might be related? I know your integration uses different communication method completely. |
I have 3x C200 with 1.3.11 sice December (#472 (comment)) with blocked DNS (only NTP is enabled - otherwise they are in zombie state) and so far no major issues. |
@scetu what does this mean? is there a guide for this? |
Blocking the access after having the issue will not help — and I am not sure if it helps at all even when not having issue as the update might be pushed through the app. In order to use the camera you will either need to wait or follow steps in main post in this issue - downgrade firmware. |
Hi @JurajNyiri José |
5.4.17PSA Has nothing new. It’s a way how to get the information to the end users and help them prevent having issues. |
Thanks for pushing the PSA as an "update". I would have missed this if it wasn't for it. I block internet access to all my cameras but from time to time I update the firmware just to keep them up-to-date. It would be a lot of work to factory reset them just to get them to work again. I see you have the "help wanted" tag, I have a C200 that I can use for testing, and I might be able to do some python debugging if that helps. |
Use AdGuard Home or Pi-Hole and add custom rules for filtering
|
hello, |
Thanks for this "update", I would have missed the issue without it. I'm using a Tapo C200 with firmware 1.3.9 Build 231019 according to the integration. I've just blocked updates with AdGuard filters, and I haven't launched the Android app. So far, everything is still working perfectly. |
Hi, actually I'm not calling the "cloud", so no "cloud password". My integration is completely based on local communication. |
Just to be entierly precise : this doesn't block their internet access per se, if the firmware contains direct IP address Pi-Hole won't be able to block it. Hence, why I'd try to block their internet access at the router level. Most consumer router from ISP comes with a "child protection mode" to block internet from specific devices at specific time, which is what I would do if I didn't have a "true" configurable router. However, this would also block NTP (Server to which the device request to, to get current time and date) requests too. That's the solution I use at my mom's house, and it works perfectly fine, with an automation to force sync date / time from HA to Tapo devices.
|
Mine are still working (well - as "well" as they always have). Have now blocked their internet access in my router, just because there is no need for them to have internet access. Cams: Tapo C200 (two of them) |
I believe accessing (or not) cameras from mobile Tapo application might explain why some cameras still operates well. I manage 3 locations with different set of users, all having same Tapo C100/C110 cameras, with same firmware versions (1.3.9 & 1.3.11, depending on the camera model). Two locations are "broken" since last few days - HA claiming authorization errors. 3rd one still works smoothly. The difference is that in two broken locations users use Android Tapo application to monitor cameras. 3rd location is only integrated with HA. I made some experiments in this 3rd location - resetting camera, resetting HA, even removing and adding integration in HA - everything still works smoothly. All locations & cameras has an Internet access so this factor does not seems to explain the phenomenon in my case. |
Thank you so much for all the hard work.
So good to have my cameras back 🙂
Sent from Outlook<http://aka.ms/weboutlook>
…________________________________
From: Juraj Nyíri ***@***.***>
Sent: 13 December 2024 13:07
To: JurajNyiri/HomeAssistant-Tapo-Control ***@***.***>
Cc: WeatherWitch ***@***.***>; Manual ***@***.***>
Subject: Re: [JurajNyiri/HomeAssistant-Tapo-Control] ❗❗❗Invalid cloud password on firmware build 230921 and higher (Issue #551)
Victory for Local Control: TP-Link Enables Third-Party Compatibility<https://github.com/JurajNyiri/HomeAssistant-Tapo-Control/releases/tag/6.0.0>
On November 5, 2023, I reported a security vulnerability to TP-Link. They addressed the issue, but by April 2024, users began reporting that their Tapo cameras had stopped working with this integration (see issue<#551 (comment)>).
Thankfully, a temporary workaround was discovered soon after: disabling the cameras' internet access and performing a factory reset restored full functionality.
Then, on May 8, 2024, I was personally affected by this change. Motivated to find a lasting solution, I developed a proof-of-concept (POC)<#551 (comment)> just a week later. Within two days, the POC was polished and ready for use<#551 (comment)>. This solution worked but required the integration to communicate with the TP-Link cloud temporarily. I reached out to TP-Link to ensure they were comfortable with exposing details of their cloud functionality.
Throughout this period, I maintained active communication with TP-Link, seeking a mutually agreeable solution. TP-Link proposed a dedicated cloud endpoint for integration but ultimately decided against implementing it. By October 2024, my proposed solution was also declined<#551 (comment)>.
Finally, the breakthrough came this month: as of December 2024, TP-Link has introduced a toggle in the Tapo app that re-enables local communication. This new feature, available on any firmware version and with internet-enabled cameras, allows seamless integration with Home Assistant and other third-party tools implementing the local protocol.
To activate this feature, simply go to your Tapo App and then click on:
Me > Tapo Lab > Third-Party Compatibility > On.
This is the best outcome we could have hoped for. It restores full local control, reaffirms TP-Link’s commitment to the open-source community, and ensures continued compatibility with Home Assistant.
________________________________
TL;DR:
Cameras are now fully functional online with the latest firmware. Enable Third-Party Compatibility in the Tapo app to integrate seamlessly with Home Assistant and other third-party tools.
—
Reply to this email directly, view it on GitHub<#551 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AG4CFCUOMN53I7CRWBIRHS32FLLXRAVCNFSM6AAAAABGFXTRQSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBRGQZDGMJZGU>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Thanks a lot, what a great news ! All credits due to JurajNyiri of course, for his hard work and dedication. But let's not forget TP Link / Tapo which allowed third-party interactions and listened to feedback and suggestions of external developers. Not all manufacturers do this (see Chamberlain and their decision to block control of their garage door from third party tools, Everything Smart Home had a nice ranting video about that, hope he would mention this happy ending with Tapo in a next video). So glad to have my 4 tapo cameras, and looking to get even more after this great move from TP Link / Tapo. |
Many many thanks @JurajNyiri for your effort and your continous communication and updates!! |
I'm on the beta program, but the lastest version is still 3.7.811. So we're patiently waiting for the update! |
In Germany also still no Android update. |
Also, big thanks for the effort here from Denmark! After adding the camera to HA, can 2-factor auth be re-enabled or does it need to stay disabled? |
Update available in Germany in the Beta Channel. Did the following steps to get it working (I had still the invalid cloud password like @t0bst4r):
Thank you so much @JurajNyiri !!!!!! I know from personal experience how difficult it is to communicate with manufacturers about stuff like this. Amazing that you put your time into making the integration work again. And we have to admit that this is also a huge step forward for TP-Link. Allowing Third-Party-Integrations is sadly not always "by-design". |
@blitzdose is that for Android? |
Yes PlayStore, Android. Signed up for the beta a couple of days ago and today I looked there and the update was online |
Thank you :) |
Works PERFECTLY ... I have my home assistant connected to my MAIN home automation system HUBITAT - and through the home assistant device bridge I am getting ALL of the camera attributes now so I can write automations to do darn near anything - IN HUBITAT. Wow great job Juraj and THANK YOU so much for the hard work AND hanging with this. How you interfaced with Tapo was very well done as well. Also - a BIG thank you to the folks at TP LINK for allowing this YOU ROCK!!! |
I am already beta tester of the Play Store version and it is still version 3.7.811, the third party integration function does not appear. |
Has anyone got this working with the C120 cameras? I've tried everything and can't get it to work. |
I thought it was fantastic and started testing it early on—it worked perfectly. Thanks to the developers and the team! Unfortunately, when I updated to version 6.0.0, the motion sensors on the C500 simply disappeared. I removed the camera from HA and re-added it, but the sensors still don’t show up. On the TC70, however, the sensors are working perfectly fine. Something in this version caused the C500 sensors to vanish. |
Follow faq for that. There is virtually no difference in 6.0.0 to previous version functionality wise. |
It's working wonderfully well with the C200 and C70 cameras. I've been waiting for this since April without updating this integration in HA. Huge thanks to everyone involved, especially @JurajNyiri, for the amazing work for the community. |
So happy it works again (C200 & C510W) !! |
This comment was marked as off-topic.
This comment was marked as off-topic.
Anyway, with that out of the way I really want to thank you @JurajNyiri for your continued effort on this matter. Communication with big companies tends to be a nightmare, but you made it work somehow. It's really awesome to see how it led to the absolutely best solution TP-Link could have offered us. Thanks again! |
Thanks a lot, I was able to add my c320ws 2.0, however for some reason HD stream is not available most of the times 🤷♂️ not sure why |
Hey @JurajNyiri I have a suggestion How about locking this issue since it's now addressed and instead, create a discussion for the chit chat post today? Feels like a lot of noise and even if there is a real new issue, it deserves a new issue. |
Great news, unfortunately i live in an android home, i don't even know people with iOS so i will have to wait for the update, but atleast it's on it's way. |
does the camera need to be connected to the internet for this to work? currently i only allow ntp |
Thank you @JurajNyiri and Tapo for this. Especially your persistence and conviction, @JurajNyiri was great and as you write in the update notes confirmed the commitment to open source. |
Thanks JurajNyiri. |
I have the opposite problem. C210 v1 and despite many restarts/resets it’s stuck on older firmware 1.3.11 and won’t see newer version. Has the ‘can only be locally controlled’ message. Tried disabling pihole, VPN and changing DNS to google for camera setup. Still no luck yet which means no notifications from the app. Motion detection also unusably slow which I assume would be resolved if I can get the firmware updated. Anyone any suggestions or experiencing something similar? |
Have you tried manually applying newer firmware via the SD card method? |
Locking this again for organisation of information. If you have any issues with camera feel free to use discussions, or issues if you are experiencing integration problems. |
Thread for invalid cloud password on firmware build 230921 and higher
Notice: This issue has been locked for discussion, and will be used to post updates only. Discuss or ask a question.
There has been reports of users on firmwares 1.3.8, and newer, or on some cameras other firmwares with build 230921 and newer of integration stopping to work. This shows as cloud password not being accepted.
I have been in touch with tplink regarding a security vulnerability I reported in the past and this is most probably a fix for it.
This currently only affects some users, not all and most probably requires camera to be connected to the internet in order to receive the update for authorization, given that it affects older firmwares as well, or possibly an interaction with the official app.
I have a solution that was rejected by TPLink to be released. However, they are working on adding a new feature to the app that would allow integration to connect to cameras. They expect this to be released by mid-november 2024.
Users reported this problem in numerous issues, this issue will serve for tracking the progress on the fix and group all the conversation under one issue.
Workarounds
If you wish to use this integration, until this issue is resolved, you will need to either:
This post will stay uptodate with the most recent updates below.
2024-04-11:
First report of the issue at #549
2024-04-12:
Second report of the issue at #550 along with more users confirming the issue.
2024-04-13:
This thread has been created.
From my side, I have unblocked one of my camera on the latest firmware to reach the internet, so that hopefully I can get this update soon and work on a fix. I hope TPLink will provide detailed instructions on what has been changed so that I can work on a fix.
2024-04-19:
Added instructions about build number as some cameras have different versioning of firmwares.
I reached out to TP-Link after 7 days for any updates.
2024-04-23:
@reypm found a solution how to workaround this issue without downgrading the firmware:
TPLink is working on providing me with the solution, got a reply today that I need to wait a bit more.
2024-05-08:
I have some very good news and a little bit of concerning news.
Good news:
Now the concerning news:
2024-05-15:
See #551 (comment)
2024-05-18:
See #551 (comment)
2024-05-29:
See #551 (comment)
2024-06-25:
See #551 (comment)
2024-07-03:
See #551 (comment)
2024-07-16:
See #551 (comment)
2024-07-18:
See #551 (comment)
2024-07-20:
See #551 (comment)
2024-07-31:
See #551 (comment)
2024-08-12:
See #551 (comment)
2024-08-19:
See #551 (comment)
2024-09-16:
See #551 (comment)
2024-09-20:
See #551 (comment)
2024-11-12:
See #551 (comment)
2024-12-01:
See #551 (comment)
2024-12-02:
See #551 (comment)
2024-12-13:
Victory for Local Control: TP-Link Enables Third-Party Compatibility
The text was updated successfully, but these errors were encountered: