controlink V2

[Dave Stenhouse-2]

I have a controlink V2 that I use to control some Insteon LampLinc
Dimmers.  Now that I am the proud owner of a PLM, I am looking to
integrate the ControLink to Misterhouse, and thinking that it should
work about how a KeypadLink works, and thus be configured about the same
way.  However, I'm having some difficulty, and want to verify my
assumptions.
Can I use the ControLink in this way, or is there some (devcat?) issue?
I have the Lamplinks working with Misterhouse, in that they are defined
as IPLD, and can be turned off and on.  They are linked to buttons on
the ControLink, which works nicely, but I want to have Misterhouse know
the status of what is happening when I press a button on the ControLink.
-Dave

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
________________________________________________________
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365

[Gregg Liming]

Dave Stenhouse wrote:

> I have a controlink V2 that I use to control some Insteon LampLinc
> Dimmers.  Now that I am the proud owner of a PLM, I am looking to
> integrate the ControLink to Misterhouse, and thinking that it should
> work about how a KeypadLink works, and thus be configured about the same
> way.  However, I'm having some difficulty, and want to verify my
> assumptions.
> Can I use the ControLink in this way, or is there some (devcat?) issue?
> I have the Lamplinks working with Misterhouse, in that they are defined
> as IPLD, and can be turned off and on.  They are linked to buttons on
> the ControLink, which works nicely, but I want to have Misterhouse know
> the status of what is happening when I press a button on the ControLink.

The ControLink works sufficiently different that I have not added
support for all of its special situations.  I don't recall, off-hand,
what the specific differences are; but, they were sufficient to cause me
to ignore it.

Gregg

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
________________________________________________________
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365

[Dave Stenhouse-2]

Gregg Liming wrote:

> Dave Stenhouse wrote:
>  
>> I have a controlink V2 that I use to control some Insteon LampLinc
>> Dimmers.  Now that I am the proud owner of a PLM, I am looking to
>> integrate the ControLink to Misterhouse, and thinking that it should
>> work about how a KeypadLink works, and thus be configured about the same
>> way.  However, I'm having some difficulty, and want to verify my
>> assumptions.
>> Can I use the ControLink in this way, or is there some (devcat?) issue?
>> I have the Lamplinks working with Misterhouse, in that they are defined
>> as IPLD, and can be turned off and on.  They are linked to buttons on
>> the ControLink, which works nicely, but I want to have Misterhouse know
>> the status of what is happening when I press a button on the ControLink.
>>    
>
> The ControLink works sufficiently different that I have not added
> support for all of its special situations.  I don't recall, off-hand,
> what the specific differences are; but, they were sufficient to cause me
> to ignore it.
>
> Gregg
>  

Since I clearly don't have the requisite skill to add support for it, I
guess it sucks to be me, at least for the moment.  If you feel like
tackling it, I would be quite willing to lend you mine for testing.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
________________________________________________________
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365

[Gregg Liming]

Dave Stenhouse wrote:

> Since I clearly don't have the requisite skill to add support for it, I
> guess it sucks to be me, at least for the moment.  If you feel like
> tackling it, I would be quite willing to lend you mine for testing.

Usually, I am quite willing and want to add support or to help others
add support for insteon devices.  This device, however, is in a
different category.  If you're familiar with insteon i1 devices (which
are most of them) eventually evolving to i2, then you realize how much
of an improvement that i2 will bring.  That being said, i1 still has to
be supported for the time being even though they are obviously inferior
from the stand point of memory management.  The ControLinc seems to
slightly pre-date i1 and, is IMO a bit of an albatross due to the
requirement to treat it differently at rather low levels.

I do have a ControLink and it sits unused on a shelf.  I don't have
plans to ever use it; so, if anyone wants it for the cost of shipping,
then let me know off-list.  The RemoteLinc and KeypadLinc "in a box" are
comparable solutions that are physically more compact and can serve
similar/equal functions.  I do recall while implementing all of the
linking support that trying to also provide support for the ControLink
would be "stepping backwards" and I deliberately avoided it.  Adding
support for it now would not be all that easy.

Sorry to be the bearer of what is likely bad news for you.

Gregg

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
________________________________________________________
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365

[Dave Stenhouse-2]

Gregg Liming wrote:

> Dave Stenhouse wrote:
>
>  
>> Since I clearly don't have the requisite skill to add support for it, I
>> guess it sucks to be me, at least for the moment.  If you feel like
>> tackling it, I would be quite willing to lend you mine for testing.
>>    
>
> Usually, I am quite willing and want to add support or to help others
> add support for insteon devices.  This device, however, is in a
> different category.  If you're familiar with insteon i1 devices (which
> are most of them) eventually evolving to i2, then you realize how much
> of an improvement that i2 will bring.  That being said, i1 still has to
> be supported for the time being even though they are obviously inferior
> from the stand point of memory management.  The ControLinc seems to
> slightly pre-date i1 and, is IMO a bit of an albatross due to the
> requirement to treat it differently at rather low levels.
>
> I do have a ControLink and it sits unused on a shelf.  I don't have
> plans to ever use it; so, if anyone wants it for the cost of shipping,
> then let me know off-list.  The RemoteLinc and KeypadLinc "in a box" are
> comparable solutions that are physically more compact and can serve
> similar/equal functions.  I do recall while implementing all of the
> linking support that trying to also provide support for the ControLink
> would be "stepping backwards" and I deliberately avoided it.  Adding
> support for it now would not be all that easy.
>
> Sorry to be the bearer of what is likely bad news for you.
>
> Gregg
>  

Well, Greg, you've crushed my dreams of using the ControLink I already
own, but that's OK.  I've been eyeing the RemoteLink with bad intent
since the day they released it.  I also certainly understand your
reasons for not supporting the ControLink.  I was early in line for
Insteon stuff, I think that the ControLink was the hybrid to the
fuel-cell of Insteon (OK, that may be pushing it a little).  Maybe the
Stanley Steamer to the Insteon Dusenberg?
Anyway, I appreciate the frank and clear explanation of the challenges
involved, and I really appreciate the work you and Jason have done to
make Insteon a really powerful protocol within the Misterhouse framework.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
________________________________________________________
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365

[Garry Doucette]

Dave

Sorry about your ControLink bad news.

I just wanted to pile on here and say that I finally got a chance to play
around with KeyPadLinc and Insteon Scenes this weekend and everything is
working very nicely thanks to the work of Gregg and Jason. Using Gregg's
documentation it was a relatively painless process.

You guys are awesome and I really, really appreciate what you have done with
Insteon and MH. The WAF is on a high for the time being, at least until I go
and break something again.

Thanks!

Garry

-----Original Message-----
From: Dave Stenhouse [mailto:dave@...]
Sent: Sunday, September 21, 2008 7:55 PM
To: The main list for the MisterHouse home automation program
Subject: Re: [mh] controlink V2

Gregg Liming wrote:

> Dave Stenhouse wrote:
>
>  
>> Since I clearly don't have the requisite skill to add support for it,
>> I guess it sucks to be me, at least for the moment.  If you feel like
>> tackling it, I would be quite willing to lend you mine for testing.
>>    
>
> Usually, I am quite willing and want to add support or to help others
> add support for insteon devices.  This device, however, is in a
> different category.  If you're familiar with insteon i1 devices (which
> are most of them) eventually evolving to i2, then you realize how much
> of an improvement that i2 will bring.  That being said, i1 still has
> to be supported for the time being even though they are obviously
> inferior from the stand point of memory management.  The ControLinc
> seems to slightly pre-date i1 and, is IMO a bit of an albatross due to
> the requirement to treat it differently at rather low levels.
>
> I do have a ControLink and it sits unused on a shelf.  I don't have
> plans to ever use it; so, if anyone wants it for the cost of shipping,
> then let me know off-list.  The RemoteLinc and KeypadLinc "in a box"
> are comparable solutions that are physically more compact and can
> serve similar/equal functions.  I do recall while implementing all of
> the linking support that trying to also provide support for the
> ControLink would be "stepping backwards" and I deliberately avoided
> it.  Adding support for it now would not be all that easy.
>
> Sorry to be the bearer of what is likely bad news for you.
>
> Gregg
>  

Well, Greg, you've crushed my dreams of using the ControLink I already own,
but that's OK.  I've been eyeing the RemoteLink with bad intent since the
day they released it.  I also certainly understand your reasons for not
supporting the ControLink.  I was early in line for Insteon stuff, I think
that the ControLink was the hybrid to the fuel-cell of Insteon (OK, that may
be pushing it a little).  Maybe the Stanley Steamer to the Insteon
Dusenberg?
Anyway, I appreciate the frank and clear explanation of the challenges
involved, and I really appreciate the work you and Jason have done to make
Insteon a really powerful protocol within the Misterhouse framework.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes Grand prize is a trip for two to an Open Source event anywhere in the
world http://moblin-contest.org/redirect.php?banner_id=100&url=/
________________________________________________________
To unsubscribe from this list, go to:
http://sourceforge.net/mail/?group_id=1365


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
________________________________________________________
To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365