Michel Kohanim

Hi okane, I must resonate with what oberkc suggested: they cannot be completely unlit unless you completely turn off the back light for all of them. With kind regards, Michel

Hi Zick, This must be quite frustrating ... perhaps it's a good time to call our tech support so that we can help you get things back in order? With kind regards, Michel

Gentstr, Excellent question and I am so very glad you asked since you would've found out the hard way: yes, please factory reset your PLM before reusing it with ISY. Otherwise, the PLM is going to start writing links starting at the end of the previous high watermark. This could have cause quite a few unintended and unexplained side effects. With kind regards, Michel

Heatvent, Yes, as long as it conforms to the following: 5 to 30 volt DC 300 mA minimum Center positive With kind regards, Michel

Hi wwat, Yes, it is. But we are not using i2 commands to communicate with it because we have found it to be unreliable. For reference, there are three types of devices: i1 only ... most INSTEON devices i2 only ... motion sensors and triggerlinc i2 that supports i1 ... thermostat is in this category With kind regards, Michel

Hi C Martin, The issue is that you cannot add Motion Sensors using "remove existing links". You can, however, add them using "add existing links" if and only if you have already factory reset your Motion Sensor. This has been fixed in 2.7.11 and there are no enhancements. With kind regards, Michel

Hi gfridland, Would you be kind enough to test the following URLs: http://www.universal-devices.com/99i/2.7.10 and http://www.universal-devices.com/99i/2.7.10/admin.jnlp Thanks and with kind regards, Michel

Hi Ben, Global Cache makes IP to Serial bridges. If you get one of these and if you have the Network Module, then you can issue Serial commands to your devices through the network: http://www.universal-devices.com/mwiki/ ... _Resources With kind regards, Michel

hi gfridland, Yes and No! It all depends on the firmware version on your EZIO ... most of the older firmware version did in fact report their status back to the PLM. Some of the newer ones, do NOT. So, the short answer is: if you could get the input status without query in 2.7.7, then you should be able to get it again in 2.7.11. If not, then you will still have to query. With kind regards, Michel

Hi Mark, Thanks so very much. At this point, it would be best if we logged into your system to see what's going on. Please do be kind enough to send an email to support@universal-devices.com (ignore mail delivery errors if any) and we'll schedule a remote session. With kind regards, Michel

Hi to both! First let me answer oberkc's question: in the case of scene commands (not direct), ISY assumes that the devices responded unless there's a NACK from the PLM. In most cases, the PLM does not send a NACK. In case of direct commands, ISY ensures that the device responded otherwise you see Device Comm. Errors. Steve, from what I see, I have a theory: 1. When you SWL is On, it does not respond to Off neither from ISY nor from your CL. This tells me that there's something with that LOAD that is causing the SWL to not respond 2. Since we are dealing with scenes and if in fact your SWL is still v.35, then I am almost certain replacing it will solve all the problems (unless the load is causing noise). With kind regards, Michel

Hi Mark, I would have to agree with you that the likelihood of having to defective KPLs (and all of a sudden) is low. May I ask more questions? 1. Did you add these KPLs/linkages in 2.7.9? 2. When you upgraded to 2.7.10, did you remove them and add them back? 3. When you click on the write update to device, on Event Viewer (level 3), do you see INST-ACK followed by INST-SRX? OR, do you see 3 or more INST-ACK not followed by any INST-SRX? #3 is very important in helping us diagnose the problem. If you do not see any INST-SRXs, then it means that either the device is NOT responding OR that somehow the response is getting lost from the KPL to the PLM. In that case, have you recently moved your PLM? What's the load connected to the KPL? What happens if you retry with the load OFF? With kind regards, Michel

Hi Mark, I would have to agree with you that the likelihood of having to defective KPLs (and all of a sudden) is low. May I ask more questions? 1. Did you add these KPLs/linkages in 2.7.9? 2. When you upgraded to 2.7.10, did you remove them and add them back? 3. When you click on the write update to device, on Event Viewer (level 3), do you see INST-ACK followed by INST-SRX? OR, do you see 3 or more INST-ACK not followed by any INST-SRX? #3 is very important in helping us diagnose the problem. If you do not see any INST-SRXs, then it means that either the device is NOT responding OR that somehow the response is getting lost from the KPL to the PLM. In that case, have you recently moved your PLM? What's the load connected to the KPL? What happens if you retry with the load OFF? With kind regards, Michel

Hi Mike, My pleasure! Yes, all links are removed ONLY from the device being added. Once all the links have been removed, ISY creates the PLM links so that you can get status updates back from the devices. With kind regards, Michel

Hi gfridland, This is related to the bug we are investigating in 2.7.10. The frequency to query depends on how many times do these inputs change in the real world. I assume every 2 minutes would be find but, then again, since this bridges your security system, I would have to leave the exact duration to you. With kind regards, Michel

Hi RLIKWARTZ, If everything goes well (and it is), hopefully mid next week. With kind regards, Michel

Hi Mark, ISY does a logical delete on each link record on that device. Logical delete is to set the first byte to 22. All INSTEON devices allow setting the first byte to 22 regardless of what's next. As such, this is not going to pose any problem especially since the high watermark does not change UNLESS you do a restore from ISY. With kind regards, Michel

Hello robfitz, Actually it does and I can verify it here. The only thing that does not work is having a mutual exclusive relationship between the sub button and the load. i.e. when button C is on turn off the load. Furthermore, you can have on level/ramp rates for each sub button controlling its own load. With kind regards, Michel

Hi Mark, In 2.7.10, ISY indicates and stores where it left off (when it failed). As such, if you do not have any nodes with green 0101 icons, we have to assume that: a. ISY actually wrote all the data b. The device responded So, the next step would be to check the client. Can you tell me which URL you are using AND, if possible, can you clear your Java cache. There was indeed a bug in the GUI in releases prior to 2.7.7 and perhaps your computer is using an old version of the Admin Console. With kind regards, Michel

Hi endiablado, In some cases, if you bring existing links, ISY captures the links and creates scenes out of them. This becomes problematic when one of the devices has a slave link while the other does not. This situation does happen if you had linked your devices with HL or if you did a cross link without performing the other side. The solution is quite simple: 1. Create a dummy scene 2. Put the offending controller/responder in the scene 3. Remove the scene With kind regards, Michel

Hi, Thanks so very much. You can also use Tools | Diagnostics | Show Device Link Table and see the link records in each device. Devices that respond to controllers to which they are not linked have slave links in them pointing to the controller. Alternatively, you can create a dummy scene, put the offending controller and responder in that scene and then remove the scene. This should remove the offending links. At this point, my theory is this: 1. You have added controllers to ISY while the responders have not been added 2. The responders have links from prior installation and thus they are still responding. Once you add the responders using "remove existing links", I believe all will work With kind regards, Michel

Hi Mark, Do you see any green 0101 icons? If not, then it means that ISY has actually been able to successfully write to the device. If the device has not been programmed properly then I have to think it's the KPL itself. Just to make sure, would you be kind enough to do a restore on another KPL and then do a compare? With kind regards, Michel

Hi mike31360, I would also like to know which version of ISY firmware you have. With kind regards, Michel

Hi all, If the device itself has an serial interface, then you can use Global Caché in conjunction with the network module. With kind regards, Michel

Hi Chris, This issue is usually caused by your firewall software (on your computer) stopping your computer from uploading files into ISY. Please do check this forum for some remedies for most firewall software out there: http://forum.universal-devices.com/viewforum.php?f=3 With kind regards, Michel