Jump to content

Please help with adjust scene.


EricK

Recommended Posts

I am trying to set up an adjust scene so some lights are on at night for the dog.  Does not seem to be working.  I have two members in the program, I think the switchlinc, v.38, controls the load, but it is the KPL button that I push at night to set the scene on.  There is another KPL with a spots button that is in the scene, but not used.

GR Spots adjust scene - [ID 00D7][Parent 0028]

If
        From     9:00:00PM
        To      Sunrise +  9 seconds (next day)
 
Then
        In Scene 'Great Room / Great Room Scenes / GR Spots' Set 'Great Room / Great Room Devices / GR Spots' 31% (On Level)
        In Scene 'Great Room / Great Room Scenes / GR Spots' Set 'Great Room / Great Room Devices / GR Spots KPL (DB) - A Spots' 31% (On Level)
 
Else
        In Scene 'Great Room / Great Room Scenes / GR Spots' Set 'Great Room / Great Room Devices / GR Spots' 100% (On Level)
        In Scene 'Great Room / Great Room Scenes / GR Spots' Set 'Great Room / Great Room Devices / GR Spots KPL (DB) - A Spots' 100% (On Level)
 

Thanks,

E

Link to comment

OK.  So the controller is the KPL button and the responder is the switchlinc.  Your program is close, but it should look more like (changes in red):

 

If
From 9:00:00PM
To Sunrise + 9 seconds (next day)

Then
In Scene 'Great Room / Great Room Scenes / KPL Button' Set 'Great Room / Great Room Devices / switchlinc' 31% (On Level)

Else
In Scene 'Great Room / Great Room Scenes / KPL Button' Set 'Great Room / Great Room Devices / switchlinc' 100% (On Level)

 

For each controller/responder, one must have a "set scene" line.  Since you only have one keypad button you use to control the switchlinc, you should need only a single line in each action.

Link to comment

There is nothing to activate the scene in your program, only light level adjustments. I assume the scenes contain the SwitchLinc and KPL buttons as controllers in the scenes.

 

What doesn't work?

Yes, both are controllers in the scene. I don't have or want a timer to activate the scene since bedtime varies from night to night. What doesn't work is that when I hit the lol at night the lights go to 100% on.

 

OK. So the controller is the KPL button and the responder is the switchlinc. Your program is close, but it should look more like (changes in red):

 

If

From 9:00:00PM

To Sunrise + 9 seconds (next day)

 

Then

In Scene 'Great Room / Great Room Scenes / KPL Button' Set 'Great Room / Great Room Devices / switchlinc' 31% (On Level)

 

Else

In Scene 'Great Room / Great Room Scenes / KPL Button' Set 'Great Room / Great Room Devices / switchlinc' 100% (On Level)

 

For each controller/responder, one must have a "set scene" line. Since you only have one keypad button you use to control the switchlinc, you should need only a single line in each action.

OK.  So the controller is the KPL button and the responder is the switchlinc.  Your program is close, but it should look more like (changes in red): IfFrom 9:00:00PMTo Sunrise + 9 seconds (next day)ThenIn Scene 'Great Room / Great Room Scenes / KPL Button' Set 'Great Room / Great Room Devices / switchlinc' 31% (On Level)ElseIn Scene 'Great Room / Great Room Scenes / KPL Button' Set 'Great Room / Great Room Devices / switchlinc' 100% (On Level) For each controller/responder, one must have a "set scene" line.  Since you only have one keypad button you use to control the switchlinc, you should need only a single line in each action.

Thanks I will give that a try
Link to comment

Oberkc,

It is the KPL that controls the load, 8 button v.43, so an older KPL. Here is the program, will have to wait until tonight to see if this works.

GR Spots adjust scene - [ID 00D7][Parent 0028]

If
        From     9:00:00PM
        To      Sunrise +  9 seconds (next day)
 
Then
        In Scene 'Great Room / Great Room Scenes / GR Spots' Set 'Great Room / Great Room Devices / GR Spots KPL (DB) - A Spots' 31% (On Level)
 
Else
        In Scene 'Great Room / Great Room Scenes / GR Spots' Set 'Great Room / Great Room Devices / GR Spots KPL (DB) - A Spots' 100% (On Level)
 

Or do I want to do this which I think you are suggesting. This involves selecting the device in the first part of the adjust scene, not the scene.

GR Spots adjust scene Copy - [ID 00DB][Parent 0028][Not Enabled]

If
        From     9:00:00PM
        To      Sunrise +  9 seconds (next day)
 
Then
        In Scene 'Great Room / Great Room Devices / GR Spots KPL (DB) - A Spots' Set 'Great Room / Great Room Devices / GR Spots KPL (DB) - A Spots' 31% (On Level)
 
Else
        In Scene 'Great Room / Great Room Devices / GR Spots KPL (DB) - A Spots' Set 'Great Room / Great Room Devices / GR Spots KPL (DB) - A Spots' 100% (On Level)
 

Thanks,

E

Link to comment

"It is the KPL that controls the load​"

 

I thought you said the switchlinc controls the load? (I am also having trouble keeping track of which names are which device.  Is it the same KPL that you press that also controls the load?

 

In general, if you want a responder device ON level to change in response to a given controller, the statement would be something like:

 

In Scene 'controller' Set 'responder' 31% (On Level)

 

Of course, pick the devices from the drop-down menu and the names will auto populate.  For each controller/responder pair, you will need such a statement, since responder levels can be unique for each controller.

Link to comment

 

In general, if you want a responder device ON level to change in response to a given controller, the statement would be something like:

 

In Scene 'controller' Set 'responder' 31% (On Level)

 

So I think what you're looking for is something like this:

 

GR Spots adjust scene - [ID 00D7][Parent 0028]

 

If

From 9:00:00PM

To Sunrise + 9 seconds (next day)

 

Then

In Scene 'Great Room / Great Room Devices / GR Spots KPL (DB) - A Spots' Set 'Great Room / Great Room Devices / GR Spots' 31% (On Level)

 

Else

In Scene 'Great Room / Great Room Devices / GR Spots KPL (DB) - A Spots' Set 'Great Room / Great Room Devices / GR Spots' 100% (On Level)

Link to comment

Oberkc, the kpl and switchlinc replaced a physical 3 way set up so I forgotten which controlled the load. I have a great room folder, then sub folders for great room devices and great room scenes to keep the admin console organized.

 

I think the confusing thing for me is in the first drop down box you select a device, not a scene. Not sure why it is called adjust scene since you are not selecting a scene.

 

Zerop, I think your program is what I listed as my second program above. I have that one in the admin console disabled. Will switch to that one.

 

Thanks guys.

Link to comment

...

 

I think the confusing thing for me is in the first drop down box you select a device, not a scene. Not sure why it is called adjust scene since you are not selecting a scene.

 

....

Definitely confusing and others don't like it but where else could you put it?

Link to comment

The first parameter is always the Controller.   If using the ISY Scene name in a Program the first parameter would be the ISY Scene name which is actually identifying the PLM as the Controller.  Nothing is actually changed in the Controller (first parameter).  The first parameter establishes the Controller (PLM or Controller device name) which identifies the Controller Insteon address in the Responder device link record.  It is a Responder link record in the Responder device that is being modified by each Adjust Scene statement.

 

The second parameter identifies the Responder device.  This provides the Insteon address of the Responder device so Adjust Scene statement knows which device Responder link table to modify.

 

It is key to know which device is the load control device.  The Controller device (first parameter) can be the same as Responder device (second parameter) if they are the same device.

 

The KPL button is the Controller.  If the KPL is also physically controlling the load (Red wire of KPL is connected to load) then the KPL is also the Responder and would also be used in the second parameter.  If the SwitchLinc is physically controlling the load (Red wire of SwitchLinc is connected to load) the SwitchLinc is the Responder and would be used as the second parameter.

 

No magic here, first parameter is always the Controller and the second parameter is always the Responder.  With both pieces of information the Adjust Scene statement knows the Insteon address of the Responder (physical location of link record table being modified) and the Insteon address of the Controller device so which link record in the Responder to modify is known.

 

Without accurately specifying the Controller name and Responder name (could be the same device) the Adjust Scene statement will be modifying the wrong Responder link record.  Really need to know whether the Red wire of the KPL or the Red wire of the SwitchLinc is connected to the load.  Without that information the Adjust Scene statement will not work.  

 

 

Example: KPL Button A Controller: 11.11.11 Group 01;  SwitchLinc Responder: 22.22.22

 

In Scene 'KPL - Button A' Set 'SwitchLinc'  31% (On Level)

 

SwitchLinc Link Table - 22.22.22 - 2nd parameter of Adjust Scene statement

 

A2 01 11.11.11 4F 1F 01

 

 

A2 - Responder link record

01 - Group number of Responder

11.11.11 - Insteon address of Controller - 1st parameter of Adjust Scene statement

4F - 31% On Level - 3rd parameter of Adjust Scene statement

1F - 0.1 second Ramp Rate

01 - Group number of KPL button A - 1st parameter of Adjust Scene 

 

Information in Red comes from Adjust Scene statement

 

 

 

Link to comment

I think the confusing thing for me is in the first drop down box you select a device, not a scene. Not sure why it is called

I understand and don't disagree. Perhaps, rather than thinking about it as "in scene", perhaps better words would be " for scene controller"

Link to comment

In this definition there are three Insteon Scenes involved.  

 

ISY Scene xxxx

KPL Button A

SwitchLinc 

 

'xxxx' represents the first Insteon Scene (also an ISY Scene).

'KPL Button A' represents the second Insteon Scene

'SwitchLinc' represents the third Insteon Scene 

 

As far as Insteon is concerned there are three Scenes, each of which is functional and independent of the others.  Each Scene has its own Controller and set of Responders.  The Adjust Scene statement is altering one Responder value in one Responder..

 

If it turns out the KPL Red wire is connected to the load, then additional Adjust Scene statements are required.

 

Then

    In Scene 'KPL Button A'  Set 'KPL Button A' 31% (On Level)

    In Scene 'KPL Button A'  Set 'SwitchLinc' 31% (On Level)  

Else

    In Scene 'KPL Button A'  Set 'KPL Button A' 100% (On Level)

    In Scene 'KPL Button A'  Set 'SwitchLinc' 100% (On Level)   

 

The first Adjust Scene statement in each clause sets the load On Level

The second Adjust Scene statement in each clause sets the On Level for the left side LED bar in SwitchLinc

 

 

If the SwitchLinc Red wire is connected to the load a single Adjust Scene statement in each clause is all that is needed because KPL Button A has no external load level indicator 

 

Then

    In Scene 'KPL Button A'  Set 'SwitchLinc' 31% (On Level)  

Else

    In Scene 'KPL Button A'  Set 'SwitchLinc' 100% (On Level)   

Link to comment

Lee,

I installed these devices 5 years ago and bought an ISY two years ago so I could not remember which was the load controller. The other day I pulled the air gap on the switchlinc to confirm it is the kpl that is wired to the load.

Thank you for explaining this. I will edit my program tonight if I have time and test this out.

Eric

Link to comment

In this definition there are three Insteon Scenes involved.  

 

ISY Scene xxxx

KPL Button A

SwitchLinc 

 

'xxxx' represents the first Insteon Scene (also an ISY Scene).

'KPL Button A' represents the second Insteon Scene

'SwitchLinc' represents the third Insteon Scene 

 

As far as Insteon is concerned there are three Scenes, each of which is functional and independent of the others.  Each Scene has its own Controller and set of Responders.  The Adjust Scene statement is altering one Responder value in one Responder..

 

If it turns out the KPL Red wire is connected to the load, then additional Adjust Scene statements are required.

 

Then

    In Scene 'KPL Button A'  Set 'KPL Button A' 31% (On Level)

    In Scene 'KPL Button A'  Set 'SwitchLinc' 31% (On Level)  

Else

    In Scene 'KPL Button A'  Set 'KPL Button A' 100% (On Level)

    In Scene 'KPL Button A'  Set 'SwitchLinc' 100% (On Level)   

 

The first Adjust Scene statement in each clause sets the load On Level

The second Adjust Scene statement in each clause sets the On Level for the left side LED bar in SwitchLinc 

To me, it looks like I have this programmed correctly, but last night it did not work.  I put a strikethru the folder structure names to make it a bit less confusing.  Can you guys look at this one more time.  Thanks.

GR Spots adjust scene Copy - [ID 00DB][Parent 0028]

If
        From     9:00:00PM
        To      Sunrise +  9 seconds (next day)
 
Then
        In Scene 'Great Room / Great Room Devices / GR Spots KPL (DB) - A Spots' Set 'Great Room / Great Room Devices / GR Spots KPL (DB) - A Spots' 31% (On Level)
        In Scene 'Great Room / Great Room Devices / GR Spots KPL (DB) - A Spots' Set 'Great Room / Great Room Devices / GR Spots' 31% (On Level)
 
Else
        In Scene 'Great Room / Great Room Devices / GR Spots KPL (DB) - A Spots' Set 'Great Room / Great Room Devices / GR Spots KPL (DB) - A Spots' 100% (On Level)
        In Scene 'Great Room / Great Room Devices / GR Spots KPL (DB) - A Spots' Set 'Great Room / Great Room Devices / GR Spots' 100% (On Level)
 

Link to comment

Please identify

 

'Great Room / Great Room Devices / GR Spots KPL (DB) - A Spots'

 

'Great Room / Great Room Devices / GR Spots'

 

Does the Program | Summary show 'GR Spots adjust scene Copy'  ran at 9 PM

 

What happened when KPL button pressed?

 

 

Suggest running Tools | Diagnostics | Event Viewer at LEVEL 3.

 

Right click on GR Spots adjust scene Copy, select Run Then

 

Turn On KPL button

 

Post event trace.

Link to comment
  • 2 weeks later...

Sorry for not getting back to this, but between work and switching out my PLM, I put this on the back burner.

Please identify

'Great Room / Great Room Devices / GR Spots KPL (DB) - A Spots'  - This is the device that is directly connected to the load.

 

'Great Room / Great Room Devices / GR Spots' - This is a secondary device that is not connected to the load.  Was in a physical 3-way before the prior owner replaced with X10.

 

Suggest running Tools | Diagnostics | Event Viewer at LEVEL 3.

 

Right click on GR Spots adjust scene Copy, select Run Then

 

Turn On KPL button

Sun 11/15/2015 09:44:01 AM : [        Time] 09:44:02 0(0)
Sun 11/15/2015 09:44:01 AM : [16 CE 8E 1  ] Link   16 : 0F78 [A201291AFE4F1A01] Saving  [..........4F....]
Sun 11/15/2015 09:44:01 AM : [D2D EVENT   ] Event [29 1A FE 1] [OL] [79] uom=0 prec=-1
Sun 11/15/2015 09:44:01 AM : [  29 1A FE 1]       OL  79
Sun 11/15/2015 09:44:01 AM : [All         ] Writing 3 bytes to devices
Sun 11/15/2015 09:44:02 AM : [16 CE 8E 1  ] Link   16 : 0F78 [A201291AFE4F1A01] Writing [..........4F....]
Sun 11/15/2015 09:44:02 AM : [INST-TX-I1  ] 02 62 16 CE 8E 0F 28 0F
Sun 11/15/2015 09:44:02 AM : [INST-ACK    ] 02 62 16.CE.8E 0F 28 0F 06          SET-MSB(0F)
Sun 11/15/2015 09:44:02 AM : [INST-SRX    ] 02 50 16.CE.8E 3B.97.32 27 28 0F    SET-MSB(0F)
Sun 11/15/2015 09:44:02 AM : [Std-Direct Ack] 16.CE.8E-->ISY/PLM Group=0, Max Hops=3, Hops Left=1
Sun 11/15/2015 09:44:02 AM : [INST-TX-I1  ] 02 62 16 CE 8E 0F 2B 7D
Sun 11/15/2015 09:44:02 AM : [INST-ACK    ] 02 62 16.CE.8E 0F 2B 7D 06          PEEK   (7D)
Sun 11/15/2015 09:44:02 AM : [INST-SRX    ] 02 50 16.CE.8E 3B.97.32 2B 2B FF    PEEK   (FF)
Sun 11/15/2015 09:44:02 AM : [Std-Direct Ack] 16.CE.8E-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Sun 11/15/2015 09:44:02 AM : [INST-TX-I1  ] 02 62 16 CE 8E 0F 29 4F
Sun 11/15/2015 09:44:02 AM : [INST-ACK    ] 02 62 16.CE.8E 0F 29 4F 06          POKE   (4F)
Sun 11/15/2015 09:44:03 AM : [INST-SRX    ] 02 50 16.CE.8E 3B.97.32 2B 29 4F    POKE   (4F)
Sun 11/15/2015 09:44:03 AM : [Std-Direct Ack] 16.CE.8E-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Sun 11/15/2015 09:44:03 AM : [INST-TX-I2CS] 02 62 29 1A FE 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0
Sun 11/15/2015 09:44:03 AM : [INST-ACK    ] 02 62 29.1A.FE 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06        (00)
Sun 11/15/2015 09:44:03 AM : [INST-SRX    ] 02 50 29.1A.FE 3B.97.32 2F 2F 00           (00)
Sun 11/15/2015 09:44:03 AM : [Std-Direct Ack] 29.1A.FE-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
Sun 11/15/2015 09:44:04 AM : [INST-ERX    ] 02 51 29 1A FE 3B 97 32 15 2F 00 00 01 0F FF 20 A2 40 3B 97 32 00 1F 08 95 
Sun 11/15/2015 09:44:04 AM : [Ext-Direct  ] 29.1A.FE-->ISY/PLM Group=0, Max Hops=1, Hops Left=1
Sun 11/15/2015 09:44:04 AM : [29 1A FE 1  ] Memory : Write dbAddr=0x0032 [4F] cmd1=0x2E cmd2=0x00
Sun 11/15/2015 09:44:04 AM : [INST-TX-I2CS] 02 62 29 1A FE 1F 2E 00 01 06 4F 00 00 00 00 00 00 00 00 00 00 7C
Sun 11/15/2015 09:44:04 AM : [INST-ACK    ] 02 62 29.1A.FE 1F 2E 00 01 06 4F 00 00 00 00 00 00 00 00 00 00 7C 06        (00)
Sun 11/15/2015 09:44:04 AM : [INST-SRX    ] 02 50 29.1A.FE 3B.97.32 2F 2E 00           (00)
Sun 11/15/2015 09:44:04 AM : [Std-Direct Ack] 29.1A.FE-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
Sun 11/15/2015 09:44:04 AM : [INST-TX-I1  ] 02 62 29 1A FE 0F 24 00
Sun 11/15/2015 09:44:04 AM : [INST-ACK    ] 02 62 29.1A.FE 0F 24 00 06                 (00)
Sun 11/15/2015 09:44:05 AM : [INST-SRX    ] 02 50 29.1A.FE 3B.97.32 2F 24 00           (00)
Sun 11/15/2015 09:44:05 AM : [Std-Direct Ack] 29.1A.FE-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
Sun 11/15/2015 09:44:05 AM : [29 1A FE 1  ] Memory : EPROM Refreshed
Sun 11/15/2015 09:44:05 AM : [All         ] Writing 0 bytes to devices
Sun 11/15/2015 09:44:23 AM : [INST-SRX    ] 02 50 29.1A.FE 00.00.01 CF 11 00    LTONRR (00)
Sun 11/15/2015 09:44:23 AM : [Std-Group   ] 29.1A.FE-->Group=1, Max Hops=3, Hops Left=3
Sun 11/15/2015 09:44:23 AM : [D2D EVENT   ] Event [29 1A FE 1] [DON] [0] uom=0 prec=-1
Sun 11/15/2015 09:44:23 AM : [  29 1A FE 1]      DON   0
Sun 11/15/2015 09:44:23 AM : [D2D EVENT   ] Event [22 97 D5 6] [ST] [255] uom=0 prec=-1
Sun 11/15/2015 09:44:23 AM : [  22 97 D5 6]       ST 255
Sun 11/15/2015 09:44:23 AM : [D2D EVENT   ] Event [3B 8C 78 6] [ST] [255] uom=0 prec=-1
Sun 11/15/2015 09:44:23 AM : [  3B 8C 78 6]       ST 255
Sun 11/15/2015 09:44:23 AM : [D2D EVENT   ] Event [16 CE 8E 1] [ST] [79] uom=0 prec=-1
Sun 11/15/2015 09:44:23 AM : [  16 CE 8E 1]       ST  79
Sun 11/15/2015 09:44:23 AM : [D2D EVENT   ] Event [29 1A FE 1] [ST] [79] uom=0 prec=-1
Sun 11/15/2015 09:44:23 AM : [  29 1A FE 1]       ST  79
Sun 11/15/2015 09:44:23 AM : [D2D-CMP 00D1] STS [29 1A FE 1] ST op=6 Event(val=79 uom=0 prec=-1) != Condition(val=0 uom=0 prec=-1) --> true
Sun 11/15/2015 09:44:23 AM : [D2D-CMP 007D] STS [29 1A FE 1] ST op=1 Event(val=79 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> false
Sun 11/15/2015 09:44:23 AM : [D2D-CMP 007C] STS [29 1A FE 1] ST op=1 Event(val=79 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> false
Sun 11/15/2015 09:44:23 AM : [D2D-CMP 0038] STS [29 1A FE 1] ST op=6 Event(val=79 uom=0 prec=-1) != Condition(val=0 uom=0 prec=-1) --> true
Sun 11/15/2015 09:44:23 AM : [D2D-CMP 0035] STS [29 1A FE 1] ST op=6 Event(val=79 uom=0 prec=-1) != Condition(val=0 uom=0 prec=-1) --> true
Sun 11/15/2015 09:44:23 AM : [INST-SRX    ] 02 50 29.1A.FE 3B.97.32 46 11 01    LTONRR (01)
Sun 11/15/2015 09:44:23 AM : [Std-Cleanup ] 29.1A.FE-->ISY/PLM Group=1, Max Hops=2, Hops Left=1
Sun 11/15/2015 09:44:23 AM : [INST-DUP    ] Previous message ignored.

Thanks,

Eric

Link to comment
  • 2 months later...

Regarding the original issue, I really recommend changing the wording as described by oberkc:

 

I understand and don't disagree. Perhaps, rather than thinking about it as "in scene", perhaps better words would be " for scene controller"

 

I just ran across this as well, and the wording "In scene", coupled with a dropdown list that includes a bunch of scenes, really leads a new user in the wrong direction (to pick a scene).  Is there any situation where it's appropriate to select a scene from that dropdown box?  If not, it would be a lot more user-friendly to change the wording to "for scene controller" and only list scene controllers.

 

I understand why it doesn't make sense to choose a scene there, but it's definitely not intuitive the way it is now.

 

Rob

Link to comment

There actually is no difference from Insteon perspective as an Insteon Scene is specified.  In this example

 

ISY Scene xxxx

Device1 - Controller

Device2 - Controller

Device3 - Responder

 

There are three Insteon Scenes.  

 

Scene xxxx (PLM is Controller) represents Insteon Scene 1.   

Device1 is a Controller of Insteon Scene 2

Device2 is a Controller of Insteon Scene 3.

 

The Adjust Scene action requires an Insteon Scene Controller in the first parameter (In Scene).  This parameter provides the Insteon address of the Scene Controller.  This Insteon address identifies the link record in the Responder device being changed by the Adjust Scene statement.  The second parameter identifies the Scene Responder device that contains the link database being adjusted.

 

In Scene 'Device1' Set 'Device3' 50% (On Level)

 

In Scene 'xxxx' Set 'Device3' 20% (On Level)

 

 

It makes more sense when the Insteon technology is understood and that three Scenes are actually defined. 

Link to comment

I think I understand.  So choosing an ISY scene as the first parameter changes the response when you set/trigger an ISY scene manually from the ISY or through a program. Choosing a device as the first parameter changes the response when a scene is triggered from that device (like flipping a switch, motion sensor detects motion, etc.), or when you send a command directly to the device from the ISY.  All correct?

 

I still feel like a wording change would make it more obvious.  Maybe changing the prompt to "For scene controller" and naming the ISY scenes "PLM - <scene name>", where it's clearer that you're always choosing a device/scene controller, even when you choose <scene name>.  That's really where it threw me off - it's clear that the devices in the list are scene controllers (non-controllers are actually excluded), but the "device" aspect of the scene entries wasn't as clear.

 

Thanks for the quick response - I think I get it now.

 

Rob

Link to comment

"or when you send a command directly to the device from the ISY.  All correct?"

 

Very good.  Your understanding is correct on all aspects except for the last point.  Sending a command to a device, either through the Admin Console buttons or a Set 'devicex' On, is sending an Insteon Direct command (rather than a Scene command) which does not use link records.

 

Insteon is not complex when evaluating the actual Insteon command involved.  Feel free to post addition questions as they come up.  Also looking at the insteon.com developer information can be helpful.  Even if the specific question/answer is not found useful information about Insteon workings is often found. 

Link to comment

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...