Michel Kohanim

Hi dss, Thanks so very much for the update. With kind regards, Michel

Hi markens, There are two explanations: 1. The NTP server returned a bogus time 2. The RTC is going bad Please do keep an eye and let us know if it happens again. With kind regards, Michel

Hello Mr. Aldridge, E is for energy ... simply add a price under the electricity tab. With kind regards, Michel Hi Michel, What about /CONF/E? I see this also in my log? Thanks, Ruben

Hi Joe, Apologies for a tardy reply. I think the best thing to do would be to simply add your new KPL to ISY ( do not replace ), try the Mutex buttons on the new KPL and let me know if it works. If it does, then the problem is isolated to either that firmware version of KPL or that specific KPL. With kind regards, Michel

Hi grog, I totally agree. We are experimenting with a few client side rich UI browser agnostic technologies. We just have to settle on the minimum features that we want supported and the mobile phones we want to support. With kind regards, Michel

Hi again, So, is it true that both 2Ds have the same issue and the 00 does not? I just need to isolate the problem and make sure it's not device firmware related vs. ISY related. Thanks so very much for your patience and input. With kind regards, Michel

Hi grog, I love bold and hate my own storm ... The reason I asked the question was because we were thinking (and still thinking) of beautifying the HTML interface. With kind regards, Michel

Ah, I am so very sorry! Those are configuration files for Open Auto DR and Flex Your Power (under Electricity tab). Since you have not configured them, it's just a warning that the modules could not be initialized. So very sorry for the wrong answer! With kind regards, Michel

Hi Joe, I thought you mentioned they were 2C (the description in ISY). So, do you have both 2Cs and 2Ds? If so, are both exhibiting the same problem? With kind regards, Michel

Hi dss, I am certain you can do as the manual outlines as long as you consider ISY the responder. So, if you follow the instructions for non-toggle on the CC while linking it to ISY, it should work. There's just no programmatic way (like KPLs) that we can accomplish the same feat. Please keep me posted. With kind regards, Michel Smarthome doesn't provide this information to their developers? Seems odd. What if it is done manually using the method outlined in the manual and then added to the ISY? Or if I purchased one with the remote and then added it to the ISY would it retain the toggle functionality? For making a theater scene with my Harmony remote to turn the lights off when the movie starts you need a non-toggle off button.

Hi Rich, I am getting a little confused as well! I do not think you would need the "is not off" condition at all. In short, the program continues to run till the status changes from on to something else. You would need the "is not off" if you used control since a control does not have a status. But, since you are using status, the condition is evaluated based on the status of the device. With kind regards, Michel

Hi again, I guess it's time for us to get a 2C KPL and test. As I mentioned before, I cannot reproduce this problem here. Are all your KPLs version 2C? With kind regards, Michel

Hi, I really think there's something else in play here. But, yes, you can factory reset and restore: 1. To factory reset your KPL, take the set button out, leave out for 10 seconds and then push it back in and hold it in for 10 seconds 2. Right mouse click on any of the buttons for the KPL and choose Restore Device With kind regards, Michel

Hi grog, Yes, you are 100% correct and that's indeed in the list of requirements to accomplish. May I ask what PDA you use? With kind regards, Michel

Hi Jim, I think they are related removed devices which were removed but the associated configuration files were not removed. Quick questions before applying the procedure to fix: 1. Do you have any of your scene which cannot be programmed (on level/ramp rate)? 2. Do you have any of your devices which are not operating properly and/or are missing? If the answer to both of these questions is NO, then please: 1. Telnet to your ISY 2. Login 3. Issue FN (Fix Nodes) With kind regards, Michel

Hi dss, You can add them just like KPL buttons but the main issue is that they will all be toggled. As of right now, we do not know how we can change that function: it's a memory location which needs to be programmed for each button and we do not have the specs for it. With kind regards, Michel

Hello mozman, ISY goes into SAFE mode if it cannot communicate with your PLM and thus you will have all those socket errors if you have a faulty PLM. Please also note that on some firewall software (McAfee and Avast), disabling them does NOT help since they still have resident programs that filter out the packets. We'll be able to figure out these problems tomorrow and hopefully from then on you'll have a more enjoyable experience with your unit. With kind regards, Michel

Hello Tim and jkraus, I just checked two of my KPLs (neither of which are 2C; they are 29 and 31), and the both work fine: A and C in 8 button configuration Load and C in 6 button configuration A and C in 6 button configuration So, I assume the load button is the issue in both cases, right? With kind regards, Michel

Hi again, NO. With kind regards, Michel

Hi jkraus, Two questions: 1. Are these buttons in any other scenes as responders? 2. Are these buttons used in any programs? Would you be kind enough to try and restore the device and report the results? Thanks and with kind regards, Michel

Hi dss, Unfortunately not ... there's nothing in the documentation that tells us where this information is stored. Could it be done while linking to ISY? With kind regards, Michel

Hi Frank, For your 26, please do make sure you actually have 2.7.0 installed. For best performance and most stable system + motion sensor and IOLinc, please move to 2.7.6. With kind regards, Michel

mozman, I do apologize for the inconvenience. What you are experiencing is not normal and it should not happen. Before spending too much time on it, please give our tech support a call or contact us so that we can figure out what's causing all these issues. SocketTimeout happens in the following cases: 1. Your PLM is defective and ISY is in the Safe Mode ... this explains why you have these problems more often when you are linking 2. You are on a wireless network with not so good of signal reception 3. Internet Connection Sharing on Windows 4. Firewall ... especially McAfee, Zone Alarm and Avast 5. Defective unit With kind regards, Michel With kind regards,

Hi matapan, Good question! All events go to a queue and are processed sequentially in the order they are received. So, the best thing would be to break up any OR conditions into new programs, check for exception, and stop those offending programs in the face of exceptions. In the case of ANDed conditions, I do not think you will have any problems since as soon as one of the conditions is false, the whole program stops. With kind regards, Michel

Hi Rich, The first question I have is: do you really want ISY to send you en email every 2.5 minutes as long as the door is open? Have you checked the event viewer to see if you actually get DOF when the door is closed? Please note that Control and Status are too different things. ISY status for a device is NOT equal to whether or not a control was issued. I think, in this case, you might want to use Status instead of control. With kind regards, Michel