Brian H

All Insteon devices have a microcontroller chip in them. All can generate some electronic noise. By rotating your radio 90 degrees the noise getting into the radios antenna was reduced.

X10 power line signals are an address that wakes up the module. Then a X10 command. If the chime module is addressed and then sent the On command and is busy processing the chime function. The next X10 Address maybe missed [the one that should tell it it is no longer the addressed module] so the chime module still thinks it is being addressed and see the on command for another module to turn on. It WILL chime again. Mine does the same thing. I send a chime on; then light some X10 addressed lights. It frequently chimes again. This is with an X10 controller and is not in any way an ISY issued command. I can also chime my module with other light addresses from my palmpad remote if I get the buttons timed exactly right. It is most likely the chimes way of working and not an ISY thing. I reread your post. It does look like in your example the actual chime on is being sent twice. So my missed new address command example may not be your problem.

If the RemoteLinc's LED starts flashing after pushing a linked button. One or more of the devices is not responding back that the command was received. Could be the signal didn't get back to an Access Point to relay the message back to the RemoteLinc.

I don't believe there is an installation CD anymore. My original ISY-26 came with a CD, but my ISY99i didn't have one. All the latest is on the web and in the wiki. http://www.universal-devices.com/mwiki/ ... =Main_Page

Could be a Firewall thing. I know my Zone Alarm Software did funny things until I put the ISY99is address in the Trusted Zone. What Firewall are you using?

Yes I have the 2.6.13 and two motion sensors. In their boxes. Until my v4.1 ApplianceLincs are going well. No more new Insteon Devices are going into my setup. I knew there was a peak poke memory location to set it. I just didn't know if it was implemented yet. Now I know it is.

There is a memory location in the motion sensor that sets the time delay after the last motion to when the off is sent. Up to 255 30 second intervals. By my calculations that is 2 hours 7 minutes and 30 seconds. I don't know if anyones software can modify this at the present time. Also Smarthome's documentation is frequently flawed. So if this setting actually works is anyones guess.

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