Jump to content
View in the app

A better way to browse. Learn more.

Universal Devices Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Michel Kohanim

Administrators
  • Joined

  • Last visited

Everything posted by Michel Kohanim

  1. 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
  2. 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
  3. 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
  4. 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
  5. Hi Gary, That should be fixed in 3.1.13 (refresh topology). With kind regards, Michel
  6. 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
  7. 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
  8. 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
  9. 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
  10. 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
  11. 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
  12. 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
  13. 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
  14. 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,
  15. 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
  16. Hi Tim, Our mail server is back up ... the main issue was that we had reached the limit and had to unblock the account for it to work again. With kind regards, Michel
  17. Hello all: Moshe, that's not normal. Please do submit a ticket so that we can log into your computer and see what's going on. idmills, we shall look into it. hagak, two cases: either you installed the module before upgrading to 3.1.12 or you need to clear your Java cache. polexian, can you verify that your UI version is 3.1.12 (Help | About). It's always best to use http://www.universal-devices.com/99i/3.1.12/admin.jnlp (after clearing your Java cache). automateme, can you explain what you mean by HomeSeer not working? How did it work before? Please note that you will have to re-export your lighting after you configure it again (you can now choose devices that have to be exported to ELK). With kind regards, Michel
  18. I do apologize ... it seems that we had a user with 1000s of emails going to gmail.coim (not gmail.com) and that caused us to reach the limit for this month. Please do be kind enough to use your own SMTP servers as much as possible. With kind regards, Michel
  19. Hello everyone, Please do be kind enough to use your own SMTP servers as much as possible. Our default mail server has reached the limit of emails for this month. I do apologize for the inconvenience. With kind regards, Michel
  20. Hello rgn2000, Please note that our default SMTP server might impose monthly limits. As such, it's best to use your own SMTP settings. If you have a gmail account, you can make sure POP/SMTP is enabled and then use the following settings: 1. Server = smtp.gmail.com 2. Port = 587 3. Userid = Your email address 4. Password = Your gmail password 5. Timeout = 1000 (or more) 6. TLS = Checked With kind regards, Michel
  21. Hello all, I am happy to announce the availability of 3.1.12 with support for ELK Module: viewtopic.php?f=25&t=7324 With kind regards, Michel
  22. Hello all, I am happy to announce the availability of 3.1.12 with support for ELK Module: viewtopic.php?f=25&t=7324 With kind regards, Michel
  23. Hello all, I am happy to announce the availability of our 3.1.12 release! For a list of changes, please take a look at this post. This is a major release: 1. Support for ELK Integration Module ($99.00 ... 40% off during Beta using coupon code elk-module-beta). Please note upgrade to 3.1.12 must be performed before installing the ELK Module 2. Reliability enhancements IMPORTANT 1. 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 2. 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. 3. 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 4. 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 Things to test: - ELK Module (if you have ELK) - Device Restore, Replace, and scene settings - Adjusting scenes within programs continuously - Network performance and status - Network resources and programs For a discussion of variables, please look at our Program Variables forum. Notes: 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. 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.12 - applet f. http://www.universal-devices.com/99i/3.1.12/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
  24. Are you still using the default mail server? If not, what is your SMTP server? Are you sure ISY can get to the Internet? With kind regards, Michel
  25. Hi Harold, If you cannot see ISY on the network then there are two cases: 1. ISY is configured with a static IP address ... factory reset should fix this BUT you need to make sure you hold the reset button for at least 30 seconds 2. If you see green blinking light on the network jack (on the back), then the unit is defective. If not, then check the connection from the Network Jack to your router With kind regards, Michel

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.