Lighting Settings in a Scene do Not Apply

[jagguar]

When adjusting a Scene, I noticed a while ago that adjusting the "On Level" of a light in the scene by dragging the "level indicator" (I don't know what else to call it) left or right did not seem to work. I can see the setting changed in the GUI, but ISY didn't stop and think for a moment (like it usually does when applying an adjustment). However, if I clicked on the line to the left or right of the "level indicator", then the difference did work correctly. So when I wanted a light setting to be 0%, I got in the habit of dragging the "level indicator" to 10%, and then clicking to the left to adjust it to 0%. After clicking, it applied the setting, and it worked.

 

Now first of all, this problem shouldn't be occurring. I would like it to be fixed. Second, the workaround that I found doesn't seem to be working consistently. I just added a few new devices, and I can't get the to respond they way that ISY shows they should. Additionally, this time around, the adjustments seem to apply... at least as far as the ISY reports. However, when I apply the scene from the switch (Keypadlinc-D really), these latest devices do not turn off. However, another interesting point is that if I apply the scene from the ISY GUI, then it works perfectly.

 

Does anyone have any ideas of how I can get this working the way it should be?

[Michel Kohanim]

Hello jagguar,

 

What's your ISY's firmware version?

 

With kind regards,

Michel

[LeeG]

jagguar

 

I have seen the slider issue from time to time and took it to be a Java problem rather than an ISY problem. The last user that noted the problem updated to the latest Java and no longer has the problem. Don’t know if that fixed the problem or it is just intermittent.

 

Note that each Scene Controller has a different set of On Level and Ramp Rate values for the Responders.

 

If you click on the Scene name and set the Responder values there, they have an effect when the Scene name is used in a Program or the Scene is manipulated from the Admin Console. Using a different Controller, such as KeypadLinc button D, there are a different set of Responder On Level and Ramp Rate values. Click on KeypadLinc button D below the Scene name and check the On Level values defined.

 

If they are correct whet devices are not responding to the On Level values and what are the On Level values set for Controller KeypadLinc button D?

 

Lee

[jagguar]

Hey guys,

I had been running ISY 3.1.17, but just upgraded to 3.2.2. The upgrade doesn't seem to have had an effect on this issue. And I'm using Java 6 Update 31.

 

To be specific, I have a scene called "Going out at night". The only controller is "Central Keypad - D". Every other device in the house is a responder to the scene. When I have the "Going out at night" scene selected, I can see that every "On Level" slider on the right is set to 0 except for "Entry Way" is at 100, which is the way that it should be. If I select the "On" button at the bottom of the GUI, then everything turns off in the house and the Entry Way turns on. This is what I expect from the scene. However, if I tap the physical switch Keypad - D, then everything turns off except for 5 lights that always come on. I just realized that 3 of those lights are ceiling fan lights using FanLincs. The other two lights share at least one scene with one of those FanLincs.

[LeeG]

The Responder On Levels for the KeypadLinc button is not what you are seeing when the Scene name is selected. Click on the KeypadLinc button node name just below the Scene name. The Responder On Levels now displayed are those in affect when the KeypadLinc button is pressed.

 

Are these new FanLincs, purchased in the last week or two? If so they are I2CS devices which must be added to the ISY under the 3.2.x image and the Scenes with the FanLinc created under 3.2.x.

[jagguar]

Holy shit, that worked! Thank you so much. So is the intent to allow multiple responders to have different effects on a scene?

 

I bought these FanLincs the moment they hit the market. I'd been waiting for them for months. They're Rev 1.0, which presumably means they're not I2CS. I forget, what does I2CS mean? And what does mean I'm lacking in my units?

[LeeG]

“So is the intent to allow multiple responders to have different effects on a scene?â€

 

For each Controller, each Responder can have a different set of On Level and Ramp Rate values.

 

Scene A

KeypadLinc button B

LampLinc A

LampLinc B

 

When the Scene name “Scene A†is used in an ISY Program or controlled through the Admin Console

LampLinc A can have On Level 30% Ramp Rate 2 seconds

LampLinc B can have On Level 50% Ramp Rate 5 seconds

 

When KeypadLinc button B is the Controller (KeypadLinc button B pressed)

LampLinc A can have On Level 40% Ramp Rate .2 seconds

LampLinc B can have On Level 100% Ramp Rate 1 second

 

The On Level and Ramp Rate values are stored in each Responder keyed to the Controller address so each Responder can have unique values for each Controller.

 

Rev 1.0 FanLincs are not I2CS. I2CS adds additional validation for long Extended messages. There is no difference in external function. Looking at a house full of I2CS devices an additional level of validation will catch powerline issues more effectively.

 

I2CS is I2 Checksum. An additional level of message validation exists with I2CS for Extended messages. It is like other evolutions in the Insteon protocol that have occurred over the years. Often these changes go unnoticed. In this case I2CS requires changes to all the applications like the ISY so it is more visible.