Dash Access Control for Home Automation

Access Control Suite

Login or Register to see price!


Access Control seems to be an important but generally missing piece of Home Automation.  While many solutions exist, a simple solution providing all the tools necessary to give your end-users a powerful and easy-to-use project access solution was needed.  Enter Dash Access Control!  This Dash App will allow you to provide centralized control & monitoring of all of your access-related devices.  It can integrate almost any URC-supported module into it easily and supports automatic programming for some devices.  Setup only takes minutes and provides your end-user with many new options (many even unrelated to Access Control when used creatively)!


Sold by: Dash OS
SKU: access. Category: .

Product Description

Dash Access is a module that allows you to use any combination of sensors & control devices to create your own two-way modules without the need to know URC’s Advanced SDK.  When paired with supported IP Devices such as miDoor (Wi-Fi Garage and Gate Controller), setup takes literally seconds and you will have two-way feedback and control built into your systems in seconds!

Since Dash Access allows you to combine any number of devices into the same interface, you can have your Garage Doors, Door Locks, Lights, and much more all in a single interface for your end-users so they don’t need to jump from module-to-module just to accomplish basic tasks within their system(s).

Dash App Features
  • Instant Two-Way Interface to your miDoor Wi-Fi Garage & Gate Controllers.
  • Multiple miDoors on a single interface or group them into multiple instances of the module.
  • Add “Custom” Devices such as Z-Wave Door Locks, Lights, and Sensors into the module.
  • Get an Event Log of all status change events for the devices.
  • Query for device status using URC’s “TCL Commands” feature.
  • Supports Cloud Logging & Debugging for quick and seamless customer support and initial setup.
  • One-Way Macro Commands to control your devices however you’d like!
  • Complete Flexibility in building a true Access Control Solution for your end-users.
Supported Hardware
  • miDoor – Sold directly by Dash OS using the form above, miDoor is a professional & high-quality device capable of controlling & monitoring your Garage Doors & Gates (and anything else that uses Relay/CCI Sensing).  Local Connectivity, Secure (SSL), and Simple to Install!
  • myQ – Login to the users myQ Account via Dash Access and add any number of myQ Devices directly to the Dash Access User Interface!  Dash Access will provide Control, Monitoring, and Event Logging for all devices added.  Requires Active Internet Connectivity & myQ Dash Access Add-On
  • Lutron VCRX – Want deeper integration with the Lutron Solution?  When combines with Lutron by Dash you can use Lutron’s Visor Controller to provide Garage, Gate, and Lighting Control from the Dash Access User Interface quickly!
  • URC Relay / Sensor – Use the URC Relays and URC Sensors to provide your users with 2-Way Garage & Gate Control & Monitoring!
  • Z-Wave – Use URC’s ZW-1 combined with it’s available Device Events & TCL Commands to provide Garage & Gate Control from Z-Wave Devices & Sensors
  • So Much More! – Dash Access provides you with the flexibility to build your own solution using almost any combination of devices you can imagine!  Join our HipChat Community if you have any questions!

Available TCL Commands

  • (Basic) New Device – Creates a new device that will be available for control in the 2-way interface
  • (Basic) Change State – This changes the state of the Basic / Custom Device from within the 2-way interface
  • (miDoor) New Device – Automatically will add a miDoor device to the interface
  • (miDoor) Control Device(s) – This will allow you to Open/Close/Toggle the connected miDoor device
  • (miDoor) Query Device – Allows you to save the state of a miDoor device into a URC Integer Variable.  This includes Door State &  Time Since Door State Last Changed, & Current Temperature.
  • (Lutron) Setup System Output – (Coming Soon) This will allow you to automatically monitor Lutron Lights and show state / provide control from the Dash Access User Interface.
  • (myQ) Login to Account – This is used in the Dash Access Startup Macro to login to the users myQ Account.
  • (myQ) New Device – Add a Device by Name or ID from the users myQ Account Dashboard.
  • (myQ) Control Device – Controls a myQ Device from any URC Macro
  • (myQ) Query Device – (Coming Soon) Query a myQ Device from any URC Macro and save the result into a URC Variable for future use in any if/else statement.

Available Device Events

  • Module Startup / Setup – This event will happen at startup and is where we put our TCL Commands that setup new devices to control
  • Device Changes State – This device will happen whenever the connected device changes state
  • Device Controlled By User – This is an event that will occur when the device is controlled from within the 2-way interface

URC Interface Support

  • URC Mobile – Phone – Full Two-Way Support, Full One-Way Support
  • URC Mobile – Tablet – Full Two-Way Support, Full One-Way Support
  • iOS v1 (Phone/Tablet) – Full One-Way Support
  • TRC-1280 – Full Two-Way Support, Full One-Way Support
  • TRC-1080 – Full Two-Way Support, Full One-Way Support
  • TKP-7000 – Full Two-Way Support, Full One-Way Support
  • TKP-2000 – Full One-Way Support
  • MRX-20 – Full Two-Way Support, Full One-Way Support

Dash App Documentation Overview

This page will guide you through the installation, configuration, and programming of the specified Dash App.  You can navigate to various sections of the documentation by using the menu to the left.  New information is always being added to Dash’s Documentation so be sure to check back often to discover new ways to utilize your apps!

Download Page:

Driver Location:

My > IP Database > AUX > Dash Apps > Access Control

Driver File:

Dash – Access Control.csd

Dash OS Update History

Whenever an update is available for a Dash App, a log of the major changes in the version will be provided below.  This does not necessarily reflect every change that was made as some minor changes may have been made that are undocumented, but it should reflect any changes that affect the operation of the Dash App.

Version 1.0

Download & Import the Dash App

In order for the Dash App to become recognized by the URC Programming Software we will need to import the provided TCM File into the Software.  Once this has been done properly the Dash App should show up in the “Add Other Devices” programming step in the “Accelerator Location” provided on the overview tab.

Import TCM

In your Programming Software locate the “Import TCM Files” button in the File tab of the top menu toolbar.  Click it to open the Windows File Browsing window.  Browse to the TCM file you wish to import and select it.

Import Dialog

Based on the Dash App / Module you are importing, a dialog similar to the below will appear.  This window indicates what interfaces are supported by the TCM File you selected.  System Plugins may only show “Driver” and “Base Station Files” when no User Interface is provided by the module.

Restart

After Importing your TCM File it is always safe to quickly restart your Accelerator Software to make sure your changes are properly made.  While this isn’t required every time, it is a good step to make sure everything is changed as needed.

Confirm

Confirm that the Dash App was successfully imported.  You can do this by navigating to the driver where the Dash App is installed (see Overview Tab) and making sure a checkbox is provided for “8. Select 2-Way Modules for Network Remotes / Keypads”

Non URC Network Setup

This Dash App does not require that a specific IP Address is setup for it to operate.  However, it should be assigned an “Instance ID.”  When a module does not require a specific IP Address be setup, you can assign any IP Address to the Dash App that is unique from any other device in the list.

Your IP Address will be used as an “Instance ID” which will separate it from any other Dash Apps or URC Modules you have setup.  This ID is helpful when you want to create jumps to the Dash App in multiple rooms / areas of your programming.

In the example below we have added two Dash Apps, “System Monitor” and “Time Tools.”  Each has been given a unique value “0.0.0.1” and “0.0.0.2.”  If they were assigned the same value the Dash App would result in an error and would not start up properly.

Step 11. 3rd Party 2-Way Settings

Properly configuring the Dash App Parameters in your Automation Programming Software is important in order to make the App work as you want it to.  These Parameters will be used each time the App starts up to configure how the App will operate.  Below we will go over each available parameter.

In System Parameter Information, you will have two optional parameters to setup. The first being Auto Dash Timelines which is set to No by default. When Enable is set to Yes, it will then automatically create Timeline Events each time Access is used for control.

The second parameter is Multi-Instance ID Setup. This is only necessary if you will be adding multiple Access Control instances and want to keep the logging separated between them. Then you would program each instance that you want separate with a unique ID.

Module Startup / Setup Event

Dash Access Control, is a a full 2-way module that includes a 2-way user interface. This is what will give us the ability to check status, see event logs, and control our devices. We need to initially setup the device we want to be able to control with Access. This will be through a Module Setup / Startup Device Event.

Within this event, we will use TCL Commands to create new devices that we will be able to control from the Access Control interface. Each device that we want to control from within Access will need to be created in this macro.

Important: Dash Access takes 2 minutes after the Controller has started up before it will run the startup macro.  While this is running you will not see anything on the user interface.

Adding miDoor To Access

Since miDoor is fully supported by Dash Access Control (only one license is required per project), all you need to do is create a “(miDoor) New Device” TCL Command and fill in the Parameters, and you’re good to go. Make sure that you miDoor has been added onto your wifi network first.

Within the miDoor Administration make sure that “Allow Admin Door Operation” and “Allow Remote Door Operation” are checked

As always with TCL Commands, we want to name them something descriptive so that we can tell what they do just by looking at them in a macro. In this example we name the command “Setup miDoor 192.168.1.20”. At a glance, we will know exactly what the command is for.

We choose our Access Control module, which will be called whatever we named it in our tree. Then we choose (miDoor) New Device. In Parameters, we will name the device, this is the name that we will see within the interface. The name must be unique from any other device added to this instance of the Module.  We fill in the correct IP for our miDoor. And then add in our username and password.

Creating A Door Lock Device

Creating a door lock to be controlled form Access only takes a simple TCL Command. Lets call this command “Create Lock Device (Front Door). We choose our Access Control module from Available Devices. This command is the Setup: New Basic Device command. In parameters we give the lock a name that will appear in our interface. Then we choose lock from the Device Type dropdown. This will get our lock to show up in access, but we will need to do some additional things in order to get it working.

Creating a Checkbox For Control

A checkbox will give us the ability to enable/disable events. Such as disabling the macro that turns on a game system. This is accomplished by using the checkbox to set a variable. The creation will be done through another TCL Command. We will call this “Create Checkbox Device (Game System). We choose our Access Control module. This command will be Setup: New Basic Device. In parameters we will call this checkbox “Game System” which is what will show up from within our interface. Then we choose Checkbox from the Device Type dropdown. Now that we have created the checkbox, we have to add some Device Events so that we can use it.

Creating Events To Control A Device

We will need to create some Device Events that will allow us to send commands when the end-user controls the device from within the interface. These become the macros that we will put our commands for what we want to happen, whether it be to lock a door or set a variable or anything else. We create two new events for every device. They will be the Device Controlled By User events. In parameters, the Device Name or IP must match what we named our Devices exactly. This is how these events get linked to the device we created. We make one for Lock/Turn Off/Close and one for Unlock/Turn On/Open.

Door Locks

For door locks we will have an event for lock and one for unlock and we will insert our commands accordingly.

Checkbox

For checkbox we use our Turn On event to enable our Game System, so we set a variable to True. And for Turn Off, we want to disable so we set the variable to false. The easiest way to do this is to create a Universal Macro that will toggle our variable and update the status at the same time. The Access Control status gets updated using TCL Commands. These commands are the Control: Change Basic Device State and we will create one for on and one for off. This way we can use this macro anytime we want to change the state of the variable and keep Access updated with the correct state. So we could create an Event Timer that happens at 9pm to disable the Game System, and Access would be updated that it was disabled. We will also use this toggle macro to update the initial status in the next step of setup.

This is how the variable would be used to enable/disable our Game System. IF the variable Game System Enabled is True, then the macro will run ELSE nothing happens.

Updating Access With Initial State

The 2-way Access Control interface will not know the state of the device until it has received that information. So we will want to provide it a status update on startup. We will include some TCL Commands into our setup event macro so that every time the module starts up, it will also update the status.

Door Locks

For Door Locks, we will use a TCL Command to query the state of the lock and then use a conditional to send the Access module the correct state. We do this using another TCL Command setup with Access as Control: Change Basic Device State. This is the command we use in order to update the status of the lock.

Checkbox

You can see in the Setup macro that we are going to run our Toggle Game System Variable universal maro. This will update Access with the initial state. So keep in mind that you will want the default state of that variable to be opposite of what we actually want it to start as. So if we want it enabled by default, we will set the initial value of the variable False and then toggle it on startup to True.

Keeping The State Updated

Now that everything is setup and working and showing the proper status, we need to keep it that way. Remember that anytime the status of the device changes, Access Control needs to be updated. With Checkbox, we have built this into our command using the Toggle Game System Variable universal macro anytime we want to change the status will also update Access Control.

Now the only thing left is to create Device Events that will update Access Control if the locks have been manually changed. We will create two Door Lock events from our Z-wave controller module. In these events we will insert the TCL Commands that will update Access Control.

Dash App Feature Tour / Walkthroughs

Welcome to the Dash App Feature Tour!   This page will go over the features available to you when using the Dash App within your Dash OS-powered systems.  These tours may include specific programming guides, file examples, drivers, or simply detailed explanations of the features listed on the Product Description tab.  Use the tabs to the left to select a feature that you would like to learn more about!  Enjoy!

These examples will require a basic understanding of TCL Commands and Device Events.

Using Access Control With MRX Relay & Sensor To Control A Garage Door

By using Dash Access Control in conjunction with an MRX relay output and a magnetic door sensor, we can attain full 2-way control and status of a garage door.

A few things are necessary in order to do this. You need to be able to get wiring form your garage to your MRX and you need to hook up the relay to the door opener. You need to install a door sensor to let the MRX know that the door is closed, a locally installed 4SEN could be used for this.

The first thing to do is add a TCL Command into the Module Startup /Setup Event. This will be a Setup: New Basic Device command. Call it “Create Garage Door” so that we know what it does just be glancing at the macro. We can name the device “Garage Door” and choose Door as the device type.

From within Accelerator, we will then setup the sensor input and relay output. The sensor mode will be Automation Trigger and lets name the device “Garage Door”. We will name the relay output the same. We will use the Check Sensor button in order to tell if the sensor ON means the door is open or closed. In this example we will find that the sensor is ON when the door is closed.

Next we will create our Automation Trigger Macro used for updating Access with the status of the door. This macro will get triggered every time the sensor changes state. This conditional will check IF the sensor is on, it will update Access that the door is closed ELSE it will update access the door is opened. This is accomplished by inserting the appropriate Control: Change Basic Device State TCL Commands into the conditional.

Then all thats left is to create a couple of Device Events for opening and closing the garage door from the Access Control interface. These will be Device Controlled By User events. Remember here that the Device Name has to match exactly what we set up in the beginning. We create one event for open and one for close. In each we will put a simple Conditional based on the status of the sensor since this relay output is essentially a toggle command. So in the pic below, we can see that for Open, it only sends the relay command if the sensor does in fact show the door as being closed.

Using Access Checkbox To Skip The Occurence Of An Event Timer

In this example, we will see how to use an Access Control Checkbox to skip one single occurrence of an Event Timer or an Alarm Clock Macro. This is nice for when we only want an event to happen the next occurence, and then return to the regular schedule. It keeps the user from having to go in and turn it off and then having to remember to go back and turn it back on.

This Access device will start out the same as all others with creating it by using the TCL Command for Setup: New Basic Device. We will use the Checkbox option so that if the box is checked, it will skip the next occurrence. Lets name it Alarm Skip.

This is relatively simple to accomplish as a task. All we are actually doing it changing the state of a True/False variable. We will then use that variable in a Conditional inside the actual event.

This way IF Alarm Skip On is true, it just sets the variable back to false and updates Access that it is now off ELSE it sends the Universal Macro for “Wake Up”. This way it will normally be off and send this macro, but if we turn on skip from Access, it will turn it back off rather than running the macro.

Now we just need to create control form Access for this device and update the status on startup. These will both be accomplished through means of a Universal Macro setup for toggle. The macro will invert our variable and send the respective update to Access. This is what the macro will look like.

Both the Device Events for On and Off will use this same Universal Macro.

We will also use this macro in our startup macro to report the initial state to Access, just remember that since we want false/off to be or primary state, we need to have the variable set as true initially so that when it inverts on startup, it will be set false.

Dash Access Control

How To Buy Dash Access Control Suite

The Dash Access Control Suite can be configured in many ways so it might be a bit confusing as-to how you should purchase it.  This page will go over how the purchasing process of Dash Access works.

  • Dash Access – Single Site License – A single license is required for every home that you wish to install the Dash Access Dash App into.  This is all that is needed for the Dash App to operate.  You do not need to purchase miDoor Hardware if you want to use Dash Access to work with a URC Relay/Sensor or any other Dash Access-created device (Z-Wave Door Locks, Lights, Outlets, etc).  Once you purchase a Dash Access Single Site License, it will be available for installation from your “Install Dash Apps” section of your Project (on your Dash OS Project Page).

Note: If for any reason you have purchased Dash Access and did add the Single Site License but it does not show any Activations Available, please contact us at contact@dashos.net or join the Customer Support Community and ask us for assistance there: Click Here to Join the Customer Support Community

  • myQ Add-On Site License – If you wish to add your myQ Devices to your Dash Access User Interface you can do so by installing a myQ Add-On License to your project.  Using the same method as above, your myQ Licenses should show up for activation to your project(s).  Each myQ License is good for one site and unlimited devices.  It is important to note that this is an add-on and requires a Dash Access Single Site License to work.
  • miDoor (Internal Antenna) – You may add as many miDoor Units as you would like to your purchase.  This unit has an internal Wi-Fi Antenna and does not require the purchasing of any additional components for operation.
  • miDoor (External Antenna) – You may add as many miDoor Units as you would like to your purchase.  This unit uses external Wi-Fi Antenna Connectors so that you can install your own antenna’s to the unit to increase range or move the antenna as-needed to an external location.  Useful when installing miDoor into an enclosure that would normally hurt its Wi-Fi Connectivity.