Michel Kohanim

Hello Tom C., Unfortunately not in the current releases but, based on your input, it shall be implemented in 3.1.17. With kind regards, Michel

Hello GreyFox, Your assumption is correct. When ISY connects to ELK, you will see ELK status messages at the top of the Admin Console. As per your screenshot, ISY is not currently communicating with ELK. This could be caused by three things: 1. You do not have the correct firmware version for ELK and ELK's Boot loader 2. When you changed ELK RP settings to support the non-secure port (2101), you didn't press the Send button to activate M1XEP with non-secure port 3. You have ELK RP connected ... ELK RP has to be disconnected for ISY to be able to communicate with ELK For 1, please review: http://www.universal-devices.com/mwiki/ ... quirements For 2, please review: http://www.universal-devices.com/mwiki/ ... guring_Elk With kind regards, Michel

Hi dss, Thanks so very much for the feedback. I do not think ZWave would work if the door lock is the only ZWave device in your network since: 1. Max range of ZWave radio is around 300ft 2. You need between 6 to 12 devices to have a good mesh (depending on the size of the location) We shall investigate Zigbee. With kind regards, Michel

Hello kaisersoze, You can currently do this by having a program that is only run at Start up. With kind regards, Michel

GreyFox, You absolutely do NOT need the ELK module. The most basic reason for buying the ELK module is "where do you want your rules to run"? If you are comfortable with the rules running in ELK (those that deal with alarm state and communicating with ISY), then you are all set. All you have to do is to export your lighting to ELK and then program rules. If you want your rules to reside in ISY, then you would need the ELK module. I hope this answers your question. With kind regards, Michel

Hello dss, Unfortunately not ... or at least not simply because there has not been much demand for it. Obviously, we are very eager to add more capabilities to 994iZ series ... just have to figure out support for devices with a little ROI. With kind regards, Michel

Hello gfridland, I have not seen those causing any issues but it might be that there are not very many installed. The best test would be to make sure you have good scene communications with all your devices. If you have failed communications with a few, please see if one is a ToggleLinc. With kind regards, Michel

Hello gfridland, Sorry, for the lack of update. This is fixed in 3.1.17. With kind regards, Michel

Hello ahwman, Excellent question and the answer is that we had complaints about the green not being bright enough. So, presupposing that ISY would be where the router is (and probably hidden) we went for the brightest blue LED on the market! With kind regards, Michel

Hi LeeG, Thanks so very much! I had completely forgotten. We should change that mostly because we use XML and, in some cases (not always) and some clients have a hard time with a / and differentiating it from /> especially when the / is at the end of the string. Admin Console work regardless but we had to put this constraint for some clients. Perhaps we can remove this limitation. With kind regards, Michel

Hello everyone, Thank so very much for the feedback. Even though there's currently no way for dimming the LEDs, we'll surely take this into consideration in our future HW designs. With kind regards, Michel

Hi Brett, I think you have one of those PLMs that have issues with RF devices. Please send an email to tech@universal-devices.com and we'll try to sort it out for you. With kind regards, Michel

Hi dsdee, Apologies I didn't see your post before. Which default names are we talking about? I am not aware of any default names with / in them. With kind regards, Michel

Hi Guys, Sincere apologies. All of these relate to intermittent program behavior when state variables were being used. In some cases, the old value of the state variable was still being used for evaluation even though a new event had updated the status. With kind regards, Michel

andyf0, what's the precise error please? dgm0522, please go to Event Viewer on Device Communications events and turn on/off a few of your switches locally. Do you see any events in the Event Viewer? Slalom, still investigating ... as you may note, a fix for this issue is not listed in our release notes. With kind regards, Michel

Hello Dwight, Are you putting the 5 minute button in a scene? With kind regards, Michel

Hello garybixler, Try https and if it fails please contact our tech support and we'll try to do it remotely. With kind regards, Michel

Hello all, Release 3.1.16 is now available. With kind regards, Michel

Hello all, Release 3.1.16 is now available. With kind regards, Michel

Hello all, I am happy to announce the availability of our 3.1.16 release! For a list of changes, please take a look at this post. This is a minor release to address some program evaluation issues. We are entering final stages of beta testing and hope to have an official release shortly. Your help in testing and identifying bugs is very much appreciated. Things to test: - Program evaluation for suboptimal INSTEON network configurations - Program evaluation for Integer variables including ELK connection - SwitchLinc Timer options Important Information 1. Due to the sensitive nature of supporting MorningLinc/ELK Security Systems, 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 2. 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. 3. Please note that Network Resource modules are now running in their own task. This might have some ramifications as calling network resources from programs no longer waits for the resource to complete. As such, a) you will experience quicker handling of network resources/programs and if you are using DSCLinc and WebLinc, your programs may behave a little differently. Please do test your network resources thoroughly 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. 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 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 7. IMPORTANT Once upgrade is completed and ISY reboots, use any of the following methods to access your ISY's Admin Console: a. 99/994i - http://isy/admin - applet (Windows only) b. 99/994i - 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/3.1.16 - applet f. http://www.universal-devices.com/99i/3.1.16/admin.jnlp - Java application 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

Hello wswartz, With TriggerLincs, you have to make sure you have a good battery and that you make sure it's in programming mode: press and hold the set button till it starts blinking. In all cases that I have dealt with, 99% of the time, the problem was the battery. With kind regards, Michel

Hello Pete, I am afraid that there's something else going on in your system. We did test IRLinc again with 3.1.15 (and 16) and they both worked fine. With kind regards, Michel

Hello connorrc, It's totally up to you what to do with the Finder as it has no bearing on the correct functioning of Admin Console. Basically, it's just a launcher. May I ask what firewall software you have? As far as conductor, do you have the problems locally or remotely? With kind regards, Michel

Hello elvisimprsntr, Thanks so very much for the update ... please do be kind enough to keep an eye and, if possible, provide as much information (even if completely irrelevant) at the time that this happens again. Hello handyman300, Tim, and sanders2222, We found some minor bugs which might be contributing to variables (specifically integer) not being initialized. We should have 3.1.16 our shortly with the fixes therein. With kind regards, Michel

Hello Pete, Thank you. We added code to support newer INSTEON devices in 3.1.15 and that might have something to do with this. The only way to rule this out, is if you would be kind enough to go back to 3.1.14 and let me know if this works. With kind regards, Michel