Access Control Database Control4 Driver License

Partner: HouseLogix
The HouseLogix Access Control Database (HACD) is the first driver of it's kind developed for the Control4 system; leveraging the power of Lua we have created a secure, easy to use, and fast graphical interface for managing users.

MSRP: $299
Login to view pricing

Supports 2.5.3+

 This device driver interfaces with supported RFID card readers, door locks and even security systems, while providing a powerful administration panel for managing user access.

Think of it as a central location to which card readers (or other devices) connect and check for user authorization.

Driver Features:

  • Optionally limit the days of the week, hours, and even calendar dates that a user is allowed access.
  • Support for up to 500 users.
  • Open API that can easily work with a number of RFID, card, or biometric readers.
  • Built-in web server for easier management. Works with any computer, tablet, or phone.
  • Secure! User management is done via secured tokens to help prevent unauthorized access. Plus, you can manually or programmatically start and stop the web server to guarantee it's not open to attack when unused.
  • Flexible driver events all you to program actions based on user access granted or denied, plus a high level access or denial event.
  • Supports the following languages
    • English
    • Spanish
    • French
    • German

Dealer Resources:

Driver License:  Site (one required per project)

v3.0
 - Add "Log" button to login screen to allow log viewing without requiring authorization.
 - Add "Database Title" property to allow for custom naming.

v2.1
- Add support for Dutch locale.

v2.0
- Adds support for French, German, and, Spanish locales.

v1.1
- Increase maximum users in database from 300 to 500.
- Added USER_ID variable
- Added USER_NAME variable

-------------------------------------------------------------------------------------------
OVERVIEW
-------------------------------------------------------------------------------------------
This driver is a user management warehouse - a central location to which card readers connect and check for user authorization.

The premise is simple: Use this driver to grant users access and manage their accounts. Supported card reader and door lock drivers
bind to this driver in Control4, and check for access.

To provide a friendly and flexible user interface for managing users, this driver generates a web server application. The administrator
can then connect to this web server and can easily manage their access control system.

-------------------------------------------------------------------------------------------
SETUP
-------------------------------------------------------------------------------------------
Add this driver to your Control4 project. Add the appropriate card reader driver to the project, and bind it to the Database (this driver).

On the Access Control Database driver, go to the Actions tab, and click "Start Server".

Browse to http://Your-Controller-IP:8000/ in your web browser. If you have not added a username/password on the driver Properties tab,
you will be prompted to setup an account the first time you access the application.

Log in, go to the Home page, and click "Add New".

Enter the Name and Access Number for the new user. Ex: "John Doe", "123456789".

You may optionally limit the days of the week, hours, and dates that a user is allowed access.

Click "Submit". When card # "123456789" is read on the card reader driver, it will connect to the database, and check for access.
If authorized, the database will approve access and log the time and date "John Doe" was granted access.

Remember to stop/shutdown the server when you are finished with the application. This provides an added security layer.
This can be accomplished by programming a custom button, or clicking "Shutdown Server" inside the web server application.

-------------------------------------------------------------------------------------------
APPLICATION USAGE
-------------------------------------------------------------------------------------------
For more specific information pertaining to the use of the access control web server application, see the Help page in the application.

-------------------------------------------------------------------------------------------
PROPERTIES
-------------------------------------------------------------------------------------------
Server Status:
Shows if server is running or stopped.

Port:
Port that the server runs on, default 8000.

UserName:
Optional admin username, if not set here, you will be prompted to create a username/password on first connect to server.

Password:
Optional admin username, if not set here, you will be prompted to create a username/password on first connect to server.

-------------------------------------------------------------------------------------------
COMMANDS
-------------------------------------------------------------------------------------------
Start Server:
Start the web server.

Stop Server:
Stop the web server. It is recommended to turn off the server when it is not in use. This can easily be tied to a custom button.

Reset Admin Account:
Wipe out the current admin account, you will be prompted to create a new one on next connect to server.

-------------------------------------------------------------------------------------------
EVENTS
-------------------------------------------------------------------------------------------
Access_Verified:
This event fires when ANY user is granted access.

Access_Denied:
This event fires when ANY user is denied access.

Verified_User_#:
This event fires when a specific user ID is granted access.

Access_Granted_Reader_#:
This event fires when the reader on binding # reads a card that is granted access.

Access_Denied_Reader_#:
This event fires when the reader on binding # reads a card that is denied access.

-------------------------------------------------------------------------------------------
PROGRAMMING EXAMPLE
-------------------------------------------------------------------------------------------
A simple programming implementation:

UserID #1 "John Doe" scans his access card/badge on Reader 1, at the Front Door.

Event: "Access_Verified" is fired, and the lights in the building are turned on.

Event: "Access_Granted_Reader_1" is fired, and the Front Door is unlocked via relay.

Event: "Verified_User_1" is fired, and "John Doe's" favorite radio station begins playing in his office.

-------------------------------------------------------------------------------------------
CONNECTIONS
-------------------------------------------------------------------------------------------
Access Reader #:
Connects the card reader to the database.

Related products