larryllix

These programs do not modify scenes. Insteon scenes are between devices and ISY has management tools to modify them. Scenes in your case can be used to group devices into looking like one device to ISY but you have no controllers in your scenes to operate outside of ISY.

That is pretty difficult, using the same SwitchLinc dimmer paddle and the dimmer circuit. hey are connected inside and the dimmer will turn on to whatever level it is set to when the paddle is clicked at the top. This will result in initially turning your light on to whatever the local level is, and then make a program or scene take over and may result in annoying flashes at 100%. However I have done it by setting a slow ramp into the Switchlinc dimmer...say 2.0 seconds and then beating the ramp response with an ISY program. You need to access the admin console devices page and set the ramp speed to about 2.0 seconds. If ... control Switchlinc is switched 'ON' Then ... run program2 (If) Else ... --- Program2 (disabled) <--- we don't want these times triggering this by itself If .... from 8:00 AM ... to 8:00 PM Then ... set Switchlinc 100% Else ... set Switchlinc 20% Get rid of the scenes in the devices as they will confuse the response and the owner. OR You can keep the scenes without a controller item installed and use the above programs to run you scenes instead of just one SwitchLinc. You will have to program the scenes to preset your bulbs to levels desired first.

Use two programs Program1 If ... triggering units send Then ...call Program2 (if) Else -- Program2 If -- Then ...Disable Program1 ...Do something ...Wait a few seconds ...Enable Program1 Else -- BTW; Your Wait waits for nothing that follows. and Right click on your program in the program tree and select "copy to clipboard"

No. Two different devices. One contrller, like an MotionSensor or a SwitchLinc, and one responder, like a LampLinc or SwitchLinc light controller. Note that a switchLinc is really two devices, a paddle controller, and a dimmer, responder.

Yes. but you have to have a scene with a controller and a responder. http://forum.universal-devices.com/topic/17495-how-to-use-a-ms-with-lights/

In your scene adjustment you need to scroll the scene pull down list to the other end, and select the controller units, that are not really scenes.

Stu is correct. This takes two programs to isolate the negative trigger from the sequence.

Twin Light Dim - [ID 0016][Parent 0019] If Status 'Twins Room Light' is Off And Control 'Twins Room Light' is switched Off Then Set 'Twins Room Light' 35% Wait 6 seconds Set Scene 'Twins Room Light - Very Slow' Off Else - No Actions - (To add one, press 'Action')

OK then the logic I gave you is close except for the mobilinc input. Some things. Scenes cannot be detected. They have no status. Devices can be detected and have statuses. I am wondering why you want to use mobilinc to turn on the scene for the night lights when there are many ways to do it easier or automatically? How many MS units are involved and should all lights referred to be involved with the response or just hall lights for wanderes at initial bedtime runs?

I really don't completely understand what you want but from my best guess, here is the logic. To turn on your night lights If ...MS.motion is switched ON <-----use the motion sensing node, not dark node ...And from sunset +/- X minutes ..........to sunrise +/- Y minutes <--- this triggers Else section Then ...set some lights to 25% ...Wait 12 hours <---just in case ...run This program (else) <----turn them off in morning Else ...set the same lights Off For the extra lights If MS.motion is switched On <---use the same trigger as many times as you like Then ...turn on other lights ...Wait 1 minute 30 seconds ...turn off other lights Else ---- Make sense? Need more help just keep asking.

Then you must have changed your lines to status, no? Switched has no false. It is a trigger and is happenning or not happenning. Status has two logical states..true and false.

See my previous post. Check your links. Then you will know what may have happened.

Then it would seem your signals are not getting into ISY. Check your links from each device and do an ISY link compare (button on report box) If different do a restore

OK. When either of your KPL buttons produce an On your program should trigger Then. When your KPLs produce an Off signal there is no program to trigger that detects the 'Off' signal. IIRC there is no status for KPLs? Try this to capture Off signals and run Else. If ( Control 'KPLs / Kitchen KPL / Kitchen KPL D (Door Sensors)' is switched On Or Control 'KPLs / Deck KPL / Deck KPL D (Door Sensors)' is switched On ) AND Control 'KPLs / Kitchen KPL / Kitchen KPL D (Door Sensors)' is NOT switched Off AND Control 'KPLs / Deck KPL / Deck KPL D (Door Sensors)' is NOT switched Off I am not sure where the parenthesis formatting falls but the AND has a higher precedence so the OR lines have to be grouped.

Just a few things t think about You have no program triggers based on motion. You have a time delay after all other lines of program code. You are waiting for nothing. I don't know what 'fade down' does. I have never used it.

What are your trigger KPLs set up as? Programs look OK, but if the KPLs can't produce and 'On' then this would make sense. Have a look at the options for the KPLs and there should be no 'Off' setting enabled.

Can your KPLs produce anything except 'On'? If not, what would run Else to disable your Chesapeake program?

The original programs may be race dependent, and work sometimes having two programs hit on a lamp for the last word on the setting.

Your last line in the first program cancels the scene ramping and sets the lights to 35%. ISY programming is not concurrent but threaded style. You call the scene control program it it spawns off to do it while the next line sets the lamps to 35% nullifying any scene action that has already taken place. Switch the lines order and insert a Wait 1 second between them. or Just write a delay loop with dimming in each loop, as Stu suggested above. If you have v5.xx you can examine the level, and subtract x% from it each time.

My apologies. I missed the "nor" there. Follow Stu. I had to factory reset my 2441ZTH units sometimes a dozen times and link them before one acted properly and one newer version never did. Both report OK but control will not work for the newer firmware,

If you have a group/ungroup menu it is for a reason. That means ISY sees more than one Node at that address.

I hear ya. Each bulb type seems to have a different curve and I usually want the bottom reliable brightness level. That does make it hard to find one percentage level that would fit all. I have some that use about 10%, some 12% and some that don't work reliably below about 17%. With voice operating three or four scenes that level would have to be programmed for each application/bulb and then the spoken phrases could be standardised. So when we use the "brighten" command the step could just be in 3-4 discreet clicks and operate those on user presets matched to that bulb/device.

What Teken said above. ...also scenes do not have the security of transmission signal that straight programmed signals do. Regular Insteon signals have confirmations and retries upon failures that, as I understand it, scene signals do not. I only use scenes for large groups or to tie two devices (think MS and lamps) together, making them independent and faster than ISY can do.

Yeah but the LED bulbs don't appear to follow a consistent curve either. I had to replace one CREE bulb in a dining room fixture of 5 bulbs. Despite being the same power rating CREE, they changed their style and it dims differently than the other four. Looks awful about 15-25% . I guess back to your point I don't think people need all these 0-100% either. Ramping is one thing, for looks, but people don't need many "clicks", just maybe full, medium, low, very dim. We don't need to have 48, 49, & 50% for fan speeds either.

Sure it is. log2( 6.25 / 3.125) = 1 log2( 12.5 / 3.125) = 2 log2( 25 / 3.125) = 3 log2( 50 / 3.125) = 4 log2( 100 / 3.12 5) = 5