LeeG

Run Tools | Diagnostics | Event Viewer at LEVEL 3. Right click on Program name and select Run Then. When Program completes tap the On paddle of 'Master Toilet Light'. Light should turn On to 30%. At the bottom of the Event Viewer popup, next to last Icon on right, does a Copy to Clipboard of event data. Paste that into forum post.

Joe Making more nodes available by deleting devices would not make the missing KPL buttons appear. Was necessary to Delete KPL and add it back to get all the KPL nodes. I would count the number of device nodes, folders and Scenes to see if max has been reached as Michel suggested. Also that KPL level (v.44) being added on 3.3.10 could explain the node problem.

As Techman has already indicated, the 2477D should be a Controller in the ISY Scene. That along with the changes to the Adjust Scene statements I posted will allow the paddle on the 2477D to set the desired On Level and Ramp Rates. Again, using the ISY Scene name in the Adjust Scene statements applies only if a Program is issuing Set Scene 'Bath Light Night' On/Off.

KYnewbie I think some information Insteon Scenes would be useful. ISY Scene Bath Light Night Master Toilet Light - Controller - SwitchLinc The ISY Scene (maybe called Bath Light Night ?) is used in a Program with Set Scene 'Bath Light Night' On/Off. Using 'Bath Light Night' as the first parameter In Scene affects what happens when the ISY Scene is used in a Program. In Scene 'Bath Light Night' Set 'Master Toilet Light' 30% (On Level) In Scene 'Bath Light Night' Set 'Master Toilet Light' 2.0 Sec (Ramp Rate) Based on the info provided, the above In Scene statements have no affect on what happens when the SwitchLinc is operated. What is needed are In Scene statements that affect what happens when SwitchLinc paddle is pressed. In Scene 'Master Toilet Light' Set 'Master Toilet Light' 30% (On Level) In Scene 'Master Toilet Light' Set 'Master Toilet Light' 2.0 Sec (Ramp Rate) I have made assumptions on names used. If the ISY Scene or SwitchLinc names do not match please provide actual Scene and SwitchLinc names. Also note that the In Scene statements in Then execute only at 11:58 PM and the In Scene statements in Else execute once at Sunrise - 1 hour 30 minutes.

Right click on Low Bat node. Select Query to reset Low Bat. The Motion Sensor is not actually queried.so no need to put Motion Sensor into linking mode.

A Program in a Wait does not stop other Programs in a Wait. Program 1 could be in a 30 minute Wait. That will not stop Program 2 in a 5 minute Wait.

The image in post #6 was not helpful. That is the ISY Links Table display. What is needed is a Tools | Diagnostics | Show Device Links Table when the module has turned On when receiving the Scene On command. Also need Insteon address of KPL and which button is pressed.

Thanks for positive feedback.

That is not correct. I have a REV2.3 hardware Leak Sensor. It is an I2CS device and does report Heartbeat On every 24 hours (nominal). There is no Low Bat for Leak Sensor.

No need to have a load connected to 2487. Simply put wire nut on the Red load wire (no load attached.). Devices that are in 3,4,5 way arrangements often use only one device to drive a load and there are configurations where none of the devices physically power a load.

Define a Scene (Buttons A D) that has buttons A, D as Responders on 2487 devices. If Control 'Den 1 - On Off' is switched Off Or Control 'Den 2 - On Off' is switched Off Then Wait 1 second Set Scene 'Buttons A D' Off Else

The simple answer is this AAAA3 Copy - [iD 0030][Parent 0001] If X10 'F2/On (3)' is Received Or X10 'F2' is Received Or Control 'KPL Test 3 - C' is switched On Then However, it will not take long to wonder whether KPL button should be On, Off after being pressed. There are non-toggle On and non-toggle Off modes a KPL button can be configured as. This could affect the command being used in If to trigger KPL. Need to think about how KPL button LED should react when pressed to start with.

Should not create a problem. Mine is also I2CS. Three is what all 120v devices used before I2CS. It means that a good transmission takes more mili-seconds to account for potentially more hops but the Smoke Bridge sends so few messages it makes no meaningful difference.

"I do have it so that I can turn the light on only using "fast on" and if I select "off" on the scene it will have the desired effect. But if I use the normal "on" process it basically runs the scene and does a ramp up at the Scene Rate (slow) rather than the rate I have on the device itself" This is normal Insteon Scene behavior. The Responder turns On and Off at the Scene ramp rate. The device can be turned on with a Direct command where Ramp Rate (applied locally) controls the Direct command ramp rate. Then use the Scene to turn the device Off which ramps at the Scene ramp rate.

Paul Thanks for the feedback and great news.

A 9 minute ramp rate applies only to very old devices. For the last several years 8 minutes is the max ramp rate.

Paul, Could be a link record problem. Both the On and Off messages for Smoke and CO nodes did not get posted to the respective nodes. If nothing is resolved after factory reset and relink of Smoke Bridge run Event Viewer at LEVEL 3. Run the Smoke Bridge Set button test and post the Insteon message trace. Could also be a Smoke Bridge failure but that is far down the list.

Paul, This is what I posted about Low Bat and Malfunction nodes when Set button test complete. What is different about your results? "From memory the Low Bat and Malfunction nodes will turn On. When test is complete right click on Low Bat node and select Query to turn Low Bat Off. Same sequence is needed for Malfunction node to reset it to Off."

The KPL is manufactured as a 6 button device. That is why the ISY indicates it as a 5 node device. If properly converted to 8 button mode it will have 8 nodes. Should be on 4.3.26 which is an Official release, or 4.4.3 RC1. One of the possible issues is the button D on a 6 button device is button F on an 8 button KPL. If the Programs are referencing button D the wrong button is being referenced. Are the Programs referencing button D or button F?

Press the Set button on the Smoke Bridge for about 1 second. When released the Smoke Bridge LED will change to Red and several Insteon Messages are sent. The Smoke and CO nodes will cycle to On, then to Off. From memory the Low Bat and Malfunction nodes will turn On. When test is complete right click on Low Bat node and select Query to turn Low Bat Off. Same sequence is needed for Malfunction node to reset it to Off.

Sorry I did not put this in previous post. A Mini-Remote does not have Bright/Dim buttons that raise or lower a small percent for each Bright/Dim button press. See the Specs section on Smarthome site for possible commands. Scene Commands Supported: On, Off, Begin Brightening, Begin Dimming, End Brightening, End Dimming, Fast On, Fast Off

Ok, thanks. When a Mini-Remote On button is pressed and held the command sequence from the Mini-Remote starts with a Fade Up. When the button is released a Fade Stop is issued. Fri 02/12/2016 10:10:57 PM : [iNST-SRX ] 02 50 1C.2D.53 00.00.01 CB 17 01 LTMCON (UP) - Fade Up Fri 02/12/2016 10:10:57 PM : [std-Group ] 1C.2D.53-->Group=1, Max Hops=3, Hops Left=2 Fri 02/12/2016 10:10:57 PM : [D2D EVENT ] Event [1C 2D 53 1] [bMAN] [1] uom=0 prec=-1 Fri 02/12/2016 10:10:57 PM : [ 1C 2D 53 1] BMAN 1 Fri 02/12/2016 10:11:01 PM : [iNST-SRX ] 02 50 1C.2D.53 00.00.01 CB 18 00 LTMCOFF(00) - Fade Stop Fri 02/12/2016 10:11:01 PM : [std-Group ] 1C.2D.53-->Group=1, Max Hops=3, Hops Left=2 Fri 02/12/2016 10:11:01 PM : [D2D EVENT ] Event [1C 2D 53 1] [sMAN] [0] uom=0 prec=-1 Fri 02/12/2016 10:11:01 PM : [ 1C 2D 53 1] SMAN 0 Fri 02/12/2016 10:11:01 PM : [D2D EVENT ] Event [1C 2D 53 1] [sT] [221] uom=0 prec=-1 Fri 02/12/2016 10:11:01 PM : [ 1C 2D 53 1] ST 221 Fri 02/12/2016 10:11:01 PM : [iNST-SRX ] 02 50 1C.2D.53 00.00.01 C7 18 00 LTMCOFF(00) Fri 02/12/2016 10:11:01 PM : [std-Group ] 1C.2D.53-->Group=1, Max Hops=3, Hops Left=1 Fri 02/12/2016 10:11:01 PM : [iNST-DUP ] Previous message ignored. An example Program would look like this RL2-4-B - [iD 009F][Parent 0001] If Control 'RL2-4 - A' is switched Fade Up Or Control 'RL2-4 - A' is not switched Fade Stop Then Set 'LampLinc3' Fade Up Else Set 'LampLinc3' Fade Stop There are inherent issues with this. The Program has a delay compared to a Scene. This will make the LampLinc out of sync with the Mini-Remote On Level.

Pressing a button on a Mini-Remote requires a Scene to alter the LampLinc. Not clear what an ISY Program is attempting. Can you post the Program

1. In the Administrative console Main Tab/Network/Isy I see all my modules in a red color. Does this mean they are linked to the ISY? I could not find anything about color indicators in programs in the user manual. All modules listed under ISY are added (linked) to the ISY. The color of the device node name indicates Controller (Red) or Responder (Black). 2. “Note: Unlike Scenes, Programs require that the ISY be online in order to function.” Does this mean it must be connected to some type of 'home base' constantly via the internet. I thought that the ISY was a stand alone controller. I do notice that the network lights on the back are blinking. I ask this because none of my programs run. The ISY does not need to be connected to the External Internet (if that is the question). Example program in the Programs Tab; This Program has a coding error. Sunset varies by location but is in the area of 5-6 PM. The "To" time of 12:45 PM is before Sunset, Noon +45 minutes. If looking for something before midnight it would be 11:59:59 PM (same day) or earlier. If looking for a "To" time 45 minutes after midnight it would be 12:45:00 AM (next day). If From Sunset – 2 minutes To 12:45:00PM (same day) Then Set 'Living Room Can' On Else Set 'Living Room Can' Off

Try this one http://forum.universal-devices.com/topic/18153-i-couldnt-find-any-connected-home-devices/