No it is not, alarm sound is trigered by camera itself.
1 Like
Hellow. For a long time period I am getting the error of âRetrying setup: Noneâ. None of the entites are neither coming. How can I solve this problem ? I have tried deleting and re-installing the integration.
1 Like
Hello. Provide logs and describe what happened when you tried reinstallingâŠ
2022-05-04 03:32:15 ERROR (MainThread) [custom_components.tapo_control] Unable to connect to Tapo: Cameras Control controller: All connection attempts failed
2022-05-04 03:32:15 WARNING (MainThread) [homeassistant.config_entries] Config entry â46.196.117.*â for tapo_control integration not ready yet: None; Retrying in background
2022-05-04 03:32:15 WARNING (MainThread) [homeassistant.config_entries] Config entry '46.196.117.â for tapo_control integration not ready yet: None; Retrying in background
It was workıng fıne before
Please describe what happened when you tried reinstalling
That IP address doesnât look like a local IP address, but a Turksat cable IP address.
What actually are you trying to do? Are you trying to access a camera remotely on a public IP? Thatâs is a really bad idea!
as others pointed out that is definitely not the correct IP address.
you should be pointing at the IP address of your camera(s). you can find this following this guide from Tapo How can I find the IP address of my Tapo camera? | Tapo
Hope that helps
Nothing actually happened.
First I tried to reboot HA. But when it became online, on Tapo integration it stucked. And after a long time the integration came with a statement âNot Loadedâ. Then I deleted the whole integration and tried to reinstall. I entered the external IP(the camera is located elsewhere). It accepted my IP. But on the next screen when I clicked submit button then again I had a long period of wait time and at the end still not loaded.
I canât point my cameras internal IP because itâs elsewhere not int the same network with my HA.
Yes itâs a local IP adress where camera is located. I am trying to let the integration work as it used too. I am trying to access the camera remoteley it is not in the same network with my HA instance. It was working fine before.
You need to be more specific, otherwise I cannot help you. Statements like âNothing happenedâ and âstill not loadedâ do not mean anything.
When you are adding a camera, it asks you for an IP, then for a username and password. It does numerous checks to verify everything works, otherwise it doesnât add the camera.
Remove the camera, start adding it again and note down exactly all the steps you did and tell me exactly any error message you see or any logs you see. Be as specific as possible with everything you see and every action you take.
Make sure to also use the latest version of the integration.
1 Like
Ok look.
Step by step
1 - In the integrations tab says âretrying setupâ error as you can see in the pic.
2 - I have deleted it.
3 - Now I am trying to reinstall from integrations tab.
4- First it asks my ip. Because the camera is located at my work adress I am entering the external IP. I entered my ip and immediately went into the second screen.
5- Now I entered my account details and it accepted and went into the next and final step
6- At he last screen only enable motion sensor and Use stream from Home assistant is checked. And then I hit submit button.
7- Everything is fine.
But the when I checked back my integration screen it says:
Nothing is loaded and I canât use the integration
That shouldnât happen as all the checks seem to have gone through correctly. Please come to Discord where we can debug together more quickly if you have the time.
when did this start ? ⊠just out of the blue, or after some update, long time ago, or some other integration you added ? , or other changes in your or the remote destination ?
before when ? read above
and you are responsible for this other locations network setting, firewall etc ?
What indicates that the Tapo camera integration is responsible for not being able to contact your cam on the remote connection ?
So, that IP address what you masked, is a Public IP address in Turksatâs IP range. If you opened ports on your router to be accessible remotely, then that is a really bad idea. The communication to the camera is not encrypted. It is, but not in that way as you would expect. Thatâs one of the reasons why the integration exists. So anybody can hijack the communication between your HA and the camera or they can even later on log in to your camera. So basically anybody can access it.
But to give you a hint. The IP address provided by most ISPs are not fixed IPs, unless you pay for it. They are so called dynamic IP addresses, so when the location disconnected from the ISPâs network it might or might not get a new IP address. So probably your camera is accessible on a different IP now. Or somebody has closed the port on the router what you have opened for the camera.
But generally donât do this. It is really a bad idea.
See the posts above where someone just asked about it, how a remote site can be accessed with HA to reach the camera there. A few other solutions has been provided.
So we talked on the Discord, all ports were opened and all checks went through.
However, when integration requests onvif event stream, camera never provides it.
It might be something with onvif, maybe it doesnt work well on public ip. Maybe it needs also udp? Maybe its something else on networkâŠ
We did also try official onvif integration but that refused to add camera with unknown error.
Restarting camera did not help.
In any case, after we disabled motion sensor, it works flawlessly. I recommended to use a software solution for motion detection (frigate) or look into network / ask for help with onvif or search for other users trying to use onvif with remote location.
As for the public port forward, as @GSzabados is describing, itâs not a good idea. AFAIK there is no known way how to attack the camera today*, but I would still advise against port forwarding anything outside of network unless its really necessary. Do it only if you know what you are doing and be prepared for a possibility of camera getting attacked and stream leaked in the future.
*From outside of cameras and/or Home Assistant network.
4 Likes
Could sounds like some âONVIF Profileâ cause, or âDiscoveryâ chain brakes/timeouts due to too much messages to Process
I.e ONVIF integration in HA uses Profile S, with H.264 encoding, and i donât think there are support for Motion Detection(in Profile S), as itâs basic video-streaming, seems like only Profile T, supports Motion Detection
Midway in this doc
Hello!
My C200 is on 1.1. 7 
Soni dare update to 1.1.16??
Hello,
yes you can update to 1.1.16.
1 Like
Actually once you put the camera open to the public, then it is just time when someone will hack it.
The authentication happens at the beginning. Only the stok value has to be acquired and then everything is non-encrypted pure HTTP communication.
With the stok value in hand the attacker can create a new user and have access to the feed as well, as @Dpavey described in his article.
Create account to access the RTSP feed
This post request will create an account to login to the RTSP feed of the camera and wipes out the previous settings. Once this method is used, itâs then possible to access the cameraâs feed in oneâs own authenticated manner.
- Username: testing
- Password: testtest
- Access via VLC player: rtsp://testing:testtest@:554/stream1
The ciphertext plays a part in blocking making on-the-fly passwords for the account without the mobile app as it acts as a signature generated for this request by the app but can still be replayed if the request is captured.