Deeper than that, even. It seems like this is intended as a local-network cloudlet[1] substrate.
Launch an app on your phone that needs a companion frontend server instance to talk to? One gets launched "in the cloud"—specifically, in a virtual cloud owned by the app author. But where is that instance, physically? Usually a provider like AWS... but with a cloudlet peering arrangement, that instance could instead end up running on your router. (Not as crazy as it sounds if your app has an N:M frontend-backend server topology.)
* It’s a play on the word “shard”.
* It suggests privacy and protection.
* It suggests something that is nearby, as opposed to “the cloud” that is far away.
…
Unfortunately, the word is probably too susceptible to negative connotation.
Revolv Hub supported devices:
I know it's anecdotal, but the Insteon forums are filled with similar stories. I was a very early adopter and have been through several generations of devices, and I'm committed to using another platform when I start replacing the remaining Insteon switches that will inevitably die.
I wouldn't recommend Insteon to anyone. X-10 was more reliable in my house. I'm evaluating Zigbee options now.
It pretty much is... it's their way of sneaking the 'home automation' core/aggregation box into people's homes masked as a wireless router (for now).
I'm sure the capability you mention will come heading into the future. The only question will be : execution/security and will a competitor come up w/ a more secure/well executed product which won't serve as a data vacuum hose to google.
This kind of product launch on the heels of their massive alphabet re-org with no understanding where it came from (division wise) or what its goal is leads me to question whether the re-org is really going to move google beyond its former execution flaws ...