Verisure integration fails log in

[PEHowland]

The problem

My Verisure integration has stopped working. Home Assistant logs suggest that it is due to fauiled log in credentials. I can log in to the Verisure My Pages using the credentials correctly. Verisure recently updated the firmware to 42080 and it may be related to this, as I think the error has started since this.

Error message from Home Assistant logs included below.

What version of Home Assistant Core has the issue?

2022.11.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Verisure

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

KeyError: 'alarm'
2022-11-25 06:47:42.144 ERROR (MainThread) [homeassistant.components.verisure] Could not read overview, Invalid response, status code: 401 - Data: {"errorGroup":"UNAUTHORIZED","errorCode":"AUT_00003","errorMessage":"No username/password provided"}
2022-11-25 06:47:42.147 ERROR (MainThread) [homeassistant.components.verisure] Unexpected error fetching verisure data: Invalid response, status code: 401 - Data: {"errorGroup":"UNAUTHORIZED","errorCode":"AUT_00003","errorMessage":"No username/password provided"}
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 205, in _async_refresh
    self.data = await self._async_update_data()
  File "/usr/src/homeassistant/homeassistant/components/verisure/coordinator.py", line 67, in _async_update_data
    overview = await self.hass.async_add_executor_job(
  File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.10/site-packages/verisure/session.py", line 211, in get_overview
    _validate_response(response)
  File "/usr/local/lib/python3.10/site-packages/verisure/session.py", line 16, in _validate_response
    raise ResponseError(response.status_code, response.text)
verisure.session.ResponseError: Invalid response, status code: 401 - Data: {"errorGroup":"UNAUTHORIZED","errorCode":"AUT_00003","errorMessage":"No username/password provided"}
2022-11-25 06:47:42.152 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 151, in _handle_refresh_interval
    await self._async_refresh(log_failures=True, scheduled=True)
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 283, in _async_refresh
    self.async_update_listeners()
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 110, in async_update_listeners
    update_callback()
  File "/usr/src/homeassistant/homeassistant/components/verisure/alarm_control_panel.py", line 90, in _handle_coordinator_update
    self.coordinator.data["alarm"]["statusType"]

Additional information

No response

[PEHowland]

config_entry-verisure-19aaf832e5c705658350eaa4ca9ed22f.json.txt

[home-assistant[bot]]

Hey there @frenck, mind taking a look at this issue as it has been labeled with an integration (verisure) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of verisure can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Change the title of the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign verisure Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

verisure documentation verisure source _{^{(message by IssueLinks)}}

[mountaindude]

FWIW, I noticed the same thing. Verisure integration stopped working around 3 days ago (i.e. ca 2022 Nov 25).

Seems the issue has sorted itself out though. I restarted HA today and the Verisure integration came back alive. Not sure what happened, but now things work again for me. Hopefully for others too.

[Kimble8650]

I had the same issue, and was beginning to get worried (since I could not really find a way to re-login to the verisure integration). But a simple reboot fixed it. Still there seems to be something fishy going on.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.