Help Needed: How to set up Frigate card w/ tapo camera 2-way audio? #8963
-
|
SOLVED by igiannakas: For 2 way audio to work, you must:
Config: Massive thanks to everyone who helped and specially igiannakas, dimatx Original Issue Starts here: Cross-posted in Reddit Hello! Does anyone have experience setting up 2way audio with tapo camera? My frigate local ip is 192.168.1.150:49182 I've added the following in the frigate config and I can see the live feed using Webrtc I am not sure if the below necessary. Since it should be re-encoded the stream to H264 w/ aac audio? and I dont need to re-encode, the tapo is h.264, but I am not sure about the audio, but again, I can get the audio via Figate card live: webrtc so I am okay without it? and is the necessary also? in the frigate card doc and for port 49185 that should be correct, this is my port mapping, I also added Port Forwarding in the router And my Frigate card config Any help appreciated |
Beta Was this translation helpful? Give feedback.
Replies: 19 comments 63 replies
-
|
no clue if this is even a problem, but you are missing the '1' at the end of the stream URL: "path: rtsp://my_user:[email protected]:554/stream # <----- The stream you want to use for record" should be: "path: rtsp://my_user:[email protected]:554/stream1 # <----- The stream you want to use for record" |
Beta Was this translation helpful? Give feedback.
-
|
thanks! I but turns out its just some copy and paste mistake when I masking my password |
Beta Was this translation helpful? Give feedback.
-
|
@hohaha045 Did you make it work? |
Beta Was this translation helpful? Give feedback.
-
|
Nope, but will re-visit this issue when I am a bit more free |
Beta Was this translation helpful? Give feedback.
-
|
Was anyone able to make it work? I am still unable to make it work:
Would be great if anyone that made it work can share. I have Tapo C110 camera Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
OK. Figured this out Just in case anyone has the same problem. Some people say you need to encrypt the password with MD5, some say SHA256... none of it worked for me. Putting plain password (password that you use to login to your mobile app Tapo application) works. Here is my config: Obviously this works only on LAN. No idea how to make it work from remote... |
Beta Was this translation helpful? Give feedback.
-
|
@groyee Can you please share the full config for that camera? Which ffmpeg profile/parameters did you have to use, if any? |
Beta Was this translation helpful? Give feedback.
-
|
Sure. If you use WebRTC, I am not even sure if you need ffmpeg transcoding here since the audio in this camera is PCM but to be on the safe side I did add it. That's pretty much it.... Then I have my frigate card: 
As long as you use https (not http) or you disabled this restriction in Chrome and as long as you are on the same network (or at least not behind symmetric nat) it should work |
Beta Was this translation helpful? Give feedback.
-
|
Are you using the TP-link Cloud password ? or the one on VLC "rtsp:username:[email protected](tapo_camera_ip):554/stream1" ?
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks @groyee. And what benefit does having both the rtsp:// and the tapo:// URI for your tapo1? |
Beta Was this translation helpful? Give feedback.
-
|
Honestly, I am not sure. I believe it will work without it as well |
Beta Was this translation helpful? Give feedback.
-
|
The one I use in the Tapo mobile app. Open the Tapo app on your mobile-> View account (the password you used there, that's the password) |
Beta Was this translation helpful? Give feedback.
-
|
Ahh still not work for me, maybe only work on LAN as you said, but what's the point of 2-way if only work on LAN lol |
Beta Was this translation helpful? Give feedback.
-
|
Well... It works on WAN as well if you are not behind symmetric NAT. https://tomchen.github.io/symmetric-nat-test/ If you try to access it from a mobile (3G, 4G, 5G) then most likely you are behind symmetric NAT and it won't work. But many times you are on a WIFI at work or other places and it can be a normal NAT and then it should work |
Beta Was this translation helpful? Give feedback.
-
|
Huh, interesting, I am using the same network via Wifi, but my HA is under a cloudflare domain name |
Beta Was this translation helpful? Give feedback.
-
|
@groyee have you upgraded to 0.14 yet? I tried your solution for my Tapo C120s. No two-way communications come up even though go2rtc probe sees the camera as capable. My dahua cameras have the mic capability within Frigate's live view. The Tapo cameras do not. |
Beta Was this translation helpful? Give feedback.
-
|
I figured this out recently and still looking for reliable solution. Just install and start go2rtc service in Home Assistant for basic troubleshooting. That is quicker to troubleshoot. Basically Tapo newer firmware is blocking things. You may follow JurajNyiri/HomeAssistant-Tapo-Control#625 for more info. I downgraded one of my C220 firmware and it started working. but only problem I noticed after that, is you can not go back to latest firmware anymore. (May be I don't know how to restore to Latest firmware) and I have still not figured out why Frigate video recorded without audio. I tried aac/pc/opus one at a time but no success however, 2-Way Audio worked perfectly. In Next: Click on Before Firmware flash: After Firmware Flash: |
Beta Was this translation helpful? Give feedback.
-
|
Anybody has done this 2-Way-Audio with frigate 0.14 & Tapo C210? |
Beta Was this translation helpful? Give feedback.
-
|
Try follow groyee reply above, and you should read this if you haven't already. But mine is not working lol But will re-try everything tomorrow |
Beta Was this translation helpful? Give feedback.
-
|
Same old news, didnt work |
Beta Was this translation helpful? Give feedback.
-
|
EDIT: Updated with latest instructions (8 March '25) However you must have webrtc configured and functioning. If webrtc is not working the two way audio won’t function. In addition, you must be accessing the frigate front end via SSL. I'm using nginx reverse proxy in front of mine. In some cases you need to enable Third-Party Compatibility" in the Tapo Lab section (Me > Tapo Lab > Third-Party Compatibility and reboot cameras. But it’s a hit or miss if that is needed always. In my case it wasn’t necessary. Lastly 've had good luck with using the latest go2rtc binary from the go2rtc repo instead of the bundled one with frigate. I think it's more up to date but that may just be me. Old reply: I’m using a C110 with the latest firmware and it worked. Settings as below: |
Beta Was this translation helpful? Give feedback.
-
Do you mind show your full config? and the frigate card setting? I am trying the config you share, and something is happening, my c210 speaker/mic volume becomes unavailable. |
Beta Was this translation helpful? Give feedback.
-
Oh WOW, never mind. ITS WORKING!! I just change my tapo cloud account to something simpler- no symbol. And it freaking worked. Thank you so much! |
Beta Was this translation helpful? Give feedback.
-
|
Awesome! Glad it worked out:) even if it was 9 months later 😀 |
Beta Was this translation helpful? Give feedback.
-
|
It also works without the ffmpeg statement - however I noticed lower quality playback when I removed it so I left it in. It may be a bug with my system though so give it a try if you want |
Beta Was this translation helpful? Give feedback.
-
|
Following up on this topic - In v0.15 I now need to set input_args: preset-rtsp-generic in the FFMPEG settings for it to work. For some reason it's not functioning with va-api. Also it appears like the video freezes when using two way audio. |
Beta Was this translation helpful? Give feedback.
-
|
Hashed it myself... Used the command here: https://github.com/AlexxIT/go2rtc?tab=readme-ov-file#source-tapo |
Beta Was this translation helpful? Give feedback.
-
|
I have the same camera: I have Frigate running in a docker on Unraid. I can see the video feed on HA and Frigate itself. ONVIF seems to work since I can control the camera's PT and set presets. However, adding/removing the tapo:// line seems to have no effect whatsoever. I've trimmed my config down to basically what you have posted above, but I still don't see a microphone for two-way talk anywhere. I can hear sound, but can't talk. Are you able to two-way talk through Frigate or would the mic only show up on HA? What does it look like? I used https://www.miraclesalad.com/webtools/md5.php to hash my password. Also tried with just tapo://@. |
Beta Was this translation helpful? Give feedback.
-
|
I am using SHA256, as the docs say that some newer cameras require that. To validate your hash, "test" (without quotes) should yield: 9F86D081884C7D659A2FEAA0C55AD015A3BF4F1B2B0B822CD15D6C15B0F00A08 as SHA256 Also, make sure the hash is uppercase. The site you linked to does not do that be default, but there is a checkbox to make it uppercase. If working, you will see the following top right in the camera feed in the Frigate web UI.
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks for that. I feel like I'm going crazy... I was using MD5 hash. After replacing it with a SHA256 hash, I saw the mic button and tested it. That was ONCE. It's gone now I can't get it to show up again. Any ideas as to why that would be? I see this in the logs: "media=audio, recvonly" wonder why recvonly.... I confirmed it is authenticating by removing RTSP auth so my configu now looks like: |
Beta Was this translation helpful? Give feedback.
-
|
Solved my issue. SSL/HTTPS is necessary for 2way audio! |
Beta Was this translation helpful? Give feedback.
-
|
Sadly, my 4 Tapo C120s were working fine and abruptly stopped without any firmware updates. I've re-flashed/reset them time and again, no go. Even went so far as to upgrade one to the latest firmware. Hash and MD5 won't work. Oh well. Was a fun ride while it lasted. |
Beta Was this translation helpful? Give feedback.
-
|
@dimatx Great question. So, two-way talk stopped at some point. Was 100% great on Frigate 0.14. I upgrade to 0.15 on stable release, but I didn't check those cameras until days later. I tried all the old steps of flashing old firmware and factory resetting, I tried MD5 and SHA, etc., and the tapo:// still fails. Seems to be camera API, though.
This is tested using the following script: |
Beta Was this translation helpful? Give feedback.
-
|
Do you have "Third-Party Compatibility" enabled in the Tapo Lab section (Me > Tapo Lab > Third-Party Compatibility) of the Tapo mobile app? |
Beta Was this translation helpful? Give feedback.
-
|
@dimatx funny enough, no. I don't know if I ever did that -or- if it was lost. Any rate, toggled it on. Still a no-go. |
Beta Was this translation helpful? Give feedback.
-
|
Ok, and just to be sure, the username and password you are using is the 'Camera account' buried deep in the settings of a given camera in the App? If so, I'm out of ideas, but if you just enabled that Third-party toggle, maybe reboot the cameras. |
Beta Was this translation helpful? Give feedback.
-
|
@dimatx I bleeping love you. I just rebooted them all and, magic, the python pulls the data and mics are working again. I have no clue what the heck went wrong. It's all been living on its own for months untouched. LOL |
Beta Was this translation helpful? Give feedback.
-
|
Guys, What's the latest config for the issue? I personally don't own the tapo anymore, but I would like the mark that as the answer, so someone could just follow in the future. |
Beta Was this translation helpful? Give feedback.
-
|
This config here works in my case: However you must have webrtc configured and functioning. If webrtc is not working the two way audio won’t function. In addition, you must be accessing the frigate front end via SSL. I'm using nginx reverse proxy in front of mine. In some cases you need to enable Third-Party Compatibility" in the Tapo Lab section (Me > Tapo Lab > Third-Party Compatibility and reboot cameras. But it’s a hit or miss if that is needed always. In my case it wasn’t necessary. Lastly 've had good luck with using the latest go2rtc binary from the go2rtc repo instead of the bundled one with frigate. I think it's more up to date but that may just be me. @hohaha045 I've updated the solution post with the above. |
Beta Was this translation helpful? Give feedback.
-
|
This one I posted the other day was confirmed working: #8963 (reply in thread) |
Beta Was this translation helpful? Give feedback.
-
|
I updated most of the details on the top, again, thank you. |
Beta Was this translation helpful? Give feedback.
-
|
Hello everyone, I don't understand what I did wrong. I have a TAPO C510W and I can't use it with go2rtc in frigate. My configuration :
My frigate.yaml is : But, if I use this frigate.yaml, the camera is visible on frigate : I take any suggestion, because I blocked with go2rtc. |
Beta Was this translation helpful? Give feedback.
-
|
You have a spelling mistake here: I am assuming it should be Also there is inconsistencies in your ip address: You're using both a .142 and .144 IP |
Beta Was this translation helpful? Give feedback.
-
Thanks, I did some cleaning for the post, because I have 4 cameras. And now, I still have the same errors, but I see that on frigate interface : |
Beta Was this translation helpful? Give feedback.
-
|
Your path is wrong: Should be: |
Beta Was this translation helpful? Give feedback.
-
THANK YOU ! It's working ! |
Beta Was this translation helpful? Give feedback.
-
|
Your welcome :) |
Beta Was this translation helpful? Give feedback.
-
|
Hi guys. If anybody has trouble with authentication with cloud password, here are some tips that I got my Tapo working with 2-way audio.
For me:
package main
import (
"fmt"
"github.com/AlexxIT/go2rtc/pkg/tapo"
)
func main() {
rawURLs := []string{
"tapo://[your-cloud-pw]@[your-tapo-local-ip]",
"tapo://admin:[cloud-pw-md5sum]@[your-tapo-local-ip]",
"tapo://admin:[cloud-pw-shad265]@[your-tapo-local-ip]",
}
for _, rawURL := range rawURLs {
client, err := tapo.Dial(rawURL)
if err != nil {
fmt.Printf("Err dial to %s: %v\n", rawURL, err)
continue
}
client.Close()
}
}
go2rtc:
streams:
tapo_c212_7a43:
- rtsp://usr:[email protected]:554/stream1
- ffmpeg:tapo_c212_7a43#audio=aac#audio=opus#video=h264#hardware
- tapo://[email protected]
Cheers and good luck. |
Beta Was this translation helpful? Give feedback.
-
|
Wondering if this thread is still monitored. I have 4 TC60 and 1 C110 cameras. They all work great in Frigate except for the audio during live view. I've tried everything I can think of. Audio is actually recorded along with the video. Appreciate if someone can help me here. streams: cameras: FFPROBE: The camera has two audio as well as just a speaker. Don't see either in Frigate live view. Please help. |
Beta Was this translation helpful? Give feedback.
-
|
I am not at home to review my tapo yaml but the most important thing is a
https connection. Are you accessing it that way?
…On Sun, Jul 20, 2025, 10:09 AM Frank ***@***.***> wrote:
Wondering if this thread is still monitored. I have 4 TC60 and 1 C110
cameras. They all work great in Frigate except for the audio during live
view. I've tried everything I can think of. Audio is actually recorded
along with the video.
Appreciate if someone can help me here.
streams:
office:
- ***@***.***/stream1
- "ffmpeg:office#audio=aac"
- ***@***.***
cameras:
Office:
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/office
input_args: preset-rtsp-restream
roles:
- record
- audio
- detect
output_args:
record: preset-record-generic-audio-copy
FFPROBE:
[{"return_code":0,"stderr":"","stdout":{"programs":[],"stream_groups":[],"streams":[{"codec_long_name":"H.264
/ AVC / MPEG-4 AVC / MPEG-4 part
10","width":2304,"height":1296,"avg_frame_rate":"15/1"},{"codec_long_name":"AAC
(Advanced Audio Coding)","avg_frame_rate":"0/0"}]}}]
The camera has two audio as well as just a speaker. Don't see either in
Frigate live view.
Please help.
—
Reply to this email directly, view it on GitHub
<#8963 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAOXG3TXQTFQLEZMZXCXKR33JOPKNAVCNFSM6AAAAABAU7A5WKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGOBSGQZTEMY>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
Frigate? I have tried directly to port 5000 and through Home Assistant proxy. I access HA through a reverse proxy so it's always https: |
Beta Was this translation helpful? Give feedback.
-
|
Just logged in through port 8971 with a configured user. Still no. |
Beta Was this translation helpful? Give feedback.
-
|
@FS1961 Okay, here's an example config that works for my Tapo setup: |
Beta Was this translation helpful? Give feedback.
-
|
I’ll give it a try. It’s nearly the same. On Jul 20, 2025, at 5:30 PM, derekcentrico ***@***.***> wrote:
@FS1961 Okay, here's an example config that works for my Tapo setup:
go2rtc:
streams:
...
portable:
- ***@***.***:554/stream1
- ***@***.***
- ffmpeg:portable#audio=aac:
cameras:
...
portable:
enabled: true
mqtt:
bounding_box: false
timestamp: false
crop: true
height: 360
quality: 100
ffmpeg:
output_args:
record: preset-record-generic-audio-aac
inputs:
- path: rtsp://127.0.0.1:8554/portable
input_args: preset-rtsp-restream-low-latency
roles:
- detect
- path:
***@***.***:554/stream1#audio=aac#video=copy
input_args: preset-rtsp-restream-low-latency
roles:
- record
hwaccel_args: preset-vaapi
...
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Okay, I made mine look like yours and it still doesn't work: Is my HASH_ID too long? Using 256. streams: cameras: 
|
Beta Was this translation helpful? Give feedback.
-
|
Tapo app. Did you enable third party compatibility under tapo lab?
Also, for what it's worth I'm using 0.16 beta 4.
…On Sun, Jul 20, 2025, 12:50 PM Frank ***@***.***> wrote:
Okay, I made mine look like yours and it still doesn't work:
streams:
office:
- ***@***.***:554/stream1
- ***@***.***
- "ffmpeg:office#audio=aac"
cameras:
Office:
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/office
input_args: preset-rtsp-restream
roles:
- detect
- path: ***@***.***:554/stream1#audio=aac#video=copy
***@***.***:554/stream1#audio=aac%23video=copy>
input_args: preset-rtsp-restream
roles:
- record
output_args:
record: preset-record-generic-audio-copy
Screenshot.2025-07-20.at.6.49.23.PM.png (view on web)
<https://github.com/user-attachments/assets/5409246a-7daf-4e2a-9307-3d0b40b9b65e>
—
Reply to this email directly, view it on GitHub
<#8963 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAOXG3UHJUMRESBQXU3XXLL3JPCGFAVCNFSM6AAAAABAU7A5WKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGOBSGUYDKNY>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
Yes - I enabled 3rd party in the tapo app. I'm currently running 0.15.2. Not sure where to go from here. It would be very nice to have the audio capabilities on these cameras in my Frigate deployment. Thanks for all your suggestions. |
Beta Was this translation helpful? Give feedback.
-
|
Current config for TC60 camera - doesn't work. go2rtc: cameras: |
Beta Was this translation helpful? Give feedback.
-
|
Hi all! Pre-reqs to get it going for Frigate are to configure the correct settings in the Tapo app: 1.) And in the app - under your account ive have enabled "Third Party Sevices" 2.) Go into the Camera and then the settings (push the settings icon on the far right corner) - Go to "Advanced Settings" and:
PLEASE NOTE --> Two way audio ONLY works via HTTPS (not http). This is my working configuration for no ffmpeg errors, PTZ and two way audio. (remember, this is not the full config.yml, it is just the camera relevant stuff) Hope it helps someone. |
Beta Was this translation helpful? Give feedback.
-
|
In any case for this to work you have to have a working webrtc connection to frigate. You can test it via the go2rtc web page |
Beta Was this translation helpful? Give feedback.
-
sub stream is not in use im my simple example above - so no its not required. I use my tapo cloud plain text password. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the continued support! I've tried both the plain text and SHA256 passwords, with and without admin or cloud userid. Nothing changes. I'm not sure I understand the environment required. I access my Frigate server two ways.
I keep reading that for the TAPO cameras I need to access via SSL. Not an expert so isn't this right? If not, maybe this is the problem? I also can't access my go2rtc via SSL but I can access directly through port 1984. Not sure what this buys me though. I feel like this is the problem. I have 2FA turned off, TAPO lab turned on. It's just odd that the TAPO C520WS works! |
Beta Was this translation helpful? Give feedback.
-
For hearing what the camera says you need to unmute the speaker icon :). Jokes aside - to get audio to work I do believe (not 100% sure here) that you need to have the following defined for your camera: |
Beta Was this translation helpful? Give feedback.
-
|
I haven't kept up sorry but one other trick that may not have been mentioned is to do a hard reset of the camera. It fixed my initial issues now that I think about it. And it's necessary after any update so disable auto updates. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks! Do you mean remove power or factory reset as a hard reset? Just curious. On Jul 24, 2025, at 2:14 PM, derekcentrico ***@***.***> wrote:
I haven't kept up sorry but one other trick that may not have been mentioned is to do a hard reset of the camera. It fixed my initial issues now that I think about it. And it's necessary after any update so disable auto updates.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Yes, do a factory reset for the camera. Stick something in the pinhole and hold the button down until it resets sort of thing. Check the specific method for that camera, my models are different. |
Beta Was this translation helpful? Give feedback.
-
|
I did a "hard reset" on the C110 camera. No change. streams: cameras: Now I have this after starting Frigate, I get the audio icon briefly and then it disappears. |
Beta Was this translation helpful? Give feedback.
-
|
Okay, this may be a browser issue as well. I've been using MacOS Safari with the above. With MS Edge on the Mac, I get this: |
Beta Was this translation helpful? Give feedback.
EDIT: Updated with latest instructions (8 March '25)
However you must have webrtc configured and functioning. If webrtc is not working the two way audio won’t function.
In addition, you must be accessing the frigate front end via SSL. I'm using nginx reverse proxy in front of mine.
In some cases you need to enable Third-Party Compatibility" in the Tapo Lab sect…