Dean Roddey
Senior Member
In order to justify making such a box, it seems to me, it would have to target the professional market, or it would never have a big enough market to make it worth doing in any kind of business sense probably. And there's already the Elk and Omni kind of sitting in that space now, so that would make it even less inviting for someone who is in it to make money (and everyone has to be in it to make money if they want to be running a real business.)
On the best-of vs. integrated, I would have to agree with the above statements. A set of components does not a system make, necesarily. This is all too often proven in the A/V world, where a set of the best of breed A/V components often make a horrible system as a whole because they just don't get along. I think that clearly Crestron shows that the strategy that appeals to the professional installer is to provide more stuff out of the box. As a software based product, we'll never provide THAT much stuff out of the box, since Crestron makes all kinds of stuff that to me seem way out of their core competency. But, within our software automation world, we think that having as much of it in one box as possible is the best way to insure it all works together smoothly today, and continues to tomorrow.
Devices like the Elk and Omni clearly fairly best case scenarios in this respect. Because of what they are, they are very much designed to cleanly integrate into a larger automation system. So combining one of them with a software product on top seems to me to be a very reasonable compromise, or requirement if you are one of those folks who doesn't feel comfy handing off fundamental stuff to a software-based system.
I don't think though that you'll never get a hardware box that can compete with the broad level of functionalty of a PC based system. By the time you did that, you'd have created a PC basically. The power available in an XP or Linux based box, and the power and flexibility of the programming tools are enormous. It wobbles the mind to think how much it's grown in my lifetime, and will continue to grow. And you have an entire industry that does nothing but enhance this platform as rapidly as possible in as many directions as possible. A company like Crestron is dwarfed by the amount of R&D and manufacturing that goes on constantly in the PC world.
At some point we'll have micro-ITX boards that are as powerful as mini-ITX boards are now, with just a few big chips, and you'll start seeing very small boxes that can serve as automation controllers, inexpensive enough that you can put one in each room more cheaply than you can build a centralized architecture perhaps. With something like the UMPC devices probably down to $250 or some such thing by then, I think that's going to start making it difficult for proprietary hardware based automation companies to keep making their own and competing.
They'll still be able to play the reliability card for sure, and I'm sure it'll still be valid to an arguable degree. But it would a whole lot cheaper to make just a couple of technologies that you can fit into a PC based architecture that to build your own system from the ground up. I think that if someone came up with a super-reliable, proprietary wired/wireless network technology (Zigbee ain't nearly fast enough), that would take care of the biggest single worry of using a PC based automation system, which isn't the controller but the network. TCP/IP just wasn't really designed for the hands-off, automagical network that we really need in homes. Failure of name resolution mechanisms is the biggest single problem we have to deal with I think, in terms of failures in customer systems. I think that it would be quite reasonable to consider a parallel, and much smarter, network just for the key subsystems of the home.
Anyway, I'm way past rambling, but it's an interesting topic that obviously I ruminate a lot about, so it's nice to ruminate out loud sometimes....
On the best-of vs. integrated, I would have to agree with the above statements. A set of components does not a system make, necesarily. This is all too often proven in the A/V world, where a set of the best of breed A/V components often make a horrible system as a whole because they just don't get along. I think that clearly Crestron shows that the strategy that appeals to the professional installer is to provide more stuff out of the box. As a software based product, we'll never provide THAT much stuff out of the box, since Crestron makes all kinds of stuff that to me seem way out of their core competency. But, within our software automation world, we think that having as much of it in one box as possible is the best way to insure it all works together smoothly today, and continues to tomorrow.
Devices like the Elk and Omni clearly fairly best case scenarios in this respect. Because of what they are, they are very much designed to cleanly integrate into a larger automation system. So combining one of them with a software product on top seems to me to be a very reasonable compromise, or requirement if you are one of those folks who doesn't feel comfy handing off fundamental stuff to a software-based system.
I don't think though that you'll never get a hardware box that can compete with the broad level of functionalty of a PC based system. By the time you did that, you'd have created a PC basically. The power available in an XP or Linux based box, and the power and flexibility of the programming tools are enormous. It wobbles the mind to think how much it's grown in my lifetime, and will continue to grow. And you have an entire industry that does nothing but enhance this platform as rapidly as possible in as many directions as possible. A company like Crestron is dwarfed by the amount of R&D and manufacturing that goes on constantly in the PC world.
At some point we'll have micro-ITX boards that are as powerful as mini-ITX boards are now, with just a few big chips, and you'll start seeing very small boxes that can serve as automation controllers, inexpensive enough that you can put one in each room more cheaply than you can build a centralized architecture perhaps. With something like the UMPC devices probably down to $250 or some such thing by then, I think that's going to start making it difficult for proprietary hardware based automation companies to keep making their own and competing.
They'll still be able to play the reliability card for sure, and I'm sure it'll still be valid to an arguable degree. But it would a whole lot cheaper to make just a couple of technologies that you can fit into a PC based architecture that to build your own system from the ground up. I think that if someone came up with a super-reliable, proprietary wired/wireless network technology (Zigbee ain't nearly fast enough), that would take care of the biggest single worry of using a PC based automation system, which isn't the controller but the network. TCP/IP just wasn't really designed for the hands-off, automagical network that we really need in homes. Failure of name resolution mechanisms is the biggest single problem we have to deal with I think, in terms of failures in customer systems. I think that it would be quite reasonable to consider a parallel, and much smarter, network just for the key subsystems of the home.
Anyway, I'm way past rambling, but it's an interesting topic that obviously I ruminate a lot about, so it's nice to ruminate out loud sometimes....