From: Mickey A. <mh...@ar...> - 2010-02-28 04:40:52
|
I hope I'm getting close to using a KPL to control X10 items (need $$$ to replace all my X10 with Insteon!) Here are the relevant entries in my MHT INSTEON_PLM, myPLM X10A, D5, couch_light, Down_Stairs|All_Lights|All_Devices, myPLM IPLL, 14.70.D4:01, Keypad8A, Down_Stairs|Kitchen|RemoteLink, myPLM IPLL, 14.70.D4:02, Keypad8B, Down_Stairs|Kitchen|RemoteLink, myPLM IPLL, 14.70.D4:03, Keypad8C, Down_Stairs|Kitchen|RemoteLink, myPLM IPLL, 14.70.D4:04, Keypad8D, Down_Stairs|Kitchen|RemoteLink, myPLM IPLL, 14.70.D4:05, Keypad8E, Down_Stairs|Kitchen|RemoteLink, myPLM IPLL, 14.70.D4:06, Keypad8F, Down_Stairs|Kitchen|RemoteLink, myPLM IPLL, 14.70.D4:07, Keypad8G, Down_Stairs|Kitchen|RemoteLink, myPLM IPLL, 14.70.D4:08, Keypad8H, Down_Stairs|Kitchen|RemoteLink, myPLM IPLL, myPLM:A0, surrogate_kpl_button_A, hidden, myPLM SCENE_MEMBER, Keypad8A, surrogate_kpl_button_A, surrogate IPLL, myPLM:A1, surrogate_kpl_button_B, hidden, myPLM SCENE_MEMBER, Keypad8B, surrogate_kpl_button_B, surrogate IPLL, myPLM:A2, surrogate_kpl_button_C, hidden, myPLM SCENE_MEMBER, Keypad8C, surrogate_kpl_button_C, surrogate IPLL, myPLM:A3, surrogate_kpl_button_D, hidden, myPLM SCENE_MEMBER, Keypad8D, surrogate_kpl_button_D, surrogate IPLL, myPLM:A4, surrogate_kpl_button_E, hidden, myPLM SCENE_MEMBER, Keypad8E, surrogate_kpl_button_E, surrogate IPLL, myPLM:A5, surrogate_kpl_button_F, hidden, myPLM SCENE_MEMBER, Keypad8F, surrogate_kpl_button_F, surrogate IPLL, myPLM:A6, surrogate_kpl_button_G, hidden, myPLM SCENE_MEMBER, Keypad8G, surrogate_kpl_button_G, surrogate IPLL, myPLM:A7, surrogate_kpl_button_H, hidden, myPLM SCENE_MEMBER, Keypad8H, surrogate_kpl_button_H, surrogate The (simplistic) code I am using to control and sync the keypad and the couch light is: if (state_now $Keypad8D eq ON) { print_log ("[Scene] Keypad 8 Couch button is now ON.\n") if $Debug{misc}; if (state $couch_light eq OFF){ print_log ("[Scene] Turning Couch light ON.\n") if $Debug{misc}; set $couch_light ON; } } if (state_now $couch_light eq ON) { print_log ("[Scene] Keypad 8 Couch button needs to be ON.\n") if $Debug{misc}; if (state $Keypad8D eq OFF) { print_log ("[Scene] Turning Keypad 8 D ON.\n") if $Debug{misc}; $Keypad8D->set(ON); } } if (state_now $Keypad8D eq OFF) { print_log ("[Scene] Keypad 8 Couch button is now OFF.\n") if $Debug{misc}; if (state $couch_light eq ON){ print_log ("[Scene] Turning Couch light OFF.\n") if $Debug{misc}; set $couch_light OFF; } } if (state_now $couch_light eq OFF) { print_log ("[Scene] Keypad 8 Couch button needs to be OFF.\n") if $Debug{misc}; if (state $Keypad8D eq ON){ print_log ("[Scene] Turning Keypad 8 D OFF.\n") if $Debug{misc}; $Keypad8D->set(OFF); } } Using Keypad8D , I can correctly turn on and off couch_light. The problem is when something else turns off couch_light, Keypad8D does not change. Here is the log file when Keypad8D is OFF and couch_light is turned on without the KPL (Insteon, X10, and Misc debugging turned on) 02/27/10 10:32:28 PM X10: Merged string data=XD5DJ 02/27/10 10:32:28 PM [Insteon_PLM] received x10 data: XDJ Running serial_data_buffer string: XD5DJ Serial data: event_type=X, event_data=XD5DJ X10: Previous units=D5 reset_flag=1 02/27/10 10:32:28 PM X10: Merged string data=XD5D5DJ 02/27/10 10:32:28 PM [Scene] Keypad 8 Couch button needs to be ON. 02/27/10 10:32:28 PM [Scene] Turning Keypad 8 D ON. 02/27/10 10:32:28 PM [Insteon_Device] $Keypad8D::set(on, ) 02/27/10 10:32:28 PM [Insteon_Device] $Keypad8D::set(on, ) Since I see the line [Scene] Turning Keypad 8 D ON, I know it is getting to $Keypad8D->set(ON);. I've also tried: set $Keypad8D ON; but that didn't have an effect on the keypad light. I've re-read the wiki several times and just can't see what I'm doing wrong. I made sure I was on the latest trunk code...anyone have an idea? Mickey Argo |
From: Marc M. <ma...@me...> - 2010-02-28 06:09:17
|
On Sat, Feb 27, 2010 at 10:40:43PM -0600, Mickey Argo wrote: > 02/27/10 10:32:28 PM X10: Merged string data=XD5DJ > 02/27/10 10:32:28 PM [Insteon_PLM] received x10 data: XDJ > Running serial_data_buffer string: XD5DJ > Serial data: event_type=X, event_data=XD5DJ > X10: Previous units=D5 reset_flag=1 > 02/27/10 10:32:28 PM X10: Merged string data=XD5D5DJ > 02/27/10 10:32:28 PM [Scene] Keypad 8 Couch button needs to be ON. > 02/27/10 10:32:28 PM [Scene] Turning Keypad 8 D ON. > 02/27/10 10:32:28 PM [Insteon_Device] $Keypad8D::set(on, ) > 02/27/10 10:32:28 PM [Insteon_Device] $Keypad8D::set(on, ) > > Since I see the line [Scene] Turning Keypad 8 D ON, I know it is getting > to $Keypad8D->set(ON);. I've also tried: > set $Keypad8D ON; but that didn't have an effect on the keypad light. > > I've re-read the wiki several times and just can't see what I'm doing > wrong. I made sure I was on the latest trunk code...anyone have an idea? I can't comment on surrogates, I never really got my head around using them :) I use http://misterhouse.wikispaces.com/Insteon+Devices+-+Quirks+and+Hints#KeypadLinc--Setting%20some_lamp%20and%20multiple%20KPLs%20with%20scenes along with $kitchen_kpl->tie_event('sync_kpl_lights($kitchen_kpl, $kitchen_kpls)'); # noloop This works for me (and is required because I have 4 KPLs and typically more than one LED to update when a device toggles). 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/ |
From: Daniel D. <da...@ma...> - 2010-03-07 16:04:32
|
Hello, The KPL light syncing is not working for me. It appears the Keypad Primer is missing a '}' in the sub sync_kpl_lights. Here is my debug output: 07/03/2010 10:29:17 MYLOGKPL: sync_kpl_lights called for state_changed on SCALAR(0x310fc40) to on for SCALAR(0x30f5648) set kpls in 1sec 07/03/2010 10:29:18 MYLOGKPL: sync_kpl_lights called for state_changed on SCALAR(0x30faf30) to 100% for SCALAR(0x355b610) set kpls in 1sec 07/03/2010 10:29:18 [Insteon_PLM] Prior cmd failed 07/03/2010 10:29:19 [Insteon_PLM] Prior cmd failed 07/03/2010 10:29:24 [Insteon_Device] WARN: queue timer on $Hall_KeyPad_scene_B expired. Attempting resend: on 07/03/2010 10:29:24 [Insteon_PLM] Prior cmd failed 07/03/2010 10:29:29 [Insteon_Device] WARN: queue timer on $Hall_KeyPad_scene_B expired. Trying next command if queued. and my kpl.pl: # repeat this line for all targets synced to kpls $Couch_Lamp->tie_event('sync_kpl_lights($Couch_Lamp, $Hall_KeyPad_scene_B)'); # noloop # this will get called every time a switch is toggled locally, or every # time you run get_status or on receipt of remote activations sub sync_kpl_lights { my ($ref_light, $kpl_scene) = @_; # avoid unnecessary traffic, like a get_status where status hasn't changed. if ($ref_light->state_changed) { print_log "MYLOGKPL: sync_kpl_lights called for state_changed on ".\ $ref_light->get_object_name." to ".$ref_light->state." for ".\ $kpl_scene->get_object_name." set kpls in 1sec"; # delay is to avoid collisions. In case we're in this code path # due to a remote toggle instead (you pushed the switch), that switch # could already be running a scene and you don't want to conflict with it # (for local state changes, this is not an issue). $kpl_scene->set_with_timer('', 1, $ref_light->state); } } and my insteon.mht: INSTEON_PLM, PLM # some_lamp_kpl_scene is then created to toggle both some_lamp and relevant KPL button(s) SCENE_MEMBER, Couch_Lamp, Hall_PadB, 100%, 0.1s # and the matching KPL button (you can list more than one) SCENE_MEMBER, Hall_PadB, Hall_KeyPad_scene_B SCENE_MEMBER, Couch_Lamp, Hall_KeyPad_scene_B IPLL, 07.E9.0B:01, Hall_Pad, buttons , PLM IPLL, 07.E9.0B:02, Hall_PadA, buttons , PLM IPLL, 07.E9.0B:03, Hall_PadB, buttons , PLM IPLL, 07.E9.0B:04, Hall_PadC, buttons , PLM IPLL, 07.E9.0B:05, Hall_PadD, buttons , PLM Any ideas? Thanks, Dan On 02/28/2010 01:09 AM, Marc MERLIN wrote: > On Sat, Feb 27, 2010 at 10:40:43PM -0600, Mickey Argo wrote: >> 02/27/10 10:32:28 PM X10: Merged string data=XD5DJ >> 02/27/10 10:32:28 PM [Insteon_PLM] received x10 data: XDJ >> Running serial_data_buffer string: XD5DJ >> Serial data: event_type=X, event_data=XD5DJ >> X10: Previous units=D5 reset_flag=1 >> 02/27/10 10:32:28 PM X10: Merged string data=XD5D5DJ >> 02/27/10 10:32:28 PM [Scene] Keypad 8 Couch button needs to be ON. >> 02/27/10 10:32:28 PM [Scene] Turning Keypad 8 D ON. >> 02/27/10 10:32:28 PM [Insteon_Device] $Keypad8D::set(on, ) >> 02/27/10 10:32:28 PM [Insteon_Device] $Keypad8D::set(on, ) >> >> Since I see the line [Scene] Turning Keypad 8 D ON, I know it is getting >> to $Keypad8D->set(ON);. I've also tried: >> set $Keypad8D ON; but that didn't have an effect on the keypad light. >> >> I've re-read the wiki several times and just can't see what I'm doing >> wrong. I made sure I was on the latest trunk code...anyone have an idea? > > I can't comment on surrogates, I never really got my head around using them > :) > > I use > http://misterhouse.wikispaces.com/Insteon+Devices+-+Quirks+and+Hints#KeypadLinc--Setting%20some_lamp%20and%20multiple%20KPLs%20with%20scenes > along with > $kitchen_kpl->tie_event('sync_kpl_lights($kitchen_kpl, $kitchen_kpls)'); # noloop > > This works for me (and is required because I have 4 KPLs and typically more > than one LED to update when a device toggles). > > Marc |
From: Marc M. <ma...@me...> - 2010-03-07 16:30:51
|
On Sun, Mar 07, 2010 at 10:40:34AM -0500, Daniel Durgin wrote: > Hello, > > The KPL light syncing is not working for me. It appears the Keypad > Primer is missing a '}' in the sub sync_kpl_lights. You are correct, I just fixed the page, thank you. > Here is my debug output: > 07/03/2010 10:29:17 MYLOGKPL: sync_kpl_lights called for state_changed > on SCALAR(0x310fc40) to on for SCALAR(0x30f5648) set kpls in 1sec > 07/03/2010 10:29:18 MYLOGKPL: sync_kpl_lights called for state_changed > on SCALAR(0x30faf30) to 100% for SCALAR(0x355b610) set kpls in 1sec Mmmh, that doesn't look right. I get: 06/03/2010 23:24:12 MYLOGKPL: sync_kpl_lights called for state_changed on $br2_sw to on for $br2_sw_kpls set kpls in 1sec that said it seems like a display problem only. > 07/03/2010 10:29:18 [Insteon_PLM] Prior cmd failed > 07/03/2010 10:29:19 [Insteon_PLM] Prior cmd failed > 07/03/2010 10:29:24 [Insteon_Device] WARN: queue timer on > $Hall_KeyPad_scene_B expired. Attempting resend: on > 07/03/2010 10:29:24 [Insteon_PLM] Prior cmd failed > 07/03/2010 10:29:29 [Insteon_Device] WARN: queue timer on > $Hall_KeyPad_scene_B expired. Trying next command if queued. but it looks like the command is actually being sent (i.e. $kpl_scene->set_with_timer('', 1, $ref_light->state); is doing its job, but the command isn't reaching the KPL). Looking at your data it looks like you are trying to send the command to a KPL button directly. You can't do that, you can only send it to a scene that the button is part of. Let me demonstrate: $entryway->tie_event('sync_kpl_lights($entryway, $entryway_kpls)'); # noloop IPLL, PLM:54, entryway_kpls, kpl_tie_scenes, PLM SCENE_MEMBER, fmr_kpl_entryway, entryway_kpls SCENE_MEMBER, kitchen_kpl_entryway, entryway_kpls SCENE_MEMBER, dining_kpl_entryway, entryway_kpls SCENE_MEMBER, lvr_kpl_entryway, entryway_kpls In other words, your target has to be a PLM scene defined with IPLL Marc > > > and my kpl.pl: > > # repeat this line for all targets synced to kpls > $Couch_Lamp->tie_event('sync_kpl_lights($Couch_Lamp, > $Hall_KeyPad_scene_B)'); # noloop > > # this will get called every time a switch is toggled locally, or every > # time you run get_status or on receipt of remote activations > > sub sync_kpl_lights > { > my ($ref_light, $kpl_scene) = @_; > # avoid unnecessary traffic, like a get_status where status hasn't > changed. > if ($ref_light->state_changed) { > print_log "MYLOGKPL: sync_kpl_lights called for state_changed > on ".\ > $ref_light->get_object_name." to ".$ref_light->state." for ".\ > $kpl_scene->get_object_name." set kpls in 1sec"; > # delay is to avoid collisions. In case we're in this code path > # due to a remote toggle instead (you pushed the switch), that > switch > # could already be running a scene and you don't want to > conflict with it > # (for local state changes, this is not an issue). > $kpl_scene->set_with_timer('', 1, $ref_light->state); > } > } > > > > and my insteon.mht: > INSTEON_PLM, PLM > > > # some_lamp_kpl_scene is then created to toggle both some_lamp and > relevant KPL button(s) > SCENE_MEMBER, Couch_Lamp, Hall_PadB, 100%, > 0.1s > # and the matching KPL button (you can list more than one) > SCENE_MEMBER, Hall_PadB, Hall_KeyPad_scene_B > SCENE_MEMBER, Couch_Lamp, Hall_KeyPad_scene_B > > > > IPLL, 07.E9.0B:01, Hall_Pad, buttons , PLM > IPLL, 07.E9.0B:02, Hall_PadA, buttons , PLM > IPLL, 07.E9.0B:03, Hall_PadB, buttons , PLM > IPLL, 07.E9.0B:04, Hall_PadC, buttons , PLM > IPLL, 07.E9.0B:05, Hall_PadD, buttons , PLM > > > > Any ideas? > > Thanks, > Dan > > > On 02/28/2010 01:09 AM, Marc MERLIN wrote: > > On Sat, Feb 27, 2010 at 10:40:43PM -0600, Mickey Argo wrote: > >> 02/27/10 10:32:28 PM X10: Merged string data=XD5DJ > >> 02/27/10 10:32:28 PM [Insteon_PLM] received x10 data: XDJ > >> Running serial_data_buffer string: XD5DJ > >> Serial data: event_type=X, event_data=XD5DJ > >> X10: Previous units=D5 reset_flag=1 > >> 02/27/10 10:32:28 PM X10: Merged string data=XD5D5DJ > >> 02/27/10 10:32:28 PM [Scene] Keypad 8 Couch button needs to be ON. > >> 02/27/10 10:32:28 PM [Scene] Turning Keypad 8 D ON. > >> 02/27/10 10:32:28 PM [Insteon_Device] $Keypad8D::set(on, ) > >> 02/27/10 10:32:28 PM [Insteon_Device] $Keypad8D::set(on, ) > >> > >> Since I see the line [Scene] Turning Keypad 8 D ON, I know it is getting > >> to $Keypad8D->set(ON);. I've also tried: > >> set $Keypad8D ON; but that didn't have an effect on the keypad light. > >> > >> I've re-read the wiki several times and just can't see what I'm doing > >> wrong. I made sure I was on the latest trunk code...anyone have an idea? > > > > I can't comment on surrogates, I never really got my head around using them > > :) > > > > I use > > http://misterhouse.wikispaces.com/Insteon+Devices+-+Quirks+and+Hints#KeypadLinc--Setting%20some_lamp%20and%20multiple%20KPLs%20with%20scenes > > along with > > $kitchen_kpl->tie_event('sync_kpl_lights($kitchen_kpl, $kitchen_kpls)'); # noloop > > > > This works for me (and is required because I have 4 KPLs and typically more > > than one LED to update when a device toggles). -- "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/ |
From: Daniel D. <da...@ma...> - 2010-03-09 15:33:11
|
Hi Marc, Thank you for the continued help. In the code : sub sync_kpl_lights { my ($ref_light, $kpl_scene) = @_; # avoid unnecessary traffic, like a get_status where status hasn't changed. if ($ref_light->state_changed) { print_log "MYLOGKPL: sync_kpl_lights called for state_changed on ".\ $ref_light->get_object_name." to ".$ref_light->state." for ".\ $kpl_scene->get_object_name." set kpls in 1sec"; # delay is to avoid collisions. In case we're in this code path # due to a remote toggle instead (you pushed the switch), that switch # could already be running a scene and you don't want to conflict with it # (for local state changes, this is not an issue). $kpl_scene->set_with_timer('', 1, $ref_light->state); } } If I remove the refence to the variables , ie \$ref_light->get_object_name becomes $ref_light->get_object_name, I get the following output: MYLOGKPL: sync_kpl_lights called for state_changed on $Den_Light to on for $HallKeyPadD_Scene set kpls in 1sec So I wonder if I have some issue with perl. I have a file called keypads.pl in my code directory where the function is stored. Should the sub routine go in a .mht file? Thanks Dan On 03/07/2010 11:30 AM, Marc MERLIN wrote: > On Sun, Mar 07, 2010 at 10:40:34AM -0500, Daniel Durgin wrote: >> Hello, >> >> The KPL light syncing is not working for me. It appears the Keypad >> Primer is missing a '}' in the sub sync_kpl_lights. > > You are correct, I just fixed the page, thank you. > >> Here is my debug output: >> 07/03/2010 10:29:17 MYLOGKPL: sync_kpl_lights called for state_changed >> on SCALAR(0x310fc40) to on for SCALAR(0x30f5648) set kpls in 1sec >> 07/03/2010 10:29:18 MYLOGKPL: sync_kpl_lights called for state_changed >> on SCALAR(0x30faf30) to 100% for SCALAR(0x355b610) set kpls in 1sec > > Mmmh, that doesn't look right. I get: > 06/03/2010 23:24:12 MYLOGKPL: sync_kpl_lights called for state_changed on $br2_sw to on for $br2_sw_kpls set kpls in 1sec > that said it seems like a display problem only. > >> 07/03/2010 10:29:18 [Insteon_PLM] Prior cmd failed >> 07/03/2010 10:29:19 [Insteon_PLM] Prior cmd failed >> 07/03/2010 10:29:24 [Insteon_Device] WARN: queue timer on >> $Hall_KeyPad_scene_B expired. Attempting resend: on >> 07/03/2010 10:29:24 [Insteon_PLM] Prior cmd failed >> 07/03/2010 10:29:29 [Insteon_Device] WARN: queue timer on >> $Hall_KeyPad_scene_B expired. Trying next command if queued. > > but it looks like the command is actually being sent (i.e. > $kpl_scene->set_with_timer('', 1, $ref_light->state); > is doing its job, but the command isn't reaching the KPL). > > Looking at your data it looks like you are trying to send the command to a > KPL button directly. You can't do that, you can only send it to a scene that > the button is part of. > > Let me demonstrate: > $entryway->tie_event('sync_kpl_lights($entryway, $entryway_kpls)'); # noloop > > IPLL, PLM:54, entryway_kpls, kpl_tie_scenes, PLM > SCENE_MEMBER, fmr_kpl_entryway, entryway_kpls > SCENE_MEMBER, kitchen_kpl_entryway, entryway_kpls > SCENE_MEMBER, dining_kpl_entryway, entryway_kpls > SCENE_MEMBER, lvr_kpl_entryway, entryway_kpls > > In other words, your target has to be a PLM scene defined with IPLL > > Marc > >> >> >> and my kpl.pl: >> >> # repeat this line for all targets synced to kpls >> $Couch_Lamp->tie_event('sync_kpl_lights($Couch_Lamp, >> $Hall_KeyPad_scene_B)'); # noloop >> >> # this will get called every time a switch is toggled locally, or every >> # time you run get_status or on receipt of remote activations >> >> sub sync_kpl_lights >> { >> my ($ref_light, $kpl_scene) = @_; >> # avoid unnecessary traffic, like a get_status where status hasn't >> changed. >> if ($ref_light->state_changed) { >> print_log "MYLOGKPL: sync_kpl_lights called for state_changed >> on ".\ >> $ref_light->get_object_name." to ".$ref_light->state." for ".\ >> $kpl_scene->get_object_name." set kpls in 1sec"; >> # delay is to avoid collisions. In case we're in this code path >> # due to a remote toggle instead (you pushed the switch), that >> switch >> # could already be running a scene and you don't want to >> conflict with it >> # (for local state changes, this is not an issue). >> $kpl_scene->set_with_timer('', 1, $ref_light->state); >> } >> } >> >> >> >> and my insteon.mht: >> INSTEON_PLM, PLM >> >> >> # some_lamp_kpl_scene is then created to toggle both some_lamp and >> relevant KPL button(s) >> SCENE_MEMBER, Couch_Lamp, Hall_PadB, 100%, >> 0.1s >> # and the matching KPL button (you can list more than one) >> SCENE_MEMBER, Hall_PadB, Hall_KeyPad_scene_B >> SCENE_MEMBER, Couch_Lamp, Hall_KeyPad_scene_B >> >> >> >> IPLL, 07.E9.0B:01, Hall_Pad, buttons , PLM >> IPLL, 07.E9.0B:02, Hall_PadA, buttons , PLM >> IPLL, 07.E9.0B:03, Hall_PadB, buttons , PLM >> IPLL, 07.E9.0B:04, Hall_PadC, buttons , PLM >> IPLL, 07.E9.0B:05, Hall_PadD, buttons , PLM >> >> >> >> Any ideas? >> >> Thanks, >> Dan >> >> >> On 02/28/2010 01:09 AM, Marc MERLIN wrote: >>> On Sat, Feb 27, 2010 at 10:40:43PM -0600, Mickey Argo wrote: >>>> 02/27/10 10:32:28 PM X10: Merged string data=XD5DJ >>>> 02/27/10 10:32:28 PM [Insteon_PLM] received x10 data: XDJ >>>> Running serial_data_buffer string: XD5DJ >>>> Serial data: event_type=X, event_data=XD5DJ >>>> X10: Previous units=D5 reset_flag=1 >>>> 02/27/10 10:32:28 PM X10: Merged string data=XD5D5DJ >>>> 02/27/10 10:32:28 PM [Scene] Keypad 8 Couch button needs to be ON. >>>> 02/27/10 10:32:28 PM [Scene] Turning Keypad 8 D ON. >>>> 02/27/10 10:32:28 PM [Insteon_Device] $Keypad8D::set(on, ) >>>> 02/27/10 10:32:28 PM [Insteon_Device] $Keypad8D::set(on, ) >>>> >>>> Since I see the line [Scene] Turning Keypad 8 D ON, I know it is getting >>>> to $Keypad8D->set(ON);. I've also tried: >>>> set $Keypad8D ON; but that didn't have an effect on the keypad light. >>>> >>>> I've re-read the wiki several times and just can't see what I'm doing >>>> wrong. I made sure I was on the latest trunk code...anyone have an idea? >>> >>> I can't comment on surrogates, I never really got my head around using them >>> :) >>> >>> I use >>> http://misterhouse.wikispaces.com/Insteon+Devices+-+Quirks+and+Hints#KeypadLinc--Setting%20some_lamp%20and%20multiple%20KPLs%20with%20scenes >>> along with >>> $kitchen_kpl->tie_event('sync_kpl_lights($kitchen_kpl, $kitchen_kpls)'); # noloop >>> >>> This works for me (and is required because I have 4 KPLs and typically more >>> than one LED to update when a device toggles). |
From: Marc M. <ma...@me...> - 2010-03-09 17:14:40
|
On Tue, Mar 09, 2010 at 10:32:59AM -0500, Daniel Durgin wrote: > Hi Marc, > > Thank you for the continued help. > > In the code : > > sub sync_kpl_lights > { > my ($ref_light, $kpl_scene) = @_; > # avoid unnecessary traffic, like a get_status where status hasn't > changed. > if ($ref_light->state_changed) { > print_log "MYLOGKPL: sync_kpl_lights called for state_changed > on ".\ > $ref_light->get_object_name." to ".$ref_light->state." for ".\ > $kpl_scene->get_object_name." set kpls in 1sec"; > # delay is to avoid collisions. In case we're in this code path > # due to a remote toggle instead (you pushed the switch), that > switch > # could already be running a scene and you don't want to > conflict with it > # (for local state changes, this is not an issue). > $kpl_scene->set_with_timer('', 1, $ref_light->state); > } > } > > If I remove the refence to the variables , ie > \$ref_light->get_object_name becomes $ref_light->get_object_name, I get > the following output: > MYLOGKPL: sync_kpl_lights called for state_changed on $Den_Light to on > for $HallKeyPadD_Scene set kpls in 1sec Oh my. \ was meant to say "truncated line", not reference. My code was actually print_log "MYLOGKPL: sync_kpl_lights called for state_changed on ".$ref_light->get_object_name." to ".$ref_light->state." for ".$kpl_scene->get_object_name." set kpls in 1sec"; I've modified the page to remove \ which indeed is confusing. Thanks, 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/ |
From: Daniel D. <da...@ma...> - 2010-03-09 17:26:10
|
Hi Marc, So I am getting the following problem when I change 09/03/2010 12:19:25 [Insteon_Device] WARN: queue timer on $HallKeyPadC_Scene expired. Trying next command if queued. 09/03/2010 12:19:26 [Insteon_Device] WARN: queue timer on $HallKeyPadD_Scene expired. Attempting resend: on 09/03/2010 12:19:26 [Insteon_PLM] Prior cmd failed Originally, I manually linked the keypadlinc to the device. Would this cause a problem? On 03/09/2010 12:14 PM, Marc MERLIN wrote: > On Tue, Mar 09, 2010 at 10:32:59AM -0500, Daniel Durgin wrote: >> Hi Marc, >> >> Thank you for the continued help. >> >> In the code : >> >> sub sync_kpl_lights >> { >> my ($ref_light, $kpl_scene) = @_; >> # avoid unnecessary traffic, like a get_status where status hasn't >> changed. >> if ($ref_light->state_changed) { >> print_log "MYLOGKPL: sync_kpl_lights called for state_changed >> on ".\ >> $ref_light->get_object_name." to ".$ref_light->state." for ".\ >> $kpl_scene->get_object_name." set kpls in 1sec"; >> # delay is to avoid collisions. In case we're in this code path >> # due to a remote toggle instead (you pushed the switch), that >> switch >> # could already be running a scene and you don't want to >> conflict with it >> # (for local state changes, this is not an issue). >> $kpl_scene->set_with_timer('', 1, $ref_light->state); >> } >> } >> >> If I remove the refence to the variables , ie >> \$ref_light->get_object_name becomes $ref_light->get_object_name, I get >> the following output: >> MYLOGKPL: sync_kpl_lights called for state_changed on $Den_Light to on >> for $HallKeyPadD_Scene set kpls in 1sec > > Oh my. \ was meant to say "truncated line", not reference. > My code was actually > print_log "MYLOGKPL: sync_kpl_lights called for state_changed on ".$ref_light->get_object_name." to ".$ref_light->state." for ".$kpl_scene->get_object_name." set kpls in 1sec"; > > I've modified the page to remove \ which indeed is confusing. > > Thanks, > Marc |
From: Marc M. <ma...@me...> - 2010-03-09 17:47:17
|
On Tue, Mar 09, 2010 at 12:26:01PM -0500, Daniel Durgin wrote: > Hi Marc, > > So I am getting the following problem when I change > > 09/03/2010 12:19:25 [Insteon_Device] WARN: queue timer on > $HallKeyPadC_Scene expired. Trying next command if queued. > 09/03/2010 12:19:26 [Insteon_Device] WARN: queue timer on > $HallKeyPadD_Scene expired. Attempting resend: on > 09/03/2010 12:19:26 [Insteon_PLM] Prior cmd failed Ok, you clearly need to get that $HallKeyPadD_Scene scene working. > Originally, I manually linked the keypadlinc to the device. Would this > cause a problem? No. Links between devices should not affect PLM scenes. But back to your PLM scene, you should again try to get it synced with the PLM and get your scene to work first from the web interface before you can hope to get it tied. Also, if you 'scan all links' on the PLM, you should see your scene in there. If not, you have a problem that you need to fix before you can proceed. 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/ |
From: Daniel D. <da...@ma...> - 2010-03-09 19:44:35
|
Hi Marc, If I Sync all links: 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_PadB (1 of 16) 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_PadD (2 of 16) 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Den_Light (3 of 16) 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Den_Light_Slave (4 of 16) 09/03/2010 14:34:15 [Sync all links] Now syncing links: $HallKeyPadC_Scene (5 of 16) 09/03/2010 14:34:15 [Sync all links] Now syncing links: $FF_Small_Bdroom (6 of 16) 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_Pad (7 of 16) 09/03/2010 14:34:15 [Sync all links] Now syncing links: $come_home_scene (8 of 16) 09/03/2010 14:34:15 [Sync all links] Now syncing links: $HallKeyPadB_Scene (9 of 16) 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Dining_Table (10 of 16) 09/03/2010 14:34:15 [Sync all links] Now syncing links: $HallKeyPadD_Scene (11 of 16) 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Garage_Int_Lights (12 of 16) 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_PadC (13 of 16) 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_PadA (14 of 16) 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Sink_Lights (15 of 16) 09/03/2010 14:34:15 [Sync all links] Now syncing links: $HallKeyPadA_Scene (16 of 16 If I Scan all link tables: 09/03/2010 14:41:03 [Scan all link tables] Now scanning: $PLM (1 of 9) 09/03/2010 14:41:06 [Scan all link tables] Now scanning: $Couch_Lamp (2 of 9) 09/03/2010 14:41:06 [Insteon_Device] $Couch_Lamp accessing memory at location: 0x0FF8 09/03/2010 14:41:10 MYLOGKPL: sync_kpl_lights called for state_changed on $Couch_Lamp to peek for $HallKeyPadA_Scene set kpls in 1sec 09/03/2010 14:41:11 [Insteon_PLM] Prior cmd failed 09/03/2010 14:41:14 [Insteon_Device] WARN: queue timer on $Couch_Lamp expired. Attempting resend: peek 09/03/2010 14:41:15 [Insteon_Device] $Couch_Lamp accessing memory at location: 0x0FF0 09/03/2010 14:41:16 [Scan all link tables] Now scanning: $Den_Light (3 of 9) 09/03/2010 14:41:16 [Insteon_Device] $Den_Light accessing memory at location: 0x0FF8 09/03/2010 14:41:16 [Insteon_Device] WARN: queue timer on $HallKeyPadA_Scene expired. Attempting resend: on 09/03/2010 14:41:16 [Insteon_PLM] Prior cmd failed 09/03/2010 14:41:20 [Insteon_Device] $Den_Light accessing memory at location: 0x0FF0 09/03/2010 14:41:21 [Insteon_Device] WARN: queue timer on $HallKeyPadA_Scene expired. Attempting resend: on 09/03/2010 14:41:21 [Insteon_PLM] Prior cmd failed 09/03/2010 14:41:24 [Insteon_Device] $Den_Light accessing memory at location: 0x0FE8 09/03/2010 14:41:26 [Insteon_Device] WARN: queue timer on $HallKeyPadA_Scene expired. Trying next command if queued. 09/03/2010 14:41:28 [Insteon_Device] $Den_Light accessing memory at location: 0x0FE0 09/03/2010 14:41:32 [Insteon_Device] $Den_Light accessing memory at location: 0x0FD8 09/03/2010 14:41:33 [Scan all link tables] Now scanning: $Den_Light_Slave (4 of 9) 09/03/2010 14:41:33 [Insteon_Device] $Den_Light_Slave accessing memory at location: 0x0FF8 09/03/2010 14:41:37 [Insteon_Device] $Den_Light_Slave accessing memory at location: 0x0FF0 09/03/2010 14:41:41 [Insteon_Device] $Den_Light_Slave accessing memory at location: 0x0FE8 09/03/2010 14:41:45 [Insteon_Device] $Den_Light_Slave accessing memory at location: 0x0FE0 09/03/2010 14:41:46 [Scan all link tables] Now scanning: $FF_Small_Bdroom (5 of 9) 09/03/2010 14:41:46 [Insteon_Device] $FF_Small_Bdroom accessing memory at location: 0x0FF8 09/03/2010 14:41:50 [Insteon_Device] $FF_Small_Bdroom accessing memory at location: 0x0FF0 09/03/2010 14:41:54 [Insteon_Device] $FF_Small_Bdroom accessing memory at location: 0x0FE8 09/03/2010 14:41:55 [Scan all link tables] Now scanning: $Hall_Pad (6 of 9) 09/03/2010 14:41:55 [Insteon_Device] $Hall_Pad accessing memory at location: 0x0FF8 09/03/2010 14:41:59 [Insteon_Device] $Hall_Pad accessing memory at location: 0x0FF0 09/03/2010 14:42:00 : Saving object states ... done 09/03/2010 14:42:03 [Insteon_Device] $Hall_Pad accessing memory at location: 0x0FE8 09/03/2010 14:42:07 [Insteon_Device] $Hall_Pad accessing memory at location: 0x0FE0 09/03/2010 14:42:11 [Insteon_Device] $Hall_Pad accessing memory at location: 0x0FD8 09/03/2010 14:42:15 [Insteon_Device] $Hall_Pad accessing memory at location: 0x0FD0 09/03/2010 14:42:19 [Insteon_Device] $Hall_Pad accessing memory at location: 0x0FC8 09/03/2010 14:42:23 [Insteon_Device] $Hall_Pad accessing memory at location: 0x0FC0 09/03/2010 14:42:27 [Insteon_Device] $Hall_Pad accessing memory at location: 0x0FB8 09/03/2010 14:42:31 [Insteon_Device] $Hall_Pad accessing memory at location: 0x0FB0 09/03/2010 14:42:35 [Insteon_Device] $Hall_Pad accessing memory at location: 0x0FA8 09/03/2010 14:42:40 [Insteon_Device] $Hall_Pad accessing memory at location: 0x0FA0 09/03/2010 14:42:44 [Insteon_Device] $Hall_Pad accessing memory at location: 0x0F98 09/03/2010 14:42:48 [Insteon_Device] $Hall_Pad accessing memory at location: 0x0F90 09/03/2010 14:42:49 [Scan all link tables] Now scanning: $Dining_Table (7 of 9) 09/03/2010 14:42:49 [Insteon_Device] $Dining_Table accessing memory at location: 0x0FF8 09/03/2010 14:42:53 [Insteon_Device] $Dining_Table accessing memory at location: 0x0FF0 09/03/2010 14:42:53 [Scan all link tables] Now scanning: $Garage_Int_Lights (8 of 9) 09/03/2010 14:42:53 [Insteon_Device] $Garage_Int_Lights accessing memory at location: 0x0FF8 09/03/2010 14:42:58 [Insteon_Device] $Garage_Int_Lights accessing memory at location: 0x0FF0 09/03/2010 14:43:00 : Saving object states ... done 09/03/2010 14:43:02 [Insteon_Device] $Garage_Int_Lights accessing memory at location: 0x0FE8 09/03/2010 14:43:03 [Scan all link tables] Now scanning: $Sink_Lights (9 of 9) 09/03/2010 14:43:03 [Insteon_Device] $Sink_Lights accessing memory at location: 0x0FF8 09/03/2010 14:43:07 [Insteon_Device] $Sink_Lights accessing memory at location: 0x0FF0 09/03/2010 14:43:11 [Insteon_Device] $Sink_Lights accessing memory at location: 0x0FE8 09/03/2010 14:43:15 [Insteon_Device] $Sink_Lights accessing memory at location: 0x0FE0 So I must have done something wrong. Any suggestions? -Dan On 03/09/2010 12:47 PM, Marc MERLIN wrote: > On Tue, Mar 09, 2010 at 12:26:01PM -0500, Daniel Durgin wrote: >> Hi Marc, >> >> So I am getting the following problem when I change >> >> 09/03/2010 12:19:25 [Insteon_Device] WARN: queue timer on >> $HallKeyPadC_Scene expired. Trying next command if queued. >> 09/03/2010 12:19:26 [Insteon_Device] WARN: queue timer on >> $HallKeyPadD_Scene expired. Attempting resend: on >> 09/03/2010 12:19:26 [Insteon_PLM] Prior cmd failed > > Ok, you clearly need to get that $HallKeyPadD_Scene scene working. > >> Originally, I manually linked the keypadlinc to the device. Would this >> cause a problem? > > No. Links between devices should not affect PLM scenes. > > But back to your PLM scene, you should again try to get it synced with the > PLM and get your scene to work first from the web interface before you can > hope to get it tied. > > Also, if you 'scan all links' on the PLM, you should see your scene in > there. If not, you have a problem that you need to fix before you can > proceed. > > Marc |
From: Marc M. <ma...@me...> - 2010-03-10 07:02:39
|
[I hand editted your Email to paste back the lines together. Do your best to provide unsplit log lines, split ones are quit ehard to read] On Tue, Mar 09, 2010 at 02:44:26PM -0500, Daniel Durgin wrote: > Hi Marc, > > If I Sync all links: > 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_PadB (1 of 16) > 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_PadD (2 of 16) > 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Den_Light (3 of 16) > 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Den_Light_Slave (4 of 16) > 09/03/2010 14:34:15 [Sync all links] Now syncing links: $HallKeyPadC_Scene (5 of 16) > 09/03/2010 14:34:15 [Sync all links] Now syncing links: $FF_Small_Bdroom (6 of 16) > 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_Pad (7 of 16) > 09/03/2010 14:34:15 [Sync all links] Now syncing links: $come_home_scene (8 of 16) > 09/03/2010 14:34:15 [Sync all links] Now syncing links: $HallKeyPadB_Scene (9 of 16) > 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Dining_Table (10 of 16) > 09/03/2010 14:34:15 [Sync all links] Now syncing links: $HallKeyPadD_Scene (11 of 16) > 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Garage_Int_Lights (12 of 16) > 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_PadC (13 of 16) > 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_PadA (14 of 16) > 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Sink_Lights (15 of 16) > 09/03/2010 14:34:15 [Sync all links] Now syncing links: $HallKeyPadA_Scene (16 of 16 If you'r going to do your entire network, it's good to scan first and than sync although Im' not sure it was a problem here. > If I Scan all link tables: I mean scan link table in the PLM drop down. Now you are indeed right that 'sync links' should be done in the scene drop down. Apparently sync all doesn't since scene links to the PLM though. So try this: 1) (re) sync all your scenes 2) scan links on the PLM to see if it worked. 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/ |
From: Marc M. <ma...@me...> - 2010-03-10 16:05:30
|
On Tue, Mar 09, 2010 at 11:02:31PM -0800, Marc MERLIN wrote: > [I hand editted your Email to paste back the lines together. Do your best to > provide unsplit log lines, split ones are quit ehard to read] > > On Tue, Mar 09, 2010 at 02:44:26PM -0500, Daniel Durgin wrote: > > Hi Marc, > > > > If I Sync all links: > > 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_PadB (1 of 16) > > 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_PadD (2 of 16) > > 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Den_Light (3 of 16) > > 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Den_Light_Slave (4 of 16) > > 09/03/2010 14:34:15 [Sync all links] Now syncing links: $HallKeyPadC_Scene (5 of 16) > > 09/03/2010 14:34:15 [Sync all links] Now syncing links: $FF_Small_Bdroom (6 of 16) > > 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_Pad (7 of 16) > > 09/03/2010 14:34:15 [Sync all links] Now syncing links: $come_home_scene (8 of 16) > > 09/03/2010 14:34:15 [Sync all links] Now syncing links: $HallKeyPadB_Scene (9 of 16) > > 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Dining_Table (10 of 16) > > 09/03/2010 14:34:15 [Sync all links] Now syncing links: $HallKeyPadD_Scene (11 of 16) > > 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Garage_Int_Lights (12 of 16) > > 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_PadC (13 of 16) > > 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_PadA (14 of 16) > > 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Sink_Lights (15 of 16) > > 09/03/2010 14:34:15 [Sync all links] Now syncing links: $HallKeyPadA_Scene (16 of 16 > > > If you'r going to do your entire network, it's good to scan first and than > sync although Im' not sure it was a problem here. > > > If I Scan all link tables: > > I mean scan link table in the PLM drop down. > > Now you are indeed right that 'sync links' should be done in the scene drop > down. Apparently sync all doesn't since scene links to the PLM though. > > So try this: > 1) (re) sync all your scenes > 2) scan links on the PLM to see if it worked. I also wrote some better instructions on how you're supposed to set and debug PLM scenes: http://misterhouse.wikispaces.com/Insteon#Insteon%20Specific%20Info-Insteon%20setup%20in%20MH-Scenes%20Explained-PLM%20Scenes-Programming/Troubleshooting%20PLM%20Scenes (whoa, I asked my friend at wikispaces to change their in document links not to be something useless and non permanent like #toc1, I guess they did that recently :) 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/ |
From: Daniel D. <da...@ma...> - 2010-03-11 14:50:40
|
Thank you for all the guidance. I finally got it working. Perhaps in my tired brain, I have a ten month old, I didn't see it spelled out. On the scene, initiate linking as controller, then press and hold button on keypad to complete link. -Dan On 03/10/2010 11:05 AM, Marc MERLIN wrote: > On Tue, Mar 09, 2010 at 11:02:31PM -0800, Marc MERLIN wrote: >> [I hand editted your Email to paste back the lines together. Do your best to >> provide unsplit log lines, split ones are quit ehard to read] >> >> On Tue, Mar 09, 2010 at 02:44:26PM -0500, Daniel Durgin wrote: >>> Hi Marc, >>> >>> If I Sync all links: >>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_PadB (1 of 16) >>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_PadD (2 of 16) >>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Den_Light (3 of 16) >>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Den_Light_Slave (4 of 16) >>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $HallKeyPadC_Scene (5 of 16) >>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $FF_Small_Bdroom (6 of 16) >>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_Pad (7 of 16) >>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $come_home_scene (8 of 16) >>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $HallKeyPadB_Scene (9 of 16) >>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Dining_Table (10 of 16) >>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $HallKeyPadD_Scene (11 of 16) >>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Garage_Int_Lights (12 of 16) >>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_PadC (13 of 16) >>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_PadA (14 of 16) >>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Sink_Lights (15 of 16) >>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $HallKeyPadA_Scene (16 of 16 >> >> >> If you'r going to do your entire network, it's good to scan first and than >> sync although Im' not sure it was a problem here. >> >>> If I Scan all link tables: >> >> I mean scan link table in the PLM drop down. >> >> Now you are indeed right that 'sync links' should be done in the scene drop >> down. Apparently sync all doesn't since scene links to the PLM though. >> >> So try this: >> 1) (re) sync all your scenes >> 2) scan links on the PLM to see if it worked. > > I also wrote some better instructions on how you're supposed to set and > debug PLM scenes: > http://misterhouse.wikispaces.com/Insteon#Insteon%20Specific%20Info-Insteon%20setup%20in%20MH-Scenes%20Explained-PLM%20Scenes-Programming/Troubleshooting%20PLM%20Scenes > > (whoa, I asked my friend at wikispaces to change their in document links not > to be something useless and non permanent like #toc1, I guess they did that > recently :) > > Marc |
From: Marc M. <ma...@me...> - 2010-03-11 16:46:18
|
On Thu, Mar 11, 2010 at 09:49:27AM -0500, Daniel Durgin wrote: > Thank you for all the guidance. I finally got it working. > > Perhaps in my tired brain, I have a ten month old, I didn't see it > spelled out. > > On the scene, initiate linking as controller, then press and hold button > on keypad to complete link. Glad you got it working. But 'Initiate linking as controller' should not be needed for a PLM scene AFAIK. I don't even remember using this function for anything other than my motion sensor IIRC. I think you just managed to get your links synced to the PLM around that time which is what made your PLM scene work. Either way, sounds like you're up and running now. Cheers, Marc > -Dan > > On 03/10/2010 11:05 AM, Marc MERLIN wrote: > > On Tue, Mar 09, 2010 at 11:02:31PM -0800, Marc MERLIN wrote: > >> [I hand editted your Email to paste back the lines together. Do your best to > >> provide unsplit log lines, split ones are quit ehard to read] > >> > >> On Tue, Mar 09, 2010 at 02:44:26PM -0500, Daniel Durgin wrote: > >>> Hi Marc, > >>> > >>> If I Sync all links: > >>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_PadB (1 of 16) > >>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_PadD (2 of 16) > >>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Den_Light (3 of 16) > >>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Den_Light_Slave (4 of 16) > >>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $HallKeyPadC_Scene (5 of 16) > >>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $FF_Small_Bdroom (6 of 16) > >>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_Pad (7 of 16) > >>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $come_home_scene (8 of 16) > >>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $HallKeyPadB_Scene (9 of 16) > >>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Dining_Table (10 of 16) > >>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $HallKeyPadD_Scene (11 of 16) > >>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Garage_Int_Lights (12 of 16) > >>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_PadC (13 of 16) > >>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_PadA (14 of 16) > >>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Sink_Lights (15 of 16) > >>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $HallKeyPadA_Scene (16 of 16 > >> > >> > >> If you'r going to do your entire network, it's good to scan first and than > >> sync although Im' not sure it was a problem here. > >> > >>> If I Scan all link tables: > >> > >> I mean scan link table in the PLM drop down. > >> > >> Now you are indeed right that 'sync links' should be done in the scene drop > >> down. Apparently sync all doesn't since scene links to the PLM though. > >> > >> So try this: > >> 1) (re) sync all your scenes > >> 2) scan links on the PLM to see if it worked. > > > > I also wrote some better instructions on how you're supposed to set and > > debug PLM scenes: > > http://misterhouse.wikispaces.com/Insteon#Insteon%20Specific%20Info-Insteon%20setup%20in%20MH-Scenes%20Explained-PLM%20Scenes-Programming/Troubleshooting%20PLM%20Scenes > > > > (whoa, I asked my friend at wikispaces to change their in document links not > > to be something useless and non permanent like #toc1, I guess they did that > > recently :) > > > > Marc > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > ________________________________________________________ > To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365 > -- "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/ |
From: Daniel D. <da...@ma...> - 2010-03-11 18:05:10
|
In the spirit of the scientific process... I tired it on the two remaining buttons. No Lights before I linked, but they worked afterward. This is a very new kpl, maybe things changed? -Dan On 03/11/2010 11:46 AM, Marc MERLIN wrote: > On Thu, Mar 11, 2010 at 09:49:27AM -0500, Daniel Durgin wrote: >> Thank you for all the guidance. I finally got it working. >> >> Perhaps in my tired brain, I have a ten month old, I didn't see it >> spelled out. >> >> On the scene, initiate linking as controller, then press and hold button >> on keypad to complete link. > > Glad you got it working. > > But 'Initiate linking as controller' should not be needed for a PLM scene > AFAIK. I don't even remember using this function for anything other than my > motion sensor IIRC. > > I think you just managed to get your links synced to the PLM around that time > which is what made your PLM scene work. > > Either way, sounds like you're up and running now. > > Cheers, > Marc > > >> -Dan >> >> On 03/10/2010 11:05 AM, Marc MERLIN wrote: >>> On Tue, Mar 09, 2010 at 11:02:31PM -0800, Marc MERLIN wrote: >>>> [I hand editted your Email to paste back the lines together. Do your best to >>>> provide unsplit log lines, split ones are quit ehard to read] >>>> >>>> On Tue, Mar 09, 2010 at 02:44:26PM -0500, Daniel Durgin wrote: >>>>> Hi Marc, >>>>> >>>>> If I Sync all links: >>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_PadB (1 of 16) >>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_PadD (2 of 16) >>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Den_Light (3 of 16) >>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Den_Light_Slave (4 of 16) >>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $HallKeyPadC_Scene (5 of 16) >>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $FF_Small_Bdroom (6 of 16) >>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_Pad (7 of 16) >>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $come_home_scene (8 of 16) >>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $HallKeyPadB_Scene (9 of 16) >>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Dining_Table (10 of 16) >>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $HallKeyPadD_Scene (11 of 16) >>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Garage_Int_Lights (12 of 16) >>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_PadC (13 of 16) >>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_PadA (14 of 16) >>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Sink_Lights (15 of 16) >>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $HallKeyPadA_Scene (16 of 16 >>>> >>>> >>>> If you'r going to do your entire network, it's good to scan first and than >>>> sync although Im' not sure it was a problem here. >>>> >>>>> If I Scan all link tables: >>>> >>>> I mean scan link table in the PLM drop down. >>>> >>>> Now you are indeed right that 'sync links' should be done in the scene drop >>>> down. Apparently sync all doesn't since scene links to the PLM though. >>>> >>>> So try this: >>>> 1) (re) sync all your scenes >>>> 2) scan links on the PLM to see if it worked. >>> >>> I also wrote some better instructions on how you're supposed to set and >>> debug PLM scenes: >>> http://misterhouse.wikispaces.com/Insteon#Insteon%20Specific%20Info-Insteon%20setup%20in%20MH-Scenes%20Explained-PLM%20Scenes-Programming/Troubleshooting%20PLM%20Scenes >>> >>> (whoa, I asked my friend at wikispaces to change their in document links not >>> to be something useless and non permanent like #toc1, I guess they did that >>> recently :) >>> >>> Marc >> >> ------------------------------------------------------------------------------ >> Download Intel® Parallel Studio Eval >> Try the new software tools for yourself. Speed compiling, find bugs >> proactively, and fine-tune applications for parallel performance. >> See why Intel Parallel Studio got high marks during beta. >> http://p.sf.net/sfu/intel-sw-dev >> ________________________________________________________ >> To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365 >> > |
From: Marc M. <ma...@me...> - 2010-03-11 18:38:10
|
On Thu, Mar 11, 2010 at 01:05:02PM -0500, Daniel Durgin wrote: > In the spirit of the scientific process... I tired it on the two > remaining buttons. No Lights before I linked, but they worked afterward. > > This is a very new kpl, maybe things changed? Gregg, does this make sense? Marc > On 03/11/2010 11:46 AM, Marc MERLIN wrote: > >On Thu, Mar 11, 2010 at 09:49:27AM -0500, Daniel Durgin wrote: > >>Thank you for all the guidance. I finally got it working. > >> > >>Perhaps in my tired brain, I have a ten month old, I didn't see it > >>spelled out. > >> > >>On the scene, initiate linking as controller, then press and hold button > >>on keypad to complete link. > > > >Glad you got it working. > > > >But 'Initiate linking as controller' should not be needed for a PLM scene > >AFAIK. I don't even remember using this function for anything other than my > >motion sensor IIRC. > > > >I think you just managed to get your links synced to the PLM around that > >time > >which is what made your PLM scene work. > > > >Either way, sounds like you're up and running now. > > > >Cheers, > >Marc > > > > > >>-Dan > >> > >>On 03/10/2010 11:05 AM, Marc MERLIN wrote: > >>>On Tue, Mar 09, 2010 at 11:02:31PM -0800, Marc MERLIN wrote: > >>>>[I hand editted your Email to paste back the lines together. Do your > >>>>best to > >>>>provide unsplit log lines, split ones are quit ehard to read] > >>>> > >>>>On Tue, Mar 09, 2010 at 02:44:26PM -0500, Daniel Durgin wrote: > >>>>>Hi Marc, > >>>>> > >>>>>If I Sync all links: > >>>>>09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_PadB (1 > >>>>>of 16) > >>>>>09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_PadD (2 > >>>>>of 16) > >>>>>09/03/2010 14:34:15 [Sync all links] Now syncing links: $Den_Light (3 > >>>>>of 16) > >>>>>09/03/2010 14:34:15 [Sync all links] Now syncing links: > >>>>>$Den_Light_Slave (4 of 16) > >>>>>09/03/2010 14:34:15 [Sync all links] Now syncing links: > >>>>>$HallKeyPadC_Scene (5 of 16) > >>>>>09/03/2010 14:34:15 [Sync all links] Now syncing links: > >>>>>$FF_Small_Bdroom (6 of 16) > >>>>>09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_Pad (7 > >>>>>of 16) > >>>>>09/03/2010 14:34:15 [Sync all links] Now syncing links: > >>>>>$come_home_scene (8 of 16) > >>>>>09/03/2010 14:34:15 [Sync all links] Now syncing links: > >>>>>$HallKeyPadB_Scene (9 of 16) > >>>>>09/03/2010 14:34:15 [Sync all links] Now syncing links: $Dining_Table > >>>>>(10 of 16) > >>>>>09/03/2010 14:34:15 [Sync all links] Now syncing links: > >>>>>$HallKeyPadD_Scene (11 of 16) > >>>>>09/03/2010 14:34:15 [Sync all links] Now syncing links: > >>>>>$Garage_Int_Lights (12 of 16) > >>>>>09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_PadC > >>>>>(13 of 16) > >>>>>09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_PadA > >>>>>(14 of 16) > >>>>>09/03/2010 14:34:15 [Sync all links] Now syncing links: $Sink_Lights > >>>>>(15 of 16) > >>>>>09/03/2010 14:34:15 [Sync all links] Now syncing links: > >>>>>$HallKeyPadA_Scene (16 of 16 > >>>> > >>>> > >>>>If you'r going to do your entire network, it's good to scan first and > >>>>than > >>>>sync although Im' not sure it was a problem here. > >>>> > >>>>>If I Scan all link tables: > >>>> > >>>>I mean scan link table in the PLM drop down. > >>>> > >>>>Now you are indeed right that 'sync links' should be done in the scene > >>>>drop > >>>>down. Apparently sync all doesn't since scene links to the PLM though. > >>>> > >>>>So try this: > >>>>1) (re) sync all your scenes > >>>>2) scan links on the PLM to see if it worked. > >>> > >>>I also wrote some better instructions on how you're supposed to set and > >>>debug PLM scenes: > >>>http://misterhouse.wikispaces.com/Insteon#Insteon%20Specific%20Info-Insteon%20setup%20in%20MH-Scenes%20Explained-PLM%20Scenes-Programming/Troubleshooting%20PLM%20Scenes > >>> > >>>(whoa, I asked my friend at wikispaces to change their in document links > >>>not > >>>to be something useless and non permanent like #toc1, I guess they did > >>>that > >>>recently :) > >>> > >>>Marc > >> > >>------------------------------------------------------------------------------ > >>Download Intel® Parallel Studio Eval > >>Try the new software tools for yourself. Speed compiling, find bugs > >>proactively, and fine-tune applications for parallel performance. > >>See why Intel Parallel Studio got high marks during beta. > >>http://p.sf.net/sfu/intel-sw-dev > >>________________________________________________________ > >>To unsubscribe from this list, go to: > >>http://sourceforge.net/mail/?group_id=1365 > >> > > -- "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/ |
From: Marc M. <ma...@me...> - 2010-03-12 05:08:10
|
On Thu, Mar 11, 2010 at 10:24:22PM -0500, Gregg Liming wrote: > Marc MERLIN wrote: > > On Thu, Mar 11, 2010 at 01:05:02PM -0500, Daniel Durgin wrote: > >> In the spirit of the scientific process... I tired it on the two > >> remaining buttons. No Lights before I linked, but they worked afterward. > >> > >> This is a very new kpl, maybe things changed? > > > > Gregg, does this make sense? > > ... not sure how you mean. It makes sense that it can work that way as > that is the most basic way to initiate linking of a PLM scene. But, to > those of us that use the other (possibly, more sophisticated) link > management functions, it may seem less "appropriate". Sometimes, it's > useful to leave multiple ways to accomplish the same thing as some ways > work better for some folks than others. That's fair, I just think Daniel wrote that he had to use the 'Initiate linking as controller' function to sync his PLM scene and that otherwise 'sync links' from the web interface did not seem to work. But maybe I misunderstood. Marc > > Marc > > > >> On 03/11/2010 11:46 AM, Marc MERLIN wrote: > >>> On Thu, Mar 11, 2010 at 09:49:27AM -0500, Daniel Durgin wrote: > >>>> Thank you for all the guidance. I finally got it working. > >>>> > >>>> Perhaps in my tired brain, I have a ten month old, I didn't see it > >>>> spelled out. > >>>> > >>>> On the scene, initiate linking as controller, then press and hold button > >>>> on keypad to complete link. > >>> Glad you got it working. > >>> > >>> But 'Initiate linking as controller' should not be needed for a PLM scene > >>> AFAIK. I don't even remember using this function for anything other than my > >>> motion sensor IIRC. > >>> > >>> I think you just managed to get your links synced to the PLM around that > >>> time > >>> which is what made your PLM scene work. > >>> > >>> Either way, sounds like you're up and running now. > >>> > >>> Cheers, > >>> Marc > >>> > >>> > >>>> -Dan > >>>> > >>>> On 03/10/2010 11:05 AM, Marc MERLIN wrote: > >>>>> On Tue, Mar 09, 2010 at 11:02:31PM -0800, Marc MERLIN wrote: > >>>>>> [I hand editted your Email to paste back the lines together. Do your > >>>>>> best to > >>>>>> provide unsplit log lines, split ones are quit ehard to read] > >>>>>> > >>>>>> On Tue, Mar 09, 2010 at 02:44:26PM -0500, Daniel Durgin wrote: > >>>>>>> Hi Marc, > >>>>>>> > >>>>>>> If I Sync all links: > >>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_PadB (1 > >>>>>>> of 16) > >>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_PadD (2 > >>>>>>> of 16) > >>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Den_Light (3 > >>>>>>> of 16) > >>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: > >>>>>>> $Den_Light_Slave (4 of 16) > >>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: > >>>>>>> $HallKeyPadC_Scene (5 of 16) > >>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: > >>>>>>> $FF_Small_Bdroom (6 of 16) > >>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_Pad (7 > >>>>>>> of 16) > >>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: > >>>>>>> $come_home_scene (8 of 16) > >>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: > >>>>>>> $HallKeyPadB_Scene (9 of 16) > >>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Dining_Table > >>>>>>> (10 of 16) > >>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: > >>>>>>> $HallKeyPadD_Scene (11 of 16) > >>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: > >>>>>>> $Garage_Int_Lights (12 of 16) > >>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_PadC > >>>>>>> (13 of 16) > >>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_PadA > >>>>>>> (14 of 16) > >>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Sink_Lights > >>>>>>> (15 of 16) > >>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: > >>>>>>> $HallKeyPadA_Scene (16 of 16 > >>>>>> > >>>>>> If you'r going to do your entire network, it's good to scan first and > >>>>>> than > >>>>>> sync although Im' not sure it was a problem here. > >>>>>> > >>>>>>> If I Scan all link tables: > >>>>>> I mean scan link table in the PLM drop down. > >>>>>> > >>>>>> Now you are indeed right that 'sync links' should be done in the scene > >>>>>> drop > >>>>>> down. Apparently sync all doesn't since scene links to the PLM though. > >>>>>> > >>>>>> So try this: > >>>>>> 1) (re) sync all your scenes > >>>>>> 2) scan links on the PLM to see if it worked. > >>>>> I also wrote some better instructions on how you're supposed to set and > >>>>> debug PLM scenes: > >>>>> http://misterhouse.wikispaces.com/Insteon#Insteon%20Specific%20Info-Insteon%20setup%20in%20MH-Scenes%20Explained-PLM%20Scenes-Programming/Troubleshooting%20PLM%20Scenes > >>>>> > >>>>> (whoa, I asked my friend at wikispaces to change their in document links > >>>>> not > >>>>> to be something useless and non permanent like #toc1, I guess they did > >>>>> that > >>>>> recently :) > >>>>> > >>>>> Marc > >>>> ------------------------------------------------------------------------------ > >>>> Download Intel® Parallel Studio Eval > >>>> Try the new software tools for yourself. Speed compiling, find bugs > >>>> proactively, and fine-tune applications for parallel performance. > >>>> See why Intel Parallel Studio got high marks during beta. > >>>> http://p.sf.net/sfu/intel-sw-dev > >>>> ________________________________________________________ > >>>> To unsubscribe from this list, go to: > >>>> http://sourceforge.net/mail/?group_id=1365 > >>>> > > > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > ________________________________________________________ > To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365 > -- "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/ |
From: Daniel D. <da...@ma...> - 2010-03-12 15:22:28
|
Hi Mark, You understood correctly. In the Insteon Group web page, I selected the 'Initiate linking as controller' from the drop down of the Keypad Scene. Next I held down that corresponding key on the kpl until it linked. I basically didn't understand, or it wasn't working for me, what other folks where saying about syncing/linking the scene. So I just figured that "my method" was what they were talking about. -Dan On 03/12/2010 12:08 AM, Marc MERLIN wrote: > On Thu, Mar 11, 2010 at 10:24:22PM -0500, Gregg Liming wrote: >> Marc MERLIN wrote: >>> On Thu, Mar 11, 2010 at 01:05:02PM -0500, Daniel Durgin wrote: >>>> In the spirit of the scientific process... I tired it on the two >>>> remaining buttons. No Lights before I linked, but they worked afterward. >>>> >>>> This is a very new kpl, maybe things changed? >>> >>> Gregg, does this make sense? >> >> ... not sure how you mean. It makes sense that it can work that way as >> that is the most basic way to initiate linking of a PLM scene. But, to >> those of us that use the other (possibly, more sophisticated) link >> management functions, it may seem less "appropriate". Sometimes, it's >> useful to leave multiple ways to accomplish the same thing as some ways >> work better for some folks than others. > > That's fair, I just think Daniel wrote that he had to use the 'Initiate > linking as controller' function to sync his PLM scene and that otherwise > 'sync links' from the web interface did not seem to work. > > But maybe I misunderstood. > > Marc > >>> Marc >>> >>>> On 03/11/2010 11:46 AM, Marc MERLIN wrote: >>>>> On Thu, Mar 11, 2010 at 09:49:27AM -0500, Daniel Durgin wrote: >>>>>> Thank you for all the guidance. I finally got it working. >>>>>> >>>>>> Perhaps in my tired brain, I have a ten month old, I didn't see it >>>>>> spelled out. >>>>>> >>>>>> On the scene, initiate linking as controller, then press and hold button >>>>>> on keypad to complete link. >>>>> Glad you got it working. >>>>> >>>>> But 'Initiate linking as controller' should not be needed for a PLM scene >>>>> AFAIK. I don't even remember using this function for anything other than my >>>>> motion sensor IIRC. >>>>> >>>>> I think you just managed to get your links synced to the PLM around that >>>>> time >>>>> which is what made your PLM scene work. >>>>> >>>>> Either way, sounds like you're up and running now. >>>>> >>>>> Cheers, >>>>> Marc >>>>> >>>>> >>>>>> -Dan >>>>>> >>>>>> On 03/10/2010 11:05 AM, Marc MERLIN wrote: >>>>>>> On Tue, Mar 09, 2010 at 11:02:31PM -0800, Marc MERLIN wrote: >>>>>>>> [I hand editted your Email to paste back the lines together. Do your >>>>>>>> best to >>>>>>>> provide unsplit log lines, split ones are quit ehard to read] >>>>>>>> >>>>>>>> On Tue, Mar 09, 2010 at 02:44:26PM -0500, Daniel Durgin wrote: >>>>>>>>> Hi Marc, >>>>>>>>> >>>>>>>>> If I Sync all links: >>>>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_PadB (1 >>>>>>>>> of 16) >>>>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_PadD (2 >>>>>>>>> of 16) >>>>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Den_Light (3 >>>>>>>>> of 16) >>>>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: >>>>>>>>> $Den_Light_Slave (4 of 16) >>>>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: >>>>>>>>> $HallKeyPadC_Scene (5 of 16) >>>>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: >>>>>>>>> $FF_Small_Bdroom (6 of 16) >>>>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_Pad (7 >>>>>>>>> of 16) >>>>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: >>>>>>>>> $come_home_scene (8 of 16) >>>>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: >>>>>>>>> $HallKeyPadB_Scene (9 of 16) >>>>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Dining_Table >>>>>>>>> (10 of 16) >>>>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: >>>>>>>>> $HallKeyPadD_Scene (11 of 16) >>>>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: >>>>>>>>> $Garage_Int_Lights (12 of 16) >>>>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_PadC >>>>>>>>> (13 of 16) >>>>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_PadA >>>>>>>>> (14 of 16) >>>>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Sink_Lights >>>>>>>>> (15 of 16) >>>>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: >>>>>>>>> $HallKeyPadA_Scene (16 of 16 >>>>>>>> >>>>>>>> If you'r going to do your entire network, it's good to scan first and >>>>>>>> than >>>>>>>> sync although Im' not sure it was a problem here. >>>>>>>> >>>>>>>>> If I Scan all link tables: >>>>>>>> I mean scan link table in the PLM drop down. >>>>>>>> >>>>>>>> Now you are indeed right that 'sync links' should be done in the scene >>>>>>>> drop >>>>>>>> down. Apparently sync all doesn't since scene links to the PLM though. >>>>>>>> >>>>>>>> So try this: >>>>>>>> 1) (re) sync all your scenes >>>>>>>> 2) scan links on the PLM to see if it worked. >>>>>>> I also wrote some better instructions on how you're supposed to set and >>>>>>> debug PLM scenes: >>>>>>> http://misterhouse.wikispaces.com/Insteon#Insteon%20Specific%20Info-Insteon%20setup%20in%20MH-Scenes%20Explained-PLM%20Scenes-Programming/Troubleshooting%20PLM%20Scenes >>>>>>> >>>>>>> (whoa, I asked my friend at wikispaces to change their in document links >>>>>>> not >>>>>>> to be something useless and non permanent like #toc1, I guess they did >>>>>>> that >>>>>>> recently :) >>>>>>> >>>>>>> Marc >>>>>> ------------------------------------------------------------------------------ >>>>>> Download Intel® Parallel Studio Eval >>>>>> Try the new software tools for yourself. Speed compiling, find bugs >>>>>> proactively, and fine-tune applications for parallel performance. >>>>>> See why Intel Parallel Studio got high marks during beta. >>>>>> http://p.sf.net/sfu/intel-sw-dev >>>>>> ________________________________________________________ >>>>>> To unsubscribe from this list, go to: >>>>>> http://sourceforge.net/mail/?group_id=1365 >>>>>> >>> >> >> >> ------------------------------------------------------------------------------ >> Download Intel® Parallel Studio Eval >> Try the new software tools for yourself. Speed compiling, find bugs >> proactively, and fine-tune applications for parallel performance. >> See why Intel Parallel Studio got high marks during beta. >> http://p.sf.net/sfu/intel-sw-dev >> ________________________________________________________ >> To unsubscribe from this list, go to: http://sourceforge.net/mail/?group_id=1365 >> > |
From: Gregg L. <gr...@li...> - 2010-03-12 03:24:30
|
Marc MERLIN wrote: > On Thu, Mar 11, 2010 at 01:05:02PM -0500, Daniel Durgin wrote: >> In the spirit of the scientific process... I tired it on the two >> remaining buttons. No Lights before I linked, but they worked afterward. >> >> This is a very new kpl, maybe things changed? > > Gregg, does this make sense? ... not sure how you mean. It makes sense that it can work that way as that is the most basic way to initiate linking of a PLM scene. But, to those of us that use the other (possibly, more sophisticated) link management functions, it may seem less "appropriate". Sometimes, it's useful to leave multiple ways to accomplish the same thing as some ways work better for some folks than others. > Marc > >> On 03/11/2010 11:46 AM, Marc MERLIN wrote: >>> On Thu, Mar 11, 2010 at 09:49:27AM -0500, Daniel Durgin wrote: >>>> Thank you for all the guidance. I finally got it working. >>>> >>>> Perhaps in my tired brain, I have a ten month old, I didn't see it >>>> spelled out. >>>> >>>> On the scene, initiate linking as controller, then press and hold button >>>> on keypad to complete link. >>> Glad you got it working. >>> >>> But 'Initiate linking as controller' should not be needed for a PLM scene >>> AFAIK. I don't even remember using this function for anything other than my >>> motion sensor IIRC. >>> >>> I think you just managed to get your links synced to the PLM around that >>> time >>> which is what made your PLM scene work. >>> >>> Either way, sounds like you're up and running now. >>> >>> Cheers, >>> Marc >>> >>> >>>> -Dan >>>> >>>> On 03/10/2010 11:05 AM, Marc MERLIN wrote: >>>>> On Tue, Mar 09, 2010 at 11:02:31PM -0800, Marc MERLIN wrote: >>>>>> [I hand editted your Email to paste back the lines together. Do your >>>>>> best to >>>>>> provide unsplit log lines, split ones are quit ehard to read] >>>>>> >>>>>> On Tue, Mar 09, 2010 at 02:44:26PM -0500, Daniel Durgin wrote: >>>>>>> Hi Marc, >>>>>>> >>>>>>> If I Sync all links: >>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_PadB (1 >>>>>>> of 16) >>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_PadD (2 >>>>>>> of 16) >>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Den_Light (3 >>>>>>> of 16) >>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: >>>>>>> $Den_Light_Slave (4 of 16) >>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: >>>>>>> $HallKeyPadC_Scene (5 of 16) >>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: >>>>>>> $FF_Small_Bdroom (6 of 16) >>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_Pad (7 >>>>>>> of 16) >>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: >>>>>>> $come_home_scene (8 of 16) >>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: >>>>>>> $HallKeyPadB_Scene (9 of 16) >>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Dining_Table >>>>>>> (10 of 16) >>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: >>>>>>> $HallKeyPadD_Scene (11 of 16) >>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: >>>>>>> $Garage_Int_Lights (12 of 16) >>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_PadC >>>>>>> (13 of 16) >>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Hall_PadA >>>>>>> (14 of 16) >>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: $Sink_Lights >>>>>>> (15 of 16) >>>>>>> 09/03/2010 14:34:15 [Sync all links] Now syncing links: >>>>>>> $HallKeyPadA_Scene (16 of 16 >>>>>> >>>>>> If you'r going to do your entire network, it's good to scan first and >>>>>> than >>>>>> sync although Im' not sure it was a problem here. >>>>>> >>>>>>> If I Scan all link tables: >>>>>> I mean scan link table in the PLM drop down. >>>>>> >>>>>> Now you are indeed right that 'sync links' should be done in the scene >>>>>> drop >>>>>> down. Apparently sync all doesn't since scene links to the PLM though. >>>>>> >>>>>> So try this: >>>>>> 1) (re) sync all your scenes >>>>>> 2) scan links on the PLM to see if it worked. >>>>> I also wrote some better instructions on how you're supposed to set and >>>>> debug PLM scenes: >>>>> http://misterhouse.wikispaces.com/Insteon#Insteon%20Specific%20Info-Insteon%20setup%20in%20MH-Scenes%20Explained-PLM%20Scenes-Programming/Troubleshooting%20PLM%20Scenes >>>>> >>>>> (whoa, I asked my friend at wikispaces to change their in document links >>>>> not >>>>> to be something useless and non permanent like #toc1, I guess they did >>>>> that >>>>> recently :) >>>>> >>>>> Marc >>>> ------------------------------------------------------------------------------ >>>> Download Intel® Parallel Studio Eval >>>> Try the new software tools for yourself. Speed compiling, find bugs >>>> proactively, and fine-tune applications for parallel performance. >>>> See why Intel Parallel Studio got high marks during beta. >>>> http://p.sf.net/sfu/intel-sw-dev >>>> ________________________________________________________ >>>> To unsubscribe from this list, go to: >>>> http://sourceforge.net/mail/?group_id=1365 >>>> > |
From: Marc M. <ma...@me...> - 2010-03-08 00:33:42
|
On Sun, Mar 07, 2010 at 07:04:19PM -0500, Daniel Durgin wrote: > Hi Marc, > > In your code you emailed, '$entryway' is the kpl? No, it's a device that I sync to 4 KPL buttons. > >Let me demonstrate: > >$entryway->tie_event('sync_kpl_lights($entryway, $entryway_kpls)'); # > >noloop > > > >IPLL, PLM:54, entryway_kpls, kpl_tie_scenes, PLM > >SCENE_MEMBER, fmr_kpl_entryway, entryway_kpls > >SCENE_MEMBER, kitchen_kpl_entryway, entryway_kpls > >SCENE_MEMBER, dining_kpl_entryway, entryway_kpls > >SCENE_MEMBER, lvr_kpl_entryway, entryway_kpls entryway_kpls is the PLM scene that links to my 4 KPL buttons. entryway is the actual device which if toggled will switch entryway_kpls too. 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/ |