YET another take on an alarm system

Hmm, try this:

remove alarm.yaml, just for now to keep it simple. Then have configuration.yaml have this:

alarm_control_panel:
  - platform: arlo
  - platform: manual
    name: Manual Alarm

Restart and if it works, it works read on, if it doesnt, i can’t help you ^^

Now check the states page for the entity’s:

should be something like:

alarm_control_panel.manual_alarm
alarm_control_panel.arlo

Now you can add those to say lovelace. You can also automate different alarms see one of my configs below:

- alias: '[Alarm] Auto Disarm Alarm when home'
  hide_entity: false
  initial_state: 'on'
  trigger:
    - platform: state
      entity_id: device_tracker.ezras_iphone
      to: home
    - platform: state
      entity_id: device_tracker.ezra
      to: home
  action:
  - service: alarm_control_panel.alarm_disarm
    entity_id: alarm_control_panel.house
    data:
      code: !secret alarm

Note that for Arlo you should add some stuff, just scanned the info page:

Hi All,

I am getting below error after upgrading the HA to 0.85.1. Please help.

Whoops!

Something went wrong with your alarm component!

The following errors have been plucked from the Home Assistant log:

Invalid config for [alarm_control_panel.bwalarm]: [clock] is an invalid option for [alarm_control_panel.bwalarm]. Check: alarm_control_panel.bwalarm->clock. (See ?, line ?). Please check the docs at https://home-assistant.io/components/alarm_control_panel.bwalarm/

config.py (ERROR)

Home Assistant: v0.85.1

This Panel: v1.3.4

Thanks in advance.
RT

post your config of alarm_control_panel: & alarm.yaml
Try to disable the clock in your alarm.yaml

The problem is. Under the alarm.yaml file, is all my config for my alarm system.
So if I remove that I will lose my config.

No problem, just paste it under the - platform: manual (if it is for your manual one) or - platform: arlo (if its your arlo config)

alarm_control_panel:
  - platform: arlo
  - platform: manual
    name: Manual Alarm

Or just post everything you have and i’ll fix it for you.

I will post it here tomorrow so you can have a look. Basically what I have running now is what the guide told me. I downloaded the custom components and added the alarm.yaml file plus the library from github. Then I pasted all the standard automations into the automation.yaml file and then tweaked it. It is working almost flawless. But as stated above, now I want to add the arlo component as well.

I will add the configurations.yaml and alert.yaml file tomorrow.

Thanks man!

I get it no problem, we’ll figure it out with some trial and error :slight_smile:

Hi @eh50,

I have already disabled the clock in alarm.yaml as shown below.

##[INTERFACE OPTIONAL SETTINGS] 
#[OPTIONAL] - False by default. True enables a clock in the center of the status bar
clock: False  
#[OPTIONAL] - False by default. True enables perimeter mode, this could be known as 'Day Mode' i.e. only arm the doors whilst there is someone using all floors
perimeter_mode: True 
#[OPTIONAL] - 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
weather: False 
#[OPTIONAL] False by Default. Allows this custom component to save the state of the alarm to file then reinstate it in the event of power loss.
persistence: False 
#[OPTIONAL] - True by default. This is a security feature when enabled hides the passcode while entering disarm code.
hide_passcode: True 
#[OPTIONAL] - False by default. This is a security feature when enabled hides the HA sidebar when the alarm is armed. The sidebar re-appears when the alarm is disarmed.
hide_sidebar: False 
#[OPTIONAL] - False by default. Setting this to True hides sensor groups (all sensors, immediate sensors, delayed sensors, inactive sensors) from the display. Open sensors will still appear
hide_sensor_groups: False 
#[OPTIONAL] - True by default. Setting this to False enables a custom panel below the sensors groups which allows you to add your own html code. Use this to bring any other features you would like to see for example displaying live camera feeds, a rotating image gallery, custom HA buttons and sensors. To use this enable the custom panel in alarm.yaml (custom_panel: True) then ensure you take a copy of custom-element.html and add it to you www/alarm/ folder. Edit the html code between the <template> tags. I'm have added a custom sample folder where I will upload examples of 'things' which can be added here. Please contribute!!!
hide_custom_panel: False 

Thanks,
RT

Home assistant log please. Also try to enable the clock? What about the time component, properly setup?

I to have the same error after updating alarm.py

2019-01-15 08:32:29 WARNING (MainThread) [homeassistant.components.http] legacy_api_password support has been enabled. If you don't require it, remove the 'api_password' from your http config. 2019-01-15 08:32:30 WARNING (MainThread) [homeassistant.loader] You are using a custom component for media_player.alexa which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant. 2019-01-15 08:32:31 WARNING (MainThread) [homeassistant.loader] You are using a custom component for alarm_control_panel.bwalarm which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant. 2019-01-15 08:32:31 ERROR (MainThread) [homeassistant.config] Invalid config for [alarm_control_panel.bwalarm]: [clock] is an invalid option for [alarm_control_panel.bwalarm]. Check: alarm_control_panel.bwalarm->clock. (See ?, line ?). Please check the docs at https://home-assistant.io/components/alarm_control_panel.bwalarm/ 2019-01-15 08:33:34 ERROR (MainThread) [frontend.js.latest.201901090] :0:0 Script error. 2019-01-15 08:33:45 ERROR (MainThread) [frontend.js.latest.201901090] :0:0 Script error. 2019-01-15 08:38:18 ERROR (MainThread) [homeassistant.components] Invalid config for [alarm_control_panel.bwalarm]: [clock] is an invalid option for [alarm_control_panel.bwalarm]. Check: alarm_control_panel.bwalarm->clock. (See ?, line ?). Please check the docs at https://home-assistant.io/components/alarm_control_panel.bwalarm/

checking the config fails and the log shows as above, I’ve tried with the clock set to true and false.

Did you only just update from a rather old version? I had to clear out my alarm.yaml when I updated to the latest version, and then use the GUI to set things back how my old alarm.yaml was

yes, that was it, didn’t realise the project had moved to a different setup, where do I find the gui to set the component up?

once you clear out the old alarm.yaml and go to the ‘alarm’ page in HA, it will all look different and have menu’s to do all the config

I was hoping you weren’t going to say that, no config options in that page

You may need to restart HA if the component doesn't load first time as HA will need to install a dependency (ruamel.yaml).

I see this on the readme, I can’t find that on my system so assume its related?

also have a script error

`019-01-15 09:19:47 ERROR (MainThread) [frontend.js.latest.201901090] :0:0 Script error.``

edit: the config page loads perfectly in chrome, must be a safari issue

Hey eh50,

Here is the configuration file:

# File include
group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
sensor: !include sensors.yaml
alarm_control_panel: !include alarm.yaml
panel_custom: !include panel_custom.yaml
scene: !include scene.yaml

# Surveilliance
ffmpeg:
      
arlo:
  username: !secret arlo_usr
  password: !secret arlo_pwd
  
camera:
  - platform: arlo
    ffmpeg_arguments: '-pred 1 -q:v 2'

Here is the alarm.yaml file:

##########################################################
## CUSTOM ALARM COMPONENT ALARM.YAML
## https://github.com/gazoscalvertos/Hass-Custom-Alarm
## VERSION:  1.0.2
## MODIFIED: 18/04/18
## CHANGE LOG:
## Add Multi Codes, names, pics
## optional code to arm alarm
## Default Interface password: HG28!!&dn
##########################################################

platform: bwalarm
name: House
code_to_arm: true
panel:
  cameras: []
  enable_sensors_panel: true
  enable_camera_panel: true
  enable_clock: true
  hide_sidebar: true
  round_buttons: true
states:
  armed_away:
    immediate:
    - binary_sensor.door_window_sensor_xxxxxxxxxxxxxxx
    - binary_sensor.door_window_sensor_xxxxxxxxxxxxxxx
    - binary_sensor.door_window_sensor_xxxxxxxxxxxxxxx
    delayed: []
    override: []
    pending_time: '25'
    warning_time: '25'
    trigger_time: '300'
  armed_home:
    immediate: []
    delayed: []
    override: []
    pending_time: 0
    warning_time: 0
    trigger_time: 600
  armed_perimeter:
    immediate: []
    delayed: []
    override: []
    pending_time: 0
    warning_time: 0
    trigger_time: 600
admin_password: xxxxxxxxxxxxxxxxxx
code: 'xxxx'
panic_code: 'xxxx'
users:
- id: xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  name: User1
  enabled: false
  code: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  picture: /local/images/ha.png
- id: xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  name: User2
  enabled: false
  code: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  picture: /local/images/ha.png
- id: xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  name: User3
  enabled: false
  code: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  picture: /local/images/ha.png

Ok, I am new here , gonna try this
I am using mqtt, on my alarm panel now , when I arm it , it instants arms the panel, without having the time to leave the building…
So is there also an arm timer that you can define, so if I actually press arm button, it will wait for like 30 seconds before sending mqtt

I see a pending timer, but I think that timer is the time before the alarm gets triggered if you enter the building?

As far as i know multiple components (at least for example service actions in automations) need a dash before it, opposed to single ones. Try this:

Make sure to fix the Indentation (spacing, dont know how to pronounced)
Also just leave it in alarm.yaml

- platform: bwalarm
  name: House
  code_to_arm: true
  panel:
  cameras: []
  enable_sensors_panel: true
  enable_camera_panel: true
  enable_clock: true
  hide_sidebar: true
  round_buttons: true
states:
  armed_away:
    immediate:
    - binary_sensor.door_window_sensor_xxxxxxxxxxxxxxx
    - binary_sensor.door_window_sensor_xxxxxxxxxxxxxxx
    - binary_sensor.door_window_sensor_xxxxxxxxxxxxxxx
    delayed: []
    override: []
    pending_time: '25'
    warning_time: '25'
    trigger_time: '300'
  armed_home:
    immediate: []
    delayed: []
    override: []
    pending_time: 0
    warning_time: 0
    trigger_time: 600
  armed_perimeter:
    immediate: []
    delayed: []
    override: []
    pending_time: 0
    warning_time: 0
    trigger_time: 600
admin_password: xxxxxxxxxxxxxxxxxx
code: 'xxxx'
panic_code: 'xxxx'
users:
- id: xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  name: User1
  enabled: false
  code: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  picture: /local/images/ha.png
- id: xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  name: User2
  enabled: false
  code: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  picture: /local/images/ha.png
- id: xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  name: User3
  enabled: false
  code: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  picture: /local/images/ha.png

- platform: manual
  name: Manual Alarm

Why wont you use arlo?

- platform: arlo
  home_mode_name: 'disarmed'
  away_mode_name: 'armed'

I tried with the above and I don’t get any fails, but I don’t get any entities :frowning:
But I can see that Stimo already replied in another topic I had, before I implemented the alarm system.
On the git page where he show his config, I see that it looks like he is using both systems.

@Stimo perhaps you can help?