Brian H

Well my fading memory maybe failing. I thought I had seen the transmit LED for the phases flash at times with Insteon Message but maybe it was the received LED.

The 2413S I am using with my ISY994i. Is a Hardware 2.1 with 9E Firmware. It is not one of those vaguely referenced. Older 2242-222 HUBs. With the network PCB replaced by a Serial Daughter Board from a 2413S. My older Hardware 1.B Firmware 9B still has the original C7 and C13 capacitors.

Michel, Thank you for the hardware version where the later caps where included. I had thought it was 2.? but that may have been where they updated the firmware. For a possible fix for the All On Syndrome.

The module would have to be reworked for Insteon. The 4826 module in your photo is strictly an X10 Coupler Repeater and had a reputation of sometimes corrupting Insteon power line signals. By thinking the tail end of an Insteon message was an X10 one and sending an X10 message. The 4816 was a similar looking one with no active electronics in it. Just a series LC network between the two Lines. I changed the small coil in one of them to tune it closer to the Insteon power line frequency but it didn't matter that much. I believe 2406H has the same coil and capacitor in it. In the case wired directly to the breakers.

http://forum.universal-devices.com/topic/16285-release-438-rc4-is-now-available/ There is a no PLM version and with PLM version of the firmware in the above release post.

If it is a 2413S Dual Band PLM. It has a LED on the right side that lights Green and turns Red during some signal processing. The older 2412S also has a LED on its right side. If you are running a 2413S and its is around two years old. It probably is failing. They have a reputation of failing just after the two year warranty is expired. Many threads here. Along with the Smarthome and Insteon Forums. One of the early signs is LED dim or out and power cycling sometimes restores it to run for a short time longer. I had one last about one extra week after power cycling. Another sign will be the link database is empty or has only a few entries. If your PLM is a 2413S and around two years old. You may want to think about getting a replacement. Before it dies again.

The Insteon Developers Guide also has information in it. http://cache.insteon.com/developer/developer-guide-022009-en.pdf Power Line Modem Guide also has details. http://cache.insteon.com/developer/2413dev-042007-en.pdf The I2CS Messaging is in this I2CS Developers Guide. http://cache.insteon.com/developer/i2CSdev-022012-en.pdf

I would also say try a new bulb. Electronics in LED Bulbs have been known to change or go bad after running for awhile. If the reset SwitchLinc and new bulb act the same. It does sound like the SwitchLinc may have failed or you have developed a poor connection in the wiring.

Where the PLM is located and what obstacles are in its RF path can also effect the distance. If you look at the carefully worded specifications. It always gives you the maximum distances. It is in open space with NO obstacles in the RF path. My 2413S can only reach one Access Point and no Dual Band module. Due to where it is mounted.

You would need an X10 TM751 or RR501 X10 transceiver to receive the X10 RF command from the Homelink Buttons and send a X10 power line signal the ISY994i could process. I looked at the Skylink 318TR web page and instruction manual. It looks like it has a dry contact output. Normally connected across the original push button for the garage door. A dry contact output should trigger an I/OLinc's Sensor Input. If you decide to use it and not the Homelink buttons built into the car. Since it simulates a manual button push. It will close the Sensor Input to send an On command then shortly send an Off when it opens. Your program or scene would have to handle the commands. http://www.skylinkstore.com/store/us/us-universal-garage-door-accessories/fixed-code-control-kits/garage-door-conversion-kit.html http://www.skylinkhome.com/docs/manuals/ha/318TR_manual_050427.pdf

The HomeLink lamp controls are X10 as Stu pointed out. There customer web site even shows the X10 Transceiver and LM465 Lamp Modules. http://www.homelink.com/about/lighting

You may want to submit a contact form to UDI. http://www.universal-devices.com/contact-support/ They can remotely connect to your setup and see exactly what is happening.

Power down both the PLM and ISY994i Power up the PLM then the ISY994i You must use the Restore Modem (PLM) choice in the File Menu. To get the IDs correct in the modules and new PLM. There is information on how to do this. On this UDI Wiki Page. http://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:File_Menu&redirect=no

ToggleLinc Line to Line in the extension cord. Neutral to Neutral. Ground to Ground. Tape up the load so it can't short to anything.

I am not well versed in the messaging. I do see the command sent to the PLM. The PLM sending an ACK back to verify it was a valid command. I only see one SRX Standard Insteon message ever being received back from the ToggleLinc.

Is the PLM connected to the same circuit as the computing equipment? Computing equipment and UPS units are known to effect power line communications. As a test. Can you power the PLM on an extension cord. To a different circuit and see if anything changes. I have my UPS on a FilterLinc and the PLM in the unfiltered pass through outlet on the front of it. The RF Beacon Tests mentioned should also be done. You did use the ISY Administrative Console to do all the linking and not the manual set button method?

For those who are interested. There is a link posted near the bottom of this Smarthome Forum thread. Indicated by end of today should be active. Is the Insteon HomeKit Knowledge Base http://forum.smarthome.com/topic.asp?TOPIC_ID=16789 There is a Press Release on the Insteon HomeKit here. Mostly related to the HUB Pro and the App. http://www.insteon.com/press-kits-store/?tag=2243-222

If you don't have the full users manual for the ISY994i yet. http://www.universal-devices.com/docs/production/ISY%20User%20Guide%204.2.8.pdf Pages 81-82 have information on replacing a SD card. Though you may want to wait for a reply from UDI first.

Smarthome use to sell a battery eliminator. Wall wart for the motion sensors but I didn't see it listed on the sales pages anymore.

From what I have read here recently. The UDI PLM is on hold for now. I have seen one beta user asking about a international HUB based Serial PLM they have. Over in the Insteon Forums. Since Smarthome or Smartlabs very rarely provide advanced information. I would say anyone's guess when or even if it will it go to production.

I also had issues with a V2.1 9E firmware. The 2440 would not be found if next to the PLM. If I moved it far away it was. Then I tried it again far away but with no other Dual Band Devices powered up. Again no access. My thoughts are the latest PLM or firmware. Can use a power line signal to another Dual Band Device for the 2440 but not its own RF processing. Also could be overloaded by the RF signal as other have thought.

I have had two Hardware 2.5 Access Points with problems. Older hardware 1.? ones are on a different base board. One just locked up and needed a power cycle. The other one was dead. Power supply was around four volts on the unregulated 12 volts. Normally closer to 20 volts. They are built on the same base 2413X PCB as the 2413S. Same capacitors issues as the hardware version 1.? 2413S PLM's. Did the capacitor change just like in my PLM and now both have been running again for over a month.

It is not a controller or responder. So what can be monitored? Its not On Off or anything in between. I did try and add mine. Using both the Auto Discover and Manual Linking method. Event Viewer Level 3 did show some communications between PLM and the Range Extender. Maybe Smarthome is pinging it with a message and just seeing if it responds. Event Viewer Level 3 communications with a Range Extender trying to add it. Auto Discover: Thu 05/28/2015 07:12:31 PM : [23 53 57 ] Added to list of devices to link to ISY Thu 05/28/2015 07:12:32 PM : [iNST-TX-I1 ] 02 62 23 53 57 0F 0D 00 Thu 05/28/2015 07:12:32 PM : [iNST-ACK ] 02 62 23.53.57 0F 0D 00 06 (00) Thu 05/28/2015 07:12:32 PM : [iNST-SRX ] 02 50 23.53.57 34.E9.19 AF 0D FF (FF) Thu 05/28/2015 07:12:32 PM : [std-Direct Nack] 23.53.57-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Thu 05/28/2015 07:12:32 PM : [iNST-TX-I2CS] 02 62 23 53 57 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 Thu 05/28/2015 07:12:32 PM : [iNST-ACK ] 02 62 23.53.57 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 06 LNK-ON (01) Thu 05/28/2015 07:12:32 PM : [iNST-SRX ] 02 50 23.53.57 34.E9.19 2F 09 01 LNK-ON (01) Thu 05/28/2015 07:12:32 PM : [std-Direct Ack] 23.53.57-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Thu 05/28/2015 07:12:32 PM : [LNK-BGN ] 02 64 01 00 06 Thu 05/28/2015 07:12:33 PM : [LNK-STAT ] 02 53 M(01) gid=00 23.53.57 001D 42 Thu 05/28/2015 07:12:33 PM : [iNST-TX-I1 ] 02 62 23 53 57 0F 0D 00 Thu 05/28/2015 07:12:33 PM : [LNK-END ] 02 65 06 Thu 05/28/2015 07:12:33 PM : [std MH ] Unexpected Ack imCmd=65 cmd1= 0x57 Thu 05/28/2015 07:12:34 PM : [iNST-ACK ] 02 62 23.53.57 0F 0D 00 06 (00) Thu 05/28/2015 07:12:34 PM : [iNST-SRX ] 02 50 23.53.57 34.E9.19 2F 0D 02 (02) Thu 05/28/2015 07:12:34 PM : [std-Direct Ack] 23.53.57-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Thu 05/28/2015 07:12:38 PM : [iNST-TX-I1 ] 02 62 23 53 57 0F 0D 00 Thu 05/28/2015 07:12:38 PM : [iNST-ACK ] 02 62 23.53.57 0F 0D 00 06 (00) Thu 05/28/2015 07:12:39 PM : [iNST-SRX ] 02 50 23.53.57 34.E9.19 2F 0D 02 (02) Thu 05/28/2015 07:12:39 PM : [std-Direct Ack] 23.53.57-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Thu 05/28/2015 07:12:39 PM : [iNST-TX-I1 ] 02 62 23 53 57 0F 10 00 Thu 05/28/2015 07:12:39 PM : [iNST-ACK ] 02 62 23.53.57 0F 10 00 06 ID-REQ (00) Thu 05/28/2015 07:12:39 PM : [iNST-SRX ] 02 50 23.53.57 34.E9.19 2F 10 00 ID-REQ (00) Thu 05/28/2015 07:12:39 PM : [std-Direct Ack] 23.53.57-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Thu 05/28/2015 07:12:39 PM : [iNST-SRX ] 02 50 23.53.57 00.1D.42 8F 01 00 (00) Thu 05/28/2015 07:12:39 PM : [std-Broadcast] 23.53.57-->00.1D.42, Max Hops=3, Hops Left=3 Thu 05/28/2015 07:12:39 PM : [23 53 57 0 ] Calibrating engine version Thu 05/28/2015 07:12:39 PM : [iNST-TX-I2CS] 02 62 23 53 57 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Thu 05/28/2015 07:12:39 PM : [iNST-ACK ] 02 62 23.53.57 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Thu 05/28/2015 07:12:40 PM : [iNST-SRX ] 02 50 23.53.57 34.E9.19 2F 2F 00 (00) Thu 05/28/2015 07:12:40 PM : [std-Direct Ack] 23.53.57-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Thu 05/28/2015 07:12:40 PM : [iNST-ERX ] 02 51 23 53 57 34 E9 19 15 2F 00 01 01 00 FF 00 A2 00 2B 96 A5 FF 1C 00 AD Thu 05/28/2015 07:12:40 PM : [Ext-Direct ] 23.53.57-->ISY/PLM Group=0, Max Hops=1, Hops Left=1 Thu 05/28/2015 07:12:40 PM : [23 53 57 0 ] Using Database Link Table offset 0x00F8 (reported 0x00F8) Thu 05/28/2015 07:12:40 PM : [23 53 57 0 ] Failed to add device, reason 10 Thu 05/28/2015 07:12:41 PM : [All ] Writing 0 bytes to devices

I am not surprised it can't be added. I would suspect it has its own firmware to make it act like a signal repeater and not a lamp module.

You may also find the FCC ID number on it is for a 2457D2 LampLinc. Mine is a 2457D2 Lamplinc board with the dimmer components and output AC connector removed. Maybe different on the newest hardware presently being sold.