From: Jason S. <ja...@sh...> - 2005-03-11 19:22:34
|
The Light_Item, Motion_Item, Door_Item are all abstract objects giving purpose functionality to any interface (not just X10). I have many relay driven lights, contact doors, DSC motion sensors that have nothing to do with X10, so I didnt add that functionality there. my mht file is something like: OCCUPANCY, om X10I, A3, x10_bedroom_Light LIGHT, x10_bedroom_light, l_bedroom STARGATEDIN, 3, sg_bedroom_motion MOTION, sg_bedroom_motion, m_bedroom PRESENCE, m_bedroom, om, pr_bedroom On Thu, 10 Mar 2005, Rob Walker wrote: > On Wednesday 09 March 2005 08:35 pm, Bruce Winter wrote: > > Rob Walker wrote: > > > X10I is for an X10 light module? > > > > > > X10A is for an X10 Appliance module? > > > > > > I grok the A=appliance, but why not D or L for dimmer or light, > > > respectively? > > > > > > I keep trying to remember what an X10I is, and keep falling back to all > > > of the examples I have seen which show lights defined that way, but I > > > still feel quite confused. > > > > Right. The base X10_Item (X10I) is dim-able, so is typically what we > > use for lights. > > > > You can also use a mht entry of LIGHT (for Light_Item) to use Jason's > > fancier Light_Item object. > > Aha! > > I didn't see that in any of the .mht files I had come across, yet. I see it > in /usr/share/perl5/misterhouse/Light_Item.pm now. Cool. > > thanks, > rob > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > ________________________________________________________ > To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365 > > |