Tapo D230 Doorbell: WebRTC Stream Fails - Only One Stream Entity Exposed #889
Description
I'm trying to add my Tapo D230 Doorbell to Home Assistant using the "Tapo: Cameras Control" integration (HACS). The integration successfully detects the doorbell and creates a single camera entity. However, when I try to use this entity with the WebRTC card on my dashboard, the stream fails to load, showing an mse: stream not found error.
I have performed several troubleshooting steps and have a strong suspicion about the root cause.
What I'm trying to do:
Integrate my Tapo D230 doorbell into Home Assistant to view a live, low-latency video stream via WebRTC.
Steps to Reproduce:
Installed and configured the "Tapo: Cameras Control" integration via HACS.
Added the Tapo D230 doorbell using its local IP address and a dedicated camera account (with RTSP enabled in the Tapo app).
The integration successfully added the doorbell and created a camera entity: camera.doorbell_hd_stream_direct.
Created a WebRTC card in the Home Assistant dashboard with the configuration:
YAML
type: custom:webrtc-camera
entity: camera.doorbell_hd_stream_direct
Expected Behavior:
The live video stream from the doorbell should be displayed on the dashboard with low latency.
Actual Behavior:
The video player shows a "mse: stream not found" error, and the stream does not load.
Additional Information & Analysis:
My other Tapo cameras (e.g., C225) are working correctly with the same WebRTC card configuration.
I have checked the stream entities in "Developer Tools > States". While my other cameras expose multiple entities like camera.c225_hd_stream and camera.c225_sub_stream, the D230 doorbell only exposes a single entity: camera.doorbell_hd_stream_direct.
This suggests that the integration is not correctly exposing the necessary RTSP streams (like a main_stream or sub_stream) that the WebRTC component relies on.
Request:
Could you please confirm if this is a known issue for the Tapo D230 doorbell? Is there a workaround to enable a compatible WebRTC stream, or will this require an update to the integration itself? Any guidance would be greatly appreciated.