Modes Agent

MSRP: $99.00
[Sign in for more info]
Cinegration LLC
Please sign in to buy

This product cannot be added to the
cart because you are not logged in.


Many dealers incorporate home 'modes' that allow the home to 'shift' when homeowners arrive or leave. This driver is designed to streamline installations that incorporate modes and provide a simple interface for dealers to implement these feature.

In addition, the driver can be used to implement 'vacation lighting' without requiring a lot of dealer programming. This saves a great deal of re-programming time if lights are added/deleted to a project.

FEATURES:

  • Create Vacation Lighting quickly and easily using any Control4 compatible Lighting system!
  • Provides rapid deployment of up to 3 Modes for any Control4 project
  • Simple Security integration into Modes (compatible with most alarm systems in Control4)
  • Thermostat Vacation On/Off per Mode
  • Control4 Keypad Integration - toggle 'through' all three Modes with automatic color assignment on all keypads
  • LED Output Only link (for more advanced keypad programming)
  • Custom email variable so a special message can be sent to the homeowner when the mode changes
  • Composer variable that changes when the mode of the driver changes (STRING type)
  • Turn all rooms off automatically when a Mode is engaged
  • Random lighting for Vacation Lighting
  • Custom events for each Mode e.g. Lock doors, Shut garage doors

REQUIREMENTS:

  • Just a Control4 System!  Now how easy is that!

Driver is provided by Cinegration LLC.  All rights reserved.

No posts found

Write a review

FEATURE ADDED 8.0.6 – Update from 7.x.x to 8.x.x.  Using the Manage Driver software from Control4.

  1.       Added new connections for easier keypad setup (Single-Double Tap Link)
  2.      Add Lighting Scene actions for keypads (Choose a lighting scene to fire when a certain mode is activated)
  3.      Added auto setting of setpoints via the driver instead of vacation mode
  4.      Added Closing of garage doors after x amount of time
  5.      Added Locking of doors after x amount of time
  6.      Made arming to DSC security panels the default arming type (command 21 arms a DSC security panel)
  7.      Auto Setup Action.  Press this button and the driver will automatically scan the project and add the thermostats, security system, door locks and garage doors to the driver.

FEATURES ADDED 8.0.3 – For explanation of these items see Addendum at the bottom of the documentation

  1.       Added new connections for easier keypad setup (Single-Double Tap Link)
  2.      Add Lighting Scene actions for keypads (Choose a lighting scene to fire when a certain mode is activated)
  3.      Added auto setting of setpoints via the driver instead of vacation mode
  4.      Added Closing of garage doors after x amount of time
  5.      Added Locking of doors after x amount of time
  6.      Made arming to DSC security panels the default arming type (command 21 arms a DSC security panel)
  7.      Auto Setup Action.  Press this button and the driver will automatically scan the project and add the thermostats, security system, door locks and garage doors to the driver.

 

 

Purpose of Driver:  Many dealers incorporate home 'modes' that allow the home to 'shift' when homeowners arrive or leave.  This driver was designed to streamline installations that incorporate modes and provide a simple interface for dealers to implement this.  Also, another major purpose for this driver is to implement 'vacation lighting' without a lot of dealer programming which can create major headaches if lights are added/deleted to a project.

 

Driver Features:

ñ Provides rapid deployment of up to 3 modes for any Control4 project

ñ Simple Security integration into modes (compatible with most alarm systems in Control4)

ñ Thermostat Vacation On/Off per mode

ñ Control4 Keypad Integration (toggle 'through' all three modes with automatic color assignment on all keypads. Compatible with both v1 and v2 keypads.  Also, you can assign each 'mode' to one keypad button (Thing about a 3Button keypad with Home, Away, and Vacation on it).

ñ LED Output Only link (for more advanced keypad programming)

ñ Custom email variable (so a special message can be sent to the homeowner when the mode changes)

ñ Composer variable that changes when the mode of the driver changes (STRING type)

ñ Turn all rooms off automatically when a mode is engaged

ñ Random lighting for mode 3 (Vacation Lighting)

◦  Create fast vacation lighting that will randomize on/off behavior of dealer chosen lights

◦  Custom Composer event for unique lighting installations

◦  Use Control4's scheduler or drivers built in time stamps for faster installations

ñ Custom events for each mode (example: Lock doors, shut garage doors)

 

How to Install:

ñ Add this driver to the project

◦  Properties

▪  Mode Currently Running

ñ This is the mode that is currently running on the program.  By default it will be Mode 1

▪  Adjust Mode

ñ Choose which mode you need to program or control

▪  Mode 1 (Programming Options)

ñ Mode 1

◦  Options (String Type) Default: Home

◦  Purpose: This is a name holder for the mode.  This name is then transcribed to the variables in the driver for easier customer implementation.

ñ Mode 1: Use Mode in Rotation

◦  Options (Yes/No) Default (Yes)

◦  Purpose: When keypad binding is used, setting this option to no will remove it from being used when one keypad button push is being used for all modes.  Another example of this is when you don't need mode 2 since your installation will only have 'Home and Vacation' modes. 

◦  Note: You must have at least 1 mode in the rotation or the driver will not work

ñ Mode 1: All Rooms Off

◦  Options (Yes/No) Default (No)

◦  Purpose: Will turn off all the rooms in the project

◦  This is done by sending the Room_Off command to each room.

◦  Note: if you have custom programming under 'Room Off' event of a particular room, that code will execute

ñ Mode 1: Tstats to

◦  Options (Vacation Off/Vacation On) Default (Vacation Off)

◦  Purpose: Will send Vacation On or Off to all thermostats listed in property Thermostats

◦  Note: Actual temp settings must be done on each thermostat.  This was done because it allows homeowners to adjust the setpoints without dealer intervention. If greater custom programming is required, please use Event: Mode 1 On

ñ Mode 1: Security System

◦  Options (Do Nothing/Arm after 5,20,30,60 Seconds/Custom) Default (Do Nothing)

◦  Purpose was to allow the dealer to automatically arm the security system after a certain amount of time when certain modes are set (Example: Leaving the home, set to away, wait 30 seconds and arm the security system)

◦  Will execute programming listed in property Security: How to arm

◦  Custom: Custom event that can be fired from composer for unique installations

◦  Note: This may not be a legal in certain countries in Europe.

ñ Mode 1: Button LED Color

◦  Options (Blue/Red/Yellow/Black/Orange/Green/Aqua/Fuchsia/Gray/Navy/Purple/Silver/Teal/White/DarkRed/DarkYellow/DarkOrange/DarkGreen/DarkBlue/Peach/Bubblegum) Default (Blue)

◦  Purpose: This color is the color that is sent to all Mode 1 keypads or Mode_Linked keypads when mode 1 is set

◦  Works with both V1 and V2 keypads.

 

▪  Mode 2 (Programming Options)

ñ Mode 2

◦  Options (String Type) Default: Away

◦  Purpose: This is a name holder for the mode.  This name is then transcribed to the variables in the driver for easier customer implementation.

ñ Mode 2: Use Mode in Rotation

◦  Options (Yes/No) Default (Yes)

◦  Purpose: When keypad binding is used, setting this option to no will remove it from being used when one keypad button push is being used for all modes.  Another example of this is when you don't need mode 2 since your installation will only have 'Home and Vacation' modes. 

◦  Note: You must have at least 1 mode in the rotation or the driver will not work

ñ Mode 2: All Rooms Off

◦  Options (Yes/No) Default (Yes)

◦  Purpose: Will turn off all the rooms in the project

◦  This is done by sending the Room_Off command to each room.

◦  Note: if you have custom programming under 'Room Off' event of a particular room, that code will execute

ñ Mode 2: Tstats to

◦  Options (Vacation Off/Vacation On) Default (Vacation Off)

◦  Purpose: Will send Vacation On or Off to all thermostats listed in property Thermostats

◦  Note: Actual temp settings must be done on each thermostat.  This was done because it allows homeowners to adjust the setpoints without dealer intervention. If greater custom programming is required, please use Event: Mode 1 On

ñ Mode 2: Security System

◦  Options (Do Nothing/Arm after 5,20,30,60 Seconds/Custom) Default (Arm after 20 Seconds)

◦  Purpose was to allow the dealer to automatically arm the security system after a certain amount of time when certain modes are set (Example: Leaving the home, set to away, wait 30 seconds and arm the security system)

◦  Will execute programming listed in property Security: How to arm

◦  Custom: Custom event that can be fired from composer for unique installations

◦  Note: This may not be a legal in certain countries in Europe.

ñ Mode 2: Button LED Color

◦  Options (Blue/Red/Yellow/Black/Orange/Green/Aqua/Fuchsia/Gray/Navy/Purple/Silver/Teal/White/DarkRed/DarkYellow/DarkOrange/DarkGreen/DarkBlue/Peach/Bubblegum) Default (Yellow)

◦  Purpose: This color is the color that is sent to all Mode 1 keypads or Mode_Linked keypads when mode 1 is set

◦  Works with both V1 and V2 keypads.

▪  Mode 3 (Programming Options)

ñ Mode 3

◦  Options (String Type) Default: Vacation

◦  Purpose: This is a name holder for the mode.  This name is then transcribed to the variables in the driver for easier customer implementation.

ñ Mode 3: Use Mode in Rotation

◦  Options (Yes/No) Default (Yes)

◦  Purpose: When keypad binding is used, setting this option to no will remove it from being used when one keypad button push is being used for all modes.  Another example of this is when you don't need mode 2 since your installation will only have 'Home and Vacation' modes. 

◦  Note: You must have at least 1 mode in the rotation or the driver will not work

ñ Mode 3: All Rooms Off

◦  Options (Yes/No) Default (Yes)

◦  Purpose: Will turn off all the rooms in the project

◦  This is done by sending the Room_Off command to each room.

◦  Note: if you have custom programming under 'Room Off' event of a particular room, that code will execute

ñ Mode 1: Tstats to

◦  Options (Vacation Off/Vacation On) Default (Vacation On)

◦  Purpose: Will send Vacation On or Off to all thermostats listed in property Thermostats

◦  Note: Actual temp settings must be done on each thermostat.  This was done because it allows homeowners to adjust the setpoints without dealer intervention. If greater custom programming is required, please use Event: Mode 1 On

ñ Mode 3: Security System

◦  Options (Do Nothing/Arm after 5,20,30,60 Seconds/Custom) Default (Arm after 20 seconds)

◦  Purpose was to allow the dealer to automatically arm the security system after a certain amount of time when certain modes are set (Example: Leaving the home, set to away, wait 30 seconds and arm the security system)

◦  Will execute programming listed in property Security: How to arm

◦  Custom: Custom event that can be fired from composer for unique installations

◦  Note: This may not be a legal in certain countries in Europe.

▪  Options for Security for each mode are: Arm after x seconds, Custom, Do Nothing

ñ Custom: is an event in Composer for unique security panels or unique situations

▪  The system uses the property: Security: How to arm.

ñ Dealer or homeowner will 'type' the button presses that 'arm' the security system.  (See Appendix A on this)

ñ Mode 3: Button LED Color

◦  Options (Blue/Red/Yellow/Black/Orange/Green/Aqua/Fuchsia/Gray/Navy/Purple/Silver/Teal/White/DarkRed/DarkYellow/DarkOrange/DarkGreen/DarkBlue/Peach/Bubblegum) Default (Red)

◦  Purpose: This color is the color that is sent to all Mode 1 keypads or Mode_Linked keypads when mode 1 is set

◦  Works with both V1 and V2 keypads.

▪  Mode 3 Lighting Options (Automatic Vacation Lighting)

ñ Mode 3: Random Lighting

◦  Options (Device Selector) Default (N/A)

◦  Purpose: Selects which lights to be part of the random lighting scene

◦  Note: If custom light pattern is chosen, dealer must select at least 1 light in this option for the driver to work.  Note: this is only for execution of script and light does not need to be part of the vacation lighting pattern

ñ Mode 3: Light Pattern

◦  Options (Random/Custom) Default (Random)

◦  Purpose: Lets dealer determine 'how' the random lighting events are handled.  They can be done automatically via the driver or by a custom event

ñ Mode 3: Shortest Light

◦  Options (Number: 1-180) Default (10)

◦  Purpose: Determines the time in minutes between Shortest and Longest for each light to 'toggle'.

◦  Turn this up or down to increase or decrease how 'erratic' the lighting is in the home

ñ Mode 3: Longest Light

◦  Options (Number: 2-180) Default (40)

◦  Purpose: Determines the time in minutes between Shortest and Longest for each light to 'toggle'.

◦  Turn this up or down to increase or decrease how 'erratic' the lighting is in the home

ñ Mode 3: Lighting Off Setting

◦  Options (Off/On/Left as is/Custom) Default (Off)

◦  Purpose: Because there is no telling what the light states will be at the end of the random lighting program.  This option tells the driver what to do with the lights.

ñ Mode 3: Lighting On Time

◦  Options (12AM-11PM/Scheduler) Default (6 PM)

◦  Purpose: This option defines at what time the random lighting should fire.  If it's set to scheduler, then this is disabled.

◦  Note: If On Time or Off Time are set to scheduler then both times will use the scheduler.

◦  Program will 'check' in once an hour on the hour and let the program know if it's within the time frame.  There are some items to remember.

▪  1. The on/off times do not reset if you change the time that they move.  Example, if you have the off time set for 6 pm, the current time is 5 pm, then move it to 3pm.  It will not reset until the next day.  The best advice is to set the times then start mode 3.

▪  2.  Upon reboot, the system will continue the random lighting until the off time is reached. Example, if the house is currently running random lighting and the home loses power past the off time.  When the home turns back on, it will continue with random lighting until the next off time. 

▪  3.  In most cases these actions are very rare and should not happen, however, dealers need to understand these items and if they feel this will create issues, they need to program disable events (programming/actions/turn off random lighting) upon reboot.

ñ Mode 3: Lighting Off Time

◦  Options (12AM-11PM/Scheduler) Default (12 AM)

◦  Same as Lighting On Time except this defines the off time sequence

ñ Mode 3: Lighting Program Status

◦  Options (Read Only) Default (N/A)

◦  Purpose: Dealer notification area to let dealer know if the random lighting sequence is running

▪  Global Properties

ñ Thermostats

◦  Options (Device Selector) Options (N/A)

◦  Purpose: Use this property to select which thermostats in the project will be controlled.

◦  Other non-Control4 drivers may work if they use the thermostatv2 proxy and incorporate vacation settings

◦  Note: multiple thermostats can be selected

◦  Only required if thermostat updating is requested

◦  If the thermostat doesn't support vacation setting, you can still use this driver and program setpoint updates under Composer->Programming->Events for each mode

ñ Security System

◦  Options (Device Selector) Options (N/A)

◦  Purpose: Selects the security system to use with the automatic arming.

◦  Only required if automatic arming is desired

ñ Security: How to arm

◦  Options (STRING) default (None)

◦  Purpose: Defines how the security system is armed when arming is selected in a mode.

◦  The driver sends 'ID' buttons to the main security system which is converted by the security system automatically.  A table below defines most security system ID numbers

◦  Note: Digits must be separated by a comma (example: typing 1234 is not the same as 1,2,3,4.  The first says ID One thousand two hundred thirty four vs, one, two, three, four)

◦  Example of arming a paradox security system to away with a code of 1,2,3,4

▪  1,2,3,4,58

 

Panel

Code

Button_ID

Paradox

STAY

59

 

AWAY

58

 

INSTANT

60

 

FORCE

61

DSC

HOME

22

 

AWAY

21

GE Networx NX-8 587E (3rd Party)

Stay

105

GE Networx 232 (Control4)

Stay

35

Elk M1 (Control4)

Away

21

 

Stay

22

 

Night

23

 

Instant

24

 

ñ Email Message

◦ Options (String) Default (Your home is now set to the $MODE mode)

◦ Message this built based on which mode is selected.  This message can say anything and $MODE is a place holder for which mode is currently running.

◦ Example: (mode 3 is running)

▪ Your home is now set to the Vacation mode

Connections

▪  Mode_Link

ñ Purpose: Keypad button to 'rotate' through modes

ñ When a new mode is selected, the led state will update immediately and 5 seconds later will update the mode.  This was added to allow customers time to 'travel' through the modes without them executing immediately

ñ Uses DO_PUSH and set led status

ñ LED of keypad will adjust automatically depending on which mode the driver is in

▪  Mode_1_Link/Mode_2_Link/Mode_3_Link

ñ Purpose: Keypad button push for mode 1,2, or 3 only

ñ LED will either be 'black' for or the LED color determined for this driver (see properties Mode LED color)

▪  LED_Update_Only

ñ Purpose: This will only update the LED state of the keypad button but not do anything with changing the driver mode. 

ñ Dealers may need to use this option for unique situations where a single button push for enabling a mode is not high enough security (Offices/Little children)

◦  Programming

▪  EVENTS

ñ Mode Changed

◦  Action: Will trigger whenever the current mode is changed

◦  Useful for email trigger

ñ Mode 1 On/Mode 2 On/Mode 3 On

◦  Action: Will trigger whenever the specific mode is engaged

◦  Useful for custom events (lighting scene on in the home/lock doors/close blinds)

ñ Mode 3 Custom Lighting On Event/Mode 3 Custom Lighting Off Event

◦  Used in conjunction with 'custom' setting under Mode 3 Light Pattern

◦  Used in special circumstances where specific lighting is requested

ñ Custom Security Arm

◦  Used in conjunction with 'custom' setting under mode x security arm

◦  Used in special cases where simple arming is not possible

▪  ACTIONS

ñ Engage Mode 1/Mode 2/Mode 3

◦  Trigger to execute specific mode

◦  Example: Custom button to change to specific mode from Control4 GUI

◦  Example: Security system disarm, Engage Mode 1

ñ Start/Stop Mode 3 Lights

◦  Starts/Stop mode 3 lighting pattern

◦  Note: Mode 3 must be active for this to work

▪  VARIABLES

ñ CURRENT_MODE

◦  Type: String

◦  Is the customer descriptions of which mode is currently in use (defaults: Mode 1 = Home, Mode 2 = Away, Mode 3 = Vacation)

ñ CURRENT_MODE_EMAIL

◦  Type: String

◦  Is the customer specific  email for faster emial creation.

◦  Most common use of this variable is to create an email with only this variable in the body and send it when the mode changes

ñ MODE_3_LIGHTING_RUNNING

◦  Type: Boolean (True/False or On/Off)

◦  Is true when Mode 3 Lighting is running

 

 

Addendum:

Single-Double_Tap_Link: These connections were designed to help a dealer with keypad integration. If this connection is used intstead of Mode_x_Link it will require a double tap in order to move to that mode.  This allows for a button like ‘Home’ or ‘Away’ to have a lighting scene attached to it but only move modes on a double tap giving a dealer and customer more flexibility in installation.

Mode x Lighting Scene Link: These connections are to be used in conjunction with the new Single-Double_Tap_Link connection.  Simply ‘bind’ the lighting scene you would like to be executed when the button is pressed (note these can also be toggles). 

Example of new feature:

                Customer requests that a button be called AWAY.  This button when pressed will only execute the lighting off scene.  When double tapped however, will engage the Away mode.

Mode X: Set Thermostats To (HEAT/COOL): These properties were added to speed up installation/configuring time on the driver.  Just set the setpoints you’d like the home to be in under each mode.  After that, all the thermostats listed under the property (Thermostats) will go to those setpoints when the mode changes.   Note: For backwards compatibility property: Mode X: Tstats to should be set to ‘Do Nothing’.  Future releases of this driver may remove this property as Control4 is discontinuing vacation setpoints.

Door Lock and Garage Door Closings:  Cinegration has now added into the driver the ability to automatically lock and close garage doors after x seconds.  This is customizable for each mode.  If the time is -1 then it will not lock or close when the mode is selected.

Example of new feature:

                Customer requests that when AWAY is selected, lock the doors and close the garage after 2 minutes automatically.  Dealer would change the Property ‘Mode 2: Lock Door After’ to 120.  Dealer would also change property ‘Mode 2: Close Garage Door After’ to 120.  Note: Dealer will need to select which garage doors and door locks under the corresponding property for this feature to work.

Common Installation Use Example:

ñ Objective

◦  Customer requests a keypad button by the back door that allows them to choose which 'mode' the home is in.  Mode 1 Should be called Home,  Mode 3 should be called Vacation.

▪  Mode 1: Turn off Vacation mode on all the thermostats, fire lighting scene 'Home'.

▪  Change Mode 2: Use Mode in Rotation to No

▪  Mode 3: Turn on Vacation mode on all the thermostats, turn off all the rooms in the home, arm the security system after 1 minute and engage random lighting between 6PM and 12AM.

 

◦  How it's done.

▪  Add the driver

▪  Bind keypad button (Under Connections) Mode_Link to keypad button

▪  Under System Design, choose thermostats and security system to driver.

▪  Type in how to ARM the security system (example, 1,2,3,4,58 = code: 1234 AWAY) Note: 58 is Paradox AWAY

▪  Under System Design, select Adjust Mode, Mode 3.

ñ Select which lights are in the random lighting event

ñ Select Lighting On/Off times to 6PM - 12AM

ñ Change Mode 3: Security System to 'Arm after 60 seconds'.

▪  To program to turn the lights on when Home is triggered, go to the programming tab, under the Event 'Mode 1 On'.

ñ Add Execute 'Home' Lighting scene

 

ñ This driver contains code written by Cinegration.  Any modification to this driver or any driver written by Cinegration without the express consent will void all warranties, constitute a ban on all drivers released by Cinegration and potentially legal action.

 

 

 

Warranty:

     Cinegration strives to provide fully working drivers without defects.  However, changes and bugs may be found.  Because of this, any bug/maintenance update to this driver will be free of charge.  However, due to the ever changing nature of computer and audio/video systems, if a new version of the Control4® software creates issues with this driver, or feature enhancements, an upgrade version will be provided for an additional expense or free as determined by Cinegration LLC.

 

Thank you for choosing a driver By: Cinegration LLC.

 

  • 1003
    • Major Code update (bug fixes and improvements)
    • Fixed modes not triggering correctly
  •  1002
    • Fixed issues with keypads not linking correctly
    • fixed issue with modes not correctly triggering
  •  1000
    • migration to Driver Central.

 

+ 8.0.0: Migration to HouseLogix server

     + 8.0.1: Fixed issue where after reboot, variable data was not pushed until a mode was changed.

     + 8.0.2: Fixed issue with license server

     + 8.0.3: Added new features to driver.  See documentation

     + 8.0.4: Corrected issue where License server would report 'Failed-to-Post' and cause the driver to stop working

     + 8.0.5: Added ability to update driver from 7.x.x to 8.x.x.

     + 8.0.6: Added support for Cinegration Showroom License