Verisure
verisure
Home Assistant has support to integrate your Verisure devices.
In Apple Home through HomeKit Bridge
What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.
| Entity | Shows up as | Note |
|---|---|---|
switch | Switch or outlet | |
lock | Lock | Needs its own HomeKit Bridge in accessory mode |
camera | Camera | Needs its own HomeKit Bridge in accessory mode |
alarm_control_panel | Security system | |
binary_sensor | Sensor (contact) | |
sensor | Sensor (humidity, temperature) |
9 reports below say how a device from this integration behaves in the Home app.
What people report
Verisure alarms, locks and sensors work via the cloud with about one-minute polling; not working in some countries and HomeKit alarm needed a code.
- Works3
- Partly works3
- Not working5
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| Verisure alarm | Works | Works in Home Arm/disarm from Home app works after setting entity_config code | Works once alarm code is configured in HomeKit entity_configSaved copyHey guys Everything works perfectly with my Verisure alarm system through Home Assistant and it also appear in the Apple Home App, but I can't arm / disarm the alarm through the Apple Home App? I think I need to give HomeKit an arm code? Please help me :-) Thanks! Excerpt saved from GitHub on 2026-10-23. | Issue #19559 · 2018-12 |
| Verisure door lock | Works | Works in Home Lock PIN now configurable so lock/unlock works in Home | Fixed after report with code optionSaved copy… (Hass.io/Docker/Windows/etc.): Hassbian Component/platform: https://www.home-assistant.io/components/homekit/ Description of problem: Not possible to lock/unlock a Verisure doorlock in HomeKit. A option to save a Lock PIN in configuration.conf needs to be added. Lock/Unlock works fine in the HA GUI if you add the PIN manually every time. This is not possible in HomeKit. Excerpt saved from GitHub on 2026-10-23. | Issue #14507 · 2018-05 |
| Verisure lock, alarm and switch | Works Cloud | State now updates immediately after commands, not waiting for pollSaved copyProposed change Update state of lock, alarm control panel and switch immediately instead of waiting for scheduled cloud poll (every 1 minute). ## Type of change - [ ] Dependency upgrade - [x] Bugfix (non-breaking change which fixes an issue) - [ ] New integration (thank you!) - [ ] New feature (which adds functionality to an existing integration) - [ ] Deprecation (breaking change to happen in the future) - [ ] Breaking change (fix/feature causing existing functionality to break) - [ ] Code quality improvements to existing code or addition of tests ## Checklist - [x] The code change is tested … Excerpt saved from GitHub on 2026-10-23. | PR #149479 · 2025-07 | |
| Verisure alarm panel | Partly works Cloud | Partly in Home Arm/disarm errors, stuck Arming; needs code in YAML config | Works in HA with code; HomeKit lacks code entry in UISaved copyThe problem I can no longer operate my alarm from HomeKit. Any action to arm or disarm it results in an error in the Home Assistant log. Performing the same action from within Home Assistant itself with the Verisure alarm panel does work. ### What is version of Home Assistant Core has the issue? core-2021.4.2 ### What was the last working version of Home Assistant Core? core-2021.3.4 ### What type of installation are you running? Home Assistant Supervised ### Integration causing the issue Verisure ### Link to integration documentation on our website … Excerpt saved from GitHub on 2026-10-23. | Issue #48972 · 2021-04 |
| Verisure alarm panel | Partly works Cloud | Docs say it may not work in France, Ireland, Italy, Spain | Docs | |
| Verisure alarm via HomeKit | Partly works Cloud | Partly in Home Arm/disarm errors; binary sensors shown not responding | Arm/disarm failed from HomeKit until a code was configured; sensors showed not respondingSaved copyThe problem I can no longer operate my alarm from HomeKit. Any action to arm or disarm it results in an error in the Home Assistant log. Performing the same action from within Home Assistant itself with the Verisure alarm panel does work. ### What is version of Home Assistant Core has the issue? core-2021.4.2 ### What was the last working version of Home Assistant Core? core-2021.3.4 ### What type of installation are you running? Home Assistant Supervised ### Integration causing the issue Verisure ### Link to integration documentation on our website … Excerpt saved from GitHub on 2026-10-23. | Issue #48972 · 2021-04 |
| Verisure alarm | Not working | Broken in Home Arm/disarm from Home fails; alarm code ignored | Alarm code from UI ignored when armed via HomeKitSaved copyThe problem The Verisure alarm code, set in the UI, seems to be ignored when using it via HomeKit. The error I'm getting is: [code] and the full call stack is: ```Logger: homeassistant.core Source: components/verisure/alarm_control_panel.py:60 First occurred: July 20, 2022 at 14:05:54 (2 occurrences) Last logged: July 20, 2022 at 19:44:02 Error executing service: Error executing service: Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/core.py", line 1722, in catch_exceptions await coro_or_task File "/usr/src/homeassistant/homeassistant/core.py", line 1741, in … Excerpt saved from GitHub on 2026-10-23. | Issue #75555 · 2022-07 |
| Verisure alarm | Not working | Broken in Home Cannot arm/disarm from Home; default code ignored | Default alarm code in UI ignoredSaved copyThe problem The default Verisure alarm code, set in the UI, seems to be ignored. With this setup, I must enter the code manually in the Lovelace panel in order to arm/disarm. Not entering any code renders this error: [code] Full error call stack: ``` Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 185, in handle_call_service await hass.services.async_call( File "/usr/src/homeassistant/homeassistant/core.py", line 1492, in async_call task.result() File "/usr/src/homeassistant/homeassistant/core.py", line 1527, in … Excerpt saved from GitHub on 2026-10-23. | Issue #56442 · 2021-09 |
| Verisure alarm and lock | Not working | Broken in Home Bridge with lock and alarm panel stopped responding after 2024.7.4 | Works in HA; bridge unresponsive; not plannedSaved copyThe problem Since I updated my homeautomation on raspberrypi 4 from core 2024.7.3 to 2024.7.4 ,my verisure alarm and lock of verisure worked propperly in homeautomation. However, a hass bridge containing a lock and an alarmpanel stopped responding. I removed the bridge and the lock from my homekit on my iphone 14+ and created a new bridge with those two components (alarmpanel and lock) but i wasn't able to make it work again. Before it worked without any interuption. ### What version of Home Assistant Core has the issue? core 2024.7.4 ### What was the last working version of Home Assistant … Excerpt saved from GitHub on 2026-10-23. | Issue #123266 · 2024-08 |
| Verisure alarm panel | Not working | Broken in Home Arming from Home app fails asking for a code | Default-code change in 2024.6 stopped HomeKit arming despite code in YAMLSaved copyThe problem I have a Verisue alarm that is available as an alarm panel in Home Assistant through the Verisure integration. Thanks to the HomeKit bridge in Home Assistant I can use it in HomeKit to arm and disarm. But since Home Assistant 2024.6 the arm function does no longer work stating that I did not provide a code to arm it. Although the code is passed along in the YAML configuration of HomeKit in Home Assistant. I think the change made to the alarm panel to being able to provide a default code is the culprit here... … Excerpt saved from GitHub on 2026-10-23. | Issue #150089 · 2025-08 |
| Verisure alarm panel | Not working | Broken in Home Arming from Home app fails: 'requires a code but none given' | Broke in HA 2024.6 after alarm code validation changeSaved copyThe problem I have a Verisue alarm that is available as an alarm panel in Home Assistant through the Verisure integration. Thanks to the HomeKit bridge in Home Assistant I can use it in HomeKit to arm and disarm. But since Home Assistant 2024.6 the arm function does no longer work stating that I did not provide a code to arm it. Although the code is passed along in the YAML configuration of HomeKit in Home Assistant. I think the change made to the alarm panel to being able to provide a default code is the culprit here... … Excerpt saved from GitHub on 2026-10-23. | Issue #119541 · 2024-06 |
Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.
How it connects
Cloud polling
Goes through the maker’s cloud, asking it for updates every so often. Needs the internet and an account.
Found automatically over
- DHCP
Details
| Installs (analytics) | 2,519 (0.36%) |
|---|---|
| Added in | Home Assistant pre 0.7 |
| Set up in the UI | Yes |
In ReReHome
Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.
Bridges get their own settings page listing the accessories behind them.