LeeG

This Program is separate from the posted Program. It reacts to the ‘nightlight’ being turned off between Sunset and Sunrise, waits 10 minutes and turns the Scene On. If From Sunset To Sunrise (next day) And Status ‘nightlight’ is Off Then Wait 10 minutes Set Scene 'IL Night Timer' On Else

Copy to Clipboard/Paste the actual Program. Make sure there are no changes pending Save for the Program and make sure the Admin Console shows button B On before the trigger time arrives. Also make sure the Program is not in a Folder with a False condition. .

The problem being that certificate management cannot be accessed when connected locally? Have you tried Help | Request/Manage SSL certificates?

Do you not have to be connected locally to work with certificates? Thought that was done for security reasons to prevent someone from the outside affecting certificates.

I take the comment about plugging the PLM into a FilterLinc is that it was done to force RF only communication to/from the PLM itself. Was that done to solve powerline problems? Is there a 900 MHz cordless phone in use? Mine has very long range so could be a neighbors. Hops Left=2 is great. Not unusual to have a Hops Left=1 which is fine if that number remains steady. Could be something like the refrigerator since it cycles infrequently. .

Thanks for the additional detail. It could be PLM but with the additional information I am more inclined to think there is intermittent interference. Not likely an Access Point issue with everything working most of the time. Is there an appliance/device running at the time of the failures? Certain light pattern during the time of the failures. It is not a major human effort to replace a PLM although it takes time for the ISY to update every installed device link database with the new PLM Insteon address. The battery powered RF only devices have to be put into linking mode and updated one at a time. Can get a general sense of the Insteon network by running Tools | Diagnostics | Event Viewer at LEVEL 3. Using the Admin Console turn On/Off various devices and look at the Hops Left=x count in the event trace. Hops Left=2 is best, Hops Left=0 is worst, Hops Left=x counts that jump around when controlling the same device indicates a problem.

With KeypadLinc buttons responding, particularly if they are Secondary buttons, I would first look at things like phase coupling. Be sure the Access Points are plugged into the intended outlets. Run the 4 tap test and verify they are receiving each other and are on opposite phases. Have any new appliances or devices been added to the electrical circuits. Have existing devices, PC, router, modem, UPS been moved or no longer on a FilterLinc. The PLM could be failing but with it working with some devices and not others I would look at other areas first before thinking about replacing PLM.

Did you reseat the SD card? Power to the ISY should be removed before unseating SD card. EDIT: I see your previous post was updated with the SD question.

To address the blinking Err LED, remove power from the ISY. Remove and reseat the micro SD card. It may have come lose during shipment.

The power to the ISY should be Off when the PLM is connected. Apply power to ISY after PLM connected and powered. This will boot the ISY. Port A does not have LEDs. Both LEDs on the Internet RJ45 jack should be On.

Was the PLM connected and powered before powering the ISY. Was the ISY rebooted after the PLM was connected?

No. Not unless the ISY has been locally configured that way.

"My understanding is that as soon as I plug the 994i into the PLM the PLM connection to the 99i is toast, unless I go through a lengthy restore." The PLM should not be affected. The normal procedure for moving from a 99i to a 994i does not require a Restore Modem (PLM) as the PLM is not affected. EDIT: also the Restore Modem (PLM) by itself is not a long process. It is if changing from active PLM address to another active PLM address as all the references in all the devices has to change. Since the same PLM is being used a Restore Modem (PLM) is simply building the PLM link database which takes a few minutes at most.

It comes with a memory card. There is no reason to try running the ISY without the PLM connected to the ISY at Port A and plugged into 120v. This should happen before the ISY is powered up. The lack of PLM and associated failure to communicate with the PLM is reflected in the LEDs on the front of the ISY. This can only confuse the issue of what LEDs are On relative to the network issue. The default mode of the ISY is DHCP so the router should be setup to provide an IP address with DHCP, at least until the ISY operating and the Admin Console is invoked so the network configuration can be changed to a static IP.

The SwitchLinc must be a Controller of a Scene. It can be a dummy Scene that is not used. Use the Adjust Scene Action statement, the In Scene and Set parameters specify the node name of the SwitchLinc. Again, to be able use the SwitchLinc node name in the In Scene parameter the SwitchLinc must be a Controller of a Scene. Specifying the SwitchLinc node name in both the In Scene and Set parameters causes the ISY to set the Local settings. These are the settings which affect what happens when the paddle is pressed..

I would think so. I do not have any of those Dual Band KPLs as they just came off Beta status. The ISY now always looks at the actual device type (cat/subcat) to determine how to process a given device. Many images back the ISY would accept the Device Type entered in New INSTEON Device as the overriding definition. This is no longer true. With the advent of I2CS devices it now is a necessity the ISY discovers from the device itself exactly what type device.

It should say 6 button although the 6 button KPL has 5 nodes. The ON/OFF buttons are represented by a single node as both the ON/OFF buttons use the same Scene (Group) number. The -222 and -232 indicate RF frequency. 2334-222 is 8 button KPL that operates on the US RF frequency. 2334-232 is 6 button KPL that operates on the US RF frequency.

WayneW This thread is related to using a PLM on 220v 50hz power (outside of US), which is outside the operating specs for the PLM. The 50 hz line frequency is incompatible with the correct operation of a PLM. Thanks for posting your experience/solution but it does not apply to the OP problem.

The RS-485 interface is accessed through the RJ45 jack. I think it is either RS-232 or RS-485, not both. I'll go through my doc and see if I have anything specific on pin usage. .

The Smartenit EZIComm is the SmartLabs PLM with a different label. SmartLabs is the only manufacturer of the Insteon PLM. The EZIComm can be purchased with an optional RS-485 interface rather than the normal RS-232 but that is just a different Daughter card. SmartLabs does not license any company to design and build their own PLM.

"I press the "Start Linking" button and the PLM makes a little squeak and begins blinking its LED. I have yet to see a pop-up message with a FINISH button to press." When the popup with the Finish button does not appear it means the data the ISY is trying to push out to the Admin Console is being blocked. Usually a problem with AV. Are you using Kaspersky or Avast? They are the usual culprits but not exclusive. The ISY has to be put into the trusted or white list (?). I don't use either of those AV products but I think that is the terminology. Since the Finish button does not display Start Linking does not terminate. It is necessary to reboot the ISY to clear the Start Linking. .

You should talk to Smarthome to determine if they have a Home Automation solution for 220v 50 hz. They market individual devices that can be powered from 100-240v 50-60 hz. There is the new Hub that replaces the SmartLinc which may offer some HA at 220v 50 hz. However, I have not seen any device that provides PLM function designed to run on other than 120v 60 hz. Based on the event traces posted no reliable Insteon communication is possible with the 120v 60 hz PLM powered from a 50 hz source. This is the first time I have heard of anyone trying to use a PLM on a power source other than one it was designed for. EDIT: note that devices are 'linked' to the PLM, not the ISY. Of course the ISY has information that the links exist but the actual 'link' is between the PLM and a device. I see no way to make that work on 50hz with the current PLM.

Sorry, I have no experience using Insteon at 50hz. No idea if the RF associated with 2413S PLM will function on 50hz. It would require Dual Band devices that have operational specs 50-60hz, 100-240v. These are questions that should be addressed to Smarthome. It has nothing to do with the ISY. There is also a serial interface issue with the PLM and Extended (long) messages at 50hz. The second line below should have been a mirror image of the line above with an 06 on the end. Note the two F6 bytes in the second message (echo message) and they are in the wrong location. That is why the device NACKed the third attempt (no response to the first two attempts) because the CheckSum byte was wrong. Until SmartLabs manufactures a PLM designed to operate at 220v 50hz I don't see your system working. Thu 07/04/2013 20:52:08 : [iNST-TX-I2CS] 02 62 1F FE AC 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 Thu 07/04/2013 20:52:08 : [iNST-ACK ] 02 62 1F.FE.AC 1F 09 00 00 00 00 00 00 00 00 00 00 F6 F6 00 00 00 06 LNK-ON (00) Thu 07/04/2013 20:52:09 : [iNST-SRX ] 02 50 1F.FE.AC 22.7F.7A A3 09 FD LNK-ON (FD) Thu 07/04/2013 20:52:09 : [std-Direct Nack] 1F.FE.AC-->ISY/PLM Group=0, Max Hops=3, Hops Left=0

The PLM will not work at 50hz. From the PLM specs - 120 Volts AC +/- 20%, 60 Hertz, single phase. X10 signals start at zero crossing so the circuitry can wait until it sees zero crossing. Insteon signals start before zero crossing so the circuitry is very sensitive to the actual line frequency. Not sure that is the only issue with your install as the PLM requires 120v as well. Whatever is being used to reduce the voltage going to the PLM is also likely interfering with the Insteon signal..

The Insteon communication is all but non-existent. In the first sequence it took three attempts to get any response from this device (different from the other post) and when it did respond on the third attempt the Hops Left=0 indicates the worst possible communication. Thu 07/04/2013 20:51:30 : [1F FE AC ] Added to list of devices to link to ISY Thu 07/04/2013 20:51:30 : [iNST-TX-I1 ] 02 62 1F FE AC 0F 0D 00 Thu 07/04/2013 20:51:30 : [iNST-ACK ] 02 62 1F.FE.AC 0F 0D 00 06 (00) Thu 07/04/2013 20:51:39 : [iNST-TX-I1 ] 02 62 1F FE AC 0F 0D 00 Thu 07/04/2013 20:51:48 : [iNST-TX-I1 ] 02 62 1F FE AC 0F 0D 00 Thu 07/04/2013 20:51:48 : [iNST-ACK ] 02 62 1F.FE.AC 0F 0D 00 06 (00) Thu 07/04/2013 20:51:50 : [iNST-SRX ] 02 50 1F.FE.AC 22.7F.7A A3 0D FF (FF) Thu 07/04/2013 20:51:50 : [std-Direct Nack] 1F.FE.AC-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 The next sequence had no better results. The request to put the device into linking mode failed with a NACK. Also it took several attempts to get any response and when it finally did the Hops Left=0 was the same bad result. Thu 07/04/2013 20:51:50 : [iNST-TX-I2CS] 02 62 1F FE AC 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 Thu 07/04/2013 20:51:59 : [iNST-TX-I2CS] 02 62 1F FE AC 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 Thu 07/04/2013 20:51:59 : [iNST-ACK ] 02 62 1F.1F.01 00 00 00 00 (00) Thu 07/04/2013 20:52:08 : [iNST-TX-I2CS] 02 62 1F FE AC 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 Thu 07/04/2013 20:52:08 : [iNST-ACK ] 02 62 1F.FE.AC 1F 09 00 00 00 00 00 00 00 00 00 00 F6 F6 00 00 00 06 LNK-ON (00) Thu 07/04/2013 20:52:09 : [iNST-SRX ] 02 50 1F.FE.AC 22.7F.7A A3 09 FD LNK-ON (FD) Thu 07/04/2013 20:52:09 : [std-Direct Nack] 1F.FE.AC-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Thu 07/04/2013 20:52:09 : [iNST-DUP ] Previous message ignored. Thu 07/04/2013 20:52:13 : [1F FE AC 0 ] Failed to add device, reason 3 Thu 07/04/2013 20:52:13 : [All ] Writing 0 bytes to devices What are the characteristics of the electrical system being used? PLMs do not run on 220v which suggests some configuration that may not be compatible. How is the PLM being powered? How is the PLM being coupled to the other phase (if there is one).