LeeG

Don't know. In Scenes Controllers and Responders are differentiated that way but they are also Blue versus Red so they tend to stand out more by color then font.

Insteon supports only one Scene running at a time. If a device button press is driving a large Scene and a Program tries to start another Scene before the button Scene is finished, one of the Scenes is cancelled.

In the evolution of devices over the life of Insteon, the Insteon protocol has evolved. Starting with I1 (Insteon 1), followed by I2 (Insteon 2), followed by the latest I2CS (I2 Checksum). Depending on when the device was manufactured it will have been built around one of these three protocols. This is known as the device engine. The Query Insteon Engine refreshes the information the ISY has recorded for what engine each device contains. The device engine dictates how the ISY interfaces with each device. Where do you see devices in Italics? In the upper section of the My Lighting tree where all the device nodes are listed or the lower section where the Scenes and related device nodes are listed? Are the device nodes a different color when in Italics?

When the ISY implemented support for turning Off Secondary buttons with 0% On Level it applies only to Controllers of the Scene, not the Scene name itself. You will notice when the Scene name is selected there are no Responders listed so none of the Responders can be set to 0% On Level. This specific problem may be resolved with the next ISY release. “In each of those scenes are all the buttons for the specified panel, except the specified button letter.†Were these Scenes set up to turn Off all buttons but the button that triggers the Program? The results are as expected. Turn the Scene On and all the Responders turn On. These Scenes (without the Controller button) are meant to turn Off all buttons but the Controller. As such the only logical use of these Scenes is Scene Off. “he program is enabled, but doesn't seem to trigger anything on the bedroom panel when I hit the kitchen panel B button. “ Does the Program get triggered (Programs | Summary panel will display last run time) but the Scene does not work or the Program does not get triggered. If the Program does not get triggered try a right click on the KPL Primary node and select Restore Device. If the link records have been lost or corrupted this will fix. If it still does not trigger the Program then a comm problem with the KPL is suspect.

Don't know when the KeypadLinc v.40 firmware first became available. The two I have are approx 6 months old.

No. The ISY assumes it might be defective and already physically replaced. No communication attempt is made to the device being replaced.

In the simple Scene that is initially described, KPL1 button B and KPL2 button B are Controllers in the same ISY Scene. The ISY will cross link the buttons such that either button B On/Off will control the other KPL button B On/Off. In a more complex arrangement where buttons B,C,D have an interrelationship in the devices/Scenes they control such that only 1 of the buttons should be On at a time, that is mutually exclusive buttons, radio buttons, etc. To achieve this three ISY Scenes are needed,. SceneB KPL1 button B Controller KPL1 button C Responder with 0% On Level KPL1 button D Responder with 0% On Level KPL2 button B Controller KPL2 button C Responder with 0% On Level KPL2 button D Responder with 0% On Level SceneC KPL1 button C Controller KPL1 button B Responder with 0% On Level KPL1 button D Responder with 0% On Level KPL2 button C Controller KPL2 button B Responder with 0% On Level KPL2 button D Responder with 0% On Level SceneD KPL1 button D Controller KPL1 button B Responder with 0% On Level KPL1 button C Responder with 0% On Level KPL2 button D Controller KPL2 button B Responder with 0% On Level KPL2 button C Responder with 0% On Level With KeypadLinc v.40 firmware this is all that is needed. With KPL firmware below v.40 pressing a button on KPL1 On will not turn Off the Responder buttons in KPL2. The KeypadLinc firmware does not support the function. To accomplish this for Scene B, an ISY Program is triggered by KPL1 button B On. The Program turns SceneX Off. SceneX has KPL2 button C and KPL2 button D as Responders. Another Program is required that triggers with KPL2 button B On. The Program turns SceneY Off. SceneY has KPL1 button C and KPL1 button D as Responders. This pair of Programs and Scenes are repeated for each of the other KPL1 and KPL2 Controller buttons.

Do not use Mutually Exclusive Groups (Button Grouping). It conflicts with using 0% On Level and it only applies to the KeypadLinc where the button is pressed. Only those Secondary buttons that are functioning in a mutually exclusive relationship should be included as Responders with On Level at 0%. With firmware below v.40 ISY Programs and additional Scenes are needed. Trigger a Program with a particular button On and have it send a Scene Off for a Scene that includes the buttons in the other KeypadLinc (not the KeypadLinc where the button is physically pressed) that should be Off. Secondary buttons in the same KeypadLinc as where the button is pressed will react to the On Level at 0%.

"Should for a scene that is set to use KPL button B as controller, should I make all the other buttons responders and set their state to off?" Yes, for those Secondary buttons that should be Off when another button is pressed. Note that if multiple KeypadLincs are used KeypadLinc V.40 firmware (or higher) is required for KeypadLinc1 to turn Off Secondary buttons in KeypadLinc2 with a Scene On.

Would not hurt to run a test to confirm. It was months ago when I did those tests myself. Things have been known to change (I'm never wrong, maybe not right all the time, but never wrong )..

It does need to be a State variable to change the Folder condition from True to False to True. An Integer can be used to affect True/False but it will not trigger the Folder by itself to change state.

I would assume MobiLinc can run a Program to set a variable. Don't use MobiLinc so can't say from direct knowledge. Maybe it can set a variable directly without running a Program. Does the MobiLinc have a User Guide that can be referenced?

Put all the Programs in a Folder. Set the Folder condition to False which will prevent the Programs in the Folder from running. Could use a KeypadLinc button On or Off to make the Folder False. Could set a State variable to a value the Folder condition checks to create a False condition.

Curiosity got the best of me. Deleted and added with Auto Discover an 8 Scene RL2. Added successfully and status changes are reported. Shows firmware v.36

I've added a Motion Sensor with Auto Discover. It shows v.41 firmware level. Did not go back and delete/readd other RF device types to see if they work. EDIT: I should note that the Motion Sensor is an I2CS device. The path for I2CS devices may support Auto Discover where older devices may not work.

That is normal when the Device Type is specified. It may be possible to use New INSTEON Device with Auto Discover. Some RF devices will add that way. The ISY queries the device for the device type which includes the device firmware level in the response. I've not tried adding an RL2 that way so no direct experience with an RL2 and Auto Discover. The RL2 still must be putting into linking mode manually.

The thermostat has a number of backlight modes. One mode has the backlight on between certain times of day. One mode has the backlight on for a few seconds and then turn Off. The backlight settings are covered in the Thermostat User Guide on 8.2.

Regarding the backlighting question, what mode is defined for the backlighting?

As it turns out I can move the right edge to the left just enough to cover the input field but not get a scroll bar. I run a high resolution so my font size is small enough to get all the fields by default. Hopefully it is just a matter of moving the right edge to the right to expose the Long input field.

Xathros I can drag the right edge of the window to make it larger. If the Java on the MAC has the same capability the input field may just be hidden. Although if I move the right edge to the left to cover Long input field I get a scroll bar which is not present in bmiller's image. I suspect a difference in the Java implementation as there is no Admin Console code specific to MAC

I don't know if this helps or adds to the confusion. I have no problem entering those values with -5 offset. I also have a different field layout, the Lat and Long are separate input fields. Has anyone without an input field to the right of Long field label tried moving the right edge of the window to the right to see if there is an input field that may be covered because of the font size.

On my T2491T1E (T1700 with Insteon dongle internal) the solder tabs labeled No Hum are J4.

The PC board was removed, soldering the back? That is likely a multi layer board so the two solder tabs on the front of the board for no humidity may not be the same thing on the back of the board.

bmiller Run Help | About and verify Firmware and Ui both show 3.2.6. I am on 3.2.6 and have separate Lat and Long input fields.

bmiller Read the post just before your last post. Michel indicates the time offset has to be set to -6 hours before setting Long.