Michel Kohanim

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

Hi again, First of all, I know how frustrating this can be especially after having gotten it to work properly and then back to square one. Now, based on what I read from your post, I think you may need some FilterLincs. This is what I would do: I would put all other devices (computer, UPS, monitor, etc) on a power strip and then I would connect the power strip to the AC outlet via a FilterLinc. This way, all sources of noise (if any) are attenuated. I would put the PLM and Access Points on their dedicated power strip (WITHOUT a FilterLinc). Then, if you have any Plasma TVs, I would filter them out using FilterLincs as well. After you are done with adding Filters, then I do recommend doing some tests (Tools->Diagnostics->Scene Test) just to make sure the signals are coming back from your devices. For those that do not respond, compare the tables. I suspect that after going through this experiment, you will have a much better status reporting from all your devices. And, finally, if your PLM has link count of around 400, I do recommend getting a replacement PLM (followed up by File->Restore Modem ). With kind regards, Michel

Hello taskman, Yes, that's precisely it. And, you need the same switches to also control other lights, simply drag and drop them in the same scene as responders. With kind regards, Michel

Hello to_lighter, Whatever you do, please DO NOT do Remove PLM; this basically removes all the PLM links from all your devices and therefore you will never ever get any status feedback from any of your devices (unless you Restore ISY + Restore Devices). In short, this is a very bad idea. From what I read, I am very positive that the problem is either the PLM OR one your Access Points (possibly unplugged)? You had mentioned that you had unplugged the PLM and then after you plugged it back in, then everything started acting up. My question: 1. Why did you have to unplug the PLM? 2. And, did you change the configuration of the PLM location after you plugged it back in? i.e. did you plug it into a different outlet? Did you add another device to the same strip? etc. With kind regards, Michel What about Remove PLM? What does that do? Cheers!

Hi Illusion, Just wanted to let you know that we have not forgotten about you and thank you again for your input. We are trying to reproduce, make a test case, and then send off to development for fix. Thanks for your patience and continued support, With kind regards, Michel

Hi to_lighter, Not receiving events is PLM related. If you had set up a static IP address, factory reset reverts back to DHCP. So, that could be one of the reasons you cannot telnet to ISY. After we figure out what's going on with your ISY, we will have to establish the fact that factory reset should almost never be done (unless you have a corrupt file system). It's surely our fault for not having documented when to factory reset; this we shall do shortly. With kind regards, Michel Good question, I'll check the lights when I get home. 99i. Cheers!

Hello intellihome, As much as I would want you to purchase a unit from us but, from experience, I can tell you that upsetting a dependable system (by introducing other variables) is usually not a good idea. Especially if X10 is involved. As far as ISY plugin, the power of ISY is in scene management (group of devices) and thus, for instance your sunset scene, would require only one command and not a sequence of commands. For this, you will need an ISY plugin. For more information on scenes, please take a look at our recently updated and enhanced Wiki: http://www.universal-devices.com/mwiki/ ... w-To_Guide . Otherwise, for what you are suggesting, there are much less expensive solutions such as PowerHome and HouseLinc which allow you to configure your INSTEON network. With kind regards, Michel

Hi RLAV, My pleasure. I am not sure ... I am going to forward this post to our guru and see what he has to say. With kind regards, Michel

Illusion, Are you also using the dusk/dawn sensor on your motion sensor? With kind regards, Michel

Hi LG, You should not have any problems as long as you have not done a Restore Devices/Restore PLM on your 99 (assuming that you used your 26 backup and restored it into your 99). With kind regards, Michel

Hi W, I do agree with you. We do have some third parties who are working on this solution, right now, and we should more than one solution hopefully soon. With kind regards, Michel

Hello RLAV, Apologies for a tardy reply. Yes, this makes a lot of sense and thanks so very much for sharing it. Perhaps we should add some information in the Wiki with regards to RF devices sending two commands. Thanks again and with kind regards, Michel

Hi BryanE, This is usually related to ISY not being able to get an IP address from your router. What worries me the most is the reason why you had to do a factory reset on ISY! With kind regards, Michel

Hello Illusion, All RF devices send two commands. The theory behind it is that sending multiple commands increases the likelihood of success. With kind regards, Michel

Hi RLAV, My pleasure. Would you be kind enough to let me know what it is you are trying to achieve? With kind regards, Michel