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. Hello Steve, Then answer is NO. The problem is that time sensitive programs have to be re-evaluated at start-up explicitly. All this is due to the fact that most people did not want their schedules to run after each restart nor did they want ISY to catch up to schedules that were not run. So, what you have to do is: 1. For programs that are TIME only (like yours), please decide if you want to run them at start up ... you can do this in program summary 2. Please decide if you want ISY to catchup (run programs that may have been missed) ... you can do this in Configuration Tab under System 3. And, finally, what grace period ... you can do this in Configuration Tab under System With kind regards, Michel
  2. Hello Mr. Zulich, Apologies for a tardy reply. What version of ISY do you have? In your firewall, are you sure you have not blocked UPnP Framework? With kind regards, Michel
  3. Hello AnthemAVM, Yes, it should work. Or, better yet, it used to work. I think RL and EZIO have the same problem that ISY and EZIO devices have (recently due to the changes in the PLM). With kind regards, Michel
  4. Hello digitaltrader, Yes, you can change ISY's HTTP and HTTPS ports. Please: 1. telnet to your ISY: http://www.universal-devices.com/mwiki/ ... o_Your_ISY 2. login and issue CWP With kind regards, Michel
  5. Hello johnradams, Apologies for a tardy reply. The errors you see in the console (connection aborted by host machine) means that "your" computer aborted the connection. This happens 99% of the time because of a firewall or anitvirus software. The other 1% might be due to a switch between your ISY and your computer. If you wish, we can try the upgrade remotely (if you have remote access enabled). If so, please send your URL to support@universal-devices.com and we'll take a look at it. With kind regards, Michel
  6. Hello all, Apologies for not responding to the posts last night + not releasing 2.6.13 on time. Had to make sure we have covered all bases. I do think that this release will be able to handle more devices but I am also sure that there are many undocumented SH features/bug that will pop up. Hopefully ISY can handle them gracefully. Please do test i1/i2 functionality like adding devices, adding scenes, moving back and forth between scenes, and changing scene attributes. Also, it would be great to read database links. Thanks again for your patience, With kind regards, Michel
  7. Hello all, Apologies for not responding to the posts last night. We were getting 13 out which does a few nice things: 1. On boot up, it will flag all the nodes to be re-evaluated for their i1/i2 compatibility 2. Using Link Management->Advanced Options, you can choose a. Automatic (default): if i1, then BAU. If not, then ISY tries an i2 command which all i2 devices MUST support (read the first record in the db). If it succeeds, then it will flag the node to use i2. If not, it flags for i1 b. Device Reported: ISY uses whatever the device asks for c. i1 Only: ISY uses i1 regardless of the device's engine version 3. Every time you go between Automatic and Device Reported, all nodes will be flagged for re-evaluation Here's the link: http://forum.universal-devices.com/viewtopic.php?t=2030 . With kind regards, Michel
  8. Hello all, Apologies for not responding to the posts last night. We were getting 13 out which does a few nice things: 1. On boot up, it will flag all the nodes to be re-evaluated for their i1/i2 compatibility 2. Using Link Management->Advanced Options, you can choose a. Automatic (default): if i1, then BAU. If not, then ISY tries an i2 command which all i2 devices MUST support (read the first record in the db). If it succeeds, then it will flag the node to use i2. If not, it flags for i1 b. Device Reported: ISY uses whatever the device asks for c. i1 Only: ISY uses i1 regardless of the device's engine version 3. Every time you go between Automatic and Device Reported, all nodes will be flagged for re-evaluation And, Gary, yes, the secret stuff has been fixed! With kind regards, Michel
  9. Release 2.6.13 beta is now available and may be downloaded immediately. For fixes and enhancements, please peruse our beta forum at http://forum.universal-devices.com/viewtopic.php?t=930. You may also post your comments/questions and issues relating to 2.6.13 to this forum. This release provides the following important features: 1. 99i Series Optional Modules (Help->Purchase Modules) --> Weather Module: allows you to add weather information in your programs --> Energy Meter Module: allows you to use Brultech Meter information in your programs --> Online Upgrade from 99i Series to 99i PRO Series 2. i2 Support --> Choose the messaging method between Automatic, Device Reported, and i1 Only Bugs None IMPORTANT 1. For those upgrading from release 2.6 --->Please note that releases 2.6.1 and above will use default HTTP/HTTPS ports of 80/443 respectively. As such, before upgrading Disable Internet Access --->You will have to upgrade to release 2.6.5 ( http://forum.universal-devices.com/viewtopic.php?t=1409 ) before upgrading to release 2.6.13 --->If you are upgrading from 2.6.1, please make sure you export all your programs and store them in a safe place 2. If you have used bookmarks, please update them accordingly. If you have problems finding ISY, try http://www.universal-devices.com/99i 3. As always, please take a backup of your ISY Due to massive [plumbing] changes in this release, please do be kind enough to thoroughly test i2 related issues such as not receiving status feedback from i2 devices. INSTRUCTIONS for ISY-26 - Userid = isy - Password = autoupdate -- Step 1 - This step is necessary if and only if you are upgrading from any release except 2.6.11 and above - Download the update from http://www.universal-devices.com/update ... nsteon.zip do not unzip - Login to Admin Console - Choose Help->Manually Upgrade My Lighting and choose the file you downloaded in the previous step -- Step 2 - Download the update from http://www.universal-devices.com/update ... nsteon.zip do not unzip - Login to Admin Console - Choose Help->Manually Upgrade My Lighting and choose the file you downloaded in the previous step INSTRUCTIONS for ISY 99i Series - Userid = isy - Password = autoupdate - Download the update from http://www.universal-devices.com/update ... nsteon.zip do not unzip - Login to Admin Console - Choose Help->Manually Upgrade My Lighting and choose the file you downloaded in the previous step - Important: After upgrading, please close Admin Console, close all web browser processes, clear your Java cache, and reopen Admin Console. If there are any web browser processes running, the Java cache will not be cleared.
  10. Hi someguy, Yes, it's easy: 1. Reboot with the older PLM 2. File->Restore Modem (PLM) mcrean, Please wait for 2.6.13 which allows you to force i1. To upgrade, reboot your ISY and follow the instructions for upgrading to 2.6.13. With kind regards, Michel
  11. Hello RF_Burns, I am so glad that it works now. But, now, I suspect noise issues that prevented it from being programmed originally. Please keep an eye on it for any abnormal (especially scene related) behavior. With kind regards, Michel
  12. Hi Brian, Thanks so very much. I just wished SH would let us know or, at the least, they would not ship wrong PLMs. We have had a 100% increase in support issues mostly because of HL2 issues. Thanks again and with kind regards, Michel
  13. Michel Kohanim replied to G W's topic in ISY994
    Hello wrj0, If this is indeed the case, then it's a bug. What you select in the configuration page should be applied to all entries in the program page (except for pressure which is mbar). I will have this looked at and will get back to you if we find a bug. In the meantime, if you change to Metric, all you have to do is to restart your Admin console to see the changes in the Program Details tab (all values will be converted automatically to the closest possible value). With kind regards, Michel
  14. Hi upstatemike, Would you also check the ISY Link Table for the device (this is what ISY thinks the device has). This has to be compared with Device Link Table for the same device. What we want to do is to make sure ISY and SWL both have the same view of the world. With kind regards, Michel
  15. Hello clark21236, The time server issue is not what bothers me. The problem was that your system was rebooted at 12:09 on 12/20: 0 null Sat 12/20/2008 12:09:24 AM System Start So, when ISY restarts and if you have not set ISY to run your program at startup, then your program will not run till the next time (perhaps next day) that it's scheduled. Now, my questions: 1. Did you have a power outage 2. Is that program enabled to be run at start up? With kind regards, Michel
  16. Hello Mr. Zulich, What operating system are you running? If Vista, please do make sure that you have Network Discovery on. If XP, then please make sure you see "Hide UPnP ..." on your left navigation bar. If you have communications problem with your devices, then I suspect noise. Is your PLM plugged into the same outlet as your computer, router, monitor, etc.? If so, you would want to put all those other devices on a FilterLinc. With kind regards, Michel
  17. Hi Michael, I think that's an excellent idea. Perhaps as part of your user profile ... unfortunately, that feature does not exist and we do not develop the forum software. As such, the best thing to do would be to bookmark them locally. With kind regards, Michel
  18. Hello RF_Burns, The first thing I suggest is to do a restore device (right mouse click on the SWL and click Restore Device) on your faulty SWL. There are also newer SWLs (600W versions only) which only work with i2 commands. So, perhaps, you would want to wait for 2.6.13 beta to see if that takes care of the problem. If not, then it's surely the switch. With kind regards, Michel
  19. Hi MV, As to_lighter suggested, you could use a program. Or, you can convert your 6 button to 8 button KPL: 1. Take the set button out 2. Press and hold the A and H buttons ( you have to have extra buttons ) 3. Press the set button in and hold it for 3 seconds When you do this, you will have to remove the KPL from ISY and re add it. With kind regards, Michel
  20. Hello MV, Unfortunately, you will have to remove and re-add it back. With kind regards, Michel
  21. Hello upstatemike, To get the link tables: 1. Click on Start 2. Choose the device from the list 3. Click on OK I am still very interested in the device link table and ISY link table for that device. If they are different, then ISY is not restoring it properly. If they are the same then the problem is either the PLM or the Switch. With kind regards, Michel
  22. Michel Kohanim replied to G W's topic in ISY994
    Hello wrj0, When you change the unit measure in the module configuration, you should see that reflected in the programs (you might have to restore your Admin Console depending on what your system caches). So, the short answer is yes. With kind regards, Michel
  23. Hi Tim, Thanks for the feedback. As far as motion sensors being undefined, the main problem is that the same category/sub category (identifying the device) is going to be used by another device. For us to manage the dev cat/sub cat changes means that we would have to maintain a list of all the changes (we went through this with KPL 8 button) which we are NOT always privy to. In any case, I do not recommending an upgrade till a complete and fully stable release. Hi Tom, You can always go back to release 2.6.8. To be 100% sure, you can also restore the backup you took in 2.6.8 and thus you'll be guaranteed to have the same behavior as you did in 2.6.8. Now, please make sure you are not using HL2 PLM for, if you do, NOTHING will work reliably. Hi someguy, I am not sure why that would be the case. Perhaps it's reporting as i2 but does not support i2 commands? With official 2.6.13 (tomorrow), you have the option of forcing ISY to treat everything as i1. Please test it and let me know if this works. With kind regards, Michel
  24. Hello, We have had many reports that the new HL2 PLM does not work with ISY. We do not know why this is the case but we are trying to figure it out. As such, getting a free HL2 upgrade is always a good idea but please do NOT use its PLM with ISY unless you are ready to spend hours troubleshooting communications issues. With kind regards, Michel
  25. Michel Kohanim replied to Dodger's topic in ISY994
    Hi Dodger, Please do NOT delete everything as the problem you are experiencing will not be solved by deleting. What you might want to do is: 1. Reboot ISY 2. Wait a couple of minutes 3. Click on View and Refresh on your Network Dialog I am assuming you have Windows Vista. 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.