Brian H

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.

None needed. The ISY-99i uses the power from the PLM it is connected to.

The Night On worked as expected yesterday. Next run time today also looks correct. It ran as it should have at the correct time.

The Sunset yesterday was 7:10 PM. Missed the scheduled time yesterday so it showed today's of 6:58 PM before I toggled DST from On to Off then back On. It then showed todays as 6:48. Closer to what I expected Today Sunset shows 7:08 PM and the night on time was where I expected it to be, 6:48 PM. -20 from Sunset. Will try to observe when it happens today.

I had a sunset miscalculation after updating from 2.6.6 to 2.6.7. Saved my data Updated. closed My Lighting Cleared Java Cache Restarted My Lighting In the Program Summary My Night On Scene is Sunset -20 minutes turn on all devices. Showed todays sunset as 07:10 PM next run for Night on was for 09/10/08 [missed todays] as 06:58 PM. I thought it would be closer to 06:48 PM Release Notes said DST was a fix so I turned off DST then back on. Now Next run of Night on was showing 06:48 PM on 09/10/08 My location is a custom Longitude and Latitude.

http://board.homeseer.com/showthread.ph ... post832142 Looks like Homeseer is now dropping the Insteon Plug In and teaming up with UDI. At least on new devices if I read the post correctly.

Thank you for thet information and great support.

Would the ISY99i have the same limits as the ISY-26; on the major update plans?

I believe the ISY99 will remove old Insteon Links when adding them. Problem maybe old X10 ones; that may not be removed when the device is added. If not flaky; then maybe the seller cleared them out.

You may also want to go to the Smarthome web sites page for the model switch you bought. There should be a link to the Full Users Manual. It can be a great help with much more data then on the Quick Users Guides in the box. Since they where in a demo home. I would do a Factory Reset on all of them to clear out any cobwebs. Even new ones; it is a good idea to Factory Reset any Insteon modules. Seems some get shipped with test data in them.

I believe the HD501 is the OEM module made by X10 that is like the RR501. I have had an RR501s power supply fail and do strange things. I rebuilt mine and again it is fine.

If you chose economy shipping; they do hold the order until complete. Standard ground shipping allows you to ship partial and they send the remainder when in stock. But the remainder is economy with no insurance and tracking. So I always use Standard and don't ship partial. Have you look in the great UDI Knowledgebase for data? Helpful data even if the unit is not in your hands yet. http://www.universal-devices.com/mwiki/ ... =Main_Page

From messages in other forums. They can get quite warm by most folks thinking of what warm or hot is. Smarthome has said in some forums that they meet UL and ETL standards and that standard is in mi option too warm; but they said it is safe. Also remember if you have two next to each other they must be derated. http://www.accessha.com/forums/showpost ... stcount=48

I have 150;200 and a 300 watt Light bulb. Not that I have them in a circuit right now. The heat is generated by the electronics in the SWL. If the dimming SWL there is a triac that regulates the level to the bulbs. It does generate heat. If it is mounted in a plastic box and not a metal one it may even get warmer as I believe some of the heat spreads through the mounting ears to the box.

Thanks for the update. A BoosterLinc of all things. APs use both RF from unit to unit and send and receive on the powerline also. For Insteon signals. X10 is not processed by APs or the older RLs. That is why my ACT CR134 X10 repeater is still in use. Though X10 is not that important any more as there are now RemoteLincs and soon to be released Motion Sensors.