Michel Kohanim

Hello backinthelab, Thanks so very much for your thorough review and not only we take your criticism constructively but also we appreciate it very much: without feedback like yours, we would not be where we are today. We are very well aware of lack of documentation and we are working on it slowly and only at off hours when we have not much else going on. Again, thanks so very much for your feedback and rest assured it is taken quite seriously. With kind regards, Michel

Hi Mark, Those errors mean that ISY cannot communicate with the said devices. Can you query those devices? If not, then we have to figure out what's causing the loss of signal. With kind regards, Michel

Hello wacvmd, Two conditions must be met before ML is added to ISY: 1. ML should be very close to an Access Point or the dual band PLM when linking 2. You have to use the 3rd option when linking ML It seems that the signals are not reaching your ML and therefore I must suspect that the ML is not close to an Access Point or the dual band PLM. With kind regards, Michel

Hello polexian, Unfortunately you cannot do that. Nodes are sorted on their names and therefore Office will always be below Bathroom. With kind regards, Michel

Hello raptor, Unfortunately I cannot help you with getting ZWave devices network enabled. There are many ZWave controllers out there which allow you network access to ZWave devices but since I have not used any, I would not be able to make any recommendations. As far as ISY side, you would need the Network Module (Help | Purchase Modules). Once you have the network module installed, then you can create rules that call network resources (such as TCP, HTTP/S, UDP, etc.). All you have to do is to call a resource on a ZWave controller to control that device. With kind regards, Michel

Hi jcanter, Thanks so very much. This is quite odd and it should work. Would it be possible to reinstall 2.8.5 and then send me the contents of the Event Viewer? With kind regards, Michel

Hi raptor, Each controller device can be a controller in one and only one scene but responder in up to 254 scenes. With kind regards, Michel

Hi gatchel, Yes but if and only if the deadbolt is accessible via the network. With kind regards, Michel

Hello raptor, Unfortunately the only way to communicate with them is via network. Do you have any devices that can communicate with your ZWave devices using network? With kind regards, Michel

Hello all: jcatner Are these motion sensors linked in a scene with the devices or do you use programs to control the devices based on motion activity? If latter, then: 1. Does the program last run time get updated correctly? 2. You do not see any motion activity in the Event Viewer? BrianH We added some network "down" detection algorithms to figure out: a. When ISY has a hard time renewing its DHCP lease b. The network is down c. It cannot communicate with the DNS server As long as you only get one or two and then nothing for a while, then I would not worry about it at all. But, if you get many of these consecutively, then we have to figure out why ISY has network connectivity issues. With kind regards, Michel

Hi Tome, ... I think so especially if this happens again. Usually, when this starts happening, rest assured that it is going to happen again and again and then it eventually dies. With kind regards, Michel

Hello someguy, Since you are using self-signed certificates, you are going to get those errors. Have you tried CACert.org? You can install a certificate that's not self signed and then add it to your certificate list. With kind regards, Michel

Hello johnnyt, I do apologize for the inconvenience. All these point to network connectivity issue (if the programs actually run). In short, the Admin Console subscribes to ISY and then from then on ISY publishes all events back to the Admin Console. If for any reason the network connection is broken, then the Admin Console does not show feedback. Can you try 2.8.5? We added some network detection algorithms that show up in the log. Having that information in addition to -5011/-5012 errors can help us figure out where the problem is. With kind regards, Michel

Hello apostolakisl, One comment on the Delete vs. Remove: As you may have already gathered, user input is very important for us and is usually implemented especially if it's something trivial and non-intrusive (just look at the enhancement section of each release: all those with numbers are user requested features). All you have to do is submit a request. With kind regards, Michel

Hello all, Release 2.8.5 RC1 is now available. Although this firmware has been tested thoroughly, please note that this is still a beta firmware. Please do be kind enough to : 1. Test Linking/Adding Devices/Creating and/or Modifying Scenes and Adjusting Scenes within programs 2. Observe any type of network anomaly 3. Checkout UI enhancements and fixes For a list of changes, please take a look at this post: http://forum.universal-devices.com/view ... =6475#6475 Please note that ISY-26 is no longer included in the firmware builds. Instructions 1. Please backup your ISY (File | Backup ISY) 2. Please download the firmware for your platform - please do not unzip ISY 99 Only - http://www.universal-devices.com/update ... _2.8.5.zip 3. It is very important that you use your current ISY's Admin Console to perform the upgrade by going to your http://your.isy.ip.address/admin. For MAC users, if upgrade fails, please try https://your.isy.ip.address/admin 4. Login to the Admin Console and choose Help | Manually Upgrade [the name of your system] 5. Choose the file saved in step 2 6. After the upgrade, ISY reboots. Please do ensure to clear your Java Cache: http://www.universal-devices.com/mwiki/ ... Java_Cache 7. IMPORTANT Once upgrade is completed and ISY reboots, use any of the following methods to access your ISY's Admin Console: a. http://isy/admin - applet (Windows only) b. http://isy/admin.jnlp - Java application (Windows only) c. http://your.isy.ip.address/admin - applet d. http://your.isy.ip.address/admin.jnlp - Java application e. http://www.universal-devices.com/99i/2.8.5 - applet f. http://www.universal-devices.com/99i/2.8.5/admin.jnlp - Java application 8. IMPORTANT If you have already installed a self signed certificate and your current firmware is 2.7.10 and below, you must reinstall a new one: http://www.universal-devices.com/mwiki/ ... rtificates IMPORTANT Due to the sensitive nature of supporting MorningLinc, users now must agree to terms and conditions upon Admin Console start up otherwise the dialog keeps popping up every time the Admin Console is started. Thanks and with kind regards, Michel

Hi Tome, The answer is: it should NOT! This is usually a symptom of a failing PLM and I strongly recommend getting it replaced. With kind regards, Michel

Hi Wayne, Thanks so very much for your feedback. I do also see a potential for this device. This said, however, the main issue is that ISY has to know the exact property of each device/type. For instance, a security system has commands and events that ISY has to know before hand. It cannot just act on any random event. So, in essence, we have to come up with device classes that ISY supports before doing anything else with external devices. Of course, this is on our requirements list alas at a low priority. With kind regards, Michel

Hello jkraus, Quite weird! The only thing I can recommend is making sure that you're close to an Access Point, open the Event Viewer on level 3, and then see the traffic. If all you see are INST-ACKs, and if your RL is in Programming mode, and if you are close to an Access Point, then I would think that you have a defective RL. With kind regards, Michel

Hi art, Unfortunately not at the moment. We have multi-user authentication/authorization on our list of requirements. With kind regards, Michel

Hello bushmg, Apologies for the inconvenience. Normally, the address is on a label in the battery compartment and sometimes right underneath the batteries. With kind regards, Michel

Hello m_later, In addition to what LeeG suggested, you are welcome to send an email to support@universal-devices.com and we'll send you the most up to date list. With kind regards, Michel

Hello rlebel, You are absolutely correct! In this case, the programmer (or, better yet, the configuration manager/builder) was ME! I take full blame for this and it shall not be repeated. With kind regards, Michel

Hello jtara92101, Where do you get " Failed to connect to gateways! " ? With kind regards, Michel

Hello jtara92101, I have to do more digging but, from what I remember, we had to basically add the level to the command (cmd2) in older versions. Putting 0 there would turn it off. The newer i2 versions were different but the difference was so different between differnet devices that we just left it as is. With kind regards, Michel

Hello ingeborgdot, I am sure Control was meant and NOT Command (we do not have such a structure). With kind regards, Michel