sfhutchi Posted May 9, 2010 Posted May 9, 2010 Possibly this is a 'feature' and not a bug.... I have a program that calls a light to go to 80%. If Status 'Motion - Master Bath-Sensor' is On And From Sunset - 2 hours To 9:59:59PM (same day) And Status 'Master Bedroom / Master Bath Light' is not On Then Set 'Master Bedroom / Master Bath Light' 80% Else - No Actions - (To add one, press 'Action') The light is later turned off using this program. If Status 'Master Bedroom / Master Bath Light' > Off And Status 'Motion - Master Bath-Sensor' is Off Then Wait 5 minutes Set Scene 'Master Bedroom / Slow Master Bath Light' Off Else - No Actions - (To add one, press 'Action') When the light is turned on again by the first program, it uses the ramp rate from the scene that shut off the light (very slow ramp)... not the local ramp rate. What is the best way to resolve this? I would like to use the local ramp rate... or do I need to use a 'set scene' command or create a new scene?
Michel Kohanim Posted May 9, 2010 Posted May 9, 2010 Hello sfhutchi, Unfortunately INSTEON spec does not allow you to use the local ramp rate for the scene ramp rate. i.e. devices participating in a scene respond with the scene ram rate. If you want to use the local ramp rate, you must address the device specifically and not within a scene. With kind regards, Michel
fitzpatri8 Posted May 9, 2010 Posted May 9, 2010 A single device can be part of hundreds of different scenes. Just create a new scene for the On using a faster ramp rate.
Sub-Routine Posted May 9, 2010 Posted May 9, 2010 What I have found is that devices use the last ramp rate when commanded to a specific level, not the local rate. So yes, create a new scene for the On command. I do this myself with motion sensors. Rand
sfhutchi Posted May 9, 2010 Author Posted May 9, 2010 What I have found is that devices use the last ramp rate when commanded to a specific level, not the local rate. So yes, create a new scene for the On command. I do this myself with motion sensors. Rand Okay. I'll do this. Sounds like an anomaly in the way that the switches are designed. Since I am commanding the device directly and I only have the option to command light level, intuitively I would assume local ramp.
aLf Posted May 9, 2010 Posted May 9, 2010 I'm having to rethink something similar. Found with MobiLinc. I have a scene that has several SWL controlled by a KPL. 99.9% of the time (until MobiLinc), I would just push the KPL to trigger the scene. If you go into ISY and look at the scene, all SWL have 100% on level and default eramp rates. The on levels for the SWL's is controlled and shows through the KPL button, i.e., 22%, 44%, Full, 52%, etc. I always had what I wanted until MobiLinc. Now if I trigger the scene through ML, I get every light on 100%. Is there a better way to create the scene and have it do what it does through the KPL push? Also if someone could post a fix for the (eventual) change to a SWL when the scene is running, i.e., Kitchen Ceiling is set to 42% in the scene and someone pushes the ceiling full on (esentially breaking the scene). Is there a way to have that switch go back to the scene called level (42%)? Thanks, aLf
Sub-Routine Posted May 9, 2010 Posted May 9, 2010 According to Insteon specs I thought that was the way it should work as well. Okay. I'll do this. Sounds like an anomaly in the way that the switches are designed. Since I am commanding the device directly and I only have the option to command light level, intuitively I would assume local ramp.
Sub-Routine Posted May 9, 2010 Posted May 9, 2010 Hi aLf, The easiest way to do this is to turn on the scene from the KPL. Then the device chart will display the current levels. Change each device level in the ISY scene to match the current (KPL) level. To change a light back to the scene level simply turn the scene On again. A program to watch for a switch press during a time period is not difficult to write. Rand I'm having to rethink something similar. Found with MobiLinc. I have a scene that has several SWL controlled by a KPL. 99.9% of the time (until MobiLinc), I would just push the KPL to trigger the scene. If you go into ISY and look at the scene, all SWL have 100% on level and default eramp rates. The on levels for the SWL's is controlled and shows through the KPL button, i.e., 22%, 44%, Full, 52%, etc. I always had what I wanted until MobiLinc. Now if I trigger the scene through ML, I get every light on 100%. Is there a better way to create the scene and have it do what it does through the KPL push? Also if someone could post a fix for the (eventual) change to a SWL when the scene is running, i.e., Kitchen Ceiling is set to 42% in the scene and someone pushes the ceiling full on (esentially breaking the scene). Is there a way to have that switch go back to the scene called level (42%)? Thanks, aLf
aLf Posted May 9, 2010 Posted May 9, 2010 Rand: I'm not sure I can turn on a KPL button directly fro MobiLinc? Also is it OK to have the levels the same in both the scene and the KPL page? aLf
Sub-Routine Posted May 9, 2010 Posted May 9, 2010 Hi aLf, It is a bit confusing. No, you cannot turn on the KPL scene from MobiLinc, only the ISY scene. When you are home press the KPL so the ISY displays the levels for those devices from that button. Then select the ISY scene and adjust the sliders to match. We thought people would rather adjust the ISY scene first. Then use the Copy Scene Attributes button to make it easy when you add a new controller to the scene. There is nothing to stop you from setting all the levels and ramp rates the same. Rand Rand: I'm not sure I can turn on a KPL button directly fro MobiLinc? Also is it OK to have the levels the same in both the scene and the KPL page? aLf
Recommended Posts