Skip to content

About

Alarm.com integration for Home Assistant, maintained by Selora Homes

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

1 star

Watchers

1 watching

Forks

 
 

Latest commit

 

History

162 Commits

Folders and files

Alarm.com for Home Assistant

This repository is the actively maintained home of the Alarm.com for Home Assistant custom integration, maintained by Selora Homes.

Its goal is to keep the integration compatible with modern Home Assistant releases and to keep developing it as the platform evolves, including compliance with the device registry enforcement requirements introduced in Home Assistant 2025.12.

Repository and issue tracker:

https://github.com/SeloraHomes/ha-alarmdotcom

Community feedback, testing, and contributions are welcome.


Project History

This project has changed hands a few times:

  1. pyalarmdotcom/alarmdotcom and its API client pyalarmdotcom/pyalarmdotcomajax - the original integration and library, created by Justin Wong and developed for years by Elahd Bar-Shai and the pyalarmdotcom contributors. No longer maintained.
  2. ibasebcast/ha-alarmdotcom - a fork by Chris Pulliam that kept the integration working on recent Home Assistant releases and added a vendored API client, camera support, lock unlock attribution, the activity feed, auto-off timers, and more. No longer active.
  3. SeloraHomes/ha-alarmdotcom (this repository) - where development continues.

Many thanks to everyone who built and maintained this integration before us. See License for how their work is credited.

If you installed the integration from one of the earlier repositories through HACS, remove that custom repository and add this one instead (see Installation). Your existing configuration entries are kept.


Maintainer

This integration is maintained by Selora Homes.

The project aims to provide:

  • Continued compatibility with new Home Assistant versions
  • Expanded device support
  • Improved reliability and error handling
  • Long-term maintenance of the integration

Overview

This custom integration allows Home Assistant to interface with Alarm.com using the Alarm.com web platform.

The integration focuses primarily on Alarm.com security system functionality and requires an Alarm.com service package that includes security system support.

Because this integration communicates with Alarm.com cloud services, functionality may change if Alarm.com modifies their platform.


Warning

Safety Notice

This integration is designed for convenience and automation, but it should not be relied upon for safety-critical functions.

Reasons include:

  1. This integration communicates with Alarm.com using unofficial endpoints.
  2. Alarm.com status updates may take time to propagate.
  3. Home Assistant automations may introduce unintended behavior.
  4. This code is community developed and may contain bugs.

For critical alerts such as:

  • Break-ins
  • Fire
  • Carbon monoxide
  • Water leaks
  • Freeze warnings

You should rely on Alarm.com's official monitoring services and mobile applications.

Where possible, use locally controlled Home Assistant integrations for automation. Local integrations continue functioning during internet outages, while this integration requires cloud communication.

Tip

Some alarm.com devices use Z-Wave, so if you have a Z-Wave dongle then you can move the devices from alarm.com to Home Assistant's native Z-Wave integration


Installation and Setup

Installation

Releases are published on the GitHub releases page.

Back up Home Assistant before updating through HACS, then restart Home Assistant.

Install Using HACS (Recommended)

Open your Home Assistant instance and open this repository inside the Home Assistant Community Store.

The button above opens this repository in HACS on your Home Assistant instance (it uses My Home Assistant). If you have not linked an instance, use the manual steps below.

  1. Open HACS
  2. Navigate to Integrations
  3. Click the three-dot menu
  4. Select Custom repositories
  5. Add the repository:
https://github.com/SeloraHomes/ha-alarmdotcom
  1. Select Integration as the category
  2. Click Add
  3. Install Alarm.com
  4. Restart Home Assistant

After restarting:

Settings → Devices & Services → Add Integration → Alarm.com

Open your Home Assistant instance and start setting up a new integration.

Prerequisites

Before setting up this integration you need the following

  1. An active alarm.com account
  2. Know the login for the alarm.com and be able to fill the One-Time Password
  3. Have a device connected to alarm.com

Permissions for a dedicated Alarm.com login

Sign into the Alarm.com website using the exact credentials configured in Home Assistant. Confirm that this login can see and control the devices you want to use. Your main login's permissions do not automatically apply to a separate HA login.

In Alarm.com's login management, grant access to the required device categories. In particular, enable Lights/Thermostats if you expect those devices in HA. Enable the Activity read permission for activity-history features. Reload the integration after changing permissions.

Missing permissions can produce empty device lists or HTTP 423 responses while other device categories continue working. In #115, enabling Lights/Thermostats for the dedicated HA login immediately restored all four lights. Check permissions before reinstalling, capturing network traffic, or trying another build.

Setup

When adding the integration you will be prompted for:

Parameter Required Description
Username Yes Alarm.com account username
Password Yes Alarm.com account password
One-Time Password Maybe Required if your account uses two-factor authentication

Integration Options

These settings can be modified later using the Configure button on the Alarm.com integration card.

Parameter Description
Code Code required for disarming or unlocking via Home Assistant
Force Bypass Bypass open zones when arming
No Entry Delay Skip entry delay sensors
Silent Arming Suppress panel beeps when arming

Some Alarm.com providers may restrict combinations of these options.


Services

This integration exposes the following services, callable from Developer Tools → Actions, automations, or scripts.

Service Purpose Target
alarmdotcom.bypass_sensor Bypass a supported sensor (e.g. a door left open) for the current arm period resource_id field (see the sensor entity's resource_id attribute), optional partition_id
alarmdotcom.unbypass_sensor Remove a bypass from a sensor Same as above
alarmdotcom.set_auto_off Schedule one or more lights to turn off after a duration - see Auto-Off Timers below Standard entity target picker, restricted to this integration's lights
alarmdotcom.cancel_auto_off Cancel a pending auto-off timer Same as above

bypass_sensor/unbypass_sensor take a resource_id, not an entity_id - find this in the sensor entity's own resource_id attribute (Settings → Devices & Services → Alarm.com → the sensor entity → Attributes). set_auto_off/cancel_auto_off use Home Assistant's standard entity target selector instead, since they operate on lights specifically and Home Assistant already has a rich picker for that.

Set a temporary access schedule

The admin-only alarmdotcom.set_temporary_access action updates the temporary schedule for an existing Alarm.com user. Select the integration account and enter the system ID, the user ID from the portal's user page, and the start and end times in ISO 8601 with Z or an explicit UTC offset.

Read a temporary user's saved schedule

The admin-only, response-only alarmdotcom.get_temporary_user_schedule action accepts the same account, system ID, and user ID as the write action. In a script:

- action: alarmdotcom.get_temporary_user_schedule
  data:
    config_entry_id: YOUR_CONFIG_ENTRY_ID
    system_id: "YOUR_SYSTEM_ID"
    user_id: "YOUR_USER_ID"
  response_variable: saved_access

Response fields are temporary_schedule (an object with UTC begin/end, or null) and credential_status (Alarm.com's numeric status, or null). No PIN, raw access document, or arbitrary server description is returned. Status values are not translated into undocumented synchronization guarantees. A null temporary schedule does not mean access is unrestricted; another access type may apply.

This is a standard HA action with response data. An existing MCP connection that supports those actions can call it without integration-specific MCP code, provided it acts as a Home Assistant administrator. Reading confirms what Alarm.com reports, not enforcement or completed synchronization on every lock/panel. User/system name pickers and unrestricted/weekly access management remain outside this build.


Supported Devices

Device Type Actions Status Low Battery Malfunction Notes
Alarm System Arm Away, Arm Stay, Arm Night, Disarm ✔ ✔ ✔
Garage Door Open, Close ✔ ✔ ✔ See MyQ / Security+ 3.0 note below
Gate Open, Close ✔ ✔ ✔ See MyQ note below
Light On / Off / Brightness ✔ ✔ ✔
Lock Lock, Unlock ✔ ✔ ✔
Sensor None ✔ ✔ ✔ Updates depend on the device events reported by Alarm.com
Thermostat Heat, Cool, Auto, Fan ✔ ✔ ✔ Fan-only mode runs for the maximum duration supported by Alarm.com
Water Valve Open, Close ✔ ✔ ✔
Camera Live WebRTC stream, Snapshot ✔ - - Live playback uses the bundled custom:alarm-webrtc-card; snapshots depend on camera support

Note

Garage Doors (MyQ): MyQ garage doors don't natively integrate with Home Assistant, but they do through Alarm.com, making this integration useful if that's what you have. A dedicated local solution like RATGDO is generally preferable for local control.

However, if your opener uses Security+ 3.0 (newer Chamberlain and LiftMaster models), no local solution currently supports it. This integration may be your only path to Home Assistant control.

Gates (MyQ): MyQ gates use Security+ 2.0 with dry-contact wiring, there is no Security+ 3.0 gate. RATGDO and similar adapters can work with them, see the RATGDO wiring guide for specifics.


Supported Sensor Types

Sensor Type Description
Carbon Monoxide CO detectors
Contact Doors and windows
Freeze Temperature threshold sensors
Glass Break / Vibration Standalone or panel-integrated
Motion Motion detection sensors
Smoke Smoke detectors
Vibration Contact Doors, safes, windows
Water Leak sensors

Alarm.com may use different internal identifiers for some sensors. If a supported sensor does not appear in Home Assistant, please open an issue.

https://github.com/SeloraHomes/ha-alarmdotcom/issues


Camera Support

This integration includes WebRTC live-streaming support for Alarm.com cameras.

Setup

  1. The camera card is bundled with the integration and served from /alarmdotcom/alarm-webrtc-card.js.
  2. In storage-mode dashboards the integration attempts to register the JavaScript module automatically. If you manage resources in YAML or automatic registration is unavailable, add that URL as a JavaScript module in your dashboard resources.
  3. Add the card to any Lovelace dashboard:
type: custom:alarm-webrtc-card
entity: camera.your_camera_name

How it works

When the card loads it requests WebRTC credentials through an authenticated Home Assistant websocket command, with camera entity read-permission checks. Tokens are never exposed as entity attributes or stored in recorder history. The card requests refreshed credentials when reconnecting.

Still-image snapshots are requested when supported by the camera and Alarm.com endpoint. Snapshot availability varies by device and account.

A camera listed in the Alarm.com account may not yet be physically installed or online. In that case, an Empty stream info returned warning can occur because no usable stream is available. The warning is throttled per camera. It does not by itself indicate an integration setup failure. If an installed camera streams in the Alarm.com app but not Home Assistant, report that separately.


Auto-Off Timers

Any light can be scheduled to turn off automatically after a duration, using the alarmdotcom.set_auto_off service - useful for things like "turn on for 30 minutes" without building a full automation for every light.

This is deliberately more capable than a plain automation using a "wait, then turn off" action:

  • Survives a Home Assistant restart. The scheduled off-time is persisted. If Home Assistant was offline when a timer was due, the light turns off immediately on startup instead of the timer being silently lost; a timer still in the future is rescheduled for its exact remaining time.
  • The scheduled off-time is visible. Every light with a pending timer shows it directly in its own auto_off_at attribute - no separate helper entity needed to check "how much time is left."
  • A summary sensor ("Active Auto-Off Timers", found on the account's System device) shows how many timers are currently pending account-wide, with a timers attribute listing each affected light and its scheduled off-time.
  • If a light is turned off some other way before its timer fires - manually, from the Alarm.com app, from an unrelated automation - the timer clears itself automatically.

Example: turn on a light for one hour

action: alarmdotcom.set_auto_off
target:
  entity_id: light.front_porch
data:
  duration:
    hours: 1

Example: automatically time out any of a group of lights whenever they're turned on

alias: Auto-off lights after 1 hour
triggers:
  - trigger: state
    entity_id:
      - light.front_porch
      - light.back_porch
      - light.garage
    to: "on"
actions:
  - action: alarmdotcom.set_auto_off
    target:
      entity_id: "{{ trigger.entity_id }}"
    data:
      duration:
        hours: 1
mode: queued

To cancel a pending timer early, call alarmdotcom.cancel_auto_off with the same target.


Lock Unlock Attribution

Lock entities expose three additional attributes: last_unlocked_by, last_unlock_method, and last_unlocked_at.

This is sourced from Alarm.com's own activity history, polled roughly every 15 seconds - a genuinely separate data path from this integration's live state updates, since "who unlocked this" isn't part of the lock's ongoing state, only its history.

Prerequisite: the Alarm.com account/login used by this integration needs the "Activity" read-only permission enabled, or these attributes will never populate at all. Confirmed by a real user - this isn't documented anywhere by Alarm.com itself, so it's easy to miss if the integration's account was set up before this feature existed, or was scoped narrowly on purpose.

Important limitation, confirmed directly from Alarm.com's own data, not a gap in this integration: Alarm.com only attributes a keypad-code unlock to a specific person. Unlocking from the Alarm.com app, the web portal, or manually at the door is not attributed to anyone - last_unlocked_by correctly shows as unset for those, since Alarm.com itself doesn't know who performed them. Lights and switches have no equivalent - Alarm.com does not attribute those to a user at all under any circumstance.

last_unlocked_by doesn't necessarily reflect the most recent unlock, and that's also not a bug. Not every unlock method generates its own distinct, loggable Alarm.com event for every lock model - a manual/inside turn may not be logged at all on some hardware. When that happens, last_unlocked_by simply keeps showing whoever the last keypad unlock was attributed to, even after a more recent manual or remote unlock, since there's no newer event for the poller to ever see. last_unlock_method exists specifically to sidestep this: it reports "keypad", "manual", or "remote" for whatever the most recently tracked unlock actually was, so an automation can gate on "was this actually a keypad entry" directly, rather than relying on a name that might be stale.

Example: a welcome-home announcement that varies by person, gated on method to avoid the staleness pitfall above

alias: Welcome home TTS
triggers:
  - trigger: state
    entity_id: lock.front_door
    attribute: last_unlocked_by
conditions:
  - condition: template
    value_template: "{{ trigger.to_state.attributes.last_unlock_method == 'keypad' }}"
actions:
  - action: tts.speak
    target:
      entity_id: tts.google_translate
    data:
      media_player_entity_id: media_player.living_room_speaker
      message: "Welcome home, {{ trigger.to_state.attributes.last_unlocked_by }}."

Activity Feed

Beyond lock unlock attribution, this integration also fires a curated event on Home Assistant's event bus for other significant Alarm.com activity - arm/disarm, lock/unlock, and camera motion triggers - and keeps a short rolling list of the most recent ones on a "Recent Activity" sensor (found on the account's System device).

This uses the same underlying poll as lock unlock attribution - nothing extra to configure, no additional load on Alarm.com's servers.

What's included by default, and why the list is deliberately curated rather than exhaustive: real captured activity data showed roughly one event every 2-3 minutes during ordinary use, much of it genuinely noisy for automation purposes - every light interaction fires twice (a command event and a state-change event), motion and button presses fire constantly. Alarm.com does not attribute any of those to a specific person either (see Lock Unlock Attribution above), so they carry less unique automation value than the events below:

  • System armed (any mode) or disarmed
  • A lock locked or unlocked
  • A camera detected motion/a person
  • A garage door opened or closed

Garage door events specifically are cross-referenced against this account's known garage door devices (the same ones the garage door cover entity is built from) before being included - this is what lets them in while ordinary window/door sensors, which share the exact same event data shape, stay out of the "Recent Activity" list.

Window/door contact sensor open/close events are still fired on the event bus (they just don't appear in the "Recent Activity" list). This gives automations a second source for those events when a live websocket update is missed.

Example: catch any curated event in an automation

alias: Log all significant Alarm.com activity
triggers:
  - trigger: event
    event_type: alarmdotcom_activity
actions:
  - action: logbook.log
    data:
      name: Alarm.com
      message: "{{ trigger.event.data.description }}"

Filter by trigger.event.data.event_type_name (e.g. ArmedStay, DoorUnlocked, VideoCameraTriggered) if you only want to react to specific kinds of activity.


Data Updates

This integrations uses both Cloud Push and Cloud Polling.

A few things run on a timer rather than arriving live over the websocket. All are configurable via the Configure button on the Alarm.com integration card:

Setting Default What it affects
Activity poll interval 15 seconds How quickly lock unlock attribution and the activity feed reflect real events
Full state poll interval 5 minutes A safety net that re-syncs everything in case a websocket event was ever missed
Camera token refresh interval 30 minutes How often each camera's WebRTC tokens are renewed; lower it if streams stop working before the next refresh

The activity poll interval in particular is worth understanding before turning it down further: it hits an entirely undocumented Alarm.com endpoint with no confirmed rate-limit information. The default of 15 seconds is a deliberate tradeoff for a prompt welcome-home automation experience, not a guarantee it's safe at any value - if you ever run into problems, this is the first thing worth dialing back up.

The rest of the entities in this integration are Cloud Push.


Removing This Integration

Removing this integration is the same as most HACS integrations:

  • Go to Settings → Devices & Services
  • Find the Alarm.com integration card
  • Click the three-dot menu on the card and select Delete
  • Repeat for any additional Alarm.com entries
  • Go to HACS, select the three-dot menu for this integration, then select Remove.
  • Then restart Home Assistant to clear the cache

Development Status

This integration is under active maintenance. The current version is the version field in manifest.json; see CHANGELOG.md for the complete, detailed history.

Highlights from the 2026.7.14.x beta cycle (click to expand)

New features

  • Auto-off timers for lights - see Auto-Off Timers above. Survives Home Assistant restarts and exposes the scheduled off-time as an entity attribute, unlike a plain "wait then turn off" automation.
  • Lock unlock attribution - see Lock Unlock Attribution above. last_unlocked_by/last_unlock_method/last_unlocked_at attributes on lock entities, sourced from Alarm.com's own activity history (an entirely undocumented endpoint, reverse-engineered and verified against real captured data before being relied on). Keypad-code unlocks are the only ones Alarm.com attributes to a name - last_unlock_method (added after real user feedback) reports the method itself (keypad/manual/remote) independent of whether a name is attached, since last_unlocked_by alone can remain stuck showing an earlier keypad user after a later, unattributed unlock.
  • A general activity feed - see Activity Feed above. A curated Home Assistant event (alarmdotcom_activity) fires for other significant activity (arm/disarm, lock/unlock, camera motion), plus a "Recent Activity" sensor with a short rolling history - built on the same poller as lock unlock attribution, no extra load added.
  • Configurable polling intervals - see Polling Intervals above. Both the activity poll (default 15s) and the full-state safety-net poll (default 5min) can now be tuned via the Configure button, rather than being fixed constants - useful for dialing back the activity poll specifically, since it hits an undocumented endpoint with no confirmed rate limit.

Fixed

  • bypass_sensor/unbypass_sensor crashed ('PartitionController' object has no attribute 'values') when called without an explicit partition_id - the auto-resolve-partition logic incorrectly treated a controller as dict-like when it's actually iterable directly, matching every other controller in this integration. There was previously no test coverage for either service at all; both are now covered, using a mock deliberately shaped like the real (iterable, not dict-like) controller so this exact class of bug can't slip through unnoticed again.

Under the hood

  • AlarmBridge.get_activity_history() - the first data source in this integration with no persistent state and no live websocket delivery; it has to be actively polled rather than subscribed to, which is a genuinely different architecture from every device platform this integration otherwise models. The poller (ActivityFeedTracker, originally LockActivityTracker before it grew beyond just locks) now also drives the general activity feed and reads its own interval from the options flow.
  • Garage door disambiguation for the activity feed - garage door open/close now appears in the curated activity feed, cross-referenced against known garage door devices so ordinary window/door sensors (which share identical event data with a garage door) stay correctly excluded.
  • Continued expansion of the automated test suite alongside every change above.
Highlights from the 2026.7.9.3 stable release (click to expand)

Security fix

Arm/disarm code enforcement was silently broken. If you configured a code to require for arming/disarming, entering any correctly-formatted code - not necessarily the one you set - would still successfully arm or disarm. This is now fixed and covered by automated regression tests. If you rely on the code requirement, you should update as soon as practical.

New features

  • A diagnostics page (Settings → Devices & Services → Alarm.com → Download diagnostics) - a downloadable snapshot of everything the integration knows about your account or a specific device, with all credentials and session tokens automatically redacted. Useful for troubleshooting and for attaching to bug reports without needing to dig through logs or worry about leaking a live camera token.
  • Account-wide low/critical battery count sensors - two new entities that track how many devices currently report low or critical battery, with the specific device names available as an attribute, so you don't have to check every sensor individually.

Bug fixes

  • Two real bugs found while adding test coverage: duplicate config entries were never actually prevented, and a crash could occur in the reconnect-recovery path after enough failed connection attempts.
  • Camera diagnostics were silently missing all camera data due to cameras using a different internal discovery path than every other device type - now fixed and verified against a real account with real cameras.
  • Live camera session tokens were being written to Home Assistant's logs whenever debug logging was enabled - this is now off by default and opt-in only, and separately redacted anywhere else this data surfaces.
  • Carried-forward fixes from 2026.7.6: the iPhone/iPad/Safari black-screen camera issue, and a bug where entity state could silently stop updating until a full integration reload.

Under the hood

  • Vendored the pyalarmdotcomajax API client directly into this repository (see "Architecture Note" below) - this was previously a real HACS compliance blocker and a source of duplicated bug reports across two repos.
  • A real, automated test suite now runs in CI on every push and pull request, covering config flow, setup/unload lifecycle, the arm-code security fix, diagnostics (including the redaction itself), and the new battery sensors.
  • mypy now reports zero type errors across the entire codebase, for the first time - ruff, codespell, and taplo all pass cleanly as well.
  • A preemptive fix for a Home Assistant deprecation that becomes a hard error in December 2026 (a config-entry reload pattern used during reauthentication), verified directly against Home Assistant's own source code before shipping.

Architecture Note: Vendored pyalarmdotcomajax

As of 2026.7.6.1b0, the pyalarmdotcomajax Alarm.com API client lives directly in this repository, instead of being installed separately via a git+ URL in manifest.json. As of 2026.7.7.1b0, it's vendored under the deliberately collision-proof name _pyalarmdotcomajax at custom_components/alarmdotcom/_pyalarmdotcomajax/ (see below for why the name changed).

Why: pyalarmdotcomajax was previously a separate repository (originally pyalarmdotcom/pyalarmdotcomajax, then the ibasebcast/pyalarmdotcomajax fork) that this integration depended on via a git+ dependency. In practice, the two repos were never really independent — nearly every bug fix required a version bump in pyalarmdotcomajax, then a matching dependency-pin bump here, then a release of both. Bugs also frequently got reported in both repos as duplicates, since from a user's perspective it's one integration. On top of the coordination overhead, a git+ dependency in manifest.json is a HACS/hassfest compliance issue, since HACS/hassfest strongly prefer plain PyPI-resolvable requirements.

What changed:

  • The library's code (and its git history) now lives under custom_components/alarmdotcom/_pyalarmdotcomajax/. It's imported as _pyalarmdotcomajax (leading underscore), not pyalarmdotcomajax, deliberately: no legitimate PyPI package can use a leading underscore, so this name can never collide with a stray pip-installed pyalarmdotcomajax (e.g. one left over from before this vendoring change). Without that, a missing or broken vendored copy could silently fall back to a stale pip-installed copy instead of failing loudly - which is exactly what happened during beta testing of 2026.7.6.1b0.
  • manifest.json no longer has a git+ requirement; it now lists the library's actual runtime dependencies directly (mashumaro, phonenumbers, pyhumps, typer, beautifulsoup4), which were previously pulled in transitively.
  • The library's internal code is otherwise unchanged and still uses absolute imports internally (e.g. from _pyalarmdotcomajax.controllers.users import ..., updated from the original pyalarmdotcomajax. prefix as part of the rename). This integration's __init__.py adds the vendored directory to sys.path before anything imports it, so those imports keep resolving without needing every file in the library rewritten to relative imports.
  • No functional/runtime behavior changes are intended by this move — it's a packaging change only.

What this means going forward:

  • Bug reports and contributions related to the Alarm.com API client now belong in this repository, not a separate one.
  • The standalone pyalarmdotcomajax repository is no longer the source of truth for this integration; see that repository's own README for its current status.

Project Roadmap

Planned areas of development include:

  • Expanded device coverage across the Alarm.com ecosystem
  • Improved websocket reliability and reconnection handling
  • Expanded automation and scene support
  • Additional device diagnostics and status reporting
  • Continued compatibility updates for new Home Assistant releases
  • Maybe submission of this custom integration as a core integration

Community testing and feedback help guide development priorities.


Contributing

Issues and pull requests are welcome.

Please report bugs or feature requests here:

https://github.com/SeloraHomes/ha-alarmdotcom/issues

When reporting issues include:

  • Home Assistant version
  • Integration version
  • Relevant Home Assistant logs
  • Diagnostics of your alarm.com config entry

Maintainer

This integration is currently maintained by:

Chris Pulliam GitHub: https://github.com/ibasebcast

The maintainer of this fork operates Alarm.com systems professionally and has access to multiple Alarm.com environments, allowing testing across a wider variety of devices and system configurations.

The goal of this project is to ensure the Alarm.com ecosystem remains usable within Home Assistant as the platform evolves.

This fork exists to provide:

  • Continued compatibility with new Home Assistant versions
  • Expanded device support
  • Improved reliability and error handling
  • Long-term maintenance of the integration

Development

You need Python 3.14, uv, and just.

just setup    # create .venv with every dependency and install the git hooks
just test     # run the test suite
just check    # run every lint job (ruff, mypy, codespell, yamllint, taplo, actionlint) on all files

The git hooks are managed by lefthook (lefthook.yml). They lint the files you commit and check that the commit message follows Conventional Commits (feat: ..., fix(camera): ...).

Changes go through pull requests to main. CI must pass before a PR can be merged. PRs are squash-merged, so the PR title becomes the commit message and must be a Conventional Commit too.

Releases

Releases are automatic. When CI passes on main and there are feat, fix, perf or breaking (!) commits since the last release, the Release workflow:

  1. picks the next version, YYYY.M.N, like Home Assistant: N counts the releases in the month from 0 (2026.11.0, 2026.11.1). October 2026 continues at 2026.10.14, after the earlier 2026.10.13.x releases, so that updates keep sorting as newer,
  2. builds alarmdotcom.zip with that version stamped into manifest.json, which is what HACS installs,
  3. publishes a GitHub release with notes generated from those commits.

To publish a pre-release of the next version (YYYY.M.N-bK, e.g. 2026.11.2-b0) for testers, run the Release workflow manually from the Actions tab. just release-preview shows what the next release would contain.


License

Contributions made since the ibasebcast fork are licensed under the Apache License 2.0 - see LICENSE.

This project is derived from pyalarmdotcom/alarmdotcom and pyalarmdotcom/pyalarmdotcomajax, which are licensed under the MIT License, Copyright (c) 2020 Justin Wong. The original code keeps that license; its notice is reproduced in LICENSE-MIT, as the MIT License requires.

About

Alarm.com integration for Home Assistant, maintained by Selora Homes

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

1 star

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages