Michel Kohanim

Hello ingeborgdot, We are open today till 4:00 PM PST. Regular hours are M-F 9:00 AM - 4:00 PM PST. What you might want to consider is to go to your NetGear port forwarding page and remove all the port forwarding rules. Once this is done, you can add them back one at a time. Since your NAS uses 443, you will have to use a different port for ISY's HTTPS (such as 8443) and forward traffic from 8443 to ISY. Once this is done, your URL to access ISY will look like: https://ingeborgdot.dnsdojo.net:8443 ... please note that 8443 at the end of the URL. Once you are satisfied that this works, you might want to change your HTTPS port again (and repeat the above) as you do not know who's snooping around at the forum and now has your remote URL. With kind regards, Michel

Hello ingeborgdot, If you note, the certificate is NOT coming from ISY so the port forwarding rules have changed. If you are available today, send an email to support@universal-devices.com, we'll login to your computer and fix it. With kind regards, Michel

Hi CopyRon, It's fixed now. With kind regards, Michel

andf0, Unfortunately the problem was the migration from 3.1.9 to later releases as noted by IM and LeeG. If you do not have 3.1.8/9 backup, then the best thing to do would be to add those devices/scenes back. ooker, Please do make sure: 1. You have cleared your Java cache 2. You are using http://www.universal-devices.com/99i/3.1.13/admin.jnlp If you are still having problems, please contact our tech support so that we can login and do root cause analysis. FRR, You do not want to use Enabled because as long as you have ELK enabled in the configuration panel, then the condition is always true. Or, perhaps, you would want to use AND instead of Or. With kind regards, Michel

Hi John, It's possible that ISY's IP address has changed. Would you please try the following URL: http://www.universal-devices.com/99i/3.1.13/admin.jnlp With kind regards, Michel

Hello andyf0, I do apologize for the inconvenience. The fact that scene were missing is quite troubling ... is it possible fo you to restore a 3.1.9 backup and see if your scenes show up? polexian, Unfortunately I will have to leave the answer to your questions for our guru who's taking a well deserved breather for a couple of days. With kind regards,

Hi ingeborgdot, Would you be kind enough to be more specific? I am now confused as to the original issue: is it remote access using a browser? is it local access using a browser? Is it Admin Console local or remote? With kind regards, Michel

Hi gatchel, we'll look into it. Hi midrar, this is not normal at all. Please open the Event Viewer on Device Communications level. Make sure ISY can in fact make connections with your M1XEP. In 3.1.12, if ISY could not connect with M1XEP, it would get into a tight loop and thus would feel sluggish. As far as not being able to backup, what's the error (i.e. could not backup /CONF/xxx.yyy)? You are welcome to send an email to me directly. With kind regards, Michel

Hi ingeborgdot, You do not have to do anything with the http port. Please make sure you to port forward to port 8443. With kind regards, Michel

Hello all, 3.1.13 is now available: viewtopic.php?f=25&t=7399 With kind regards, Michel

Hello all, 3.1.13 is now available: viewtopic.php?f=25&t=7399 With kind regards, Michel

Hello all, I am happy to announce the availability of our 3.1.13 release! For a list of changes, please take a look at this post. This is a minor release with mostly ELK module bug fixes and enhancements: 1. Support for thermostats in ELK 2. Reliability enhancements ELK Integration Module ($99.00 ... 40% off during Beta using coupon code elk-module-beta). Please note upgrade to 3.1.13 must be performed before installing the ELK Module Important Information 1. ISY-26 is no longer included in the firmware builds 2. 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 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. 4. 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 5. 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. 6. 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 7. 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 8. For a discussion of variables, please look at our Program Variables forum. Things to test: - ELK Module (if you have ELK) - Device Restore, Replace, and scene settings - Adjusting scenes within programs continuously 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 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 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.13 - applet f. http://www.universal-devices.com/99i/3.1.13/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 junkycosmos, Thanks so very much ... looking forward to the result of your investigation. DON must be a bug ... it shall be fixed. With kind regards, Michel

Hello ingeborgdot, It's best to use the HTTPS (secure) port for remote access and port forwarding. I am not sure what's going on with your network but it seems that your NAS has opened up a port in your router. If you didn't do this yourself, that's cause for concern! With kind regards, Michel

Hi Tim, I think it would be best to schedule a call with our tech support team to see what's going on. Please note that if you already have port forwarding rules in your router, then you do NOT need File | Enable Internet Access. With kind regards, Michel

Hello ingeborgdot, Looking at the certificate, the URL is pointing to your NetGear router. This means that you probably have remote admin enabled on your NetGear and thus all traffic for port 443 are now going to your router instead of ISY. Two choices: 1. Disable the remote admin on your NetGear 2. Change ISY's https port to something else (i.e. 8443) and then redo your port forwarding to 8843 With kind regards, Michel

Hi Tim, If you do a Query on My Lighting, all your devices will be queried again and their status will be updated in the Admin Console. If your Admin Console is no longer communicating with ISY, then the only way is to either go to File | Login or close/reopen. With kind regards, Michel

kingtd, Are you specifically looking for button presses (i.e. Control) or status? There's no easy way to assertively figure out if someone is "actively" changing the debug level. We might have to implement a global one. With kind regards, Michel

Hello ingeborgdot, If you are certain your DynDNS is working properly, then the only explanation is: The port mapping has changed and thus you are not talking to a different device on your network (not ISY). You might want to check the port forwarding rules in your router to ensure that they are still going to ISY. With kind regards, Michel

Hello junkycosmos, Thanks so very much. FCS errors are frame check sequence errors which are usually related to hardware (including cable and duplex mismatch). I am not sure how we can troubleshoot this but here are some basics: http://www.pathsolutions.com/SwMonDemo/ ... Errors.htm Since you have already replaced the cable, would it be possible to connect to a different port on your switch and check the errors again. Do they increase/decrease/remain constant? With kind regards, Michel

Hello junkycosmos, Do you have an ELK system and, if so, do you have your ISY integrated with ELK? Completely benign. This is a configuration file for electricity monitor and since you do not have one installed, thus the entry ... Again, completely benign and a bug in 3.1.10. As you note, they all happen right before reboot ... the bug was that the system was not properly flushing the logs at reboot With kind regards, Michel

Hi Rick, It all depends on what device you are renaming. For instance, for KeypadLincs, there are multiple nodes (buttons) which may be renamed if you so choose (depending on the option you choose). You can always choose the option that renames that specific node. To see the hierarchy of nodes, right mouse click on a node and choose Group devices (if the menu item presents itself). With kind regards, Michel

Hello tunaman, did you get a 200 response code (success)? Hello Elvis, that's very good to know! Thanks so very much for the update. With kind regards, Michel

kingtd, The reason for stupidly turning the level back to zero is unnecessary network traffic. It's like running in debug mode and for devices that are connected to the Internet (some with 3G modems), the extra traffic is approximately 300 - 500% more than at level 0. What I do not understand is: what in debug information do you need for your EventGhost? In my view, all important events are already published. With kind regards, Michel

Hi Tim, There seems to have been an issue with upgrading the database records from 3.1.9 to 3.1.10. If you have 3.1.9 backup, it would be best to restore 3.1.9 backup and then follow the same File | Restore Modem procedure. With kind regards, Michel