Michel Kohanim

WARNING Although we are quite confident that the severity and the number of any bugs is quite low, however this is still not an official release and thus there might be bugs that have not been uncovered during our testing. As such, any changes made to ISY may be lost because you may have to either restart or restore a backup from release 2.7.7, 2.7.11, or prior official releases. ------------------------------------------------------------------------------------ Hello all, Thank you for your support in helping us go through the alpha and beta stages of 2.7.8 and above. With the release of 2.7.14 RC1, we feel that we have an extremely stable system and, if all goes well, the next release will be an official release of 2.7.15. Please review the list of fixed bug and enhancements here: http://forum.universal-devices.com/viewtopic.php?p=6475 Do be kind enough to test as many of the items as possible and specifically registering devices within ISY and creating/removing scenes. For those who have PRO series, it would be great if batch functions are tested thoroughly. Instructions 1. Please backup your ISY (File | Backup ISY) 2. Please download the firmware for your platform - please do not unzip a. ISY 26 - http://www.universal-devices.com/update ... nsteon.zip b. ISY 99 - http://www.universal-devices.com/update ... nsteon.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 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.7.14 - applet f. http://www.universal-devices.com/99i/2.7.14/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 9. General instructions (especially for adding V2 thermostats) for the new features in 2.7.7+ can be found here: http://forum.universal-devices.com/view ... hp?p=27368 Upgrading from 2.7.8 through 2.7.10 Upon reboot, ISY tries to migrate all configuration files to release 2.7.12 levels. This said, however, in the case of KeypadLincs, the following settings shall be lost (ISY will be out of synch with your devices) for those KPLs that were setup/configured in 2.7.8 or 2.7.9: a. Button toggle mode b. Button backlight c. Button groupings (in scenes or otherwise) d. Button mutual exclusivity As such, if you have setup any KPLs in 2.7.8 or 2.7.9, it's best to remove them from ISY, do a factory reset on them, add them back and reconfigure them. Alternatively - and you have not made massive changes using 2.7.8/9, you can restore your 2.7.7 backup (File | Restore ISY) and let ISY migrate everything. Thanks so very much for your help and support. With kind regards, Michel

Hi krenzk, Query All in releases 2.7.11 and above only logs status of devices if they have actually changed (i.e. there's a mismatch between ISY and what the status is actually is). With kind regards, Michel

Hi sk8er2, What firmware version do you have and who is your ISP? There were some bugs with Verizon FIOS not allowing packets with 0 size window to go through. We put a workaround for it in 2.7.13. With kind regards, Michel

Hi biffom, Thanks so very much for the information. We are actually working (concept) of adding more feature to the Network resource to make it more functional. Unfortunately I cannot give you any ETAs since we are still in the concept phase. Thanks again and with kind regards, Michel

Hi Larry, Yes, absolutely. If your unit is still under warranty, please do send an email to sales@universal-devices.com (closed Tuesday/Wednesday this week) and we'll make sure you are covered. Please note: 1. Use a new SD Card. If you have an old SD Card, please format using FAT16 2. Once you get ISY up and running, then go to http://www.universal-devices.com/99i/[your_isy_firmware_version] 3. Login 4. Upgrade using the latest firmware 5. Once upgrade is complete, Restore your backup With kind regards, Michel

Hi Larry, I am so very sorry to hear this. This seems to be a file system error. Please try removing the SD Card, inserting it back in, and try the restore again. For some reason, it seems as if the whole SD card has been wiped out. If that's the case, we can send you a replacement OR if you have an SD Card, you might want to have it replaced. Once replaced, first go to our website to login to your ISY, secondly upgrade the firmware, and finally restore your backup. With kind regards, Michel

Hi jkraus, Even if you had a power failure and if ISY had started up again, then you would see everything in the log. The only case would be that ISY was completely powered off. This has nothing to do with network connection. Please do keep an eye for a few days ... if you don't mind, please have the Birch light program run more often. With kind regards, Michel

Hi jkraus, The power LED was on when you got home, correct? Do you or have you ever had IRLinc TX installed? Beyond that, I am afraid that we have had a system crash which is most probably hardware related. With kind regards, Michel

Hi jkraus, It seems that ISY went offline at 9:38 PM on 3/27. Since I do not see anything between that time and the time you rebooted and since you noted that the power LED was on, I have no choice but to assume a system crash or an infinite loop. Can you tell me which programs turn on/off the Birch Tree? With kind regards, Michel

Moshe, Excellent and so very glad to hear. And, thanks for the update. With kind regards, Michel

Hi jkraus, That is horrible ... I do not think it's related because ISY could not communicate with your INSTEON devices. Can you check the log entries for the day before you came back? If you have many -2s, then we have to figure out what's causing the PLM not to communicate with your INSTEON devices. If you do not have many -2s, then I would like to know the last 30 entries before the last Start record (which is when you rebooted your ISY). With kind regards, Michel

Hi cnutco, I am so very sorry to hear this. If you have a backup from before the port forwarding endeavors, you can restore it ... this way you do not have to start from scratch. Also, please do contact our tech support to help you setup port forwarding in your router. With kind regards, Michel

Hi Dave, Apologies for the inconvenience. Unfortunately 26 does not support V2 thermostats due to memory constraints. With kind regards, Michel

Hi Moshe, What this means is that you have a mapping between port 443 to the new port on your ISY. In most routers, when you create port forwarding rules, they allow you to provide an public port (i.e. 443 in your case) and a private port (i.e. your ISY's new port in this case). What you want to do is to make sure that the public port is EQUAL to the private port (=ISY's new port). With kind regards, Michel

ScottK, It should turn on/off when you activate/deactivate the scene regardless of controller/responder. I recommend doing a restore on your KPL. If that does not help, please do a compare between ISY/KPL links. Last resort: factory reset your KPL and then restore from ISY. With kind regards, Michel

Hi Moshe, Can you let me know which one of the following URLs work on your local network (not internet): httpS://your.isy.ip.address httpS://your.isy.ip.address:new_isy_port With kind regards, Michel

Hi Moshe, I am completely at a loss! From what I know of routers and NAT (network address translation), your case is simply an anomaly! Are you sure you do not have any port forwarding rules for port 443 pointing to ISY? Beyond that, unfortunately, I really do not know what else could be wrong except perhaps a bug in the router. Have you tried rebooting the router? With kind regards, Michel

Hi ScottK, I am not certain I understand the question since you can always add KPL buttons as responders to as many scenes as you may wish. And, there's no limitation of the buttons to have to be controllers. With kind regards, Michel

Hi Jeff, thank you. We're doing a root cause analysis to see what's causing this behavior on MAC ... unfortunately, we cannot reproduce it on the 32 bit but we have not given up yet. With kind regards, Michel

Hi io_guy, Thanks so very much. It does make sense. With kind regards, Michel

Hi io_guy, Please see my comments below. With kind regards, Michel Unfortunately, that's the only way. Precisely Any reason why you do not use a scene with the sub button as a controller?

Hi Moshe, I would certainly look at the DMZ ... you will find it under firewall section. DMZ basically means that your ISY is on the internet and all traffic is forwarded to it. Davonavo, thanks so very much. Sometimes I forget that some of these terms are a little technical. With kind regards, Michel

Hi Jeff, Thank you. Would you be kind enough to go to Java Preferences and look at the order of JVMs. If you have a 64 bit machine, then the 64 bit version should be listed first. With kind regards, Michel

Hello kingwr, Thanks so very much for the feedback. I must apologize to all for the wrong information; it seems that even I was under the wrong impression. Here's how things work: For every event that is related to a condition for which there's a program, the whole program is re-evaluated and the execution of the Action part starts from the beginning. kingwr, specifically to your point, if the status does NOT change, then the execution continues. If the status changes, then the WAIT/REPEAT are interrupted. So, if you want your motion sensors to keep starting from the beginning, then you should use Control instead of Status. Of course, this does not completely address your concerns (the execution starts from the top) but it will alleviate having to write multiple programs. We will be working on enhancing the program structure and execution and your comments/suggestions are surely taken into consideration. With kind regards, Michel

kingwr, As you may have seen, we are quite eager in improving ISY. The main problem is that, at the moment, I am not entirely sure what it is you are requesting. Is it not to stop the wait when the condition is turned to false? As far as folders, I did respond to your previous post but never got a response back. As Rand suggested, the first and foremost the folders are used for organizational purposes. Just like any other folder concept out there. Secondly, and more importantly, folders allow for reuse of conditions. In short, why would you want to have the same condition repeated in 10 programs when it can be added on the folder as a constraint? Now, if you could possibly let me know what it is you are after, then we would surely take it into consideration. With kind regards, Michel