Users only get three hours of free Nest video storage, but Google can retrieve videos much later.
See full article...
See full article...
If anyone is concerned about keeping their doorbell camera footage after their house burns down simply set up off site backup. That doesn't really have anything to do with my comment though, which was about preferring wired cameras over wifi. Neither have anything to do with uploading to a cloud server somewhere.*more vulnerabilities and more risk. Losing footage in event of fire/flood/tornado/theft.
POE doorbell puts an exterior network access point. Can be knocked off and someone could have access to network without actual physical access.
If you want to go the ultra-cheap route, you can even just use ffmpeg to read rtsp streams and write the video files to disk. I do this for internal wifi cameras that I set up whenever we're gone for a long time. I even use the privacy-nightmarish Eufy cameras but completely block their internet access; all they can do is talk to the linux box that reads their rtsp streams. Not for the totally non-technical types, but anyone on here can do it if you just want something simple.Blue Iris is what I am looking for!
My use case is mainly my long driveway. I would like to keep track of people/vehicles coming and going. I would setup the network exactly as jimrose describes.
Hardware is my forte, just needed a little help with the software end of things.
Thanks.
ExecStart=ffmpeg -hide_banner -y -loglevel error -rtsp_transport tcp -stimeout 15000000 -use_wallclock_as_timestamps 1 -i $URL -vcodec copy -acodec copy -f segment -reset_timestamps 1 -segment_time 3600 -segment_format mkv -segment_atclocktime 1 -strftime 1 /mnt/LCARSStorage01/nvr/%i/%%Y-%%m-%%dT%%H%%M-%i.mkvHave you found a non-wired Unifi doorbell solution? I've looked (though not in the last few months) and only found PoE ones.What I just suggested above has WiFi options, I just prefer POE hardwiring. Less network issues and vulnerabilities, no batteries. But you don't have to run cable to make it all work.
I use Amcrest AL-P402W wifi cameras. They have SD card support. There is a cloud service but it is optional and I don't use it. I can store around 2 weeks of HD video on a single SD card. Multiple camera support through their Amcrest link app that is rock solid.What solutions do fellow Arsians recommend for WiFi cameras connecting back to local storage? I want to run maybe 3 Wifi camera, possibly solar powered, connecting back to a computer running some kind of software to grab the video and archive it. I would be willing to pay for the software, but open source solutions are nice too.
The cameras don't need to be sold as solar powered as I can figure out how to solar power any camera with a DC input.
I just want to buy the equipment once and own it forever. I abhor the subscription model.
Taking victim blaming to a new level here, aren’t you?Data retention outrage aside, it is kind of unbelievable that someone of her means wouldn't spring for the upgraded subscription if she insists on using a product that relies on said subscription for (what I consider) basic functionality.
The G4 has a WiFi option, but it's out of stock at the moment:Have you found a non-wired Unifi doorbell solution? I've looked (though not in the last few months) and only found PoE ones.
My house used to have doorbell wiring, but it disappeared in one of the remodels that previous owners did over the last 50 years. Getting a cable to the front door would be a huge effort with lots of drywall patching, because there's no crawlspace anywhere and no attic over the front entryway.
Running ethernet cabling is really easy, just make sure you get plenum rated cable if it will go in the wall and watch a couple tutorials on how to terminate the ends into an RJ45 connector. Running things into the attic, basement, or crawl space will be the easiest way to move laterally from room to room. In many houses you can access the eaves through the attic, so you can run the cable out there and connect your camera that way. For a doorbell, follow the existing wire if you can (or use it to pull your Cat6 cable if you don't need it and it isn't secured inside the wall which they often aren't); the only electric risk there is at the transformer, but you can disconnect the doorbell wire (if you are uncomfortable doing it live, you can always flip the breaker off that it is connected to first). PoE is the way to go since you don't need to run power then and a PoE injector is fairly inexpensive if you don't have a switch that provides power.I also want my own security system but I’m a relatively new homeowner. Don’t these cameras need to be wired? I’m so daunted by having to run cables - data and power (may be solved by PoE) but it seems like it’ll cost be 2-3K for an electrician to do this. Plus equipment and all, isn’t it like 5K to get it all done? I’m not the best when it comes to electricity, having shocked myself a couple of times lol. I was thinking of getting the Reolink from Costco.
I do want to move over but I chose ecobee because the project seems daunting. Would love to have my own setup though.
That's not really the takeaway here, and the article even tried to preempt comments like this.Google keeps personal data without our knowledge? Shocking.
This is why I hid mine inside of an old console stereo-style cabinet.The only real downside is basically the same as the upside: the video is all stored locally. If someone breaks into my house and smashes my UDMP with a hammer, then the video is toast.
If your exterior network drops give you access to anything other than cameras, you've seriously fucked up the most basic of security practices.*more vulnerabilities and more risk. Losing footage in event of fire/flood/tornado/theft.
POE doorbell puts an exterior network access point. Can be knocked off and someone could have access to network without actual physical access.
I know a lot of engineers at Google, and this 100% tracks with my perspective as well. The company is really far, far less nefarious than a lot of people generally think. Sure, they show ads based on data and have deeply enshittified search, but it's not some giant data-sucking conspiracy, either.Yeah, this is pretty normal. I was an engineer at Google for a decade or so, ending ~11 years ago. I was in Adwords, mostly behind the scenes stuff like data persistence and ad quality / safety rather than directly user-facing stuff. Still, we had tons of advertiser data and some user data (click logs and the like). PII would get cleaned up promptly because there are legal requirements. But for other stuff where there wasn't a law or a TOS, we might delete the references to the data but leave the underlying files lying around until some sort of periodic garbage collection happened. This was just for efficiency, not from any nefarious intent.
I'm not sure how this would affect any particular third-party data in Google Cloud. It totally depends on the TOS and security guarantees the customer is paying for.
What I'm guessing happened here (and it's just a guess) is that someone at Google dug through the Nest logs to see if there were any "events" at the Guthrie house. Then they went out to the filesystem (or Spanner, Bigtable, whatever new hotness they use now.) and were lucky to find that those files / entries hasn't been deleted yet. At that point some messing about on the command line would get them the data.
Addressing the "Google sells all your data" crowd: They really don't — or didn't a decade ago anyway. The attitude was that they're better than anyone else in the world at extracting values from the data, eg by using it to decide which adds to show when. So they thought they could make more money by hanging on to data instead of trying to sell it.
Whether that is any better than selling the data is an exercise for the reader.
Thanks, Aurich!The G4 has a WiFi option, but it's out of stock at the moment:
https://store.ui.com/us/en/category...4-doorbell-pro?variant=uvc-g4-doorbell-pro-us
Software? https://frigate.video/What solutions do fellow Arsians recommend for WiFi cameras connecting back to local storage? I want to run maybe 3 Wifi camera, possibly solar powered, connecting back to a computer running some kind of software to grab the video and archive it. I would be willing to pay for the software, but open source solutions are nice too.
The cameras don't need to be sold as solar powered as I can figure out how to solar power any camera with a DC input.
I just want to buy the equipment once and own it forever. I abhor the subscription model.
If you have the capability to get from my doorbell ethernet, through my UniFi NVR, and into the rest of my network then you are some kind of state level actor that would simply break into my house and take whatever you want or kidnap me instead of bothering lol.If your exterior network drops give you access to anything other than cameras, you've seriously fucked up the most basic of security practices.
Besides, what would they be doing? If they wanted all my data, it'd be faster to just bust a window, rip my server out of the rack, and hightail it out of there before the cops show up. Well, as long as they brought a friend. A single person isn't running with my server on hand. Do they just want to see what the cameras see? Ok, well, if they manage to break into the cameras (granted, I don't trust that they're all that secure, that's why they're segregated in the first place), then cool, they can see around the outside of my house....just like they could if they picked their head up from their laptop?If you have the capability to get from my doorbell ethernet, through my UniFi NVR, and into the rest of my network then you are some kind of state level actor that would simply break into my house and take whatever you want or kidnap me instead of bothering lol.
I always get a chuckle when I see people claiming Google sells your data.Yeah, this is pretty normal. I was an engineer at Google for a decade or so, ending ~11 years ago. I was in Adwords, mostly behind the scenes stuff like data persistence and ad quality / safety rather than directly user-facing stuff. Still, we had tons of advertiser data and some user data (click logs and the like). PII would get cleaned up promptly because there are legal requirements. But for other stuff where there wasn't a law or a TOS, we might delete the references to the data but leave the underlying files lying around until some sort of periodic garbage collection happened. This was just for efficiency, not from any nefarious intent.
I'm not sure how this would affect any particular third-party data in Google Cloud. It totally depends on the TOS and security guarantees the customer is paying for.
What I'm guessing happened here (and it's just a guess) is that someone at Google dug through the Nest logs to see if there were any "events" at the Guthrie house. Then they went out to the filesystem (or Spanner, Bigtable, whatever new hotness they use now.) and were lucky to find that those files / entries hasn't been deleted yet. At that point some messing about on the command line would get them the data.
Addressing the "Google sells all your data" crowd: They really don't — or didn't a decade ago anyway. The attitude was that they're better than anyone else in the world at extracting values from the data, eg by using it to decide which adds to show when. So they thought they could make more money by hanging on to data instead of trying to sell it.
Whether that is any better than selling the data is an exercise for the reader.
You are of course, right.I always get a chuckle when I see people claiming Google sells your data.
Same here. I opt out of personalized ads, and I use an ad blocker whenever possible. I even used one when I was an Adwords engineer, though I told it not to block the text ads in the search results. Those weren't as frequent or obtrusive a decade ago, plus I needed to be able to see them to do my job.Like you said, is that better than just selling the data? Eh. I'd say it's not as bad as selling the data. I still opt out of personalized ads.
Plenum is overkill for running inside the walls. You only need it if you're pulling the cable through air ducts. Plenum is non-toxic when burned, standard ethernet casing is toxic when burned. In the event of a fire, you don't want your air ducts to spew toxic smoke.Running ethernet cabling is really easy, just make sure you get plenum rated cable if it will go in the wall and watch a couple tutorials on how to terminate the ends into an RJ45 connector. Running things into the attic, basement, or crawl space will be the easiest way to move laterally from room to room. In many houses you can access the eaves through the attic, so you can run the cable out there and connect your camera that way. For a doorbell, follow the existing wire if you can (or use it to pull your Cat6 cable if you don't need it and it isn't secured inside the wall which they often aren't); the only electric risk there is at the transformer, but you can disconnect the doorbell wire (if you are uncomfortable doing it live, you can always flip the breaker off that it is connected to first). PoE is the way to go since you don't need to run power then and a PoE injector is fairly inexpensive if you don't have a switch that provides power.
That said, there are solar powered wireless options, though I am not very familiar with them since I just hardwired cameras around the house over the course of a day or so.
At work, we keep even the most temporary files for 7 days. That way if something goes wrong, I have a few days to figure out what and reprocess everything. Add a few more days in case something happens over a holiday, and nobody notices until we're back at work.I don't think there was anything nefarious going on here, clearly google didn't have intimidate access to footage. Which likely means they went to a fairly great effort to hunt down the physical drive that it was originally stored on in a data center so that the footage could be manually recovered before it was overwritten.
I agree that (specific technical details aside) the circumstances in this case support that Google isn't just saving everything for nefarious purposes, and had to actively work out a way to retrieve "deleted" data that was only deleted in the standard, fast-but-non-destructive, "mark this as deleted" sense.I don't think there was anything nefarious going on here, clearly google didn't have intimidate access to footage. Which likely means they went to a fairly great effort to hunt down the physical drive that it was originally stored on in a data center so that the footage could be manually recovered before it was overwritten.
In large-scale enterprise storage solutions, “deleted” for the user doesn’t always mean that the data is gone.
Can it ring a standard chimebox?My needs are modest, so I set up an entry level UniFI camera doorbell combo.
$99 Doorbell Lite, hardwired with power over ethernet.
https://store.ui.com/us/en/category/cameras-doorbells/products/uvc-doorbell-lite
NVR Instant with an 8 gig drive.
https://store.ui.com/us/en/category/cameras-nvr/collections/unvr-instant
Have it hooked into my Apple ecosystem with Scrypted running on my Unraid server. Doorbell rings my Homepod Mini, camera shows up on my AppleTV, all recordings local, cannot be WiFi jammed, not expensive.
To be honest I don't know, we ripped ours out. I think no though.Can it ring a standard chimebox?
If there even is a deletion request.Sigh. What likely really happened: Google is likely using some sort of a "garbage collection" algorithm for video records. When a video is "deleted" from the account, only a pointer to the video record is immediately deleted.
Then some background process sweeps the blob storage and deletes records that are not referenced. This typically takes some time, and in this case employees likely were able to get in and manually retrieve the stored video.
And yes, GDPR actually is fine with that. It's OK for the deletion requests to take reasonable time to be processed.
It’s possible to conclude the exact opposite from this story. Why does anyone have security cameras? So that the video can be used later. If you are using a cloud service, you should be paying to have the video stored for some amount of time.Well, that's that. I'm going fully over to Ubiquiti since I own my data. It can still be subpoenaed by the courts, but at least I'm in control of my own data retention.
I mostly have security cameras so I can see when someone comes up to the door without having to interrupt my work if it's not important, or to check on the dogs if they're playing outside without me having to get up from whatever I'm doing.It’s possible to conclude the exact opposite from this story. Why does anyone have security cameras? So that the video can be used later. If you are using a cloud service, you should be paying to have the video stored for some amount of time.
I have ring cameras, outside only, and I pay so that they are stored in the cloud for 30 days. If criminals get recorded, the videos will be accessible.
I mean, it’s outside. I have no idea if my neighbors across the street have a security camera recording my front yard all the time. I really don’t expect privacy in my front yard. I don’t care if the cloud storage provider truly deletes it after the designated time.
Or pulled from tape. Google absolutely murders tape drives because of the volume they store.I don't think there was anything nefarious going on here, clearly google didn't have intimidate access to footage. Which likely means they went to a fairly great effort to hunt down the physical drive that it was originally stored on in a data center so that the footage could be manually recovered before it was overwritten.
Kansas! Actually that’s very unlikely but it’s the only other data store I could remember off the top of my head you didn’t mention.Yeah, this is pretty normal. I was an engineer at Google for a decade or so, ending ~11 years ago. I was in Adwords, mostly behind the scenes stuff like data persistence and ad quality / safety rather than directly user-facing stuff. Still, we had tons of advertiser data and some user data (click logs and the like). PII would get cleaned up promptly because there are legal requirements. But for other stuff where there wasn't a law or a TOS, we might delete the references to the data but leave the underlying files lying around until some sort of periodic garbage collection happened. This was just for efficiency, not from any nefarious intent.
I'm not sure how this would affect any particular third-party data in Google Cloud. It totally depends on the TOS and security guarantees the customer is paying for.
What I'm guessing happened here (and it's just a guess) is that someone at Google dug through the Nest logs to see if there were any "events" at the Guthrie house. Then they went out to the filesystem (or Spanner, Bigtable, whatever new hotness they use now.) and were lucky to find that those files / entries hasn't been deleted yet. At that point some messing about on the command line would get them the data.
Addressing the "Google sells all your data" crowd: They really don't — or didn't a decade ago anyway. The attitude was that they're better than anyone else in the world at extracting values from the data, eg by using it to decide which adds to show when. So they thought they could make more money by hanging on to data instead of trying to sell it.
Whether that is any better than selling the data is an exercise for the reader.
I really doubt Nest cam videos ever make it to tape. They don't keep them around that long and what they do store is expected to be more or less immediately available if it gets called up.Or pulled from tape. Google absolutely murders tape drives because of the volume they store.
Of course they can make it to tape. The whole idea is recovery if something catastrophic takes place after all. It's been used to rebuild a lot of GMail at one point (it's in the public SRE handbook, so it can be talked about)I really doubt Nest cam videos ever make it to tape. They don't keep them around that long and what they do store is expected to be more or less immediately available if it gets called up.
Sigh. What likely really happened: Google is likely using some sort of a "garbage collection" algorithm for video records. When a video is "deleted" from the account, only a pointer to the video record is immediately deleted.
Then some background process sweeps the blob storage and deletes records that are not referenced. This typically takes some time, and in this case employees likely were able to get in and manually retrieve the stored video.
And yes, GDPR actually is fine with that. It's OK for the deletion requests to take reasonable time to be processed.
I use Eufy cameras and so far am fairly happy with them.What solutions do fellow Arsians recommend for WiFi cameras connecting back to local storage? I want to run maybe 3 Wifi camera, possibly solar powered, connecting back to a computer running some kind of software to grab the video and archive it. I would be willing to pay for the software, but open source solutions are nice too.
The cameras don't need to be sold as solar powered as I can figure out how to solar power any camera with a DC input.
I just want to buy the equipment once and own it forever. I abhor the subscription model.