Reply To: Getting Insteon Scene to Trigger an Action 2017-12-21T22:59:53+00:00

HOME Forums Gateways EZSrve Getting Insteon Scene to Trigger an Action Reply To: Getting Insteon Scene to Trigger an Action

Anonymous
Post count: 1001

For the most part you do not want EZServe or any other HA software/firmware involved in basic lighting. Anything that can be done using native Insteon hardware should be done with native Insteon hardware. It is faster and should EZServe be unavailable for any reason, the basic lighting still functions.

Establish the device to device link relationships as you would if using the Tap Set button method. It is just much easier to accomplish with EZServe Scene/link management. When the proper links are established the status LEDs stay in Sync without any intervention from EZServe or any other HA software/firmware. This is the way Insteon hardware is designed to work.

The hardware linking should look like this… (Insteon calls this cross-linking of devices)

KeypadLinc1 – Button D – Controller
OD Front Yard Light – Responder
Entry Way – Responder
KeypadLinc2 – Button x – Responder
KeypadLinc3 – Button y – Responder

KeypadLinc2 – Button x – Controller
OD Front Yard Light – Responder
Entry Way – Responder
KeypadLinc1 – Button D – Responder
KeypadLinc3 – Button y – Responder

KeypadLinc3 – Button y – Controller
OD Front Yard Light – Responder
Entry Way – Responder
KeypadLinc1 – Button D – Responder
KeypadLinc2 – Button x – Responder

I included KeypadLinc2 and KeypadLinc3 for the sake of the example to show how your future KeypadLincs will be linked. When the devices are linked this way pressing Button D (KPL1) or Button x (KPL2) or Button y (KPL3) will control OD Front Yard Light and Entry Way and the other KeypadLinc button LEDs, all without any HA intervention. That is, pressing Button D on KPL1 will turn On/Off OD Front Yard Light, Entry Way. KPL2 Button x LED, KPL3 Button y LED.

To establish the above links/cross links using EZServe define the following…

Scene x
Controllers
KeypadLinc1 Unit 6 (representing button D in six button mode)
KeypadLinc2 Unit x (unit number representing button used on KPL2)
KeypadLinc3 Unit y (unit number representing button used on KPL3)
Responders
OD Front Yard Light LD3 0, (LD1 and LD2 values represent Bright and Ramp Rate values of your choice)
Entry Way LD3 0, (LD1 and LD2 represent Bright and Ramp Rate values of your choice)
KeypadLinc1 LD1 100%, LD2 .1 second, LD3 6 (for Button D in 6 button mode)
KeypadLinc2 LD1 100%, LD2 .1 second, LD3 x (value representing button x)
KeypadLinc3 LD1 100%, LD2 .1 second, LD3 y (value representing button y)

Note that EZServe is neither a Controller nor Responder as once these links/cross links are established by EZServe, you can unplug EZServe and the above device relationships work.

The time base Action at Sunset +15 requires a Scene where EZServe is the Controller and whatever device(s) you want to respond are Responders. The Controller Unit number is your choice for this Scene, just don’t duplicate Unit number usage where EZServe is the Controller. If you want KPL button LEDs to turn On/Off in response to this EZServe Scene add each KPL button as a Responder.

Scene y
Controllers
EZServe Unit 4 (this number is your choice, do not use same Unit number for different scenes)
Responders
OD Front Yard Lights LD3 0, (LD1 and LD2 represent Bright and Ramp Rate values of your choice)
Entry Way LD3 0, (LD1 and LD2 represent Bright and Ramp Rate values of your choice)
KeypadLinc1 LD1 100%, LD2 .1 second, LD3 6 (for Button D in 6 button mode)
KeypadLinc2 LD1 100%, LD2 .1 second, LD3 x (unit number representing button used on KPL2)
KeypadLinc3 LD1 100%, LD2 .1 second, LD3 y (unit number representing button used on KPL3)

The Responders listed in Scene y are whatever devices and KPL buttons that you want to respond to the Scene.

You will not see EZServe in the list of devices as there is nothing to check for EZServe itself. You are checking the state/status of individual devices, which EZServe firmware is keeping track of, but there is no specific state/status of EZServe itself.

Hope this clears up some of the questions. You do not need or want an Action to keep the KPL button LEDs in sync. Once the devices are properly linked/cross linked the Insteon hardware will keep things in sync as the hardware was designed to do. Remember the Insteon devices are designed to work without any HA. Only when you get into the more sophisticated things like controlling devices at certain times of day (Sunset +15 for example) or complex Conditioning is HA stuff needed and very useful. HA does make the process of defining and maintaining the links much easier. You could use the Tap Set button press technique to establish the links/cross links with the same results but it is much easier when doing from the PC.