Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Wanted to spy on my dog, ended up spying on TP-Link

kennedn.com

Post reply on HN
Print view View original

111–120 of 181 posts

Re: Wanted to spy on my dog, ended up spying on TP-Link

#111

Post by xrd »

BLKNSLVR wrote: post #106

I tried and failed at enough suggestions I found on the internet and via AI to cobble together a frigate configuration that eventually worked with the Tapo cameras. RTC setup section: go2rtc: streams: : - rtsp://tapoadmin: @ :554/stream1 - ffmpeg: #audio=opus - tapo:// @ _sub: - rtsp://tapoadmin: @ :554/stream2 - ffmpeg: _sub#audio=opus - tapo:// @ Main section: : ffmpeg: output_args: record: preset-record-generic-au…

Do you use an outdoor camera with this? I'm trying to find one and my c402 does not appear to have that support.

Re: Wanted to spy on my dog, ended up spying on TP-Link

#112

Post by jrockway »

machinate wrote: post #75
3abiton wrote: post #72

Earlier quoted context omitted.

What I don't get is, if I am using my bank website on linux (with full root ability), it's still almost nearly the same as having the app on Android. The argument of "we lock it down to protect you makes 0 sense to me"

They usually don't let you deposit checks via web app.

It's unclear what device attestation does here. You can print a fake check and take whatever picture you want. If it's using dead pixels or something as a device fingerprint, you get those dead pixels. You can also fake dead pixels, of course. Authenticating the phone's OS doesn't authenticate the camera, or what the camera's looking at. It's a signal, maybe, but the weak link in "a napkin with the right numbers and scribble on it is a money transfer" is probably not whether someone has root on the device that's taking a picture of the napkin.

Re: Wanted to spy on my dog, ended up spying on TP-Link

#113

Post by Gigachad »

selinkocalar wrote: post #89

IoT security is generally terrible, but the fact that consumer routers are essentially unaudited black boxes processing all your network traffic is genuinely concerning. Most people have no idea their router firmware hasn't been updated in years and is probably running known CVEs. The supply chain trust model for networking hardware is broken.

There are countless routers in between you and your destination which you can't audit anyway. End devices long since consider the routers to be compromised and have everything verified and encrypted in transit. So unless your router is participating in a DDoS or mining bitcoins it doesn't really matter how secure it is.

Re: Wanted to spy on my dog, ended up spying on TP-Link

#114

Post by xrd »

BLKNSLVR wrote: post #98
xrd wrote: post #55

Earlier quoted context omitted.

Really? Mine has a switch for static. You aren't seeing that in the app? Configuration -> Advanced settings -> Network

Confirmed here. I've got four of them, and they all have this setting. I know because I changed them from DHCP reservation to static IP recently.

Are any of these outdoor cameras? Do you use rtsp if so? I'm trying to find an outdoor camera that supports frigate and surprised my new c402 does not.

Re: Wanted to spy on my dog, ended up spying on TP-Link

#115

Post by gradstudent »

drnick1 wrote: post #107
briHass wrote: post #103

Earlier quoted context omitted.

The stuff on the shelf, sure, but you can always go 'prosumer-grade' like Ubiquiti or Mikrotik for hardware that actually receives timely updates and has competently written firmware.

Ubiquiti is awful, it's a cloud-centric ecosystem. The best "prosumer-grade" stuff is probably OpenWrt. If you need more power, opnSense or a plain Linux distro on an x86 machine.

Not entirely true. There's a local admin option, where your Ubiquiti devices never see the internet (well, except your gateway). You can then connect and admin the whole thing remotely via your own VPN. It's quite nice, actually.

Re: Wanted to spy on my dog, ended up spying on TP-Link

#116

Post by kennedn »

BLKNSLVR wrote: post #106

I tried and failed at enough suggestions I found on the internet and via AI to cobble together a frigate configuration that eventually worked with the Tapo cameras. RTC setup section: go2rtc: streams: : - rtsp://tapoadmin: @ :554/stream1 - ffmpeg: #audio=opus - tapo:// @ _sub: - rtsp://tapoadmin: @ :554/stream2 - ffmpeg: _sub#audio=opus - tapo:// @ Main section: : ffmpeg: output_args: record: preset-record-generic-au…

Hello, as I alluded to in my blog post you should use tapo:// as the main stream source to get two-way audio. You can then optionally use rtsp://.../stream2 as a lower resolution sub stream source for detections. Defining both tapo:// and rtsp:// in a single stream is redundant as go2rtc only picks one or the other. My own configuration is here for reference https://github.com/kennedn/frigate/blob/7c56604e819d2cb1da28...

Re: Wanted to spy on my dog, ended up spying on TP-Link

#117

Post by BLKNSLVR »

xrd wrote: post #111
BLKNSLVR wrote: post #106

I tried and failed at enough suggestions I found on the internet and via AI to cobble together a frigate configuration that eventually worked with the Tapo cameras. RTC setup section: go2rtc: streams: : - rtsp://tapoadmin: @ :554/stream1 - ffmpeg: #audio=opus - tapo:// @ _sub: - rtsp://tapoadmin: @ :554/stream2 - ffmpeg: _sub#audio=opus - tapo:// @ Main section: : ffmpeg: output_args: record: preset-record-generic-au…

Do you use an outdoor camera with this? I'm trying to find one and my c402 does not appear to have that support.

Sorry no.

I use Reolink's for outdoor. The Tapo's are all indoor C210/C211 (cheap, but do the job just fine).

Looks like the C402 has two different hardware versions[0] so maybe the old one doesn't work but the new one does? A firmware upgrade might also be worth trying. This reddit page suggests trying ONVIF as the go2RTC connection[1].

Good luck!

[0]: https://www.tp-link.com/us/support/download/tapo-c402/

[1]: https://www.reddit.com/r/frigate_nvr/comments/1liosei/tapo_c...

Re: Wanted to spy on my dog, ended up spying on TP-Link

#118

Post by kennedn »

xrd wrote: post #110

Does anyone have a good reference for which tapo cameras support rtsp? I have a c210 that works well (sort of, you can't use it with their cloud capture) and I have it working with frigate. But today I got a c402 (outdoor) thinking I could use it to capture my son's soccer practice. But that doesn't have the camera account option under advanced. I love the price point of these devices but the functionality is all ove…

You should still be able to use the tapo:// go2rtc stream source even if the camera does not support the rtsp:// via the camera account option. Have a look at my frigate configuration for reference - https://github.com/kennedn/frigate/blob/7c56604e819d2cb1da28...

Re: Wanted to spy on my dog, ended up spying on TP-Link

#119

Post by BLKNSLVR »

kennedn wrote: post #116
BLKNSLVR wrote: post #106

I tried and failed at enough suggestions I found on the internet and via AI to cobble together a frigate configuration that eventually worked with the Tapo cameras. RTC setup section: go2rtc: streams: : - rtsp://tapoadmin: @ :554/stream1 - ffmpeg: #audio=opus - tapo:// @ _sub: - rtsp://tapoadmin: @ :554/stream2 - ffmpeg: _sub#audio=opus - tapo:// @ Main section: : ffmpeg: output_args: record: preset-record-generic-au…

Hello, as I alluded to in my blog post you should use tapo:// as the main stream source to get two-way audio. You can then optionally use rtsp://.../stream2 as a lower resolution sub stream source for detections. Defining both tapo:// and rtsp:// in a single stream is redundant as go2rtc only picks one or the other. My own configuration is here for reference https://github.com/kennedn/frigate/blob/7c56604e819d2cb1da2…

Aaaah, I should have specified above that I don't use (or care about) the two-way audio in the frigate config.

Thanks for the info, I just hacked away at various config suggestions until one combination worked.

Cheers!

Re: Wanted to spy on my dog, ended up spying on TP-Link

#120

Post by bayesianbot »

> SIDENOTE: If you want 2 way audio to work in frigate you must use the tapo:// go2rtc configuration for your main stream instead of the usual rtsp://. TP-Link are lazy and only implement 2 way audio on their own proprietary API.

Annoyingly when this is in use, I can't use ONVIF which seems like the only way to pan and tilt the camera using open tools. So if I want to use two way audio and also control the camera, I have to stop the process reading tapo:// stream, start onvif client and rotate, turn off onvif client and start streaming using tapo:// again

Post reply on HN