🇧🇷 Versao em Portugues
4Drivers

4Drivers Yale Connect Hub Hub

Manufacturer: Yale / ASSA ABLOY Platform: Yale Connect Brazil Minimum OS: Control4 3.0.0

Overview

The 4Drivers Yale Connect Hub driver integrates the Yale Connect Brazil (ASSA ABLOY) platform with the Control4 system. It manages cloud authentication, synchronizes locks registered to the account, and communicates with individual lock drivers (4Drivers Yale Connect Lock) installed in the project.

HTML Interface

Accessible from any Control4 Navigator — physical touchscreen, iOS/Android app, and browser.

Yale Connect Interface
Full interface with lock list, status panel, access history, and daily activity chart
SectionDescription
LocksLists all visible locks with state (Locked/Unlocked) and Online/Offline indicator
Status PanelDetails for the selected lock: name, state, battery alert, Lock and Unlock buttons
Access HistoryEvents by date: time, lock, state, access method, and user
Activity ChartVisual timeline from 0:00 to 23:59 — green bars (unlocked) and red bars (locked). Hover shows exact time.
ShareExports the history as text for sharing or copies it to the clipboard

Requirements

Properties

Yale Connect User Data

PropertyTypeDefaultDescription
EmailString—Login email for the Yale Connect Brazil account
PasswordPassword—Yale Connect account password (masked field)
Icon TypeListYaleIcon displayed on the Navigator

Interface Preferences

PropertyTypeDefaultDescription
Add Control4 Lock DriverListYesYes: automatically adds the Control4 door lock proxy when a Lock driver is first connected. No: skips that step (use when the proxy already exists in the project).
LanguageListPortugueseLanguage for the HTML interface: Portuguese, English, or Spanish

Driver License

PropertyTypeDefaultDescription
License KeyStringTrialLicense key provided by 4Drivers. Use Trial for evaluation.
ValidacaoStringautoLicense status — filled in automatically (read-only)
Developer UsePassword—Reserved for 4Drivers use

Driver Info

PropertyTypeDefaultDescription
Debug ModeListOffWhen On, displays hub-to-lock driver traffic in the Composer log. Disable after commissioning.
StatusString—Current driver state: authenticated, error, offline (read-only)
Driver VersionString—Installed driver version (read-only)

Actions

ActionWhen to use
List LocksSynchronizes locks from the Yale account and detects installed Lock drivers. Run whenever you add a new lock to the app or install a new Lock driver.
LoginAuthenticates with the configured credentials and runs the synchronization. Use on first setup or after changing the password.
Force PollRe-authenticates and refreshes the state of all locks. Useful to force an immediate update.
Get Status FechadurasQueries the current state without re-authenticating — uses the token already obtained.
Get Access HistoryFetches the access history for the current day.

Events

EventWhen it fires
Hub OnlineCommunication with the Yale API has been restored after an offline period
Hub OfflineThe driver detected a communication failure with the Yale API

Use these events in programming to notify the end user when the connection to the Yale cloud is lost or restored.

Step-by-Step Setup

1 — Add the Hub driver to the project

  1. Copy 4Drivers_Yale_Connect_Hub.c4z to the Composer drivers folder
    Windows: C:\Users\[user]\Documents\Control4\Drivers\
  2. In Composer Pro, search for 4Drivers Yale Connect and drag the 4Drivers Yale Connect Account driver into the project

2 — Enter credentials

  1. Open the driver's Properties tab
  2. Fill in Email and Password with the Yale Connect account details
  3. Save (File > Save) — the driver detects the credentials and logs in automatically
  4. Wait a few seconds and check the Status property — it should show Authenticated — X lock(s)
If an authentication error appears, confirm the email and password by logging into the Yale Connect app on your phone. You can also trigger login manually via Actions > Login.

3 — Install the lock driver

  1. Copy 4Drivers_Yale_Connect_Lock.c4z to the Composer drivers folder
The lock driver does not need to be added manually to the project. The List Locks action automatically creates and configures one driver instance for each lock found in the Yale account.

4 — Synchronize locks

  1. In the Hub driver's Actions, click List Locks
  2. The driver automatically creates a Lock driver for each account lock, already linked and configured with the correct ID
  3. Check the Status property for the count of detected locks

5 — Configure each Lock driver

  1. Open the Properties of the automatically created Lock driver
  2. Adjust Lock Name Selected to a user-friendly name if desired
  3. Set Visible on Interface: Yes (shows in UI) or No (hidden — useful for service or private area locks)

6 — Configure Navigator visibility

In the room properties, on the Navigator tab, set the 4Drivers_Yale_Connect_Hub driver as Visible in the desired Experience Menu — we recommend Security.

Navigator configuration
Navigator tab — driver set as Visible in the Security menu

7 — Verify the HTML interface

  1. On the Navigator, access the Yale Connect item
  2. Confirm that locks appear with the correct state (Locked/Unlocked)
  3. Test the Lock and Unlock buttons
  4. Access Access History and click View History to validate the records

8 — Finish

  1. Make sure Debug Mode is set to Off
  2. Save and publish the project
Setup complete. The driver will automatically renew the authentication token and keep lock states updated by polling.

Troubleshooting

ProblemSolution
Login error / Invalid tokenConfirm email and password in the Yale Connect app. Click Login in Composer.
Locks not appearing in the interfaceRun List Locks. Verify that the Lock drivers are bound to the Hub.
Lock appears but does not respondCheck the Online/Offline indicator. If Offline, the physical Yale hub may have lost internet connectivity.
History shows no eventsCheck if the date has activity in the Yale app. History is fetched in real time from the cloud.

Technical Information

ItemValue
ProtocolHTTPS — Yale Connect Brazil API
AuthenticationBearer Token with automatic renewal
State pollingAutomatic polling
Hub-lock communicationControl4 virtual binding (ID 100, class 4d_Yale_Connect)
PersistenceToken, IDs, and lock map in PersistData — survives reboot
Minimum OSControl4 3.0.0

Change Log

VersionDateChanges
105507/24/2026Initial adjustments
105007/19/2026Initial release