I’m trying since some days to get the MQTT functionality running but when I uncomment the mqtt part of the alarm.yaml the Alarm Panel at all is not working anymore. I just see a red circle (in Chrome). I have also tried to open the Alarm Panel with Firefox and Internet Explorer but no success. I have already added “frontend: javascript_version: latest” in my configuration.yaml but also no success. I got some errors in the logfile (the logfile entry is very long so I only insert the beginning):
2018-02-18 19:33:36 ERROR (MainThread) [frontend.js.latest.201802090] http://192.168.1.xxx:8123/frontend/panels/alarm-…
2018-02-18 19:33:36 ERROR (MainThread) [frontend.js.latest.201802090] http://192.168.1.xxx:8123/frontend_latest/panels/ha-panel-hassio-ad7aa…
I am using this for more than a month and it is now part of our life. Every night we arm the alarm, and every morning we disarm it. Same goes when we are away. My wife feels a lot safer now, and she also thinks it is easy to use. If she thinks this alarm is easy, then everyone can use it. She fully understands how it works! I made the interface a little easier to read and attractive by removing the unnecessary badge, enlarging the clock and the weather letters. I also exchanged the dark sky component with the openweathermap, as it seems to be more accurate (at least where I live).
Thank you for your effort!
One thing I am trying to figure out is the panic code. How do I implement it in an automation?
How can I use the attribute “panic_mode=ACTIVE” from the alarm sensor?
Seems odd that it works on one and not the other. Does the camera require authentication and could it be the iphone has saved credentials in the browser?
- action:
- data:
message: Come help me! I am held hostage by evil magneto!
service: notify.theX-men
alias: '[Alarm] Panic Mode'
condition: []
id: 'alarmpanicmode'
trigger:
- platform: template
value_template: '{{states.alarm_control_panel.jarvis_alarm_system.attributes.panic_mode=="ACTIVE"}}'
I will test the persistence mode later or tomorrow.
If you need any help, I am willing to contribute in any way I can. Even by just testing anything you like.
I almost had this working. I had the weather disabled but the clock wasn’t showing. Notifications were working. I realised I needed to add a time sensor for the clock to display and did so. I added a dark sky summary sensor at the same time and I also disabed hiding of the sidebar to assist with testing. Unfortunately when I restarted the alarm tab refused to display. The dark sky summary sensor and time sensor opperated correctly in the default display. I disbled the time and weather sensors in the alarm_panel.yaml. I also re-enabled hiding of the sidebar and then restarted but still can not get the tab to display again. This is the error I receive in Chrome (the firefox error log is enormous in comparison):
http://hassio.local:8123/frontend/panels/alarm-001f97509c39e788542bd2b51deb052d.html:250:34 Uncaught TypeError: Cannot read property 'attributes' of undefined
Ive tried es5, latest, and auto as the javascript version in the frontend but no change. Ive spent hours scouring my settings for errant spaces but can’t for the life of me work out why this is now not displaying. Anyone have any idea?
You need to clear browser cache and history or by ctrl+F5 on your browser if you use pc regarding the alarm tab
For javascript_version: auto is the best solution for now which not only effected the alarm control panel but also other setting involved with javascript (custom ui, etc).
His latest version of alarm control panel didn’t use javascript anymore from what I have read. However, you still need to put javascript_version: auto under frontend platform.
Thanks. I should have mentioned that I did clear my cache and I even tried another browser (that had never opened hassio) and I do currently have the JS version set to auto. All without success.
Hi, I am a beginner with HA, is it possible to schedule arm home at midnight and disarm in the morning?
I have searched the forum but I didn’t find a solution for this.
Ok here’s the panel_custom.yaml and alarm.yaml files. See anything wrong?
- name: alarm
sidebar_title: Alarm
sidebar_icon: mdi:security-home
config:
alarmid: alarm_control_panel.Home ## USE THE SAME ID AS USED IN YOUR ALARM.YAML
platform: bwalarm
name: Home
code: !secret alarm_code #Code, should consist of one or more digits ie '6482' ensure your passcode is encapsulated by quotes
panic_code: !secret panic_code #[OPTIONAL] Panic Code should consist of one or more digits ie '9876' ensure your passcode is encapsulated by quotes, it needs to be different to your standard alarm code. This enables a special panic mode. This can be used under duress to deactivate the alarm which would appear to the unseeing eye as deactivated however a special attribute [panic_mode] listed under the alarm_control_panel.[identifier] will change to ACTIVE. This status could be used in your automations to send a notification to someone else police/spouse/sibling/neighbour that you are under duress. To deactive this mode arm then disarm your alarm in the usual manner.
pending_time: 20 #Grace time in seconds to allow for exit and entry using Away mode
trigger_time: 180
alarm: automation.alarm_triggered
warning: automation.alarm_warning
##[OPTIONAL SETTINGS]
clock: False #[Optional] - False by default. True enables a clock in the center of the status bar
perimeter_mode: True #[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
weather: False #[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
persistence: 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.
hide_passcode: True #[OPTIONAL] - True by default. This is a security feature when enabled hides the passcode while entering disarm code.
hide_sidebar: False #[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_sensor_groups: True #[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_custom_panel: True #[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!!!
##[PASSCODE RELATED]
passcode_attempts: 3 #[Optional] Disabled if commented out. When a value equal or greater than 0 is set, the system will only allow the set amount of password attempts before timing out
passcode_attempts_timeout: 30 #[Optional] Default 30 seconds. When set with the password attempts option the panel will timeout for the amount of seconds set if the password is entered incorrectly as per the password_attempts option. The system will then reset the allowed password attempts
##[MQTT RELATED]
#mqtt: True #[OPTIONAL] - False by default. Settings this to True will enable MQTT Mode. Uncomment options below to use See the README for guidance.
#override_code: True #[OPTIONAL] False by default. if true allows MQTT commands to disarm the alarm without a valid code.
#state_topic: 'home/alarm' #[OPTIONAL] The MQTT topic HA will publish state updates to.
#command_topic: 'home/alarm/set' #[OPTIONAL] The MQTT topic HA will subscribe to, to receive commands from a remote device to change the alarm state.
#qos: 0 #[OPTIONAL] The maximum QoS level for subscribing and publishing to MQTT messages. Default is 0.
#payload_disarm: "DISARM" #[OPTIONAL] The payload to disarm this Alarm Panel. Default is “DISARM”.
#payload_arm_home: "ARM_HOME" #[OPTIONAL] The payload to set armed-home mode on this Alarm Panel. Default is “ARM_HOME”.
#payload_arm_away: "ARM_AWAY" #[OPTIONAL] The payload to set armed-away mode on this Alarm Panel. Default is “ARM_AWAY”.
#payload_arm_night: "ARM_NIGHT" #[OPTIONAL] The payload to set armed-night mode on this Alarm Panel. Default is “ARM_NIGHT”.
############### COLOURS ########### Use any HTML format
warning_colour: 'orange'
pending_colour: 'orange'
disarmed_colour: '#03A9F4'
armed_home_colour: 'black'
armed_away_colour: 'black'
triggered_colour: 'red'
############# SENSOR GROUPS ########################
##Sensors in this group tigger the alarm immediately
immediate:
- binary_sensor.pir_dining
- binary_sensor.pir_laundry
- binary_sensor.pir_lounge
- binary_sensor.pir_masterbedroom
- binary_sensor.pir_rumpus
- binary_sensor.pir_sparebedroom
- binary_sensor.pir_study
- binary_sensor.pir_workshop
##Sensors in this group start the clock (pending_time) when tripped before the alarm is activated in 'Away' mode
delayed:
- binary_sensor.pir_entry
##Same as notathome but hopefully the title is more self explanatory. Can still use notathome for backwards compatibility
##Note sensors can exist in more than one group notice top_floor appears in two groups
homemodeignore:
- binary_sensor.pir_entry
- binary_sensor.pir_dining
- binary_sensor.pir_lounge
- binary_sensor.pir_masterbedroom
- binary_sensor.pir_sparebedroom
##Use this group to automatically override the warning message on open sensors when setting 'away' mode. (I use this as I have a motion sensor at the front door)
override:
- binary_sensor.pir_entry
##This group is special and only effects 'perimeter mode'. If perimeter_mode is enabled then any sensor in this group will trigger the alarm immediately if arm perimeter is set. There is no delayed group for this mode (unless requested as a feature of course!)
perimeter:
- binary_sensor.pir_entry
- binary_sensor.pir_dining
- binary_sensor.pir_laundry
- binary_sensor.pir_rumpus
- binary_sensor.pir_sparebedroom
- binary_sensor.pir_study
- binary_sensor.pir_workshop
##[OPTIONAL] - CUSTOM SENSOR STATUSES - These settings allow devices which are not natively supported by this panel to be used.
##This is to be used when the state of the device is not recognised by the panel. Examples are provided below
custom_supported_statuses_on:
- 'Detected' #Motion & Smoke Detector
custom_supported_statuses_off:
- 'Clear' #Motion & Smoke Detector
stop your HA / sudo sytemctl stop home-assistant@homeassistant (or name what you put it)
clear your browser cache and history from Google Chrome (recommend google chrome)
delete your home-assistant-v2.db <== I cannot remember the exact name but the it is ***.db file.
in panel_custom.yaml change the alarmid: alarm_control_panel.Home <== change to home <== no captital letter here
all of your pir already supported in this alarm system so put # in front of below option
##[OPTIONAL] - CUSTOM SENSOR STATUSES - These settings allow devices which are not natively supported by this panel to be used.
##This is to be used when the state of the device is not recognised by the panel. Examples are provided below #custom_supported_statuses_on:
# - ‘Detected’ #Motion & Smoke Detector #custom_supported_statuses_off:
# - ‘Clear’ #Motion & Smoke Detector
reboot your server. This will take a little longer to load HA because you have deleted ***.db file but everything clean from HA and browser.
