YET another take on an alarm system

carlostico · February 27, 2019, 11:53pm

What about Lovelace ???

gitgrooves · February 27, 2019, 11:58pm

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!

krinehart · February 28, 2019, 2:42am

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!

Cress · February 28, 2019, 6:13am

Thanks !!

Cress · February 28, 2019, 6:16am

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:

AhmadK · February 28, 2019, 7:03am

Try this one

AhmadK · February 28, 2019, 7:14am

You can fix at least some of your errors.
Regarding

try to edit alarm.html as described here

AhmadK · February 28, 2019, 7:17am

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

nebbiadigiorno · February 28, 2019, 9:41pm

is the custom component working on0.88.1 or it need to be upgrated?

AhmadK · February 28, 2019, 9:45pm

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…

AhmadK · February 28, 2019, 9:48pm

Do you call this alarm panel “the custom component”?
If yes then my one is working fine on 0.88.1, but I don’t know how to upgrate it as the latest release of this alarm panel happened much earlier than 0.88.1 came out.
And there are some unmerged patches that fix some wrong behaviour so you might need to patch your copy as well.

AhmadK · March 1, 2019, 8:53am

What do you mean?

lostage · March 1, 2019, 3:18pm

You might check your alarm.yaml and make sure your code: is not in quotation marks:

code: 1234

I also did that for panic_code: though, not sure if it’s needed.

After making the updates you’re referring to and doing that, the keypad is working once again for me. Hopefully you’ll have the same experience.

Yoinkz · March 1, 2019, 8:36pm

Did anyone try changing this?

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.

AhmadK · March 1, 2019, 9:10pm

Did you try reading this?

Yoinkz · March 1, 2019, 11:57pm

I guess not .
Thanks!

gitgrooves · March 3, 2019, 4:25pm

Thank you for the guidance AhmadK! I will have a look at input_boolean and see how I can use it.

Cress · March 3, 2019, 8:46pm

Hi
Could you share the file bwalarm.py? I have applied different arrangements and I am not sure if it is correct.
Thanks

manzn · March 4, 2019, 9:00pm

Hy!

First at all THANKS @gazoscalvertos for this genius piece of software …

I like it for configuration - but its not working in landscape mode on my Fire 8 HD.
So I build with Node-Red this Alarm Panel - its working with the alarm states of the alarm_control_panel and mqtt.

Its not finish at the moment - but its working for enable/disable alarm and show the current state.

For MQTT fix I use this version of the bwalarm.py LINK from Tyre88

What do you think?

AhmadK · March 4, 2019, 9:23pm

What do you mean by that?