MikeB

I haven't tested, but once the sensor goes OFF the IF statement should become false and the program should stop running.

I haven't tested, but how about something like this: If Time is 12:00:00AM And Status 'GarageSensor1' is On Then Repeat 4 times Set 'GarageRelay1' On Wait 20 seconds Else - No Actions - (To add one, press 'Action')

Hi Steve - Could you list the exact steps you are taking and detail the symptoms so I can try to duplicate here? Thanks

Unfortunately, KPL secondary buttons cannot be controlled directly. Try adding the button to a scene, and controlling the scene instead.

Create a scene and drag both the KPL button and ToggleLinc in as controllers.

Only other suggestion I might have would be to create a scene that contains the Motion Sensor and your problem device, then delete the scene. Try that on a single device to see if it helps.

I assume you checked to be sure there isn't a scene programmed somewhere that you are missing? If not, did you originally have the ISY crawl and import existing links into the ISY? If so it sounds like you have half-links that were imported into the ISY. Unfortunately, at this point I think your best solution is: - remove each of the problem devices from the ISY - factory reset each device - add each device back into the ISY - add each device into your scenes as needed

Seems strange. I would do the following: - factory reset one of the responding devices - test to ensure it no longer responds to the MS - do a restore on the responding device from the ISY - test again to ensure it no longer responds to the MS Let me know your results...

Try doing a Restore Device on one of the devices you do not want to respond and see if that helps. I suspect you have slave links still in those devices.

If I understand correctly, I believe the issue is that when TriggerOff is checked the results of a query are not as you expect. The EZIO products show this same behavior, and as far as I know the IOLinc is the same. Basically, TriggerOff reverses the INSTEON command sent when the state of the sensor changes, but does NOT change the result returned when the sensor is queried. For example, depending on the door sensor you have the IOLinc may show ON when your door is closed (which, in mosts cases, is not what you'd prefer). Checking TriggerOff reverses the command sent when the sensor state changes, but when the device is queried it will STILL show ON when your door is closed. The best solution would be to get a difference sensor. I use this sensor, which you can use as either normally open or normally closed: http://www.smarthome.com/7455B/Garage-D ... -3-/p.aspx

2.7.7 alpha seems to be a very stable release so far.

No issue viewing the log here running Windows 7 Ultimate 64-Bit, ISY firmware 2.7.7 alpha, Excel 2007 SP2.

One more comment is that Restore Device does NOT remove any X10 codes stored in a device. It's not uncommon for an INSTEON device to come pre-programmed from the factory with an unwanted X10 code, which is one reason I always suggest factory resetting a device before installing.

Be sure you are downloading the correct upgrade file. Note that there are 2 files - one for the ISY-26, and another for the ISY-99. Be sure to read the upgrade instructions carefully. In short, be sure you are on a stable network connection (wired if possible) and disable any anti-virus/firewall software you might be running.

I missed that. Sorry for the bad information!

Our STORE links should have been updated with the new URL: http://www.homeorchestrator.com/UDStore ... ctPurchase Did you find a link that we missed and need to update? Thanks

Here is the article on resetting the password: http://www.universal-devices.com/mwiki/ ... d/Password So, you would connect using the serial cable like discussed above and follow the above instructions to reset your password. I believe that replacing/wiping the SD card will reset your device config and login information, but I'm pretty certain your static IP will stay the same so logging in with the serial cable would still be necessary. If you do replace/wipe the SD card, be sure to connect using the UDI URL and reload your firmware. http://www.universal-devices.com/99i

You could purchase a USB to serial adapter which would be handy to have anyhow - they are fairly inexpensive. Here are a couple links that should help you find one locally: http://www.staples.com/Belkin-USB-to-Se ... plesSearch http://www.bestbuy.com/site/olspage.jsp ... ies&ks=960 Or, if you can wait a couple of days, you should be able to find them online for $20 or less.

I'd say there's a good chance you will experience future issues. The PLM links shouldn't just disappear like that. If you'd rather not go through the trouble of replacing it at the moment, I'd at least have a spare PLM handly in case it happens again.

Perhaps something like this: If Status 'CabinetLights' is not Off Then Wait 5 minutes Set 'CabinetLights' Off Else - No Actions - (To add one, press 'Action')

Yes, looks correct to me.

Hi John - It runs twice per day. At Sunet + 20 minutes the THEN portion is run, and at 10:00pm the ELSE portion is run.

Each controller can have different on levels and ramp rates for each device in a scene. There can be multiple controllers within a scene. Highlighting the scene itself sets the levels for when the PLM itself is a controller (when the scene is controlled via ISY Programs for example). Keep in mind that some INSTEON devices (such as SwitchLincs) may need to be power cycled before ramp rate and on level changes take effect. For a SwitchLinc, simply pull out the reset tab for about 10 seconds, then pop it back in.

Keep in mind that may not be 100% accurate. In some instances you may be able to communicate with devices on opposite legs of power if distance to the utility pole is not too far. Also, operation of 220v equipment such as a dryer will couple the legs.

Make sure you Programs trigger based on CONTROL and not STATUS. If based on CONTROL, they will trigger any time the Motion Sensor sends an ON command (no matter what the ISY thinks the current status is).