Michel Kohanim

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

Hi mpf541, Would you be kind to do one more test: 1. Please remove both the sensor and the relay from all the scenes to which they belong 2. Redo the query and let me know if you still have the same issue In the meantime, I am going to contact SH for further clarification. I do have a v36 here which does not exhibit the same issues you are experiencing. With kind regards, Michel

Hi ryarber, You can safely ignore these errors if: 1. You are using a mobile client (such as iLinc or eKeypad) 2. Some connections are lost These errors basically mean that the subscriber could no longer be reached and thus the subscription is expired. With kind regards, Michel

Hi jason|99, Every time a program's state changes the conditions to which it's part of are re-evaluated. If I use the concept of Control vs. Status, programs only support Status. With kind regards, Michel

Hello Al, Would you be kind enough to let me know whether or not ISY considers this device as "unsupported". If yes, can you give me the numbers after the "v" on the top center of the screen for this device? Thanks and with kind regards, Michel

someguy! What URL as you using? There are two files: 1. One is the macro file which is part of the applet code 2. The other is the actual log which is downloaded from ISY 1 requires 2. With kind regards, Michel

Hi Paul, [ignore] means two things: 1. The device itself shall ignore this record 2. You should consider this record as a logical delete and ignore it With kind regards, Michel

Hi greg, Please do be kind enough to try our 2.7.7 firmware. Once you have this installed, then use http:/www.universal-devices.com/99i/2.7.7, make sure the options are correct (Momentary C), and then let us know how it works out. If you are interested in installing our 2.7.7 alpha release (which is very stable), please send an email to support@universal-devices.com. With kind regards, Michel

Hello mpf541, please check the version of your IOLinc. If you have anything below 32, please have them contact us so that we can resolve the issue. It's a known fact that IOLinc versions 31 and below report the status of the relay as the status of the sensor. This should have been addressed in higher versions. With kind regards, Michel

Hi fasttimes, Apologies for a tardy reply. Yes. Please use Event Viewer/Level 3 to figure out which device is causing this issues. In most cases the problem is signal. In 10% of the cases the problem is the device itself refusing to write to a specific memory location. Factory reset fixes this issue. With kind regards, Michel

Hello UDNewUser, I did send you couple of emails one of which was almost immediately after I received your email. Since I didn't hear anything back, I sent you another email after about 15 minutes and still didn't get anything back. I also called you this morning but got the voicemail. Please do be kind enough to call us so that we can get to the bottom of this issue as soon as possible. With kind regards, Michel

Hi Paul, Unfortunately that feature is not available currently but is high on our list. With kind regards, Michel

Hi UDNewUser, Can you send an email to support@universal-devices.com now? I would like to login to your computer and see what's going on. Thanks and with kind regards, Michel

fasttimes!!! You are indeed quite fast! This is a hotly requested feature and we will indeed include it in one of our releases in the near future. With kind regards, Michel

Hi fasttimes, I do apologize for a tardy reply ... Using Event Viewer/Level 3 you would know exactly what is causing request failed. What seems to be happening is that due to the failures, some links have not been removed. Currently, the easiest way to remove them is to: 1. Create a dummy scene 2. Put both your RL and the device that responds to RL 3. Make sure that the RL is actually controlling that device 4. Event Viewer/Level 3 5. Remove the scene altogether ... please make sure to save the Event Viewer log and send it to us in case this procedure fails We are currently working on a more direct way of removing unwanted links ... we just haven't figured out the best way of doing so without jeopardizing the synchronization between ISY and the devices. With kind regards, Michel