-
-
Notifications
You must be signed in to change notification settings - Fork 223
Cannot add Tapo Plug P110 to Home Assistant 2024.2.3 - Error in debug mode #797
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
Comments
Hi, Your error messages are definitely related, the device is reporting that it doesn't support that command which is used to query the energy meter information. Would you mind trying if it works with the current git master branch? I also have a P110 that I have been using for development, and it is working just fine. You could also try to run the dump_devinfo devtools script ( Was yours marketed with energy monitoring, and is it also working? Do you have a different hw or sw version reported by the cli tool? |
Hi there.
Running the same command under current git master branch (installed with poetry), I get no error anymore, but instead (redacted personal information):
Here is mine: There are definitely quite some differences, some eventually caused by the fw version in each? If needed, I have a spare (another) P110, which I can upgrade to latest fw version (1.3.0), to check if it works better.
Yes, definitely supporting energy monitoring, and data is showing in Tapo app (even though 0). Hardware and Software versions in Tapo app fit exactly what is reported (above) by cli Please let me know if you need anything else. |
I think there are a couple of issues here:
|
Thanks for the fixture file, @pplucky, that's really helpful, and we should add it to our fixture collection! You could definitely try to perform a firmware update, that should fix it for you, but we should also fix this in the library.
I think |
Beats me, also. The fact is that when using kasa from the latest master (installed via poetry after git clone), I managed to get that output.
I plugged something that would actually consume energy and here is output from Tapo app: and the cli output:
or when calling emeter command:
Btw, is it normal that the Current and Voltage are both None? This also seems to happen for the other P110 plug I have (which is in 1.1.5 and had no issues in being added to HA). In HA, no current and voltage sensors exist. Now that I notice, I also didn't have these in the previous Tapo custom component, but just out of curiosity, I had 2 additional sensors: ![]() These were probably obtained from device info properties overheated and rssi. Please let me know if there's anything else you need/want me to check for this 1.0.7 plug before I upgrade its firmware ;-). |
Yes, the device doesn't report this information. We are moving to a more dynamic approach for presenting the available information (see below) so this can be ignored for now.
Yes they are. We are moving towards supporting more devices and more features directly out-of-the-box but it involves lots of changes, targeting currently homeassistant 2024.4. |
Uh oh!
There was an error while loading. Please reload this page.
Hello.
Looking at HA documentation, I supposed Tapo Plug P110 should be supported by TP-Link integration using authentication.
Still then, no matter how much I tried, I always get error message 'Failed to connect' after entering user + password (which I already checked to be working properly while logging directly into Tapo Cloud website or Tapo app).
Activating the HA logger level DEBUG, I got the following message which seems related:
[kasa.smartprotocol] Unable to query the device: 172.16.23.73, not retrying: Error querying device: 172.16.23.73: UNKNOWN_METHOD_ERROR(-1002) for method: get_current_power
Running kasa directly in HA docker:
kasa --host 172.16.23.73 --device-family SMART.TAPOPLUG --encrypt-type AES --username my-email@email.com --password my password
I get the following output:
It is worth mentioning that the plug is currently with firmware version 1.0.7 (update to 1.3.0 is currently proposed via Tapo app), it works properly via Tapo app and it also works in another HA instance using a custom component.
For all this, it seems to me that this may be an issue in the integration.
Can anyone help further? If you need any further logs or additional info, please let me know.
Thanks in advance.
The text was updated successfully, but these errors were encountered: