Re: [mh] MH + Insteon setup for total mh beginners

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

On Thu, Feb 12, 2009 at 02:09:43PM -0500, Gregg Liming wrote:
> Marc MERLIN wrote:
> 
> > Then it says 'Example entry in ~mh/code/insteon.mht:'
> > but I have no such file or file that looks like it.
> 
> I use .../code/items.mht as creating separate *.mht files is pointless 
> (and can cause dependency problems if you're not paying attention) in my 
> opinion.

I'll do that, thanks.

> >> gargamel:/var/local/src/mh/mh-svn# grep -r IPLD code/
> >> gargamel:/var/local/src/mh/mh-svn# 
> > 
> > it's also unclear where I'm supposed to put that file that I guess
> > I'm supposed to create.
> 
> That's a much more basic question.  I think that there are basic docs 
> somewhere that discuss creating your own user code directory, etc.  It 
> has nothing to do w/ insteon as it's a generic mh getting started concept.

Gotcha. I'll go find those first.

> > "In your user code directory also create ~mh/code/insteon.pl:"
> > ok, so I guess I'm supposed to make my own directory there, but
> > how does it get included/parsed?
> 
> You don't have to do that unless you know that you have something that 
> goes in it.  It's just an example for completeness.  Personally, I throw 
> *everything* in my items.mht file in the way of declarations. 
> Everything else (for me) ends up in special *.pl that are functional 
> (e.g., lighting.pl) not device centric (e.g., insteon.pl).  It's purely 
> up to you and what you are trying to accomplish.  My suggestion is to 
> start w/ just your items.mht and then make sure that your devices show 
> up in the web interface.  Then, move on to creating your own user code.
 
Will do, thanks.
 
> > "The PLM module is designed to interrogate every device at startup (not reload) so that the real device state is known and used to initialize the state value for each defined Insteon_Device."
> >>From this, it would seem that since I already configured 
> > Insteon_PLM_serial_port, mh should find all my switches and 
> > show them in its interface. Unfortunately, it does not.
> 
> I suppose that the above statement could be slightly misleading.  mh 
> does not discover each device and *then* interrogate every device.  It 
> only interrogates the devices that you've told it about.  Obviously, it 
> doesn't know anything if you haven't added entries into some *.mht file.

Thanks for explaining. I was under the impression that there was a way to
scan the bus and have all the devices report themselves. Sounds like I was
too optimistic :)
So, it's just a matter putting all the hex addresses in the right file, I'll
do that.

> > That page also says at the bottom
> > "INSTEON Extended Messages supported (for PLM)". What are those?
> 
> Newer insteon devices tend to use them.  Ignore it; only developers 
> should care.  Quite honestly, that entire section on controller 
> comparison should be deleted.

Ok. One reason I was looking at that is that I have the PLM but it won't
talk to my EZX10RF bridge, and it's a pain in the ass to program through its
single button interface.
It can be programmed through the PLC, but the docs still kind of warn
against using it, so I have a PLM, which then I can't use to easily program
the EZX10RF. I suppose I could buy one of each, but what's the status of the
PLC? Still a bad idea to buy today?

> >>From reading 
> > http://misterhouse.wikispaces.com/Insteon+Linking+and+Scenes
> > it seems to imply that I need to link a switch to my PLM using the
> > special procedure there.
> > That said, I can just ignore that and poll switch on/off status too,
> > right?
> 
> It is possible.  IMO, that approach is far more effort; but, up to you.

Understood, just confirming my understanding.

> > Also, last but not least
> > http://misterhouse.wikispaces.com/Insteon+Devices+-+Quirks+and+Hints#keypadlinc
> > explains how to manually configure some insteon devices in the config
> > file. So, is the config file half generated by a scan (which I haven't
> > gotten working yet),
> 
> no
 
Right, got that now.
 
Thanks for your answers,
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 & security ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/