Hi.
I'm trying to integrate a Tapo door bell camera (battery powered) to Home Assistant and enable live view in the dashboard. As part of this exercise, i see that we need to open the port 554 for RTSP. I have the Speedport Pro Plus router. In menu option "Internet" and "Port activation", I have added a new rule by selecting the device (camera), a description, (no template), TCP - Public 554, Local 554. Saved and restarted the router. But the port still seems to be closed.
I have also marked the IP address of this camera as static under menu "Network" , "Connected devices", - always the same IPv4 address.
When i try to integrate the door bell into home assistant, i get the error "Unable to access the camera stream, verify that you have set up the camera account: Error opening stream (EXIT, Immediate exit requested, rtsp://****:****@192.XXX.X.XXX:554/stream1) ".
I believe this is because of the port not being open.
Could you please guide me on this ?
vor 22 Tagen
****:****@192.XXX.X.XXX:554/stream1)
Hi.
I'm trying to integrate a Tapo door bell camera (battery powered) to Home Assistant and enable live view in the dashboard. As part of this exercise, i see that we need to open the port 554 for RTSP. I have the Speedport Pro Plus router. In menu option "Internet" and "Port activation", I have added a new rule by selecting the device (camera), a description, (no template), TCP - Public 554, Local 554. Saved and restarted the router. But the port still seems to be closed.
I have also marked the IP address of this camera as static under menu "Network" , "Connected devices", - always the same IPv4 address.
When i try to integrate the door bell into home assistant, i get the error "Unable to access the camera stream, verify that you have set up the camera account: Error opening stream (EXIT, Immediate exit requested, rtsp://****:****@192.XXX.X.XXX:554/stream1) ".
I believe this is because of the port not being open.
Could you please guide me on this ?
That 192.xxx address appears to be a private address on the LAN side of the router (it should continue as 192.168.2.xxx). These addresses are only addressable from within the same local area network, i.e behind the same router.
Is your Home Assistant controller on the same LAN? If so, the camera and the controller can talk to each other directly, no opening or forwarding of ports required.
Or is the controller somewhere "on the Internet"? In this case, you need to address the camera by the router's WAN address and port forwarding.
0
vor 22 Tagen
Hi ,
the home assistant control is on a raspberry Pi, connected to the speed port pro plus router directly via LAN cable. And yes you are right. The camera IP address as in the Tapo app continues as 192.168.2 .XXX. I just hid it before pasting here.
In Home Assistant, when I don’t select the LIVE view , I’m able to integrate the camera. But it just shows a small line if motion was detected etc. No view of the camera. If I select the option of LIVE view while integrating, then the above error pops up. So it’s something with the rtsp i guess.
0
6
von
vor 21 Tagen
s where people had it working for the same model
Hi,
Firmware is up to date. But in the TAPO app, I’m unable to find this option to be set as “ always on”. In given path I only see diagnostics and power frequency.
About the last point on battery powered devices not usually supporting RTSP, I’m not sure. I have seen some reddit or github chats where people had it working for the same model. Not sure where this should be fixed.
please tell us the name of the model :)
and did you try this?:
Test the Stream: Use a player like VLC: “Media → Open Network Stream” → enter the RTSP URL to check if it works.
von
vor 18 Tagen
Hi @buenni @lejupp Sorry about the delayed feedback. some distractions from the mechanical part of life.
The point is - this thing now works !!
What have i done ? - After my last message, nothing at all.
I have no clue what made it work all of a sudden. When i check in the tools for port checker - it still shows the port as closed. So, you are right that port opening was not the root cause.
The camera is now in my HA dashboard, with the live view., of course with a minor lag, by a couple of seconds.
Model is D305.
I still have an entry in the router page. it just shows the device, TCP : Public - 554, Local 554.
In the camera app, there is third party compatibility turned on.
And the TAPO : Camera Control integration in Home Assistant, installed through HACS.
I'm not going near these settings now.
Thank you both for your tips and comments. Appreciate it.
Thanks,
Vivek
von
vor 18 Tagen
What have i done ? - After my last message, nothing at all.
Hi @buenni @lejupp Sorry about the delayed feedback. some distractions from the mechanical part of life.
The point is - this thing now works !!
What have i done ? - After my last message, nothing at all.
I have no clue what made it work all of a sudden. When i check in the tools for port checker - it still shows the port as closed. So, you are right that port opening was not the root cause.
The camera is now in my HA dashboard, with the live view., of course with a minor lag, by a couple of seconds.
Model is D305.
I still have an entry in the router page. it just shows the device, TCP : Public - 554, Local 554.
In the camera app, there is third party compatibility turned on.
And the TAPO : Camera Control integration in Home Assistant, installed through HACS.
I'm not going near these settings now.
Thank you both for your tips and comments. Appreciate it.
Thanks,
Vivek
Best not to ask too many questions and just be happy that it works ;-)
Uneingeloggter Nutzer
von
vor 22 Tagen
Practical Tips for Using RTSP with Tapo Doorbells
Enable Always-On Mode: In the Tapo app, go to your doorbell → Advanced Settings → Always-On → enable it. This is a requirement for RTSP on the supported doorbells.
Test the Stream: Use a player like VLC: “Media → Open Network Stream” → enter the RTSP URL to check if it works.
Check Firmware: Make sure your doorbell’s firmware is up-to-date. For example, for the D235, firmware version 1.1.14 (Build 240929) officially added support for RTSP in Always-On mode. TP-Link Community
Be Aware of Power Constraints: Since RTSP requires “always-on,” battery-only operation isn’t suitable for this use case — you’ll likely need to wire the doorbell.
0
Uneingeloggter Nutzer
von