LeeG

Run Tools | Diagnostics | Event Viewer at Level 3. Run the various scenarios with the event trace running. It will show the commands executed. Any time the Fade Stop is not issued immediately after the Fade Up/Down (with appropriate Wait in between) it leaves the device exposed.

Another option. When pressing the KPL button that turns Off an Off command is sent to responders which could be an inconvenience even though the ISY Program will put things back. The two KPL buttons can be put into non-toggle On mode. The buttons will always issue an On command no matter how many times the button is pressed. A KPL button in non-toggle mode blinks twice when pressed as in indication it is in one of the non-toggle modes. The other button LED will still turn Off as a result of the Responder On Level of 0%.

It sounds like the Scene name Responder On Levels are not set as needed. When using the Scene name in a Program the PLM is the Controller which has a unique set of Responder On Levels, separate from button press Responder On Levels. Click the ISY Scene Name and check the Responder On Levels

Thanks for the additional information. Fade Up/Down should be paired with a Fade Stop. Otherwise the Fade function is left half done with unpredictable results. When a button/paddle is pressed and held the device sends a Start Manual Change command, either Up or Down, to the Responders. The functional equivalent in an ISY Program is Fade Up or Fade Down. When the button/paddle is released a Stop Manual Change command is sent to the Responders. The functional equivalent in an ISY Program is Fade Stop. There are no exceptions. When a device initiates a Fade Up/Down operation it is always terminated with a Fade Stop. An ISY Program must follow the requirement and issue a Fade Stop at the end of a Fade Up/Down. What happens at a device if the Fade Stop is not issued varies from type to type. That is an exception condition, not documented or committed as to result.

The two options use the same underlying function in the device which is why the newer Scene approach is recommended. Do not use Button Grouping. Define an ISY Scene, specify button X as the Controller and button Y as a Responder with a 0% On Level. Define another ISY Scene, specify button Y as the Controller and button X as a Responder with 0% On Level. Be sure to select the button node name below the Scene name when setting the Responder On Level to 0%.

Is the DIM command being used or Fade Down command?

ISY Programming can do that. Something like setting an ISY Variable to 5 with the initial button On press. Each subsequent On button press would add 5 to the ISY Variable. Another Program would decrement the ISY Variable by 1 for each minute the Program runs. When the ISY Variable reaches zero the Zone is turned Off. Only one EZFlora Zone can be on at a time.

Such as do something if the On button is pressed 3 times within 5 seconds, something like that, sure that can be done. Insteon will treat multiple button presses done very close together as a Fast On rather than a simple On so there are some caveats. Can you expand on what the counting of button clicks is to accomplish.

The I/O Linc Relay is a Responder Only node. It does not send state changes back to ISY. I don't think you want Relay follows Sensor as the Relay will turn Off when the Sensor turns Off (it is following Sensor). Use Latching mode and turn the Relay On from an ISY Program when the I/O Linc Sensor turns On. The Relay will remain On until explicitly turned Off when in Latching mode.

You need to be on the latest 3.3.3 beta.

The alarm condition can be noted in an ISY Variable. The I/O Linc Relay operating in Latching Mode can be turned On when the I/O Linc Sensor sends an On command to the ISY if an Insteon device indication is preferred. A dedicated LampLinc or ApplianceLinc or Secondary KeypadLinc button can be used. Really need more information on how the alarm condition needs to be remembered by the ISY.

The email timing is as expected. The next On command comes after the 1 minute Motion Sensor Timeout interval. Either the Motion Sensor Timeout value has to be increased or the Program logic adjusted to not send an email while in the 4 minute Wait.

Is Sensing Mode option checked or unchecked. If Sensing Mode is On the Motion Sensor sends On commands for every motion detected. If not Sensing Mode the Motion Sensor sends On commands only after timeout interval has expired. How long between Motion On messages?

The current temperature is a value that can be checked just like the Bright level of a Dimmer. A set of ISY Programs could adjust the FanLinc Motor On Level for various ambient temperature ranges. The FanLinc cannot reverse the Fan direction.

The Folder Condition looks incorrect when evaluating the current state of the various elements. However, the $iAway element was the last to change its value. The Integer Variable value of 0 makes the Condition True but based on Timestamp it was the last element to change. Being an Integer Variable it would not have triggered the Folder to change the True/False state even though looking at the values in their static state the Folder would evaluate to True if it did trigger.

Use New INSTEON Device, enter Insteon address of RemoteLinc and Name of your choice. Leave Device Type set to Auto Discover. Press Dim/Bright buttons together until RemoteLinc LED blinks continuously. Click Ok on New INSTEON Device popup. Be sure RemoteLinc is in good RF range of a Dual Band device.

The Else clause should not turn the light On. Anytime the Elk zones are violated outside the desired time range the else clause runs turning the light On.

Thanks for the last trace. It is of a Start Linking sequence that did not check for the Insteon Engine so it does not know it is an I2CS device. All the Peek/Poke commands fail to function because the I2CS firmware does not contain Peek/Poke. I don't know what UI (Admin Console) is being used but it is not 3.2.6. I don’t see how Help | About can be displaying Firmware and UI as 3.2.6.

Take a look at page 1 of this topic. It was easy to identify I2CS devices back in April because many folks were not yet on an ISY level that had I2CS support. Now just about everyone is on an ISY level that supports I2CS so as new device types are being released by SmartLabs they go unnoticed. Eventually the Dimmer types will be switched to I2CS which may explain the 2486D. viewtopic.php?f=30&t=8434&hilit=partial+list+i2cs

Insteon has no concept of Scene status. MobiLinc must be looking at the individual status of all the devices in the Scene. I know that MobiLinc will drive a Scene rather than an individual device when the device that is clicked is a Controller of a Scene. That type of logic is relegated to 3rd party applications. The Admin Console is showing more basic Insteon information.

The Elk zone is not staying violated. During the Wait the zone changes state causing the Program If section to be reevaluated to False driving the Else clause so statement(s) after the Wait are not executed.

Except for two 2486d devices which I cannot explain, the others are Relay devices which have been shipping with I2CS firmware. SmartLabs started with the Relay types and some others (like thermostats) for update to the I2CS protocol. The Dimmer types have been trailing the conversion process.

flemingmike The Show PLM Links Table and subsequent Count has to be done multiple times to see if the number is reproducible. Any Insteon traffic reaching the PLM during the Show will cause the count to be artificially high or low depending on where the link is that matches in the inbound traffic versus how far the Show has progressed.

I think it would help if you posted the Scene detail. For each ISY Scene, what are the Controllers, what are the Responders and what does each show. As far as the EZX10RF each node is a Controller only node. It reflects the last command received from that node. The same for RemoteLinc and RemoteLinc2 buttons, the nodes are Controller only nodes. They reflect the last command received from each node.

To achieve the effect, ANDing the time range with either of the other conditions, add the parens as follows If { Elk Zone 'Front Door' is Violated Or Elk Zone 'Garage Entry Dr' is Violated } And From Sunset To Sunrise (next day) Then Set 'Insteon Bulb' Fast On Wait 2 minutes Set 'Insteon Bulb' Fast Off Else - No Actions - (To add one, press 'Action') There is an order of precedence which is described in the Wiki EDIT: The original Program without parens is the same as coding If Elk Zone 'Front Door' is Violated Or { Elk Zone 'Garage Entry Dr' is Violated And From Sunset To Sunrise (next day) } Then Set 'Insteon Bulb' Fast On Wait 2 minutes Set 'Insteon Bulb' Fast Off Else - No Actions - (To add one, press 'Action')