[APP] Tapo - Smart devices for smart living

Thank you for your response. The function was on and turning it off and on again unfortunately did not help.
I tried:

I think only the developer can fix it. Local API is not needed (I have it disabled and my Tapo devices work fine).

There is a new version on test (v2.1.7):

Energy monitoring:

  • Fixed energy monitoring for local devices
  • Removed the opt-in setting - energy monitoring is now always enabled again
  • Added cumulative meter (meter_power) for Homey Energy integration
  • Kept daily meter (meter_power_today) for users who want to see today’s usage

Rate limiting:

  • The rate limit issue appears to be resolved on TP-Link’s side
  • Polling interval is now 60 seconds

Stability improvements:

  • Devices now retry indefinitely when unreachable (instead of giving up or falling back to cloud)
  • Camera ONVIF connections also retry indefinitely (was limited to 5 attempts)
  • Added jitter to reconnection attempts to prevent CPU spikes

Hi, is it possible to add snapshot support for the cameras as well for use on Homey Pro 2019?

Please update to v2.1.9. The previous version (v2.1.8) results in to many requests to the API unfortunately.

My two led strips aint working anymore, might be due to latest update. Cant remember it they worked yesterday or not, but i think they did.

Same here. And the repair function just generates an error message.

The previous release causes this issue and will be resolved when the users that are overflowing the API are installing v1.2.9.

I do have 2.1.9, yet still im affekter by the problem. Also im not using local API of its of any help. :grinning_face:

Since update 2.1.9 I’m having issues with my smart plugs. In the Homey app it looks like they are switching on and off, but the physical plug doesn’t do anything. No error messages, but it just won’t trigger.

The plugs are still working fine in the official Tapo app. Anyone else having this issue or knows a fix?

I am a new user of the HP26 and try to connect the Tapo app. Have been reading as much as possible about this matter, but still can’t add my Tapo P100/P110 plugs. Too many tries or just a black screen. Compatibility is on, and even the first try 24 hours later gives too many tries..

Does anyone know the solution?

Where do you get the black screen? Does it appear when pairing the device, or on the Tapo authentication page?

Hey, I also have a C200 (and a C500) installed with ONVIF. Do you get Notifications? I do not get any. The Tapo App supports only motion alarms but I would need the baby crying alarm.

That happens when pairing a device.

I can’t adopt Tapo devices, I get error 10104

Hi,

Responding to myself.
I wasn’t able to get any progress with these issues until now.
Finally I seem to have figured it out.
Originally, I set up the all cameras with the same credentials for the camera account thinking it wouldn’t matter and it would be easier to remember just one set of username/password.
For lack of other ideas I tried changing the credentials the other day so that all cameras have unique usernames and that seems to have fixed the problem.
I have not read anywhere that this is required but, for me at least, it seems to have resolved the issues with my cameras.

The problem seems to have been resolved; today the Tapo v2.1.12 update was released, and with it I was able to access my account and add the S505 device.

Since the update of today the tapo p115’s do not give powerreadings anymore :frowning: @Koktail

Due to growing users and more traffic the Tapo API all users got rate limited most of the time. This is because Tapo does this on integration leven. That means that every user that does to many requests trips the limit.

Yesterday I released a new version that will exponential backoff when this happens. And reduced the amount of requests in total. Unfortunately the energy usage is one of that because that did take -+8% of de budget.

:police_car_light: For all users that are still on v2.1.8 or lower, please upgrade to v2.1.12 because these older versions are going to be deprecated soon.