updatin gto 0.92 gives this error, any clue?
2019-04-27 15:14:52 ERROR (MainThread) [homeassistant.setup] Error during setup of component alarm_control_panel
Traceback (most recent call last):
File “/usr/local/lib/python3.7/site-packages/homeassistant/setup.py”, line 156, in _async_setup_component
component.setup, hass, processed_config) # type: ignore
AttributeError: module ‘custom_components.alarm_control_panel’ has no attribute ‘setup’
plus also create an empty __init__.py and place this with the file above in the same folder as the bwalarm component
I only created manifest.json and have no issues after updating to 0.92.0
Same, but others have had to create the __init__.py file also to get not just this but other custom components to work
Ok, I’ve just created a fork of this alarm panel that incorporates most of fixes/PRs to the original one (up to HA 0.92.0 inclusive) and you can check it out here.
Not sure if I need to create a separate topic for it… thoughts?
Open to ideas/suggestions. Enjoy!
As it’s only a temporary thing I reckon here is good. Unless you start adding features and the fork drifts to a project of it’s own.
Thanks for doing this.
nice work with the fork
only query i have is the folder structure for the great migration
in your fork you have
custom_components/alarm_control_panel/bwalarm/alarm_control_panel.py
should it not be
custom_components/bwalarm/alarm_control_panel.py
You’re right, that’s fixed now.
Well, my thought was it’s easy to get confused for new users or people who didn’t read the whole 1768 posts in this topic (I know none!) to get the idea that it’s pointless to use the OP’s repository at the moment and they have to use mine one until the author is back.
There is no way to update the original post as well so it’s hard to convey that fork announcement.
And when they go “I followed the instructions and installed the latest version” what should we ask them first? Every single time? 
But I’m not insisting…
You know one 
You also make a good point about the confusion it could cause. So I’ve changed my mind. You would probably be better off making a new post.
ANNOUNCEMENT
Anyone who is interested in having a working version of this component is welcome to join a new topic dedicated to my fork that incorporates most of the fixes and pull requests up to this date.
I’ll follow mainly that topic to help with resolving further issues/PRs provided one uses that fork because at the moment there is little sense in supporting what’s in the OP’s GitHub as it’s just way too outdated.
Do you know how to get the round buttons :)?
Are you asking about those Home/Away buttons?
You can have them round, but it won’t be great to my taste, that’s why I have them rectangular.
Just edit alarm.yaml so in panel section there is
round_buttons: true
or go to Alarm -> Settings and change it there.
Fixed some css. But I cant get the Number bigger and change color…
Works with inline css in chrome. But not in the css file. Any ideas?
Sorry, I don’t know… just played around with the .css file to make the panel looking less ugly
A slightly left field question – has anyone got a good solution for an alarm keypad that meets the “family acceptance factor” ?
I found a solution online using an RPi Zero W and touchscreen, but i could just never get it working.
I have built something that works using an ESP8266 NodeMcu board, with LCD and keypad, but its considered “ugly”
Has anyone managed to interface with an exisitng alarm keypad or anything like that ?
Long time ago I decided to have a 7" Android tablet as control panel for my alarm, and I still like the result.
It’s inexpensive and MILES more flexible than any hardware configuration. My only wish at the moment is to change its connection from WiFi to Ethernet…
Hello to everyone, I’m new here so maybe I’m asking a silly question… is there a way to exclude a sensor if it’s on the “on” state at the moment of arming? I explain with an example: I have a small window in my bedroom and i usually open it during summer nights; if i open it and then arm the alarm, after a while it is triggered by the “open” state of the window sensor. The only solution is not to use the sensor at all. 
I’m a bit confused.
You cannot arm the alarm with your window open unless you click Override when it says there are open sensors.
And if you do so, the only reason for the alarm to trigger is if the window’s sensor changes its state to active, i.e from closed to open. It shouldn’t happen just “after a while”…
So could you be as detailed as possible about your issue?
One more important note - this component is abandoned at the moment. Please read this.
