LeeG

The ISY needs to be powered down when connecting the new PLM. Power up the new PLM, then power up the ISY. Be sure to follow Wiki instructions for replacing PLM.

If/when the Folder is no longer True the Programs in the Folder cannot Run. Perhaps the Away/Home check is in each Program rather than a Folder. When "If 'statevar' is Away" would turn False when Home, driving the Else clause.

Or that SwitchLinc is not handling them. That is why I suggested using an extension cord to plug the SwitchLinc into the PLM power point. All the home improvement stores carry them, plug on one end, bare stripped wires on the other. I test all my devices that way before installing in permanent location.

Extended messages are not used between devices and not used by ISY to turn On/Off the SwitchLinc. They are used during add of device to the ISY and when Scenes are created or modified. Something in the Insteon network is not handling Extended (long) messages.

This is what a v.44 SwitchLinc add should look like in this area. Thu 02/19/2015 10:22:30 PM : [LNK-STAT ] 02 53 M(01) gid=00 33.95.41 0120 44 Thu 02/19/2015 10:22:30 PM : [33.95.41 00] Linked device type=01.20 fw=44 Thu 02/19/2015 10:22:30 PM : [33 95 41 0 ] Added to list of devices to link to ISY Thu 02/19/2015 10:22:30 PM : [LNK-BGN ] 02 64 01 00 06 Thu 02/19/2015 10:22:39 PM : Stop Insteon Device Linking Mode, Final processing to follow Thu 02/19/2015 10:22:39 PM : [D2D EVENT ] Event [11 B6 BC 1] [DOF] [1] uom=0 prec=-1 Thu 02/19/2015 10:22:39 PM : [ 11 B6 BC 1] DOF 1 Thu 02/19/2015 10:22:39 PM : [D2D-CMP 0073] CTL [11 B6 BC 1] DOF op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Thu 02/19/2015 10:22:39 PM : [LNK-END ] 02 65 06 : : Unexpected, ignored (65) Thu 02/19/2015 10:22:39 PM : [D2D-CMP 004F] CTL [11 B6 BC 1] DOF op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Thu 02/19/2015 10:22:39 PM : [iNST-TX-I1 ] 02 62 33 95 41 0F 0D 00 Thu 02/19/2015 10:22:39 PM : [iNST-ACK ] 02 62 33.95.41 0F 0D 00 06 (00) Thu 02/19/2015 10:22:39 PM : [iNST-SRX ] 02 50 33.95.41 22.80.0B 2B 0D 02 (02) Thu 02/19/2015 10:22:39 PM : [std-Direct Ack] 33.95.41-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 02/19/2015 10:22:39 PM : [33 95 41 0 ] Calibrating engine version Thu 02/19/2015 10:22:39 PM : [iNST-TX-I2CS] 02 62 33 95 41 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Thu 02/19/2015 10:22:40 PM : [iNST-ACK ] 02 62 33.95.41 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Thu 02/19/2015 10:22:40 PM : [iNST-SRX ] 02 50 33.95.41 22.80.0B 2B 2F 00 (00) Thu 02/19/2015 10:22:40 PM : [std-Direct Ack] 33.95.41-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 02/19/2015 10:22:40 PM : [iNST-ERX ] 02 51 33 95 41 22 80 0B 11 2F 00 00 01 0F FF 00 AA 00 22 80 0B 00 1C 01 4E Thu 02/19/2015 10:22:40 PM : [Ext-Direct ] 33.95.41-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Thu 02/19/2015 10:22:40 PM : [33 95 41 0 ] Using Database Link Table offset 0x0FF8 (reported 0x0FF8) Thu 02/19/2015 10:22:41 PM : [33 95 41 1 ] Start : Adding device to ISY Thu 02/19/2015 10:22:41 PM : [33 95 41 1 ] Finish : Adding device to ISY was Successful Thu 02/19/2015 10:22:41 PM : [33 95 41 1 ] Link 0 : 0FF8 [A20022800BFF1F01] Saving [A20022800BFF1F01] There are additional trace entries but the Red shows what should be happening. The Blue messages are missing. Either 1 - Extended message is not reaching SwitchLinc 2 - SwitchLinc is not responding 3 - Response not making it back to PLM Suggest putting SwitchLinc on extension cord and powering from PLM location.

The command that asks for the link database location was issued three times and failed to get a response to any of the three attempts. There should have been an 02 5x response. Is this device some distance from the PLM? How old are the devices around this device? There should have been an Extended message response. Wed 02/18/2015 08:23:28 PM : [iNST-TX-I2CS] 02 62 33 98 5D 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 02/18/2015 08:23:28 PM : [iNST-ACK ] 02 62 33.98.5D 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Wed 02/18/2015 08:23:37 PM : [iNST-TX-I2CS] 02 62 33 98 5D 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 02/18/2015 08:23:37 PM : [iNST-ACK ] 02 62 33.98.5D 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Wed 02/18/2015 08:23:46 PM : [iNST-TX-I2CS] 02 62 33 98 5D 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 02/18/2015 08:23:46 PM : [iNST-ACK ] 02 62 33.98.5D 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Wed 02/18/2015 08:23:50 PM : [33 98 5D 0 ] Failed to add device, reason 9

Unfortunately not.

The older PLMs (before PLM hardware v.20) had power supply problems (bad capacitors) that had various symptoms. Smarthome is shipping PLMs with the corrected hardware. UDI has 5 PLMs ready to ship but has to wait for All On symptoms to be corrected with new PLM firmware (PLM firmware comes from SmartLabs) or it is proven that the PLM is not the cause. If your PLM is failing get a new one from Smarthome. The problem is your symptoms could well be Insteon network related rather than PLM.

Click on the Red door sensor below the Scene name. The On Level and Ramp Rate values apply to when the door sensor is the Controller.

If it is cycling through different devices that may be fine. Can you see the Insteon address in the small popup window

Link records are Insteon structures. There is an insteondetails.pdf on insteon.com that covers the basic link record.

Do a Show Device Links Table for the SwitchLinc Relay that is reacting. It sounds like it has a half the ISY is not aware of.

A Scene issued from the PLM (as in Program issued) is not ACKed nor retried. When an issue exists when Scene driven from a device it means a Insteon network issue as there are ACKs and retries. When problems are seen here it is common to see problems when driven from PLM.

The first Direct On works, the second and third are lost. The Set Scene ..... On is a single Insteon command that makes it out of the PLM before the next Fast On message is received. A Scene On/Off is fine if the Insteon network is good. It is a single Insteon command with no retry. If moving to Set Scene then the X10 messages will likely overlap the additional Fast On message so a Wait between the Set Scene and the x10 activity is a possibility.

Not sure what the question is. If asking can "If Control" be used, yes. If Control 'dryer-Opened' is switched Off Or Control 'dryer-Opened' is switched On Then

Add a 2 second delay. One second may be enough but start with 2 seconds. From the trace the Remote Fast On messages are being received at the same time outbound messages are being sent. Outbound to 33 AE BF and 33 AD 62 are lost during the overlap Sun 02/15/2015 02:44:54 PM : [iNST-SRX ] 02 50 2E.E9.72 00.00.07 CF 12 00 LTON-F (00) Sun 02/15/2015 02:44:54 PM : [std-Group ] 2E.E9.72-->Group=7, Max Hops=3, Hops Left=3 Sun 02/15/2015 02:44:54 PM : [D2D EVENT ] Event [2E E9 72 7] [DFON] [0] uom=0 prec=-1 Sun 02/15/2015 02:44:54 PM : [ 2E E9 72 7] DFON 0 Sun 02/15/2015 02:44:54 PM : [D2D-CMP 000A] CTL [2E E9 72 7] DFON op=1 Event(val=0 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Sun 02/15/2015 02:44:54 PM : [iNST-SRX ] 02 50 2E.E9.72 00.00.07 CF 12 00 LTON-F (00) Sun 02/15/2015 02:44:54 PM : [std-Group ] 2E.E9.72-->Group=7, Max Hops=3, Hops Left=3 Sun 02/15/2015 02:44:54 PM : [iNST-DUP ] Previous message ignored. Sun 02/15/2015 02:44:54 PM : [iNST-TX-I1 ] 02 62 33 A8 54 0F 11 FF Sun 02/15/2015 02:44:54 PM : [iNST-TX-I1 ] 02 62 33 AE BF 0F 11 FF Sun 02/15/2015 02:44:54 PM : [iNST-TX-I1 ] 02 62 33 AD 62 0F 11 FF Sun 02/15/2015 02:44:54 PM : [iNST-TX-I1 ] 02 62 33 A7 86 0F 11 FF Sun 02/15/2015 02:44:54 PM : [iNST-TX-I1 ] 02 62 33 A8 3F 0F 11 FF Sun 02/15/2015 02:44:54 PM : [iNST-TX-I1 ] 02 62 33 A8 33 0F 11 FF Sun 02/15/2015 02:44:54 PM : [iNST-SRX ] 02 50 2E.E9.72 33.5D.7B 4A 12 07 LTON-F (07) Sun 02/15/2015 02:44:54 PM : [std-Cleanup ] 2E.E9.72-->ISY/PLM Group=7, Max Hops=2, Hops Left=2 Sun 02/15/2015 02:44:54 PM : [iNST-DUP ] Previous message ignored. Sun 02/15/2015 02:44:54 PM : [iNST-ACK ] 02 62 33.A8.54 0F 11 FF 06 LTONRR (FF) Sun 02/15/2015 02:44:54 PM : [iNST-ACK ] 02 62 33.A8.54 0F 11 FF 06 LTONRR (FF): Duplicate or ACK for a different device

Suggest the following changes when using default single node. If Status 'dryer-Opened' is Off Or Status 'dryer-Opened' is On Then Wait 15 seconds Wait 5 minutes Run Program 'Dryer is done - Notify' (Then) Else - No Actions - (To add one, press 'Action')

Need information on how the Open Close Sensor is configured. Is an External sensor being used, is it configured for both nodes. If set up for two nodes, both nodes send On commands so "If Status" does not work. Once Status of both nodes changes to On the Program is not triggered. If configured for two nodes "If Control" must be used. No need for two Wait statements. A single Wait of 5 minutes is fine.

Because these are individual device On/Off, if the suggestion from PurdueGuy does not resolve things, run Tools | Diagnostics | Event Viewer at LEVEL 3 and post event trace. The Acks and Hop counts should provide information about Insteon network quality. The Remotes send multiple RF On/Off commands which can interfere with the first few devices which is why PurdueGuy suggestion will often solve the problem.

"Any suggestions about keeping the clock time matching the computer time." Enable NTP access. If the PC time does not match the US government NTP time, right click on PC time display and adjust to match NTP time.

Unfortunately my 8 button 2334-222 v.43 blinks buttons B and G and H when in non-toggle On mode or non-toggle Off mode. What ISY firmware is being used? (Help | About for Firmware and UI levels)

Were G and H turned On by button B?

Which button blinks twice (as mine do) and which does not blink? What KPL firmware and 6 or 8 button?

Good news. Happy to help.

Use "If Status" for the Off check. If Control ..... is switched Off does not And well. There will not be two Off commands received at the same time but there will be If Status Off for both at the same time.