LeeG

I do not know what is in a SmartLinc 2412N but it cannot be transferred to an ISY. I think MobiLinc can control cameras but this is what I think, not what I know, and for sure no ISY function is used for camera control.

The Simplehomenet/Smartenit devices have been at their current firmware for several years. They have no plans to change how they work. The I/O Linc Relay reverses the command action based on On Level setting. With 0% On Level the Relay turns Off with an On command and turns On with an Off command. There is no absolute regarding how relays react across all relay devices.

My EZIO8SA Relays work the same. The On Level 0% has no affect. Separate Scenes for On and Off will be required.

The Adjust Scene statements posted adjust what happens when the Scene name is used in a Program or controlled from the Admin Console. To adjust the Local values both the In Scene and Set parameters have to specify the individual switch. Then In Scene 'switch1' Set 'switch1' 20% In Scene 'switch2' Set 'switch2' 20% Else In Scene 'switch1' Set 'switch1' 73% In Scene 'switch2' Set 'switch2' 73%

Can you post the Customizations tab with these messages? Can also open a Ticket and someone from UDI will help code the lines. Using xx yy zz without the node number etc cannot work and those options are simply confusing the actual variable requirement ${sys.node.E F5 1C 1.ST}

Which one is correct? 0E.5F.1C or sys.node.E F5 1C 1.ST

Also missing the node number sys.node.E F5 1C 1.ST See this link for the correct format viewtopic.php?f=68&t=14346&p=112009

Drop the leading 0 sys.node.E F5 1C.ST viewtopic.php?f=68&t=14346&p=112009

You running on an 99i? If so move to a 994i. If running a 994i move to a later ISY firmware.

philgood They would have signed an NDA to access that information. Some of Insteon itself is not documented to us mortals because we have not signed an NDA.

The earlier post only has the interpretation of an Insteon message without the actual Insteon message itself. To understand what the D2D EVENT lines indicate for example the Insteon message they are analyzing is needed. Below the DON is simply interpreting the ON command (11) code in the Insteon message. The Heat/Cool State (CLIHCS 2) indicates Cool State if my memory is correct. The various thermostat values (CLIHCS) can be found in this WIKI section. http://wiki.universal-devices.com/index ... _Variables The "uom=0 prec=-1" are new interpretations that UDI has recently added to the LEVEL 3 trace. I could guess that uom= is Unit of Measure maybe, the prec= is Precision maybe. These I have not seen any doc as to what they actually mean being they are new. There are new D2D CMP lines that interpret a Program trigger from the Insteon message Sat 04/26/2014 05:51:44 PM : [D2D-CMP 004F] CTL [11 B6 BC 1] DOF op=1 Event(val=1 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true Trying to evaluate the interpretations without the original Insteon message is difficult. The previous message is a Program trigger showing Program ID (004F), type of trigger (CTL = Control), etc. Without looking at the Program itself it is more difficult to evaluate what the information being presented actually means.l Sat 04/26/2014 12:21:15 PM : [iNST-SRX ] 02 50 1D.6C.D6 00.00.01 CB 11 00 LTONRR (00) Sat 04/26/2014 12:21:15 PM : [std-Group ] 1D.6C.D6-->Group=1, Max Hops=3, Hops Left=2 Sat 04/26/2014 12:21:15 PM : [D2D EVENT ] Event [1D 6C D6 2] [DON] [0] uom=0 prec=-1 Sat 04/26/2014 12:21:15 PM : [ 1D 6C D6 2] DON 0 Sat 04/26/2014 12:21:15 PM : [D2D EVENT ] Event [1D 6C D6 2] [sT] [255] uom=0 prec=-1 Sat 04/26/2014 12:21:15 PM : [ 1D 6C D6 2] ST 255 Sat 04/26/2014 12:21:15 PM : [D2D EVENT ] Event [1D 6C D6 1] [CLIHCS] [2] uom=0 prec=-1 Sat 04/26/2014 12:21:15 PM : [ 1D 6C D6 1] CLIHCS 2 To get an accurate evaluation of the D2D EVENTs the Insteon message that generated those messages would be helpful

Were the actual Insteon messages not included? UDI has added additional interpretation of each message, D2D for example, of the actual Insteon messages. Some day UDI may explain these additional messages. For now seeing the actual Insteon message from which these additional information messages were generated would be very helpful. Sat 04/26/2014 12:21:15 PM : [iNST-SRX ] 02 50 1D.6C.D6 00.00.01 CB 11 00 LTONRR (00) Sat 04/26/2014 12:21:15 PM : [std-Group ] 1D.6C.D6-->Group=1, Max Hops=3, Hops Left=2 Sat 04/26/2014 12:21:15 PM : [D2D EVENT ] Event [1D 6C D6 2] [DON] [0] uom=0 prec=-1 Sat 04/26/2014 12:21:15 PM : [ 1D 6C D6 2] DON 0 Sat 04/26/2014 12:21:15 PM : [D2D EVENT ] Event [1D 6C D6 2] [sT] [255] uom=0 prec=-1 Sat 04/26/2014 12:21:15 PM : [ 1D 6C D6 2] ST 255 Sat 04/26/2014 12:21:15 PM : [D2D EVENT ] Event [1D 6C D6 1] [CLIHCS] [2] uom=0 prec=-1 Sat 04/26/2014 12:21:15 PM : [ 1D 6C D6 1] CLIHCS 2 Sat 04/26/2014 12:21:16 PM : [iNST-SRX ] 02 50 1D.6C.D6 00.00.01 CB 11 00 LTONRR (00) Sat 04/26/2014 12:21:16 PM : [std-Group ] 1D.6C.D6-->Group=1, Max Hops=3, Hops Left=2 Sat 04/26/2014 12:21:16 PM : [D2D EVENT ] Event [1D 6C D6 2] [DON] [0] uom=0 prec=-1 Sat 04/26/2014 12:21:16 PM : [ 1D 6C D6 2] DON 0

Not as far as the EZIO8SA is concerned.

"Is it possible to decouple the LED light for Button A from the actual Dimmer?" No. What is the KeypadLinc firmware level? What ISY level is being used? I assigned a V.41 KPL button A as non-toggle On and Controller of a Scene using 4.2.1. The LED action of blinking twice and remaining On and the Event Viewer confirm it is in non-toggle On mode.

Setting up multiple environments to control the same devices is difficult at best. With today's I2CS devices they need to be linked to the PLM to do even basic On/Off operations. Linking devices to two PLMs and maintaining those links are difficult. I don't think the idea is practical.

Just in case the idea is lost, the cat 16, subcat 17 are decimal numbers. When looking at the New INSTEON Device list that is the same as [10.11] which are hex numbers; 0x10=16 decimal 0x11=17 decimal

I have not been able to get a single On/Off. The SynchroLinc is checking the current flow. The washer has too many On/Off cycles spread too far apart for a single On/Off.

I am one confused individual. I thought the issue was not able to add a SynchroLinc. The last trace (not the two that were just posted that I assume were some that were deleted) is not the SynchroLinc (19.8B.D3).

The SynchroLinc sent an Extended message in response to a Poke command. This is not valid and the ISY stopped the process. I went back to earlier posts to see if there is any correlation with other traces but found them deleted. Fri 04/18/2014 07:21:47 PM : [iNST-TX-I1 ] 02 62 19 8B D3 0F 29 01 Fri 04/18/2014 07:21:47 PM : [iNST-ACK ] 02 62 19.8B.D3 0F 29 01 06 POKE (01) Fri 04/18/2014 07:21:50 PM : [iNST-ERX ] 02 51 19 8B D3 22 FF 06 13 88 00 00 00 EB B3 00 00 00 00 00 00 00 00 00 00 Fri 04/18/2014 07:21:50 PM : [Ext-Direct ] 19.8B.D3-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Fri 04/18/2014 07:21:54 PM : [19 8B D3 1 ] Link 0 : 0FF8 [E20122FF06010001] *Failed Writing [E20122FF06010001] Fri 04/18/2014 07:21:54 PM : [ 19 8B D3 1] ERR 1 The Access Point has improved comm to the SynchroLinc. The earlier test where the PLM was put into the 4 tap Set button test showed the SynchroLinc is on the opposite 120v leg. The Access Point has removed one of the extra hops. Fri 04/18/2014 07:21:16 PM : [iNST-TX-I1 ] 02 62 19 8B D3 0F 28 0F Fri 04/18/2014 07:21:16 PM : [iNST-ACK ] 02 62 19.8B.D3 0F 28 0F 06 SET-MSB(0F) Fri 04/18/2014 07:21:17 PM : [iNST-SRX ] 02 50 19.8B.D3 22.FF.06 27 28 0F SET-MSB(0F) Fri 04/18/2014 07:21:17 PM : [std-Direct Ack] 19.8B.D3-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Fri 04/18/2014 07:21:17 PM : [iNST-TX-I1 ] 02 62 19 8B D3 0F 2B F8 Fri 04/18/2014 07:21:17 PM : [iNST-ACK ] 02 62 19.8B.D3 0F 2B F8 06 PEEK (F8) Fri 04/18/2014 07:21:17 PM : [iNST-SRX ] 02 50 19.8B.D3 22.FF.06 27 2B E2 PEEK (E2) Fri 04/18/2014 07:21:17 PM : [std-Direct Ack] 19.8B.D3-->ISY/PLM Group=0, Max Hops=3, Hops Left=1

The only thing I find is what is on the SynchroLinc sales page.

An ISY Program is necessary to turn KPL button B Off based on the On Level of the load being controlled by the SwitchLinc. if Status 'switch1' is not 50% Or Status 'switch2' is not 50% Then Set Scene 'xxxx' Off Else Your approach to the All Off is the solution.

The Insteon Direct On/Off commands do not have a placeholder to identify which KPL button should react. Sending an Direct On/Off command to a KPL turns the load control button and load On/Off.

A Scene is not defined as to what command will trigger the Scene. Not within Insteon capability. An ISY Program can be triggered with an Off command from a device and the Program issue an On command to the Scene. If Control 'devicex' is switched Off Then Set Scene xxxx On Else where Scene xxxx has the KPL button as a Responder

badman85283 There have been some upgrade programs since the 99i was frozen more than a year ago. Click the Buy tab on the UDI web site. Select Universal Devices, scroll to the bottom of the page for the 99i to 994i upgrade options. .

The Broadcast option will not resolve the missing state messages. The links that the ISY establishes will override that option. Either the PLM link database has become full such that the Responder link records could not be written into the PLM or the EZIO2X4 firmware is expecting the links in the EZIO2X4 to be written other than at 1FFF. For the PLM either look at the actual links in the PLM for the required Responder link records for the EZIO2X4 or simply do a File | Restore Modem (PLM) to reload the PLM link database. The Restore Modem takes a few minutes which is normally must faster than looking at all the PLM records. the Restore Modem (PLM) will compress out duplicate and no longer used link records. For the EZIO2X4 it is more difficult to verify where the device is expecting the link records. The easiest test is to Set button link a Controller to one of the EZIO2X4 relays. Then use the Show Device Links Table to see if that Set button link was added to the end of those written by the ISY. If not there than use the Show Device Links Table to display the link record at 0FF8. The EZIO2X4 firmware may have been reflashed to a level that expects the link records to start at 0FF8.