Michel Kohanim

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

Hi rlebel, I just verified that both setpoints only show when in Auto mode. If it takes 2 minutes to communicate with your thermostats, then there's surely a communications problem. Is it possible to move your thermostat closer to your PLM and retest? Or, perhaps move the Access Point closer to the thermostat? With kind regards, Michel Yes, that is correct. On the PC I see both setpoints. In our other thread you suggest that I should not see both setpoints unless the thermostat is in Auto mode, so perhaps the Mac GUI is "more correct" by that model, however I believe that model is wrong and (if allowed by the thermostat) you should always show both setpoints, on the Mac as you do on the PC. Even on the PC I have seen some odd behavior, which might be do to mode changes. I also see on the PC a VERY long interaction between the ISY and the thermostat (about two minutes). Perhaps we should schedule a session.

Hello rlebel, Thanks so very much for letting us get to your system. Indeed this was a bug which is already fixed and included in 2.7.7. Thanks again and with kind regards, Michel

Hi Mark, Two things: 1. If you have not already upgraded to 2.7.6, please do so (http://forum.universal-devices.com/viewtopic.php?t=3007 ) 2. Within that scene, click on the A button, view the On Level for the load button and make sure it's not at 0. If it is, then change it to your desired level With kind regards, Michel

rlebel, So the strange behavior of one setpoint showing up only is only on MAC? With kind regards, Michel

rlebel, Two setpoints will only appear if and only if you are in Auto Mode. If you are in cool mode, you will get the Cool setpoint; in heat mode, you will get Heat setpoint. With kind regards, Michel I am not sure why anyone would care, but in 2.7.6 on both my Mac and PC I only get one setpoint to compare, not separate heat and cool setpoints.

Hi rlebel, Thanks so very much for the update. I am very curious to see what other scenes/programs control those buttons. In no way should ISY be out of synch with the status of the devices unless it does not HEAR them. With kind regards, Michel

Hi rlebel, I do think it would be best for us to login to your computer (or access your ISY remotely) to see where the problem is. You can either call us to schedule an appointment or submit a ticket: http://www.universal-devices.com/contact.htm . I am so very sorry for the problems you've been having. With kind regards, Michel

Hi rlebel, This is extremely odd. Have you recently upgraded your ISY? Perhaps you should clear the Java cache and try it again. If all fails, please let me know the version as reported by ISY for your KPL. With kind regards, Michel Yes, I do mean the Action in the Then part, and my KPLs are properly recognized as 2486D units, but they don't have the 1-99% in the dropdown, just the 100% and 0%. My other dimmers do, however, have 0, 1, 2, ... 100% dropdowns. In a Scene I am allowed to set the KPLs on level, but not in the Action after Then. If it matters I am on a Mac.

rlebel, I assume that by Action you mean the Action in Then part of a program. So, if your KPL is IN FACT a dimmer and NOT a relay, then you should have all the on levels listed from 1% to 99%. If you are trying to set the ON LEVEL for your KPL so that it when you turn it on physically it turns on to that level, then you should use a scene. With kind regards, Michel

Hi rlebel, You can change the status of KPL buttons by putting them in scenes. Please use the Admin Console to turn off the Everything scene again and let me know if they still report as on. I suspect that something else turns them on OR that they are not responding to the scene. With kind regards, Michel

Hi Nick, Thanks so very much. That makes sense ... although a lot of programming but it might be worth it. Thanks again and with kind regards, Michel