MikeB

Thanks for the referral, Rand! Wooper - If you want to use an IR remote with no line of site to the ISY, you have a couple of options: 1 - Use an IRLinc from Smarthome, which we support: http://www.smarthome.com/2411R/IRLinc-R ... ter/p.aspx 2 - Use an IR to RF repeater. I've heard some people have good results from the inexpensive units Radio Shack sells: http://www.radioshack.com/product/index ... Id=2049642

You could use an ISY program to extend the WAIT if you'd like. Instead of adding the Motion Sensor to your scene, create an ISY program to trigger based on the status of the motion sensor. The biggest downside would be a slight delay in response.

Neal - Glad to hear. Sorry for your troubles - I wish we didn't have to deal with these anti-virus / firewall issues to begin with! Thanks for sharing the information, and please keep us posted on Trend's response.

Hey Neal - Unfortunately I'm not very familiar with Trend so can't offer any specific advice. However, look for a way to exclude a URL and/or IP address from its scanning - and exclude the URL/IP for the ISY. I'm not certain what other functionality might be affected, possible firmware updates and maybe more. I took a quick look at this documentation: http://www.trendmicro.com/ftp/documenta ... 1%20AG.pdf I assume this matches the version you are running. If so, check out sectio 5-13 and create a firewall exception to and from your ISY (all ports). You might also want to disable the Web Threat Detection on 5-15 to see if that helps. If it does, you may want to adjust its settings as well. Good luck, and please let us know how you make out.

You may want to consider running a 'restore device' on any problematic devices, especially if links on that device were programmed with 2.6.13. That firmware was using i2 commands to program newer i2-capable devices, but some users experienced issues programming links with those commands. The newer firmware uses i2 commands only for devices which REQUIRE it (Motion Sensors, etc.), but any links programmed with 2.6.13 could still be corrupt. Otherwise, you may be having typical comm issues as Rand pointed out above. Please let me know how you make out.

Windows Firewall will not cause any issues. Do you have any anti-virus software that may be interferring? If so, please try to disable it completely as a test. Also, please try closing all web browsers and clearing your Java cache: http://www.universal-devices.com/mwiki/ ... Java_Cache

Not sure I quite understand, but the initial program will change to true if, during the specified time periods, the 'Garage Lantern S' switch is turned FAST ON (double-tap ON). When do you want it to go false, when you turn the 'Garage Lantern S' switch off? If so, you could try changing the IF statement to: If ( From Sunset To Sunrise (next day) ) And Control 'Garage Lantern S' is switched Fast On And Control 'Garage Lantern S' is not switched Off

If you're running 2.6.13, I would highly recommend upgrading to our release firmware 2.7.0. Please post back if that does not resolve your issues. Thanks

Check out the wiki article here: http://www.universal-devices.com/mwiki/ ... ion_Sensor

Not sure if this will help, but you might try factory resetting a problematic device, then doing a Restore on it and see if it helps.

Sounds like are trying to combine what should be two separate conditionals. Try this instead: If From 12:00:00AM on 2009/04/01 To 11:59:59PM on 2009/10/31 And Time is Sunset + 15 minutes

START CONTROL PANEL PROGRAMS (only if not in Classic View) JAVA SETTINGS button DELETE FILES button

The thermostat should be in manual mode for the ISY to control it. Personally, I don't use the thermostat's automatic modes at all (unless I want to disable ISY control). Please see the following link to see what I'm doing with my office thermostat - maybe it will give you some ideas: http://forum.universal-devices.com/view ... thermostat

Hi Joe 1 - A scene is a group of devices that are linked together in ways that you specify. Some devices can be controllers (when pressed, they control other devices in the scene) or just responders (they simply respond to controllers in that scene). For example, if you want to link 2 switches together so they both control your kitchen table lights, you would create a scene and add them both in as controllers. Or, if you want to link a switch and a lamp module together so the switch controls the lamp, you would create a scene and add the switch as a controller and the lamp module as a responder. 2 - You should ALWAYS link your devices through the ISY (using scenes). If you link them manually, the ISY will not be aware of those links and you will have problems. 3 - Sounds like you linked the RemoteLinc and LampLinc outside of the ISY, so your ISY does not know that the RemoteLinc turned the LampLinc on. You should unlink these devices manually, then re-link them using the ISY. As for your example, you can certainly create ISY programs to do what you ask - but since the RemoteLinc does not have any visual feedback like the LED on a KeypadLinc, you won't know for certain what your current mode is (without looking at the Admin Console). Personally I'd find a KeypadLinc much more suited to this.

Sure. 'Switched Off' (control) means the device is physically switched off (someone walks up to the switch and turns it off). 'Off" (status) refers to any time the device is off, whether it was physically switched off, turned off by another device (motion sensor, a linked switch, etc), turned off by an ISY program, etc.

Personally I agree. This is currently on our list of possible changes to consider, and we hope to discuss this soon.

Though the secondary buttons do not show up on the right-hand pane of the Admin Console when you select My Lighting, they do show up in the list of nodes on the left-hand side of the screen under My Lighting. If you highlight the button on the left, you will see the status displayed on the right.

IMPORTANT Please note there is an issue with firmware version 2.6.15 and higher that may cause a corrupt file system if the user tries to factory reset the ISY. Please do not attempt a factory reset without assistance from someone at UDI until further notice. Thanks

Sounding like a bad PLM. I'm assuming you don't have a spare to try? Have you tried factory restting your PLM then trying a restore?

I would do it like this: If Status 'Light' is not Off And Status 'Motion Sensor' is not On Then Wait 4 minutes Set 'Light' Off Else - No Actions - (To add one, press 'Action') Unless I'm missing something that should be fairly straightforward. Make sure the motion sensor is in ON/OFF mode. This assumes your motion sensor is set for a 1 minute timeout (1+4=5).

Sounds like something has happened to your PLM, but we need to first find out why you now cannot access your ISY. - does your My Lighting icon show up in My Network Places? - can you access your ISY via http://www.universal-devices.com/99i ? - what firmware are you running on your ISY?

I assume this program is not your PGM2 program? If it is, it will not work because you are disabling it within itself.

1 - If you plan on making a lot of link changes with your motion sensor in the future, it certainly might make sense to simply use ISY programs to trigger events based on motion instead of putting your Motion Sensor in scenes. There are 2 limitations to keep in mind, however: - if your ISY goes down for any reason, your programs do not run - there is an additional delay with using ISY programs vs. direct device-to-device links 2 - The motion sensor does have an ON/OFF mode. So, you could sense motion based on the ON command and do whatever action you'd like (turn lights on), then watch for the OFF command. When the OFF command is received, you know there has been no motion for x number of minutes (whatever timeout you have configured on the Motion Sensor). I agree that the ON only mode is rather limited, in my opinion. 3 - I haven't seen this yet, but my motion sensors have been in low-traffic areas (closets, etc.)

Hi Martyn - I apologize, it is confusing. To be certain, I went ahead and rolled back my testbed ISY-26 here to 2.6 and did a direct upgrade to 2.7.0 - and it went flawlessly. I would suggest the following for you: - disable all firewall and anti-virus software - ensure you have a good backup of your ISY - login to the admin console and disable your internet access - perform an automatic upgrade of your ISY from the HELP menu - close all web browsers, clear your Java cache - once your ISY finishes booting, login to the admin console and re-enable internet access - also be sure to request and install a SSL certificate (via the HELP menu) At this point you should be up and running with 2.7.0! Also, for the record, firmware 2.6 is actually different than 2.6.0 listed in the upgrade instructions. Due to memory limitations on the ISY-26, we needed to create a dumbed-down firmware to free memory before firmware upgrades in some scenarios. It is a non-functional firmware and should only be installed temporarily before upgrading to the latest firmware. Though this temporary firmware load is not required in all cases, it is required in some - and there's no harm in loading it even when not needed. Please let us know if you have any issues.

There is a delay when you use ISY programs to perform actions based on triggers (switch presses, etc) instead of using scenes. The signal has to make it from the switch to the PLM, the ISY has to process it, then send a command back to the PLM which then broadcasts it to the powerline. Device-to-device links (scenes) are much faster, but don't have the logic to do what you need in your programs. That being said - I think 2 seconds sounds a bit long, but may be normal. Most of the things I do with ISY programs that are similar take, I'd say, 1-2 seconds to react.