[mh] Insteon Branch status

[Marc M. <ma...@me...>]

On Mon, Aug 27, 2012 at 07:25:11PM -0700, George Farris wrote:
> > The insteon branch is indeed looking for one or more people interested in
> > taking it over to continue its support and finish the few things that are
> > missing.
> 
> Marc can you outline what is missing?  I am using the Insteon branch and
> it seems to work very well.  I am interested in updating the Insteon
> documentation.

0) See the InsteonRedux wiki from Greg on our wiki for a few notes from
him.

1) scan all links, sync all links, delete orphans are all unstable for
me and can stop in the middle, causing insteon scans to stop working
until I restart mh (there are likely several sub bugs there)

2) lamp update onlevel/ramprate kills mh

This still fails:
18/06/2011 17:11:22  Running: lvr lamp update onlevel/ramprate
18/06/2011 17:11:22  [Insteon::ALDB_i1] $lvr_lamp accessing memory at location: 0x0032
18/06/2011 17:11:22  [Insteon_PLM] DEBUG: Parsing serial data: 02620a99e505280006
18/06/2011 17:11:22  [Insteon_PLM] DEBUG: received interface acknowledge: obj=$lvr_lamp; command=set_address_msb; extra=00
18/06/2011 17:11:23  [Insteon_PLM] DEBUG: Parsing serial data: 02500a99e518d4ce212800
18/06/2011 17:11:23  [Insteon_PLM] DEBUG: Parsing serial data: 02620a99e5052b3206
18/06/2011 17:11:23  [Insteon_PLM] DEBUG: received interface acknowledge: obj=$lvr_lamp; command=peek; extra=32
18/06/2011 17:11:23  [Insteon_PLM] DEBUG: Parsing serial data: 02500a99e518d4ce212bfe
Can't locate object method "local_onlevel" via package "Insteon::ALDB_i1" at
../lib/Insteon/AllLinkDatabase.pm line 534.

On Mon, Aug 27, 2012 at 08:27:04PM -0700, George Farris wrote:
> Hi all,
> 
> I recently updated my PLM to a new dual band (DB) unit and also bought a
> DB Lamplinc.
> 
> This will probably apply to the earlier thread which I just found, about
> appliancelincs.
> 
> BTW I am using Gregg's Insteon branch so this won't apply to the trunk I
> expect.
 
Wise choice. The old code is not as modular, and dead for maintenance.

> All new devices that are i2cs MUST be linked to a controller before it
> will respond to a command.  What does this mean?  Well from a practical
> stand point, if you want to control a device, say $test_lamp, it must be
> linked to the PLM with a scene first.  I wasn't successful linking it
> manually.
 
Thanks for that info.
Just to make sure, what do you mean with "link with a scene"?
Does 'link to plm' option not work?
 
> This of course was all discovered mostly trial and error thanks to the
> incredible piece of s*it Smarthome are about support.  I mean why on

To be fair, they only support their windows software. MH is not really
their problem, starting with the fact that MH does not support the lastest
I2 protocol from what I understand.

> earth would you develop a product and the restrict people from
> developing software for it.  They need fire a few people at Smarthome.

Don't they provide programming info? They not super good at doing so,
but they do AFAIK.

Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/