416to305 Posted November 11, 2014 Posted November 11, 2014 Hey everyone, bit lost here. I have a KeyPad linc where Scene B button turns my lamp on or off as it's a controller of the scene with the lamp a responder. If I turn the lamp on manually or rather through the ISY etc, the keypadlinc light stays off. I was reading here http://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Controlling_KeypadLinc_LEDsbut not really understanding it. How can I set it so that any time the lamp is on, the Scene B button on the keypad lights up and whenever it's off it turns off? Similar basically to the way it works as a scene. Thanks!
andyf0 Posted November 11, 2014 Posted November 11, 2014 Presumably the light is attached to a module or SwitchLinc. Add the module or the switch as another controller to the scene, not as a responder.
416to305 Posted November 11, 2014 Author Posted November 11, 2014 The light is an Insteon LED bulb so can't make it a controller, guess that's a deal breaker then eh? I can put it back to a Dimmerlinc just figured I could get away with using an LED since the Keypadlinc is literally right beside it. Have a bunch of the LEDs but hard to find uses for them due to how you turn them on or off.
LeeG Posted November 11, 2014 Posted November 11, 2014 Turning an individual device On/Off does not affect the Scene or other devices in the Scene. That is an Insteon design point from the beginning of Insteon. Need to turn the Scene On/Off to have all the Scene devices react.
Techman Posted November 11, 2014 Posted November 11, 2014 416to305 If you turn on (or off) the scene in the ISY rather than the LED bulb then your KPL will show the correct status
stusviews Posted November 11, 2014 Posted November 11, 2014 The purpose of the INSTEON LED bulb is to be able to control unswitched lighting or lighting where the switch is inaccessible or inconvenient (e.g., behind furniture) or even in a switched lamp to enable remote control. In any case, it's not meant to be controlled manually. Also, whenever you use the ISY to send a command to a device, only that device responds to the command, not any of its controllers nor any of its responders.
Guest Digger Posted November 11, 2014 Posted November 11, 2014 Can you write a program that whenever the bulb status is on then activate a scene that the switch button is a controller? That should turn the button light on.
416to305 Posted November 11, 2014 Author Posted November 11, 2014 (edited) I didn't know a program could activate a scene, I thought it could only modify properties of one like the light level of something etc.. When I say manually I mean turning it on like by using a mobile app. Normally I'd use a dimmerlinc on this lamp (making it a controller does nothing to turn the LED on on the keypadlinc) but I figured since I had a spare LED bulb I'd use it. I mean at the end of the day, a lamp with an LED Insteon bulb or a Dimmerlinc is going to do the same thing, unless you consider getting on your hands and knees to turn it on at the outlet convenience lol. This lamp will pretty much only ever manually be turned on by the keypadlinc, but every night it comes on at sunset to about 3am, so was just hoping to have the keypadlinc reflect that. The only reason it's a pain right now is because if the lamp is on and I want to turn it off (and turned it on either manually or with the timer), you basically have to press it twice on the keypadlinc, once to make the LED light up on the keypad, and then again to turn it off. So just not really overly friendly to anyone that you haven't explained how to turn the lamp on to. Was hoping to have a button that says LAMP making it obvious how to do it, but someone pressing it just once might think it doesn't work since you'd have to press it twice. I think I know the answer now to this, but does this mean that I also can't do like I was hoping and say if the front door opens, the Keypadlinc LED flashes 10 times, or if hidden door sensor changes to Open, the keypad lights up BUT stays lit for 10 minutes and then goes off? Wanted that in my bedroom so that if someone comes in, the keypad would light up but stay on vs right now where they close the door it immediately goes off. Edited November 11, 2014 by 416to305
416to305 Posted November 11, 2014 Author Posted November 11, 2014 (edited) Actually I can do what I want with the Vera since I use Vera as the main controller and the ISY just for Insteon stuff. Vera can turn an Insteon scene on or off even if the ISY can't. So I just made a scene which has just one Keypadlinc button as the controller. When you turn it on or off on the ISY the LED goes on or off on the KPL. So I can just set a scene in the Vera to say if the status of the lamp is on, turn on ISY scene and if it's off turn it off. Edit: That worked! Just made a quick scene if the lamp status is on, Vera tells the ISY to turn on the Lamp scene, and if it's off it tells it to turn it off. Did it as a test and if I turn the lamp on from my cell, it immediately updates on the KPL. Edited November 11, 2014 by 416to305
Guest Digger Posted November 11, 2014 Posted November 11, 2014 I didn't know a program could activate a scene, I thought it could only modify properties of one like the light level of something etc.. When I say manually I mean turning it on like by using a mobile app. Normally I'd use a dimmerlinc on this lamp (making it a controller does nothing to turn the LED on on the keypadlinc) but I figured since I had a spare LED bulb I'd use it. I mean at the end of the day, a lamp with an LED Insteon bulb or a Dimmerlinc is going to do the same thing, unless you consider getting on your hands and knees to turn it on at the outlet convenience lol. This lamp will pretty much only ever manually be turned on by the keypadlinc, but every night it comes on at sunset to about 3am, so was just hoping to have the keypadlinc reflect that. The only reason it's a pain right now is because if the lamp is on and I want to turn it off (and turned it on either manually or with the timer), you basically have to press it twice on the keypadlinc, once to make the LED light up on the keypad, and then again to turn it off. So just not really overly friendly to anyone that you haven't explained how to turn the lamp on to. Was hoping to have a button that says LAMP making it obvious how to do it, but someone pressing it just once might think it doesn't work since you'd have to press it twice. I think I know the answer now to this, but does this mean that I also can't do like I was hoping and say if the front door opens, the Keypadlinc LED flashes 10 times, or if hidden door sensor changes to Open, the keypad lights up BUT stays lit for 10 minutes and then goes off? Wanted that in my bedroom so that if someone comes in, the keypad would light up but stay on vs right now where they close the door it immediately goes off. Your if statement can be if the hidden sensor is open and your then statement can be turn on Keypad button B. I think that should work. As far as flashing it your if statement can be turn it on then wait X seconds then turn it off then wait X seconds and keep rinsing and repeating. I have not tried the above but I think you can play with it and make it work. The ISY is very capable if you get familiar with it. Many times there are easier ways to do a program after you get to know it more. I just got an ISY a few weeks ago but had an original ISY 26 way back when. Its the most reliable controller I have seen in the past decade.
oberkc Posted November 11, 2014 Posted November 11, 2014 I didn't know a program could activate a scene, I thought it could only modify properties of one like the light level of something etc.. Yes, indeed, a program can activate a scene. I see no reason the ISY cannot do what you want. Write a program: if status "insteon bulblinc" is not off set "scene" on else set "scene" off
416to305 Posted November 11, 2014 Author Posted November 11, 2014 (edited) Ah you're right ober, I remember I had this same issue before. I keep thinking you can't control a scene because in the ISY program, I always from the drop down assume you'd pick Scene to change a scene, which of course is just to modify stuff in a scene. I never think to pick SET instead and then pick the scene so that's awesome, was a bit leery on relying on the Vera. Side note, can the load on a KPL not dim?? I put one in my front foyer which has amazing dimming lights, but it's either 100% super bright on, or off. Under SET I don't have any options like picking brightness level, same with in the ISY like you would on a dimmer. Bit disappointed there, this is a 6 scene KPL. Not really end of the world but assumed everything could dim! Edited November 11, 2014 by 416to305
stusviews Posted November 11, 2014 Posted November 11, 2014 Which specific KPL? All my KPL 6-button dimmers (15) can set both the On-level and ramp rate.
toflaherty Posted November 11, 2014 Posted November 11, 2014 It's probably a kpl switch, not a kpl dimmer.
416to305 Posted November 11, 2014 Author Posted November 11, 2014 (edited) Oh you're right just checked and it is, didn't even realize there were different ones! Is that probably why they make a loud click sound when turning on and off? All my other Insteon switches are silent but these make a click. Not as loud as my Lutron motion switches but still loud enough. I'd keep these and buy the proper ones, but if the dimmer ones are silent then I'd exchange them. Edited November 11, 2014 by 416to305
stusviews Posted November 11, 2014 Posted November 11, 2014 Dimmers use TRIACs which control the dimness electronically whereas the On/Off devices use a mechanical relay, thus the audible click.
416to305 Posted November 11, 2014 Author Posted November 11, 2014 I'm having an issue with the program above, I did it basically like: ifstatus "insteon bulblinc" is not offset "scene" onelseset "scene" off Which does work if I turn the lamp on from my cell for example, however if I turn the lamp on by pressing the KPL button that is the scene controller, the lamp flashes on and off over and over until I disable the above program. Basically gets stuck in a loop on and off on and off. When I used the Vera to run this scene whenever the lamp status was on, it worked fine so not sure why it's doing it now. Any ideas?
LeeG Posted November 11, 2014 Posted November 11, 2014 What is "scene"? What type of device? Perhaps that should be Set Scene "scene" On still need to know what is in "scene" and what actual commands issued. Best to Copy to Clipboard the Program and paste into post as well as cover "scene" context
416to305 Posted November 11, 2014 Author Posted November 11, 2014 Sure thing sorry. The scene is very basic, it's called "Living Room Lamp" and includes the KPL Button B, and Living Room Lamp Dimmerlinc. They are both controller and responder for the above scene. If I press KPL button B, it lights up and the lamp comes on and if I press it again it goes off with the lamp. I'm trying to have it so that if I turn the lamp on with a timer, or with a mobile device, the KPL button lights up. So the program I used for that is: If Status 'Living Room Lamp' is not Off Then Set Scene 'Living Room Lamp' On Else Set Scene 'Living Room Lamp' Off This works if I then use my cell phone or a timer to turn the lamp on or off, as when I turn the lamp on the KPL lights up and so on. The problem is that if I now go to the KPL and press button B to turn the lamp on, it comes on, then immediately goes off, then back on, and then back and forth in a loop flashing. The program above in the ISY you see flipping from TRUE to FALSE over and over until I disable it. What I don't get though is that in my Vera connected to the ISY, I originally made a program there as I forgot I could do it from the ISY, so on the Vera I said if the status of the lamp is on, then set the above scene on, and if it's off then set the scene off. This worked perfectly fine no looping. I deleted all the stuff in the Vera to create the above, so it's not the culprit. Thanks!
LeeG Posted November 11, 2014 Posted November 11, 2014 Not a good idea to have device and Scene with same name. Run Tools | Diagnostics | Event Viewer at LEVEL 3. Press KPL button so device cycles On/Off a few times and post the event trace
416to305 Posted November 11, 2014 Author Posted November 11, 2014 (edited) Oh yeah I can rename it I just did it quick when testing, didn't think of that. This is weird though now it works totally fine. The only thing different I did was I had unplugged the ISY and moved it with the PLM from the basement to upstairs (same distance away physically from the KPL if that matters). Maybe it was just glitching earlier? Here's the log either way: Tue 11/11/2014 09:37:04 AM : [iNST-SRX ] 02 50 30.0F.AA 00.00.04 CB 11 00 LTONRR (00) Tue 11/11/2014 09:37:04 AM : [std-Group ] 30.0F.AA-->Group=4, Max Hops=3, Hops Left=2 Tue 11/11/2014 09:37:04 AM : [D2D EVENT ] Event [30 F AA 4] [DON] [0] uom=0 prec=-1 Tue 11/11/2014 09:37:04 AM : [ 30 F AA 4] DON 0 Tue 11/11/2014 09:37:04 AM : [D2D EVENT ] Event [30 F AA 4] [sT] [255] uom=0 prec=-1 Tue 11/11/2014 09:37:04 AM : [ 30 F AA 4] ST 255 Tue 11/11/2014 09:37:04 AM : [D2D EVENT ] Event [26 93 59 1] [sT] [255] uom=0 prec=-1 Tue 11/11/2014 09:37:04 AM : [ 26 93 59 1] ST 255 Tue 11/11/2014 09:37:04 AM : [D2D-CMP 0006] STS [26 93 59 1] ST op=6 Event(val=255 uom=0 prec=-1) != Condition(val=0 uom=0 prec=-1) --> true Tue 11/11/2014 09:37:04 AM : [iNST-SRX ] 02 50 30.0F.AA 2C.08.F8 41 11 04 LTONRR (04) Tue 11/11/2014 09:37:04 AM : [std-Cleanup ] 30.0F.AA-->ISY/PLM Group=4, Max Hops=1, Hops Left=0 Tue 11/11/2014 09:37:04 AM : [iNST-DUP ] Previous message ignored. Tue 11/11/2014 09:37:04 AM : [iNST-SRX ] 02 50 30.0F.AA 11.02.04 CB 06 00 (00) Tue 11/11/2014 09:37:04 AM : [std-Group ] 30.0F.AA-->11.02.04, Max Hops=3, Hops Left=2 Tue 11/11/2014 09:37:04 AM : [iNST-INFO ] Previous message ignored. Tue 11/11/2014 09:37:04 AM : [iNST-TX-I1 ] 02 62 00 00 11 CF 11 00 Tue 11/11/2014 09:37:05 AM : [iNST-ACK ] 02 62 00.00.11 CF 11 00 06 LTONRR (00) Tue 11/11/2014 09:37:12 AM : [iNST-SRX ] 02 50 30.0F.AA 00.00.04 C7 13 00 LTOFFRR(00) Tue 11/11/2014 09:37:12 AM : [std-Group ] 30.0F.AA-->Group=4, Max Hops=3, Hops Left=1 Tue 11/11/2014 09:37:12 AM : [D2D EVENT ] Event [30 F AA 4] [DOF] [0] uom=0 prec=-1 Tue 11/11/2014 09:37:12 AM : [ 30 F AA 4] DOF 0 Tue 11/11/2014 09:37:12 AM : [D2D EVENT ] Event [30 F AA 4] [sT] [0] uom=0 prec=-1 Tue 11/11/2014 09:37:12 AM : [ 30 F AA 4] ST 0 Tue 11/11/2014 09:37:12 AM : [D2D EVENT ] Event [26 93 59 1] [sT] [0] uom=0 prec=-1 Tue 11/11/2014 09:37:12 AM : [ 26 93 59 1] ST 0 Tue 11/11/2014 09:37:12 AM : [D2D-CMP 0006] STS [26 93 59 1] ST op=6 Event(val=0 uom=0 prec=-1) != Condition(val=0 uom=0 prec=-1) --> false Tue 11/11/2014 09:37:12 AM : [iNST-SRX ] 02 50 30.0F.AA 00.00.04 C3 13 00 LTOFFRR(00) Tue 11/11/2014 09:37:12 AM : [std-Group ] 30.0F.AA-->Group=4, Max Hops=3, Hops Left=0 Tue 11/11/2014 09:37:12 AM : [iNST-DUP ] Previous message ignored. Tue 11/11/2014 09:37:12 AM : [iNST-SRX ] 02 50 30.0F.AA 2C.08.F8 41 13 04 LTOFFRR(04) Tue 11/11/2014 09:37:12 AM : [std-Cleanup ] 30.0F.AA-->ISY/PLM Group=4, Max Hops=1, Hops Left=0 Tue 11/11/2014 09:37:12 AM : [iNST-DUP ] Previous message ignored. Tue 11/11/2014 09:37:12 AM : [iNST-SRX ] 02 50 30.0F.AA 13.02.04 C7 06 00 (00) Tue 11/11/2014 09:37:12 AM : [std-Group ] 30.0F.AA-->13.02.04, Max Hops=3, Hops Left=1 Tue 11/11/2014 09:37:12 AM : [iNST-INFO ] Previous message ignored. Tue 11/11/2014 09:37:13 AM : [iNST-TX-I1 ] 02 62 00 00 11 CF 13 00 Tue 11/11/2014 09:37:13 AM : [iNST-ACK ] 02 62 00.00.11 CF 13 00 06 LTOFFRR(00) Tue 11/11/2014 09:37:15 AM : [iNST-SRX ] 02 50 30.0F.AA 00.00.04 CB 11 00 LTONRR (00) Tue 11/11/2014 09:37:15 AM : [std-Group ] 30.0F.AA-->Group=4, Max Hops=3, Hops Left=2 Tue 11/11/2014 09:37:15 AM : [D2D EVENT ] Event [30 F AA 4] [DON] [0] uom=0 prec=-1 Tue 11/11/2014 09:37:15 AM : [ 30 F AA 4] DON 0 Tue 11/11/2014 09:37:15 AM : [D2D EVENT ] Event [30 F AA 4] [sT] [255] uom=0 prec=-1 Tue 11/11/2014 09:37:15 AM : [ 30 F AA 4] ST 255 Tue 11/11/2014 09:37:15 AM : [D2D EVENT ] Event [26 93 59 1] [sT] [255] uom=0 prec=-1 Tue 11/11/2014 09:37:15 AM : [ 26 93 59 1] ST 255 Tue 11/11/2014 09:37:15 AM : [D2D-CMP 0006] STS [26 93 59 1] ST op=6 Event(val=255 uom=0 prec=-1) != Condition(val=0 uom=0 prec=-1) --> true Tue 11/11/2014 09:37:16 AM : [iNST-SRX ] 02 50 30.0F.AA 2C.08.F8 41 11 04 LTONRR (04) Tue 11/11/2014 09:37:16 AM : [std-Cleanup ] 30.0F.AA-->ISY/PLM Group=4, Max Hops=1, Hops Left=0 Tue 11/11/2014 09:37:16 AM : [iNST-DUP ] Previous message ignored. Tue 11/11/2014 09:37:16 AM : [iNST-SRX ] 02 50 30.0F.AA 11.02.04 CB 06 00 (00) Tue 11/11/2014 09:37:16 AM : [std-Group ] 30.0F.AA-->11.02.04, Max Hops=3, Hops Left=2 Tue 11/11/2014 09:37:16 AM : [iNST-INFO ] Previous message ignored. Tue 11/11/2014 09:37:17 AM : [iNST-TX-I1 ] 02 62 00 00 11 CF 11 00 Tue 11/11/2014 09:37:17 AM : [iNST-ACK ] 02 62 00.00.11 CF 11 00 06 LTONRR (00) Tue 11/11/2014 09:37:22 AM : [iNST-SRX ] 02 50 30.0F.AA 00.00.04 CB 13 00 LTOFFRR(00) Tue 11/11/2014 09:37:22 AM : [std-Group ] 30.0F.AA-->Group=4, Max Hops=3, Hops Left=2 Tue 11/11/2014 09:37:22 AM : [D2D EVENT ] Event [30 F AA 4] [DOF] [0] uom=0 prec=-1 Tue 11/11/2014 09:37:22 AM : [ 30 F AA 4] DOF 0 Tue 11/11/2014 09:37:22 AM : [D2D EVENT ] Event [30 F AA 4] [sT] [0] uom=0 prec=-1 Tue 11/11/2014 09:37:22 AM : [ 30 F AA 4] ST 0 Tue 11/11/2014 09:37:22 AM : [D2D EVENT ] Event [26 93 59 1] [sT] [0] uom=0 prec=-1 Tue 11/11/2014 09:37:22 AM : [ 26 93 59 1] ST 0 Tue 11/11/2014 09:37:22 AM : [D2D-CMP 0006] STS [26 93 59 1] ST op=6 Event(val=0 uom=0 prec=-1) != Condition(val=0 uom=0 prec=-1) --> false Tue 11/11/2014 09:37:22 AM : [iNST-SRX ] 02 50 30.0F.AA 2C.08.F8 41 13 04 LTOFFRR(04) Tue 11/11/2014 09:37:22 AM : [std-Cleanup ] 30.0F.AA-->ISY/PLM Group=4, Max Hops=1, Hops Left=0 Tue 11/11/2014 09:37:22 AM : [iNST-DUP ] Previous message ignored. Tue 11/11/2014 09:37:22 AM : [iNST-SRX ] 02 50 30.0F.AA 13.02.04 CB 06 00 (00) Tue 11/11/2014 09:37:22 AM : [std-Group ] 30.0F.AA-->13.02.04, Max Hops=3, Hops Left=2 Tue 11/11/2014 09:37:22 AM : [iNST-INFO ] Previous message ignored. Tue 11/11/2014 09:37:22 AM : [iNST-TX-I1 ] 02 62 00 00 11 CF 13 00 Tue 11/11/2014 09:37:22 AM : [iNST-ACK ] 02 62 00.00.11 CF 13 00 06 LTOFFRR(00) Tue 11/11/2014 09:37:46 AM : [iNST-TX-I1 ] 02 62 26 93 59 0F 11 FF Tue 11/11/2014 09:37:46 AM : [iNST-ACK ] 02 62 26.93.59 0F 11 FF 06 LTONRR (FF) Tue 11/11/2014 09:37:47 AM : [iNST-SRX ] 02 50 26.93.59 2C.08.F8 2B 11 FF LTONRR (FF) Tue 11/11/2014 09:37:47 AM : [std-Direct Ack] 26.93.59-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 11/11/2014 09:37:47 AM : [D2D EVENT ] Event [26 93 59 1] [sT] [255] uom=0 prec=-1 Tue 11/11/2014 09:37:47 AM : [ 26 93 59 1] ST 255 Tue 11/11/2014 09:37:47 AM : [D2D-CMP 0006] STS [26 93 59 1] ST op=6 Event(val=255 uom=0 prec=-1) != Condition(val=0 uom=0 prec=-1) --> true Tue 11/11/2014 09:37:47 AM : [iNST-TX-I1 ] 02 62 00 00 11 CF 11 00 Tue 11/11/2014 09:37:47 AM : [iNST-ACK ] 02 62 00.00.11 CF 11 00 06 LTONRR (00) Tue 11/11/2014 09:37:47 AM : [D2D EVENT ] Event [30 F AA 4] [sT] [255] uom=0 prec=-1 Tue 11/11/2014 09:37:47 AM : [ 30 F AA 4] ST 255 Tue 11/11/2014 09:37:49 AM : [iNST-TX-I1 ] 02 62 26 93 59 0F 13 00 Tue 11/11/2014 09:37:49 AM : [iNST-ACK ] 02 62 26.93.59 0F 13 00 06 LTOFFRR(00) Tue 11/11/2014 09:37:50 AM : [iNST-SRX ] 02 50 26.93.59 2C.08.F8 2B 13 00 LTOFFRR(00) Tue 11/11/2014 09:37:50 AM : [std-Direct Ack] 26.93.59-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 11/11/2014 09:37:50 AM : [D2D EVENT ] Event [26 93 59 1] [sT] [0] uom=0 prec=-1 Tue 11/11/2014 09:37:50 AM : [ 26 93 59 1] ST 0 Tue 11/11/2014 09:37:50 AM : [D2D-CMP 0006] STS [26 93 59 1] ST op=6 Event(val=0 uom=0 prec=-1) != Condition(val=0 uom=0 prec=-1) --> false Tue 11/11/2014 09:37:50 AM : [iNST-TX-I1 ] 02 62 00 00 11 CF 13 00 Tue 11/11/2014 09:37:50 AM : [iNST-ACK ] 02 62 00.00.11 CF 13 00 06 LTOFFRR(00) Tue 11/11/2014 09:37:50 AM : [D2D EVENT ] Event [30 F AA 4] [sT] [0] uom=0 prec=-1 Tue 11/11/2014 09:37:50 AM : [ 30 F AA 4] ST 0 Tue 11/11/2014 09:37:53 AM : [iNST-SRX ] 02 50 30.0F.AA 00.00.04 C7 11 00 LTONRR (00) Tue 11/11/2014 09:37:53 AM : [std-Group ] 30.0F.AA-->Group=4, Max Hops=3, Hops Left=1 Tue 11/11/2014 09:37:53 AM : [D2D EVENT ] Event [30 F AA 4] [DON] [0] uom=0 prec=-1 Tue 11/11/2014 09:37:53 AM : [ 30 F AA 4] DON 0 Tue 11/11/2014 09:37:53 AM : [D2D EVENT ] Event [30 F AA 4] [sT] [255] uom=0 prec=-1 Tue 11/11/2014 09:37:53 AM : [ 30 F AA 4] ST 255 Tue 11/11/2014 09:37:53 AM : [D2D EVENT ] Event [26 93 59 1] [sT] [255] uom=0 prec=-1 Tue 11/11/2014 09:37:53 AM : [ 26 93 59 1] ST 255 Tue 11/11/2014 09:37:53 AM : [D2D-CMP 0006] STS [26 93 59 1] ST op=6 Event(val=255 uom=0 prec=-1) != Condition(val=0 uom=0 prec=-1) --> true Tue 11/11/2014 09:37:53 AM : [iNST-SRX ] 02 50 30.0F.AA 00.00.04 CB 11 00 LTONRR (00) Tue 11/11/2014 09:37:53 AM : [std-Group ] 30.0F.AA-->Group=4, Max Hops=3, Hops Left=2 Tue 11/11/2014 09:37:53 AM : [iNST-DUP ] Previous message ignored. Tue 11/11/2014 09:37:54 AM : [iNST-SRX ] 02 50 30.0F.AA 2C.08.F8 41 11 04 LTONRR (04) Tue 11/11/2014 09:37:54 AM : [std-Cleanup ] 30.0F.AA-->ISY/PLM Group=4, Max Hops=1, Hops Left=0 Tue 11/11/2014 09:37:54 AM : [iNST-DUP ] Previous message ignored. Tue 11/11/2014 09:37:54 AM : [iNST-SRX ] 02 50 30.0F.AA 11.02.04 C7 06 00 (00) Tue 11/11/2014 09:37:54 AM : [std-Group ] 30.0F.AA-->11.02.04, Max Hops=3, Hops Left=1 Tue 11/11/2014 09:37:54 AM : [iNST-INFO ] Previous message ignored. Tue 11/11/2014 09:37:55 AM : [iNST-TX-I1 ] 02 62 00 00 11 CF 11 00 Tue 11/11/2014 09:37:55 AM : [iNST-ACK ] 02 62 00.00.11 CF 11 00 06 LTONRR (00) Tue 11/11/2014 09:37:59 AM : [iNST-SRX ] 02 50 30.0F.AA 00.00.04 CB 13 00 LTOFFRR(00) Tue 11/11/2014 09:37:59 AM : [std-Group ] 30.0F.AA-->Group=4, Max Hops=3, Hops Left=2 Tue 11/11/2014 09:37:59 AM : [D2D EVENT ] Event [30 F AA 4] [DOF] [0] uom=0 prec=-1 Tue 11/11/2014 09:37:59 AM : [ 30 F AA 4] DOF 0 Tue 11/11/2014 09:37:59 AM : [D2D EVENT ] Event [30 F AA 4] [sT] [0] uom=0 prec=-1 Tue 11/11/2014 09:37:59 AM : [ 30 F AA 4] ST 0 Tue 11/11/2014 09:37:59 AM : [D2D EVENT ] Event [26 93 59 1] [sT] [0] uom=0 prec=-1 Tue 11/11/2014 09:37:59 AM : [ 26 93 59 1] ST 0 Tue 11/11/2014 09:37:59 AM : [D2D-CMP 0006] STS [26 93 59 1] ST op=6 Event(val=0 uom=0 prec=-1) != Condition(val=0 uom=0 prec=-1) --> false Tue 11/11/2014 09:37:59 AM : [iNST-SRX ] 02 50 30.0F.AA 00.00.04 C3 13 00 LTOFFRR(00) Tue 11/11/2014 09:37:59 AM : [std-Group ] 30.0F.AA-->Group=4, Max Hops=3, Hops Left=0 Tue 11/11/2014 09:37:59 AM : [iNST-DUP ] Previous message ignored. Tue 11/11/2014 09:37:59 AM : [iNST-SRX ] 02 50 30.0F.AA 2C.08.F8 41 13 04 LTOFFRR(04) Tue 11/11/2014 09:37:59 AM : [std-Cleanup ] 30.0F.AA-->ISY/PLM Group=4, Max Hops=1, Hops Left=0 Tue 11/11/2014 09:37:59 AM : [iNST-DUP ] Previous message ignored. Tue 11/11/2014 09:37:59 AM : [iNST-SRX ] 02 50 30.0F.AA 13.02.04 CB 06 00 (00) Tue 11/11/2014 09:37:59 AM : [std-Group ] 30.0F.AA-->13.02.04, Max Hops=3, Hops Left=2 Tue 11/11/2014 09:37:59 AM : [iNST-INFO ] Previous message ignored. Tue 11/11/2014 09:38:00 AM : [iNST-TX-I1 ] 02 62 00 00 11 CF 13 00 Tue 11/11/2014 09:38:00 AM : [iNST-ACK ] 02 62 00.00.11 CF 13 00 06 LTOFFRR(00) The first few times was me pressing the KPL on and off, then the 2nd last time I turned it on from my cell phone and off again just in case, and then the last time I did it on and off on the KPL again. Doesn't flash at all, so strange. Edited November 11, 2014 by 416to305
EricK Posted November 11, 2014 Posted November 11, 2014 Hi, I just read this thread and it seems what you want is simple and should be able to be accomplished with scenes. You have a scene with the KPL button and and lamplinc dimmer (I think that is the device) as both controllers and responders of a scene, "Living Room Lamp". Anytime you want the lamp on, even with a timer, make sure you turn on that scene, not the device itself. By turning on the scene, both responders, the KPL button and the dimmer will turn on. The KPL button will then reflect the status of the scene. If you just turn on the dimmer, the KPL button does not know it. Ex: If time is sunset to 3AM next day Then set scene 'living Room lamp' On Else set scene 'Living Room Lamp" Off Now, sometimes things do not behave like you expect them to. If you needed what I call a "correction program" for the KPL button to show the lamp status then this is what I would do. Create a scene called 'KPL button Living Room Lamp' and set the KPL button as a responder of the scene. No other devices are needed in the scene. Then write the program. If Status 'Living Room Lamp' is not Off Then Set Scene 'KPL button Living Room Lamp' On Else Set Scene 'KPL button Living Room Lamp' Off I hope this helps to clarify things. Eric
clarkes71 Posted November 11, 2014 Posted November 11, 2014 I do what EricK is stating... Using a Insteon LED bulb I would create a scene called 'Living Room Lamp- LED Bulb' and add the KPL Button B as controller and LED Bulb as responder. I would create a Scene called 'Living Room Lamp-KPL Button B' and put only the KPL Button B in it. Create program: IfStatus 'Living Room LED Bulb' is not OffThenSet Scene 'Living Room Lamp-KPL Button B' OnElseSet Scene 'Living Room Lamp-KPL Button B' Off This way, if the Lamp on/off status is changed by another program or mobile device, the LED responds correctly. It won't go in a loop because only the KPL button is in Scene 'Living Room Lamp-KPL Button B' -- it is only a toggle for the KPL LED backlight.
416to305 Posted November 11, 2014 Author Posted November 11, 2014 Thanks so much guys I have it working now. Now that I've been playing with the KPL more it makes sense. I think I was thinking that a KPL button had to be the controller of a scene for its LED to come on, as in it had to be the device to start the scene for the LED to come on. Now I realize though that just making it the single responder and device in a scene is all you need to control the LED on it however you want. So now everything is great, seems like such a dumb question now that I understand how it works!
toflaherty Posted November 11, 2014 Posted November 11, 2014 Glad you got it all figured out. I'm doing the same thing as you, that is using a kpl button to reflect the status of a lamplinc dimmer. What works for me is having the button and lamplinc in a scene with both as controllers. This works properly regardless of whether i use the button on the kpl, the button on the lamplinc, or mobilinc. Every method results in all statuses being reflected properly. I have no scenes for these devices with any responders. Don't know why this works this way but it works. No programs either, just one scene with two controllers.
Recommended Posts