|
|
|
|
|
|
by vicaya
4482 days ago
|
|
|
I was partially being facetious. This article is about a Rube Goldberg-esque API and this site is about hackers. I'm just pointing out that it can be done cheaply with better flexibility and precision by hackers like me. I'm one of those people who find the Nest algorithm frustrating and want to tinker with it (with more properly placed sensors etc). It's not really rocket science for people who understand the basics of control theory. BTW, what does a deadbolt have anything to do with your Nest/HVAC system? Do you want to depend on Google to open/close your locks as well? It's _not_ normal to take 15-30 seconds to open a Z-wave deadbolt remotely (it's immediate if you use the lock keypad) with 50% of success rate: something (probably the security C/R exchanges) is timing out: the default timeout is 20 seconds. For me, it was 100% (knocking on wood:) with a few seconds latency for the times I tried, executing a night arrival scene from a phone in a car, which turned on path/door lights and unlocked the door, because I'd have groceries/takeouts in my both hands. I'd tend to agree that Z-Wave devices and a Vera* controller is probably too much for non-tinkerers to handle in the current state, because average people can't even handle a wifi printer :). There are people who use Nest as a basic thermostat, i.e., for the looks only. The main motivation for me to squawk on this topic is that I don't like the _trend_ of external services (nothing against Google per se :) owning my data and now control of my home. We (hackers/tinkerers) can do better and demand a choice. |
|
|
Yes, something's definitely timing out. If I watch the Vera UI after sending the command, it times out and retries several times before giving up. Yet other times it works, but usually only after at least one retry. The hub isn't too far from the door, and there's no walls in-between. The unreliability of z-wave stuff is my biggest problem with it.
The Nest responds pretty much instantly to commands despite them having to go out to the internet then back. The unofficial APIs provide access to everything the device and its web/mobile apps can do. Same with my Belkin WeMo switches and sensors -- you're probably not a fan of WeMo either, but I'm a fan of them responding instantly and speaking UPnP.
The divide between these products isn't really about "tinkerers vs non-tinkerers". If that was it, Nest/WeMo/etc would win over the monoprice z-wave stuff any day. They're much easier to hack with (no extra hardware required, HTTP APIs, open source libraries readily available) and typically do a lot more than the generic single-function devices.
The divide you've set up is around privacy and external dependency. The tradeoffs there aren't the same, and not everyone's going to agree with you on that either, even hackers with full knowledge. I don't necessarily think self-hosted and self-supported APIs are a better future. That's a future that would limit a lot of the cool stuff you can do with these devices to us, instead of making it available to everyone. Most of the coolest stuff in our homes today already relies on entrusting a certain amount of control and information to 3rd parties, from your electric company, to your ISP, to the makers of all the set-top boxes connected to your TV, to the phone in your pocket. All of these things involve giving up tons of data and control of your home.
I have no problem with "smart thing" makers hosting APIs so long as they remain trustworthy with that data, and reliable, which is not a huge ask. I'm a lot more confident Google can run Nest's API reliably and securely than Vera staying in business and keeping its P.O.S. MiOS functioning.