You remote is easily jammed/intercepted. Don’t do that with a RF remote.
Oops so they are, sorry for any confusion caused.
Sorry for the possibly stupid question, am coming late to this project. Have got it all installed but am struggling a little with understanding some (not all) of the options and the differences between the different modes. e.g. I’m looking for a “night mode” and a way to disarm night mode through a particular PIR sensor sensing me before all the rest do (i.e. me coming down the stairs in the morning!). Also wanting some assistance understanding the override column of sensors and what the implications are for a sensor being selected in that column. So anyway I’m coming to a point…is there any documentation available beyond the installation instructions on GitHub?
Thanks!!
You will have to write an automation for this.
If a sensor is in the override column it will not prevent the alarm from arming if active. Could be handy for an exit door or PIR near the alarm panel. If it is not in this column and is active when trying to arm you will get a warning and the alarm wont arm.
Thanks, Tom. But in terms of a “night mode” isn’t this essentially what “home mode” is ? Don’t you get two different alarm modes (or even three if you turn on perimeter mode)?
Yes indeed, but if you want to disable it with a PIR that is going to be up to you. Here’s an example of disarming using an automation:
- id: automatic_alarm_disarm
alias: Automatic Alarm Disarm
trigger:
- entity_id: device_tracker.iphonex
platform: state
to: 'home'
condition:
condition: template
value_template: "{{ not is_state('alarm_control_panel.house', 'disarmed') }}"
action:
service: script.turn_on
entity_id: script.alarm_disarm
You could change the trigger and add a condition to only do this if armed in home or perimeter mode.
I posted the script above: YET another take on an alarm system
Did you ever get this sorted? Be handy to use Telegram
While it doesnt pass the template editor until something actually triggers the alarm, it works with facebook and telegram…
'Alarm triggered by {{ states[states.alarm_control_panel.house.attributes.changed_by.split(".")
[0]][ states.alarm_control_panel.house.attributes.changed_by.split(".")[1]].name }}'
note: the alarm_control_panel.house has to be changed with the one being used by you. By default the control panels name is house, but if you have changed it, you have to use the right one. Just check your states in your dev panel.
1 Like
Just a thought, is there any way this could be integrated with custom_updater? At the moment I’m manually patching bugs based on bug reports and suggested fixes on GitHub.
2 Likes
With about 1500 posts in this topic Im sorry if this is asked before. Firstly very good job with this panel, but is it any way to make the control panel more reactive? I tried to use it on a Fire tab 10, and the “keypad” is very slow, at the point if it go from 1-9 with “regular speed” it maybe catches 4-5 of the numbers and some of them is just selected with the grey overlay.
Well, on my Acer Iconia 7 it lags sometimes, but not always. Can’t say it’s super fast, but most of the time it does the job well.
And apparently in the future it might change is the author is slamming to migrate from Polymer to something else, no idea it will impact the things
Just updated to ,88 and get the below error
Thu Feb 21 2019 15:39:50 GMT+1300 (NZDT)
Not passing an entity ID to a service to target all entities is deprecated. Update your call to alarm_control_panel.alarm_disarm to be instead: entity_id: all
Alignment of text and icon in by alarm panel not lining up i.e. away text not in centre of circle it is off to one side
Also on Lovelace ui there is no keypad
Any help would be appreciated
There are a bunch of fixes further up the thread you can make yourself or wait until Gaz releases the next version.
See: 2 bugfixes by akasma74 · Pull Request #69 · gazoscalvertos/Hass-Custom-Alarm · GitHub
and:
and:
also:
and:
More:
I think that’s all of them.
After upgrading to 0.88.0 there are several problems… the MDI update was covered in the post above under the panel-custom change. The custom component directory and python file will need their names swapped to clean up some errors, and I changed up a TON of CSS code to make things more responsive before upgrading but after, it looks like this:
After looking at the breaking changes it seems that they have discontinued use of paper-button and are using mwc-button now. After changing everything over to the new supported version of the button, it places a button within the frame of the existing button and nothing works properly. I reverted and am looking for a fix yet, but this and the image posted a few above is caused by dropping support for paper-button.
Anyone have ideas for getting the replacement working for now, ir ideas for importing paper-button.js back into this component until the new non-polymer UI is released?
Thanks
Have latest files as of the 10th, but some the above still needed to be done thanks
But when you use Lovelace Alarm Panel there is still n Keypad
I’ve just upgraded Hass.io and the only difference I can see is that text is not centered within buttons, but they are still round. Cleared cache before checking.
and yes, it says “WARNING (MainThread) [homeassistant.loader] Integrations need to be in their own folder. Change alarm_control_panel/bwalarm.py to bwalarm/alarm_control_panel.py. This will stop working soon.”