Michel Kohanim

Hello keribi, I think the problem is those gray arrows: they mean that at some point ISY tried to program your RL, it failed, now there are pending updates for your RL which have failed at least once. What you need to do is: 1. Put your RL in programming mode 2. Right mouse click on one of the gray RL buttons in Admin Console and then choose Write updates to device With kind regards, Michel

Hello Rascot, I did reply to your support ticket. There seems to be an IP Conflict between your ISY and some other device on the network. If you have devices with static IP address, please do make sure they are not in the range of your router's DHCP. With kind regards, Michel

Hi Tim, What is the reported firmware version of your RL2? This has been reported by others as well. But, we just cannot reproduce it here. Please note that RL2 buttons might not match the UI .. so, please use the Event Viewer to see if there is any traffic when you do actual button presses. With kind regards, Michel

Hi Tim, Please do NOT use Device Reported. As far as 100ft, I think the safest length for an RJ45 is 50 so you might have some issues. With kind regards, Michel

Hi Tim, There's no easy way to count the programs. When you reach 300, it simply will not let you add more. Upgrade to Pro is as easy as Help | Purchase Modules followed by Help | Manage Modules (once the purchase is complete and you have received a confirmation email). With kind regards, Michel

Hi dss, The problem is that your ISY is not communicating with ELK. Please do ensure you review configuration documentation here: http://www.universal-devices.com/mwiki/ ... ity_Module Hi Elvis, There were some documentation issues with keypads and text which have already been fixed in the next release. 401 might be OK because when you start wget, it has to first send a request with no credentials and then fill in the credentials and send it again. /rest/security is NOT deprecated. It's still used when you do not have the ELK module. As far as other anomalies, I would sincerely appreciate it if you could be more specific with respect to the commands and the outcome. Hi Brian, Yes indeed! Thanks so very much .. it's fixed. With kind regards, Michel

Hi barclay, The most important point to consider is that Wait and Repeat constructs are interruptible. This means that if the condition turns false while the program is in Wait or Repeat, then the program stops execution at that point and does not go any further. The problem with your program is that Sunset + Grace period (Configuration | System tab) is less than the total amount of wait in your Then statement. As such, the program turns to false and stops prematurely. What you may want to do is to change your condition and instead use: If From Sunset To Sunset + 2 hours (same day) Then ... With kind regards, Michel

Hi Rick, Welcome back ... Network Module does not come with ISY. Please send us an email and we'll try to accommodate. Also, in 3.1.0 and above, we have made major networking performance improvements so please try the email/notifications first and see if they meet your requirements. With kind regards, Michel

Hello keribi, It seems that at one point in time the RL sent a NACK and thus the error. Please go to the Admin Console, look at the status of each button on your RL, and then turn those buttons on/off physically on the RL and see if their status changes. With kind regards, Michel

Hi Harold, Try this link in the Wiki. With kind regards, Michel

Hello all, Elvis 401 = Unauthorized so please make sure userid/password is OK. Now, ELK has it's own WSDK and REST interface the documentation for which you will find here. FRR, we'll get back to you shortly. tunaman, thanks so very much for the update. With kind regards, Michel

Hi Guys, Lee is correct: if you run the Event Viewer on Device Communications level, you will see those informational messages in the log. They should go away if a) you change the level you close Event Viewer or c) you close the Admin Console. With kind regards, Michel

Hello wharris, It seems that there are no links for the KPL in your PLM and that's why you are not getting any status updates. Would you please open Event Viewer and choose Device Communications level, then turn on/off your KPL physically and note any activity. If there are no activities, please try Right Mouse click on KPL | Restore Device and retry. If that does not work, then I would suspect you are way above the number of links supported by the PLM. If this works - and if feasible - do the same test on other devices that you have. If one or more are now not reporting the status, then again you have reached the maximum number of links supported by the PLM. In this case, you will need to try and combine some of your scenes to reduce the number of links. With kind regards, Michel

Hello ZinGasm, Sincere apologies. Please do be kind enough to send your shipping address to sales@universal-devices.com with subject Power Supply Adapter and we'll mail one to you immediately and free of charge. With kind regards, Michel

Hello mdcastle, would you please try https instead of http? Some firewall software would exclude https from the firewall rules. With kind regards, Michel

Hello Jorge, The problem could be two things: 1. You are pointed to the wrong URL ... this may happen if you have a proxy server in between 2. Data is not available for your chosen station Can you send your WB station ID to support@universal-devices.com? With kind regards, Michel

Hi IM/Lee, thanks so very much for the information ... it's fixed for the next release. Frank, Access code has to either be 4 or 6 digits otherwise ISY considers the code an invalid access code and won't even try to connect. If the access code 4 o 6 (quick syntax test), then ISY tries to connect ; making a connection has nothing to do with the Access Code. Connection merely means that ISY has established a network connection to M1XEP. Now, if the Access Code is wrong, the only thing you cannot do is arm/disarm. So, are you certain that you have the correct access code? With kind regards, Michel

Hi Mark, Can you send a sample device list with capabilities that we can use. This can speed up development. For instance: Device Type (i.e. relay), Device Subtype (i.e specific model), capabilities/properties (i.e. on/off). Furthermore, how can we extract device type/subtype from the unit itself? With kind regards, Michel

Hello IM, thanks so very much! You are correct ... the only time ISY considers itself disconnected from ELK is if it cannot communicate with it. As far as the ISY/Device links table, would you be kind enough to let me know the procedure you used? I tried all permutations and could not reproduce the problem. I used Node | Right Mouse Click | Diagnostics menu ... With kind regards, Michel

Hello tunaman, if you are available tomorrow (Sunday) please send an email to support@universal-devices.com and we'll try to accommodate a remote session. wuench/FRR, we are looking into this issue as we speak. With kind regards, Michel

Hi Jim, As long as ISY is set to DHCP, then changing ISP providers and even routers should be completely transparent. If you have setup a static IP address for ISY, then, before changing your router you have to make sure that you set it back to DHCP, change your router, then access ISY again and change it back to the static IP address of your own choosing. With kind regards, Michel

Hello richardl007, Unfortunately you cannot. You will have to use programs. With kind regards, Michel

Hello ooker, THANKS SO VERY MUCH! With kind regards, Michel

Hello ingeborgdot, If you are available tomorrow (Sunday) please send an email to support@universal-devices.com and we'll try to accommodate a remote session. With kind regards, Michel

Hello ooker, I think the problems are related. The fact that Programs tab takes a long time to load indicates that ISY is very busy running programs and thus cannot release the lock so that the Admin Console can load program config. The fact that your ELK is sluggish when ISY is connected indicates that ISY is trying to send it commands too frequently. What I suggest is: 1. Try to get to the Programs Summary tab 2. Look for all programs that are in the Running state 3. Right mouse click on each and then choose Stop ... this might take a while since ISY is busy --> for each program you stop, observe the performance of ELK; if ELK performance improves then that specific program is the cause With kind regards, Michel