Michel Kohanim

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

Hi Brian, Admin Console was not designed as a nice user UI. It was designed for configuration and administration. Dashboard will probably be used (once finished) for nice user experience for command and control. With kind regards, Michel

Hello all, For a list of bug fixes/enhancements in 3.1.13, please see this post. tunaman The problem with zone names not populating is because we do not have a refresh topology button in 3.1.12 (it has been added to 3.1.13). So, all you have to do for now is to type the following in your browser: http://your.isy.ip.address/rest/elk/refresh/topology ... if you are on windows, you can try http://isy/rest/elk/refresh/topology FRR It seems that you installed the module before the upgrade. The only way to recover is for us to reactivate the module for you. Please do be kind enough to send your Google invoice to sales@universal-devices.com with subject Reactivate. polexian If you have Run at startup, then enable/disable flag is ignored With kind regards, Michel

Hello Brian, Unfortunately not in the Admin Console but some third party apps (such as MobiLinc) allow you to define specific tags for specific states. With kind regards, Michel

tunaman, I just went through some troubleshooting with another customer and the problem was that port 2101 was NOT sent to M1XEP. To test whether or not port 2101 is open, on RP: 1. Go to account 2. Bottom right corner change the port to 2101 3. Connect using Network If this does not work, then click on M1XEP setup and then click on the Send button. In short, the same exact settings for 2101 using RP should work with ISY. With kind regards, Michel

Hi Gary, That should be fixed in 3.1.13 (refresh topology). With kind regards, Michel

boot/tunaman, We are going to have another release shortly which will have more diagnostics information. At the moment, it would be best to wait for the new release (3.1.13). wwat, my pleasure and sincere apologies for all the problems. With kind regards, Michel

tunaman and boot, can you make sure that M1XEP supports 2101 port (in ELKRP Account Settings). apostolakisl, unfortunately I do not have the answer. We used the latest firmware on both. With kind regards, Michel

Hi boots, Is ELK RP connected to your ELK at the moment? Please note that if ELK RP is connected then you will have problems connecting ISY. Also, do you have the latest firmware for M1XEP and ELK M1? With kind regards, Michel

Hi tunaman, Do you have ELK RP connected? 3.1.13 which is to be out shortly, has more diagnostic features and perhaps can help us troubleshoot. With kind regards, Michel

tunaman and boots, Both of those problems are related to the fact that ISY cannot extract information from ELK and then gets into a tight loop (this has been fixed in 3.1.13 to be out shortly). What you need to do is to make sure: 1. Your M1XEP and ELK M1 have the latest firmware without which you will experience other intermittent behavior including sluggishness and unresponsiveness 2. Make sure you can connect to M1XEP on port 2101 ... you can try: telnet m1xep.ip.address 2101 Please do keep us posted. wwat, that's really odd. I think we have to start thinking about a new SD Card With kind regards, Michel

Hello all, wwat, this is not normal and it does go back to the problem of missing links. Please do be kind enough to run your scene profile programs and ensure that you are not losing any database links. If you do, then we would really have to think about hardware/file system issues. andyf0, yes, we should have a fix within the next couple of days. IM, that should also be fixed (reporting connection to ELK even though you do not have the module installed). Please make sure you have the latest ELK/M1XEP firmware. elvisimprsntr, that's not good. Would you be kind enough to keep an eye and, the next time in happens, can you check and see if you get status from other devices (such as INSTEON)? Is it possible that you may have used two different URLs? With kind regards, Michel

Harold, 1. The null modem cable only comes with 99i PRO series. Are you sure it's PRO? 2. It's indistinguishable from any other serial cable (M-M) 3. If that's all you are looking for, please send us your shipping address to sales@universal-devices.com and we'll mail one out to you With kind regards, Michel

Hi Tim, I think this post should explain what you need to do: http://email.about.com/od/accessingmobi ... ttings.htm With kind regards, Michel

Hi Tim, what is your server? You have to make sure you use the correct port for your specific server. Also, please note that some ISPs mail servers, do not require userid/password (you are already on their network). With kind regards,

Hello all, Sincere apologies for the late response. As andyf0 mentioned, we found the issue with Request Failed or otherwise error dialog at start up. chuck_b, please note that you need to have latest version of ELK firmware and ensure that the access code is entered. If you are still having problems, please do contact our support and we'll log in remotely to see what's going on. We found an issue where ISY would try getting the topology from ELK while ELK would not respond properly (older ELK versions). polexian, we will look into ... elvisimprsntr, are your ELK information being updated locally? The humidity sensor on your thermostat; can you please let me know how this can be reproduced? With kind regards, Michel