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:
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
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.
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
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
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?
- 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
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.