Brian H

Sounds interesting. Since the momentary switch is normally open you could even add the modules output in parallel with the case switch and both would work. Going off may need a longer time depending on your motherboards SETUP. Mine needs the power switch held for four seconds to go off if the software doesn't turn it off.

Since ISY and Powerhome are both messing with the same PLM Link Table. That could be the problem. Using two different programs to alter the same PLM is not a good idea. Or did I read you post incorrectly and you have two PLM Modules and not trying to use the same for both setups?

The new manual says. Move the jumper. Wait 10 seconds. Then initiate a motion detect to set the new setting.

I would also say read the latest manual. I believe after a jumper is moved a procedure has to be followed before the change happens.

Do you have communications issues with then off to other parts of your setup? Do the new lamps have electronic ballasts or dimers? If so they could be a problem. ToggleLinc relay or dimmer?

When I was programming mine and was done. I should have just let them time out. I decided to hit another button to stop it early and ended up turning off the LED and sounder.

I believe that is correct. I had the pre release and don't remember the Advanced Option.

If by some chance. The setup then gets poor communications. Some cell phone chargers make lots of power line noise.

It is the local sensing current that keeps the LED lights dim all the time. Even if you set the Local Control Off it is still there. Just that the module will ignore any local switches being toggled. The ApplianceLincs also do the same thing.

I believe I have read the Windows Firewall is ok as is. Though with all the XP security updates always coming our way. Maybe someone has new data if it is now a problem.

What firewall are you using? Some need some tweaking to allow access. I know my Zone Alarm needed tweaking or My Lighting disappeared all the time. I have XP Pro SP3.

From what I have seen. The HL2 PLM has some special device catalog in it and only works with HL2.

I have two in use and they do not eat batteries like yours does. I would also say call Smarthome as I have also seen messages on short battery life.

Where did you find a USB PLM? I thought the only USB PLM was in the HouseLinc2 Kit and was specially loaded for that software. You didn't by chance buy a 2414U PLC did you? The PLM is a 2412S

Well only a guess here. The OutletLinc on-line manual indicates you can turn local sensing on and off. If it is like the ApplianceLinc the current is always there. You just set it to follow or ignore the load bring toggled. My light bulb thing as you know is not the only way to stop the flickers and dim LEDs. I have even see some X10 users where the current is much higher than Insteon Modules. Use some 220,000 Ohm 1/2W resistors to drain the current. Update: I did some tests and found the 220K resistor does not help much with a 15 White LED screw in bulb. Tried it with a few X10 and Insteon Modules. With a 56K 1/2 Watt. A New ApplianceLinc HW 4.1 still glows, but an old HW 1.3 no visible glow. I know that the new HW 4.1 ApplianceLinks do not sputter and click on my known problem load that drives the old ones crazy. I also have measured a higher local sensing current on the new models.

They may glow dimly when off. The Local Control Sensing current maybe enough to keep them glowing dimly. Even though you can disable the Local Control. The current is still there; just not acted on. If you get a glow. One fix is a small incandescent 4 watt night light connected to the output of the LampLinc. Using one of those power cubes that allow you to connect more than one item to an outlet.

The default setup for the Motion Sensor. Sends an Off after 1 minute of not detecting any motion. It can be set to never send an Off and it can also be reprogrammed by software to time out in 30 seconds. I have not calculated the max timeout. There are a few other I2 commands to do things, but I have no idea if they really work.

I have a single Sunset Program miss the NSR time after a power loss. It showed that the following day was the next time it should run and not the same day as it should have. This was in 2.6.7 and maybe it carried to 2.6.8. Update: I just replaced my PLM using the restore PLM choice in the Files Tab. The Program summary showed my lone Sunset -20 minutes as not to be run until 11/29/08. I went into the Configuration Tab and unchecked Use Daylight Savings Time. Let it do its thing. Then rechecked the tab and again let it do its thing. Now the next expected run time is 11/28/08 as it should be. This is with 2.6.8

Sounds like Smarthome has created a Monster!

I also always do a Factory Reset on all my new Insteon devices. As I have seen others with strange things happening. Some modules have even had X10 addresses in them from what I have read.

I believe only Smarthome flashes the Firmware at the factory. The 2414S is a PLC but I know for a fact my early 2412S PLM was a 2414S with PLM Firmware and even the original Daughter Card. Unused RTC Chip and all.

Even more fun. Sometimes the quirks vary depending on the firmware revision.

Did the LED on the RemoteLinc start flashing? You may want to try moving the RemoteLinc closer to one of your Access Points and see if it maybe a range thing. Maybe trying a Factory reset on it may also help. When I added my second RemoteLinc. I used the Add new Insteon Device mode and then linked the buttons to varied modules.

Yes my new ApplianceLinc hardware 4.1 shows a lower firmware version; but was higher than my older ones.

Most time it is a bad idea to try and dim transformer run low voltage lighting. Unless the lights specifications say they can be dimmed. An ApplianceLinc V2 would be better and I have found the new hardware version 4.1 can control my cranky loads the older version 1.3 could not. Without sputters and things.