Jump to content

2nd time New User - Programming Help Please


jamesrm

Recommended Posts

Hello,

  I had a small setup 3 years ago at a residence. Recently, I purchased a 4,000 foot finished (with 2,000 additional feet unfinished) home and have replaced nearly 100 switches and outlets with insteon products. I also have quite a few hidden door links, motion detectors, leak detectors, and have the garage door kits installed on several doors (using the walk through here)...

 

  I am trying to create the following programs and need some help:

 

1) I would like button 8 on my 8 button keypad links to be illuminated if any of the interior lights are on. I would like a button press WHEN the light is illuminated (so an interior light is on, somewhere) to turn off all the lights OR trigger a leaving script, which turns off the lights that are on and turns on a few lights for a limited duration. I had something like this before, but I forgot how to properly code that.

 

2) I read somewhere that double clicks can be used to toggle scenes. I have a kitchen scene that turns on all the lights to ON. But, it would be nice to use the same keypadlinc button to maybe toggle to a more dim scene. How do I do this?

 

3) I have an exterior scene with my outside lights that is also on a program to run a little after sunset until a bit before sunrise. I previously had made it that anytime a exterior light was manually turned off, the scene turned the light back on. How do I set that code up? It would be cool if a double toggle would over ride the scene, or another event could over ride it, but normally I would want that scene on at night.

 

Thanks for the help!

James

Link to comment

I do just that. If any one of the three lights I'm concerned about are on, then button G is lit. One push on button G turns those lights off. Two programs and two scenes are used as follows:

 

DR Front Off Button scene has only the button as a responder and is controlled by the programs.

DR Front Off scene has the button as a controller and the lights as responders. The button is set to Non-Toggle Off and is operated manually

 

DR Front On Program
If
        Status  'CR / Devices / CR FanLinc-Light 80' is not Off            {
     Or Status  'KT / Devices / KT Ceiling 50' is not Off                      {  Status is used instead of Control, so it doesn't matter how the light was turned on
     Or Status  'LR / Devices / LR Ceiling Light KPL 20' is not Off      {
 
Then
        Set Scene 'DR / Scenes / DR Front Off Button' On <--this statement turns on the button LED if any one light is turned on
 
Else
        Set Scene 'DR / Scenes / DR Front Off Button' Off
 

 

DR Front Off Program
If
        Status  'CR / Devices / CR FanLinc-Light 80' is Off
    And Status  'KT / Devices / KT Ceiling 50' is Off
    And Status  'LR / Devices / LR Ceiling Light KPL 20' is Off
 
Then
        Set Scene 'DR / Scenes / DR Front Off Button' Off <--This statement turns the button LED of is all lights are turned off.
 
Else
        Set Scene 'DR / Scenes / DR Front Off Button' On
 

 

Link to comment

Sorry for the sideline but....

 

For both our educations.

 

 

DR Front On Program
If
        Status  'CR / Devices / CR FanLinc-Light 80' is not Off            {
     Or Status  'KT / Devices / KT Ceiling 50' is not Off                      {  Status is used instead of Control, so it doesn't matter how the light was turned on
     Or Status  'LR / Devices / LR Ceiling Light KPL 20' is not Off      {
 
Then....

 

How does ISY know if a device was operated via some scene or

-  do you never operate devices involved via scene control, or

 - do you detect the scene operation via the initiating device command sent, or

 - will status always know a devices status? I didn't think this was true and hardly ever use it anyway

 - other

Link to comment

Hello,

  I had a small setup 3 years ago at a residence. Recently, I purchased a 4,000 foot finished (with 2,000 additional feet unfinished) home and have replaced nearly 100 switches and outlets with insteon products. I also have quite a few hidden door links, motion detectors, leak detectors, and have the garage door kits installed on several doors (using the walk through here)...

 

  I am trying to create the following programs and need some help:

 

...

2) I read somewhere that double clicks can be used to toggle scenes. I have a kitchen scene that turns on all the lights to ON. But, it would be nice to use the same keypadlinc button to maybe toggle to a more dim scene. How do I do this?

 

...

 

Thanks for the help!

James

I use one Switchlinc Dimmer for seven different scenes.

 

Double tap up -- all lights in room on full

Single tap up  - Lights in TV watching mode, toggles between reading mode scene

Long press up - brighter scene for room

Long press down - Movie watching mode and trn on coloured lights around perimeter

Single tap down - All lights off scene - bedtime

Double tap down. -  Turn on coloured lights only - turn on Off scene for white lights

 

I use these programs to set one variable to a value (non zero except Off scene).

I built many programs that turn on scenes based on that variable value.

If I change an involved light say... brighter over a desk, when I turn off that switch over the desk I can resume the scene by setting the variable to -1 (no scene) and then back to it's value again. ISY is automagic!

 

 

Here is a sample of both ends of this code using the double tap up  command on any of 4 SwitchLinc Dimmers ora 4 button RemoteLinc that clones the tapping styles of the main SwitchLinc.

 

Note $cMODE.FULLON is an integer variable only used for a  constant and predefined in the variables for easy reading and programming.

Also note the use of a second variable, $sGathRm.Colours, to duplicate this process with coloured light scenarios.

GathRm Mode.FullOn.select - [ID 005F][Parent 0004]

If
        Control 'Gathering Room / PotLights over Chairs' is switched Fast On
     Or Control 'Gathering Room / GathRm KeyPad.A' is switched Fast On
     Or Control 'Gathering Room / PotLight over Desk' is switched Fast On
     Or Control 'Gathering Room / PotLight over Table' is switched Fast On
     Or Control 'PotLights over TV' is switched Fast On
 
Then
        $sGathRm.Mode  = -1
        $sGathRm.Mode  = $cMODE.FULLON
        $sGathRm.Mode Init To $sGathRm.Mode
        $sGathRm.Colours  = $cCOLOUR.FULLON
        Wait  1 second
        Run Program 'GathRm Mode.FullOn.select' (Else Path)
 
Else
   - No Actions - (To add one, press 'Action')
 

Here is one program that actually operates the white light scene

GathRm Mode.FullOn - [ID 00AF][Parent 00C8]

If
        $sGathRm.Mode is $cMODE.FULLON
 
Then
        Set Scene 'Gathering Room / FullOn' On
 
Else
   - No Actions - (To add one, press 'Action')
 
Link to comment

Sorry for the sideline but....

 

For both our educations.

 

 

 

DR Front On Program

If

        Status  'CR / Devices / CR FanLinc-Light 80' is not Off            {

     Or Status  'KT / Devices / KT Ceiling 50' is not Off                      {  Status is used instead of Control, so it doesn't matter how the light was turned on

     Or Status  'LR / Devices / LR Ceiling Light KPL 20' is not Off      {

 

Then....

 

 

How does ISY know if a device was operated via some scene or

-  do you never operate devices involved via scene control, or

 - do you detect the scene operation via the initiating device command sent, or

 - will status always know a devices status? I didn't think this was true and hardly ever use it anyway

 - other

Yes, "status" will reflect actual device status, regardless of how achieved. This assumes, of course, proper communications.

Link to comment

The ISY doesn't "know" how a device was turned on (or off), but the ISY does keep track of the state of the device including the On-level if the device is a dimmer.

 

Using Control as a condition will trigger the program only if the device was manually operated or if a direct command was sent. But, using Status will trigger the program no matter how the state of the device was changed even if the change in state was initiated via a scene.

 

If a scene does not update the devices status, then you may have a communication difficulty.

Link to comment

I have to disagree somewhat.

If I send an X10 On to an Insteon  LampLinc module   ISY has no idea the lamp has turned on unless I detect the X10 command or manually query the LampLinc module. 

 

Also, ISY does not keep track of scene statuses and presents no status on the scene's setup page. This was discussed elsewhere that ISY can send scene commands but not (or won't)  receive them.

 

ISY only keeps track of commands from itself or initiating devices and doesn't really know the true status of any device. This is why there are so many ISY status blanks on power up. Most of the time this is transparent.

Link to comment

Not so. The ISY does keep track of a device's status, unless you have a communication problem.

 

However, the ISY does not and cannot determine that state of a scene. That's because a scene can turn some devices on, some to a specific On-level and other device off.

Link to comment

I have to disagree somewhat.

If I send an X10 On to an Insteon  LampLinc module   ISY has no idea the lamp has turned on unless I detect the X10 command or manually query the LampLinc module. 

 

Also, ISY does not keep track of scene statuses and presents no status on the scene's setup page. This was discussed elsewhere that ISY can send scene commands but not (or won't)  receive them.

 

ISY only keeps track of commands from itself or initiating devices and doesn't really know the true status of any device. This is why there are so many ISY status blanks on power up. Most of the time this is transparent.

Yes, much of the status tracking is assumed, based on signals from controllers and scene definitions. If communication is good, however, this will be accurate. Yes, "status" refers to individual devices and not to scenes.

 

If you do not consider this tracking of status, then I guess we disagree somewhat, as you suggest. For my purposes, I have found this to be sufficiently accurate on which to base program actions. ,

Link to comment

Archived

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


×
×
  • Create New...