MikeB

How about something like this instead: WATCH TV ON If IR 'IR_001' is Pressed And Status 'TV Light' is Off Then Set Scene 'Button B - Watch TV' On Else - No Actions - (To add one, press 'Action') WATCH TV OFF If IR 'IR_001' is Pressed And Status 'TV Light' is On Then Set Scene 'Button B - Watch TV' Off Else - No Actions - (To add one, press 'Action')

Try: http://www.myipaddress.com

Just a note - a couple of months back I was having some issues with pool.ntp.org on some Windows Servers. Nothing as dramatic as 1941, but a good 10-15 minutes off, which really isn't acceptable for me. I've switched to: 1.north-america.pool.ntp.org 2.north-america.pool.ntp.org 3.north-america.pool.ntp.org ..and haven't had any issues since. I also switched my ISY over (to 2.north-america.pool.ntp.org). I can't help but wonder if these are issues with a server or 2 on pool.ntp.org. I searched my ISY log and did not find any 1941 entries.

Make sure iLinc is configured to connect to the ISY using your public IP address, not your internal address.

You want to take the load buttons out of toggle mode. I believe this is pretty much an undocumented feature. Follow the instructions here: http://wiki.smarthome.com/index.php?tit ... oggle_Mode

Please check out this page, which should help: http://www.portforward.com/english/rout ... /HTTPS.htm

Unfortunately I wouldn't expect that to change in the future. As of right now the ISY's 2nd serial port is dedicated to configuration and troubleshooting of the ISY. I personally use an Elk IP-232 to control my Russound from the ISY, which has a much smaller form factor than the Global Cache products if you're only looking for a serial port.

We're definitely not seeing this issue here, and can't figure out what the cause might be. If you're still having the issue and would like us to check it out, please submit a tech support request here and someone will get back to you to schedule a session: http://www.universal-devices.com/supp_contact.htm Thanks

Glad to hear! You might consider upgrading to firmware 2.7.6 listed above when you have some time.

Are you still able to access the ISY using the following URL? http://www.universal-devices.com/99i If so, what firmware version are you running? If not, please power cycle the ISY and PLM and try again. What are the status of the ISY's LEDs?

Are you on firmware 2.7.6? If not, please upgrade to 2.7.6: http://forum.universal-devices.com/viewtopic.php?t=3007 Once installed, close all browsers, clear your Java cache, and please try this URL and let us know your results: http://www.universal-devices.com/99i/2.7.6/admin.jnlp

Please login to the ISY's Admin Console through the link on the support page, then open the Configuration tab, then the Networking tab, and finally the Web Server tab. Please click the Use Default button on the bottom of the screen and you should be all set. Thanks, and sorry for the inconvenience.

Please check this thread for instructions on updating to the latest firmware: http://forum.universal-devices.com/viewtopic.php?t=3007 Information on using the REST interface here: http://forum.universal-devices.com/viewtopic.php?t=2252

The REST interface is now included free with the latest firmware releases.

No, the ISY's serial port is primarily for configuring the ISY. You could, however, use an ethernet to RS-232 adapter to send commands from the ISY to serial devices. This requires the ISY-99's optional Networking module. The ISY will not, however, receive serial commands. I'm not sure if anyone has tried interfacing with a Crestron controller. See this link for a bit more information: http://www.universal-devices.com/mwiki/ ... _Resources

I typically hold the SET button in for a good 10 seconds when plugging back in to do a factory reset, but yeah - even after 3 seconds the LED blanks out here when I release. Another bad PLM? Hope your replacements arrive soon.

They shouldn't be listed. What ISY firmware version are you running?

I assume you've tried a different Cat5 cable between the ISY and PLM to ensure it's not defective? If you feel comfortable, you can try using a small screwdriver to pull down the pins on the PLM's RJ-45 connector a bit. We have seen instances where the cable is not making good contact with the PLM's connector.

This is one of my biggest complaints about Insteon. Luckily this only happens in 1 or 2 areas of my home and, honestly, we just changed our habits to hit 1 switch per second. Not bad once you get used to it, but something I wish Smarthome would account for.

I'm curious what happens if you create a scene with one of these problem devices as a responder, and another device as a controller. Can the device be successfully controlled from another controller? If you control the scene from the ISY, does the device respond as expected?

Wow, that's a strange one. Anything else linked to these switches besides the ISY?

Hi Tony - It sounds like these switches do not have the loads attached to them, but are linked to devices that control the load. Is this the case? If so, when controlling the light from the ISY, you must control the entire scenes - not the individual switches.

I think this is a great product idea. I'd buy several!

I've been using cheap CFLs here in certain areas, nothing fancy. I believe they are Honeywell and Sylvania.

Hi John - Your description sounds like your overall communications are OK, and perhaps you'll only need to relocate your PLM. While your other switches/keypads only need to communicate reliably to maybe a few others, perhaps in relatively close proximity, the ISY/PLM has a distinct disadvantage in that you want it to communicate reliably with EVERY device in your home. You might want to take a 50 foot extension cord and use it to move your PLM around until you find a good location for it on the powerline. Again, a circuit with no other electronics is ideal. An AccessPoint right on top of the PLM really helps as well. Also, something that might help a SMALL amount is using an AC adapter to power the ISY. Using the PLM to power the ISY is fine in the vast majority of cases, but it does take a bit of power away from the PLM's transmitter. Don't count on this to help much if at all however. Sorry, not familiar with the EZSnsRF at all, but perhaps it was having communication issues as well?