Michel Kohanim

Hello arw01, I am not sure how GC would help you since it seems what you are looking for is an IR receiver which translates IR signals to ISY. I do not know of any such device (yet). With kind regards, Michel

Hi Scott, Please use method 2 and make sure: 1. Your Leak Sensor is in programming mode 2. Your Leak Sensor is in close range of the PLM or another dual band device With kind regards, Michel

Hi Ralph, Quite strange indeed. To recap: 1. Factory reset 2. Program button H to non-toggle-off 3. Add it to a scene (or any other type of programming) and then it goes back to non-toggle-on If this is accurate, can you tell me whether or not you have other buttons from the same KPL in the scene. We had reports (by johnnyt) of KPL v36 having button H corrupted as well. Just want to figure out whether or not there are any relationships: viewtopic.php?f=25&t=10662 With kind regards, Michel

Hi someguy, Thank you. Can we at least agree that you should NOT do another Restore PLM before contacting us? With kind regards, Michel

Hello pierre, We are still working on the updates to 3.3.10 user guide. If you look at the changes since 3.2.6, you'll note that they are mostly support for additional devices, bug fixes, and some cosmetic enchancements. We do not have a Ping function. With kind regards, Michel

Mr. Moore, Our development plan is mostly a function of demand and then ROI. We do not have that much demand for Zigbee door locks yet. With kind regards, Michel

Hello az1324, No, we only added group 4 (PLM is slave in the sensor and sensor is the master in the PLM). And, we have never had to add group 255 and thus it's something I am not comfortable doing without analysis. Confusion is going to be there regardless; I am confused myself! With kind regards, Michel

Hi Ken, Please either upgrade your OS to 10.7 OR use the following link instead: http://isy.universal-devices.com/99i/3. ... min16.jnlp With kind regards, Michel

Hello db2ace2, THANKS SO VERY MUCH. This is excellent input and feedback and pretty much more than I expected. Your contribution will certainly help us figure out where those dates are coming from. At a high level, none of the conditions seem to be time based, so that might be a clue. Thanks again SO very much and with kind regards, Michel

Mr. Moore, No, we have not yet. This said, ZWave door locks should work. With kind regards, Michel

Hi John, Control is unlike status and it requires a lot of care to be used in conditional/event based logic. What you suggest will also include DIM/BRT/FAST ON/OFF and all other controls and that's not what the intent of your program is. With kind regards, Michel

Hello all, Please note that although we added support for it based on the developer's guide, we could not test anything except the test button. In short, we have never ever seen any of the commands (just like the Leak Sensor/Heartbeat). As such: 1. Please do keep us abreast of whatever you find 2. Do not assume that this works With kind regards, Michel

Hi Kate, How old is your unit? With kind regards, Michel

Hi Xathros, thank you. Hi LeeG, thanks so very much. I do agree with you and we have to keep consistent with the underlying protocol. With kind regards, Michel

Hi Kate, Risky referred to formatting your original SD Card. Apologies for the confusion. With kind regards, Michel

Hi Kate, Shortcut is a bug with Java 1.7 not being able to show .png icons. Workaround Courtesy of Xathros: 1) Open Java preferences and clear the cache (Including applications) 2) Connect to the website and download admin.jnlp: http://www.universal-devices.com/99i/admin.jnlp (Save this to the applications folder or desktop) 3) Double click the admin.jnlp from step 2 (inside applications folder). This will download the applet into Java cache, complain about not being able to create a shortcut, the run normally. Then, all you need to do is to create an alias in the application folder and put on your desktop or open directly from the applications folder. With kind regards, Michel

Hi LeeG, I totally agree with you. At the moment, making an automated link is going to be a little problematic. I think we should agree that the unit has to be removed and then added back. The only remaining question is: can we assume Wet = On and Dry = Off. Does anyone have any problems with this? With kind regards, Michel

Hi again, Yes, you may but it's quite risky. With kind regards, Michel

Hello again, I am so very sorry to hear. In the Adapter there's a little microSD Card. You are correct, ISY supports up to 16GB only. If you wish, you can send your mailing address to support@universal-devices.com and we'll send you one. With kind regards, Michel

Hello Kentinada, I am so very sorry to hear. Flashing red error light means file system error. If you have a new SD Card, please try the following: http://wiki.universal-devices.com/index ... an_SD_Card Please do NOT format your original SD Card since we might need it only because your last backup failed. If you are still having problems, please do let us know. With kind regards, Michel

Hello db2ace2, Indeed quite strange. Can you please copy to clipboard your program for which you had this issue and paste here? With kind regards, Michel

Hi someguy, This must be much more than frustrating; this is horrendous. Is it possible to plug your PLM to a different outlet? Also, do you mind sending me an email (support@universal-devices.com) so that I can forward to our reps at SmartHome. We will have to find the root cause and I am sure SmartHome would certainly want to know what's going on. With kind regards, Michel

Hi LeeG, Thanks so very much for the clarification. I think that's what we have already implemented. Based on the documentation: To address: 0x00 0x00 0x04 Mode: Broadcast cmd: 0x11 = dry; 0x13 = Wet param: 0x04 And, this is what we have in our code: if (cmd == LIGHT_ON_INSTEON_COMMAND) { if (param == 0x01 || param == 0x04) { //Dry Set Dry Node to 255 Set Wet Node to 0 } else if (param == 0x02) { //Wet Set Wet Node to 255 Set Dry Node to 0 } } else if (param == LIGHT_OFF_INSTEON_COMMAND) { if (param == 0x04) { //Wet Set Wet Node to 255 Set Dry Node to 0 } } [/code] In short, I think all we need to do is to add group 0x04 as responder in PLM & controller in Leak Sensor and everything else should work as is. The main question becomes support. At the moment - and even though we might not have room in 99 - I think having a heartbeat node would be much easier for users. But, at the same time - and unlike the Wet/Dry nodes, the heartbeat node has both states combined into one. A little bit convoluted. What do you think? With kind regards, Michel

Hi LeeG, Reviewing your comments since we have just started the surgery. I need more clarification on this statement: Thanks as always. With kind regards, Michel

Hi someguy, This is VERY abnormal and something we have never ever had reported before. How new is your PLM? What's the firmware version on it (Tools | Diagnostics | PLM Info/Status)? With kind regards, Michel