I’m going to try that solution.
Thanks
Would this be an idea? Apparently it won’t work for the HTML files etc but would work for the “custom component” element of it. I guess if it won’t update as a whole it might be counterproductive and confusing.
The alarm in principle works well. Although with version 88.1 the panel numbers are smaller and do not look good. Any ideas?
Already reported earlier.
I have the same. Don’t have time to look into it as it’s still functional.
But UGLY 
For those who wants to get rid of the following warning in HA log
[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.
Just do what they say, namely: in create /config/custom_components/bwalarm folder, move bwalarm.py there and rename it to alarm_control_panel.py. Then it’s safe to remove /config/custom_components/alarm_control_panel folder
IMPORTANT UPDATE: if you set logging level for the alarm, it’s affected by this change and you need to change its full name. For example, in configuration.yaml it should be:
default: warning
logs:
# old style naming, doesn't work
# custom_components.alarm_control_panel.bwalarm: debug
custom_components.bwalarm.alarm_control_panel: error
A word of caution regarding 0.88.1 - make sure all your automations have initial_state: true as they will be disabled by default.
This was a requirement after .85 i believe, so hopefully most people have made the change
lets hope
My config was functional on 0.88.0, but after upgrading to 0.88.1 I found few automations not working exactly because they had no explicit initial_state.
One thing you can do is edit www/alarm/alarm.css. On lines 802 and 595 (edit: 486 as well) add:
justify-content: center;
align-items: center;
Of course you’ll have to clear your cache to see the changes. There also might be other places, those are just the ones that affected me.
What about Lovelace ???
I was wondering if anyone has used Xiaomi Vibration sensors successfully for triggering the Hass Custom Alarm?
The default config that HA sets up for this vibration sensor does not work so I found that the correct way to detect a vibration is to use “movement_type: vibrate” for example:
- alias: Side Kitchen door vibrate sensor
trigger:
platform: event
event_type: xiaomi_aqara.movement
event_data:
entity_id: binary_sensor.vibration_10000000000
movement_type: vibrate
action:
- service: notify.pushover
data:
message: Side Kitchen Door Vibration Detected
The above automation works perfectly when the door is banged.
I think that Hass Custom Alarm uses the default HA config for this sensor. If that is the case, is there somewhere in Hass Custom Alarm files I can change the event data for this sensor to movement_type: vibrate?
Cheers!
Can anyone help me uninstall this component? There are thousands of these entries in my log file and I’m sick of trying to make this work:
2019-02-27 19:38:04 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: domain=system_log, service=write, service_data=logger=frontend.js.es5.201902200, message=http://192.168.1.117:8123/api/panel_custom/alarm:2092:41 Uncaught TypeError: Cannot read property ‘state’ of undefined>
2019-02-27 19:38:04 ERROR (MainThread) [frontend.js.es5.201902200] http://192.168.1.117:8123/api/panel_custom/alarm:2092:41 Uncaught TypeError: Cannot read property ‘state’ of undefined
2019-02-27 19:38:04 DEBUG (MainThread) [homeassistant.components.websocket_api.http.connection.547818364768] Sending {‘id’: 4429, ‘type’: ‘result’, ‘success’: True, ‘result’: None}
2019-02-27 19:38:04 INFO (MainThread) [homeassistant.components.http.view] Serving /api/error_log to 192.168.1.120 (auth: True)
2019-02-27 19:38:04 DEBUG (MainThread) [homeassistant.components.websocket_api.http.connection.547818364768] Received {‘type’: ‘call_service’, ‘domain’: ‘system_log’, ‘service’: ‘write’, ‘service_data’: {‘logger’: ‘frontend.js.es5.201902200’, ‘message’: “http://192.168.1.117:8123/api/panel_custom/alarm:2092:41 Uncaught TypeError: Cannot read property ‘state’ of undefined”}, ‘id’: 4430}
I’m running Hass.IO, .88.1, on a Raspberry Pi 3 B+ 64bit. TIA!
Thanks !! 
The alarm works fine, but after a few hours, any attempt to change status stops working.
I receive this warning.
Log Details (WARNING)
Not passing an entity ID to a service to target all entities is deprecated. Update your call to alarm_control_panel.alarm_arm_away to be instead: entity_id: all
if restart the HA works again correctly, but unfortunately only works a few hours.
the restart I do not see it as a solution 
I tried this, but I did not solve the problem:
I don’t know what is “default config for a sensor” in HA.
If the automation works for you, create a input_boolean and turn it on in your action instead of sending a message.
Use that input_boolean as a sensor in the alarm.
And don’t forget to turn off the input_boolean after say, 5 seconds after it’s on.
That should do the trick
is the custom component working on0.88.1 or it need to be upgrated?
Thanks, very useful. It might be a good idea to add what styles one need to apply it too as many of us have alarm.css edited so line numbers might vary… 