YET another take on an alarm system

[tom_l]

What Dark Sky weather sensors do you have defined? You need an apparent temperature and a summary sensor or Firefox will complain. The install instructions only list the summary sensor as being required but they both are. See the first part of my post here:

YET another take on an alarm system

Thanks very much for your help Sunonline. I fixed it. It was the dark sky sensor. GitHub lists this under the optional settings: “weather: True #[OPTIONAL, Boolean] False by Default. Allows a weather summary to be displayed on the status bar. Dark Sky weather component must be enabled with the name sensor.dark_sky_summary” However reading through alarm.html panel I discovered as well as the dark sky summary sensor it also requires the apparent_temperature sensor. Once I had added this I had n…

[ProfKay]

Tom
Thank you, disabled weather, in alarm.yaml and no more error, and panel displays in Firefox
Will now add temperature sensor, and test, once again thanks for the assistance.

Update: All working now, thanks for the assistance

[piaso82 (Giovanni)]

thanks to all, now working also for me.

[gazoscalvertos]

OK,

I’m proposing changing the alarm.yaml config so that each state must configure its own groups. Times can still be inherited for example:

armed_home: #Either home/away with perimeter as optional
  pending_time: 10 
  trigger_time: 600 
  immediate:  #[OPTIONAL however either an immediate or delayed group must exist]
     - binary_sensor.whatever
  delayed: #[OPTIONAL]
     - binary_sensor.whatever
  override: #[OPTIONAL]
     - binary_sensor.whatever

This would drop the current homemodeignore group too so not backwards compatible with current release

Also how about splitting pending time so that there is a pending time for arming the alarm and a separate warning time for when a device is tripped?

[gazoscalvertos]

If someone wants to share a mockup of a super clean (mobile/reduced feature set) panel too I’ll code it up

[j.assuncao (Jorge Assunção)]

That would be awesome! I’m using HADashboard with an iframe to show the alarm panel and only part of it shows without scrolling…

[AhmadK (akasma74)]

Hi guys, I’m setting up my alarm system and currently have a simple problem.
My siren goes off when the alarm is triggered in Away mode because I have alarm_triggered rule in automations.yaml.
However, when trigger_time elapses, the alarm system automatically falls back to Away mode but does not switch the siren off.
I tried to add service call switch.turn_off to the alarm_arming_away automation rule, but it didn’t work.
I ended up calling switch.turn_off for my siren from alarm_armed_away and it works, but I don’t feel that’s kind of the right choice.

How it supposed to be configured properly?

And also, having read HA documentation on templating and noticing several complaints in this thread regarding automation not working, I believe there should be data_template: instead of data: in every alarm_xxx automation’s action.

[tremebundo (Juan Manuel)]

I think that would be a more intuitive aproach to understand the configuration.
Also, it would give more flexibility to have a pending time to armed state and a different one to trigger.

[kegra (John)]

hi, thanks for this great project! I updated all the files from github with latest files, running hassio 0.65.4 on a raspberry pi, for browsing I use safari on a mac, I get this on my log when visiting the alarm panel XXX.XXXX.XXX/local/alarm/alarm_scripts.js:38:20 TypeError: null is not an object (evaluating ‘main.left’) any help ?

[Paul_Flavel (Paul.F)]

Cannot read property 'left' of null

[gazoscalvertos]

Ahh, I have not yet tested with the latest HA.

Please leave it with me

[AhmadK (akasma74)]

can confirm that there is nothing like that on 0.64.3

[gazoscalvertos]

Any entity, automation or group (groups can include automations) defined under alarm within your alarm.yaml:

alarm:

Will switch on when the alarm is triggered.

You could define your automation and add your sirens to a group then set in your config above, when the alarm resets back to armed state after the allotted time the group will switch off.

You are better off using an automation however than groups to keep things simple.

For example you could use an automation to monitor the state of alarm_control_panel which only looks at the ‘from_state’ attribute ‘triggered’ then switches off your siren. For examlple:

  alias: '[Alarm] Resetting'
  trigger:
  - platform: state
    entity_id: alarm_control_panel.house
    from: 'triggered'
  action:
  - service: switch.turn_off
    entity_id: switch.siren_ground_floor_switch #Or alternatively define a group for multiple sirens
  - service: switch.turn_off
    entity_id: switch.siren_1st_floor_switch
  - service: switch.turn_off
    entity_id: switch.siren_2nd_floor_switch

[AhmadK (akasma74)]

@gazoscalvertos

Any entity, automation or group (groups can include automations) defined under alarm within your alarm.yaml

Currently it’s alarm: automation.alarm_triggered
So I was right when added switch.turn_on of the siren in action section of that automation.
I think it’s a good idea to add a comment about it in alarm.yaml

The idea of monitoring the state of alarm_control_pane is good as well. I’d rather do it like that
alias: ‘[Alarm] Resetting’
trigger:

• platform: state
  entity_id: alarm_control_panel.house
  from: ‘triggered’
  action:
• service: switch.turn_off
  entity_id:
  • switch.siren_ground_floor_switch
  • switch.siren_1st_floor_switch
  • switch.siren_2nd_floor_switch

or use a group of sirens.

Thanks for the explanation!

[ProfKay]

Hi All

Trying to get the following automation to work, but getting an error when validateing the config file, can any throw some light on this for me.

- alias: '[Alarm] Panic Mode'
  trigger:
    - platform: state
      entity_id: alarm_control_panel.house
      value_template: "{{ states.alarm_control_panel.house.attributes.panic_mode | upper }}"
      to: "ACTIVE"
  action:
    service: notify.kp
    data_template:
      message: '!! Panic Alarm Set !!'

I am getting the following error

automation: - Invalid config for [automation]: [value_template] is an invalid option for [automation]. Check: automation->trigger->0->value_template. (See /config/configuration.yaml, line 88). Please check the docs at Automation - Home Assistant

[argykaraz]

The platform has to be “template”
Use this:

- action:
  - data:
    service: notify.kp
    data_template:
      message: '!! Panic Alarm Set !!'
  alias: '[Alarm] Panic Mode'
  condition: []
  id: 'alarmpanicmode'
  trigger:
  - platform: template
    value_template: '{{states.alarm_control_panel.jarvis_alarm_system.attributes.panic_mode=="ACTIVE"}}'

[ProfKay]

@argykaraz

Thank you!

[ProfKay]

Hi guys,

Spotted another issue, I have clock: true, in the alarm.yaml, yet the clock does not get displayed, anyone help here.

[AhmadK (akasma74)]

it’s a known feature. I found the answer earlier in this thread.
Display the clock : You also need the following in your configuration.yaml

sensor:

• platform: time_date
  display_options:
  • ‘time’

[ProfKay]

@AhmadK
I did go through the whole thread, and just knew was missing a sensor, but this thread now is so long, I just missed it, anyway thank you.