- Create Scheduled events and maintain them via any device that manages a google calendar (iPhone, PC, MAC, Android).
- Event Monitor events from a Control4 system
- Driver can be installed multiple times in a single project connecting to separate calendars allowing for support of property management companies or dealer/home status
- Does not require 4Sight subscription
- Set Sprinkler, Thermostat, Lighting scenes, fountains etc… from any GC (Google Calendar) account
- Create Bar TV schedules before the games start!
- Create a welcome macro for guest staying at your house
- Setup monthly or yearly maintenance scheduled for home automation products.
- Track events and changes to your home or office automatically
- DO ALL OF THIS WITHOUT ANY CONTROL4 COMPOSER or 4SIGHT SERVICE!
- Control4 2.7.2 or higher
- A Google Account with access to the Calendar
Driver is provided by Cinegration LLC. All rights reserved.
No posts found
Developed by: Cinegration LLC (2016)
Many dealers and homeowners have longed for a simple way to create scheduled events from a mobile device. This driver does exactly that and more! Using the power of the Google Calendar system, Cinegration has developed a gateway driver to allow scheduled events to be done via a google calendar.
Create Scheduled events and maintain them via any device that manages a google calendar (iPhone, PC, MAC, Android).
Monitor events from a Control4 system
Driver can be installed multiple times in a single project connecting to separate calendars allowing for support of property management companies or dealer/home status (see appendix on how to).
Does not require 4Sight subscription
Common Examples for a use of this driver:
Set Sprinkler, Thermostat, Lighting scenes, fountains etc… from any GC (Google Calendar) account
Create Bar TV schedules before the games start!
Create a welcome macro for guest staying at your house
Setup monthly or yearly maintenance scheduled for home automation products.
DO ALL OF THIS WITHOUT ANY CONTROL4 COMPOSER or 4SIGHT SERVICE!
The driver installation is broken into 4 parts: Google Account Setup, Calendar Setup, Control4 Monitoring Setup, Test and Verification of Event execution.
Part 1: Google Account Setup
- Add Driver to Project
- Copy the Google oAuth User Code (located on the main system design page of the driver)
- Visit this website: https://www.google.com/device
- Log into the google account this driver will be attached to
- A screen like the one below should appear, just paste the auth code here.
- Choose accept on the next screen and close your browser.
- After a few seconds the driver Property: oAuth: Status should say Authorization Complete…
- The driver is now linked together with the google account
Part II: Calendar Setup
- Actions: Retrieve Calendar List
- This grabs the current calendars from the google account and puts that list in the property “Calendar Name”
- Create a new calendar (recommended) or choose the calendar you want to make the house calendar
- Note: The calendar name will be whatever is entered into property “New Calendar”
- At this point the calendar and google are setup. The driver is now ready for scheduling deployment.
- Choose what gets ‘monitored’ by selecting the control4 devices under each category
PART III: Monitoring Events
PART IV: Test and Verify.
After setting up Calendar has been completed. The driver is now ready for deployment. Under Actions, press Send Test Event. After a few seconds the google calendar should have an event listed under the calendar.
Creating a scheduled event
- Go to google calendar and create an appointment at the time you want to have the event to start.
- Note: Make sure you choose the calendar being used! This is most likely NOT the default calendar chosen!
- The appointment name will be a the action you want to do on the Control4 system. Here are some examples:
- Trigger lighting scene ‘morning’ at 6 am
- Trigger macro ‘sprinklers on’ which turns the sprinklers on in the home at 8am
- Trigger lighting scene ‘evening lights’ at 6pm
- Watch the TiVo in the family room and change the channel to 653 to begin the football game
Driver Process Messages:
The driver will process up to 5 ‘events’ at a time. Each event is checked for validation, and proper time signature. The driver will then ‘update’ the appointment summary with either a ! for an error, and * for good, ready to go.
In the above examples: scene, evening lights is good. Clicking on the appointment will bring up the history log for this particular event and any helpful ideas as to why it’s not working. (example1: scene, morning, example2: scene evening lights)
Example of Event History Log after successful execution of event:
Once event has been executed, the * is automatically removed from the event and history log inside the event is updated as follows:
How to use the driver:
Cinegration has developed a simple syntax for controlling and operating scheduled events. This is completed by using syntax: MODULE, DEVICE NAME, ACTION, PARAMETERS. Each event must be structured in this format. Note: Case is in-sensitive as the driver sets all messages to upper case when processed. Thus scene, Scene and SCENE are the same thing to the driver.
o This is the category or ‘type’ of message that the driver needs to process. This can be any of the following:
Scene. This will execute a lighting scene. This module does not require an action or parameter. Example: scene,All On
Macro. This will execute a macro command. These are programming events that are custom built in each Control4 project. This module does not require an action or parameter. Example: macro, Start Day
Device. This will send a command directly to a device in the Control4 project. The action and parameters required are determined by the individual device you are controlling. Some examples are:
Device, Kitchen Lights, On
Device, Study Fan, Off
Device, Backyard Fountain, On
Device, Garage Door, Close
Device, Security System, BUTTON_PRESS, AWAY, ButtonID = Away
o Note: there is an easier way to do this command above (see module Security!)
Room. This will send a command to a room. Some examples are:
Room, Theater, Off = Turs off the Theater
Room, Theater, Cable = Sets the current selected device as Cable in the room
Room, Theater, Cable, 653 = Sets the current selected device as cable and changes the channel to 653
Using a comma or semi-colon in the device name (these must be removed for the driver to work)
Dual device names. In order for the driver to ‘know’ which device you are controlling it will require the room name in addition to the device name. An example of this would be ‘CHANDELIER’. If there are two devices named CHANDELIER, then the driver will require the name to include the room name with a / in between. Example:
o Living Room/Chandelier
o Rec Room/Chandelier
Remember if you can’t do it via composer programming you WILL NOT BE ABLE TO DO IT VIA THIS DRIVER! Example: security, away will not work if you have a Honeywell alarm panel that doesn’t support non-alarm code arming.
A trick to find out what the action or parameters need to be can be done by creating the composer action, copying the data and pasting it in a notepad program. Here is an example of what you will see:
o <cutitems><item><Proxy>security</Proxy><Type>Command</Type><DeviceID>1021</DeviceID><Description>Press Button: AWAY</Description><XmlData><devicecommand owneridtype="" owneriditem="-1"><command>BUTTON_PRESS</command><params><param><name>ButtonID</name><value type="STRING"><static>58</static></value></param></params></devicecommand></XmlData></item></cutitems>
o Here you can see the command or action is BUTTON_PRESS and the parameter requires a ButtonID value. This value is 58 so the action would be:
Device, security system, BUTTON_PRESS, ButtonID = 58. This would cause the alarm system to arm to away.
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.
Cinegration strives to provide fully working drivers without defects. However, changes and bugs may be found. Because of this, any reasonable 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 as determined by Cinegration LLC.
Thank you for choosing a driver by: Cinegration LLC.
- Updatd oAuth/Google Settings
- migration to driverCentral
- Official Launch of Driver
- Fixed issue with MACRO events not firing
- Fixed issue where some device/room names would not work properly
- Cleaned up look of history report for events
- Added helper tools for customers/dealers when something goes wrong
Resolved issue with Door Locks not displaying status on Google Calendar
- Added in support for Cinegration Showroom license support
- Fixed issue with monitored devices not 're-linking' after a reboot
- Fixed issue when loading project into driver and not having the macro or lighting scene agents
- Fixed issue with version number on HouseLogix
- timezone setup now longer required. Driver uses Control4 timezone when calendar isn't setup with a timezone
- Bug fixes in: Lighting and macro execution
- Optimized initial setup
- Moved calendar list as a drop down menu
- Updated documentation
- Minor Bug fixes.