Reverse-Engineering Google Nest Devices

I find it fascinating that people keep obsessing on how Nest is "monetizing the user's data" through Google.

I won't go into details, but believe me when I say there's way more effort being put in guaranteeing customer privacy than in integrating Nest data into Google's platform. In fact, if you Google around you'll find press announcements describing, in much more detail than I could go here, the kind of arrangement Google and Nest arrived at when the acquisition happened. The data separation clause was a huge part of it. Nest wasn't acquired for the consumer data they could bring over, but rather because... you know, biggest company in the (then booming) IoT sector. Investments on projected revenue are made all the time, but when Google makes one people cook up all kinds of theories about nefarious purposes ¯\_(ツ)_/¯

So, no. What I meant is there wouldn't be enough people buying this "expert" versions of Nest Cams to justify building them. That's all. If you have solid research to the contrary, I'm sure our PMs would love to talk to you.

> If you treat people like idiots, they will respond in kind.

That's a big assumption you are making about how I treated potential customers of my own startup that I put over a year and a half of effort in. It's not about "idiocy", it's just not the same crowd you have in the Bay Area, were store owners will gladly try anything to attract more customers. Leaflets and "neighborhood bulletins" are still a thing there, even when it gives you 0 visibility on how effective they are as a marketing tool and it costs thousands of dollars per month. Anyway, if you want the details, we can discuss them offline.

> You think people can buy and install Nest's current thermostats, but won't be able to install a turn-key local server that needs literally the same WiFi information?

It's not just the server, then you have to setup the camera to point it to the server, provide some rigging to make the video consumable, create credentials in the server if you want any kind of protection against MitM/Spoofing, etc. etc. etc. The very reason Dropcam was founded was because the CEO's dad, an EE, couldn't figure out how to setup one of those "expert" systems. Greg Duffy saw the potential business opportunity and went for it.

I understand if it's not the product you want. We don't pretend to be the perfect product for everyone. My personal opinion - not reflecting Nest's policy on this opinion at all - is that I'd rather sacrifice a 5% increase in sales than increase engineering/operations/marketing/sales effort a 15%. It's just bad business.

From my perspective it is pretty bad. While I could edit an entry in the schedule (e.g. move it, change temp range), I had no way to add or remove an entry in the schedule, had no idea what the original values were, how to cancel/undo, or know what I was editing without making a change. It was frustrating at best.