Michel Kohanim

Hello all, I am happy to announce the availability of our 3.3.4 (RC1) release! For a list of changes, please take a look at this post. This is a minor release and an official release candidate. Know Issues - None Things to test: - SSL and IE9 especially for ISY99 - Admin Console on MAC - EZRain/IO not responding condition - Leak and Open/Door sensors 994i ZS Series - Meter communications and utility price signals Important Information 1. Important Brultech module is no longer supported on ISY99 Series. Please contact sales@universal-devices.com for options 2. Important NetBios removed from ISY99 Series. You can no longer access ISY by going to http://isy on Windows 3. Important If you have a 994, you will need to re-install a certificate. Please review ISY994 Series Advanced Network Security Configuration for more information. 4. Important We have removed SSLv2 support (very insecure) from ISY99/ISY994. Unfortunately, the only protocol supported by MAC with Java 1.6 is SSLv2. As such, you MUST upgrade your MAC to Java 1.7 (Software Update) 4. Please note that Safari does not support SSL session reuse and thus might take an exorbitant amount of time to communicate with ISY. As such, when using 2048 bit SSL, it's best not to use Safari. 5. If you are using the Irrigation Module and are upgrading from releases prior to 3.1.5, you must edit the programs using Irrigation variables and save the programs again. Irrigation module is no longer on promotion 6. Upgrading from 3.1.3 and below: If you are using WeatherBug Module's Rain Today in your programs, please note that the precision has changed from 1/10 to 1/100 and thus your programs might not run properly 7. For a discussion of variables, please look at our Program Variables forum. Instructions: 1. Please backup your ISY (File | Backup ISY). If you are backing up a 3.1.6 system, please note that the backups are corrupted. If you have a backup from prior releases, you should be OK 2. Please download the firmware for your platform - please do not unzip ISY 99i Series ISY 994i Series 3. Login to the Admin Console and choose Help | Manually Upgrade [the name of your system] 4. Choose the file saved in step 2 5. After the upgrade, ISY reboots. Please do ensure to clear your Java Cache 6. IMPORTANT Once upgrade is completed and ISY reboots, use any of the following methods to access your ISY's Admin Console: a. http://your.isy.ip.address/admin - applet --- Security Warning: Due to recent Java security problems, it's best to always use method #d b. http://your.isy.ip.address/admin.jnlp - Java application c. http://www.universal-devices.com/99i/3.3.4 - applet --- Security Warning: Due to recent Java security problems, it's best to always use method #d d. http://www.universal-devices.com/99i/3.3.4/admin.jnlp - Java application Best method to access Admin Console Dashboard - not fully supported - http://www.universal-devices.com/99i/3. ... board.jnlp 8. Please backup your system again Thanks and with kind regards, Michel

Hi Dennis, Unfortunately it's not an upgrade but a replacement: you will have to replace the Zigbee radio to a Smart Grid Zigbee radio. Who's your utility? Each utility has different procedures for provisioning a HAN device. With kind regards, Michel

Hi jmed999, Thank you. Do you see an exclamation mark next to NTP Server? Would you please send me your Tools | Error Log to support@universal-devices.com ? With kind regards, Michel

Hello jmed999, Two questions: 1. Do you have Daylight Saving Time checkbox checked? and, if so: 2. Are you in a region that honors DST? With kind regards, Michel

Hi johnsmal, The first thing I recommend is for you to be local to your ISY. Once local, then please go to Help | Request Manage SSL Certificates and install a new certificate in your ISY. With kind regards, Michel

Hi cookin_carl, I am so very sorry to hear. If you are not confident about your backup, then do the following: 1. Put a new SD Card in your ISY 2. Factory reset ISY 3. Put the old SD Card back in and reboot 4. Go to Configuration | System | Network and reset your network settings If you are comfortable with your backup: 1. Factory reset your ISY 2. Restore your backup and when asked whether or not you want to change the configuration, make the appropriate decision (you don't want to replace current configuration which is DHCP with what's in your backup) 3. Once rebooted, go to Configuration | System | Network and reset your network settings as you wish With kind regards, Michel

Hi chuck4084, Please clear your Java cache (http://www.universal-devices.com/mwiki/ ... Java_Cache) and then go to http://www.universal-devices.com/99i/admin.jnlp . With kind regards, Michel

Hi Tim, Thanks so very much for the information. I do not think it's a coincidence. We shall take a look. With kind regards, Michel

Hi IM, Yes, I agree. With kind regards, Michel

Hello IM/LeeG, Thanks so very much. This is indeed great news and, at the same time, not such great news since we now have to figure out why some devices (at the end of the database) do not send status updates. Thanks again so very much to both. With kind regards, Michel

Hello llovering, If you do not see any of your programs, please go to Tools | Diagnostics | PLM Status/Info and let me know what you get. If you are still having problems, it's best to schedule a remote session with our tech support team (links below). With kind regards, Michel

Hello IM, Thanks so very much for this thorough analysis. The problems we are finding are that: 1. Link count is much larger than what it should be (>800) 2. Devices do not send status updates The only commonality in this case is duplicate link records. Sometimes, a PLM restore removes some of the duplicate records but, in most cases, the duplicates are the same (i.e. same devices). Was this the case with your 2412S as well? With kind regards, Michel

Hi Gary, Thanks for reporting. We'll take a look. With kind regards, Michel

Hi someguy, in addition to LeeG's comments right above, would you please do a quick browse through of your PLM links table and see if you have many IDENTICAL records. By identical I mean truly identical: everything is identical! Lately, we have had many reports of PLMs with identical records (which should be an impossibility) and thus contributing to large number for link count. With kind regards, Michel

Hello davidology, Yes, there are definitely plans to expand our Zigbee product support. This said, it all depends on demand for specific products. Specifically for Zigbee, unfortunately interoperability is only at a Profile layer. So, for instance, Home Automation Profile is NOT interoperable with RC Profile. SEP is not interoperable with anything else. So, we will basically have to figure out where most of the demand comes from and implement those. With kind regards, Michel

Hi Guys, We have had this request many times and we have decided against it for the following reasons: 1. ISY does not need to be backed up unless you are explicitly making changes to its configuration. In those case, it's always best to backup at success points. So, in short, once you are done with any configuration, take a backup and you are done 2. The problem of automatic backup gets into many intricate details of delta vs. full, at what times, during what events, blocked by what other events, and many different permutations thereof With kind regards, Michel

Hi Stephan, Please send to support@universal-devices.com. I am only interested in the negotiation packets. With kind regards, Michel

Hi johncrab, You cannot query a folder in programs. You can query scenes. Are we talking about the same thing? With kind regards, Michel

Stephan, I am not worried about traffic between ISY and the server. I am more interested in the traffic between your computer and the server. With kind regards, Michel

Hi jmed999, 3.3.3. With kind regards, Michel

Hi guys, Based on their documentation, the mode MUST be URL Encoded. I really do not know what else to try. Perhaps their server (HTTPS) requires client certificates. Or, perhaps they require higher level of security. If you have a 994, perhaps changing the strength to high might help: http://www.universal-devices.com/docs/I ... 0Guide.pdf Apart from the above, I really do not know what else could be contributing to this issue. Wireshark (not LiveHeader) traffic log would be quite useful. With kind regards, Michel

Hi Stephan, In your test (outside of ISY), please remove the cookie and let me know if it still works. I suspect that the server is maintaining a session. With kind regards, Michel

Hi Stephan, the problem is that I do not know what curl does. Can you send me a wireshark traffic of a system that works. I cannot fathom why you would get request failed for content-encoding header. With kind regards, Michel

Hi Stephan, viewtopic.php?f=27&t=9770 With kind regards, Michel

Stephan, Yes, it's on the agenda with a very low priority and thus no ETA. With kind regards, Michel