YET another take on an alarm system

brillb · September 30, 2018, 10:00pm

Yes, I see that now. Apparently I had the old file stuck in browser cache. Had to do clear cached data to get a refresh of that page. It now is working. Also I like where you moved the “0” button to, it makes more sense there.

mar_robHD · October 3, 2018, 5:54pm

How can I go to this GUI

tom_l · October 3, 2018, 11:12pm

Follow the instructions here:

github.com

gazoscalvertos/Hass-Custom-Alarm/blob/master/guidance/configuration.md

## Installation Guide
To get this running add the files (alarm.yaml, panels/alarm.html, custom_components/alarm_control_panel/bwalarm.py, www/lib/countdown360.js, www/lib/jquery-3.2.1.min.js, www/alarm/alarm.css) from this repo into your home assistant configuration directory, then add the following to your configuration.yaml file:

**NOTE:** If you already have a panel_custom.yaml for say floorplan then just copy and paste the code from this repo file into your own panel_custom.yaml to prevent floorplan from being overritten.
**NOTE:** Same goes for Automations.yaml. Append the samples inside of this file into your own automations.yaml

```
alarm_control_panel: !include alarm.yaml
panel_custom: !include panel_custom.yaml
```

**NOTE:** If you experience issues with the page not displaying then add the following:
```
#CONFIGURATION.YAML
frontend:
  javascript_version: latest
```
## Configuration variables:

**Alarm.yaml configuration settings:**

This file has been truncated. show original

vlamofiel · October 4, 2018, 12:02pm

Maybe a noob question, but couldn’t find it via search nor in the Configuration manual on github. I would like different scripts to be triggered based on the different Alarm Modes, so for Home Mode trigger X, for away mode trigger Y and for perimeter mode, trigger Z. How can I achieve that? Shouldn’t something like that be added to the manual page?

sparkydave · October 5, 2018, 1:00am

currently the automations for this alarm only have the single action for ALL alarm modes.

tom_l · October 5, 2018, 1:12am

I was thinking you could differentiate them with templates in the action section of the alarm_triggered automation, however

{{ states.alarm_control_panel.house.state }}

Changes from armed_away, armed_home or armed_perimeter to triggered as soon as it is triggered.

So you would have to use an input_select or mqtt sensor to store the state of states.alarm_control_panel.house.state when the alarm is armed. You could then use this to template conditions in the alarm_triggered automation actions. You may also have to set this input select (or mqtt sensor) to disarmed with the alarm_disarmed automation.

dasbooter · October 6, 2018, 3:52am

Wow this seemed to cool for a newb like me to set up but the directions were clear enough that I actually got this going somewhat. I have a few hue motion sensors going and was actually able to engage and trigger an alarm/automation (turning on a very scary angry red hue light bulb lol).

I have this in my logs though and thought I would check in:

 Log Details (WARNING)

Fri Oct 05 2018 22:34:16 GMT-0500 (Central Daylight Time)

Unable to find service alarm_control_panel/

Should I worry about this? Did I miss something? Clearly I have alot more to do but thanks a bunch gazos and all who contributed

Garrett.Raney · October 12, 2018, 12:57am

I feel like it’s probably fair to go ahead and change the title to be “THE BEST take on an alarm system”.

Just got everything up and running and fully tested. It’s working like a charm! This alarm is simple, has great UX, and the config makes it a breeze to implement. Seriously good work here. Thanks! I bought you a beer

I’m using mine with door/window sensors, shock sensors, and PIR sensors all from Monoprice. If anyone has issues w/ these devices (I had many issues w/ the hardware…) hit me up, I might be able to help, or can share my configs at least.

tremebundo · October 12, 2018, 9:24am

It could be nice to get your configs to get some inspiration.

aidbish · October 12, 2018, 11:45pm

Just did an upgrade to .80 and the alarm no longer arms. getting the below error.
Going back to 79.3 fixes it.

2018-10-12 23:41:13 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File “/usr/src/app/homeassistant/helpers/service.py”, line 224, in _handle_service_platform_call
await getattr(entity, func)(**data)
File “/usr/local/lib/python3.6/concurrent/futures/thread.py”, line 56, in run
result = self.fn(*self.args, **self.kwargs)
File “/config/custom_components/alarm_control_panel/bwalarm.py”, line 476, in alarm_arm_home
self.process_event(Events.ArmHome)
File “/config/custom_components/alarm_control_panel/bwalarm.py”, line 574, in process_event
switch.turn_on(self._hass, self._warning)
AttributeError: module ‘homeassistant.components.switch’ has no attribute ‘turn_on’

may have something to do with breaking changes

Developers only: we have removed all service helpers (like turn_on method in light coponent), as they werent used. (@cdce8p - #16832 , #16879, #16863 , #16892, #16920 , #17038, #17055, #16917 )

marine88 · October 13, 2018, 5:47pm

1 is broken in new version of homeassistant

cdce8p · October 13, 2018, 10:14pm

Custom components must now use hass.services.call(DOMAIN, service, data) or hass.services.async_call instead of switch.turn_on. That’s indeed related to the breaking changes you mentioned.

github.com

home-assistant/core/blob/dev/homeassistant/core.py#L1073-L1128


    self._services: Dict[str, Dict[str, Service]] = {}
    self._hass = hass

@property
def services(self) -> Dict[str, Dict[str, Service]]:
    """Return dictionary with per domain a list of available services."""
    return run_callback_threadsafe(self._hass.loop, self.async_services).result()

@callback
def async_services(self) -> Dict[str, Dict[str, Service]]:
    """Return dictionary with per domain a list of available services.

    This method must be run in the event loop.
    """
    return {domain: self._services[domain].copy() for domain in self._services}

def has_service(self, domain: str, service: str) -> bool:
    """Test if specified service exists.

    Async friendly.

This file has been truncated. show original

gazoscalvertos · October 13, 2018, 11:00pm

ok folks have identified the issue and believe I have a fix to resolve the defect caused by the withdrawal of the switch.turn_on. Will test and update tomorrow.

For those interested it should be a case of replacing the switch.turn_on (or off) with:

                    self._hass.services.call('switch', 'turn_on', self._config.get(CONF_WARNING))

Respectively

Kelvin_Sudlow · October 14, 2018, 6:53pm

Great Hope this fix’s the issue as I have no alarm now

tbrasser · October 14, 2018, 9:40pm

I don’t know how, but I’m on 0.80 and arming the alarm (arm home) still seems to work? How?

Does it affect only a specific function like disarming or arming away mode?

It works from both the ha frontend, including Lovelace and from the alarm panel.

gazoscalvertos · October 14, 2018, 9:54pm

It’s only effecting those users who have switches defined in the yaml file for the warning and alarm settings.

It won’t effect the majority of users as most tend to use automations to do something when the alarm state has changed

gazoscalvertos · October 14, 2018, 9:57pm

How many of you are using the newUI? Any feedback? I’m going to put this live in the repo shortly.

Also working on a standalone webpage which runs outside of the home assistant UI for security purposes (Wall Panels at egress). The standalone site will also be prone to less defects as it moves away from the complicated HA/polymer setup and passes the traffic via Websockets

This should also help with legacy devices (older IOS/Android) as I’ll compile a version for javascript es5 too. One of my older devices (Galaxy Tab 10.1) struggles to run the interface, very laggy as it doesn’t have a lot of ram.

Also toying with the idea of creating dedicated android/ios apps.

marine88 · October 14, 2018, 11:37pm

i think its a very good idea tge android app i have 1 tablet on my wall just to homeassistant!

suds32 · October 15, 2018, 1:30am

great idea

aidbish · October 15, 2018, 7:21am

Hi @gazoscalvertos

Just wondering if the update will be pushed today, would like to update to .80 to test another component