Banichi Posted December 9, 2020 Posted December 9, 2020 So I have a similar question to one recently posted and I learned a bit from there about how IF conditions work. I don't typically use programs for basic scene control but I'm trying to troubleshoot why some LEDs flicker when a scene is triggered by a KPL button (member of scene) vs say triggering the scene directly from the ISY which produces zero flicker. So in an attempt to have the button trigger the scene rather than being part of the scene I tried to make a program that was like below:IF 'Master Suite / .Mstr Bath His Sconce / .Mstr Bath All' is switched on THEN Set 'Master Suite / Master Bath All' On I have also run with Status instead of control. When I have it as control nothing at all happens. If I have it as status nothing happens on it's own but if I "run IF" then it will do what I expect. It just doesn't seem to evaluate the IF on its own. Of note is that the 'control' variant would always show 'true' regardless of the button being on or off whereas the status reflects state correctly. My ultimate goal is to deal with the flicker on the LEDs but since the scene triggered from admin console produces no flicker I thought this would be a decent workaround. But on that note if I set the ramp rate to something like 2 or 4.5 seconds there is significant flicker on dimming. If I push and hold to dim it is smooth until I release the button in which case I get a brief flicker. Anywho. I would appreciate any thoughts on either issue.
MrBill Posted December 9, 2020 Posted December 9, 2020 Are you aware that the Ramp Rate and On level are different for each controller? That is, when defining the scene setting the Ramp Rate and On level at the root level are the values that will be used when controlled by the ISY or an ISY programs. Also click each Controller listed with a RED name within the scene and set the Ramp Rate and On Level that occur when that specific controller is used. As for the program, 'Control' would be the feature you would want to use. however, if there are multiple controllers you must OR them all together and realize that "Switched On" (single tap) is different that fast on(double tap), or hold button to dim. At the bottom of this post is an example that catches all the possibilities from two different KPL buttons. With 'Status' I have the most luck using "is Not Off" and "is Off" in an If statement. ---- Manual.on - [ID 00A5][Parent 00A7] If 'DN Back Door Recessed+# / {hide}Lamp 4' is switched On Or 'DN Back Door Recessed+# / {hide}Lamp 4' is switched Fast On Or 'DN Back Door Recessed+# / {hide}Lamp 4' is switched Fade Stop Or '{hide}OUT Lower Fans - High / {hide}DN Lamp 4' is switched On Or '{hide}OUT Lower Fans - High / {hide}DN Lamp 4' is switched Fast On Or '{hide}OUT Lower Fans - High / {hide}DN Lamp 4' is switched Fade Stop Then $Dim.Lamp4 = 101 Else - No Actions - (To add one, press 'Action')
Banichi Posted December 9, 2020 Author Posted December 9, 2020 Yeah the button was originally part of the scene and had the same ramp rates and on-levels as the root scene. I removed it from the scene and then tried to use it in the program. I did use control but it did not function at all. So not sure if I have greater issues in the network. I have used status in some timers and typically use the 'is not off' operator as well and it functions well. But neither were working in this case. Event viewer shows a time stamp if I run the IF statement on control but it does not trigger the scene. No idea what I'm missing. I feel like the button on the KP may be part of the issue.
lilyoyo1 Posted December 9, 2020 Posted December 9, 2020 2 hours ago, Banichi said: So I have a similar question to one recently posted and I learned a bit from there about how IF conditions work. I don't typically use programs for basic scene control but I'm trying to troubleshoot why some LEDs flicker when a scene is triggered by a KPL button (member of scene) vs say triggering the scene directly from the ISY which produces zero flicker. So in an attempt to have the button trigger the scene rather than being part of the scene I tried to make a program that was like below:IF 'Master Suite / .Mstr Bath His Sconce / .Mstr Bath All' is switched on THEN Set 'Master Suite / Master Bath All' On I have also run with Status instead of control. When I have it as control nothing at all happens. If I have it as status nothing happens on it's own but if I "run IF" then it will do what I expect. It just doesn't seem to evaluate the IF on its own. Of note is that the 'control' variant would always show 'true' regardless of the button being on or off whereas the status reflects state correctly. My ultimate goal is to deal with the flicker on the LEDs but since the scene triggered from admin console produces no flicker I thought this would be a decent workaround. But on that note if I set the ramp rate to something like 2 or 4.5 seconds there is significant flicker on dimming. If I push and hold to dim it is smooth until I release the button in which case I get a brief flicker. Anywho. I would appreciate any thoughts on either issue. What's your firmware and UI? Does the ISY see when you manually turn on the keypad? What happens when you run the "then" portion
Banichi Posted December 10, 2020 Author Posted December 10, 2020 4 hours ago, lilyoyo1 said: What's your firmware and UI? Does the ISY see when you manually turn on the keypad? What happens when you run the "then" portion 5.0.16C UI is the same. Good question on the "then" portion. I didn't run just the "then". I will be back at the client's home early next week and can try.
Recommended Posts