AD8BC Posted December 2, 2007 Share Posted December 2, 2007 OK, it's a stretch... ran into this device: http://www.hobbyengineering.com/H2012.html It's an Ethernet based Input/Output controller. My thoughts being that the ISY could talk to this over the Ethernet and use the inputs as triggers and could write to the outputs... Just a thought... might be easier than interfacing to the EZIO series devices. Link to comment
d_l Posted December 2, 2007 Share Posted December 2, 2007 Certainly the ability of the ISY to send and receive user-defined command strings over the LAN and conditionally test for received strings in its programs would be a wonderful addition to its capabilities. It would really make the ISY a Universal Device. Link to comment
Michel Kohanim Posted December 26, 2007 Share Posted December 26, 2007 AD8BC, I am so very sorry for the tardy reply ... yes, indeed this is possible. My only concerns are: 1. It has no case 2. It's not a known brand (like Global Cache) But, for sure, this would be an excellent idea and something we'd be looking into. Thanks so very much! With kind regards, Michel OK, it's a stretch... ran into this device: http://www.hobbyengineering.com/H2012.html It's an Ethernet based Input/Output controller. My thoughts being that the ISY could talk to this over the Ethernet and use the inputs as triggers and could write to the outputs... Just a thought... might be easier than interfacing to the EZIO series devices. Link to comment
rowland Posted December 27, 2007 Share Posted December 27, 2007 The device that AD8BC referred to is just one example of an Ethernet enabled device that would be desirable to interface to the ISY/99. I'm sure that ISY/99 users will discover many, many more such Ethernet enabled devices that would be desirable to interface to the ISY/99. Extending the current ISY/99 Program semantics in a general way to accomodate each of these devices would be difficult, if not impossible. There are just too many varieties of devices, each with their own characteristics and idiosyncrasies. It is also difficult to make the business case for a particular device to be supported. A better way would be to add one Condition type (in addition to Status, Control, Program, X10, and IR), say JSDKCondition, that would become true when a JSDK event was created. The interface for an Ethernet enabled device would be captured in a Java program, not in a ISY/99 Program. Link to comment
Michel Kohanim Posted December 27, 2007 Share Posted December 27, 2007 rowland, Very interesting idea! I do think that we would eventually have to support other network based appliances within ISY otherwise we might run the risk of asking the clients to have a computer always on. With kind regards, Michel The device that AD8BC referred to is just one example of an Ethernet enabled device that would be desirable to interface to the ISY/99. I'm sure that ISY/99 users will discover many, many more such Ethernet enabled devices that would be desirable to interface to the ISY/99. Extending the current ISY/99 Program semantics in a general way to accomodate each of these devices would be difficult, if not impossible. There are just too many varieties of devices, each with their own characteristics and idiosyncrasies. It is also difficult to make the business case for a particular device to be supported. A better way would be to add one Condition type (in addition to Status, Control, Program, X10, and IR), say JSDKCondition, that would become true when a JSDK event was created. The interface for an Ethernet enabled device would be captured in a Java program, not in a ISY/99 Program. Link to comment
rowland Posted December 27, 2007 Share Posted December 27, 2007 There would definitely be two classes of network based appliances. The first being an officially sanctioned class that would have ISY Program support. The second class (the unsanctioned, the unwashed, the unwanted step children, etc) would be those that would interface in the way I described. It would be this second class that users are on their own; riskier but providing more possibilities. In some cases an unsanctioned interface to a network appliance could "graduate" to become a sanctioned interface worthy of ISY Program support if it proves to be popular, well-understood, etc. Link to comment
Morris Hansen Posted December 28, 2007 Share Posted December 28, 2007 Maybe I am missing something with the Elk integration. I would think the Elk would be a great way to collect/control IO interfaced with the ISY. Some examples: Control HVAC from an Insteon keypad. IR command of Elk - Movie mode that would control the lighting, blinds, etc. Having this type of integration would really open up the flexibility of both the ISY and the Elk. Link to comment
Michel Kohanim Posted December 28, 2007 Share Posted December 28, 2007 I agree with both of you (Rowland and mohansen). We are currently working on simplifying our framework to allow easier integration with external network appliances such as ELK, IES Touchscreen, as well as JSDK/Web Services events as Rowland suggested. With kind regards, Michel Link to comment
jgraziano Posted December 28, 2007 Share Posted December 28, 2007 Touchscreen, yes! It would be so nice to have an ethernet based touchscreen that can manipulate and display the new internal variables in a future ISY release. Assign a button to set an internal bit and use the bit in programs. Or monitor bit status with an indicator on the touchscreen. Or, really cool, display analog variable data such as On level or time remaining in a 'wait' cycle in a program. Michel if you guys would just decide to dedicate yourselves to this, never see your families and throw out your life, we could have these things!!!!! Aren't we worth it? Good luck!!!!! Link to comment
Michel Kohanim Posted December 30, 2007 Share Posted December 30, 2007 Jim, With Pleasure (except not seeing the family part)! With kind regards, Michel Touchscreen, yes!It would be so nice to have an ethernet based touchscreen that can manipulate and display the new internal variables in a future ISY release. Assign a button to set an internal bit and use the bit in programs. Or monitor bit status with an indicator on the touchscreen. Or, really cool, display analog variable data such as On level or time remaining in a 'wait' cycle in a program. Michel if you guys would just decide to dedicate yourselves to this, never see your families and throw out your life, we could have these things!!!!! Aren't we worth it? Good luck!!!!! Link to comment
jgraziano Posted December 30, 2007 Share Posted December 30, 2007 Well, we all thank you guys for the tremendous support. (and family is always the priority). Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.