Sub-Routine

Using a stopwatch it is ~4 minutes. The log looks like it is using the extended messaging when it shouldn't be. My levels and rates all show 0/9min on these devices. It seems to treat some devices correctly. The ISY did not do a Query at Reboot, and it didn't seem to catchup the schedules either. I tried to do a network query (before I started the logger) and it didn't do it. When I next queried one device it apparently went through some of the network. I don't believe I have any I2 devices, I reinstalled 2.6.8 and all is well again. Rand

I believe that is a fault in the switches. I have an older Insteon switch, v.24, that never has, and never will, report changes in it's status. I replaced it once, but the new switch burnt out in about 8 hours, so it went back in. Since I don't use it in any programs I haven't worried about it. MikeB's test might be worth a shot though. Rand

The ISY-99 is powered from the PLM but may be powered with a separate supply. The ISY-26 needed a separate power supply. Rand

Seems like an odd request, most people use buttons as indicators. Press the button so it is illuminated and use the admin console to set the button to non-toggle. From then on the button will only send On commands. Rand

The 'Vacation Button' is any device you want to turn on to indicate that Vacation On is True. I have a button on a keypad that I can use if we have an unplanned away period. I also use a series of programs for specific dates. I have one program that checks for the button to be On or any of those programs to be True, thus enabling the Vacation timers. Rand

I am sure I am not the only one to appreciate your detailed response. Thank you very much Michel. It can't get any easier than that, eh?? Are you saying that if they kept the PEEK/POKE commands programming would be easier? All you need are memory maps? Sounds like the SDM built-in At least Smarthome is employing programmers Hopefully they will get things ironed out. Rand

I probably should aim this at Smarthome, but the experts here don't fly evasive maneuvers I know that I2 allows for extended commands and that this method allows more parameters to be embedded in a command. I believe that this will make creating groups (scenes) quicker by a factor of about 8, right? Are there any other advantages to it? Sending group commands and cleanups all use I1, short messages. Changing rates and levels in groups also use the short messages, right? So once all my original scenes are created the only advantages would be in adding or deleting devices from scenes? If so, why bother? Rand

You can use the Copy option from the right button menu and then Find/Replace, or the Export/Import from the same menu to use a text editor. I have to believe that would be safer than modifying the whole backup. Rand

You should be able to factory reset and use the ISY to Restore the device as long as you did not use the 'Add devices found in links' option when you linked it to the ISY. Then you would not have to recreate your scenes and without a need to reprogram devices already linked to it. Rand

There are plans for using separate passwords for the HTML interface and the Administration Console, which is why you have to sign in twice to use the AC. In the AdminCon, under Configuration/System you can select from a list of access control for the HTML pages (HTML Role). I have mine set to Basic which allows a user to Run or Stop programs but not to be able to Enable/Disable programs. I have programs that monitor the presses of some switches to call new scenes upon a press and eventually return scenes to the default settings. For example, all my Outside Lights are on a dim state all night. If someone has a reason to turn on any one of these lights all the outside lights come on bright. These are in my Midnight Folder Folder Conditions for 'When Midnight' Add conditions to limit when programs in this folder are allowed to run. If From 11:00:00PM To 4:44:00AM (next day) And Program 'Vacation On' is False Or From 11:59:00PM To 5:14:00AM (next day) And Program 'Vacation On' is True Then Allow the programs in this folder to run. Backyard On If Control 'Backyard' is switched Fast On Or Control 'Backyard' is switched On Then Set Scene 'Outside Lights' Fast On Else - No Actions - (To add one, press 'Action') When the switch is pressed Off another program runs which returns the lights to the overnight state. Backyard Off If Control 'Backyard' is switched Off Or Control 'Backyard' is switched Fast Off Then Set 'Backyard' 49% Run Program 'All Off OL Dark' (Then Path) Else - No Actions - (To add one, press 'Action') All Off OL Dark If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set Scene 'Outside Lights - Evening' On Wait 3 minutes Wait 2 minutes (Random) Set Scene 'Outside Lights - Midnight' On Else - No Actions - (To add one, press 'Action') I have similar programs for other times. Rand

Clearing the Java cache may have unclogged the plug. I wonder sometimes if some of these "live" updates need a restart/reboot before they take effect. They always used to... Glad you found a fix though How's it going now? Rand

While KeypadLincs seem to have a status for each button... RemoteLincs and ControLincs do not have a status. They do not remember what button you pressed. They do not control a load. The ISY keeps track of the button presses and calculates a status for those devices. When the ISY is reset it automatically queries all devices and apparently it resets the status for such devices as unknown because these devices cannot be queried. The same will be true for the new Motion Sensor. And any other devices you have that a query fails on (disconnected units, communication interference, etc.). ...All the KeypadLincs do have a status for one load. That is why button 1 always shows a status. I have four buttons on a KPL that control the same group of lights at various levels and I have them all set to non-toggle on. The buttons are always illuminated (on) but that does not indicate that any particular scene is on. In fact only one (or none) of the scenes can be on at once. IIRC only some versions of KPLs can report the status of the buttons. After I typed all that I realize I should have just said, This is an Insteon limitation. Rand

Works for me. .NET 3.5. Rand

Oops, missed that line

Darrell, I must admit I have never tried it, but I was under the impression that using the Scene Set command would change the parameters within the responder. The Off/Off Program I suggested would have the latency. Rand

Another option would be to use an Off/Off with the SwitchLinc. If the light is off and you press off on the SwitchLinc you can use a program in the ISY to turn the light on to a low level by using a scene. If Status 'Basement Stairs' is Off And Control 'Basement Stairs' is switched Off Then Set Scene 'Basement Stairs Dim Scene' On Else - No Actions - (To add one, press 'Action') 'Basement Stairs Dim Scene' sets the lights to 30% with a 2 second ramp rate. You would have to get used to pressing Off for the dimmer light though. Rand

LOL, I've been playing with the family room lights. I have to wait until the weekend is over to tweak it more. I didn't put in any Conditions, I plan to Run it manually. Here is what I have been playing with. Each Scene has all the lights in it, some at 0%, some at 28%, etc. I also use different ramp rates. The Fade commands are another ramp rate. I was thinking of lightning so I use the FastOn and then the lights begin to dim to the scene levels. If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Repeat Every 45 seconds Set Scene 'Halloween Dim' Fast On Set Scene 'Halloween Dim' On Wait 13 seconds Set Scene 'Halloween Dim' Fast On Set Scene 'Halloween Dim' On Wait 13 seconds Set Scene 'Halloween Dim' Fast On Set Scene 'Halloween Dim' On Wait 13 seconds Set Scene 'Halloween Dim' Fast On Set Scene 'Halloween Dim' Fade Down Wait 2 seconds Set Scene 'Halloween Dim' Fast On Wait 2 seconds Set Scene 'Halloween Dim' Fade Stop Set Scene 'Halloween Default' On Wait 15 seconds Else - No Actions - (To add one, press 'Action') I did create another Scene, Halloween Bright, that I will mix in somewhere. Rand

If you are using a SwitchLinc to directly control the light levels and rates are not effective until the switch is reset. You could use the SwitchLinc to control an InlineLinc. A KeypadLinc, AFAIK, does not need a reset. Rand

Another opportunity to renew my request for "virtual" dates. Last Thursday in November, for example Rand

John, sorry I didn't see this sooner To use each button on a KPL as a controller make a new scene and include the KPL button and the devices you want to control. When you see a controller flashing that means communication with the device is bad. Sometimes rearranging the AccessPoints can help. I can't help with the forum bug. Rand

I'm glad it works! I think only the fade commands act this way. There are a few quirks in Insteon. Good thing we have the ISY to help us out

I think it will work if you add a couple of lines to your existing program... If IR 'TV : Channel +' is Held And IR 'TV : Channel +' is not Released Then Set Scene 'My Lighting' Fade Down Set 'My Light' Query Else Set Scene 'My Lighting' Fade Stop Set 'My Light' Query and another program: If Status 'My Light' is Off Then Set Scene 'My Button' Off Else Rand

Without this "feature" pressing a switch on when it is already on to it's local level from the local controller would never affect a change. I imagine the designers thought that if the light is so dim that you press the switch on a second time that the light should brighten considerably. To brighten gradually you can press and hold. It actually is a feature I use very often, much more than I would have thought. When using a slave I double-tap. Then a single tap dims the light again. I think it is a good idea once I became used to it.

You can replace the switches and perform a factory reset on them. Add them to the ISY. Don't bother naming them. Use the right button menu Replace With -> The ISY will change all the old links to refer to the new device. The old device does not have to be present. Wait for all the lights to finish blinking. This can take several minutes. I would do one device at a time. Rand

Ray, that is an Insteon "feature". There is nothing the ISY can do about it. The idea is that if a switch is at it's local level from a touch, one more touch will bring it to full brightness. Another touch returns the switch to it's local level. It is a local only feature. It's not a double-tap to fast on, the switches broadcast the changes as group on commands. When the master sees a command from a slave it uses it's database to see what the level and rate it should use for the on command from that particular slave and reacts accordingly. The switch you refer to as a slave can have a load and also control another device and can be controlled from another device and it's entirely likely that that is the desired effect. Different scenes from different switches for the same group of devices. Rand