From: Gregg L. <gr...@li...> - 2008-05-05 21:22:39
|
David Deutsch wrote: > Does that mean that I DO have to pair a SwitchLinc or button device? Only if you want to know that it is being locally controlled via it's button/paddle. In general, I think it is a good idea; and, it's trivial to do via mh w/o having to go around manually setting buttons, etc. > Or > like the InLine-Linc, can I connect and start to receive messages from > SwitchLincs as well? I ask this because I will have at least 250-300 > Insteon devices and would love to just record all their addresses in a > big table rather than go around pushing buttons :) Yep--I no longer push buttons to perform link management and instead exclusively use mh. > If you do have to "pair" such devices, wouldn't you also have to do the > InLinc for them to feedback the "status" to the PLM? It depends upon what you mean by status... If you want to get status via polling, then no pairing is required. If you want to receive a message the second that a paddle/button is touched, then yes--you have to pair. In addition, mh sees the dim started event and will poll the device for a status on stopping a locally initiated (i.e., human) dim. This means that mh will always know the exact light level that you might locally control. Now, I have no idea what the InlinLincs do--I'm assuming that they are simple, "passive" devices like LampLincs or ApplianceLincs where pairing (or reverse linking) isn't useful. BTW: Something that you didn't ask, but probably will (eventually) is: yes, it is possible to manage the linking between some KeypadLinc button (not the primary) and an InlineLinc via mh. For that matter, you can do n-way circuits from any controller and to any responder. Gregg |