Michel Kohanim

Hi greg, 1. If you change anything on ISY, it overrides whatever you have done locally on the device 2. 2.7.7=2.7.7/1 (the one you have installed) should have this issue fixed. I think the problem is that you are not using this specific URL: http://www.universal-devices.com/99i/2.7.7/admin.jnlp 3. When you use the above mentioned URL, you will get different labels which would make much more sense + they will fix the issues you are having With kind regards, Michel

Hi slopdog, Are these statuses or controls? With kind regards, Michel

Hi Devon, Excellent idea. The closest I've seen is Sonos with the Network module ... but, this is not going to be as seamless and integrated as Control4. With kind regards, Michel

Hi RickL66, The email speed depends on three things: 1. The specified timeout 2. How long it takes the SMTP server to respond 3. How many other tasks of higher priority are running It's quite unlikely that ISY will ever be able to send emails within 5 seconds. With kind regards, Michel

Hello, Apologies for a tardy reply. We had to push back the date till Monday. Thanks so very much for your patience. With kind regards, Michel

Not at all! With kind regards, Michel

Hi tome, You usually see that after a duplicate message. In short, the process message failed since it was a duplicate of the previous message. Some RF devices send their messages twice (for reliability) and ISY intelligently discards the duplicate. With kind regards, Michel

Hi Al, Have you recently replaced your PLM? 87 links in your PLM is awfully low unless you have just a handful of devices. If you still have record mismatches, it means that ISY could not write to that device. Try the compare one more time but this time make sure you read the whole Device Link Database again before doing the compare. With kind regards, Michel

Hi Al, This cannot be!!! You will have to click on the Start button first to choose your device/Start the process. Did you do this? With kind regards, Michel

Hi Al, Would you be kind enough to go to Tools | Diagnostics | Show Device Link Table ... when done, click on the Compare button. If you do not have identical records, then do a Restore Device on it. Personally I think the problem is that you do not have any links in the PLM for those other buttons. What is your PLM firmware version and how many links does it currently contain (Tools | Show PLM Link Table --> Count). With kind regards, Michel

Hi wacvmd, I do apologize for not seeing your original post. You can use the OR to include other devices in your conditions. But, perhaps, I am not understanding what you are trying to accomplish. You are always welcome to call our tech support line to schedule a call so that we can walk you through some of these difficulties. With kind regards, Michel

Hello slopdog, Yes, this is correct. All you have to do is to replace your battery and then issue a Query on the low bat node in the Admin Console. With kind regards, Michel

Hi jason|99, Yes indeed you are correct. You should consider programs as Control variables. This means that every time the program is set to true (even if it was true before), all other programs that are evaluated based on this program are re-evaluated. Just like using Control Switch On in programs. With kind regards, Michel

Hi fasttimes, On the main panel, the sub button have no attributes. The sub buttons respond only to On/Off. So, you cannot have an On command turn it off and an Off command turn it on. Also, if you want to control the status of the backlights in your programs, simply put them in a scene and activate/deactivate the scene. Are we talking about the same thing? With kind regards, Michel

Hi tome, As far as version, yes it's correct since the Motion Sensor does not provide us with its version. My only comment is remote programming: every time you do anything with your MS on ISY, you are using remote programming. I do not recommend turning this feature off unless you are no longer going to modify the scene settings for your MS. With kind regards, Michel

Hi someguy, The URL points to the latest stable UI build which has not yet been built into the firmware. When the firmware is released, this UI will also be included. Thanks so very much for the update. With kind regards, Michel

Hi slopdog, When you add your Motion Sensor, you get three nodes in the tree one of which has Low Battery suffix in its name. You can use this node to test for on/off events in scenes and/or programs. With kind regards, Michel

Hi Kelly, Good to know and thanks so very much for the update. For that to work, you will have to use programs (not scenes) ... With kind regards, Michel

Hi fasttimes, This is not a bug. You cannot set on level/ramp rate for sub buttons. Only for the load button are those attributes available. Which web page are we talking about? This error does not look familiar. [did you get my last emails?]. With kind regards, Michel

Hi busybaby, The problem is that your button A is in the "On" state (for some reason) so it will toggle to Off first. If button A is never used to turn off a scene, please use Button Toggle Mode button (at the bottom of the main panel) to make this button non-Toggle On. This way, this button will always send on. With kind regards, Michel

Hi slopdog, They are surely on our plate for the release after next. I just cannot be firm on the date. Thanks so very much for your patience. With kind regards, Michel

Hello again, Variables as well as some means of control vs. status for programs are in the works. This said, however, I cannot give you a firm date since - currently - we are adding so many features into the next release that it might take a little while. With kind regards, Michel

Hi someguy, would you be kind enough to try http://www.universal-devices.com/99i/2.7.7 and let me know the results? Thanks and with kind regards, Michel

Hi jmayzurk, This is by design and I completely understand the confusion however once you get a hang of it things will fall into place. Unlike procedural programming (like C), ISY is event based. So, anything that causes the condition to become false would cause ISY to re-evaluate the block. The best analogy for this paradigm is multi threaded programming where two (or more) threads are dependent on the value of one variable: if the variable changes, the change is reflected in other threads as well. If you want your programs be base on user actions (such as someone pressing a button) it is best to use Control instead of Status. This way, the program is evaluated IF AND ONLY IF someone does something to the switch AND the event generated is the one you are looking for. i.e. Fast On, Fast Off, On, Off ... With kind regards, Michel

Hello again, Thanks so very much for trying the test. I am glad that there's a workaround however that's not how it should work with the latest firmware for IOLinc (including the one I have right here). I have already contacted SH and I will let you know as soon as I hear back ... With kind regards, Michel