[APP][Pro] Verisure

Apps
, ,
485

I have the same issue. Devices stop updating. Restarting the app doesn’t help, but logging in again (just click “login” in the settings) seems to work. I have to do this daily, at least, so it’s not a useful solution.

I’m guessing an auth token is expiring sooner than before, or the token refresh logic is broken.

486

Hopefully Verisure will make an official app. But I won’t hold my breath. :joy: Every customer survey they’ve sent I have written I hope they will officially support Homey.

487

HI Team,

i’m unable to get the app connected, does anyone else has the same experience lateley?

Kind regards, Kees

488

Does anyone know if the door lock below can work with this app?

489

Impossible for me to Signin my account.
I guess it is because Verisure now forces double auth (and cant disable it).

Hope they will create an official app.

490

Same here, I cannot log in to my account, also the devices updates sporadically. I have also just addes two new Smoke detectors, but they do not show up in Homey =(

491

Is there a way to perform the login action through Homey Script? It seems I need to do the login action regularly (like once a day) to keep the verisure units connected to homey.

I tried with restarting the app dailty through a flow, but that doesnt always work.

492

Hi everyone.

I had similar issue with Verisure not working anymore. I went to “my pages” on the web and it seems my MFA (two factor login) had been re-enabled. I just disabled it again, and it seems to be working now. Without doing anything (like trying to re-login or restarting the app) I did get readings from sensors (smoke alarm temperature values) again.

We will see if it keeps working.

493

Hi all,

I’m new to homey.

I’m also using a Jeedom atlas box, that is out of support, and have to changed.

I’m using the french services of Verisure, forced to user 2FA authentication for months/years.

I have installed the Verisure app on my Homey Pro box, but I cannot connect with a dedicated account, created for it, and get an error message saying that my userid and password is not correct.

I have tried the same with the Verisure plugin on my Jeedom box.

There are some diffrerences, as it is asking another information, the installation ID and the type of alarm (1,2 or 3, and the one I’m using is the first as I bought my verisure systems years ago).

When I authenticated, it works with the usr/password I have used for homey app, and then asks me in return which phone number I want to use for 2FA (As it is when you connect to the french customer front end of Verisure), replied and then is able to read the configuration of the alarm and the logs.

Capture d'écran 2026-02-09 114746
Capture d'écran 2026-02-09 1147461485×895 104 KB

I’ve checked afterwards if it has created a trusted asset, but it did’nt have. It looks that the token that it had is kept somewhere and then used afterwards.

However, what it lightens out is that 2FA in not an option for french users, and that there is a way to authenticate through APIs, that also seem to require which type of alarm system is in used (1,2 or 3) and also requires the installation ID.

I’m not sure it is helping, but I hope so.

Regards.

494

I am new to Homey. And now I try to connect Homey Pro 2026 to my Verisure alarm system.
Logging in fails.

I created a new user in Verisure, disabled 2FA.
The error that appears is:
cannot read properties of undefined (reading ‘length’)

I hope someone can help. Thanks in advance,
Arjen

495

Same problem here

496

New to Homey.

Connected Verisure. Connected the components as well, only the Keypad gives me a problem "Cannot read properties of undefined (reading ‘data’)

497

[Bug][Spain] Verisure app 3.4.14 rejects numeric username – “Invalid or non-existing value for email”

Hi @norenz,

I have found what seems to be a login compatibility issue with Verisure accounts in Spain.

I am using Verisure for Homey v3.4.14.

In Spain, my Verisure account uses a numeric username, not an email address. The same numeric username is the one used to access my Verisure account normally.

When I enter this username in the Homey Verisure app settings and press Login, authentication fails immediately with:

“Error: Invalid or non-existing value for email”

This suggests that the current authentication implementation is treating the username as an email address, while Spanish Verisure accounts may use a numeric user ID.

Steps to reproduce

  1. Open Homey → Apps → Verisure → Settings
  2. Enter a valid Spanish Verisure numeric username
  3. Enter the corresponding password
  4. Enter the arm/disarm code if required
  5. Press Login
  6. The app returns: “Invalid or non-existing value for email”

Expected behaviour:
The username field should accept the Verisure account username, including numeric usernames used by Spanish Verisure/Securitas Direct accounts.

Actual behaviour:
The login request appears to require or validate an email address and therefore rejects the Spanish numeric username.

Environment:

  • Homey Pro
  • Verisure Homey app: 3.4.14
  • Country/account: Spain (Verisure / Securitas Direct)
  • Username format: numeric
  • Official Verisure login with these credentials: working

I have attached screenshots showing the settings screen and the error. I have redacted the actual username/password.

I also noticed that the GitHub “Report an issue” link on the Homey App Store currently returns a 404, so I’m reporting it here.

Could you please check whether the authentication code currently assumes that username is an email address, and whether numeric usernames could be supported for Spanish accounts?

Thanks.

498

Have the same issue. Would be great to hear from the Developer on this? Also, its been 6 days since my components have given an update to Verisure units in Homey. And when I try to login again, with my user its states only: Error: Cannot read properties of undefined (reading ‘length’)

499

Hi all,

I got a little tired of the Verisure app not working properly (no MFA, daily re-logins, accounts getting blocked for polling too often), so I rebuilt it from scratch. Thanks to Adam Norén for the original app, which got many of us started.

The new app is built on the same Verisure library that Home Assistant uses, so the login and API handling are proven code.

What it does

  • :locked_with_key: MFA login. Enter the SMS code once and Homey becomes a trusted device. It stays logged in and signs itself in again when the session expires. No more pressing “Login” every day.
  • :shield: Alarm: arm away, arm home and disarm. Force arm if a window is open. See who changed the alarm and how. You can also arm or disarm with a personal code per flow, so Verisure logs the right person.
  • :white_check_mark: “Can the alarm be armed?” asks Verisure, without arming, and tells you which door or window is in the way. Handy before you leave.
  • :door: Door/window sensors for open and closed, including quick openings between updates.
  • :fire: Smoke, :droplet: water and :person_running: motion detectors, plus tamper and low battery on every sensor.
  • :thermometer: Temperature and humidity from smoke detectors, sirens and climate sensors.
  • :electric_plug: Smart plugs, smart locks and cameras.
  • :turtle: One request per minute for the whole installation, with automatic back-off if Verisure starts limiting requests.

Status
I haven’t published it in the App Store yet, so for now it’s for those of you comfortable with the Homey CLI. Installation steps are in the README:
:backhand_index_pointing_right: GitHub - mikeSwe77/com.verisure.myapp: Verisure alarm, sensors and detectors for Homey Pro (SDK3, MFA sign-in) · GitHub

If we think it’s in good enough shape, I can publish it to the App Store rather quickly.

Please note

  • I have only tested it with Verisure in Sweden. Reports from other countries are very welcome, since MFA and the API can differ.
  • I have a rather dated system, so I haven’t been able to test everything. Smart locks and cameras are untested on real hardware.
  • Disable the old Verisure app while testing. Running both doubles the requests to Verisure, and Verisure blocks accounts that poll too much.
  • Verisure motion detectors only detect while the alarm is armed. That’s how the hardware works.
  • Please don’t test smoke or water detectors for real without calling Verisure first. It can start a real alarm response.
  • Tip: create a separate Verisure user for Homey. Everything Homey does is then easy to recognise in the log.

Feedback
Bugs and test reports are best posted as GitHub issues. There’s a Device test report form for exactly this. Comments here in the thread are welcome too. Please never post passwords, codes or your installation ID.

If you find it useful, there’s a :hot_beverage: link in the repo. No pressure at all.

/Michael

500

Hi all Verisure users,

Sorry for the long silence, and thanks for your patience. I’ve rebuilt the Verisure app from the ground up, and version 4.0.0 is on its way through the App Store, starting with the test version: Verisure | Homey

What’s fixed

  • Two-step verification (MFA) works. Enter the code once and Homey is remembered as a trusted device.
  • No more daily logins. The app keeps its session alive and signs itself in again when needed.
  • Gentler on Verisure. It checks once a minute per installation (you can change this, minimum 30 s) and backs off automatically if Verisure starts limiting, so accounts shouldn’t get blocked.
  • The login error “Cannot read properties of undefined (reading ‘length’)” and the keypad error “(reading ‘data’)” are gone.

What’s new

  • Sign in when you add a device, with no app settings needed. Several accounts and installations can be used side by side.
  • New device types: climate sensors, motion detectors and cameras (cameras are experimental).
  • Smoke, water, tamper and low-battery alarms. The alarm device also triggers on alarms from Verisure devices you haven’t added to Homey.
  • Quick door and window openings between updates are picked up.
  • See who armed or disarmed and how, arm with a code from a Flow, and arm even if a window is open.
  • An alarm widget for the dashboard, and new images and icons for all devices.

Upgrading from 3.x

  • Your devices, Flows and Insights stay. No need to re-add anything.
  • Your login and alarm code move over automatically. The code ends up in the alarm device’s settings.
  • If your account uses two-step verification, or a device says it needs repair: open the device → Maintenance → Repair, and sign in.
  • Requires Homey v12.3 or newer. Older Homeys stay on 3.4.14.

Good to know

  • Use a Verisure user with administrator rights. Smoke, water, motion, tamper and battery alarms come from Verisure’s event log, which only admins can read. A separate user for Homey also makes Homey’s actions easy to spot in the Verisure app.
  • Motion detectors usually only report while the alarm is armed.
  • Please don’t set off smoke or water detectors to test without calling Verisure first.
  • Accounts that sign in with a username instead of an e-mail address (for example in Spain) use a different Verisure platform that this app can’t connect to.

Problems?
Send a diagnostic report from the app’s page in the Homey app, then post here what happened and when. The logs never contain passwords, codes or addresses. Turning on Verbose logging in the app settings gives me even more detail.

Thanks for sticking with the app!
/Adam

501

Thanks!

The test version is quite good already. Couple of things I’ve noticed.

  1. The alarm controll card is not showing the whole card when adding to homepage on Android phones
  2. Opening the Verisure Alarm card, and the alarm is off, it will automatically enable the alarm (old version do this too)
  3. Can finally add indoor cameras and the panel pluss nightstand panels, very good.
  4. I miss flow cards that collect all window sensors in one, so we can use it to push messages if someone opens a door or window. Can do it one by one, but that creates too many flows
  5. The units are not reporting temperature and humidity to Homey, in the climate page (data is pulled from Verisure and show for each unit)

Thanks for the new version.

502

Thank you updating the app. :grinning_face:

I also noticed that the devices stop updating at some point. After doing a repair on one device they start updating again. Is there som logging I can provide?

When going in to one of the devices I get this “error message”: Some data is not available from Verisure right now. Homey tries again later.

Since the smoke detector and siren isn’t reporting temperature and humidity they do not work through the Matter app and in HomeKit.

503

I also have flow feature request, if possible: To set Auto-lock on smart locks. Today I use the “logic” in the Verisure app on my iPhone. It would give more flexibility to do it in Homey. :grinning_face: Example: In case of fire, turn off Auto-lock and unlock all doors.

504

Verisure 4.0.1 – Devices not updating (SYS_00004)

Hi @norenz

First of all, thanks for the work on version 4.0!

I’m experiencing similar issues to those reported by @MNHPetersen and @kaieivind , where devices stop updating in Homey.

I checked the diagnostic logs and noticed that several API operations (door/window sensors, smart locks, climate and broadband) repeatedly fail with:

SYS_00004 (503): XBN Database is not activated

Authentication and session refreshes appear to work correctly, and all 18 devices are shown as available in Homey. However, some data hasn’t been updated for over 90 minutes.

One observation is that the app continues to report a healthy connection (health=ok) despite these repeated API errors.

I’ve submitted a diagnostic report for further investigation:

Report ID: 30acd9cb-fe7e-4d53-a7c0-a2fd3fe6a26e

Hopefully, this provides some additional information to help identify the issue.