ZOOM – Universal Notifier v20261119

Driver: Control4 DriverWorks Platform: ZOOM drivers Minimum OS: 3.0.0

PT EN

Overview

ZOOM Universal Notifier is the notification hub for ZOOM drivers. Locks, alarms, sensors and other ZOOM drivers report their events to it, and the Notifier sends them to the chosen channels:

Every notification has a severity: Critical (jammed lock, device offline, alarm), Warning (low battery, door left open) or Info (lock unlocked or locked). The customer chooses, on a Navigator screen, what goes to each channel. There are also quiet hours, pause and protection against repeated alerts.

The driver is free, and a single Notifier serves every ZOOM driver in the project.

Prerequisites

Installation

  1. Add the ZOOM – Universal Notifier driver to the project in Composer Pro (one per project).
  2. In the Connections tab, connect the Notifier connection of each ZOOM driver to the Notifications connection of the Universal Notifier. Several drivers can share the same connection.
  3. In the properties, fill in Home Name (shown at the start of each alert) and enable the channels you want (see Setting up the channels).
  4. Run the Send Test Notification action to check that the channels receive it.
  5. Enable the interface in Navigator: select the room → Navigator tab → Menu Settings → set ZOOM Universal Notifier as Visible in the desired experience (e.g. Security).
Each connected driver shows up in the interface, with the list of events it can generate, a few seconds after being connected. If it does not, run the Refresh Connected Drivers action.

How notifications are chosen

The choice happens in two places:

  1. In the source driver itself (e.g. the lock). On the driver's settings screen, or in the Send Notifications property, the customer chooses whether the driver reports all events (every lock and unlock), alerts only (default: critical and warnings) or nothing, and can turn each event on or off.
  2. In the Universal Notifier, which decides which channels each event goes to.

In the Notifier, each alert goes through these rules, in this order:

RuleWhat it does
PauseWhile notifications are paused nothing is sent, but everything stays in the history.
Driver offA whole driver can be turned off on the What to send screen.
Do not repeatThe same event from the same device is not sent again within the chosen time (default 10 min).
Quiet hoursDuring the chosen period only critical alerts go out (if allowed). Integrator alerts ignore quiet hours.
ChannelFor each channel, the choice made for that event applies (always or never). With no choice (automatic), the channel's minimum severity set in Composer applies.

Navigator interface

Tap the Notifier icon in Navigator (touchscreen, iOS/Android app). The screen has three tabs and the PT / EN / ES languages.

Notification history
History: latest notifications, with severity, source driver and where each one was sent, or why it was not (Repeated, Quiet, Paused...).
What to send
What to send: each connected driver with its events. Tap a channel to switch between automatic, always and never.
Settings
Settings: pause, quiet hours, repeat window and the status of each channel, with a test button.

On the What to send tab, an event turned off in the source driver itself shows Turned off in the driver itself: to receive it, turn it on in that driver's settings screen.

Setting up the channels

Control4 Push

On by default. It uses the project's Push Notification agent: add the agent and the users in Composer. Default minimum severity: warnings and critical.

E-mail

Set up the Control4 Email Notification agent (outgoing server). In the Notifier, turn on Email Enabled and fill in Email Recipients with one or more addresses separated by comma.

WhatsApp

Turn on WhatsApp Enabled, choose the WhatsApp Service, paste the key in WhatsApp API Key and fill in WhatsApp Numbers with country and area code (e.g. 5551999998888), separated by comma. Messages go out a few seconds apart, as the services require.

Telegram

Create a bot with @BotFather and copy the token to Telegram Bot Token. Each person (or group) must send a message to the bot first; then put the chat ID in Telegram Chat IDs (several separated by comma).

Webhook

Fill in Webhook URL with the address that will receive the alerts. Each alert is sent with home, severity, title, message, source and date/time.

Integrator

Technical alerts, such as a module or device offline and failures, usually matter more to the integrator than to the client. Turn on Integrator Enabled and fill in Integrator Email and/or Integrator WhatsApp (with country and area code, separated by comma). E-mail uses the project's Email Notification agent; WhatsApp uses the service chosen in the WhatsApp section, even if the client's WhatsApp is off.

In automatic mode the integrator gets only the technical alerts from ZOOM drivers, from the Integrator Minimum Severity level up (default: alerts and critical), also during quiet hours. In the What to send screen the Integrator column turns each event on or off, and the client can turn these alerts off in the other channels. Fill in Home Name so the integrator knows which home the alert is from.

Properties

PropertyDescription
Driver InformationDriver messages, such as a channel failing to send.
Log Level / Log ModeLog detail level and destination.
StatusActive or Paused.
Connected DriversHow many drivers are connected to the Notifier.
Last NotificationDate, time and title of the last alert received.
Push Agent / Email AgentOK when the Push Notification or Email Notification agent was found in the project; Not found when the agent still needs to be added.
Home NameName shown at the start of each alert (e.g. Beach House - Lock jammed).
Repeat Suppression (min)Time (0–120 min) during which the same event from the same device is not sent again. 0 turns it off. Default: 10.
Quiet Hours, Quiet Hours Start, Quiet Hours EndQuiet hours (HH:MM format, may cross midnight).
Critical During Quiet HoursWhether critical alerts are sent even during quiet hours. Default: Yes.
Push Enabled / Push Minimum SeverityTurns on Control4 push and its minimum severity in automatic mode.
Email Enabled, Email Recipients, Email Minimum SeverityE-mail: recipients separated by comma.
WhatsApp Enabled, WhatsApp Service, WhatsApp API Key, WhatsApp Numbers, WhatsApp Minimum SeverityWhatsApp: service, key and numbers.
Telegram Enabled, Telegram Bot Token, Telegram Chat IDs, Telegram Minimum SeverityTelegram: bot token and chats.
Integrator Enabled, Integrator Email, Integrator WhatsApp, Integrator Minimum SeverityTechnical alerts for the integrator: e-mails and WhatsApp numbers. Default: alerts and critical.
Webhook Enabled, Webhook URL, Webhook Minimum SeverityWebhook: destination address.

Minimum severity: Critical Only, Warning and Critical or All. Quiet hours and the repeat window can also be changed by the customer in the interface.

Actions

ActionDescription
Send Test NotificationSends a test alert (critical) to every enabled channel.
Refresh Connected DriversAsks every connected driver for its event list again.
Forget Disconnected DriversRemoves from the interface the drivers that are no longer connected, along with the choices made for them.
Clear HistoryClears the notification history.

Commands, connections and events

Programming commands

CommandDescription
Send NotificationSends a programming alert with severity (Critical, Warning or Info), title and message. It shows up in the interface as Programming and follows the same rules.
Pause Notifications / Resume NotificationsPauses and resumes sending (e.g. pause while the family is home).

Connections

ConnectionDescription
NotificationsReceives the Notifier connection of ZOOM drivers. Accepts several drivers.

Events

EventWhen it fires
Notification ReceivedAny alert arrived (even if paused or filtered).
Critical NotificationA critical alert arrived.

Variables: LAST_TITLE, LAST_MESSAGE, LAST_SEVERITY and PAUSED, for use in programming.

Troubleshooting

SymptomWhat to check
Connected driver does not show in What to sendCheck the connection in the Connections tab and run Refresh Connected Drivers. The source driver must be on a version that supports the Notifier.
Alert shows in the history as No channelNo enabled channel accepts that severity. Lower the channel's minimum severity or mark always on the event.
Lock and unlock alerts do not arriveBy default drivers report alerts only. On the lock driver's settings screen, choose all events or turn on the desired event.
Push does not arriveCheck the Push Notification agent in the project and that the user has the Control4 app with notifications allowed.
WhatsApp or Telegram shows Failed in SettingsCheck the key or token and the numbers. On Telegram, the person must have sent a message to the bot first.

Licensing

ZOOM Universal Notifier is free to use with ZOOM drivers and needs no license of its own: it only sends when at least one licensed (or trial) ZOOM driver is bound to the Notifications connection. Without one, the status shows "Waiting for a licensed ZOOM driver" and the history lists notices as "No ZOOM driver". Source drivers keep their own licenses. WhatsApp services may charge separately, depending on the customer's plan.

Support and Updates

Release Notes

VersionDateDescription
2026111911/19/2026WhatsApp through the official ZOOM number with the ZOOM WhatsApp AI driver, with no third-party account. New integrator channel: technical alerts, such as a device offline, go to the integrator e-mail and WhatsApp. Fixed: turning a driver back on, resuming from pause or turning quiet hours off in the Navigator screen now takes effect right away. The driver is now named ZOOM Universal Notifier: the ZOOM drivers bound to it need the 11/19/2026 version or newer.
2026102310/23/2026Initial version: Control4 push, e-mail, WhatsApp, Telegram and webhook; per-event and per-channel choice on the Navigator interface (PT/EN/ES); quiet hours, pause, repeated-alert protection and history. Replaces the ZOOM WhatsApp Message driver.