From: <w20...@wo...> - 2009-04-26 16:06:33
|
Marc MERLIN wrote: > Just to make sure I get this. > > If I have some_lamp that is linked to 4 KPLs. > > Is the mh way to have some_lamp->set(ON) also switch the 4 KPLs, to make 4 > surrogates, one for each of the 4 KPLs buttons and then tie all 4 surrogates > to some_lamp? > Instead, can I now make a scene that sets my 4 KPL buttons, and tie that > single scene to some_lamp? > I understand you just need a MH scene defined that has all 4 KPLs and some_lamp in it. Then, you merely must use the scene instead of trying to turn on the lamp directly. You only need a surrogate if you want to control the button lights outside of any scene/All-Link that has that KPL button as a member. (Where it appears a surrogate is just an explicit scene/All-Link between the PLM and KP, and now we've gone full circle.) > I'm also confused as for the need to make PLM scenes just to talk to a KPL > button. > For a switchlink, it's an IPPL with one target: MAC:1 > For a KPL, it's an IPPL with 6 to 8 targets: MAC:1 to MAC:6-8 > KPL is like 8 switchlinks at the same address, so it needs 8 groups to identify which switch? Since the address is the same for them all, the only way to communicate with just one of them is by using the group (button number). > mh is able to do switchlink->set(ON) without having a predefined scene. > So, why would I need a predefined scene instead of being able to just do > KPLbut5->set(ON) (without surrogate scenes that is) > The set(ON) triggers an Insteon scene to turn on the device, and it doesn't accept a group. So you need to scene/All-link in place already to turn on that button. While the set(ON) could do some fancy work to map set(ON, button2) to a scene if one is defined or else always ensure that one is, it's just more logical to invoke the set(ON) on the scene? > Isn't a KPL just a switchlink with 6-8 targets (or initiators) inside? > > Does the Insteon protocol only allow directly setting target #1, but require > a scene to talk to targets 2 and above? > > Make sure to keep separate the Insteon protocol and the MH implementation of the engine. MH might be able to do this using DIRECT commands instead of scene all-link commands, but I don't know at which level of support it implements them. Maybe surrogate implements them or is the way around this. |