ulrick65

No, I am sure what Michel was referring to was the ISY Firmware. Currently there is no way to update firmware for Insteon devices in the field. Much debate on that one...but for now, Smarthome is not making that available.

For the additional Keypadlinc, drag the second button to the scene and drop it (or right click on it and go to "Add to Scene" and select the scene you want to add it to). Add it as a Controller for the scene and it will work as you expect. I can't help with the second question, I don't have an IRLinc.

The only way to do this is to go into each scene, click on the controller and click on "Copy Scene Attributes from..." this sets each device to the same settings as the scene...but you have to do it for each controller.

The Remote Linc shows up in the device tree just like any other device. What problem are you having with it? Are you not able to get it to link at all? Hmmm... okay... maybe it's working, then. It only takes a minute or so for the progress bar to go away and the solid light on the RL goes back to flashing. Does that mean it's done? If so, where is the device represented in the UDI console software? How do I link it to things in the software?

It's not really strange if you consider how it's working: Anything higher than 0% is ON to the KPL so issuing a Brighten command must mean the light is either ON or turning ON and the LED will come on (the LED does not respond to brightness levels, just on and off). So as you brighten it, it will be on each and everytime and when you get 100% it is still on so it appears to be "in sync" even though it really does not know you are at 100%. However, as you DIM the only thing the KPL knows is that you are dimming...when you get to 0% it has no way of knowing that (it never saw an off command) so it is still ON...which is NOT "in sync" any longer. As Keith said, this is not a bug really...perhaps maybe a flaw in the design of the KPL.

You didnt post the program that you are using to call the first program, so it is hard to say why they keep repeating. However, in the first program you are calling the Then statements of the second program and therefore bypassing the If portion all together. Edit: Jimmy beat me to the punch...sorry for the duplicate answer.

Yes they do. A couple different versions. There is a cheaper 1 input 1 output version coming out soon (that means whenever it gets here in Smarthome time). Other than that, here's one currently available: http://www.smarthome.com/31283/EZIO40-INSTEON-4-Output-Relay-Load-Controller/p.aspx Now, you could build your own as you said with a Switchlink Relay (I wouldnt use a dimmer...just because) and your own little relay that you get from radio shack.

Someone else can jump in to correct me in case I am mistaken, but I am 97.4% sure that this is not possible without doing it with programs. Once you introduce a second controller to the mix, the mutual exclusivity does not function.

So I assume it worked correctly after that? Off to the Aquarium today with the family... No automation playtime for me today according to the wife!

I think I see the problem...it is in the folder conditions. The switch must be toggled off once to get the thing jump started. I did not have this problem, because I tested the folder conditions right away when I put it in. I will take a look (and please, someone jump in if you have a fix) but in the mean time, try putting it back it in and then check the Folder on the program summary tab...I am betting it will be FALSE. Tap the light on then tap it off and it will go TRUE then it will start working correctly. Let me know what you find. Thanks.

With some creative programming in ISY you can do all of those things with the Venstar. However, you don't need the 7 day programmable one...since you will be doing all the programming with ISY anyway...unless you need the other features of it for some reason. I got this one: http://www.smarthome.com/2491T1/Venstar-Thermostat-INSTEON-Remote-Control-Thermostat-1-Day-Programmable/p.aspx It works perfectly and controls the AC and heat. Unless you need duel fuel, this one should work fine.

Wayne, Can you post the folder conditions you have and the program that you have? I've tested it and it works...though I simulated the motion sensor with a keypad button...but should work the same. Thanks.

What I wrote gives you that ability. In fact, it works just like your 5 programs do, only with 1 program and folder conditions. If you tap the OFF button, it will shut off the light and re-enable the motion sensor. The only thing that wouldn't is the very last (optional) program that I posted just in case you wanted to turn the light out after a long period of time if someone forgets. This is optional and not needed to work like you stated in your updated requirements. If someone turns on the light manually, it will stay on forever (and the motion sensing will stay disabled) until they tap the off button....which is the same way it works in your program.

Assuming that you want to use the off time setup in the motion sensor (which is how you have your programs setup) then I would do it this way: In my example, the light is called "Test Light" and the motion sensor is called "Test Motion Sensor". Setup a Folder for it (I called it Test Motion) with the following conditions: Folder Conditions for 'Test Motion Folder' If Control 'Test Light' is not switched On And Control 'Test Light' is switched Off Then Allow the programs in this folder to run. Whenever someone turns on the light, it will disable the program(s) in the folder. Inside this folder is the following program: Program Name: Test Motion Control If Control 'Test Motion Sensor' is switched On And Control 'Test Motion Sensor' is not switched Off Then Set 'Test Light' On Else Set 'Test Light' Off This should work as you want: When someone enters the room, the light will turn on when the motion sensor sends the on command and will turn off when the motion sensor sends the off command. If the person taps the ON button on the light control, it will disable the folder conditions and consequently disable the motion program from working. It will stay disabled until someone turns the light out by tapping the OFF button. You could add the Fast On and Fast Off buttons accordingly if you want. You could have another program that waits a LONG time, then turns the light out (just in case someone forgets) like this: Program Name: Test Light On To Long If Control 'Test Light' is switched On And Control 'Test Light' is not switched Off Then Wait 1 hour Set 'Test Light' Off Else - No Actions - (To add one, press 'Action') The only issue with this last one is that it will keep your Motion sensing disabled...the light will turn out, but the folder conditions will not be reset and therefore the light will have to be turned off or on manually again to get the motion sensing enabled. Maybe OK, since this would be an indication that someone left the light on too long or something. Just an idea... I did not run this through any paces, but it should work. Let me know what you think.

That is what I thought you might want...and is a bit more complicated. To much "Christmas Cheer" for me to post anything that might be closely related to coherent programming tonight.... Merry Christmas...and post what you have corrected when you get it!

Did you upgrade to the latest release firmware 2.6.13 as Michel suggested? Also, once done with that, do a "Restore Devices" from the file menu...this will wipe out existing links and restore only the links that ISY is aware of. Did you do this yet?

This is what I'm doing with the above code and it works perfectly, but I'm wondering whether it could be written more efficiently Wayne Unless I am mistaken, it's not exactly what you are doing...it appears to me by the programs posted that once the Motion Sensor goes off, then it resets everything and turns out the light. What I was asking is if this is what you wanted, or did you want motion sensing completely disabled until the user pushes a button again. Since you say it works perfectly how you want it, then I think it is fine. I prefer the methods that Darell posted in the link I posted, but that is just me. I am not sure efficiency has anything to do with it though...just that I think it gives more control from within ISY and is easier to manage.

I got my new Blackberry Storm the first day it was released and it was terrible slow...etc. etc. However, I upgraded to the new revision when it came out a couple weeks ago and it has made a HUGE improvement. I have not had to reboot once since doing this. Did you update to 4.7.0.75 yet?

I am not 100% clear on what you are wanting to do when someone taps the switch. Are you looking to turn the light on when someon taps the switch AND ignore the motion sensor completely...forever, until someone turns the light off manually and then go back to motion mode? or Are you looking to turn the light on OR off when someone taps the on/off paddle on the switch...but still allow the motion sensor to turn the light off when motion is no longer sensed? Thanks.

Here's a good thread on the subject. Specifically for X10, but the principles are similar and should give you some good ideas. http://forum.universal-devices.com/view ... sensor+x10

I think he means a 2414 PLC?

Not sure...what version switch is it that was giving the problem? Prehaps it is a new one and related to I2 issues....restoring it with the new version rewrites the link table in the device and makes sure that it matches what ISY thinks is linked there.

Install the latest Beta of 2.6.13 and see if that helps. Restoring the device may help as well. Have you checked the event log and see if you are getting anything into ISY when you turn on the ICON?

I would double check to make sure the on level and ramp rate for that device at the scene level are set properly. If so, I would do a restore on that device and see if that fixes it. (actually I never do a restore device, I always remove the device from ISY, factory reset it and re-add it...but that is just me, I think restore device works fine based on other peoples postings anyway). Eric

I have 49 new switchlinc dimmers due to arrive at my house tomorrow for installation over the coming week. I am guessing they will all be 4.x versions. In light of recent events with I2 and issues arising with newer firmware versions, newer switches, etc. I am wondering if I even want to install these or not. I am in a bit of a unique position in that I have 20 SLD's version 3.3 with datecodes in the first qtr of 2008 that I could install instead, but I thought installing the new versions would be better. I am looking for input: Should I install the 4.x's and sell any remaining 3.3's that I have left or install the 3.3's and sell the remaining 4.x's? What is currently to be gained (or lost) by installing the 4.x's? What might I gain in the future with the 4.x's assuming we get the I2 debacle ironed out? Lastly: Any thoughts on Keypadlinc's? Is there benefit to the newer versions over the older versions? Are the new ones of these I2 as well and if so what does that give us (or take away as the case may be)? Eric