Thanks. Our driver has been updated now and seems to be all happy with the new eco stuff.
While I have you, just to provide some feedback, which I know will be spitting into the ocean but nonetheless… From the perspective of an automation system vendor, and knowing what is going out there in the professional automation world, I have to say that the smarter you guys (who are making these types of devices) make them, the more of a PITA they are to support in a useful way.
The thing is, when it comes to installing automation systems, the biggest single problem that we have is that of defining generic semantics for various type of devices via which we can expose them in a way that makes them interchangeable. Without that, every system becomes a bespoke, customized operation. When we can fit all devices of a given type into a generalized view of such things and expose them in standardized way, then the integrator can create generic logic and touch screen interfaces and voice control and so forth that will work with any device of that type.
That is the only way to make real automation (as opposed to standalone islands of functionality) available for a lower price. If every system has to be customized, it remains where it is, pricey and marginal. And it’s that lack of standardization that is the bane of the automation world.
We have worked so hard over the last four’ish years to create a set of ‘device classes’ via which we can expose various types of devices (or fractional parts of functionality such as volume control.) The benefits that this work has generated are immense for the person setting up the solution (either for himself or for his customer.) The further a device strays from the commonality of its type, the harder and harder it becomes to make it fit within that generalized view, and at some point we just give up and don’t try to do so. And that device gets left out of a whole raft of benefits, which makes the customer a lot less likely to select it.
From the point of view of the automation system vendor and integrator, who is looking for real integration, not just a screen for this device, a screen for that device which is trivial and of limited value, we frankly would do better with dumb devices that do what they are told and report what they know, because those are almost always easier to expose via a generic device type.
I know that this is probably not something anyone at Nest wants to hear. I’m guessing that selling to individuals who use them outside of any integration is the primary business of Nest. I have to remind people all the time that the IoTs and automation are at opposite ends of the spectrum, the former being about selling standalone widgets and the latter being about creating a powerful team of devices designed to be subservient to a global controller. But, to the degree that use in automation systems in a non-trivial way matters, and to the degree that furthering the goal of highly integrated automation becoming more accessible is desired, all of the above needs to be kept in mind. With integration, it’s the team that matters, not the individuals.
Charmed Quark Systems, Ltd