Nest Acquires Home Automation Hub Revolv, but Will Stop Selling It
recode.net
recode.net
One big disappointment was that when Nest purchased DropCam they shelved Dropcam's then up-coming "Tabs" which were security sensors which communicated to a DropCam and you could receive alerts via their hub[0].
Honestly in the rush to home automation it really feels like security has been ignored. Traditional security companies charge too much and their products are antiquated ($30/month subscriptions anyone?).
A lot of people aren't comfortable with IP cams in their home for obvious reasons. They would be more comfortable with motion sensors which connect into a hub and allow you to receive push notifications when they're triggered on a schedule.
I know for an elderly relative I wanted that exact setup. She was uncomfortable with an IP camera in her home (which is reasonable) so I was looking for a single motion sensor which would send me alerts so the same thing could be accomplished without invading privacy.
Home security is ripe for disruption.
As a software engineer, residential security systems bug the hell out of me. Almost all of them are susceptible to someone coming up to your house and snipping the phone and network cables before entering. That's right, these systems do nothing if the connection is cut. There is no keep-alive. Apparently, phone lines disconnect so much that if the security company called the police every time it happened, there would be a lot more false positives than actual emergencies. ADT does have a product that helps with this: they use wired phone lines as well as cellular lines for communication. This setup is harder to disrupt.
Moreover, almost all security systems are susceptible to a very simple attack: run into the house and find the wiring panel. Then smash it. There, now no call will be made to the monitoring station. Most "new" internet connected panels suffer from this because they integrate the key pad and the central unit into one easily smashable device that is typically installed right by the entrance.
Also, I actually get a discount on my homeowner's insurance by having burglary and fire protection installed. If I do this myself, no matter how clever, the insurance company won't see it as a real system.
Realistically, if someone wants to get into your house, and grab something or hurt you, they will. No security system you can afford will prevent that. What you really want is a big fat ADT (or whatever) sign in your front yard, so that the lowest level burglars simply move on. Fire protection is a whole other game and at least to me is very important: I want to protect my possessions, but even more importantly my pets.
Re: your comment about your insurance company not recognizing a homebrew security system, all I've got to say about that is that I don't care how good a coder you are, being the sole QA person for your house's security system is probably a pretty miserable experience. :)
- There are use cases for "smart" motion sensors which aren't security (did you see my elderly relative example?).
- Most common criminals won't cut the wires into your home. They're looking for an easy score unless you are a common target of professional criminals I wouldn't worry about it.
- There are degrees of security systems. A simple smart system definitely won't be in the upper echelons of what is available, but that's fine, there is market enough below that.
- Cannot argue with an insurance discount, good point.
However if anyone is interesting in hiring a wicked-smart (former) Revolv electrical engineer/hardware engineer who also has software engineer experience, let me know. They will be relocating to Bay Area anyway - my email is in the last line of my profile.
This basically means I might as well go back to my ISY-99i Pro with a bunch of python glue code. sigh
There seems to be a hub phobia. I'm not saying it makes tons of sense to have multiple little servers for every device but I look at things like my kitchen and wonder, which heating hub I would choose. my microwave, oven, toaster, etc.
If there is going to be some kind of singular hub (which would be great) it needs to run apps and have expansion capabilities for the radios. A nest will not cut it. Also, without nest having thread enabled, the only way for things to talk is over wifi (nest <-> api.nest.com) and http. not bad for consistency but it sure would be nice to have all of the communication stay in the local network.
On another note, my San Fran apartment doesn't have a thermostat....