GodOfCheese

I have a few simple dim-at-sunset/brighten-at-sunrise programs and have been trying to debug them. Originally I was using a folder with sunrise scheduling, but it was hard to debug. So instead I set a state variable to control "brightening", "dimming", and "normal" state and have folders keying off those state variables. What I noticed: the folder status (set by the variable in response to schedule) is correct, but the program status (set by the devices) is not. If I Query the devices involved, then suddenly all the programs run and the system behaves as expected. Why wouldn't the device states be accurate? Is this indicative of a communication problem? For reference, here's a snippet of the programs I'm using: 2. Start Brightening at Sunrise - [iD 0010][Parent 0022] If Time is Sunrise Or Time is Sunrise + 1 hour Or Time is Sunrise + 2 hours Then $Kitchen_Light_State = 2 Else - No Actions - (To add one, press 'Action') I have a "Brightening State" folder: =================================================================================== 2. Brightening - [iD 000D][Parent 0022] Folder Conditions for '2. Brightening' If $Kitchen_Light_State is 2 Then Allow the programs in this folder to run. In the folder, I have a variety of programs like this: Brighten KL if on - [iD 0043][Parent 000D] If Status 'Kitchen Dimmer - Entry Master' is not Off Then Set Scene 'Kitchen Main Lights / Kitchen Mains Slow Bright' On Else - No Actions - (To add one, press 'Action') ...and a "done" program: Done if lights are bright or off - [iD 000F][Parent 000D] If ( Status 'Kitchen Ceiling Fan-Light' is Off Or Status 'Kitchen Ceiling Fan-Light' is 100% ) And ( Status 'Kitchen Dimmer - Entry Master' is 100% Or Status 'Kitchen Dimmer - Entry Master' is Off ) Then Wait 5 seconds $Kitchen_Light_State = 0 Else - No Actions - (To add one, press 'Action')

Literal LOL! That all makes sense now! Thanks!

(this programming is my workaround for http://forum.universal-devices.com/topic/19943-ramp-rates-not-being-honored/. Even if it turns out not to be necessary by fixing the ramp rates, I'd still like to understand how I can run a program periodically but recover or prevent missed execution times...) Thanks!

I'm trying to dim the lights in a scene very slowly, however it seems that my switches are ignoring the Ramp Rate settings for the scene. The scene contains only three Insteon 2477D.v45s as controllers. I set the ramp rate on the scene to 9 minutes, wait a few seconds, then set to On, but the lights rapidly dim to the target level using the default rate of 0.1s. I've also tried creating a second scene using the three as responders, always having the ramp rate set to 9 minutes, and always with the target level set to like 20%. No dice-- still uses the 0.1s ramp rate. Then it occurred to me that the individual devices in the scene might need their ramp rates set locally, so I made sure to drill into each device in the scene and set the ramp rate to 9m. Still dims in less than a second. What am I missing here? Thanks!

I am trying to dim certain lights simultaneously at rates so low that my wife and kids won't notice. The right thing to do is probably to use a Scene, but I am having unrelated problems with it (separate post to come). Essentially, I want to Dim the lights every ten seconds or so. Very simple. Unfortunately, sometimes the dimming gets stuck at like 63% and never reaches 15%. I suspect this is because the ISY misses the timing interval and so the if-clause is not triggered. Is there a more reliable way to trigger this on a cadence? I thought about just having a ten second wait after the dim and running while the light was >15%, but would more than one copy of the program run during the wait interval? Background: I put the lights in a dimming state with the '2. Start dimming' program, and exit the state when all the lights I'm dimming reach the appropriate levels OR are off (I don't want to dim lights that are already off). The dimming programs all look like this one, but with different scenes, and all are in a folder gated by being in the dimming state. The "Kitchen Ceiling Fan/KCF Light" scene is one button of a KPL and a FanLinc. The program is pretty simple: 2. dim KCF manually if bright - [iD 0037][Parent 0033] If Status 'Kitchen Ceiling Fan-Light' > 15% And ( Time is Last Run Time for '2. dim KCF manually if bright' + 10 seconds Or Time is Last Run Time for '2. Start Dimming' + 10 seconds ) Then Set Scene 'Kitchen Ceiling Fan / KCF Light' Dim Else - No Actions - (To add one, press 'Action')

Many of my family members have smartphones. Is there any way for me to give them different usernames and passwords, or at least to create a user who does not have admin privileges on the ISY and have them share it?