Michel Kohanim

Hi LeeG, I must agree with you (as always). It seems that the master links were missing in the PLM and thus no status updates. Thanks so very much and with kind regards, Michel

Hello jtara92101, There's definitely something very wrong either with the KPLs or the PLM (I think it's the latter). All links should be written when you add a KPL to ISY so that you would get status updates. If not - and if you do not have 0101 green icon next to it - then there's something very wrong. With kind regards, Michel

Hello jtara92101, Do you seen any traffic in the event viewer (on level 3) when you click any of those buttons? With kind regards, Michel

Hello jtara92101 I totally concur! Would you be kind enough to post this post in our SmartHome Channel ( http://forum.universal-devices.com/viewforum.php?f=30 ). SmartHome reps are quite responsive on that forum and I am sure they would respond with technical details. Thanks and with kind regards, Michel

Hello thruster999, 1. Add to ISY the new device which is going to replace the old device 2. Right mouse click on the old device and then from the Replace with ... menu item choose the device you added in #1 With kind regards, Michel

Hello jtara92101, The first thing I would do is to make sure your PLM has not reached its capacity. Please do the following: 1. Tools | Diagnostics | PLM Status/Info .. please let me know what you see 2. Tools | Diagnostics | Show PLM Links Table and when complete click on the count button In short, for you to get status updates back from the KPLs, there must exist a slave link in the PLM for that specific KPL+Button combination. I think for some reason either these records are missing or are not being created. With kind regards, Michel

Hello rlebel, Long time no see! I cannot comment on the flickers but I can tell you that ISY does support replacing a 2476D with a 2477D. With kind regards, Michel

Hello someguy, In addition to the great suggestion from Tom, please also check and see if you can send any notifications. The problem might be that your router is not letting ISY to resolve domain names. If that's the case, then we have to figure out what network configuration you are using and why would it cause the problem. With kind regards, Michel

Hello pespisjm, Please go to Tools | Diagnostics | PLM Status/Info and make sure the PLM is connected. Also, is the device trying to add RF and, if so, is it close to an Access Point? With kind regards, Michel

Hi Traditore, You are correct ... I had completley forgotten about the limitations of IRLinc TX. I think you are on the right path and your programs seem solid. With kind regards, Michel

Hi Traditore, Is there a reason you do not have the KPL button as a controller in the scene itself (instead of using programs)? With kind regards, Michel

Hi JP, Thanks so very much for the update. I can tell you from experience that SWL v35s do in fact contribute A LOT to instability in INSTEON network. The first thing I would do is replace those and then we can address other issues as they arise. With kind regards, Michel

Hello johnnyt, Just one comment: on 64 bit Windows machines, you need to install both the 32 bit and 64 bit versions of Java. With kind regards, Michel

Hi JP, From experience I can tell you that there are basically just a very very small fraction of situations wherein signal issues cannot be solved. Do you know or have any feelings as far as where the source of line quality issues are? The point is that if you have line qualitiy issues, perhaps the signals do not even get to the AP to be sent out. With kind regards, Michel

Hello johnnyt, Did you send your backup to support@universal-devices.com? If so, we have not received it. With kind regards, Michel

Hello kaplansa, The fact that you could not add the devices using Start Linking tells me that there is surely a signal issue from the PLM to these switches. You see, Start Linking uses the lowest amount of power to ensure that subsequent communications will always succeed. If that failed, I am almost certain that this is the reason why you see all those 0101 icons since ISY cannot reliably communicate with your KPLs. My suggestion is, if possible, try one of the KPLs next to the PLM and see if that solves the problem. If it does, then we might have to think about either noise or phase bridging. Do you already bridge your phases with Access Points? With kind regards, Michel

Hello JP, Thanks ... I am quite baffled too. This does not make sense at all. I am not sure what else I can suggest except for swapping the APs and see if the problem moves with the AP. With kind regards, Michel

Hi Mack, You are correct! With kind regards, Michel

Hi Illusion, Ghost is probably the culprit here Now, we just have to figure out if the ghost is in your house or in the unit. And, no, I have never heard anyone complain about this issue. Hopefully, others viewing this topic can chime in if they have experienced something similar. I am pondering if the new PLM has anything to do with it. With kind regards, Michel

Hi Illusion, Thanks so very much. Unless this is a bug somewhere, control should never be activated unless someone or something actually turns the device on. Would you please keep an eye and let us know if you encounter the same problem again. In the meantime, the same program with the same switch and the same PLM is setup and is monitored as well. Wtih kind regards, Michel

Hello JP, In some cases, too many APs (especially when used in smaller venues) cause more harm than good. If you know how many phases you have, the best thing to do would be to bridge the phases right at the breaker (using APs) and then use APs only when you wish to extend the RF range for RF devices. As it is right now, it seems that you are using the APs for both extending the RF range as well as bridging the phases. Correct? With kind regards, Michel

Is your 2.8.4 one that you just downloaded and installed yesterday? Please note that Java cache does NOT get cleared if you have any browsers open or if you have any Java applications running. With kind regards, Michel

Hi Illusion, Thank you. I am a little confused: how do you know the this program was run because of your 2476D? 2476D comprises only two of the conditions. How about all the other conditions? In short, how did you arrive at the conclusion that the problem was the 2476D in the bathroom? With kind regards, Michel

Hi Mike, I am so very glad that you got everything working. The reason you have two nodes is the way they should behave when responders in a scene. For instance, if you put the off in a scene, on commands can unlock and vice versa. If you are not going to use them in any scenes, then they are identical. With kind regards, Michel

Hi Illusion, Indeed quite odd! May I ask the type of device and the firmware version? With kind regards, Michel