It no longer connects to rtsp stream if disabled.
Hello everyone! Is it possible to control the camera using webhook triggers? Could someone share an example and how the link looks like for enabling or disabling the private mode on the Tapo C225 camera? Thank you!
Its very far to see me blinking, its catching the person detection, which would be very helpful. But I guess you answered my question its not a feature (hopefully yet 
)
Hi
I never managed to get the issue resolved, but I did find a potential pointer to what the issue was.
In the TAPO camera setup guide it tells how you setup a user for RTSP streaming. On the TAPO website I found that TAPO cameras can only accept one connection to the RTSP stream. So, with frigate already configured to use that stream, this component couldn’t connect as a second user for the stream. I disabled frigate and this component connected, but frigate couldn’t for the single user issue. That’s the point where I gave up. Frigate is more important to me.
Maybe other users can connect multiple users? I certainly couldn’t.
This is explained in more detail in FAQ.
You can (should) use webrtc along with this integration and then pass the go2rtc stream links to frigate (or anything else) for near instantaneous streams, working audio, and unlimited restreams.
1 Like
Hi all!
I am getting an error while trying to configure the integration:
“Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble”
I am using Core 2024.4.0 and Frontend 20240403.1; Inside a docker container through CasaOS.
I posted the logs here the other day.
Any idea what to look into to fix this?
In the meantime I got them working through Frigate but being able to control them (PTZ) would be appreciated.
Thanks!
Hello, first of all thank you for providing Tapo: Cameras Control, I’m so glad I can use this.
I have two Tapo TC60 in use and until last night they worked perfectly with TCC. Last night one camera suddenly lost the motion sensors, the other kept working fine. This morning the second camera lost them as well.
I checked the FAQ and tried all the things there, please find what I did in line:
- Motion sensor is added only after a motion is detected for the first time. → Did this every time I changed or tried something
- Make sure the camera has motion detection turned on → It is on.
- Make sure the camera has privacy mode turned off → It is off.
- Make sure the camera can see you and your movement → Stream works perfectly, via HA and via VLC Player.
- If you have webhooks enabled, and your Home Assistant internal URL is reachable on HTTP, make sure camera can reach it. → I do not have webhooks enabled.
- Make sure you have correct IP set for Home Assistant. Turn on Advanced Mode under
/profile. Go to/config/networkand underNetwork Adapterverify correct IP is shown for the device. DO NOT USE HTTPS. → IP is correct - Certain camera firmwares have pullpoint broken, with only webhooks working. If you are not able to run webhooks because of above (https, or vlan setup), binary sensor will never show up. → Should not apply since it already worked perfectly for some time.
- Try walking in front of the camera → Did this every time I changed something.
- If above didn’t work, restart the camera and try again → Restarted the camera multiple times, also reset it and integrated it into HA again.
- binary sensor is not disabled via entity, check .storage/core.entity_registry for disabled entities, look for “disabled_by”: “user” on platform “tapo_control”. If it is, remove the whole entity or change to “disabled_by”: null, and restart HASS. → grepped it, there is not a single entry in that file where disabled_by is not null.
- binary sensor is enabled in tapo integration options → it’s enabled
- onvif port 2020 on camera is opened → It’s open according to a nmap scan
I also removed the camera, reset it and reintegrated it, but to no avail.
I think this might be due to an automatic firmware update which is not yet compatible to Tapo: Cameras Control and that’s also why I am posting here, anyone else got this problem? The FW is 1.3.11 Build 231121 Rel.39414n(4555)
If not, what can I do? After all it worked perfectly in quite some automations and then just stopped working. I did not change any configuration in Home Assistant that day.
Thanks and best regards
And did you checked in Setting/Devices# entities, Whether the “Entity” in fact was still there ?
Could it be that it was in the UI you saw it was “Unavailable” ?
Please check this above
Yes , however still not figured out whether it’s a “problem” nor what “causes” it
I Have experienced ( Looking/Checking in the UI Integration Page ) for both Motion and Noise, they showed as unavailable ( at random time, not the same time for both thou )
How ever the “Entities was infact there” ( Look under entities ! )
Few hours later or next day, they were there “Clear” again in the UI, i didn’t do anything, beside i might have “crossed the line/walking by” , most important, i didn’t start to reset, change settings etc. frenetically. ( I might have restarted after latest OS, Core update ! )
And as You don’t provide any logs, and btw don’t tell whether the mentioned FW is the same on both, i wouldn’t/can’t come to the conclusion that it is a FW issue
So i suggest you 1. Make sure you are on latest HA Versions, 2. Set up the Cam and make sure the motion/noice Entity is there !, after enabled/and Motion detected ( Check in Settings#Device And in #Entities ! )
Then leave it alone !, If you keep removing, installing, changing frenetic , you’ll never come to a "structured conclusion "
And if it shows “Unavailable” again, first thing, try to trigger the motion(walking by), then check the LOGS( LogBook & CORE -Log ), First to verify whether it’s been triggered or have Errors
EDIT: Btw what is TCC ? , And Why not enable WebHook ?
Thanks for your answer!
The firmware is the same on both devices. Triggering the motion sensor multiple times was in fact the first thing I tried before doing anything else, the camera is used for providing a night light (with a LED strip) for my children when they leave their rooms at night and I noticed that something is wrong since the automation would not work anymore. So this was tried first and it was given about 12h to spontaneously fix itself.
I’ll give it some time and another HA reboot and report back tomorrow. My HA is the latest available container from the Unraid docker “store”.
Edit: TCC was me being lazy and not wanting to write Tapo: Cameras Control
Why should I enable webhook? I didn’t check it out, because everything worked the way it was.
Firstly, thank you for following FAQ and providing detailed steps you have taken!
Certain camera firmwares have pullpoint broken, with only webhooks working. If you are not able to run webhooks because of above (https, or vlan setup), binary sensor will never show up. → Should not apply since it already worked perfectly for some time.
Firmware was updated, therefore it applies and if it worked before is irrelevant.
You need to ensure webhooks connection works or downgrade firmware.
Because it usually pays off, if a system already runs, to not enable as much additional protocols/features/addons as possible.
Thanks, I understood that wrong. Due to your post I checked the FAQ and found the explanation on webhooks and this is of course a good reason to enable communication with it. I’ll try to get this to work and then disable automatic firmware updates so I do not lose motion detection while I am on a two week holidays. 
1 Like
Right, i have also disabled autoupdates on all my Devices, Also in the respective phone APPS
PSA: Firmware 1.3.9 and newer might cause integration not to work
There has been numerous reports of integration stopping to work on firmwares 1.3.9 and newer. If you wish to continue using this integration, until this issue is resolved, you will need to either:
- Block internet access of camera and stop using the app temporarily if you are using firmware 1.3.9 and newer (not confirmed working)
- Use older firmware than 1.3.9 and factory reset camera (SHOULD work)
Learn more and discuss at ❗❗❗PSA: Firmware 1.3.9 and newer might cause integration not to work · Issue #551 · JurajNyiri/HomeAssistant-Tapo-Control · GitHub .
1 Like
hmmm, i have 4 C200 and 1 C310 on 1.3.9, working and motion, noise, and recording working
Latest HAOS
Running HTTP on HA, no external access
Cams are not blocked from internet, everything ok in the APP also
So are you saying i should not install 5.4.17PSA
Im on 5.4.17
PS: Works in HA-AP on Android 9 also
In your case you should stop using the official app and block camera from internet otherwise it might stop working. Nothing to do with integration the new ‘version’ is not really a new version just a way how to contact all users of the integration about this.
1 Like
ok, but i blocked autoupdates on my cams and tapo app since long (1.3.6), so only update manually
Just reinstalled C310 2 days ago, after moving it, from my test-unit, so i did add it to the tapo-app with no issues, hmmm ( Getting noise, motion notifications etc also )
Ok, Thanks alot for the Warnings, however im honestly sometimes a huge risktaker, so i’ll wait for symptoms 
That does not matter. There are users on 1.3.9 affected. To be completely safe and to prevent this from happening you will need to block the internet completely and stop using the official app as it might push the update anyways as users reported this.
1 Like
Ok, i’ll obey You , … beside 1 cam … just to see what happens 
Thanks again
PS: After reading on Tapo community/support online, i took the last one offline aswell 
Seems like quite some people got their C200 bricked, Tapo’s Answer !
"
@Carlos_Graniel following the troubleshooting here: What to do if my Tapo Camera gets bricked after a firmware update? - Smart Home Community, if the tips do not work, you can buy a new camera.
"
@Tangindian it seems the camera is faulty, you may buy a new one if it’s not under warranty…
"
2 weeks ago and last week, both C200 & C310 bricked at autoupdate
And this were not the only ones !
Im shocked " GO BUY A NEW " Seems like an absurd standard answer, is this a late aprils joke from Tapo’s side ?
FYI, all 7 of my cameras are now running 1.3.11 with no issues at all 
1 Like