Sub-Routine

Are you sure you haven't set a long ramp rate for the switch in the scene? I noticed that when adding a device to a scene it defaults to 9 minutes. Rand

If I understand your question you want to be sure the KPL LEDs indicate the status of the lights when your schedule changes the lights. And the buttons are already in scenes as controllers to those lights. You need to change your programs so they control those scenes instead of the individual devices. If you like you can create new scenes with the buttons a responders so they can be controlled by your programs. Rand

C to H are easy enough. C, D, F: Create a new scene for each button. Add the responders (In-LineLincs) to the appropriate scenes. Add the buttons to the desired scenes as controllers. Use your schedules and other programs to change the scenes, not the responders. E: Create a new scene. Add the ToggleLinc Relay as a controller. Add button E to the scene as a controller. Use your programs to change the scene. G: Create a new scene. Add the LampLincs and the ToggleLinc Relay as responders. Include the button in the scene as a controller. Use your programs to change the scene. Note that you can use different levels and rates using the ISY as a controller (for your schedules) and using the buttons or switch as a controller. A & B will take more brainwork. Rand

Catch up at Restart (Configuration) has a few glitches this way. They were gone for a while but I think some are back. For now I have unchecked that option. After a power outage the lights should return to their previous levels, so if no schedules were missed nothing is wrong. Rand

Glad you got it working. Also, nice move on the rewiring Rand

The ISY should reset after the firmware is installed. Are you sure you have a valid copy of the older firmware? Also check your firewall and virus checker. Some McAfee versions blocked upgrades. Rand

Hi Michel, I don't understand the value of forcing i1. Since most of my devices are new, I am assuming they are i2 compatible. Is there a reason that I would want to force i1 compatibility? Cheers! Since most of my devices are old they are not responding to all i2 commands, but the test the ISY is using for i1/i2 is unreliable. While Michel and company search for a more reliable test they have decided to 'hardwire' a solution. So it's for me and a few other users Rand

For local level and rate changes to 'stick' you have to power cycle the switch. Pull out the button at the bottom for a few seconds or cycle the circuit breaker. You don't need to do this for keypads. Rand

Windows Firewall probably opened a requester the first time you accessed the ISY. The trouble now is that the ISY address has changed so it should appear as a new device. Unfortunately the old device is missing and this confuses your Network Neighborhood, and probably the firewall, because it has the same MAC address as the old link. I used the router (D-Link) to always assign the ISY MAC address to the same IP address whenever it is rebooted. I also noticed that some time ago McAfee snuck in an install of it's firewall. I know I had to change something there. Rand

Using different on levels does not function natively on older KPLs. To work around this do not put the KPL in the scene associated with the button. Use the button to trigger a program that calls another scene to set the KPL level and rate. Rand

If you can see an icon in the Network folder you can drag it to the desktop. Rand

Yes, you should reset the switches. Rand

Resetting a controller does not remove links in responding devices. To remove all those links you would direct the ISY to remove the controller. The ISY will use it's database to determine what devices are linked to the controller and remove those links from those responders. If the ISY does not know about the link it cannot remove it. In that case the responding device would have to be restored to remove the link from the controller. So besides doing a restore on the ControLinc you should run a restore on any devices that aren't reacting correctly to the ControLinc. Rand

Reading the links should not take so long no matter what option you use. This is a problem with the latest ISY firmware. I am working with Michel on this issue and I was surprised no one else was reporting it. So now I am not as crazy as I thought Rand

Nope, not what I was looking for. I know,

Simply link the button to a plug-in module and unplug the module. Every time you press the button it will blink.

I think you are confusing the Log with the Event Viewer. Rand

In my experience: Yes, you need unique names to refer to another program. Otherwise the first named program in the tree runs. If you are not calling a program they run when enabled no matter how many have the same name. Rand

I wouldn't even think of replacing all those thermostats. Perhaps one or two in certain areas could be useful. Probably more with the AC than the heat. Rand

I am seeing this as well. Every morning at 3AM I get a notice. If I do a manual query the email is also sent. Rand

If you paste the text between Code tags it will remain formatted. Rand

We had a great discussion about this when the forum began. It was pretty much decided that it would be impossible to implement with 21st century technology during the estimated life of the solar system so it's been shelved. You could use one program to check the status of the lights to use as a Boolean value (True/False) in other programs. Rand

Like Mike says, just create new scenes. I use individual programs for the times though. I dim mine to about 50% for the middle of the night and raise them up again in the morning. 25% is almost useless, but of course, you should experiment. Sunset and sunrise offsets are great ways to start and end the sequence. On weekends I keep the lights bright later. I use all 9 minute ramp rates with my schedules, it's difficult to notice the changes. If you want to assign another controller to the same scenes I would suggest much quicker level changes. Rand

I sort of had a feeling about the PLM. Yes, Query at Restart is checked as well as Catch up schedules at Restart. Rand

Yes, a good and bad solution. That's really odd it was only certain devices. I have a 2.4 with firmware 52 for over a year. How long did it take to replace the modem? What ISY version are you using? Rand