From: Bruce W. <br...@mi...> - 2002-03-25 13:49:04
|
> this is awesome. thanks a lot... > i have a question about the dimming from off, though... i admit > that i haven't taken a look at the way the code works internaly > yet this morning, but would'nt it be possible to have > an extra step of sending an 'ON' if $level = OFF? Sure, sound like a good idea. Not sure why I didn't think of it :) Attached is a modified set_level that seems to do the trick. Bruce -------- # Allow for specific light levels on older devices by monitoring current level sub set_level { my ($self, $level) = @_; # Modify only dd% states if ($level =~ /^(\d+)\%/) { $level = $1; my $level_now = $self->{level}; unless (defined $level_now) { $self->set(ON); # First turn it on, then go to specified level $level_now = 100; } my $level_diff = $level - $level_now; # Round of to nearest 5, since cm11 only does by 5 $level_diff = 5 * int $level_diff/5; &main::print_log("Changing light by $level_diff ($level - $level_now)") if $main::config_parms{x10_errata} >= 3; $level = $level_diff; } $self->set($level) if $level; # No need to set if level=0 } |
From: Bruce W. <br...@mi...> - 2002-03-25 13:50:15
|
> >So, the 2 options I see are to: > > > > - add another parm to X10_Item that tells us what kind of device it is > > > > - add another method, to use with the older devices. > > > you know, after thinking about it a bit, i think the 1st method > would be more elegant in the long run. just starting to play > around with this new code and it is already becoming > cumbersome to keep track of which lights are on LM14s and which > are on old-school lamp modules. i've started naming my variables > with a suffix to keep track... > > i'll take a look at the X10_Item and see if i can figure out > you're dealing with the states and try creating another param for > X10_Item, keeping things backward compatble for the > existing users... Good point. If you have a mix of modules, it would be much easier to keep track of them when they are defined. So what this means is that those of you who have LM14s (or any other module that can do preset dims) would need to defined them with something like: $light_new = new X10_Item('A1', 'LM14') $light_old = new X10_Item('A2'); in order to take advantage of the preset dim abilities. If you didn't specify LM14, it would still work, but would dim from full on, like the old modules do. Sounds good to me. Anyone object or have a different suggestion? Scott, if you have not done this yet, I can do it here. I think all we need to do is store the moddule type, and then query it in the set method. Bruce |
From: Jeph B. <jb...@ne...> - 2002-03-25 21:36:32
|
Forgive me if there's a FAQ on this topic, but I'm new X10 in generally, and I've been browsing this list for a little while now, to get a feel for things.. To get started, I obviously need a PC board X10 2-way transmitter/receiver. Although this is not listed under "System Requirements" on the webpage, there are several referrences to hardware, speficically the X10 CM11 ActiveHome and the CM17 Firecracker, which is cheaper. The question is, to hook up to my Linux / FreeBSD (/ MacOS X?) machine and run MisterHouse X10 apps, does it matter which one I buy? Are there any limitations to the Firecracker over the ActiveHome, besides the Windows software that comes with it that will go unused anyway? I figure, the only way to jump into this stuff is to, well, jump into this stuff, but I don't want to jump into buying a piece of hardware that has serious limitations that I'll find down the road. Also, I own (and happen to wear daily for some reason) a Sun Java Ring that friend from Sun gave me. This has an end that looks a lot like the iButton. Seeing the Java references from the iButton page, leads me to believe this is a type of iButton. Anyone know if I'm on track here? Thank for the help in getting started. -- Jeff A. Blaize Network Engineer <jb...@ne...> |
From: Bruce W. <br...@mi...> - 2002-03-26 01:43:22
|
> Forgive me if there's a FAQ on this topic, but I'm new X10 in generally, > and I've been browsing this list for a little while now, to get a feel for > things.. > > To get started, I obviously need a PC board X10 2-way > transmitter/receiver. Although this is not listed under "System > Requirements" on the webpage, there are several referrences to hardware, > speficically the X10 CM11 ActiveHome and the CM17 Firecracker, which is > cheaper. The question is, to hook up to my Linux / FreeBSD (/ MacOS X?) > machine and run MisterHouse X10 apps, does it matter which one I buy? > Are there any limitations to the Firecracker over the ActiveHome, besides > the Windows software that comes with it that will go unused anyway? > > I figure, the only way to jump into this stuff is to, well, jump into this > stuff, but I don't want to jump into buying a piece of hardware that has > serious limitations that I'll find down the road. > > Also, I own (and happen to wear daily for some reason) a Sun Java Ring > that friend from Sun gave me. This has an end that looks a lot like the > iButton. Seeing the Java references from the iButton page, leads me to > believe this is a type of iButton. Anyone know if I'm on track here? The CM17 (firecracker) is slower, can not do fancier X10 commands (like preset dims), and worst of all, is xmit only. It was a good buy back when it was $6, mainly for the other modules that came with it :) It is useful for driving the 'IR commander' (see recent post). I think the Java Ring is more than a smiple ibutton ID button. I think it can download and run Java code. We currently don't have code that interaces to it, but maybe it can function as a simple ID button? Bruce |