Verisure (Securitas Direct) Integration Experience

Third party integrations
1

Hi,

Probably getting Verisure in Sweden within a few weeks.

How is your experience with the integration?

  • Is it stable?
  • How ofter does the API break due to Verisure updates?
  • Have you been penalised due to accessing their API too much (or outside app)?
  • What kind of pheriperals can you retrieve data from?

I wish to trigger automations based on larm status, and read sensor data, such as temperature status, and motion sensor data.

Much thanks,
Br,
Tim

2

Hi,
here it is.

esphome:
name: consumo-agua-general
platform: ESP32
board: nodemcu-32s

Enable logging

logger:

web_server:
port: 80

Enable Home Assistant API

api:

ota:
password: “xxx”

wifi:
ssid: “MOVISTAR_xxx”
password: “xxx”

…

manual_ip:

# Set this to the IP of the ESP

static_ip: 192…x.x.x

# Set this to the IP address of the router. Often ends with .1

gateway: 192.168.0.1

# The subnet of the network. 255.255.255.0 works for most home networks.

subnet: 255.255.255.0

Enable fallback hotspot (captive portal) in case wifi connection fails

ap:
ssid: “Consumo-Agua-General”
password: “xxxx”

captive_portal:

Example configuration entry

sensor:

  • platform: pulse_counter
    pin: 2
    name: “consumo Agua general L/min”
    update_interval : 60s
    filters:

    • lambda: return (x / 373.0);
      unit_of_measurement: “L/min”

  • platform: pulse_counter
    pin: 2
    name: “consumo Agua general L/hora”
    update_interval : 60s
    filters:

    • lambda: return (x / 373.0) * 60.0;
      unit_of_measurement: “L/Hr”

  • platform: pulse_counter
    name: “consumo agua litros”
    update_interval : 60s
    pin: 2
    #number: GPIO2
    #mode: INPUT_PULLUP
    icon: “mdi:water”
    filters:

    • lambda: return (x / 373.0);
      #- lambda: return x * (1/140.0);

    se ha calibrado con cubo de 5 litros = 1864 pulsos

    1 litro = 373 pulsos

    unit_of_measurement: “Litros”