Michel Kohanim

Hello Illusion, We added code in ISY to ignore the duplicates sent by RF devices. Since I was not able to reproduce the same exact symptoms as you had outlined, I do think that this fix will most probably also address what you are experiencing. 2.7.1 should be out in a couple of days. With kind regards, Michel

Hi Ken, Thanks so very much. Based on what I see in the logs, I speculate the following (in the order of probability): 1. A corrupted database on your device ... please do a factory reset on it and retry the same case 2. noise ... if this device is attached to any load, remove the load. Other sources of noise are CFL, plasma, phone chargers, old computer monitors, etc. 3. Defective device With kind regards, Michel

Hello NewTech, I do recommend the following: 1. As others have suggested, I would certainly put a FilterLinc on the entertainment devices (TV, etc.) 2. If you have any access points, try moving them closer to the troubled switch (hopefully on the same phase) Please do keep us posted. With kind regards, Michel

gregoryx, Thanks so very much. I would sincerely appreciate it. With kind regards, Michel

Hello ncarney, Yes, this is true: 1. When you do a manual query, ISY clears all the previous states and thus, regardless of the change, you will get an event 2. When you do a program query, ISY does not clear the previous states for the device and thus you will only get an event for states that have actually changed from the last time With kind regards, Michel

Hello Ken, Yes, thanks so very much. This tells me that you have good communications and that the status should be correct. Now, what we have to figure out is why you get a failure message when you try to add this to a scene. Can you try adding this to a completely empty scene while keeping the event viewer on level 3? Thanks and with kind regards, Michel

Hello markhamk, I am so very sorry to hear this and I do apologize for the inconvenience. If ISY shows you not connected status for the PLM, then in all likelihood, you do have a defective PLM. Please note that receiving X10 messages is NOT equal to ISY having the ability to communicate with the PLM. I strongly suggest getting a replacement for your PLM. If you wish - and if you have an extra RJ45 cable - you might want to try switching the cable between ISY and the PLM. Again, I am so very sorry to hear about all the problems you've been having. With kind regards, Michel

Hello Joe, No, you can have multiple controllers per scene except for buttons from the "same" RLs and CLs (ControLincs). With kind regards, Michel

Hi Joe, Yes: 1. Each controller in a scene can have different on level/ramp rates for any of the other controller/responders in the same scene. This way, your Entrance and Exit buttons could have different effects while both controlling the same set of lights 2. The Scene itself could have different on level/ramp rates for all the members in the scene. These settings are used when you use the scene in a Program 3. If you want all of them to have the same effect, apply the changes to the scene first and then, for each controller, click on Copy Scene Attributes from .... With kind regards, Michel

Hi to_lighter, I do agree very much but, at the moment - and unfortunately so - the PLM gets out of synch with ISY commands and it's rather difficult to make them in synch. In any case, I do think that you have more than 800 links because all the symptoms point to the fact that the PLM does not forward the traffic to ISY. With kind regards, Michel

Hello tazal, I am so very sorry for a tardy reply ... for some reason I had not noticed your post. Thanks so very much for the feedback ... I shall have this added to our todo list but I must also let you know that it will have a very low priority. With kind regards, Michel

Hi aLf, it's not necessary if you do not use dim/brighten extensively. If you do, all you have to do is to: If Time is 3:00 AM Then Set Scene My Lighting Query With kind regards,

Hello guy, I think the best way for us to fix this would be to have a remote account on your system. Is this possible? This way, you can tell us about all the issues and we can solve them while logged into your system. With kind regards, Michel

Hi gregoryx, This seems to be bug. The main question is whether or not you get system busy even if you restart your browser? With kind regards, Michel

Hi David D, NO! You should have only one. Please remove the other one. With kind regards, Michel

Hi oberkc, Would you be kind enough to start Tools->Diagnostics->Event Viewer (Level 3), do a query on the device, save the log and paste it here? With kind regards, Michel

Hi gregoryx, Does this go away if you restart your browser? With kind regards, Michel

Hello guy, First of all, I do apologize for the inconvenience. Secondly, the Restore process actually completes regardless of errors. So, rest assured that ISY did its best to restore all your devices. 2.7.0 is an official release and NOT a work in progress. As far as Linux, we do test under Red Hat. We have never tested under Ubunto 64 bits nor do we have any plans for doing so. It's so very odd that Java behaves differently on different platforms. It's actually quite sad. With kind regards, Michel

Hi to_litgther, If you have 1700+ links, and if you have PLM v72, then I strongly recommend getting a replacement PLM. Also, I strongly recommend that you try and merge some of your scenes. 1700 is A LOT of links and I do not think you are going to have consistent behavior. Factory reset is not a problem if yours worked. With kind regards, Michel Thanks Rand, The link was very informative, thank you. I now feel better about the Scene Test results differing from what I was seeing with my own eyes. My link count on the PLM is 1748. I'm going to run it a few more times to see if it is consistent. Cheers!

NewTech, The first message is because the applet cannot find ISY. The second happens because of Java cache. I suspect you are not going to see the first one after you clear your Java cache: Close all your browser windows Control Panel->Java->Settings->Delete Files With kind regards, Michel

Hello to_lighter, Thanks so very much for the detailed response. And, so am I very interested in getting to the root cause of this since if it happens once, it wills surely happen again. To this end, I still need to understand what "corrupted" means: is it devices do NOT report their status? is that they do not respond to scenes? in short, what are the symptoms? As far as the PLM blinking but ISY not seeing traffic, this still does confirm the problem is a corrupted ISY simply because: 1. For each event received by the PLM, the PLM's LED blinks 2. For each event, the PLM has to go find a record for this device as a slave without which the event is NOT passed on to ISY. Now there are two cases: --- a. If your PLM has more than 400 links, then - in some cases - the PLM will NOT be able to find the record and ISY will not get the notification. This will require a PLM replacement --- b. The record is NOT in your PLM in which case the problem might either be the PLM (got corrupted) or when you restored all your devices, then some devices did not get programmed properly into the PLM I strongly believe the problem is the PLM (with more links than 400) and even more so because removing the device and adding it back in helps. The reason is that when you remove a device from ISY, you are also removing it from all the scenes it belongs to ... so, in short, you will be FREEING n number of links in the PLM. I bet you if you start adding the device to multiple scenes, you will start having the same issues either with the same switch or with some others. If I know more of the symptoms of the "corruption" you refer to, then I'll be better able to help out with the diagnosis. With kind regards, Michel Hi Michel, Thanks for responding. "Impossibly corrupted" means that my perfectly functional system became largely corrupted after unplugging my PLM. I am currently working on restoring functionality to one switch before moving on ... I have a strong interest in making sure that the ISY/Insteon combo works well together, so I hope we can figure out what has happened, and why many of my switches are no longer recognized by the ISY. However, my detective work so far has demonstrated that the problematic switches do generate LED activity at the PLM, but not in the activity log of the ISY. Removing the first problematic switch from the ISY and then reinstalling it has resolved all of the communication problems. I think this is sufficient to rule out electrical noise as the issue, and so I think the future focus should not be upon FilterLinks, especially given that I have a bunch of them in place, and none of them changed at the time of the fatal unplugging of the PLM. Somehow, a simple unplug and replug of the PLM has made my ISY99i unable to respond to a large number of my devices. Worst comes to worst, I guess I will remove them and reinstall them one-by-one, a process akin to starting again from scratch. Given the very large number of switches that I have, I certainly hope that this will not be necessary every time the PLM loses power. As per your suggestion, I have started with a switch that participates in multiple scenes and programs. Once I get that switch working reliably, I will move on to other problematic switches. Thanks

Hello to_lighter, Is the issue only status updates or do we have other issues. I can think of one scenario when removing devices from ISY and then adding them back in will get the status to work for that device BUT they will make some other device not to report status. That case is if your PLM has around 400+ links. With kind regards, Michel Hi Mike, Thanks for responding. As mentioned above, I have definitely already tried the factory reset/restore method. That approach does not help. Removing the device and reinstalling does. I haven't had time to try any more of the problematic devices (a very large number) so I will wait until I have tried the usual restore methods on other devices. Thanks.

Hello to_lighter, I am so very sorry to hear this. What does "incredibly corrupted" mean? As Mike suggested, can you factory reset another one (without removing from ISY) and then do a restore? With kind regards, Michel

Hi to_lighter, Your assumption is correct. It basically means that you are not bridging all the phases. Going back to FilterLincs, would you be amenable to trying some? With kind regards, Michel

Hello matapan, The only thing we can currently test is the PLM by doing Tools->Diagnostics->PLM Status/Info. Beyond that, there's basically no way of knowing if the problem is obstruction of communications or a defective device for both exhibit the same symptoms: they do not respond to ISY. With kind regards, Michel