-
Notifications
You must be signed in to change notification settings - Fork 490
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dahua and Tapo cameras: two-way not working for Frigate and HA #1464
Comments
Showing you the part of the config which need to get right, you need admin: and your tapo account password sha256 hashed in upper case (the password you use to login to tapo services) your ffmpeg line is wrong too
|
Thanks, I'll tweak that. How do you have the URL for the actual cameras? |
You mean the ip address? |
@derekcentrico For this setup I use only go2rtc and Custom: WebRTC Camera card in HA go2rtc config
Custom: WebRTC Camera
|
@mofman Like the camera section in Frigate config.
|
Assuming its running on the location and the dafault port, use rtsp://127.0.0.1:8554/Kitchen - keep the name the same. |
@mofman and @rici44 thank you both. I revised my cameras. Oddly, I get this error when using the go2rtc URL for the camera: rtsp://127.0.0.1:8554/kitchen: Invalid data found when processing input Cloud password is the password that goes to the Tapo app, correct? I tried that one and the tapocam:password from the RTSP setup just for kicks. No go.
I have firmware 1.1.3 flashed to it, using the very last release of 1.1.3 available as a bin. Did y'all have an issue with a password or anything? |
LOL now I get "2024-11-15 18:31:15.077453990 18:31:15.077 WRN [rtsp] error="streams: Expected StatusCode to be 401, received 200, exec: rtsp://127.0.0.1:8554/kitchen?video&audio: Invalid data found when processing input\n" stream=portable" using "Tapo_C120v1_en_1.1.3_Build_230930_Rel.56236n_up_boot-signed_1697192563556.bin" instead of "Tapo_C120v1_en_1.1.3_Build_230930_Rel.56236n_up_boot-signed_1697194362284.bin" |
Did you block the domains I suggested? |
Yeah I blocked them via pihole. My firewalla shows only one domain it's hitting, 5 times. aps1-relay-dcipc-beta.i.tplinknbu.com |
Are you familiar with python? If so Can you try this code, install pytapo via pip then create the script below replacing with your values and let me know what your response is when you run it pip3 install pytapo
|
@mofman Sure, so here is the resulting matter:
Seems like I'm stuck in what the other issue thread is about. Hoping @rici44 sends me the blob filename for 1.2.2 so I can download/flash it. 🥇 |
1.2.2 is just the latest version available from the app, Go through this checklist
|
Domains blocked. No flows are going through to any of those domains. Py script started giving results after factory reset: I tried the tapo:// combinations of plain text password, admin:MD5 and admin:shasum256. None work. Generated those using the same password used in the py script. |
You're really close now that you're successfuly getting authenticated. Try all these combos below, you can try them all at once. Then go to your go2rtc web client and see if it creates any producers http://192.168.0.XXX:1984/
|
@mofman So, added all those and boom something works because it is in Frigate now. Thanks!!! |
No problem, you should be able to identify which is the working line is using a process of elimination. |
@derekcentrico proper camera reset and proper blocked domains are necessary steps. I block domains with IP addresses of those domains (nslookup) but IPs changed and I had to reset camera again and block with domain names. |
@rici44 yeah so I used pihole to null route the recommended domains and I monitored the network flows with my Firewalla. All good for 2 cameras. The 3rd one appears to be bricked upon flashing. Blinking red for 30 minutes after the reboot. Siiiigh |
@AlexxIT I’m wondering if it might be worth considering a mechanism where the user could simply enter their Tapo account password, for example:
When go2rtc attempts to connect, it could try various combinations automatically, such as admin:md5, admin:sha256, etc., eliminating the need for users to figure out which combination works. This should be feasible to implement without disrupting existing setups... |
@mofman go2rtc supports password as plaint text for tapo source: |
I have Tapo and Dahua cameras. I set them up with Frigate based upon their documentation. However, two-way communication doesn't work at all. Dahua shows the mic icon but doesn't transmit. Tapo doesn't even show the mic icon. I am using HTTPS. They referred me here and I've been tinkering ever since.
@mofman and @rici44 would you be kind enough to provide Frigate go2rtc and camera configs, and maybe any card configuration data from HA?
Anyone else with thoughts I'd be grateful.
This is what I got going currently:
Frigate
Home Assistant Card:
The text was updated successfully, but these errors were encountered: