Hi everybody, just wanted to give something back, as this thread helped me a lot.
Something I don’t remember reading anywhere but experienced: The Wifi connection can cause the motion detection entity to become “stuck” in state “detected” or disappear randomly. Other entities might become un/available randomly too.
In particular my use of a Wifi MLO Network caused this with my Tapo C110.
I experienced similar behaviour with other devices. Just something to keep in mind.
Fixed it by using a separate 2,4GHz wifi net.
.- Simon
Hi,
i have two C460 camera with solar pannel and 2 c220 cameras.
Media sync is enabled, but it only works on the c220 cameras.
The media folder for the c460 remains empty.
Any idea how i van fix that?
Grts
Hi all,
I have a very strange issue. I have two C310 cameras bought as part of a twin pack. As far as I can tell they have identical settings in the app, but only one of the cameras is exposing a Binary Sensor for Person Detection in the integration.
Help please!
Hey,
Not sure if you found the answer yet…
It will create the binary sensor after the first detection, and after restart of HA, the sensor will be unavailable until the first detection post restart.
Hi and thanks for this integration. It has solved many of my issues and problems with the standard camera config in HA.
A question: is there a best practice to avoid configuring specific IP addresses for each camera, so that DHCP changes won’t cause headaches. The cameras don’t seem to announce a .local DNS name, so I guess I’m left with having to set static address assignments in my router.
Or am I missing something that makes life easier?
Thanks again
Rather that allocating a static address on camera, I’ve reserved DHCP addressed for the cameras on my DHCP server, so they get allocated the same address every time.
NO, if you avoid it, the change that it will change IP is heigher, And it WILL give you a headaches , Your Tapo-App and HA don’t work the same way
First you name your Cam in your Tapo-APP, Then you name it( The Same Name ) in your Router(Both when you add your Cam) ( And in the DHCP-Scope, you manual add/map i.e the IP it got to the MAC & Name
Then you either wait, or restart your HA, and then in HA, when you see the IP-number, of your cam, You ADD-IT and Name it Also the Same there.
Consistency, in all points/aspects of the Network is the Most “Best Practice”
can you share how you accomplished this? I tried adding -vf "transpose=2" to the extra arguments for ffmpeg (restart required) field and restarted, but it had no effect.
Great integration! But could it be that different hardware versions of the same type provide different sensors?
In my case, I initially had two C200s that worked perfectly with this integration. These have hardware version 3.0 and firmware 1.4.5. I have now purchased another C200 and integrated it without any problems. However, this one has hardware version 5.0 and firmware 1.3.1.
It does not provide a motion sensor. No “binary_sensor.tapo_c200_cell_motion_detection”, no “binary_sensor.tapo_c200_motion_alarm”.
It is also strange that the motion sensors sometimes appear on the C200 V5, but are deactivated with the note ‘Deactivated by device.’
Is this normal or am I overlooking something?
Did you check the FAQ in the initial post? Motion sensors only come up after triggered.
At least the sensor triggers when there is movement and records a video.
For both entities, it says “disabled_by”:‘device’. Can I change this to “null,” or does this mean that the camera does not provide these entities?
sorry. I do not have that scenario, so can´t answer that. I don´t have the same camera as you… if you can try, just try and see
I need help needed with testing new integration version, if you have Doorbell, Chimes, or devices accessible via a Hub.
Please download new version https://github.com/JurajNyiri/HomeAssistant-Tapo-Control/archive/refs/heads/pytapo_3_4_0.zip and install manually following GitHub - JurajNyiri/HomeAssistant-Tapo-Control at pytapo_3_4_0
If you see integration version 7.0.14 you have installed it correctly.
This version switches transport / encryption layer from inhouse to python-kasa so that there is 1 code for TPLink encryptions going forwards, resulting in faster reactions to any new firmware changes.
Please report success / failures here or in Entities Unavailable After 3 Minutes, HTTP 401 Error C100 · Issue #1163 · JurajNyiri/HomeAssistant-Tapo-Control · GitHub .
I need at least:
1 report of it working on a doorbell and chime
1 report of it working on any device connected through a hub
Then I can release it as a new stable version.
Thank you all!
Dumb question but what is the best way to use this integration and restream the HD feed via go2rtc? Go2rtc supports several native Home Assistant cameras but not the Tapo ones. Do I have to manually set them up via Onvif or RTSP and if so, doesn’t this defeat the purpose of half of this integration? If I double up camera integrations pointing to the same Tapo camera, do I double up on resources consumed?
Since the last update of HA, I keep getting the following error constantly: Failed to sync time for … What can I do? Thanks in advance."
There are Issues on GitHub for this with workarounds/updates…seems to be a TPLink prob rather than this Integration…best have a look on GitHub for the detail
Just installed the latest update and it seemingly fried my sensors, creating duplicates across the board for all my cameras. Anyone else having issues?
No duplicates here after updating to latest.
After upgrade to HA 2026.02, integration was not working for 2 C200 cameras. They were working fine before until upgrade.
After several restarts and reinstallation, now I’m not able to add any Tapo device, because integration takes always this issue “500 Internal Server Error Server got itself in trouble”
And this is what I take from log
homeassistant.requirements.RequirementsNotFound: Requirements for tapo_control not found: [‘pytapo==3.4.7’]
Someone has same issue or can help me about how to proceed?
Have you updated to latest version of this integration ?
