Michel Kohanim

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

Hi stevehoyt, Flex Your Power is a program independent of the Smart Meters. It simply gives you an indication of when CA ISOs may need your help. 0 = in active and the control is the module = Flex Your Power. With kind regards, Michel

Hi tandar, First of all, thanks so very much for your vote of confidence. It actually means a lot to all of us at UDI. Would you be kind enough to try an address within the DHCP range of your router (at the higher end). Some rudimentary routers might just look at the number ... With kind regards, Michel

Hi Mark, Thanks so very much! It's good to cook dinner: it allows one to ponder about life in general and HA in particular! First of all, I am beginning to think that at least some of the problem is in 2.7.9. As far as having too many links, KPL (and most INSTEON devices except the ICON brand) should be able to handle 417 links. If you have 96 nodes only for one button, how many nodes do you think are linked to other buttons? Here's a rough estimate: 1. 8 links right of the bat for ISY to receive status updates 2. For each responder in a scene, one link 3. For each controller in a scene, two links If you are not going to add any motion sensors, may I humbly recommend upgrading to 2.7.10? With kind regards, Michel

Hi donkur, Please try the following: 1. Use https://your.isy.ip.address instead of http ... this might sometimes be able to trick some anti virus software 2. If 1 failed, please take a look at this post: http://forum.universal-devices.com/viewtopic.php?t=179 Hi gfridland, thanks so very much for the update. With kind regards, Michel

Hi tandar, Thanks so very much for the info. In most cases, the routers do NOT relay DNS requests for IP addresses that they have not issued themselves (using DHCP). I think this is the case with your situation. To rectify this issue, please use DHCP and then in your router, please reserve the IP address in the DHCP client table. This way, the router will never give your ISY a different IP address and it's happy that ISY is one of its DHCP clients. With kind regards, Michel

Hi rlav, Thanks so very much. We'll use this information for further investigation ... I do appreciate your patience. With kind regards, Michel

Hi gfridland, 1. The certificate issue is normal and please do reinstall a new certificate 2. The event log now shows what we are writing to what memory location. This is used to write information to memory locations that are NOT link database related 3. Can you elaborate a bit on local on level/ramp rate not written to certain devices? Please note that unlike KPLs, most other devices have to be rebooted before local on level/ramp rate setting can take effect With kind regards, Michel

Hi Mark, What's the firmware version on your ISY? Do you have missing links or record mismatch? Can you send me one example of a missing link and provide me with the address for both of your KPLs (old and new)? With kind regards, Michel

Hi Dave, I think I did answer the question but most probably not clearly. You see, unfortunately you can NOT put button A (or any KPL load button) in a mutually exclusive relationship with any other one of its buttons. I really wished I could help out here but this is completely outside of our control. With kind regards, Michel

Hi rlav, We are going to do more investigation on this issue. In the meantime, it would be great if you could go back to 2.7.7 and let me know if you still have the same issue. hart2hart, Thanks so very much for bringing this up. It's being investigated and shall be fixed shortly. With kind regards, Michel

Hi tummalarb, Please checkout this article in our Wiki: http://www.universal-devices.com/mwiki/ ... N:Schedule With kind regards, Michel