Michel Kohanim

Hello ficklma1, Apologies for tardy reply ... I think it's best for me to explain how ISY works so perhaps it will give you some pointers: 1. There are a limited number of HTTP tasks 2. REST and Admin Console communicate with ISY through the HTTP tasks 3. Some HTTP tasks are synchronous and thus will wait for the operation to be completed 4. Operations that are device related are synchronous, so, the task doing the job is going to wait for the process to finish 5. If you send REST commands continuously to increment/decrement setpoints, you will eventually exhaust all the HTTP tasks (some of them are waiting for the first one to complete) 6. In the case of thermostats, each operation may take up to a 35 seconds depending on the communications reliability. So, in case you have issues with a thermostat, and in case you have exhausted all HTTP tasks (by changing the setpoint continuously), then you will not be able to access ISY till all operations are complete. This might take a few minutes In short, instead of rebooting ISY, please wait for a couple of minutes and observe the RX/TX LEDs. If they are still blinking (even though infrequently), then ISY is still trying to complete all the tasks. Hi James, That does not make sense at all. Did you have communications errors? Adding them back to ISY is not going to solve the original problem which I think is PLM related. Next time this happens, please call our tech support before taking drastic measures. Hi dennisric, 1. What URL are you using? 2. What is your firewall software? With kind regards, Michel

Hello cartwrig, Although not advised, but it should not matter since we track each message sent out and wait for the correct response from the same device. If anything fails, you will see the 0101 green icons as an indication that there are pending writes and then you can take corrective measures. With kind regards, Michel

Hello dcardellini, Apologies for tardy reply. What is your ISY's firmware version? When you are local, what URL do you use to access your ISY? With kind regards, Michel

Hello ficklma1, Thanks so very much for the detail. 404 means that the REST command failed; i.e. it could not complete the task so perhaps ISY is having problems communicating with your thermostat. May I humbly suggest the following: When you get REST errors, would you be kind enough to go back to the Admin Console and check and see if the icon for your thermostat has changed to ! ? With kind regards, Michel

Hello thruster999, The SP version is SmartHome PRO version. I am not entirely sure what the difference is. For ISY, we consider both the same. With kind regards, Michel

Hello ficklma1, Please do make sure you do not have any 0101 green icons on any of your nodes. It might be the case that ISY is trying to write pending updates. With kind regards, Michel

Hello Avonlea22, Sincere apologies for missing this post. The answer is, YES, provided that: 1. You have firmware version 2.7.15 and above 2. You either use Start Linking and then use the Set Button OR you use Auto Discover in Add New INSTEON Device 3. Your thermostat mode is OFF when you link With kind regards, Michel

Hello bmarsh, What happens if you go directly to the ISY's IP address? Or, in the case of Finder, adding http://your.isy.ip.address in the list? With kind regards, Michel

Hello ficklma1, Yes, 2.8.15 MUST fix that issue. Please do let us know if it didn't. bocaray, thanks so very much. Looking forward to your feedback. With kind regards, Michel

Hi Jeff, I am certain that was the issue! Thanks so very much for the update. With kind regards, Michel

Hello Jeff, Yes, sincere apologies ... that was for you. Backup requires higher bandwidth and more encryptions per cycle. If you do not mind, would you please change your userid/password to admin/admin, send your remote URL to tech@universal-devices.com ... I would like to make sure we can do the backup remotely. With kind regards, Michel

Hello Avonlea22, What is your ISY's firmware version? Please make sure you are on 2.8.15. If you are certain that you are using Link Management | Start Linking, and if you still get v00, then in all likelihood it's a defecitve thermostat dongle. With kind regards, Michel

Hello all, jcanter, thanks so very much for going through the process. If possible, would you please try changing your https port to something else. I think the problem is that your router is somehow interfering with port 443. Enable Internet Access requires the router to respond to UPnP requests. This is not a very reliable method since, some routers do not actually do it properly and thus you will be left with Internet Access disabled. Whenever you reboot ISY, ISY tries to figure out whether or not there are any port forwarding rules for it in the router, removes them, and then recreates them. I suspect when ISY reboots, it has a hard time configuring your router. bocaray: 1. Please do not do hard reset. Please unplug your PLM, wait a second, and plug it back in ... I want to isolate the problem and I think it's PLM related 2. The enabled checkbox is a known bug 3. Unfortunately you cannot run programs based on communications errors ... the major problem with that is that it's going to get into infinite loop With kind regards, Michel

Hello johnmsch, I have an old one here that does support double click. In your programs, you would want to use Control and Fast On (double click on) and Fast Off (double click off) as conditions. Then you can turn on/off a scene (or other 3 devices) accordingly. With kind regards, Michel

jcanter: 1. Do you use File | Enable Internet Access to enable remote access or do you have manual port forwarding rules? 2. The auto update status has nothing to do with ISY. In the Admin Console, there's a little piece of code that checks to see if you need to upgrade to the next official release. I suspect your computer has not internet connectivity ... or it could have been a glitch in our server (but I cannot reproduce now) bocaray: This does not make sense at all since the configuration files do not change when you upgrade. Would you please simply reboot your ISY and see if you experience the same issue? And, if you do, instead of linking everything again, please simply unplug the PLM, wait a minute, then plug it back in. Let me know if that works please. Jeff: I do not recommend upgrading remotely. The SSL issue you are experiencing is probably due to a bad SSL certificate. Did you install one for your ISY? With kind regards, Michel

Hello Brucem, What firmware version do you have on your ISY? It's quite odd what you still get v00 even though you are using Start Linking. There are only three cases: 1. You do not have the correct ISY firmware ... please make sure you use the latest 2.8.15 2. Your thermostat adapter is not V2 3. You have a defect thermostat adapter With kind regards, Michel

Hello all, Release 2.8.15 is now available: http://forum.universal-devices.com/viewtopic.php?t=5935 With kind regards, Michel

Hello all, I do apologize for all these releases ... we just want to make sure that we have nailed down all serious bugs. There was an extremely rare case of race condition in the presence of incessant DSCLinc activity which triggered programs that tried to communicate with devices that had communications problems (adjusting scenes). Hopefully this is the last release before our official release. Things to test: Please use any REST device (including DSCLinc) and bombard ISY with requests of varying types and specifically those that call Programs. For a list of changes, please take a look at this post: http://forum.universal-devices.com/view ... =6475#6475 Notes: 1. ISY-26 is no longer included in the firmware builds 2. 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 Instructions: 1. Please backup your ISY (File | Backup ISY) 2. Please download the firmware for your platform - please do not unzip ISY 99i Series: http://www.universal-devices.com/update ... 2.8.15.zip 3. Important Due to invalid Java certificate chain in releases 2.8.5 and above, please make sure to remove all Universal Devices certificates from Java: a. Close all browser sessions b. Open Java Control Panel (Java Preferences on MAC) c. Click on the Security tab. Remove all Universal Devices certificates (on MAC, click on the '-' button at the bottom) e. Clear your Java Cache ( http://www.universal-devices.com/mwiki/ ... Java_Cache ) f. Go to http://www.universal-devices.com/99i/2.8.15/admin.jnlp 4. Login to the Admin Console and choose Help | Manually Upgrade [the name of your system] 5. Choose the file saved in step 2 MAC users: if upgrade fails, please add https://your.isy.ip.address to ISY Finder (see 3f above) 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.15 - applet f. http://www.universal-devices.com/99i/2.8.15/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 Thanks and with kind regards, Michel

Hello Bruce, I am so very sorry ... I am just relaying the information I got from SmartHome. I have two SWLs here one of which is Dual Band and I still cannot do LED brightness. The other one works fine ... In summary, if you look at the event viewer, and if you see traffic when you adjust brightness, and if your SWL does not respond, then the problem is with the SWL (probably does not have the correct firmware version). With kind regards, Michel

Hi Brian, I am not sure! Although I do not think upgrade is going to help, but please upgrade to 2.8.14 so we have the same point of reference. Also, can you send beep commands through programs and does your SWL actually beep? With kind regards, Michel

Hi clockwrkz, I am glad it worked. The reaso for two nodes is because that's how SmartLabs defined the on/off groups for ML. If you are not going to use them in scenes, then they are identical. With kind regards, Michel

Hello clockwrkz, As per instructions here: http://www.universal-devices.com/mwiki/ ... orningLinc It's very important for you to choose the 3rd option when you get the Linking Dialog. If you don't, nothing will work. Please repeat the factory reset, removal from ISY, and adding back in but make sure you use the 3rd option. With kind regards, Michel

Hello clockwrkz, I do think that the problem is with your MorningLinc; the reason is that ISY can communicate with it and MorningLinc is responding back to ISY. So, the communications are working properly. Somehow, these communications are not initiating a command to the door lock. The next thing to try is to factory reset your MorningLinc and then restore it from ISY. With kind regards, Michel

Hello kevkmartin, Not publicly. With kind regards, Michel

Hello k7zpj, Thanks for the update. Only SwitchLincs with BEEP support LED brightness. With kind regards, Michel