Michel Kohanim

Hello cmccartney, Comments below. I do not see any reference as to how we can poll the averages from the Display. And, even if we did, all these queries (which are probably every second) do cause major network performance issues. I think it would be best for ISY to include these functions using the readings from iMeter directly rather than getting them from the display. We'll look into it. With kind regards, Michel

Hi Teken, You can send Beep commands to devices that support Beep. In the Action section, choose Beep (in the same list as on/off/1% ... ). Above and beyond that, we do not know how to configure the KPL to be a Chime! With kind regards, Michel

Hello Elecrick, In addition to Lee's questions, my questions is: what firewall software do you use? Is it possible that you had put exclusion rules for your ISY26 but now ISY99 has a new IP and thus not excluded from your firewall rules? With kind regards, Michel

Hi Guys, We spent a couple of days on Energy Display and realized that there's really not much we can do with it: 1. To get temperature, it has to be polled 2. You can only link it to an iMeter but the problem is that the linking in this case does not follow regular INSTEON linking 3. ISY supports iMeter Solo so readings from iMeter Solo can be done directly to iMeter Solo So, our main question to every one is: above and beyond temperature reading, what else did you have in mind as far as ISY support for this device? With kind regards, Michel

Hello williammanda, Unfortunately there are no videos. To answer your questions: 1. You can add/configure devices/scenes 2. You can add/modify programs 3. Programs are point/click (you do not have to write anything except perhaps comments for your programs) Our Wiki has extensive tutorials with pictures: http://www.universal-devices.com/mwiki/ ... w-To_Guide With kind regards, Michel

Hello srogala, Unrelated: it's best to restore your backup from 3.1.9 as there was a migration bug from 3.1.9 to 3.1.10 where some devices lost their scene settings. With kind regards, Michel

Hello keribi, Thanks for the update! The gray arrows should not cause any missed timer events. With kind regards, Michel

Hi LeeG, Thanks so very much. The main issue is that we are getting increasing number of reports with RL/RL2 (and some KPLs) not reporting their status using dual band PLM. We did send a detailed report to SmartHome describing the situation which seems to be corrupted PLM database (addresses are filled with 00s). With kind regards, Michel

polexian, Comments in variables we'll take into consideration. elk-arm-state variable changes based on area/zone status. What are you trying to accomplish? Elvis, Thank you. Most of the errors are documentation errors which have been fixed. If you wish, you can send an email to me to tech@universal-devices.com and I can send you the latest doc (which will be including in 3.1.14). All events and objects are defined in /web/elkobjs.xsd (Schema file). With kind regards, Michel

RickL66, Sorry to disappoint but no. With kind regards, Michel

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