Brian H

Hold the Bright and Dim buttons. Until the LED starts flashing. You then have about four minutes to write to the RemoteLinc. If you have the Pro version. You can also set it to not automatically update battery powered devices. Then individually put the RF device in the linking mode and then write to it.

Some Insteon Modules had issues with certain firmware revisions.

If you find some used ones. You may want to verify that that don't have known issues. Like some earlier SwitchLincs having intermittent buttons. That Smartlabs extended the warranty to seven years. To the original owner with a Smarthome Invoice Number.

You should normally type in the Insteon Address to the Add an Insteon Device Screen. Some of us have made a chart or list of IDs as we install them. Makes finding it easier than removing switch plates etc. If you used the other linking choice of Start Linking and then walked around to all the modules and used their linking buttons. Then they are found and added.

When you send the Insteon On signal to the I/OLinc from ISY. You can also two lines of code to send the X10 On signal to the UM506. Then the beeper will sound. Like in the morning when my lights are turned on. I send an X10 On command to my chime module to sound a reminder to get up. I send the X10 On code then added a 2 second pause to allow the X10 signals to complete. Then the Insteon command to light the lights is sent.

You may have some power line noise makers, signal absorbers or phase coupling issues. The Ocelots higher signal strength maybe strong enough to over come this and the 2413S is not. Do you have any X10 phase couplers in the system? The 2443 Access Points and all Insteon modules do not resend X10 signals. Do you have any filters on the computer or UPS units you may have. The 2413S should not be on a filtered surge strip. Also Insteon modules being two way also absorb X10 and Insteon signals. Insteon gets resent X10 does not. Many have seen X10 get more problematic as Insteon devices are added to the system.

Sending the X10 signal does sound like a way to go. You could even reset the UM506 to Sounder Only if the clunk of the relay was annoying.

Yes the UM506 does have a beeper that could be triggered when the relay was turned On. I don't believe you can do that with a IOLinc. You may have to trigger an external beeper. Maybe with another Insteon module or trigger it off the closing signal from the IOLinc.

There are others here that have the Garage Door Kit. I am sure they will have good tips for you. I believe you can set the relay's properties in ISY and not have to do the button sequences mentioned in the manual.

Page 11 of the Full Users Manual. How to set the relay to momentary closure. Can also be done through the ISY interface. http://www.smarthome.com/manuals/2450.pdf Smarthome also has a garage door kit that uses the I/OLinc. There is a link on the sales page to how it is hooked up. That may give you some ideas. http://www.smarthome.com/74551/I-O-Linc ... Kit/p.aspx http://www.smarthome.com/manuals/74551qs.pdf

I have the IR option in mine, but at present am not utilizing it. I have a JV Engineering XTB-IIR that hits the power lines with over 10 volts of X10 signals. It also was designed to ignore Insteon power line signals.

One point that may effect your X10 and Insteon installation. Insteon devices are two way as they can also send power line signals. The transmitter in them can absorb power line signals. Insteon modules do resend their messages but not X10 ones. Some have found as they add Insteon devices. The Insteon network gets more reliable while the remaining X10 devices get less reliable. I have a mixed system but have a very strong X10 coupler repeater. So when I added the Insteon my X10 signals are still strong enough.

I assist in the X10 forums. With all the modern electronic devices, making power line noise and absorbing power line signals. Getting a system 100% is not easy. I still use X10 for tests and some modules still not in Insteon. Like a chime module and sixteen button palm pad remote. All my Insteon modules also have an X10 address in them. For use with the palm pad. I have a JV Engineering XTB-IIR Repeater Coupler that hits the power lines with over a ten volt X10 signal. My lowest signal is 1.25 volts. As measured by their XTBM X10 signal meter. It also is smart enough to recognize an Insteon signal and not garbage it. By trying to duplicate it as an X10 signal.

If you coupler is a XPCP coupler. It also has a set of twin tuned transformers. Not sure how narrow it coupling range is.

You most likely have power line communications issues. First if you have the PLM on the same circuit as the computer or an UPS. Filter the computer or UPS but not the PLM. If the PLM is on a surge strip. Try it in an outlet alone. Try disconnecting electronic devices as some can absorb power line signals or make line noise. I would also verify you don't have any loads on dimmers that are not rated for dimming. Like CFLs or low voltage lighting not rated for dimming. If you have any active X10 Repeater/Couplers left over from your X10 days. Try disconnecting them. Some garbage Insteon power line signals. Passive couplers most time do not effect Insteon signals. Insteon is way more reliable than X10 but nothing is 100% out of the box. I am extremely happy with my ISY99i that was an upgrade from the older ISY26 that I started out with.

Can you elaborate on the problems you are having? Some noise and signal absorbers can effect Insteon to some degree as they can with X10 power line signals.

Since I am not using these features. The following erroer messages can be ignored. Thu 2011/09/29 10:10:49 AM System -170001 [sLF] FileOpen Failed: /CONF/IR.CFG Thu 2011/09/29 10:10:50 AM System -170001 [sLF] FileOpen Failed: /CONF/INTEGER.VAR Thu 2011/09/29 10:10:50 AM System -170001 [sLF] FileOpen Failed: /CONF/STATE.VAR Thu 2011/09/29 10:10:50 AM System -170001 [sLF] FileOpen Failed: /CONF/INTEGER.VAR Thu 2011/09/29 10:10:50 AM System -170001 [sLF] FileOpen Failed: /CONF/STATE.VAR Thu 2011/09/29 10:10:51 AM System -170001 [sLF] FileOpen Failed: /CONF/NET/WOL.CFG Thu 2011/09/29 10:10:58 AM System -170001 [sLF] FileOpen Failed: /CONF/ELK.CNF Thu 2011/09/29 10:11:04 AM System -170001 [sLF] FileOpen Failed: /CONF/NET/WOL.CFG Thu 2011/09/29 10:11:07 AM System -170001 [sLF] FileOpen Failed: /CONF/ELK.CNF

Are the Motion Sensors V1 or V2 hardware. I believe only the V2 sensors can be remotely configured. Jumper 5 enables remote configuration. Manuals for both V1 and V2 are here if you can't find yours. http://wiki.smarthome.com/index.php?tit ... art_Guides

Smarthome accidentally had the earlier Insteon PLM Developers Guide avilable for download. It is still avilable on a few sites. http://www.aartech.ca/docs/2412sdevguide.pdf Membership in Developers Group. Isn't what it is cracked up to be. Though occasionally you do get a few tidbits. Serious consultation requires a fee be paid to Smartlabs.

I have had this happen a few times, but not consistently. Open Administrative Console using the jnp link I downloaded for 3.1.9 No Module Status shows in My Lighting for the modules. Open Event Viewer and set to communications messages. Do a query of My Lighting. Ready Icon on bottom left stays Ready. Nothing shows in the Event Viewer. No Query progress box shows on the screen. Though I think it is doing a query as the LEDs on some of the modules are flashing. Indicating messages are on the power line. Closing Administration Console and restarting. Then everything is OK.

They look nice. I have used the 773 series a few times. They have a push in style clamp and not the nice flip release.

http://www.insteon.net/pdf/insteondetails.pdf I will look and see if I can find any others that are not in the developers restricted area.

If Avast recently updated to 6.0.1289. I would also suggest you check the link TJF1960 provided.

From the main sales page: PLM, Power Supply needed for use with the 2413S, shipping and optional taxes. Not included http://www.homeorchestrator.com/UDStore ... ctPurchase

I am using 32 bit, Java Version 6 update 26 with no problems. Beta 3.1.9.