Re: [mh] encountered a nack message (sender_id_not_in_responder_aldb) for XXXX. It may be unplugged or have a burned out bulb

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

On Mon, Dec 03, 2012 at 09:58:34AM -0600, John wrote:
> If there is no technical reason to have up front stuff like linking inside
> mh, we should consider this not as a fall back, but as what we lead with.

There totally is. Mh benefits from knowing how devices are linked
because if you toggle A, and A is linked to B, the PLM will only know
that A changed.
However, because you configured the linking in MH, it knows that B also
toggled.
Once you've gone through that work of setting the relationships, you
might as well have mh keep all the links in sync too, well at least
until now when it doesn't work anymore :(

> An extreme approach would be an external app that uses xPL for
> control/response as well.
> This would also have advantage of being general solution for non-mh clients
> and therefore maybe have broader usage/contribution as well.

xPL just makes things harder in my experience.

On Mon, Dec 03, 2012 at 12:28:30PM -0700, Bauer, Steven J. wrote:
> Several other home automation venders appear to be going the route of supporting insteon via the use of an isy-99i/isy-994.  (http://cocoontech.com/forums/topic/11026-homeseer-drops-insteon-plugin-development/)

It is an option. I'm assuming they did fix their code to support the new
protocols.
I just don't know how well it'll integrate and sync with mh, and I'd
rather not depend on that thing to do all the things I currently do in
mh (actually I know it cannot/will not).

Has anyone integrated one both ways with mh (both ways = mh can control
insteon via ISY and ISY send device updates to mh) ?

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/