- Posted on
Sun Nov 09, 2008 8:49 pm
-
Jann
offline
-
- Posts: 120
- Joined: Mar 12, 2006
- Location: Auburndale, FL
-
Please don't get me wrong. I think Indigo *can* be extended...just extend it intelligently.
We are *still* seeing further Insteon integration in Indigo (as well as X10 updates to new X10 modules -- still waiting for FULL EZX10RF Link Management support, Matt). I just would like to see it done smartly in a method that stays true to what Indigo was meant to be. (If I am speaking out of turn, Matt, please clobber me) but it would seem that versus coding for 1 item in it's own format of speaking is not the smartest way to go. As a programmer myself I look for the greatest return on investment. That return (to me) would be to extend this to other full product lines such as UPB, ZWave, ZigBee, etc. That way, once you code for one switch, most switches of that type "just work". Think programming for a plug in light controller...all outlet type devices are now much easier to add since you have a 'base' to work from. This is why, for instance, that it does not matter whether you use a Levitan or X10 switch, since Matt coded for one already, the other was much easier to add to Indigo. You get a larger return on investment with your user base.
For instance, supporting this thermostat would do several things right-off, not all of them good.
You would have to include either a Kludge or an "Ecobee" engine in and of itself to "speak" the device's language.
You would need a way to let people know that when they are dealing with this device it may have different results and therefore the troubleshooting would be harder for the user. (wifi connectivity vs simple power line interface issues for example).
You are also then placing this "new device" in front of the other "formats" for support. This is purely political. Do you wish to tick off all those waiting for UPB and instead do this add-on? We all waited nice and long for Matt to finish his Linking protocols for Insteon. Many many of us upgraded simply for Insteon Link Management. Does the EcoBee have that kind of following?
If Indigo actually supported other formats such as UPB, it could be used to "bridge" the format languages such that we all could have access to the devices on the "other side". For instance for the UPB people that want to use the less-expensive Insteon for a few purposes when there is no UPB alternative I can see that Indigo *could* be made to be the interpreter. Since UPB still has no RF, this opens up a whole new world for the UPB owners. Conversely Insteon/X10 owners could use long-distance UPB adapters for controlling lawn lighting, garage items, etc (those items that are longer distance than the RF/PowerLine Mesh technology of Insteon would normally allow)
To "anode's" "Times are Tough" statement I would only add that opening up a program such as Indigo to an entirely new audience of "UPB","Zwave", or "ZigBee" owners is, in the long run, a much better investment in programming time cos you then have opened up your audience to a purchaser of an entire product line versus an audience simply buying a thermostat.
Plus, it would give Norm an entire new product line to sell that is Indigo compatible! The elephant in the room that no one really speaks of (that we understand and appreciate though) is that Norm at MacHomeStore.com makes a living off of product lines -- not necessarily products in and of themselves. It may be good for us to be able to buy the EcoBee at MacHomeStore.com and use it in Indigo, but if it is only one item that Matt adds, the audience for Norm is *much* smaller. Think for a second: Would the Venstar T1700 or T1900 Thermostat & Insteon Adapter sell better than a EcoBee Thermostat? Well, if the buyer has a bunch of Insteon or X10 devices, they are more likely to purchase the Venstar devices because they ARE Insteon compatible (as I did this week -- I love it!). Thus, the investment that Matt made in adding this device (thanks Matt!) to Indigo *and* the investment that Norm made in stocking the Venstar devices is truly working for both of them. Their businesses feed off each other -- even if they were not designed to. (Sounds like a really good affiliate relationship Matt!)
In short, don't be offended that I took the tack that I did. I was just trying to say that it is better to support a format than a product.
Jann
Again, I am not trying to speak for Matt. He probably has opinions that are directly opposite from mine. I am just stating a few things that I think go toward supporting "Formats" and not "Products"