261–270 of 376 posts
Earlier quoted context omitted.
I have found that the fog generating alarm systems are the ones that will stop burglars in their tracks. If they can't see, they're not going to hang about and if they've tooled up with NV then that's a whole different threat model.
You need to add the dobermans - the old fog&dog gets 'em every time.
The fog&dog&log never fails.
Earlier quoted context omitted.
You need to add the dobermans - the old fog&dog gets 'em every time.
A wooden battering ram from the ceiling does wonders. The fog&dog&log never fails.
Earlier quoted context omitted.
How did you hide it so that the thieves didn't find it?
A 7U cabinet in an overhead space that is difficult to access. Installation and configuration were a bit of a headache but ended up being worth it. There was a NAS in the office and they stripped 7 drives, sleds and all, out of it. I'm guessing with such an obvious endpoint for the camera storage it never occurred to anyone there was a second box. I had something like this in mind when I wired the building. It seemed…
But, re: alarms, I'd like to add a suggestion: Indoor sirens. They can be intolerably, painfully loud for not very much money (because piezos are cheap and square waves are easy). Using a small, random mixture of them can let them beat at different frequencies and periods, which can make them very unpleasant to behold even with hearing protection.
If you feel like being clever, you can even run them with a local battery that activates when they're disconnected. If you feel like being extra-clever, you can make them activate when they don't have the correct termination resistance at the far end of the line, or exactly the correct voltage: This way, whether the wire goes open or short, the sirens activate.
Super-extra bonus points for using a combination of methods. Any time that a thief spends figuring this out is time they aren't carrying stuff out.
And if that still seems incomplete, then: Fill the shop with smoke. They can't function when they can't even see their hand in front of their face. https://www.youtube.com/watch?v=RPgcysyFUiI
Earlier quoted context omitted.
The same is true for our AI processing on the cameras. This is entirely local and private. You can even air gap the UniFi Protect system from the Internet and it'll operate fine.
The cost is just insane though. $4-$500 for a camera that I can get equivalent specs for $50-100.
As others have pointed out they are supported for a long time. I have some earlier generations cameras that are going on 7 years of updates. Not only are you barely getting maybe a year of firmware updates at the $50-100 range but there's no comparison on the quality of the optics, sensor and overall hardware at that price differential.
Ubiquiti has done some shitty things over the years but Ubiquiti isn't competing against the $50-100 market. They're competing against the Axis and Panasonic quality builds. You've definitely got it backwards here.
And while, yes, you can get a decent camera from Reolink and the like at a good price it isn't surrounded by an exceptionally mature and well supported ecosystem that has yet to nickel and dime its customers with half ass SaaS and paid for features.
This comment couldn't be further from the reality of Ubiquiti's lineup in comparison.
Earlier quoted context omitted.
I mean, in the NAS space with a plethora of open source alternatives, that is a viable stance.
Yeah actually, there are tons of PE-proof ways to go about building a NAS. My "NAS" is a NUC with a couple drives plugged into it using a USB DAS. apt install zfs samba, and away you go.
I could split up the functions into different boxes and build a faster LAN to connect them, but doing that wouldn't improve anything except giving me more parts to goof around with. :)
Ubiquiti's biggest feature is no monthly recurring cost. I really hope they continue the streak on products like this. Seems like anything else bought up these days is switched to an MRR model with no vision into the long term viability.
I just wish they would put better processors in their stuff. Is this yet another NAS powered by an ARM Cortex?
Earlier quoted context omitted.
Have you priced a Supermicro box with 16 bays and SAS running Ubuntu?
I have, in pre-COVID days, though. The total bill including a skylake xeon E3-1285 v6 CPU, 64 GB ECC RAM, and the supermicro X11 board + chassis ( https://www.supermicro.com/en/products/archive/chassis/SC836... ) was under $1k.
Earlier quoted context omitted.
Some years ago, there were mud-slinging myths being thrown around about ZFS. Things like "ZFS needs 1GB of RAM per 1TB of storage" and "it requires that RAM to be ECC" were once common to find online. These sort of thing seemed to lead to widespread beliefs that it was inefficient, expensive, and fragile. None of that is true, of course, but folks might remember and believe these myths and conclude that it is (or was…
I still got told that I need 16GB of RAM to migrate my 12TB btrfs array from a Synology with 6GB of RAM (2GB actually used) - by TrueNAS people. Are they wrong?
No you do not need 16GB simply for a 12TB ZFS array on a plain Linux/FreeBSD box. It'll be faster, but you don't need it.
Earlier quoted context omitted.
QNAP unforgivably uses a proprietary version of ZFS with their own extensions that are not compatible with mainline OpenZFS. It can only zfs send/receive to other QNAP devices. While your data is protected like any other ZFS system, it is _NOT_ interoperable. You can not take a zpool out of a QNAP system and access it on another system with ZFS. I discovered this painfully the hard way, and won't buy from them again,…
I think the ZFS changes were due to needing a way to allow qnap systems to expand zfs pools. The raidz expansion features in openzfs probably took too long for qnap to wait.