MikeB

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).

I hope to do one within the next 30-45 days. Please keep an eye on this thread.

Hi John - Unfortunately not. We tried recording a previous session, but the quality wasn't there. I may try recording the next session, but we're also working on some short how-to videos that we'll have posted up.

Great, glad to hear!

Try changing the ANDs to ORs.

Yes. Unfortunately, in order to control a KPL secondary button you need to create a scene containing it and control the scene instead.

Make sure your program turns off a scene containing ONLY the KPL button that you want to turn off (not the scene containing all your lights). "Is Load" is purely cosmetic. Some users use this to indicate that an installed switch carries a load.

Check out this thread: http://forum.universal-devices.com/viewtopic.php?t=2280

Correct. The Motion Sensor is not a responder. Consider this scenario if it worked like you suggest - you walk into a room, the Motion Sensor kicks in and turns your scene on, you walk to the light switch and turn the switch off, which turns the scene off and let's say it turns the Motion Sensor off like you desire. What happens when you move again in that room? The second you take a step, the Motion Sensor would trip again - and your scene would turn back on!