LeeG

SetMonkey13 Is this an ISY Scene that was defined with the RemoteLinc2 added as a Controller or manual Set button links established before adding the RemoteLinc2 to the ISY as a device. If an ISY Scene it should be listed at the bottom of the My Lighting tree after the device definitions. If these were manual links perhaps they were eliminated when adding the RemoteLinc2 using the default (and preferred) "erase existing links" option. Lee

Okay, thanks, I think I've got the picture. When the Red Button A entry below the Scene name is selected and the KPL load button ON is set to 85% Then the Red Button B entry below the Scene name is selected and the KPL load button ON is set to 5% Then the Red Button C entry below the Scene name is selected and the KPL load button ON is set to 5% Then select some other entry in the My Lighting tree Then select the Red Button A below the Scene name and the KPL load button ON is no longer set to 85% Is that accurate? What ISY firmware level is being used? I set that Scene up and Button A, Button B and Button B Controller entries maintain the set On level for KPL load control button on 3.1.13. When the On Level slider is moved to some level does a Progress Bar appear and green arrow Icons appear to the left of the KPL nodes?

matapan There is some use of terms that is causing a little confusion on my part. Local Scene Settings - not sure what this means. Button 1,2,3 - these are secondary buttons on the KeypadLinc? An ISY Scene actually consists of multiple Insteon Scenes so it is best to take this to the Insteon Scene level. Each Insteon Scene has 1 Controller which I think is one of the Secondary KeypadLinc buttons (A,B,C,D) . Button1 is Secondary KeypadLinc Button A,B,C,D ?(which one for a single example) is a Controller. KeypadLinc ON button is a Responder ApplianceLinc is a Responder LampLinc is a Responder When Button 1 is selected each Responder has a unique Responder On Level and Ramp Rate which is associated with Button 1 being pressed. Do not know what Local Scene Settings term means in relation to the this. When Secondary Button 1 is pressed ON the defined Responder On Levels go into effect. When a different Secondary Button2 is pressed ON the defined Responder On Levels for that button go into effect. If Secondary button 1 is pressed again it generates an OFF which should turn its Responders OFF. When Secondary Button 1 is pressed ON again, what happens? It would be helpful to use the actual KeypadLinc Secondary button nomenclature A,B,C,D and explain what is meant by Local Scene Settings. Is there any Button Grouping involved? Lee

dkaleita There is no Scene status. Although each device must be included in the If there is only one Program needed. If Status 'ICON Dimmer 1' is Off And Status 'ICON Relay 1' is Off And Status 'KeypadLinc Relay' is Off And Status 'SwitchLinc Dimmer' is Off Then Set Scene 'KPLButton' Off Else - No Actions - (To add one, press 'Action') Lee

apostolakisl If you can post the Event Viewer trace from a beep operation it will be easier to evaluate. No one has found a device that utilizes the beep duration. It appears to be one of those Insteon interface values that may eventually be used by some device but so far none do. The beep function itself is generic but only a few devices have implemented beep in any form. There is often function described in the command spec's that take time to show up in an actual device. In what is sometimes described as Insteon 1 (I1) there is an entire collection of Extended commands that no device ever implemented. Lee EDIT: what is the switch device type and the firmware level in the device

matapan Is it the result in the folder example the Program with the null If does not trigger? Lee ' EDIT: the above is really asking to define the difference observed. Folder conditions allow Programs in the folder to run as opposed to triggering Programs to run. This may not have any relevance to the difference of interest.

The Event Viewer provides the definitive information. The LTON-F (On-Fast) annotation by the ISY will indicate when a Fast On is received or look for a 0x12 command. RemoteLinc buttons can be difficult to double tap. Maybe watching the event viewer trace as the button is double tapped. It will show how fast the button must be double tapped for the RemoteLinc to generate a Fast xxx command. ToggleLincs are also difficult to generate a double tap Fast xxx because of the mechanics of the toggle.

Great documentation, thanks. The RemoteLinc is not sending a Fast On or Fast Off, The Fast On command is 0x12 and a Fast Off is 0x14. The following are examples of a Fast On followed by a Fast Off from my RemoteLinc. Thu 12/08/2011 11:13:35 AM : [iNST-SRX ] 02 50 11.AD.CF 00.00.02 CB 12 00 LTON-F (00) Thu 12/08/2011 11:13:35 AM : [standard-Group][11.AD.CF-->Group=2] Max Hops=3, Hops Left=2 Thu 12/08/2011 11:13:35 AM : [ 11 AD CF 2] DFON 0 Thu 12/08/2011 11:13:35 AM : [iNST-SRX ] 02 50 11.AD.CF 00.00.02 CB 12 00 LTON-F (00) Thu 12/08/2011 11:13:36 AM : [standard-Group][11.AD.CF-->Group=2] Max Hops=3, Hops Left=2 Thu 12/08/2011 11:13:36 AM : Duplicate: ignored Thu 12/08/2011 11:13:36 AM : [iNST-SRX ] 02 50 11.AD.CF 00.00.02 CB 12 00 LTON-F (00): Process Message: failed Thu 12/08/2011 11:13:36 AM : [standard-Group][11.AD.CF-->Group=2] Max Hops=3, Hops Left=2 Thu 12/08/2011 11:13:36 AM : [iNST-SRX ] 02 50 11.AD.CF 19.70.15 41 12 02 LTON-F (02) Thu 12/08/2011 11:13:36 AM : [standard-Cleanup][11.AD.CF-->ISY/PLM Group=2] Max Hops=1, Hops Left=0 Thu 12/08/2011 11:13:40 AM : [iNST-SRX ] 02 50 11.AD.CF 00.00.02 CB 14 00 LTOFF-F(00) Thu 12/08/2011 11:13:40 AM : [standard-Group][11.AD.CF-->Group=2] Max Hops=3, Hops Left=2 Thu 12/08/2011 11:13:40 AM : [ 11 AD CF 2] DFOF 0 Thu 12/08/2011 11:13:40 AM : [ 11 AD CF 2] ST 0 Thu 12/08/2011 11:13:40 AM : [iNST-SRX ] 02 50 11.AD.CF 00.00.02 CB 14 00 LTOFF-F(00) Thu 12/08/2011 11:13:40 AM : [standard-Group][11.AD.CF-->Group=2] Max Hops=3, Hops Left=2 Thu 12/08/2011 11:13:40 AM : Duplicate: ignored Thu 12/08/2011 11:13:40 AM : [iNST-SRX ] 02 50 11.AD.CF 00.00.02 CB 14 00 LTOFF-F(00): Process Message: failed Thu 12/08/2011 11:13:40 AM : [standard-Group][11.AD.CF-->Group=2] Max Hops=3, Hops Left=2 Thu 12/08/2011 11:13:41 AM : [iNST-SRX ] 02 50 11.AD.CF 19.70.15 41 14 02 LTOFF-F(02) Thu 12/08/2011 11:13:41 AM : [standard-Cleanup][11.AD.CF-->ISY/PLM Group=2] Max Hops=1, Hops Left=0 Looking at your event log all the commands are 0x11 On and 0x13 Off.

Thanks. Run Tools | Diagnostics | Event Viewer with Device communications events selected. When the Program does not respond to a double tap (Fast On) post that part of the event trace. The RemoteLinc may not be sending a Fast xxx command. Also if you can post the Program I will set up that same Program here and try to recreate with the same definition.

bocarob Can you provide some more detail. Linked responders not reacting, Program not triggering, etc. I am not able to recreate not seeing Fast On/Off from my RemoteLinc. Lee

killervette For those of us who came from a programming background it is a little strange but there are uses for such behavior in an event driven environment. State variables, Insteon Status work the same way. The reevaluation applies to the Repeat function as well as the Wait function. The Wiki has a good explanation of how all these things interact. Lee

killervette When statements after a Wait do not execute it means the If condition has changed before the Wait expires with the resulting reevaluation to False so the Else clause runs. Check the Status column which will likely indicate False for that last run condition. Have this Program Run another Program which contains all the current Then statements and nothing in the If clause. The second Program will not reevaluate so the statements after the Wait will execute. Lee

Rmlinnovator Regarding the cross-linking define an ISY Scene adding both KeypadLinc Secondary buttons as Controllers of the ISY Scene. ISY assumes a Controller is also a Responder and will cross-cross link the buttons so the button LEDs stay in Scene. I prefer Scenes over Programs as there is no latency (very small delay) associated with the ISY receiving a command, invoking a Program which issues an Action. The ISY Scene that is cross-linking the KeypadLinc buttons can have whatever devices you want to turn Off as Responders to the same Scene. In addition the KeypadLinc buttons should be put into non-toggle Off mode so the button only turns devices Off. Otherwise turning the KeypadLinc button On will turn all the responders On (unless that is what you want). If a Program (rather than adding the devices as responders to the Scene) is used different Actions could be assigned to the ON versus OFF. OFF could turn all the devices OFF and perform a tstat setback. The ON could turn On some devices and change the tstat to a normal temp. The KeypadLinc buttons would not be placed in non-toggle mode for this implementation. With the ISY there are lots of choices. Not sure about the tstat setback. Do not have one so I don’t know if that can be part of the same Scene. I’m sure others will jump in here. Lee

There should be a line immediately below the Firmware line that contains the UI (Admin Console) level. If that line is not there either the Java cache was not cleared or the URL to access the 3.1.13 Admin Console is not being used.

What does Help | About show for Firmware and UI?

Yes, that is correct.

You can select Link Management | New INSTEON Device and click on the Device Type pulldown. Scroll through the list of [01.xx] entries. Should find an [01.21] entry. The Cancel button on the New INSTEON Device popup can be used to cancel without actually adding a device. Just a means of verifying there is an entry there. I have that entry on my 3.1.13.

Scroll down the Device Type pulldown list and look for [01.21] (2472D) Dual Band OutletLinc Dimmer The list is not in absolute order but it should be in the 01.xx list. The [01.21] is a hex number which is 1.33 in decimal which is what the unsupported message displays. If that is not in the list be sure Help | About is showing 3.1.13 for the UI level.

Each zone has a maximum run time. Set the maximum zone run time to a value greater than the longest run time for the zone. The EZFlora will shut Off the zone if max zone run time is reached.

That device is supported in 3.1.13. What ISY firmware is being used?

After the unsupported it will show numbers; 1.40 for example, which is the cat/subcat of the device. What is the number of the unsupported OutletLinc? edit: The 2473SWH is not a Dual Band device. Is it possible they are something else?

SteveSBE The RemoteLinc buttons cannot be turned On Programmatically. The RemoteLinc has no Responder capability and is likely asleep (although maybe not asleep in this scenario). Suggest running Tools | Diagnostics | Event Viewer with Device communications events selected. Post the event log when Scene A turns On unexpectedly. I suspect there is a Scene A On coming from the RemoteLinc. Lee

Teken Have you actually tried the Beep under HL. The Beep duration has no affect on other devices which makes me think HL is simply repeating a Beep command multiple times if it actually does sound a longer Beep. Lee

In addition to good information apostolakisl already provided, when a device is added to the ISY all links necessary for the ISY to be aware of device state changes are automatically established. Device to Device control is established separately by defining ISY Scenes, adding the respective devices to the Scenes as either Controllers (which are assumed to also be Responders) or Responders. Once defined the ISY writes all the necessary link records (cross-linking). Set button links should not be done. There are a few exceptions but they are spelled out when needed.

tdmarra There is no mechanism to trigger on a communications error. The 170001 messages are informational, generated when the event viewer as been started with Device communications events selected. Can you post an example of the 100. Lee