Michel Kohanim

Hi Wayne, are you saying that you get a Request Failed as soon as you get the Admin Console? Do you have Network Magic software installed on any computer on your network? With kind regards, Michel

Hello Walter, No because we realized it was not a bug. This is what happens: With i2, RL takes a little longer to program (sometimes more than 4 minutes) and thus your RL goes out of programming mode. What you need to do is either use i1 Only mode OR: sit next to your RL and after about 4 minutes, put your RL back into programming mode (the LED will stop blinking and you will not see any traffic). We have also noticed that with battery operated devices, battery charge level has a TREMENDOUS impact on how quickly i2 messages are processed. So, you might want to make sure you have a good battery. With kind regards, Michel

It should be couple of months because we need it for our own configurable web modules (you can reconfigure ISY's GUI). With kind regards, Michel

Hello Vortec4800, Yes, REST would be much easier to handle and it's something we are actively working on. It's surely much simpler than doing heavy web services calls. With kind regards, Michel

Hello Vortec4800, We do have a free Web Services library which you are welcome to use (simply send an email to support@universal-devices.com with your request). But, I think you are talking about a REST approach where everything is URL based. If so, we are working on it as it would make things much easier for smaller projects. With kind regards, Michel

Hi Bob, Please do be kind enough to check the On Level for this switch. Please make sure to airgap the switch if you make any changes. As far as NTP not working, please check the logs and look for -6000x error. If you find one, then ISY is having a hard time resolving pool.ntp.org to an IP address. With kind regards, Michel

Hello someguy, I cannot reproduce this issue here and I have 3 Motion Sensors. Would you be kind enough doing a Restore Device on your motion sensor? Also, when you click the set button manually, does the status change? With kind regards, Michel

Hello okane, Two possibilities: 1. You chose the 3rd option which brought along existing links 2. Some of your devices are i2 which previous versions did not support In both cases, please download the latest (2.6.13) and then do File->Restore Devices which, in effect, will remove all your links that are not recognized by ISY. With kind regards, Michel

Hi Bob, Motion sensors are NOT queryable because you will have to put them in Programming mode before you can communicate with them. This is actually a bug that we fixed! With kind regards, Michel I'm seeing the same thing. ISY-26, PLM v52. I upgraded from 2.6.12 directly. All three of the motion sensor devices show up with blank status and if I try to query any one of them, I get nothing. No messages in the log (set at level 2). I tried changing the advanced options to "Device Reported" and did a query of My Lighting and again, no entries in the log for the motion sensor. I'm also seeing the same behavior for the EZRain zones. All my other devices are queried just fine.

Hello Gary, Would you be kind enough to try http://www.universal-devices.com/99i . If this works, then please download again and reinstall. Hi Burak, I tested the motion sensor again and it works fine. Perhaps there's no motion??? Thanks so very much, With kind regards, Michel

Hi Burakk, Apologies for a VERY tardy reply; I must have missed your post. Your assumption is correct but that's not our experience. The values should not be sporadic: ISY works based on change only. So, by the virtue of having the program check the status of last run time of another program, you are effectively saying that you don't care about what happens within an hour. May I humbly suggest the following: 1. Remove the time constraint (since last time) 2. Change the condition to include a range (for instance, due point between 82 and 87) Please let me know. With kind regards, Michel

Hello wrj0, It might be something that treo itself is blocking. Perhaps it's using it for SNPP (default port is 444). Would you mind trying a different port such as 8443 or 40443? With kind regards, Michel

Hello wrj0, Apologies for a tardy reply. Yes, indeed a bug the root cause of which is that we did not create a one to one mapping between the unit type entries. This shall be fixed. Thanks so very much, With kind regards, Michel

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

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

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

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

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

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

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

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

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.

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

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

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