Michel Kohanim

Hello, Yes, that should have the same effect. With kind regards, Michel

Hi Sean, We were hoping that it would be included in 2.7.7 but it didn't make it. It should be available in the next release. With kind regards, Michel

Hi lloverin, Two cases: 1. ISY cannot communicate with the KPL or defective KPL 2. ISY cannot communicate with the responder or defective responder What I recommend is this: Try querying each device and see if you get any comm errors. If not, then it would be best to factory reset your KPL and then do a Restore Device on it (right mouse click on the node). If that works, do the same for the responder. If anyone fails, then I suspect first comm errors and second defective device. With kind regards, Michel

Hi brklaas1, The main question for me would be why is this switch turning itself off. Is it possible that this switch was programmed before as a responder to some other INSTEON device? May I humbly recommend the following: 1. Please remove the switch from ISY 2. Do a factory reset on it 3. Add it back to ISY Please let me know if this fixes the issue. With kind regards, Michel

Hi, I do very much apologize for the inconvenience. The link provided is for purchasing modules. Since we have migrated our store front to a new server, the links through the Admin console do not work. As such, if you would like to purchase modules, you will need firmware 2.7.7 which is due out over the weekend. Again, sincere apologies for the inconvenience. With kind regards, Michel

Hi GerryFr, This is not the intended nor designed behavior. I do not want to ask you to upgrade to 2.7.6 since it's still beta (although very stable). It would really be best to talk to have our tech support take a look at your system to ascertain where the problem is. With kind regards, Michel

Hi kcrossly, It's always best to take advantage of INSTEON protocol where possible. As such, my recommendation is to use a scene. With kind regards, Michel Yep, that's the problem. I spoke with SimpleHomeNet tech support and they confirmed that the device needs to be added as a controller. Once 2.7.7 is out is it better to setup this device as a Scene or a Program?

Hi GerryFr, Run then should run regardless of the condition. If you have 2.7.0, that might explain the issue but it would be best if you called our tech support so that we can ensure there's no bug. With kind regards, Michel

Hi Mark, You do not have to pick the type; just use Auto Discover (from the list). Unfortunately the addresses MUST be entered correctly otherwise, ISY is going to look for a device that does not exist and that might take up to 1 minute. With kind regards, Michel

Hi GerryFr, I specifically need to know if you get to the Admin Console via http://192.168.020 or via http://www.universal-devices.com/99i ? With kind regards, Michel

Hi aLf, Hopefully you still have the serial cable that came with your ISY. The only way to factory reset the 26 is to use Hyperterminal and connect to your ISY using a serial port on your computer (http://www.universal-devices.com/mwiki/ ... erial_Port). Once connected, and logged in: 1. To make your ISY have a dynamic address, issue CT followed by 0.0.0.0 for the IP address 2. To factory reset your ISY, issue FR With kind regards, Michel

Hi GerryFr, This is quite odd. No, there are no setup options. Can you tell me what's your ISY's firmware version and what URL you use to access your ISY? With kind regards, Michel

GerryFr, I am assuming that you see some X10 traffic sent out from ISY when the programs run normally? If not, you might have a defective PLM. Let's go through the steps: 1. Program Summary 2. Click on the row wherein your desired program is listed (highlight the row) 3. Click on the dropdown list and chose Run Then 4. Click on Apply If this does not work, please do contact our tech support team so that we can figure out what's causing the issue. With kind regards, Michel

Nick and Kelly, Found the issue ... it was a bug in the GUI which is fixed and should be available shortly (in 2.7.7). This is the one relating to the node being added as a responder. As far as linking this device, the only thing I can tell you is that it worked perfectly when we added support for it almost 1.5 years ago. I am not sure how it works with the current EZSnSRF firmware. With kind regards, Michel

Hi Kelly, Thanks. Go to http://your.isy.ip.address/rest/nodes, look for the EZSnSRF device and copy and paste the value between . Thanks and with kind regards, Michel

Hello again, Thanks for the update. The only time you will get an indication on the Admin Console is when Run Then is in a loop and thus its continually executing. Otherwise, Run Then will be executed so quickly that you might only see the status change for a fraction of a second. Now, as far as this program not sending X10, please do try the Event Viewer to see if ISY actually sends the commands. This will be quite helpful in debugging. With kind regards, Michel

Hi guys, I just checked the code and ISY should consider EZSnSRF as a controller UNLESS (and I won't doubt it for a second) EZSnSRF now has a different dev cat and sub cat. If any of you can send me your dev cat/sub cats then I can update the code. With kind regards, Michel

Hi Kelly, Yes, we are fully aware! It's got to do with the same migration that removed all our credentials from the update site! It should be back and up and running by Monday. With kind regards, Michel

Hi tbe, Unfortunately we are not in the middle of getting 2.7.7 alpha out and this would have to wait. But, it would be great if you could send me an email so that I can contact you directly once we have this feature ready for you to test (support@universal-devices.com). With kind regards, Michel

Hi kcrossley, First of all, my pleasure! Now, if EZSnSRF is automatically added as a responder then this is surely a bug. Are you sure that node is not already a controller for some other scene? With kind regards, Michel

Hello GerryFr, It's very difficult to troubleshoot based on your descriptions. Here are my recommendations: 1. Open Tools | Diagnostics | Event Viewer (level 3) 2. Go to Program Summary, click on the program you are testing, then click on Run Then and then Apply 3. Make sure you checkout the traffic on the Event Viewer If you ISY is actually sending the X10 commands, then the problem is that the signal is somehow getting lost and does not get to your X10 device. Or, if you wish, you can Copy to Clipboard your program and then paste it here. This way, we'll be better able to troubleshoot. With kind regards, Michel

Hello Joel, Thanks so very much for the update. Yes, Kaspersky is usually the culprit ... but most of the time it only impacts file upload. I have never seen it block status updates/events. With kind regards, Michel

Hi Mark, Do you know what PowerHome expects? i.e. is it looking for binary data or ASCII? Does it require you to do a POST or a GET? If you can get Dave to let us know what is expected, then we can help you come up with the parameters. With kind regards, Michel

Unfortunately, there's no way of knowing that from the INSTEON APIs (we do not even know what type of thermostat it is). With kind regards, Michel

rlebel, I think we have to be more clear in our communications: you are referring to Programs in which case it has been fixed in 2.7.7. With kind regards, Michel