Verisure smart home integration, free and open source
Arm, disarm and follow your Verisure alarm, its detectors and sensors from Gladys.
Published by prohand
- Devices
- Version 1.1.0
- Requires Gladys >=5.1.0
- ★ 0
Drive your Verisure alarm from Gladys: arm, disarm, follow its detectors, and react in your scenes.
The integration goes through the Verisure cloud ("Cloud" badge on the devices): it needs Internet access, and the data refreshes every 2 minutes by default. Unofficial API: Verisure can change it without notice.
Which Verisure app?
Two Verisure clouds exist, with different accounts and features. Pick the one of the app you use:
| App | Countries | What Gladys sees |
|---|---|---|
| My Verisure | France, Spain, Italy, Portugal, United Kingdom, Ireland, Argentina, Brazil, Chile, Peru | The alarm (all its modes, perimeter included) and the comfort sensors (temperature, humidity) |
| Verisure | Sweden, Norway, Denmark, Finland, Belgium, Netherlands, Germany... | The alarm (disarmed, partial, total), door/window detectors, temperature/humidity sensors, smart plugs and smart locks |
Configuration
- Open the Configuration tab of the integration.
- Pick your Verisure app and, for My Verisure, your country.
- Type the username and the password of your app.
- Verisure app only: type the alarm code (the keypad one). It arms, disarms and drives the locks. My Verisure does not need it.
- Save, then click Test the connection.
The verification code (first connection)
At the first connection, Verisure asks to validate this new "device":
- click Send a code: Verisure sends a code by SMS (or e-mail);
- type the code in Validate the code, then click the button.
Done once: the session is kept in the /data folder of the integration, a
restart does not ask for a new code. If Verisure asks again later (password
changed, session expired), the connection status of the Configuration screen
says so, and your scenes can know it with the The Verisure connection is
lost trigger.
The other settings
- Refresh interval: 120 seconds by default, 60 at least. Verisure blocks accounts that ask too often (sometimes for hours): do not lower it without a reason.
- Detailed logs: logs every exchange with Verisure (never the password, the codes or the tokens), to diagnose a problem.
The buttons
- Test the connection: logs in, lists your installations and their mode.
- Send a code / Validate the code: the SMS validation above.
- Forget the session: logs out from Verisure and deletes the kept session. The next connection may ask for a code again.
Devices
Once connected, open the Discover tab and add the devices with Add to Gladys:
- Verisure installation name: the alarm mode, a select. The modes offered are the ones of your panel: Disarmed, Partial (day), Partial (night) and Total, plus the perimeter modes when your installation has outdoor detectors. Choosing a mode sends the order; the value changes once Verisure confirmed it (from a few seconds to a minute and a half).
- Door/window detectors (Verisure app): open / closed.
- Temperature and humidity sensors.
- Smart plugs and locks (Verisure app).
When the alarm refuses to arm (a door or a window open), the order fails and Gladys shows the error.
Scenes
The integration adds its own cards to the scene editor (Gladys 5.1 or later), under the Integrations category.
Triggers
- Verisure alarm mode changed: armed or disarmed from the keypad, a badge,
the app or a remote. Filter on the alarm and the new mode. The following
actions can read
{{triggerEvent.data.mode}},{{triggerEvent.data.previous_mode}}and{{triggerEvent.data.changed_by}}(who changed it, when Verisure tells). Gladys's own orders never fire it, to avoid loops. - A Verisure door/window detector moved (Verisure app): filter on the detector and the state (opened, closed).
- The Verisure connection is lost: Verisure stopped answering, refused the login, throttles the requests or asks for a new code. Ideal to send yourself a message.
The mode values: disarmed, armed_home (partial day), armed_night (partial
night), armed_away (total), perimeter, armed_home_perimeter,
armed_night_perimeter, armed_away_perimeter.
Actions
- Set the Verisure alarm mode: pick the alarm (empty = the only one of the
account) and the mode. Tick Arm even with a door or window open to force
when the panel allows it. Outputs for the following actions:
success(true / false),mode(the alarm mode) andreason(why it was refused, e.g. the door left open). A refusal does not stop the scene: testsuccessin a condition. - Read the Verisure alarm now: asks the alarm its real state without
waiting for the next refresh. Output:
mode.
Dashboard
In Dashboard → Edit → New widget, add the Verisure alarm widget: alarm mode (green disarmed, orange partial, red total), last change (who, how long ago), open doors and windows, connection, temperature, and buttons to arm (every tap asks for a confirmation).
The Disarm button only shows when you tick Show a Disarm button in the widget settings. Beware: anyone who sees that dashboard can then disarm your alarm. Do not tick it on a shared dashboard or one shown in the entrance.
Troubleshooting
- "Verisure asks for a verification code": follow the code validation.
- "Verisure refused the username or the password": check them in the Verisure app, and the app chosen (My Verisure or Verisure). The integration stops trying until the configuration changes, so your account is not blocked.
- "Verisure limits the requests": the integration waits 15 minutes before trying again. Raise the refresh interval if it happens again.
- The alarm code is missing (Verisure app): fill it in to arm, disarm and drive the locks.
- For the details, turn the detailed logs on and read the integration logs from Gladys.
Configuration settings
These are the settings Verisure asks for in its configuration screen in Gladys.
| Setting | Type | Required | Description |
|---|---|---|---|
| Getting started | section | No | Use the login of your Verisure app. Two Verisure clouds exist: "My Verisure" (France, Spain, Italy, Portugal, United Kingdom, Ireland, Latin America) and "Verisure" (Nordics, Benelux, Germany...). The first connection asks for a code sent by SMS or e-mail: save, click "Send a code", then type it in "Validate the code". |
| Verisure app | select | Yes | The app you use to drive your alarm. |
| Country (My Verisure) | select | No | Country of your contract. Only used by the My Verisure app. |
| Username | string | Yes | The login of your Verisure app (e-mail or customer number). |
| Password | secret | Yes | |
| Alarm code | secret | No | Verisure app only: the code that arms and disarms the alarm and drives the locks. My Verisure does not need it. |
| Refresh interval (s) | number | No | How often Verisure is read, in seconds. Verisure blocks accounts that ask too often: keep 120 or more. |
| Detailed logs | boolean | No | Log every exchange with Verisure (no password, no token), to diagnose a problem. |
How to install Verisure in Gladys
- In Gladys, open Integrations: Verisure appears in the catalog, next to the native integrations, with a community badge.
- Click Install. Gladys pulls the Docker image (
ghcr.io/prohand/gladys-verisure:1.1.0), starts it in a sandbox isolated from the core, and generates the integration's interface (devices, discovery and configuration). - Open the Configuration screen of the integration, fill in the settings, and save.
- You can also install it directly from its repository URL: https://github.com/prohand/gladys-verisure.
Verisure requires Gladys >=5.1.0. The catalog inside Gladys refreshes every hour, so a new version becomes available at most one hour after its release.
Not running Gladys yet? It is free and open source: follow the installation guide to get started.
About external integrations
Verisure is an external integration: a community integration packaged as a Docker container and published on GitHub, that Gladys installs in one click and runs in a sandbox isolated from its core. It is published and maintained by prohand, not by the Gladys core team.
- Browse all external integrations
- Discover the native integrations built into Gladys
- Build and publish your own external integration
- Source code on GitHub — source of this documentation