LeeG

At From time the Program is triggered with a True condition that could finally evaluate False based on other checks in the If. At To time the Program is triggered with a False condition that could finally evaluate True based on other checks in the If. In a simple example ..... If From 2:00 PM To 3:00 PM Then Else At 2 PM the Program is triggered as True running the Then clause At 3 PM the Program is triggered as False running the Else clause.

Your system was originally on a 99i, with 99i ISY Backup installed on a 994i ? The My Lighting name is ISY for a system built on the 994i (not built from 99i Backup). The original Set Scene 'ISY' Query could not be resolved with the My Lighting and is marked <Not Specified>

Another possibility ... If Time is 3:00:00AM Then Set Scene 'My Lighting' Query Else - No Actions - (To add one, press 'Action') This system originated from a 99i where the high level name is "My Lighting". I think Stu's system was built on a 994i which is why his is using 'ISY' rather than 'My Lighting'

What Browser is being used when incomplete activity is being Saved?

The Set statement in the Then clause does not identify an object.

Michaelco Would you provide the exact interaction that Save did not pick up.

These are the messages that should be seen under LEVEL 3. The Smoke Bridge LED will turn Red when the Set button is tapped and will blink Red as the messages are sent. Tue 12/02/2014 10:28:39 PM : [iNST-SRX ] 02 50 23.50.FD 00.00.01 CB 11 80 LTONRR (80) Tue 12/02/2014 10:28:39 PM : [std-Group ] 23.50.FD-->Group=1, Max Hops=3, Hops Left=2 Tue 12/02/2014 10:28:39 PM : [D2D EVENT ] Event [23 50 FD 1] [DON] [128] uom=0 prec=-1 Tue 12/02/2014 10:28:39 PM : [ 23 50 FD 1] DON 128 Tue 12/02/2014 10:28:39 PM : [D2D EVENT ] Event [23 50 FD 1] [sT] [255] uom=0 prec=-1 Tue 12/02/2014 10:28:39 PM : [ 23 50 FD 1] ST 255 Tue 12/02/2014 10:28:39 PM : [iNST-SRX ] 02 50 23.50.FD 11.00.01 CB 06 00 (00) Tue 12/02/2014 10:28:39 PM : [std-Group ] 23.50.FD-->11.00.01, Max Hops=3, Hops Left=2 Tue 12/02/2014 10:28:39 PM : [iNST-INFO ] Previous message ignored. Tue 12/02/2014 10:28:43 PM : [iNST-SRX ] 02 50 23.50.FD 00.00.02 CB 11 40 LTONRR (40) Tue 12/02/2014 10:28:43 PM : [std-Group ] 23.50.FD-->Group=2, Max Hops=3, Hops Left=2 Tue 12/02/2014 10:28:43 PM : [D2D EVENT ] Event [23 50 FD 2] [DON] [64] uom=0 prec=-1 Tue 12/02/2014 10:28:43 PM : [ 23 50 FD 2] DON 64 Tue 12/02/2014 10:28:43 PM : [D2D EVENT ] Event [23 50 FD 2] [sT] [255] uom=0 prec=-1 Tue 12/02/2014 10:28:43 PM : [ 23 50 FD 2] ST 255 Tue 12/02/2014 10:28:43 PM : [iNST-SRX ] 02 50 23.50.FD 11.00.02 CB 06 00 (00) Tue 12/02/2014 10:28:43 PM : [std-Group ] 23.50.FD-->11.00.02, Max Hops=3, Hops Left=2 Tue 12/02/2014 10:28:43 PM : [iNST-INFO ] Previous message ignored. Tue 12/02/2014 10:28:48 PM : [iNST-SRX ] 02 50 23.50.FD 00.00.06 CB 11 10 LTONRR (10) Tue 12/02/2014 10:28:48 PM : [std-Group ] 23.50.FD-->Group=6, Max Hops=3, Hops Left=2 Tue 12/02/2014 10:28:48 PM : [D2D EVENT ] Event [23 50 FD 6] [DON] [16] uom=0 prec=-1 Tue 12/02/2014 10:28:48 PM : [ 23 50 FD 6] DON 16 Tue 12/02/2014 10:28:48 PM : [iNST-SRX ] 02 50 23.50.FD 11.00.06 CB 06 00 (00) Tue 12/02/2014 10:28:48 PM : [std-Group ] 23.50.FD-->11.00.06, Max Hops=3, Hops Left=2 Tue 12/02/2014 10:28:48 PM : [iNST-INFO ] Previous message ignored. Tue 12/02/2014 10:28:53 PM : [iNST-SRX ] 02 50 23.50.FD 00.00.07 CB 11 08 LTONRR (08) Tue 12/02/2014 10:28:53 PM : [std-Group ] 23.50.FD-->Group=7, Max Hops=3, Hops Left=2 Tue 12/02/2014 10:28:53 PM : [D2D EVENT ] Event [23 50 FD 7] [DON] [8] uom=0 prec=-1 Tue 12/02/2014 10:28:53 PM : [ 23 50 FD 7] DON 8 Tue 12/02/2014 10:28:53 PM : [iNST-SRX ] 02 50 23.50.FD 11.00.07 CB 06 00 (00) Tue 12/02/2014 10:28:53 PM : [std-Group ] 23.50.FD-->11.00.07, Max Hops=3, Hops Left=2 Tue 12/02/2014 10:28:53 PM : [iNST-INFO ] Previous message ignored. Tue 12/02/2014 10:28:58 PM : [iNST-SRX ] 02 50 23.50.FD 00.00.05 CB 11 00 LTONRR (00) Tue 12/02/2014 10:28:58 PM : [std-Group ] 23.50.FD-->Group=5, Max Hops=3, Hops Left=2 Tue 12/02/2014 10:28:58 PM : [D2D EVENT ] Event [23 50 FD 5] [DON] [0] uom=0 prec=-1 Tue 12/02/2014 10:28:58 PM : [ 23 50 FD 5] DON 0 Tue 12/02/2014 10:28:58 PM : [D2D EVENT ] Event [23 50 FD 1] [sT] [0] uom=0 prec=-1 Tue 12/02/2014 10:28:58 PM : [ 23 50 FD 1] ST 0 Tue 12/02/2014 10:28:58 PM : [D2D EVENT ] Event [23 50 FD 2] [sT] [0] uom=0 prec=-1 Tue 12/02/2014 10:28:58 PM : [ 23 50 FD 2] ST 0 Tue 12/02/2014 10:28:58 PM : [iNST-SRX ] 02 50 23.50.FD 11.00.05 CB 06 00 (00) Tue 12/02/2014 10:28:58 PM : [std-Group ] 23.50.FD-->11.00.05, Max Hops=3, Hops Left=2 Tue 12/02/2014 10:28:58 PM : [iNST-INFO ] Previous message ignored.

Normal for the test button on the actual sensor. Tap the Set button on the Smoke Bridge. That will generate 5 test messages, for Smoke, CO, and three other nodes. Initially Smoke and CO will be On. When the last test message is sent Smoke and CO will be Off. Watch the Event Viewer at LEVEL 3 to see the 5 test messages.

The Wait and Repeat statements allow the If clause to be reevaluated should a trigger condition change. If From Sunset To Sunrise (next day) And Status '19.5C.D1-Sensor' is On Then Set Scene 'Garage' 100% Wait 5 minutes Set Scene 'Garage' Off Else - No Actions - (To add one, press 'Action')

I have seen event traces where a duplicate Query response with a low Hops Left value comes back late, falling into the next Query command sequence. It gave the appearance of a node state that was not true. I looked for this case yesterday in my collection of trace files but could not find an old trace with this circumstance. The trace was posted by the user but did not find it in the forum either. It is rare and requires an event trace of the actual situation to confirm. This is very rare so it may not have anything to do with this thread.

When a Wait or Repeat statement is executed the If clause can run again when any of the trigger conditions change. For the statements after the Wait not to execute it means a trigger condition changed while inthe Wait causing the If to execute again with a False result causing the Else clause to execute.

Small nit ... This should be Set Scene 'ROG_KPL_A' Off

dba62 You will miss Heartbeat messages as well as Wet condition messages until comm (Max Hops=3, Hops Left=varying to 0) with the remote location is improved.

Is the Trigger Reverse option set for the I/O Linc? If so the Sensor state will change with 3AM Query because Trigger Reverse does not reverse the Query result.

Not as good. The fact that the Hops Left=x is changing is indicative of lower comm quality Sun 11/30/2014 10:58:06 AM : [iNST-SRX ] 02 50 2E.14.DF 00.00.02 C7 11 02 LTONRR (02) Sun 11/30/2014 10:58:06 AM : [std-Group ] 2E.14.DF-->Group=2, Max Hops=3, Hops Left=1 Sun 11/30/2014 10:58:06 AM : [D2D EVENT ] Event [2E 14 DF 2] [DON] [2] uom=0 prec=-1 Sun 11/30/2014 10:58:06 AM : [ 2E 14 DF 2] DON 2 Sun 11/30/2014 10:58:06 AM : [D2D EVENT ] Event [2E 14 DF 2] [sT] [255] uom=0 prec=-1 Sun 11/30/2014 10:58:06 AM : [ 2E 14 DF 2] ST 255 Sun 11/30/2014 10:58:06 AM : [D2D EVENT ] Event [2E 14 DF 1] [sT] [0] uom=0 prec=-1 Sun 11/30/2014 10:58:06 AM : [ 2E 14 DF 1] ST 0 Sun 11/30/2014 10:58:06 AM : [iNST-SRX ] 02 50 2E.14.DF 00.00.02 CB 11 02 LTONRR (02) Sun 11/30/2014 10:58:06 AM : [std-Group ] 2E.14.DF-->Group=2, Max Hops=3, Hops Left=2 Sun 11/30/2014 10:59:26 AM : [iNST-SRX ] 02 50 28.54.F7 11.01.01 C3 06 00 (00) Sun 11/30/2014 10:59:26 AM : [std-Group ] 28.54.F7-->11.01.01, Max Hops=3, Hops Left=0 Sun 11/30/2014 10:59:26 AM : [iNST-INFO ] Previous message ignored. Sun 11/30/2014 10:59:27 AM : [iNST-SRX ] 02 50 28.54.F7 11.01.01 C7 06 00 (00) Sun 11/30/2014 10:59:27 AM : [std-Group ] 28.54.F7-->11.01.01, Max Hops=3, Hops Left=1

The Hub and the PLM are different devices. It sounds like the Hub has better reception than the PLM. Look for the differences, sources of noise or signal attenuation between the two devices. The PLM should be plugged directly into an outlet with nothing else (not filtered) that can be reducing the Insteon signal on the same circuit.

The Group=4 indicates the Heartbeat message. The combination of Max Hops=3, Hops Left=2 is the indicator of comm quality. Hops Left=2 is as good as it gets. Sun 11/30/2014 08:53:53 AM : [iNST-SRX ] 02 50 28.54.F7 00.00.04 CB 11 04 LTONRR (04) Sun 11/30/2014 08:53:53 AM : [std-Group ] 28.54.F7-->Group=4, Max Hops=3, Hops Left=2

Thanks for the additional data. It looks as it should, the Heartbeat message is there with good comm. When you move two to their remote location try the Set button tap again to see how comm is at the final location. Sun 11/30/2014 08:53:53 AM : [iNST-SRX ] 02 50 28.54.F7 00.00.04 CB 11 04 LTONRR (04) Sun 11/30/2014 08:53:53 AM : [std-Group ] 28.54.F7-->Group=4, Max Hops=3, Hops Left=2 Sun 11/30/2014 08:53:53 AM : [D2D EVENT ] Event [28 54 F7 4] [DON] [4] uom=0 prec=-1 Sun 11/30/2014 08:53:53 AM : [ 28 54 F7 4] DON 4 Sun 11/30/2014 08:53:53 AM : [D2D EVENT ] Event [28 54 F7 1] [sT] [255] uom=0 prec=-1 Sun 11/30/2014 08:53:53 AM : [ 28 54 F7 1] ST 255

I take it you are now running a 99i. There are various devices 3.3.10 does not support. Replacing a KPL with a current KPL is not supported. That normally does not crash the 3.3.10 Admin Console but the KPL will not add. What does Help | About show for Firmware and UI levels? What devices are being replaced?

The next test is have the Event Viewer at LEVEL 3 as before. Tap the Leak Sensor Set button to generate a Dry On or Wet On followed by a Heartbeat message 15-20 seconds later. Post the event trace.

Device 2E.14.DF Leak Sensor with firmware v.41 added successfully with the best comm possible. Could not be any better comm.

There are some additional items to look into. It is not possible to have multiple Leak Sensor failures. Are there other wireless devices (not Insteon) in use such as a wireless baby sitter or some other source for RF activity? Unless the PLM RF has failed which is unlikely the Leak Sensor should have no trouble talking to the PLM a few feet away. I'm hoping there is something else that is using RF which is interfering with Leak Sensor to PLM comm.

Thanks. That means the only RF battery devices are the Leak Sensors. Could mean there is not reliable RF coverage for some reason. I would move to 4.2.18. It has always been stable and is now the latest Official release. Use Help | About to confirm both Firmware and UI indicate 4.2.18. Run Tools | Diagnostics | Event Viewer at LEVEL 3. Use New INSTEON Device. Enter a Leak Sensor address, use Name of choice, and Auto Discover. Before clicking Ok put Leak Sensor into manual linking mode and have it near the 2413 PLM, then click Ok. Post the event trace when New INSTEON Device completes.

Are there other battery powered RF only devices in use (Motion Sensor, TriggerLinc, Mini Remote, etc)?

UDI is working on a PLM, estimated to be available in 1st Qtr 2015.