Sub-Routine

GA, there is a bug in the new firmware (2.7.0) in that the Status is not updated on the ISY display. It doesn't affect programs. The Options are explained in the Wiki. Linking_an_I/O_Linc Rand

Sometimes the router has to be rebooted to see a new device. Rand

aLf, you can use Login to My ISY. The most recent documentation can be found in the Wiki. Specifically you want to look in the Quick Start Guide#IP_Address_and_URL. Rand

Hello aLf Please see this Wiki page: Migrating_To_Your_ISY-99i. The upgrade to the ISY can be done after you restore your configuration. The easiest way to reset your ISY-26 is to telnet to the device and issue a FR (factory reset) command. Telnet_To_Your_ISY. The upgrade can be applied after the reset. Note that there are different upgrade files for the 26 and 99i. Rand

Yes

Yes Joe, there are no explicit variables in the ISY. What you want to use are Folder Conditions to specify dates. Within Folder Conditions can be more Folder Conditions like times and finally Program Conditions to achieve nested If/Thens. Boolean (True/False) variables are global program conditions and can be manipulated and interpreted by other ISY programs. Rand

Correct, the program is evaluated only when the Status changes. Rand

No, it's not necessary to have two scenes. Controllers that can be responders (switches) are automatically responders. It is also possible to make another scene where the switches are only responders. This is useful when you would like the ISY to control the scene using a program, like for your motion sensor or a scheduled action. Switches can be responders in hundreds of scenes but can only be controllers in one scene. On the Configuration pane there is an IR tab. I am not familiar with Global Cache. Rand

I'm glad to read that. I am glad to read that as well Rand

I see you've found it I was already typing so it here goes anyway. You can control the scene instead of the light. Note that when the Motion Sensor activates the scene you can set different levels/rates than the switches use. I made a new scene that doesn't include one of the no-load switches so I can use that for an over-ride. If Control 'Kitchen Motion Sensor' is switched Off And Control 'Kitchen Motion Sensor' is not switched On And Status 'Kitchen South' is Off Then Wait 30 seconds Set Scene 'Kitchen Low' On Wait 30 seconds Set Scene 'Kitchen Low' Off Else - No Actions - (To add one, press 'Action') If 'Kitchen South' (a SwitchLinc) is on the program will not turn off the lights. The 'Kitchen Low' scene uses 19 second ramp rates so going in and out often doesn't resemble a strobe light Rand

to_lighter, are any of the lights illuminated on the ISY? Do you have an ISY-26 or a 99i? Rand

someguy, I have been using a motion sensor in our kitchen for about 2 weeks. 1. I liked the instant On when linked but I wasn't happy with the Off. Our kitchen is too busy at times. So I am using the ISY to switch the lights on and off. There is a slight delay. If the ISY goes down we still have our usual switches in place. 2. I watch for the MS Off command and add some seconds to it. When our kitchen is typically busy (breakfast and dinner) I don't turn the lights off, but I dim them. This reduces annoyance due to the lag. I use a non-load switch in the kitchen to override the motion sensor programs. I also key on a lamp in our family room to maintain a dim state when we are watching TV. I use three different On levels/rates that depend on the time of day (and night) and the status of the lamp. You can't do that when directly linked. 3. I have only seen a command missed when I try, I haven't experienced it in daily use. There is ~2-4 seconds when sending a command that the MS is busy. Perhaps relocating the sensor would solve that issue. Do you have an Access point on your PLM? Rand

Yes, thank you! Rand

Great! I am going to "borrow" this for a How-To in the Wiki Rand

To follow up, If you only want to control the KPL button create another scene with only the button (as a responder) in it. This should save some wear on your door operator Rand

Sure. Do you have one AP on the PLM? Can you unplug the new TV and see if things improve? Sometimes they don't even have to be on.

I think it is normal for the IOLinc. The sensor is only a controller and the relay is only a responder. Any command to control the IOLinc can only switch the relay. The 4 seconds is probably a built-in time out to prevent relay chatter. Though with Momentary A checked it should only be activated with an On OR an Off. Rand

I would have to suspect the LampLinc. There could be something wrong with the dimmer circuitry. Certainly the remote would not keep broadcasting noise for an hour, the batteries would wear out. Rand

If you are controlling scenes (aren't we all?) you will probably not see errors in the log. Have you tried the new Test Scene function? Tools/Diagnostics/Test Scene. That should help you locate noise sources. Rand

Correct. AutoUpdate should ask you to install v.2.7.0 when you open the Administrative Console. The User Guide for 2.7 can be found on the menu Help/UDI Wiki (Help Contents). User Guide The 99 will not have 2.7 installed and will also AutoUpdate after you register the device with UDI. Rand

If you have another LampLinc I would suggest using Replace. I have seen LampLincs go south (I have some OLD devices). If the database seems to become corrupted in the replacement I would have to suspect some power line noise in the area. I don't understand why your program should sometimes fail. Can you Copy/Paste it here? If you increase the Wait time it may be easier to watch in the Program Summary tab to see if it changes to False before sending the Off. Rand

We are embarrassed that we did not see this bug before we released 2.7.0. Michel has already found that error (and another) and a fix will be available shortly. Meanwhile I have found that programs that rely on the sensor still function properly; the bug appears to only affect the display. The state can be reversed using Trigger Off in the Set Options. Correct. There is a Relay Follows Sensor option as well, but the statuses are still independent. Would the Momentary: Look at Sensor option be useful for that? See this Wiki page. Rand

Randy, I would definitely attempt Restore before deleting and re-adding a device. Do you think a lot of your devices are corrupted? Are you using v2.7? Rand

Oops. Add Schedules to the reason a program runs, not only Conditions. Rand

Not exactly. A program is evaluated every time any of the Conditions in the program change. If the conditions are met the Then clause is executed, otherwise the Else actions are performed. In jrabin's program example anytime IR '1' changes the program is evaluated. Rand