Michel Kohanim

Hello All, Thanks so very much for all the feedback. I managed to reproduce the problem on our iMAC. The problem is that [for some unknown reason] the latest MAC does not send the HTTP body within the ISY alloted timeout (and hence invalid length since not all the body was sent). Thankfully, you can set the HTTP/HTTPS timeout value for ISY: 1. Telnet to ISY 2. Login 3. Issue CWT 4. Change the HTTP timeout to 10000 or above Alternatively, you can use the following URL: https://your.isy.ip.address/admin OR https://your.isy.ip.address/admin.jnlp Since HTTPS has a higher timeout value, the upgrade succeeds. I tried both methods and both succeed. With kind regards, Michel

Hi PBusby, I am a little concerned that something may not be quite right: I have never heard of 12 hours of processing! Would you be kind enough to go to Tools | Diagnostics | Event Viewer, change the level to 3 and let me know if you see any traffic whatsoever on the event viewer. If ISY is still spidering your network, you should see quick successions of INST-ACK and INST-SRX every 500 milliseconds. With kind regards, Michel

Hi David, I just want to make sure we are talking about the same thing: Static IP address is for your ISY and in 99.9% of the cases it has nothing to do with your ISP (such as Quest). What you want to do is to assign a static IP address for your ISY and the forward port 443 to that IP address. As far as the console not working, would you be kind enough to let me know which URL you are using? With kind regards, Michel

Hi mitch236, Two questions: 1. What happens if you try to turn on that device using the Admin Console or our HTML interface? 2. Do you get status updates in the Admin Console if you turn on/off that device physically? With kind regards, Michel

Hi Glenn, Is your sunset time still 20 minutes off? If so then our lat/long values are wrong for Toronto. Please keep me posted. With kind regards, Michel

Hi Clarence, Yes, they are pretty good at it. With kind regards, Michel

HI Clarence, No. Only SwitchLincs version 35 (as reported by the Admin Console) and if and only if you have communications problems. With kind regards, Michel

Hello all, Thanks so very much for the reports. For those of you with invalid length errors (which means ISY did NOT get the whole packet), please do be kind enough to try the following: 1. Firewall software cannot be turned off or disabled. In most cases, specific actions should be taken to make sure ISY is a trusted application 2. Reboot ISY 3. Make sure you are using http://your.isy.ip.address to access the Admin Console If you are still experiencing issues, please do contact us and we'll try to upgrade remotely. Simon, md5 checksum is something that we have been wanting to do for a long time and just haven't had enough time to spend on it. With kind regards, Michel

Hi Glenn, Thanks so very much. Let's take it one step at a time: 1. If sunrise/sunset times are off by 15-20 minutes, then you must choose the correct location for your ISY (Configuration/System tab). Sunrise/sunset times are calculated and must be accurate to within 1 minute 2. If you could not control your devices from the Admin Console, then I am really suspecting that something is blocking the communications with ISY. This is especially the case since you do not see any status updates either If you cannot discern a pattern for when these timers do not work, then the best thing to do would be to have a simple program that checks the status of your bathroom switch (and send you an email or SMS to your phone). If you do not get the message then we'll use the Event Viewer to see if we are actually seeing the status change in ISY. With kind regards, Michel

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 stages of 2.7.8 and above. With the release of 2.7.13 BETA, we do now have a very stable firmware. 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. 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.13 - applet f. http://www.universal-devices.com/99i/2.7.13/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 Paul, I would ignore the XML parse error for now since it probably has to do with your firewall. The little green arrows with 0101 mean that ISY needs to write updates to your devices but it has not been able to. This points to device communication errors: i.e. the signals do not reach the devices from the PLM. Now, a few questions: 1. Do you have any SWL 35s installed? 2. Do you have any CFL/Halogen lights? 3. Do you have any SignaLinc RF devices (with antennae)? With kind regards, Michel

Hi, Thanks so very much for the programs. I have three more questions: 1. Please open Tools | Diagnostics | Event Viewer on level 3 ... then, please turn on/off your bathroom switch. Please let me know if you see any traffic. Especially, I would like to know if the status of your bathroom switch changes in the Admin Console 2. Please let me know if the sunrise/sunset times are accurate on the top portion of the Admin Console 3. Can you turn on/off any device from the Admin Console? With kind regards, Michel

Hi Mark, Currently - and as far as we know - only two systems use this feature: TouchSwitch ... which also works with folders IES touchscreen We are waiting for IES to migrate to folders and then we'll remove the floorplan altogether. With kind regards, Michel

Hi drglenn, Yes, absolutely. All new LampLincs (especially the dual band one) have sense feature which means that: 1. You can use Control - on/off/dim/brighten/fast on/fast off in programs 2. Use the device as controller in a scene. This way, if someone manually turns on the LL, the responders in the scene for which the LL is a controller shall respond accordingly With kind regards, Michel

Hi Ken, In addition to Rand's suggestions, please note that there was a bug with firmware 2.7.6 and below which caused this behavior. If you have not yet, I strongly recommend upgrading to 2.7.12. With kind regards, Michel

Hi Glenn, Can you cut and paste one of the programs that quit working? With kind regards, Michel

Hi Ron, I am not sure how would ISY communicate with this device since it's neither INSTEON nor do we even know what type of RF device it is. With kind regards, Michel

Glenn, Please try any of the following URLs: http://www.universal-devices.com/99i/2.7.12 http://www.universal-devices.com/99i/2.7.12/admin.jnlp http://your.isy.ip.address/ http://your.isy.ip.address/admin.jnlp With kind regards, Michel

Hello stevehoyt, Apologies for missing this post. I will include it in our list of requirements but please note that this will have a very low priority simply because what you are requesting causes all statuses to be wiped out and requeried. This may take a long time depending on the total number of devices and may make the whole system inoperable. We can possibly make it an option. With kind regards, Michel

Hi Glenn, If you have version 2.7.6 and below, then time might be off (gone to 1941) ... I strongly recommend upgrading to 2.7.12. If you are already on 2.7.12, would you be kind enough to provide more information: 1. The scenes work ... so it's not the PLM 2. What are the common characteristics of the programs that do not work? With kind regards, Michel

Hi mitch236, If you are going to replace both: 1. Backup your old ISY and then unplug both the PLM and ISY 2. Connect the new ISY to the new PLM 3. Log in to the Admin Console on the new ISY 4. Restore your backup from #1 (File | Restore ISY) 5. Let the system reboot 6. Log back in to the Admin Console 7. Click on File | Restore Modem (PLM) With kind regards, Michel

Hi aLf, Apologies for the confusion. You cannot cut and paste the whole URL since the editor builds the stream for you with all the headers. Please send me the URL you wish to access and I'll create a rule for you and send it back for you to import (tech@universal-devices.com). With kind regards, Michel

Hi mitch236, This happens when the Admin Console tries to contact our website to see if there are any updates available for your ISY and it fails. The causes could be: 1. In corporate settings, there might be a firewall that stops communications with our server 2. No network connection 3. Our server could have been down With kind regards, Michel

Hi aLf, 1. Go to Networking | Network Resources tab 2. Double click on the middle column 3. A Resource Editor Dialog will pop up and will let you update the resource specifications With kind regards, Michel

Hi ingeborgdot, Click on any one of the sensor nodes (on the left) and then click on the Set Options on the mid/bottom of the right panel. You will see a Darkness Sensitivity field which you can adjust. Unfortunately, when the sensor is off, you cannot communicate with it simply because it goes to sleep mode. This is required otherwise you would run out of batteries every few weeks. With kind regards, Michel