LeeG

Were any manual Set button links established before using ISY Scenes? Were the Motion Sensors put into linking mode one at a time when the Scenes were deleted so the links could be deleted from the Motion Sensors?

"and the lights till go out after 1 minutes even though the program tells it to wait 15." That is normally the result of having linked the Motion Sensor as Controller and the lights as Responder(s). The Motion Sensor times out after 1 minute and turns the lights Off because it is a Controller of the Scene. Could have another Program being triggered that shuts the lights Off in 1 minute but it sounds more like the Motion Sensor is still acting as a Controller. Was the Motion Sensor ever manually linked to the lights, perhaps before you started using ISY Scenes? Resetting the PLM is not an action that should affect the Motion Sensor functioning as a Controller of a Scene. If the Motion Sensor was linked manually to the lights then the Motion Sensor and the lights should be factory reset followed by a Restore Device to each device. If the Motion Sensor was added to an ISY Scene it should be deleted from the ISY Scene.

Variables are signed 32 bit integers, no strings. See this link viewtopic.php?f=68&t=6063 Q1 and Q2 - No, not the way you mean.

It normally will. A KeypadLinc button is like any other Responder. Make sure the specific RemoteLinc button is in the list of Controller link records in the RemoteLinc and the KeypadLinc has the equivalent Responder link record. Can also be the KeypadLinc cannot be reached from the Dual Band device receiving the RemoteLinc RF. The RemoteLinc needs E2 xx yy.yy.yy zz zz zz where xx is 01 through 06 for the RemoteLinc button number. yy.yy.yy is the KeypadLinc Insteon address. zz zz zz does not matter. The KeypadLinc needs A2 aa bb.bb.bb cc dd ee where aa is the same value as xx in the RemoteLinc. bb.bb.bb is the RemoteLinc Insteon address. cc should be FF, dd would normally be 1F, ee is the KPL button number.

What level ISY firmware is in use? I created the situation you describe and neither Motion Sensor has a Responder link record. Neither Motion Sensor would be reacting to the others motion message. Also neither Motion Sensor LED blinks when motion is sensed. .

The EZFlora has no internal clock. It does not run its internal programs without being directed to do so. Seems like you will need Insteon Mesh Network access through a PLM to run the EZFlora programs if the assumption is the ISY is not in the picture. With Insteon Mesh Network capability as part of your package it would not be that much more to update the EZFlora programs or drive the Valves/Zones directly as the ISY does.

You're welcome. Thanks for taking the time to post back the results.

It sounds like the RemoteLinc has lost it link records. The Insteon manual bright/dim functions are not dependent on link records in the RemoteLinc. Put the RemoteLinc into manual linking mode, right click RemoteLinc Primary node and select Restore Device. That will rebuild the RemoteLinc link database. If the batteries are old replace the batteries before doing the Restore Device.

One of the Status conditions being checked is changing state before the Wait expires. The Wait and Repeat statements can be interrupted by a change in Status the If is checking. The solution is what you implemented, put the Wait in the second Program where it will not be interrupted. The UDI Wiki covers the operation of the Wait and Repeat and that they can be interrupted. It is always good to post the actual Program. Right click the Program name, select Copy to Clipboard. You have already confirmed the problem and solution by using two Programs.

Look for a Green Icon to the left of the nodes involved with the Scene. These indicate pending writes which indicate the link record(s) were not deleted. The Motion Sensor has to be put into manual linking mode for it to be awake so the ISY can update the link database. There is a Show Device Links Table function that displays the link records in a device is you want to visually verify they are deleted.

"Is it that I setup the lights in a Scene... because before I setup any type of program, it would turn them on or off." If the Scene has the Motion Sensor as a Controller and the lights as Responder that is the problem. Delete the Scene as it is turning the lights Off independent of what the Program is doing.

In this sample If Status 'xxxx' is On And Status 'yyyy' is On And Status 'zzzz' is On Then some action Else some action a change in Status of 'xxxx' or 'yyyy' or 'zzzz' with trigger the Program (cause it to execute). The entire If is evaluated when the Program is triggered. When all three devices are On the Then clause runs. When any of the three devices is not On the Else clause runs. Any of the If statements can make the Program run. Note that not every statement that can be placed in the If section will trigger the Program. A test of an Integer variable will affect the True/False evaluation but will not trigger the Program. Once triggered the If is evaluated top down as one would read the If section to evaluate True/False

Compound If statements are not required for the Else clause to execute. A simple single If statement can cause the Else to executed. Neither the Then nor Else clause run all the time. Something in the If section causes the Program to be triggered. For example, If Status 'xxxxx' is On. When the Status of 'xxxxx' changes the Program is triggered (executed). When the If statement is True, in this case Status is On, the Then clause runs. When the If statement is False, in this case Status is other than On, the Else clause runs. Everything is event driven, Status has to change for the Program to be triggered (executed). Once the Program is triggered the If evaluation determines which clause, Then or Else, is executed. The answer to the specific question, yes, when Motion is triggered outside the time range the Else clause executes because the If is False. Also at the specific From and To times the Program is triggered. The If example is missing either Status or Control so the results of the If, True or False, cannot be accurately stated. At the To time the If will be False because it is later, albeit by milli seconds, past the time range.

That means the router does not support (or is not enabled) for UPnP. It is best to define port forwarding since access established with UPnP will be lost if the router reboots. See page 1 of this topic.

You posted the same question twice. Look at your other post. I answered the original question in your other post with the same question. Here is the link to your other post with the same question viewtopic.php?f=26&t=12381

Make sure the Admin Console is showing the expected Status in the Current State column for the I/O Linc Sensor. Make sure the Program does not have a Save pending. Check the Programs | Summary tab. Is the Program being triggered at all (Last Run Time)? Select the Program name, select Copy to Clipboard and post Program.

Duplicate. See other post.

Assuming the KeypadLinc button is a Secondary button define a ISY Scene with the Secondary KPL button as a Responder. The ISY Program turns the Scene Off when the I/O Linc Sensor is On and turns the Scene On when the Sensor is Off If Status 'io Linc sensor' is On Then Set Scene xxxx Off Else Set Scene xxxx On

The ISY does not support the management of native EZFlora programs. Although anything is possible I would not expect that capability to be added to the ISY since the same type of Valve/Zone sequencing can be accomplished with ISY Programs.

That can be a problem with Fast On/Off. It is sensitive to the speed of the double tap. With the event viewer running at LEVEL 3 so the actual command sent can be verified try a slightly slower or slightly faster double tap. The tendency can be too fast on the double tap. The second tap needs to be immediate but not necessarily rapid. It can take a little practice to get the speed right. The event viewer is the only way to know for sure what command the device is issuing. The device is coming up to 100% because that is what it should do with a second tap if a Fast On is not generated. First tap brings the device to Local On Level, second tap brings it to 100%. Visually it looks like a double tap Fast On/Off but the device is taking it as two single taps.

bsobel I find the sequence easier to understand if ORed together (just the way my mind works) but both AND and OR produce the same results If ( Control 'SwitchLinc DB Dimmer v40' is switched Fast On And Control 'SwitchLinc DB Dimmer v40' is not switched Fast Off ) Produces the same result as If ( Control 'SwitchLinc DB Dimmer v40' is switched Fast On Or Control 'SwitchLinc DB Dimmer v40' is not switched Fast Off )

bsobel With If Control only one command is possible at a time. With the following If the first line is True when a Fast On is created and the second line is True when a Fast On is created because of "not switched Fast Off". See the event trace I posted above which shows the Then is executed with a Fast On and the Else is executed with a Fast Off. If ( Control 'SwitchLinc DB Dimmer v40' is switched Fast On And Control 'SwitchLinc DB Dimmer v40' is not switched Fast Off )

I added Actions to the Then (X10 A1/On) and Else (X10 A1/Off) clauses. This is what the event trace should look like. Thu 09/26/2013 09:02:24 PM : [iNST-SRX ] 02 50 1D.38.00 00.00.01 CB 12 00 LTON-F (00) Thu 09/26/2013 09:02:24 PM : [std-Group ] 1D.38.00-->Group=1, Max Hops=3, Hops Left=2 Thu 09/26/2013 09:02:24 PM : [ 1D 38 0 1] DFON 0 Thu 09/26/2013 09:02:24 PM : [ 1D 38 0 1] ST 255 Thu 09/26/2013 09:02:24 PM : [X10-RSP ] 02 63 66 00 06 Thu 09/26/2013 09:02:24 PM : [ 20 29 9C 1] ST 255 Thu 09/26/2013 09:02:24 PM : [ X10] A1 Thu 09/26/2013 09:02:24 PM : [ X10] A1/On (3) Thu 09/26/2013 09:02:25 PM : [iNST-SRX ] 02 50 1D.38.00 22.80.0B 4B 12 01 LTON-F (01) Thu 09/26/2013 09:02:25 PM : [std-Cleanup ] 1D.38.00-->ISY/PLM Group=1, Max Hops=3, Hops Left=2 Thu 09/26/2013 09:02:25 PM : [iNST-DUP ] Previous message ignored. Thu 09/26/2013 09:02:57 PM : [iNST-SRX ] 02 50 1D.38.00 00.00.01 CB 14 00 LTOFF-F(00) Thu 09/26/2013 09:02:57 PM : [std-Group ] 1D.38.00-->Group=1, Max Hops=3, Hops Left=2 Thu 09/26/2013 09:02:57 PM : [ 1D 38 0 1] DFOF 0 Thu 09/26/2013 09:02:57 PM : [ 1D 38 0 1] ST 0 Thu 09/26/2013 09:02:57 PM : [X10-RSP ] 02 63 66 00 06 Thu 09/26/2013 09:02:57 PM : [ 20 29 9C 1] ST 0 Thu 09/26/2013 09:02:57 PM : [ X10] A1 Thu 09/26/2013 09:02:57 PM : [ X10] A1/Off (11) Thu 09/26/2013 09:02:58 PM : [iNST-SRX ] 02 50 1D.38.00 22.80.0B 4B 14 01 LTOFF-F(01) Thu 09/26/2013 09:02:58 PM : [std-Cleanup ] 1D.38.00-->ISY/PLM Group=1, Max Hops=3, Hops Left=2 Thu 09/26/2013 09:02:58 PM : [iNST-DUP ] Previous message ignored.

This Program is triggered True when a Fast On is created and triggered False when a Fast Off is created. Suggest checking to be sure a program save is not pending, the program is Enabled, not in a Folder that has a False status. If ( Control 'SwitchLinc DB Dimmer v40' is switched Fast On And Control 'SwitchLinc DB Dimmer v40' is not switched Fast Off ) Or ( Control 'SwitchLinc Relay' is switched Fast On And Control 'SwitchLinc Relay' is not switched Fast Off ) Then Send X10 'A1/On (3)' Else Send X10 'A1/Off (11)' - No Actions - (To add one, press 'Action') If nothing obvious is found run Tools | Diagnostics | Event Viewer at LEVEL 3. Create the double tap and confirm the event trace actually shows a Fast On command.

Set the KeypadLinc button to non-toggle On mode. Add the various devices as Responders to an ISY Scene that has the KeypadLinc button as Controller of the Scene. Set the devices that should turn Off to a 0% On Level. Set the devices that should turn On to whatever On Level each device should turn On. Both sets of On Levels are defined when the KeypadLinc button node name below the Scene name is selected. Each time the KPL button is pressed the devices will react to the defined On Levels.