You are using an unsupported browser. Please update your browser to the latest version on or before July 31, 2020.
close
You are viewing the article in preview mode. It is not live at the moment.
Looking for Z-Box Hub Support? Please click here to access the Z-Box Hub Support Portal.
Home > General Questions > Alarm.com and Z-Wave: Avoid Compatibility Surprises
Alarm.com and Z-Wave: Avoid Compatibility Surprises
print icon

If you have ever tried to add a Z-Wave device to an Alarm.com system and gotten unexpected results, you are not alone.

 

One user includes a device and it works perfectly. Another person using the same Alarm.com app cannot get the device to include at all. A third gets it paired, but only basic controls appear while advanced features are missing.

From the outside, this feels inconsistent. In reality, it is completely logical once you understand how Alarm.com systems are structured and who controls what.

Alarm.com Is Not the Z-Wave Hardware Controller

Alarm.com is the cloud platform and mobile app. It connects your system to the internet and gives you remote access, automation rules, and account management. It is not the physical hardware Z-Wave controller inside your home. The actual controller is the hardware installed on site. That might be:

  • An Alarm.com automation hub

  • A security panel from Qolsys

  • A security panel from 2GIG

  • Another compatible gateway or panel

That hardware determines:

  • Which Z-Wave devices can be added

  • Which features are supported

  • How devices appear in the interface

  • How automation behaves

When you include a Z-Wave device, it pairs directly with the hardware controller, and it is the hardware controller that decides what to allow. The Alarm.com app simply displays what the controller provides. Two homes can use the same Alarm.com app and support completely different devices because the hardware behind the app is different. 

Two Types of Alarm.com Systems

Not all Alarm.com systems are built the same. The type of hardware installed matters more than the app.

 

Alarm.com Automation Hubs

Some homes use hubs designed and managed directly by Alarm.com. Examples include:

Because Alarm.com controls both the cloud platform and the firmware inside these hubs, it can directly integrate specific third party Z-Wave devices.

When a device is officially supported, the hub firmware includes:

  • The device fingerprint

  • Correct command mappings

  • Proper interface controls

  • Supported configuration parameters

This results in clean inclusion and full feature access. Supported Zooz devices tend to work reliably on these Alarm.com branded hubs because the integrations are intentionally built into the firmware.

 

Security Panels Connected to Alarm.com

Other homes use security panels from manufacturers like Qolsys or 2GIG.

These systems connect to Alarm.com and use the same mobile app. However, the Z-Wave controller lives inside the hardware panel, and the panel manufacturer controls the firmware.

That means the panel decides:

  • Which devices can be included

  • Which command classes are supported

  • What features appear in the interface

  • How automation options are exposed

Alarm.com displays the result, but it does not override the panel’s design. This is why device support can vary significantly between systems that appear identical in the app.

Dealer-Controlled Capabilities and Account Permissions

In addition to hardware limitations, there is another important layer: dealer configuration. Every Alarm.com account is managed by an alarm dealer. Dealers have the ability to enable or disable capabilities at the account level. These settings can directly affect:

  • Which device categories are visible in the app

  • Whether certain device types can be added

  • Access to advanced automation features

  • User-level permissions

  • Visibility of specific controls

For example, a dealer can disable support for certain device classes or automation features within an account. If that capability is turned off, the app will not present the option to add or control those devices—even if the hardware technically supports them. This means two customers with identical hardware may still see different behavior depending on how their dealer has configured their account.

 

For installers, this is an important troubleshooting step. If a device should be supported by the hardware but cannot be added or does not display correctly, the dealer-level feature configuration should be verified before assuming a compatibility issue.

For consumers, this explains why “it works for my friend” is not always a reliable comparison. The dealer managing the system plays a role in what is enabled and only they can access the system to make these changes.

Why Z-Wave Certification Does Not Guarantee Full Support

Z-Wave is designed as an interoperable standard, and as such, certified devices follow defined communication rules called command classes. All Zooz devices are Z-Wave certified, so they accurately follow the required command classes to support interoperability. In theory, that means devices should work across systems; however, in practice, security panels often limit which devices they fully support. This isn't a device issue, it'a hardware panel-imposed limitation. 

 

Controlled Device Lists

Many hardware panels/hubs maintain internal device databases within their firmware. If a device is in that database, the panel knows exactly how to handle it. It can expose the correct settings, automation triggers, and configuration options. If a certified device is not in the database, several things can happen:

  • It may include as a generic device

  • Only basic controls may appear

  • Advanced features may be hidden

  • Inclusion may fail entirely

This reflects how the panel firmware was written, and it does not mean the device is defective or non compliant.

 

Manufacturer Ecosystems

Security panels are often designed around branded accessories, and limiting third party integrations keeps installations predictable and easier to support at scale. For installers and homeowners, the key point is simple.

While Z-Wave certification ensures standard communication, the panel firmware still determines how much of that communication is actually used.

Why Zooz Devices Sometimes Work Anyway

Customers often report that a Zooz device includes successfully even when it is not officially listed as supported. There are a few technical reasons this can happen.

 

Generic Device Fallback

Many panels include fallback support for common device types like switches and dimmers. If a device reports standard on off or multilevel commands, the panel may allow it to include as a generic control with support for basic functionality (on/off and dimming control. Meanwhile, the available advanced may not appear, such as:

  • Scene control

  • Custom configuration parameters

  • Multi endpoint controls

  • Specialized reporting

The panel treats the device as a simplified version of itself.

 

Shared Command Classes

Devices that rely on very common command classes are more likely to function at a basic level, like light switches, dimmers, and basic on/off plugs. Devices that depend on advanced features like central scene commands or complex endpoint structures are more likely to experience limitations unless the panel firmware explicitly supports them. It's important to note that successful inclusion does not always mean full feature support. An excellent example of this is the ZAC38 Range Extender. It can be included to nearly any hub, and it will act as a repeating device to strengthen the mesh. However, it's secondary function, to report power outages, is not exposed on most panels. 

Official Zooz Integrations for Alarm.com Hubs

The following Zooz devices have been formally integrated into these specific Alarm.com automation hubs. 

Automation Hubs

Zooz Integrated Devices

Official integration means the hub firmware includes the required device fingerprint, command mappings, interface definitions, and configuration handling. On supported Alarm.com automation hubs, these devices are expected to include cleanly and operate as expected.

What to Check Before Buying a Z-Wave Device

If you remember one thing, remember this: Alarm.com provides the cloud service and app. The physical hardware controller determines compatibility.

Before purchasing a Z-Wave device for use with your Alarm.com system, confirm:

  • The exact model of hub or alarm panel installed

  • Whether it is an Alarm.com automation hub or a third-party security panel (Qolsys, 2GIG, etc.)

  • Whether your dealer has enabled the necessary capabilities on your account

  • Whether the specific device is officially integrated for that hardware

Compatibility can vary even between panels from the same manufacturer. Simply knowing that a system “uses Alarm.com” is not enough. Confirming the hardware and dealer configuration first is the most reliable way to avoid surprises and ensure a smooth installation.

Feedback
0 out of 0 found this helpful

Have you tried our virtual assistant chatbot? This AI tool can help you find answers from thousands of articles in our Knowledge Base quickly. Find it in the bottom righthand corner of the page.

Need more help? Our friendly team is ready to help you with any questions or concerns you may have about Zooz devices. Click here to submit a support ticket.

Are your devices registered? Extended warranty and firmware access is available for registered Zooz customers. Click here to submit your registration form.

Find the latest Zooz devices and great Z-Wave deals at The Smartest House.
 
scroll to top icon