/
Integration with alarm.com

Integration with alarm.com

With the alarm.com integration enabled, you can manage your BAS-IP panel remotely, keep configuration synchronized and stay informed with real-time events — all from a single dashboard.

The integration is currently available for the following Android 4.4 BAS-IP panels:

The presence of the integration in device firmware does not guarantee support on the alarm.com platform.

For example, BAS-IP firmware 4.0.0 adds alarm.com integration support for AA-14FBS / AA-14FBIS panels running Android 6+. However, availability on the alarm.com platform depends on alarm.com compatibility and rollout status.

The list of supported models may expand over time.
Refer to the official documentation for the latest availability information.
Compatibility and supported firmware availability are defined by alarm.com.

 

Integration setup

  1. Back up your settings and database.

  2. Update the panel to firmware 3.26.7, then install 3.27.1 and wait for the device to reboot.

Update flow:

  • RUT manual update: install 3.26.7 first, then 3.27.1 — skipping intermediate versions is not supported;

  • OTA update: the web interface automatically offers 3.26.7 first, then 3.27.1.

After completing the 3.26.7 → 3.27.1 update flow, rollback to earlier firmware versions may become unavailable.

Firmware version support

Firmware 3.27.1 was the first BAS-IP firmware version that introduced support for alarm.com integration. Newer firmware versions may also be supported. Supported firmware versions are defined by alarm.com and may change over time.

If the installed firmware version is not supported, the integration cannot be activated and the panel web interface displays the firmware version required to activate the integration.

  1. Open the panel web interface by entering its IP address in a browser and logging in as an administrator.

  2. Navigate to Integrations → alarm.com.

  3. Enable the alarm.com integration.

  4. Enter the pairing code or integration credentials required on the alarm.com side and save the changes.

  5. Reboot the panel if prompted.

  6. Open the alarm.com integrator portal and confirm that the BAS-IP panel appears in the device list.

  7. Check that remote management is available:

    • settings;

    • users;

    • numbers;

    • forwarding rules;

    • event delivery.

Знімок екрана 2026-05-11 о 13.06.21.png

When the integration is active, the Web UI intentionally hides a number of cards and settings. The Updates card disappears, and local firmware updates become unavailable.
This is expected behavior, not an error.

Web interface access

When the integration is activated, alarm.com automatically changes the panel administrator password and the web interface access port.

After activation, access to the panel web interface is available only through the alarm.com Partner Portal.

To open the panel web interface, the panel and the administrator workstation must be located on the same local network. If the device is removed from the alarm.com platform, alarm.com sends the current web interface access credentials to the email address associated with the panel.

Resetting the panel does not reset alarm.com integration settings.

 

Firmware compatibility

The integration requires firmware versions supported by the alarm.com platform.

If a non-supported firmware version is installed, the integration may become unavailable or temporarily disabled. In such cases, both the panel web interface and the alarm.com Partner Portal display information explaining that a supported firmware version is required.

The integration remains unavailable until a supported firmware version is installed.

 

Forwarding and call routing

The integration supports forwarding destinations using the adc: prefix.

Example:

adc:1001

The adc: direction works within the existing forwarding logic and does not require a separate routing scheme.

Existing forwarding modes and routing scenarios continue to work without changes to the configuration principles.

Forwarding behavior

Calls can now be delivered both to local indoor monitors and to forwarding destinations configured in the forwarding rules, including alarm.com destinations.

Forwarding rules are now processed even when a local indoor monitor is available.

If forwarding destinations are configured, their execution no longer depends on whether a local indoor monitor is available.

Calls may be delivered simultaneously to multiple recipients.

When configuring alarm.com forwarding scenarios, consider this behavior to avoid unexpected call delivery.