Michel Kohanim

black_fx_35, My pleasure! The IR version should suppor any remote with signals at 36-7KHz (most universal remotes) and should be seamless. We have not tested with Logitech yet but it's a universal remote running within those frequencies. With kind regards, Michel

black_fx_35, We do have an IR enabled version planned for later this year. The price is going to be a little higher. Or, if you don't want to wait, you can always use an IR/X10 bridge and use the X10 to trigger INSTEON actions. With kind regards, Michel

sfhutchi, Yes, you are right! With kind regards, Michel

Hi Mark, No. Not fixed yet ... it's pretty hard to reproduce. With kind regards, Michel

siegeld, Excellent. We shall have it out to you by the end of the week. Thanks so very much, With kind regards, Michel

sfhutchi, Eventually, YES but not yet in this drop. With kind regards, Michel

siegeld, We are testing it as we speak. Do you currently create/manage schedules/triggers from within the JSDK library? If not, then we can possibly have something available with in a couple of days. With kind regards, Michel

jlevans, Apologies for the inconvenience. Please send an email to tech@universal-devices.com and we shall send you the latest update which fixes this "bug". With kind regards, Michel

Mark, Thanks so very much. The colors are pretty much consistent. I am still a little baffled by: ISY Local/Scene ISY Local What do they mean? With kind regards, Michel

Rand, Excellent suggestion ... I've put it on our list to review. With kind regards, MikeB, Part of the problem with Dim/Brighten a scene is that all devices step to the next of 32 levels. Some devices may change as much as 3% and others only 0.39% So, Yes, you are most likely to be happier with a new scene. Along with Set All Devices I would like to see a slider to modify the levels of all the devices in a scene using a percentage. Perhaps 0-100% slider with a toggle next to it to select Dim or Brighten. Dim would start at 100% and brighten would initially be 0%. Using Dim for example: Set the slider to 50% and devices that were 79% become 39.5%, 64% becomes 32%, etc. Dim and Brighten All Devices In A Scene was next on my list for Group Commander. I think after you get the ratios correct among the devices in a scene it could come close to being a mirrored dimmer or brighter scene. Something logarithmically related to light output versus power level would be more accurate. That could keep the ISY team busy for a while I'm not sure if anyone would have a use for the same function with ramp rates, that is already proportional to the level. Thank you, Rand

Mark, Thank you. It shall be analyzed and resolved. With kind regards, Michel

C Martin, Thank you for the suggestion: we have now made it bold (in the next drop). With kind regards, Michel

sloop, I am so very glad you are up and running again. From the little I gather from your post, I can immediately guess that you are running out links in your PLM (currently, 417 maximum). SmartHome is testing a new PLM which has support for 1024 links. I shall send you instruction on how to get one. As far as the order in which you put the devices in scenes, YOU'VE GOT IT ... with that order, you have overcome the KPL limitation (load/sub button) while keeping the total time to program devices to the minimum. Thanks so very much for the "retry", With kind regards, Michel

Mark, Cool. It's settled then. We'll try to come up with some type of dialog/text to describe different scenarios. With kind regards, Michel

Rand, And, as usual, you come to the rescue! You are right right on about the pop-up asking the users to air-gap their non-KPL devices when the local settings have changed. As far as the labels, anything that would make it easier for the users to understand the relationship between ISY/devices/scenes is surely a step in the right direction. I think the main issue is that have not been able to efficiently explain this relationship nor has it been captured on ISY in such a way that makes sense. Thanks so very much, With kind regards, Michel

Jon, Just to make sure we are in synch: Movie Scene KPL A -- Controller .... make sure the sub-button is added before the load KPL Load -- Controller SWL -- Controller In the above scene EVERYTHING works except for having KPL A apply a different on level/ramp rate for KPL Load. Other than that, everything else should work. i.e. if you click on KPL A, then KPL Load will turn on/off. Yes, triggers will work but I think they would be an overkill for what you're trying to accomplish. With kind regards, Michel

Mark, Thank you! Anything you do with ISY, and if it has any impact to any device, it's stored. I am afraid that the concept of "Stored" may have some other connotations that would require more explanation rather than acting as clarification. You already have the answer to your last question. The scene itself will ALWAYS run from ISY. There's no other way. The controllers within a scene, will ONLY run if someone actually/physically alters their state. You cannot run controller scenes from ISY. You simply can't because INSTEON does not let you act on the behalf of another device. Now, the last item is the on level/ramp rate for the controller itself when it's controlling the scene. Obviously, since you are physically changing that controller, THEREFORE the on level and ramp rates are the local ones. So, what am I missing? With kind regards, Michel Stored means where the link/level/rate data is stored. You always have a copy of the data in the ISY. You don't always have a copy of the data in the device. As in the case when the keypadlinc load with non-load you don't store the data in the keypadlinc only in the ISY. So your saying these would be the four naming options that would end up over the slider names like I demoed above? Scene == Stored ISY & Device Scene Local == Stored Device Only Controller == Stored ISY & Device Controller Local == Stored ISY Only I can hang with the Scene, Controller, Local idea if that is what you go with. The end result I am trying to reach is a way to see if the scene is going to need me to run it from the ISY directly, because it is not going to run with a complete result from the device.

Jon, My pleasure. INSTEON has a single address for all the buttons on a KPL and, thus, you cannot send a group command from one of the KPL's sub-buttons (i.e. b,c,d, e...) to the load. In short, if you have the KPL load button and one (or more of its sub-buttons) in the same scene as controllers, then when you click on any of the sub-buttons, it can only turn on/off the load to the local preset levels just as if you are clicking the load button itself. With kind regards, Michel

Mark and sceaton, Thank you so very much for the feedback. I think we are close: 1. Mark, I am not sure what you mean by "Stored". ISY stores everything and, as such, the terminology gets more confusing. But, I like the idea of "Local" 2. sceaton, at the moment, I love your idea to spell it out: These sliders adjust On Levels and Ramp rates when controlled by " where controller could either by ISY or the actual controller's name So, this way, we should have the following: Scene - Adjusts the on levels/ramp rates when activated by ISY Controller - Adjusts the on levels/ramp rates when activated by Controller --- Add local when the Controller = one of the sliders on the right What do you guys think? With kind regards,

Jon_W, Welcome! No, your configuration is correct. Here lies the issue that you are running into: You have a KPL (or any other switch for that matter) which is a controller for a scene for which it, itself, is a responder. This means that when you click on that switch physically, you want the "load" for that switch to do something specific (on level/ramprate). This is equal to the local on level/ramp rate for that device (root device config as you referred to it). Please note that you can have a different on level/ramp rate for your KPL's load when you click on the SWL. Furthermore, you can have a different on level/ramp rate for your KPL's load at the scene level (Movie). Please do let me know if this makes sense. Thank you and with kind regards, Michel

Mike, Dim/Bright/FON/FOFF will be added in the next drop. This said, however, INSTEON does not allow sending a group command (to a scene) with the desired on level. That's why device, within a scene, has its own onlevel and ramprate. In short, you cannot issue something like: Set Scene x to 50% You can always do: Set Scene x to Dim/Bright which simply brighten/dim the scene on notch. With kind regards, Michel

Mark, Good idea. With kind regards, Michel

Mark, Sounds good but Global is not the right word since it's only applied at the scene level. With kind regards,

siegeld, My pleasure ... please don't hesitate to contact us with your questions vis-a-vis JSDK. With kind regards, Michel

aLf, You are 100% correct. I am sure that there "must" be a solution out there so let me see if we can come up with it. Thanks and with kind regards, Michel