Verification Request: @omarshahine/homebridge-alarm-dot-com

Plugin Name

@omarshahine/homebridge-alarm-dot-com

Link To GitHub Repo

https://github.com/omarshahine/homebridge-alarm-dot-com

Plugin Icon (Optional)

homebridge-node-alarm-dot-com also targets Alarm.com and currently covers more device classes. This plugin is a clean-room implementation whose differentiators are first-class two-factor authentication (in-UI OTP enrollment via a custom Config UI X page or bundled CLI, with a persisted trusted-device token — the existing plugin requires manually copying a browser cookie from DevTools), a single long-lived session (no timed re-logins, which have historically triggered Alarm.com rate limiting), and WebSocket real-time updates. Additional device classes are on the roadmap.

The plugin does not offer the same nor less functionality than that of any existing verified plugin.

🟢 Yes

The plugin successfully installs and does not start unless it is configured.

🟢 Yes

The plugin does not require the user to run Homebridge in a TTY or with non-standard startup parameters, even for initial configuration.

🟢 Yes

The plugin does not contain any analytics or calls that enable you to track the user.

🟢 Yes

If the plugin needs to write files to disk (cache, keys, etc.), it stores them inside the Homebridge storage directory.

🟢 Yes

The plugin does not throw unhandled exceptions, the plugin must catch and log its own errors.

🟢 Yes

More Information

No response

Review the plugin repository at https://github.com/omarshahine/homebridge-alarm-dot-com against the verification checklist in this issue. Start by checking the installation, configuration, storage, authentication, error-handling, and tracking claims; done means the plugin satisfies the stated requirements and can be verified.