Michel Kohanim

Hello all, Release 2.8.6 RC2 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 programs especially those that activate scenes based on the status of other programs 2. Test Linking/Adding Devices/Creating and/or Modifying Scenes and Adjusting Scenes within programs 3. Observe any type of network anomaly 4. 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.6.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.6 - applet f. http://www.universal-devices.com/99i/2.8.6/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

Hello ingeborgdot, I think it would be much more efficient and much less waste of your time if you contacted our tech support and we'll help you out. Our hours are 9:00 AM to 4:00 PM Pacific time. With kind regards, Michel

Hello jkraus, You want to access the programs and make changes? If so, then nothing like that exists. If you just want to view the status of your devices, programs, and resources then you can use ISY AJAX. With kind regards, Michel

Hi Lee, You are so very correct. I had not even considered the fact that PLCs use linear database. So, that rules out PLC. We can certainly use PLM and then the same method as EZxx devices. But, we really have to support multiple nodes otherwise it would be difficult for the software attached to the PLM to know which scene is being activated. With kind regards, Michel

Hi LeeG, It's supported as ONE node ... what we need is to somehow figure out how many groups the PLC is supporting (just like a keypad). This way, things would be more or less like dealing with a keypad (but with more buttons). It's certainly doable but it's not something I look forward to!!! Hi tpolito, If your software can listen to network sockets and then issue commands, then you can use the Network Module to basically control all the facets of your software that are accessible via network. REST is to control ISY (the reverse of above). So, if your software is capable of sending HTTP requests, then you can have it initiate a REST command on ISY and thus control your devices from your software. With kind regards, Michel

Hi Tom, thanks so very much for your interest. There are very many problems with having two controllers in our specific configuration one of which is that all the configurations made by one is not scene by the other and it may even overwrite the configurations in the other. For instance, for you to be able to use your software to sense INSTEON signals, the USB PLM on your controller MUST be a responder for those specific devices. This may cause major synchronization issues between the two. The questions I have for you are: 1. Can you send X10 signals for communications purposes between the two controllers (instead of INSTEON)? 2. Can your Alarm Panel be activated by X10? 3. Can your Alarm Panel send and X10 when armed/disarmed? If so, then, you will be OK. If not, then - and as much as I want us to sell you an ISY - I think you will have a much more complicated system than is worth. With kind regards, Michel

Hello capsterx, Dim resume is an option that we have not yet implemented mostly because most older devices do not support this option. With kind regards, Michel

Hello LeeG, Please do not delete your posts just because it might offend us. We spent months with group commands and how the PLM handles the responses before deciding on not using the PLM's Group Command. Instead, we modify the raw INSTEON command to act as a group command but the PLM does NOT know that it's sending a group command. In short, we do send a group command but the PLM does not know it's a group command so it does not send cleanup etc. The major problems with group commands are more visible when you have programs that activate large scenes (more than 5) and if you have multiple programs that might want to do something while the PLM is processing the cleanup. This caused major unpredictability issues and thus we had to forego using it. As a matter of fact, we still have the code #defined so that it's not compiled. With kind regards, Michel

Hi Tom, No unless the program activate the Scene (which contains all those devices). With kind regards, Michel

Hello tome, Yes, you can have as many controllers as you would like in a single scene. The only limitation is that a controller can be a controller for one and only one scene. With kind regards, Michel

Hello IM, Thanks so very much for your kind words! The compare issue has been identified and fixed in the next drop. Since this is a UI only issue, we can always update the website and you can use the updated UI. If you are in a rush, please do let me know and we can do that quickly. Thanks again and with kind regards, Michel

Hello apostolakisl, I agree with the icon and renaming Remove to Delete. May I trouble you to post these requirements in our Product Requests forum ( http://forum.universal-devices.com/viewforum.php?f=7 )? As far as the percentage, they do mean A LOT. For network related activities (such as backup, restore, upgrade) they are 100% accurate since the worst case scenario is an error which stops the process. For INSTEON commands, there are 3 parameters: 1. Number of commands pending to be written to the device 2. Delay between each command (usually 500 ms) 3. The time it takes for each command to complete So, in ISY, we send the Admin Console a pretty accurate rendition of the above parameters. In an ideal case, the progress bar will be quite accurate. But, in the case of a non-responding device, the progress bar will be out of synch since ISY will retry each command 4 times before giving up. So, we could have assumed the worst case scenario, or the best case scenario, but instead we chose the middle case scenario. As such, in case there are no errors, the progress bar shall be pretty accurate. In case of error, the client queries ISY for the number of commands and makes necessary adjustments and heuristics. With kind regards, Michel

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