rowland

I'm seeing mismatched records and I never ran 2.6.13. The last version before 2.6.14 was 2.6.11.

Thanks for the report. I'm interested to know if the filter helps. BTW, inconsistent reports about the PLM links table doesn't indicate a bad PLM. It indicates line noise that causes devices to malfunction but doesn't cause communications problems.

It's possible that your problems are due to line noise that causes the logic in the devices to not work properly. This is different than line noise that blocks communications between properly working devices. The symptoms manifested by these two different types of problems are quite similar. It's important to determine which type of problem you have since the methods to fix one type of problem are ineffective at fixing the other. A simple test to determine if you have the former problem is to direct the PLM to report it's links table. In the admin console Tools->Diagnostics->Show PLM Links Table. By selecting Start the contents of the PLM's links table will be presented. It's the number of links reported that is important. Do this 4 or 5 times and see if the number of links reported varies. If it does then you probably have line noise that causes the devices to not work properly (i.e. not communication issues). Note, the Count button on the dialog box won't help - it just reports the number of links. It's the act of getting the PLM to retrieve and list the link table that is important. If you have this type of problem it's relatively easy to locate the source. My strategy was to first get a minimal working configuration, i.e. where the number of links reported is consistent. Then I planned to add parts of the network in small increments and testing (via listing the links table) after each increment. In the first step I had only one breaker on that ran the PLM (and the ISY connected to it), the router, and the PC. Testing this showed that I had the problem even in this minimal configuration. Replacing the PC with a laptop fixed the problem; i.e. listing the links table worked consistently. I was lucky that I found the problem in the first step. But, the point is that you can try different things and determine quickly and reliably if you've made a difference. I have a theory about why this PC caused the problem. In a sense, it's not really relevant, since the fix was to either replace the PC, or it's power supply. Two Filterlincs wired in series with the PC didn't fix the problem. If you're interested you might want to check out http://forum.universal-devices.com/viewtopic.php?t=1188

Actually, SH has a really excellent beta program. Lots of very experienced users that try out new and old products in a wide array of applications. Many, many, many problems have been discovered by the beta users. SH has done an excellent job of developing the beta program; it just runs itself. And, SH has managed to get the beta users pay SH to be in the program. The only problem with the beta program is that all of the people in this forum are in the program. As far as I can tell there are no actual end users of SH products, just beta users. [/rant]

Oh, I guess I left that part out. SCAN Z shows the contents of the PLM's link database. As such, it should show the same results each time it is run. If it shows a different number of entries on different invocations then you could be having the kind of problem that I had. So run it 4 or 5 times and see if you get the same number of entries listed. If not, you might want to check out http://forum.universal-devices.com/viewtopic.php?t=1188

SCAN Z is the command to list the link database of the attached PLM. To list the link database of a particular device use SCAN where has any leading 0 and all ".' removed. E.g to list the link database of the device 0A.17.E7 issue the command SCAN A17E7

Michel, Not sure if you saw blartyo's reference about providing a way to control the Keypad's LED brightness. Did you guys plan on providing this capability?

I've used Firefox with the ISY without any problems

Hmm, I'm seeing just the opposite. When the backlight is set to OFF or very low the LED brightness in the ON state is very low. I called SH and they confirmed that is the way it is supposed to work. Actually, I'd like them to work the way Wayne describes it; OFF state being very dim of off, and On state being bright enough to see in the daytime

This could possibly be done using the ISY-JSDK and JavaMail API 1.4.1. I don't have any experience with JavaMail but I did take a quick look. It would appear to be a mature enough package to have the parts necessary to catch a specific email. It's a question of how desirable the feature is. This kind of thing is what is so great about the ISY. Supporting an email as an event that triggers Insteon processes probably can't be justified in terms of the coporate resources required by UD. However, the ISY-JSDK interfaces to the ISY at a level that makes possible all sorts of one-off, arcane applications.

Thanks for the info. You never know when SH will do the right thing. But, I should've checked first.

Actually, since a PLM is not field upgradable to new firmware versions, I think it's all a marketing plot on the part of SH to sell more PLMs to people who have already own a PLM.

How did you guys do this? It's not that I actually need to know, I'm just curious. I tried using HouseLinc to look at the KPL's link database but HouseLinc can't read the link database. I'm supposing this means that the link database contains links in a configuration that HouseLinc doesn't understand, much less, know how to present.

My 2.4.11 seems to be working fine.