v4.0.1-beta.2 authentication issue with alarm.com with workaround

[Grigolla]

v3.0.15 authenticates with alarm.com fine but the latest beta 4.0.1-beta.2 will not.

Work around is to first install v3.0.15 and configure with login then re-download the 4.0.1-beta2 that works with the latest HA Core

Claude gives this as the reason:

Great question — and it reveals something important.
When you were on v3.0.15, it used an older version of the underlying pyalarmdotcomajax library that had a different (and working) OTP/MFA flow. The login worked fine.
When you upgraded to v4.0.1-beta.2, it pulled in the completely rewritten pyalarmdotcomajax v0.6.x library as part of the upgrade. That new library handles the MFA cookie step differently — and that's exactly where the bug is. The new code can't find the cookie in Alarm.com's response.

Currently using:
alarmdotcom v4.0.1-beta.2
HA Core version 2026.5.1

[jbs7106]

"Work around is to first install v3.0.15 and configure with login then re-download the 4.0.1-beta2 that works with the latest HA Core"

This worked for me.

[Grigolla]

There was an issue i found that Alarm.com stops sending updates to HA after some time. My work around was to set HA to restart at 3am every morning will the bug is fixed.

Claude:

That confirms it — the push notification connection from Alarm.com to HA is dropping and not recovering on its own. Restarting HA re-establishes it.
This is a known v4.0 beta issue. Looking back at the release notes we checked earlier, v4.0.0-beta.9 (May 23, 2026) specifically addressed this:

"Missed State Changes: Integration now performs a pull-update after disconnecting and reconnecting to the push-notification server."

[numericOverflow]

+1 Having this issue too