LeeG

Switching to a new PLM after doing a Delete PLM does not restore the PLM activity. Delete PLM has removed all PLM references in the ISY configuration as well as removing PLM Controller links in each device. Simply switching to a new PLM DOES NOT restore the PLM information in the ISY nor the devices. PLEASE DO NOT DELETE PLM. YOU WILL BE VERY SORRY FOR THAT ACTION.

The Heartbeat occurs once every 24 hours (nominal). Have you gone a full 24 hours?

gadgetfreak NEVER, NEVER, NEVER DELETE PLM!!!!! That is the latest hardware level. After the change to the new PLM, Tools | Diagnostics | PLM Info/Status will show PLM firmware. There is a recovery process if the PLM is Deleted but it requires current ISY Backup and is not always successful.

Along with the Program comments from larryllix the Motion Sensor has configuration options. The Motion Sensor is fine and produces motion messages based on how you have it configured. Suggest you post the current Motion Sensor options as not triggering on motion indicates it is in its Timeout countdown. The Motion Sensor does not send motion message while in Timeout. The Options can be configured to not have a Timeout.

For "If Status" to trigger a Program multiple times the Status must change to Off and then back to On. Multiple On commands in a row does NOT cause the Program to trigger on each On. "If Control" would trigger multiple times but not "If Status". Post the Program with If Status.

Any time guys. Happy to pass on that info.

Notes was added in 4.3.10 according to the announcement.

Sure. http://192.168.2.2/rest/nodes/33 95 41 1/notes <NodeProperties> <location>Location Bedroom</location> <description>Note text.</description> <isLoad>false</isLoad> <spoken/> </NodeProperties>

It lets you know the Hidden Door Sensor battery and device are functional. Some use the Hidden Door Sensor on a door where usage of door is important to know, particularly a door that is not opened/closed under normal circumstances. An example is the side door to my garage. It is rarely used and a door open is important to know. If battery drops to the point where the device is not operating Heartbeat (or lack of it) is important. Other doors it makes little difference.

Obtained 1st week of June 2015 Hardware REV 1.B Firmware V.43 Production Date 4614 I2CS No Jumper No "Options"

The PLM hardware is v2.0 That hardware level should not have capacitor failures.

That will not work on the new I2CS devices. They have link requirements the I1 and I2 devices do not have.

Since you chose to Delete and readd the Current State for Heartbeat is null unless the Set button was tapped. If Heartbeat is null the Leak Sensor can remain in its current location as the Heartbeat will change to On (or Off depending on firmware) when the first Heartbeat message is received.

GMD99 As Teken has described the Heartbeat message pattern varies by device hardware/firmware. There is usually a method to force a Heartbeat message but that DOES NOT verify the device will send a Heartbeat at the 24 hour mark. Locate the Leak Sensor near the PLM for 24+ hours. May not take that long but it could take 24 hours to receive the timed Heartbeat message. Be sure your Program is testing for both Heartbeat On and Heartbeat Off. This test Program will issue an X10 message if the Heartbeat is not received. Most users prefer to have a Notify if the Heartbeat is not received. Once it is confirmed the Heartbeat is being sent and the required link records exist in the Leak Sensor and PLM it can be moved to the desired location to see if Heartbeat is received from the new location. HeartBeat - [iD 0044][Parent 0001] If Control 'Leak Sensor-Heartbeat' is switched On Or Control 'Leak Sensor-Heartbeat' is switched Off Then Wait 25 hours Send X10 'A10/All Lights On (5)' Else - No Actions - (To add one, press 'Action') The fact that the Heartbeat node has Status means the device sent a Heartbeat message after the Leak Sensor was added to the ISY as the Status is null until some Heartbeat is received. Looking at the Heartbeat Current State field is not useful as some Leak Sensors send only one type command for the Heartbeat message. The Event Trace will show the Heartbeat message but the trace has to run the full 24 hours and you need to be familiar with Insteon traffic. Although it takes 24 hours the test Program is the easiest way to know if Heartbeat is received.

mcwxlsxn The Home Depot in South Hill, VA carries Kidde and First Alert smoke detectors. They are not located next to each other so you may need to look in another isle.

If it does not say ONELink it does not work with the Smoke Bridge.

After more thought using Momentary Mode and the I/O Linc Timeout is a better approach. It reduces the Insteon commands issued. Using a Timeout value of 1 second for example and a Wait of two seconds should produce a more reliable On time pattern. Then Set 'BuzzLinc-Relay' On Wait 2 second Set 'BuzzLinc-Relay' On Wait 2 second Set 'BuzzLinc-Relay' On ......

So the picture on the sales page does not match what you were shipped nor does what you received match the image on any of the sites that advertise ONELink devices. Do you have a HomeDepot retail store in driving range?

Unless the ISY is hundreds of miles away!

That is up to you as far as how the BuzzLinc sounds. When using the Repeat loop there is a delay associated with the Repeat action. That delay does not exist when you string the On/Off commands. I suspect a Wait would be useful but that depends on how long the BuzzLinc should remain On and how quickly the next On/Off sequence needs to occur to get the sound you want. Then Set 'BuzzLinc-Relay' On Wait 1 second Set 'BuzzLinc-Relay' Off Wait 1 second Set 'BuzzLinc-Relay' On

larryllix is using one of the I/O Linc Momentary modes and the I/O Linc Timeout to turn the I/O Linc Relay Off.

Program 1 must have existed and been Enabled at 8AM, otherwise the single opportunity for the Then clause to run will not happen until tomorrow.

Thanks Stu.

I cannot replicate your trace nor explain how it is happening. The I/O Linc Relay is turned On 5 times (in Red) without any Off commands being issued. Mon 08/10/2015 06:37:36 PM : [iNST-SRX ] 02 50 2C.71.97 11.01.01 CB 06 00 (00) Mon 08/10/2015 06:37:36 PM : [std-Group ] 2C.71.97-->11.01.01, Max Hops=3, Hops Left=2 Mon 08/10/2015 06:37:36 PM : [iNST-INFO ] Previous message ignored. Mon 08/10/2015 06:37:37 PM : [iNST-SRX ] 02 50 2C.71.97 11.01.01 CB 06 00 (00) Mon 08/10/2015 06:37:37 PM : [std-Group ] 2C.71.97-->11.01.01, Max Hops=3, Hops Left=2 Mon 08/10/2015 06:37:37 PM : [iNST-INFO ] Previous message ignored. Mon 08/10/2015 06:37:38 PM : [iNST-TX-I1 ] 02 62 31 6F 1C 0F 11 02 Mon 08/10/2015 06:37:38 PM : [D2D EVENT ] Event [2C 71 97 1] [sT] [255] uom=0 prec=-1 Mon 08/10/2015 06:37:38 PM : [ 2C 71 97 1] ST 255 Mon 08/10/2015 06:37:38 PM : [D2D-CMP 0012] STS [2C 71 97 1] ST op=1 Event(val=255 uom=0 prec=-1) is Condition(val=255 uom=0 prec=-1) --> true Mon 08/10/2015 06:37:38 PM : [iNST-ACK ] 02 62 31.6F.1C 0F 11 02 06 LTONRR (02) Mon 08/10/2015 06:37:38 PM : [iNST-TX-I1 ] 02 62 31 6F 1C 0F 11 02 Mon 08/10/2015 06:37:38 PM : [iNST-SRX ] 02 50 31.6F.1C 28.CC.6C 2B 11 02 LTONRR (02) Mon 08/10/2015 06:37:38 PM : [std-Direct Ack] 31.6F.1C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 08/10/2015 06:37:38 PM : [iNST-ACK ] 02 62 31.6F.1C 0F 11 02 06 LTONRR (02) Mon 08/10/2015 06:37:38 PM : [iNST-SRX ] 02 50 31.6F.1C 28.CC.6C 2B 11 02 LTONRR (02) Mon 08/10/2015 06:37:38 PM : [std-Direct Ack] 31.6F.1C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 08/10/2015 06:37:39 PM : [iNST-TX-I1 ] 02 62 31 6F 1C 0F 11 02 Mon 08/10/2015 06:37:39 PM : [iNST-ACK ] 02 62 31.6F.1C 0F 11 02 06 LTONRR (02) Mon 08/10/2015 06:37:39 PM : [iNST-SRX ] 02 50 31.6F.1C 28.CC.6C 2B 11 02 LTONRR (02) Mon 08/10/2015 06:37:39 PM : [std-Direct Ack] 31.6F.1C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 08/10/2015 06:37:40 PM : [iNST-TX-I1 ] 02 62 31 6F 1C 0F 11 02 Mon 08/10/2015 06:37:40 PM : [iNST-SRX ] 02 50 2C.71.97 00.00.01 C7 13 01 LTOFFRR(01) Mon 08/10/2015 06:37:40 PM : [std-Group ] 2C.71.97-->Group=1, Max Hops=3, Hops Left=1 Mon 08/10/2015 06:37:40 PM : [iNST-ACK ] 02 62 31.6F.1C 0F 11 02 06 LTONRR (02) Mon 08/10/2015 06:37:40 PM : [D2D EVENT ] Event [2C 71 97 1] [DOF] [1] uom=0 prec=-1 Mon 08/10/2015 06:37:40 PM : [ 2C 71 97 1] DOF 1 Mon 08/10/2015 06:37:40 PM : [D2D EVENT ] Event [2C 71 97 1] [sT] [0] uom=0 prec=-1 Mon 08/10/2015 06:37:40 PM : [ 2C 71 97 1] ST 0 Mon 08/10/2015 06:37:40 PM : [D2D-CMP 0012] STS [2C 71 97 1] ST op=1 Event(val=0 uom=0 prec=-1) is Condition(val=255 uom=0 prec=-1) --> false Mon 08/10/2015 06:37:40 PM : [iNST-SRX ] 02 50 31.6F.1C 28.CC.6C 2B 11 02 LTONRR (02) Mon 08/10/2015 06:37:40 PM : [std-Direct Ack] 31.6F.1C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 08/10/2015 06:37:40 PM : [iNST-SRX ] 02 50 2C.71.97 28.CC.6C 41 13 01 LTOFFRR(01) Mon 08/10/2015 06:37:40 PM : [std-Cleanup ] 2C.71.97-->ISY/PLM Group=1, Max Hops=1, Hops Left=0 Mon 08/10/2015 06:37:40 PM : [D2D EVENT ] Event [2C 71 97 1] [DOF] [0] uom=0 prec=-1 Mon 08/10/2015 06:37:40 PM : [ 2C 71 97 1] DOF 0 Mon 08/10/2015 06:37:41 PM : [iNST-SRX ] 02 50 2C.71.97 28.CC.6C 42 13 01 LTOFFRR(01) Mon 08/10/2015 06:37:41 PM : [std-Cleanup ] 2C.71.97-->ISY/PLM Group=1, Max Hops=2, Hops Left=0 Mon 08/10/2015 06:37:41 PM : [iNST-DUP ] Previous message ignored. Mon 08/10/2015 06:37:41 PM : [iNST-SRX ] 02 50 2C.71.97 13.01.01 C7 06 00 (00) Mon 08/10/2015 06:37:41 PM : [std-Group ] 2C.71.97-->13.01.01, Max Hops=3, Hops Left=1 Mon 08/10/2015 06:37:41 PM : [iNST-INFO ] Previous message ignored. Mon 08/10/2015 06:37:42 PM : [iNST-SRX ] 02 50 2C.71.97 13.01.01 C7 06 00 (00) Mon 08/10/2015 06:37:42 PM : [std-Group ] 2C.71.97-->13.01.01, Max Hops=3, Hops Left=1 Mon 08/10/2015 06:37:42 PM : [iNST-INFO ] Previous message ignored. Mon 08/10/2015 06:37:42 PM : [iNST-TX-I1 ] 02 62 31 6F 1C 0F 11 02 Mon 08/10/2015 06:37:42 PM : [iNST-ACK ] 02 62 31.6F.1C 0F 11 02 06 LTONRR (02) Mon 08/10/2015 06:37:42 PM : [iNST-SRX ] 02 50 31.6F.1C 28.CC.6C 2B 11 02 LTONRR (02) Mon 08/10/2015 06:37:42 PM : [std-Direct Ack] 31.6F.1C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

When using "If Control" the Else clause will be driven only at Sunrise (next day). I'm trying to recreate what your trace is showing. No success so far but several Options I want to try.