Unavailable TapoL510 bulb after updating to new 1.2.13 version and plugp100==2.1.17 #206
Comments
|
I have same problem. |
This could be a regression issue. Have you tried to remove and re-add device? |
I tried, it doesn't work |
|
Here the same problem with L530 Series in two different devices. Before it was perfectly working |
|
I've got the same issue. 3 L510 lights not working with HA 2022.7.2 and 1.2.13. I get invalid authentication when I try to remove and readd them, when I know they added with the same details before the updates |
|
Hello, |
|
Same authentication issue for me on Raspberry Pi 4 and p100 plugs |
|
Exactly same setup and problem as pietrouk above |
|
Hi, In my case changing password (changing capital letters to lower case only) as suggested in #122 make my L510 smart bulb available again. |
|
username and password all lower case and numerals |
|
+1 not working with P100 plug. Already tried to change psw, remove and add again device. Still invalid credentials (no capital letters) |
|
+1 I have done the same and the issue continues. I wish I could figure out the issue? |
|
Hi, same issue all of my p100 sockets are offline following the latest HA release. PW is all lowercase as suggested and I'm still getting authentication failed. Any idea? |
|
I had the same issue with 1.2.13 on HA 2022.7.2, but changing the PSW to all lowercase (+ numbers and symbols) worked for me. My email was already all lowercase. My setup includes a P100 and two L530E lightbulbs. |
|
Hi guys, I've a tapo l510 that's works fine with the latest version. My suggestion is to remove all tapo devices from integration and re-add it. Similarly, I suppose that the "Invalid authentication" is related to a "transient" state of tapo devices, which aren't synchronized properly with tapo cloud. So try to change password and remove and re-add tapo device from tapo app. |
-1501 error is an |
|
Hello, |
|
+1 not working with P100 plug. Already tried to change password, remove and add again device. Only rolling back to version 2022.6.7 helps me 🫤 |
|
+1 P100 isn't authenticating following upgrade. |
|
Can you report a detailed log? |
If you can let me know where to grab it from I will |
|
system > logs. You can search on google how to get home assistant log registry |
|
1st jump to 2022.7.3 Logger: homeassistant.setup Setup failed for custom integration tapo: Requirements for tapo not found: ['plugp100==2.1.14']. then upgraded in HACS restart
Restore my VM snapshot back to 2022.6.7 & v1.2.12, all working again |
|
Setup failed for custom integration tapo: Requirements for tapo not found: ['plugp100==2.1.14']. This suggests that you are installing an old version of tapo integration. I suggest you to follow this steps:
|
|
Hi, this is all I can find in the logs: 2022-07-11 12:05:52 DEBUG (MainThread) [custom_components.tapo.common_setup] Finished fetching tapo data in 18.409 seconds (success: False) |
After these actions, there are no logs, and in the integration displays "Retrying setup:None" |
|
Okay, there is good news, or rather in the logs there is an error. I tried to add the tapo p100 device via YAML and got the following error in the logs 2022-07-11 14:17:16 ERROR (MainThread) [homeassistant.components.switch] Error while setting up tapo platform for switch During handling of the above exception, another exception occurred: Traceback (most recent call last): The above exception was the direct cause of the following exception: Traceback (most recent call last): The above exception was the direct cause of the following exception: Traceback (most recent call last): |
No retry should be shown if you remove It, upgrade, and install, cause removing delete everything. |
I tried to remove the tapo integration from hacs completely and reinstall it, but it had no effect. The logs still show the same error as I showed above, and when adding a device via UI, the error: "Invalid authentication". |
Sorry realised that after I'd posted the reply.... I've just updated to the latest version and I still can't re-add my P100 plugs... |
|
Strange, something is telling lies. Installing the integration fails, but adding the TP100 smart plug manually into configuration.yaml with its ip address and username and password gives me a working Tapo switch on my dashboard. Who knows? |
What? How? Are you using the latest version of tapo integration and HA? |
I tried that now. It does not work and produce the following log: 2022-07-11 17:18:41 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration tapo which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant |
|
There is a lot of confusion ahahaha So please READ THIS:
|
|
latest from log (when attempting manual set up): |
|
yes, I have HW 1.20 and have the auth problem |
As I say, open a new issue with a detailed report |
I have the latest version of tapo installed and every device has a static IP. Okay, let's assume that the whole problem is in the firmware of the Tapo device itself, because it has version 1.20.0. But why then on the previous version of HA (2022.6.7 and version Tapo Control 1.2.12) everything works fine? 🤔 |
There are a lot of variables. First python3.10 and third party dependencies, if you want you can try to use the snippet of code inside plugp100 library by using plugp100 at 2.1.14 version to check if works independently of integration |
|
|
More and more curious I reported a plug working. It did. It doesn't now because I have added another 5 plugs to the yaml file in the same manner and with ascending fixed ip addresses. Now the first plug is greyed out on the dashboard and the other 5 dont appear. I very much appreciate the time and effort put into this by the developer/s and I cant help because I dont understand much more than I've already reported. All I can say is that when this does get resolved l will be buying said developer quite a few coffees. I probably wish I had bought the Ikea triffid stuff. |
|
Its repeatable. Something is wrong with either the addon or my configuration. But that's been working without issue and I was a very early adopter of the 8 Gb pi4. I'll be back in a week to see if there is any progress. In the meantime i will delete the custom comp0nents tapo directory and the yaml item. |
|
I tried removing one of my L510's from the UI integration and adding it to config, where I get this error Raspberry Pi 3B, Home Assistant OS 2022.7.3, Tapo Controller v1.2.13 |
|
In short, I dare say it's because of the move to Python 3.10. Based on its documentation a lot of things have changed, and most likely because of this integration does not work. |
|
It worked for me after removing all tapo lights, removing and reading the TAPO integrations(hacs), changed tapo credentials (no capital letters), readed the lights. 5 Lights L530. |
Can you report firware and hardware version of tapo device by taking a screenshot oftapo app? |
can you attach here your configuration yaml? |
|
On Mon, 11 Jul 2022 at 18:45, petretiandrea ***@***.***> wrote:
More and more curious
I reported a plug working. It did.
It doesn't now because I have added another 5 plugs to the yaml file in
the same manner and with ascending fixed ip addresses.
Now the first plug is greyed out on the dashboard and the other 5 dont
appear.
I very much appreciate the time and effort put into this by the
developer/s and I cant help because I dont understand much more than I've
already reported.
All I can say is that when this does get resolved l will be buying said
developer quite a few coffees.
I probably wish I had bought the Ikea triffid stuff.
can you attach here your configuration yaml?
—
Reply to this email directly, view it on GitHub
<#206 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIDKDS4PCJDMFKFIBH34GBDVTRMUPANCNFSM53DV6TTA>
.
You are receiving this because you commented.Message ID:
***@***.***>
I will tomorrow when I’ve depersonalised it.
But it was switch: host plus ip, username, password.
No capitals anywhere fixed ip latest home assistant latest firmware latest
Tapo integration release.
Hope this helps
Tony
|
|
|
Two Tapo lamps L510 Series, both Hardware 1.0.0, Firmware 1.2.2 Build 20220110 Rel.72329 (latest found and installed by the Tapo app). Password (8-char long) and email contain only lowercase letters and digits. Tapo Intergration stopped working since HA 2022.7. With new 1.2.13 version got the same auth error in UI, same logs for yaml config.
Lamps still work without issues. |
|
Hi, In my case I have problem with changes with file taporequest.py from 2.1.17 - after going back to previous version (containing requestTimeMils and terminalUUID) my light bulbs are correctly working. I'm using example code using plugp100 library: import logging import asyncio logging.basicConfig(level=logging.DEBUG) async def main(): loop = asyncio.get_event_loop() I have created pull request to roll back this changes petretiandrea/plugp100#48 |
|
Thanks for hint, I will release a new version by now. It's an unexpected regression |
|
A new version of integration released, please try it (v1.2.14) |
|
Now it seems to be working correctly (also for Tapo P100). Thank you very much to all contributors! |
|
Now it works with L530, thank you very much for the effort! |
|
works perfect again! aweseom thanks! |
|
@petretiandrea - Same for me, it's now working again, thanks for the update! |
Hi,
After updating to newest version on HA 2022.7.2 integration is now installed correctly, but my light bulbs are unavailable
I tried to run python with debug enabled:
import logging
import asyncio
from plugp100 import TapoApiClient
logging.basicConfig(level=logging.DEBUG)
async def main():
# create generic tapo api
sw = TapoApiClient("ip", "email", "password")
await sw.login()
await sw.on()
await sw.set_brightness(100)
print(await sw.get_state())
loop = asyncio.get_event_loop()
loop.run_until_complete(main())
loop.run_until_complete(asyncio.sleep(0.1))
loop.close()
And I got result:
DEBUG:plugp100.api:Device inner response: {'error_code': -1501}
Traceback (most recent call last):
File "", line 1, in
File "/usr/local/lib/python3.10/asyncio/base_events.py", line 646, in run_until_complete
return future.result()
File "", line 4, in main
File "/usr/local/lib/python3.10/site-packages/plugp100/api.py", line 85, in login
await self._login_request(self.username, self.password)
File "/usr/local/lib/python3.10/site-packages/plugp100/api.py", line 209, in _login_request
self.token = decrypted_inner_response['result']['token']
KeyError: 'result'
Version of the custom_component
1.2.13, HA 2022.7
Configuration
Describe the bug
Can't use light bulbs - before with 2022.6.7 it worked correctly. There was no changes on devices
Debug log
The text was updated successfully, but these errors were encountered: