domotinc-customs Posted April 21, 2016 Posted April 21, 2016 hi all, first post here as I got my ISY yesterday. this forum is SOOO useful! in the ISY interface, I created a scene to turn on a keypad button (I have read it's the only way) doing this works for all my 4 keypad except one keypad.... when I press the button on the keypad itself, I see it's status turn ON in the ISY scene, but if I turn on the scene , the button stay off, even if status went to on. tried turning off the circuit beaker for this keypad. still not working. in the exact same scene, I added a button of another keypad. when I turn on the scene, this other keypad button goes on, but the problem remains on the keypad (talking about the secondary button all the time here, all as responder in the scene) any idea?
Techman Posted April 21, 2016 Posted April 21, 2016 hi all, first post here as I got my ISY yesterday. this forum is SOOO useful! in the ISY interface, I created a scene to turn on a keypad button (I have read it's the only way) doing this works for all my 4 keypad except one keypad.... when I press the button on the keypad itself, I see it's status turn ON in the ISY scene, but if I turn on the scene , the button stay off, even if status went to on. tried turning off the circuit beaker for this keypad. still not working. in the exact same scene, I added a button of another keypad. when I turn on the scene, this other keypad button goes on, but the problem remains on the keypad (talking about the secondary button all the time here, all as responder in the scene) any idea? Welcome to the forum. If you want the Keypad button to control the scene then delete it from the scene and then add it back to the scene as a controller. Then the button will control the scene and will stay lit when the scene is on. The device that you're controlling should also be in the same scene as the Keypad button.
jerlands Posted April 21, 2016 Posted April 21, 2016 It sounds like the keypad is working correctly but you can check by opening Event Viewer to Level 3 (Tools > Diagnostics > Event Viewer) press the keypad button and you should see the trace in the viewer. Jon...
LeeG Posted April 21, 2016 Posted April 21, 2016 Is the Scene being turned On by an ISY Program? The ISY marks the Secondary button Status On as that is what should happen with the Scene, not what actually happened (assuming Scene turned On by Program). Check the Keypad button Responder On Level and Ramp Rate. What devices are being used to couple the 2 120v legs? The On command may not be reaching the KPL if the KPL is on the opposite 120v leg compared to the PLM and the 120v legs are not correctly coupled.
domotinc-customs Posted April 22, 2016 Author Posted April 22, 2016 I did another test. took 3 keypad including the one I have issues with, created a new scene in ISY, added one secondary button per keypad in the scene. all 3 button as controller. if I press the button on the keypad that cause me issues, it can successfully turn on and off the button on the other 2 keypad. the the other 2 keypad fail to turn on or off the button the the keypad causing me issues.
domotinc-customs Posted April 22, 2016 Author Posted April 22, 2016 here are the logs.. the keypad caussing issues is 2a.10.fc (if that can be of any help ) I pressed the button on a "working" keypad. the keypad causing issues didn't responded hope someone understand something from those logs thanks all! Thu 04/21/2016 21:23:31 : [iNST-SRX ] 02 50 22.A1.5E 00.00.04 CB 13 00 LTOFFRR(00) Thu 04/21/2016 21:23:31 : [std-Group ] 22.A1.5E-->Group=4, Max Hops=3, Hops Left=2 Thu 04/21/2016 21:23:31 : [D2D EVENT ] Event [22 A1 5E 4] [DOF] [0] uom=0 prec=-1 Thu 04/21/2016 21:23:31 : [ 22 A1 5E 4] DOF 0 Thu 04/21/2016 21:23:31 : [D2D EVENT ] Event [34 DD 55 6] [sT] [0] uom=0 prec=-1 Thu 04/21/2016 21:23:31 : [ 34 DD 55 6] ST 0 Thu 04/21/2016 21:23:31 : [D2D EVENT ] Event [2A 10 FC 6] [sT] [0] uom=0 prec=-1 Thu 04/21/2016 21:23:31 : [ 2A 10 FC 6] ST 0 Thu 04/21/2016 21:23:31 : [D2D-CMP 0006] STS [2A 10 FC 6] ST op=1 Event(val=0 uom=0 prec=-1) is Condition(val=255 uom=0 prec=-1) --> false Thu 04/21/2016 21:23:31 : [iNST-SRX ] 02 50 22.A1.5E 40.55.2D 4A 13 04 LTOFFRR(04) Thu 04/21/2016 21:23:31 : [std-Cleanup ] 22.A1.5E-->ISY/PLM Group=4, Max Hops=2, Hops Left=2 Thu 04/21/2016 21:23:31 : [iNST-DUP ] Previous message ignored. Thu 04/21/2016 21:23:32 : [iNST-SRX ] 02 50 22.A1.5E 40.55.2D 4F 13 04 LTOFFRR(04) Thu 04/21/2016 21:23:32 : [std-Cleanup ] 22.A1.5E-->ISY/PLM Group=4, Max Hops=3, Hops Left=3 Thu 04/21/2016 21:23:32 : [iNST-DUP ] Previous message ignored. Thu 04/21/2016 21:23:33 : [iNST-TX-I1 ] 02 62 39 47 B0 0F 13 02 Thu 04/21/2016 21:23:33 : [iNST-ACK ] 02 62 39.47.B0 0F 13 02 06 LTOFFRR(02) Thu 04/21/2016 21:23:33 : [D2D EVENT ] Event [22 A1 5E 4] [sT] [0] uom=0 prec=-1 Thu 04/21/2016 21:23:33 : [ 22 A1 5E 4] ST 0 Thu 04/21/2016 21:23:33 : [iNST-SRX ] 02 50 22.A1.5E 40.55.2D 43 13 04 LTOFFRR(04) Thu 04/21/2016 21:23:33 : [std-Cleanup ] 22.A1.5E-->ISY/PLM Group=4, Max Hops=3, Hops Left=0 Thu 04/21/2016 21:23:33 : [iNST-DUP ] Previous message ignored. Thu 04/21/2016 21:23:33 : [iNST-SRX ] 02 50 39.47.B0 40.55.2D 2F 13 02 LTOFFRR(02) Thu 04/21/2016 21:23:33 : [std-Direct Ack] 39.47.B0-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Thu 04/21/2016 21:23:33 : [D2D EVENT ] Event [39 47 B0 2] [sT] [0] uom=0 prec=-1 Thu 04/21/2016 21:23:33 : [ 39 47 B0 2] ST 0 Thu 04/21/2016 21:23:33 : [iNST-SRX ] 02 50 22.A1.5E 40.55.2D 4B 13 04 LTOFFRR(04) Thu 04/21/2016 21:23:33 : [std-Cleanup ] 22.A1.5E-->ISY/PLM Group=4, Max Hops=3, Hops Left=2 Thu 04/21/2016 21:23:33 : [D2D EVENT ] Event [22 A1 5E 4] [DOF] [0] uom=0 prec=-1 Thu 04/21/2016 21:23:33 : [ 22 A1 5E 4] DOF 0 Thu 04/21/2016 21:23:34 : [iNST-SRX ] 02 50 22.A1.5E 13.03.04 CB 06 01 (01) Thu 04/21/2016 21:23:34 : [std-Group ] 22.A1.5E-->13.03.04, Max Hops=3, Hops Left=2 Thu 04/21/2016 21:23:34 : [iNST-INFO ] Previous message ignored.
Techman Posted April 22, 2016 Posted April 22, 2016 (edited) When you installed the keypads did you install them one at a time using the ISY link new devices? If so, then try pulling the air gap to remove power from the device, wait a few seconds then push it back in. That sometimes will clear up problems within the keypads. Edited April 22, 2016 by Techman
LeeG Posted April 22, 2016 Posted April 22, 2016 The Event Trace does not show button on 2a.10.fc being pressed. That is why the question about how the 120v legs are coupled. The button press message does not reach the PLM.
domotinc-customs Posted April 22, 2016 Author Posted April 22, 2016 What devices are used to couple the 120v legs? not quite sure I understand your question. sorry. seems pretty simple... shame on me... lol all my 5 keypad are connected to the 3 wires (ground neutral and 120v) only the keypad causing me issues have something connected on the red wire. it does turn on a light with the main button on that keypad. all other 4 keypad have have nothing connected to the red wire. could that be it? or I didn't understand your question...
domotinc-customs Posted April 22, 2016 Author Posted April 22, 2016 The Event Trace does not show button on 2a.10.fc being pressed. That is why the question about how the 120v legs are coupled. The button press message does not reach the PLM. actualy I didn't press the button on the keypad causing issues. I pressed the button on a working keypad where ISY is configured to turn on a secondary button on that "causing issues" keypad when I press a button on the "causing issues" keypad, it successfully turn on what ever I want.
LeeG Posted April 22, 2016 Posted April 22, 2016 Normal house power in US is 240v AC which is made up of two 120 v legs. Most powered Insteon devices run off of 120v. For the Insteon signal to reach devices powered on the other 120v leg two Dual Band devices are required, one powered by 120v leg 1 and one powered by 120v leg 2. There is also a hardwired coupler, 2406H, that can be wired at the power panel to both 120v legs. Without coupling Insteon signals cannot reach powered Insteon devices on both 120v legs. As for the Event Trace, if the KPL that that does not react when linked to another device is not pressed, actual messages from the failing KPL would not be expected to appear in the event trace. When device 1 is pressed, messages from linked device 2 would not be in the trace.
domotinc-customs Posted April 22, 2016 Author Posted April 22, 2016 Normal house power in US is 240v AC which is made up of two 120 v legs. Most powered Insteon devices run off of 120v. For the Insteon signal to reach devices powered on the other 120v leg two Dual Band devices are required, one powered by 120v leg 1 and one powered by 120v leg 2. There is also a hardwired coupler, 2406H, that can be wired at the power panel to both 120v legs. Without coupling Insteon signals cannot reach powered Insteon devices on both 120v legs. As for the Event Trace, if the KPL that that does not react when linked to another device is not pressed, actual messages from the failing KPL would not be expected to appear in the event trace. When device 1 is pressed, messages from linked device 2 would not be in the trace. ok now I understand your question. no clue on which one of the 120v it is connected. I had issues in the past when I had only 3-4 insteon devices. now that all my house have insteon (about 40 devices) I don't have those communication issues anymore.
LeeG Posted April 22, 2016 Posted April 22, 2016 Turn On Event Trace LEVEL 3. Press the KPL button that does not respond to other KPL button press. Post the event log.
domotinc-customs Posted April 22, 2016 Author Posted April 22, 2016 ok found it. sorry guys for bugging you. I tried turning the circuit braker off, didn't solved the issue. I removed the KPL from ISY and re-added it. seems to work now. before I only had one button that could get turned on, now I have 3 (out of 3 attempts) I guess something went wrong when I added the KPL to ISY in the first place...
Recommended Posts