YET another take on an alarm system

[William_Rodriguez]

@gazoscalvertos

Could you post your customization for one that doesnt?

This is my sensors template

- platform: template
  sensors:
    fdstatus:
      value_template: '{% if is_state("sensor.front_door_sensor_access_control", "23") %}closed{% else %}open{% endif %}'
      friendly_name: 'FD'

    ydstatus:
      value_template: '{% if is_state("sensor.yard_door_sensor_alarm_level", "0") %}closed{% else %}open{% endif %}'
      friendly_name: 'YD'

    gdstatus:
      value_template: '{% if is_state("sensor.garage_interior_door_alarm_level", "0") %}closed{% else %}open{% endif %}'
      friendly_name: 'GD'

    awdstatus:
      value_template: '{% if is_state("binary_sensor.andrews_window_opened", "off") %}closed{% else %}open{% endif %}'
      friendly_name: 'AWD'

    awlightstatus:
      value_template: '{% if is_state("switch.andrews_bedroom_switch", "off") %}Off{% else %}On{% endif %}'
      friendly_name: 'ABD'

    mblstatus:
      value_template: '{% if is_state("switch.my_bedroom", "off") %}Off{% else %}On{% endif %}'
      friendly_name: 'MBL'


    arwdstatus:
      value_template: '{% if is_state("binary_sensor.visonic_mct340_e_0b2a7984_1", "off") %}closed{% else %}open{% endif %}'
      friendly_name: 'arwd'
      
    lrwd1status:
      value_template: '{% if is_state("binary_sensor.visonic_mct340_e_0b0011fb_1", "off") %}closed{% else %}open{% endif %}'
      friendly_name: 'lrwd1'
      
    lrwd2status:
      value_template: '{% if is_state("binary_sensor.visonic_mct340_e_0b000c64_1", "off") %}closed{% else %}open{% endif %}'
      friendly_name: 'lrwd2'
      
    lrwd3status:
      value_template: '{% if is_state("binary_sensor.window_living_room_3_sensor", "off") %}closed{% else %}open{% endif %}'
      friendly_name: 'lrwd3'
      
    lrwd4status:
      value_template: '{% if is_state("binary_sensor.window_living_room_4_sensor", "off") %}closed{% else %}open{% endif %}'
      friendly_name: 'lrwd4'
      
    lrmotionstatus:
      value_template: '{% if is_state("binary_sensor.living_room_motion_sensor_sensor", "off") %}clear{% else %}detected{% endif %}'
      friendly_name: 'lrmotionsensor'
      icon_template: >
        {% if is_state('sensor.lrmotionstatus', 'detected') %}
        mdi:walk
        {% else %}
        mdi:run-fast
        {% endif %}

and here is the customized.yaml

sensor.fdstatus:
  friendly_name: Front Door
  icon: mdi:glassdoor
  
sensor.ydstatus:
  friendly_name: Yard Door
  icon: mdi:glassdoor
  
sensor.gdstatus:
  friendly_name: Garage Door
  icon: mdi:glassdoor
  
sensor.awdstatus:
  friendly_name: Andrew's Window
  icon: mdi:window-closed
  
group.weather_fw:
  icon: mdi:weather-sunny
  
sensor.awlightstatus:
  friendly_name: Andrew's Bedroom
  icon: mdi:ceiling-light

sensor.mbl:
  friendly_name: Master Bedroom Light
  icon: mdi:ceiling-light
  
sensor.arwdstatus:
  friendly_name: Arelly's Window
  icon: mdi:window-closed

sensor.yweather_condition:
  friendly_name: Condition
  
sensor.andrews_window_opened_battery:
  icon: mdi:battery

sensor.lrwd1status:
  friendly_name: Living Room Window 1
  icon: mdi:window-closed
  
sensor.lrwd2status:
  friendly_name: Living Room Window 2
  icon: mdi:window-closed

sensor.lrwd3status:
  friendly_name: Living Room Window 3
  icon: mdi:window-closed
  
sensor.lrwd4status:
  friendly_name: Living Room Window 4
  icon: mdi:window-closed
  
sensor.yweather_temperature:
  friendly_name: Temperature
  icon: mdi:temperature-fahrenheit
  
sensor.lrmotionstatus:
  friendly_name: Living Room Motion Sensor
  #icon: mdi:run

[gazoscalvertos]

Could you try removing the custom state for one of the binary senors say awd and instead of the custom state in customize.yaml use:

device_class: opening

Also remove the icon from customize.yaml

[gazoscalvertos]

Apologies all. Took a little longer to get the code into a shape to upload. Github updated as of 2 mins ago!

Changes:

Perimeter Mode (Optional) - I use this to just arm the doors/windows during the day when I am in
Weather Icon/Summary (Optional) - You need Dark Sky for this to work
Added 0 to code panel as requested by @thundergreen (Not sure about the design, if anyone could suggest/upload a decent layout it would be appreciated)

Any issues let me know.

[William_Rodriguez]

@gazoscalvertos

ould you try removing the custom state for one of the binary senors say awd and instead of the custom state in customize.yaml use:

device_class: opening

Also remove the icon from customize.yaml

Made the changes but they didn’t help. I’m going to remove each sensor from the alarm and place them back one at a time to see if I can identify the root cause. Will let you know if I come up with a solution.

[nebbiadigiorno (nebbia)]

i have a question. with the introduction of “perimeter mode” we need an another automation?

[gazoscalvertos]

Nope it still activates ‘triggered’ status on trip so all your existing automation should be good to go. Just make sure you add the sensors to ‘perimeter’ group

[nebbiadigiorno (nebbia)]

maybe only the one for the notification?

[gazoscalvertos]

Yeah true if you have notifications set for alarm activations

[William_Rodriguez]

@William_Rodriguez

Made the changes but they didn’t help. I’m going to remove each sensor from the alarm and place them back one at a time to see if I can identify the root cause. Will let you know if I come up with a solution.

Ok, every sensor that is on/off close/open on their own without the customization work without a problem. Why is that the customization cause the issue since the sensor that is being used is still outputting the same information just formatted differently?

[William_Rodriguez]

@William_Rodriguez

Made the changes but they didn’t help. I’m going to remove each sensor from the alarm and place them back one at a time to see if I can identify the root cause. Will let you know if I come up with a solution.

Ok, every sensor that is on/off close/open on their own without the customization work without a problem. Why is that the customization causes the issue since the sensor that is being used is still outputting the same information just formatted differently?

@gazoscalvertos - I finally have it going. Originally I was customizing the sensors as standard sensors, with the help of @a_ndy on another thread I posted trying to discover the cause of why device_class: opening wasn’t working for me, he enlightened me that I needed to convert the sensor into a binary_sensor. That did the trick!

[gazoscalvertos]

Brilliant! Glad you got it sorted.

We learn something new everyday!

I’ll update the readme on the github page with your findings.

[3m0]

How can I just run this as a separate tab on my front end? I would love to use this but only want it in a tab

[gazoscalvertos]

At the moment you can only run this as a panel, not much different to a tab view.

I’ll implement statecards ie views/tabs once the design, features and bugs are worked out

[Chronocento (Andrea)]

Hi gazoscalvertos,
thank you for your project, I had to replace drytoastman component due to incompatibility with the latest versions of HA, and yours provided a smooth transistion, more or less: I wanted to ask you if there’s a way to avoid asking for a digit code entry on disarm; I use some automations to temporarily disable the alarm on certain situations, and they are not working, probably for the inability to disarm the system without pin.

[gazoscalvertos]

In your automation your can set the alarm code:

alias: '[Alarm] Disarm'
trigger:
  [YOUR TRIGGER]
action:
- service: alarm_control_panel.alarm_disarm
  entity_id: alarm_control_panel.house
  data:
    code: 1234

[Chronocento (Andrea)]

Great, I’ll try it immediately, thanks!

[Hefford27 (Graham Hefford)]

I am trying do do something with a Amazon Dash Button via MQTT to enable and disable the alarm from the Dash Button on a set of keys… Im close but cant get the disarm to work, any ideas

- alias: 'Alarm Arm and Disarm Using Amazon Dash Olay'
  initial_state: 'on'
  trigger:
    platform: state
    entity_id: switch.olay_dash_switch
    to: 'on'
  action:
    service_template: >
     {% if is_state('alarm_control_panel.house', 'disarmed') %}
       alarm_control_panel.alarm_disarm
     {% else %}
        alarm_control_panel.alarm_arm_away
     {% endif %}
    data_template:
      entity_id:  alarm_control_panel.house
      data: >
       {% if is_state('alarm_control_panel.house', 'disarmed') %}
         code: 9999
       {% endif %}

[gazoscalvertos]

Looks like your missing an ! from your service template:

{% if !is_state('alarm_control_panel.house', 'disarmed') %}

And your data template:

{% if !is_state('alarm_control_panel.house', 'disarmed') %}

[Hefford27 (Graham Hefford)]

@gazoscalvertos thanks i get the following error when added !

2017-12-04 14:04:43 ERROR (MainThread) [homeassistant.config] Invalid config for [automation]: invalid template (TemplateSyntaxError: unexpected char ‘!’ at 6) for dictionary value @ data[‘action’][0][‘data_template’][‘data’]. Got None invalid template (TemplateSyntaxError: unexpected char ‘!’ at 6) for dictionary value @ data[‘action’][0][‘service_template’]. Got None. (See /home/homeassistant/.homeassistant/configuration.yaml, line 27). Please check the docs at https://home-assistant.io/components/automation/

[gazoscalvertos]

Hi, I didn’t realize that syntax wouldn’t work in Jinja2

try {% if is_state(‘alarm_control_panel.house’, ‘disarmed’) == false %}

You can test this in the templates section of HA before editing your code https://[HA URL]/dev-template

I have just tried this as a test and it works

{% if is_state('alarm_control_panel.house', 'disarmed') == false %}
  set
{% else %}
  not set
{% endif %}