Michel Kohanim

Hi Ken, In addition to Rand's suggestions, please note that there was a bug with firmware 2.7.6 and below which caused this behavior. If you have not yet, I strongly recommend upgrading to 2.7.12. With kind regards, Michel

Hi Glenn, Can you cut and paste one of the programs that quit working? With kind regards, Michel

Hi Ron, I am not sure how would ISY communicate with this device since it's neither INSTEON nor do we even know what type of RF device it is. With kind regards, Michel

Glenn, Please try any of the following URLs: http://www.universal-devices.com/99i/2.7.12 http://www.universal-devices.com/99i/2.7.12/admin.jnlp http://your.isy.ip.address/ http://your.isy.ip.address/admin.jnlp With kind regards, Michel

Hello stevehoyt, Apologies for missing this post. I will include it in our list of requirements but please note that this will have a very low priority simply because what you are requesting causes all statuses to be wiped out and requeried. This may take a long time depending on the total number of devices and may make the whole system inoperable. We can possibly make it an option. With kind regards, Michel

Hi Glenn, If you have version 2.7.6 and below, then time might be off (gone to 1941) ... I strongly recommend upgrading to 2.7.12. If you are already on 2.7.12, would you be kind enough to provide more information: 1. The scenes work ... so it's not the PLM 2. What are the common characteristics of the programs that do not work? With kind regards, Michel

Hi mitch236, If you are going to replace both: 1. Backup your old ISY and then unplug both the PLM and ISY 2. Connect the new ISY to the new PLM 3. Log in to the Admin Console on the new ISY 4. Restore your backup from #1 (File | Restore ISY) 5. Let the system reboot 6. Log back in to the Admin Console 7. Click on File | Restore Modem (PLM) With kind regards, Michel

Hi aLf, Apologies for the confusion. You cannot cut and paste the whole URL since the editor builds the stream for you with all the headers. Please send me the URL you wish to access and I'll create a rule for you and send it back for you to import (tech@universal-devices.com). With kind regards, Michel

Hi mitch236, This happens when the Admin Console tries to contact our website to see if there are any updates available for your ISY and it fails. The causes could be: 1. In corporate settings, there might be a firewall that stops communications with our server 2. No network connection 3. Our server could have been down With kind regards, Michel

Hi aLf, 1. Go to Networking | Network Resources tab 2. Double click on the middle column 3. A Resource Editor Dialog will pop up and will let you update the resource specifications With kind regards, Michel

Hi ingeborgdot, Click on any one of the sensor nodes (on the left) and then click on the Set Options on the mid/bottom of the right panel. You will see a Darkness Sensitivity field which you can adjust. Unfortunately, when the sensor is off, you cannot communicate with it simply because it goes to sleep mode. This is required otherwise you would run out of batteries every few weeks. With kind regards, Michel

Hi south, What you have should work provided that Coming In's last runtime is actually valid. When you go to Program Summary, is the last runtime accurate? With kind regards, Michel

Hello south, You can use the last run time of a program as conditions in your other programs and evaluate the elapsed time. With kind regards, Michel

Hello Joe, No ... i was just wondering what happened above and beyond loading an old backup. With kind regards, Michel

Hello jcip, The first thing I recommend is to upgrade to 2.7.12. Please note that the fan mode/state changes have a little issue in thermostats: if you turn the fan on/off quickly enough, the thermostat dongle may get confused and from then on provide you with the wrong status. With kind regards, Michel

Hi again, Thanks so very much for the detailed description. Things are a little more clear now: 1. In firmware 2.7.7 and below, you could not create a controller/responder link between sub buttons of the same KPL in scenes. For that you had to use Button Groupings (or Mutually Exclusive buttons). As such, the first thing I recommend is upgrading to 2.7.12 2. In all cases, and for all KPLs: - You cannot create a mutually exclusive relationship between a sub button and the load for the same KPL. i.e. you cannot have it such that when button C is on the load should turn off. You can, however, adjust the on level and ramp rate for the load given the sub button as a controller - There are no on levels/ramp rates for sub buttons; they can either turn on or off With kind regards, Michel

Hi Joe, That's indeed bad news! What is this specific KPL connected to? Did you do a factory reset on it before restoring it? With kind regards, Michel

jkraus, It's really not in an endless loop. It's trying to write all pending writes for all devices. This might take a while especially if those devices are not responding. If you have time, please let ISY try completing what it's doing. Once done, please take a look at your devices and make sure you do not have any devices with green 0101. If you do, then we have to figure out why they cannot be written out. With kind regards, Michel

Hi matapan, Yes and specifically: -Getting status updates from the thermostat without having to query them With kind regards, Michel

Hi mbrett, I have searched both the Google Account history for your name as well as our accounting system for any orders for your name and there's only one order. Would you be kind enough to send your full name to sales@universal-devices.com with a link to this post? With kind regards, Michel

Hi Dave, Yes, I am certain! With kind regards, Michel

Hi Dave, No, ISY should continue with the execution. I am thinking that the problem is that ISY cannot communicate with none of your devices in the action list. With kind regards, Michel

Hi stevehoyt, Increasing the retry count would cause degradation of performance. I do not recommend it. 3 tries should be enough. I think it would be best to figure out under what conditions you see the comm. errors. With kind regards, Michel

Hi mbrett, I have searched the system and there is only one order for you on 4/10/2009 for an ISY. Is it possible that you ordered using a different name? If so, would you be kind enough to send the possible names that may have been used to place the order to sales@universal-devices.com? With kind regards, Michel

Hi Mark, You are 100% correct ... I think it had to do with our paranoia about security: the certificate holds your private key and we felt that it should not be stored on your machine and thus it was deleted after the installation. We just made a change that asks the user whether or not the file should be stored on the machine with a warning that this might constitute a security risk. Thanks again and with kind regards, Michel