Originally Posted by chinadog
What it really comes down to is what works for you.
Agreed. I wasn't stating a case to influence you one way or another, just offering a different perspective for those of us who have automation systems and want a singular integrated source of control instead of individual apps for different devices.
Dennis - perhaps you had overlooked this in a previous post, but the NEST thermostat specifically does not provide the command codes, so the entire device driver would have to be built from scratch to integrate with third party control systems. You would think that the NEST folks would want to not limit their market by not opening themselves up to third part control.
There are code "sniffers" that will allow you to fully characterize every command to build a device driver - but who the heck wants to go through that laborious process? I've had to build my own RS-232 device drivers before back before the days of IP control and it is a tedious and thankless job at-best.
The other complicating issue with the Nest is that it doesn't accept static IP addresses. You could use DHCPD (daemon) some static leases as part of a DHCP pool, tying each static lease to a specific MAC address only, so the lease is only granted for that specific IP if the MAC address of the network card is the same as specified in the static lease. You have to hope that you never have a problem where another device would steal an IP defined as static lease, even if the specified MAC address was not present online. Those static leases are permanent DHCP leases (they are leased for ever, even if I have specified they should be leased for 1440 minutes). If you go this route, enable a DHCP pool with a maximum of 1 client. You could also define this IP as static lease, i.e. that it is only leased to a specific MAC address. So you would be sure that your device always connects at the same IP and that no other device gets that IP (well, except for hackers...).
So until the Nest is Crestron or Savant certified with an officially validated device driver, it won't be ready for prime time, particularly in multiple t-stat homes. But like Bud rightly said, it really depends on what works for you.