before everyone starts losing their shit, take a breath and realize that we don’t know what any of this means yet.
- yes, the nest api is going away, but it sucked to begin with, so let’s not cry over spoiled milk.
- the surprising thing should be that it took so long for google to integrate the nest acquisition into the fold, but they were probably waiting for the assistant platform to mature a bit.
- we don’t really care about the google smart home platform, per se. we care about local access to the DEVICE. as long as we can read from and configure the device via some sort of local method, we’re going to be just fine, and quite frankly, there’s pretty much zero chance that google is going to make whatever the nest API mutates into any worse than it is at the moment (~4 “streaming” data points/hour…whole integer granularity for temperature? 5% granularity for humidity?).
local device access? what ever in the world are you talking about? do we even have some sort of reference for what this would look like?
sure looks like local access to a device part of the google smart home ecosystem to me!
so yeah. chill. we got till august to see what’s what. if the existing google home hardware devices are any indication, there may very well end up being an undocumented local API which can be reverse engineered with a bit of sweat.
in the meantime, if you’re a recent nest owner, find someone who had a nest dev account before they shut off the faucet, they can still, at least as of yesterday, generate oauth tokens.