Alarm.com ceased to function

[ghds514]

The problem

Control panel for alarm.com integration has ceased to function (error log below). This followed update to HassOS 3.09 and persisted in 3.10. Cannot say with certainty that the HassOS update directly led to the problem. EDIT: Now appears unrelated to update.

Environment

HASS.IO (Home Assistant Core) on RPi4

• Home Assistant release with the issue: 0.105.2
• Last working Home Assistant release (if known): 0.105.2
• Operating environment (Hass.io/Docker/Windows/etc.): Home Assistant Core (Hass.io)
• Integration causing this issue: alarmdotcom
• Link to integration documentation on our website: /integrations/alarmdotcom/

Problem-relevant configuration.yaml

alarm_control_panel:
  platform: alarmdotcom
  username: [USERNAME]
  password: !secret [REDACTED]
  code: !secret [REDACTED]

Traceback/Error logs

Mon Feb 10 2020 10:16:14 GMT-0500 (Eastern Standard Time)
Error while setting up alarmdotcom platform for alarm_control_panel
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/pyalarmdotcom/pyalarmdotcom.py", line 188, in async_login
self.state = tree.select(self.ALARM_STATE)[0].get_text()
IndexError: list index out of range

During handling of the above exception, another exception occurred:

File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 159, in _async_setup_platform
await asyncio.wait_for(asyncio.shield(task), SLOW_SETUP_MAX_WAIT)
File "/usr/local/lib/python3.7/asyncio/tasks.py", line 442, in wait_for
return fut.result()
File "/usr/src/homeassistant/homeassistant/components/alarmdotcom/alarm_control_panel.py", line 48, in async_setup_platform
await alarmdotcom.async_login()
File "/usr/src/homeassistant/homeassistant/components/alarmdotcom/alarm_control_panel.py", line 70, in async_login
await self._alarm.async_login()
File "/usr/local/lib/python3.7/site-packages/pyalarmdotcom/pyalarmdotcom.py", line 197, in async_login
'#{}'.format(self.ERROR_CONTROL))[0].attrs.get('value')
IndexError: list index out of range

Additional information

A visit to the alarm.com site suggests that the login process may have changed slightly.

[Tangston311]

A number of us are seeing this issue. See link for discussion on Home Assistant Community:

https://community.home-assistant.io/t/alarm-com-list-index-out-of-range/170670

I'm on HA 100.1 and changed nothing in HA - it just stopped working this morning with exactly that same error. It was working fine as of last night.

[ghds514]

Community discussion suggests HassOS update is not relevant to the problem.

[ziptbm]

I'm seeing this as well on 0.105.2. Worked fine yesterday. Started overnight and has produced the exact same set of errors as described above.

[Quentame]

@ghds514 May you fill the issue template ?

[ghds514]

DELETED, First post edited.

[Quentame]

@ghds514 It's the old template. Click "New issue", and "Get started" to find the new one.

Also, do not create a new comment but edit the first one ! (3 dots on the top right of your comment to edit)

[Tangston311]

Btw it looks like the issue is no longer occurring for some folks, including me (see HA Community discussion linked above)

[ghds514]

Unfortunately, the issue is persisting for me but I will keep an eye on it.

[ghds514]

Several reports in the community of the integration resuming normal function following reboot. However, following several reboots, it remains down for me.

[Quentame]

Can you try to remove the integration, reboot, add the integration again and reboot ?

_{Sent with GitHawk}

[ghds514]

Yes, I did try that by commenting out the integration in my configuration.yaml file, rebooting once, re-including the integration, and then rebooting again. Unfortunately, the problem persists for me.

[Quentame]

Any help on this @jnewland ?

May you also add yourself as codeowners ?

[jnewland]

Hey @Quentame! I can report that my use of this integration did experience some similar problems a few days ago but everything is now working as expected. From the information reported here it looks like something briefly changed about alarm.com's PDA login flow, and since it's changed back my hunch is that it was just temporarily broken. A Home Assistant restart should re-establish connectivity.

[ghds514]

Reboots seem to have helped many. However, I have rebooted many times in an effort to see this resume and that has not been successful.

[ghds514]

In the latest attempt, I have tried entering an intentionally incorrect password to see what the result would be. The error log is exactly the same as earlier reported. Should I be looking to delete the files from the integration off my Pi and then reboot?

[ghds514]

Solved. I had enabled two factor authentication in the past. Whatever update occurred on the alarm.com site was preventing HA from gaining access without ever texting out the authentication code. Now that it is back in, I will see if I can re-enable 2 factor or if I must live without it.