Michel Kohanim

Hi Brian, Known issue which should be fixed in the next release. Thanks and with kind regards, Michel

Hi Charles, If you are using Ubuntu, there's a known problem with Java whereby you will have to add manual links to Java libraries. Yes, I would love to check it out remotely. Please do be kind enough to send your URL and credentials to tech@Universal-devices.com. With kind regards, MIchel

Hi Kevin, Yes, because ISY currently manages all communications with devices using atomic operations. We do very well know what every bit of information does, where it goes, and what the outcome should be. We also know what exceptions we should take into consideration. And, most importantly, we make Restore points to which you can always return. Now, if we open up sending arbitrary INSTEON commands through ISY, we run the risk of not being able to help our customers figure out where the problems are if any. And, we can never run a Restore device. With kind regards, Michel

Hello andyf0, yes, consider it done. Brian, if and only if you have 994 with Zigbee enabled. So, this is a bug. Thanks for reporting. With kind regards, Michel

Hello junkycosmos, We did get a hold of them and we do have plans to support their products. Currently, we are 100% focused on ELK integration. With kind regards, Michel

Hello jz6pwc, What happens if you right mouse click on the program and the click Run Then? If this works, then the problem is the condition not being evaluated to true. If this does not work, then please check your Error Log for errors starting with -50000 and let use know what they are. If neither, then please check your junkmail. With kind regards, Michel

Hi Illusion, I assume this is on MAC. I cannot reproduce on MAC. All, do you see the same problem on your PC/Linux? With kind regards, Michel

Hi All, Thanks so very much for the feedback! Illusion, thank you ... the post has been updated (see above). andyf0, what URL are you using? Please make sure you are using your local ISY Admin OR the server URL at /99i/3.1.3/ Nick, thanks so very much! Done. As you may have noticed - and as per your request - our version of ISY AJAX is also open source. Everyone is welcome to make improvements and we'd be delighted to hear your comments. ergodic, for #1, please make sure that you have cleared your Java cache and that you are using the latest UI (3.1.3). For #2, we'll investigate and get back to you. With kind regards, Michel

Hello ingeborgdot, What is your heat setpoint? If you are in Auto mode, you cannot have your cool set point be lower than heat set point (by 2 degrees). With kind regards, Michel

Hi All, Release 3.1.3 is now available: http://forum.universal-devices.com/viewtopic.php?t=6449 With kind regards, Michel

Hello all, I am happy to announce the availability of our 3.1.3 release! For a list of changes, please take a look at this post: viewtopic.php?t=6015 Things to test: Evapotranspiration AJAX Interface Variables For a discussion of variables, please look at the new Program Variables forum viewforum.php?f=68 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 3. 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 before the upgrade: http://www.universal-devices.com/mwiki/ ... rtificates 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 ... _3.1.3.zip OR 994i Series: http://www.universal-devices.com/update ... _3.1.3.zip 3. Important (If upgrading from 2.8.5 through 2.8.14) Due to invalid Java certificate chain, 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 ) 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. 99ihttp://isy/admin'>http://isy/admin - applet (Windows only) b. 99ihttp://isy/admin.jnlp'>http://isy/admin.jnlp - Java application (Windows only) a. 994ihttp://isy/admin - applet (Windows only) b. 994ihttp://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/3.1.3 - applet f. http://www.universal-devices.com/99i/3.1.3/admin.jnlp - Java application Thanks and with kind regards, Michel

Hello deirwin, A simple test would be to remove ELK configuration (the IP address/port) from ISY and see if the problem persists. This way, at least we know if the problem is ELK related. With kind regards, Michel

Hello Kevin, Unfortunately you cannot. I am so very sorry. With kind regards, Michel

Hi Brian, I am so very sorry to hear. This is not good. Please do be kind enough to send your error log to support@universal-devices.com and we'll take a look at it. Also, would you please disable the plugin and see if you are still having the same issues? With kind regards, Michel

Hi Brian, Yes, both the error logs as well as the logs are persistent (unless you do a factory reset). I do not recognize these errors. Where are they coming from and which plugin are you referring to? With kind regards, Michel

Hi Brian, Thanks so very much. This will be the only test necessary to figure out if the problem is with configuration or hardware. In the meantime, if you have not factory reset yet, would you be kind enough to send us your error logs (support@universal-devices.com). Thanks and with kind regards, Michel

Hello ssingh1234, Unfortunately I am out of ideas except: 1. Please factory reset the one that used to work when you used option 1 2. Make sure you are within a range of an access point 3. The actual door lock is close to ML With kind regards, Michel

Hello Brian, 1. Do you have self signed certificates? 2. If you have a good backup, please factory reset your ISY and then let me know if it stays up 3. If it does, please go to Tools | Diagnostics | PLM Status/Info and let me know what you see With kind regards, Michel

Hello thruster999, What's your ISY's firmware version? Also, when this happens, you do not get any status updates back from the motion sensors in the Event Viewer or do you? Do you get any green 0101 icons next to any of your devices when this happens? With kind regards, Michel

Hello ssingh1234, Just to be certain, did you follow the instructions here: http://www.universal-devices.com/mwiki/ ... orningLinc ? It's very important that you choose the 3rd option otherwise everything will be removed. With kind regards, Michel

Hello rossarmstrong, Evapotranspiration was added to our 3.1.3 release to be out shortly. The accuracy depends on the averages of temperature and humidity as provided by WeatherBug. Testing was minimal since we really do not know the points of reference except those freely available on the Internet. With kind regards, Michel

Hello cashoefman, Thank so very much for your contribution! With kind regards, Michel

Hello thruster999, On level/ramp rates/scene activations are all stored in devices themselves and ISY is bypassed for those types of scenarios. So, no, ISY is not the problem here. The problem is that the responder or the controller in that scene are losing their links and therefore do not communicate with one another properly. If the problem is isolated only to scenes with motion sensors, I strongly advise against restoring EVERYTHING for two reasons: 1. Now, we do not know which one of your devices were causing the problem 2. Restoring things that do not need to be restored is a waste of our valuable time So, if this happens again: 1. Restore the responder (KPL or SWL or whatever device responds to your motion sensor or the scene in ISY). If this works, then the problem is the responder 2. Restore the controller (i.e. the motion sensor). If this works, then the problem is the motion sensor 3. If the problem is that on level/ramp rates for a specific scene when activated from ISY are lost, then restore the PLM. if this fixes the problem then the issue is a defective PLM With kind regards, Michel

j0dan, Perhaps but this will go to the core networking and quite abrasive when it comes to regression testing. What are you trying to communicate with? With kind regards, Michel

Hi j0dan, DNS resolution requests are not thread safe and therefore, we put a lock around it and thus the delay. So, you should see a variable amount of delay depending on what other network activity/operation ISY is currently performing. With kind regards, Michel