nielsfaber / alarmo Goto Github PK

Today you can enable the "Allow open" sensor option only if you first disable the "Immediate" option. This should not be the case IMHO.
I have a corridor with motion sensor which is leading me to my entry area. If I walk out fast it could be that I will fail to arm the alarm as the sensor is still active. The way to allow me to ignore it is to set the "Allow open" option (which is I love) but then I have the side effect that I also need to mark it not immediate which is not accurate. I want the alarm to trigger immediately if someone get to the hallway without first disabling the alarm.
So, I think these 2 options should get separated and allow me to set "Allow open" to sensors even if I do want them to trigger the alert immediately if they turn on later.

hello could you include a setup menu for the siren entity (switch) with the times to set? I ask this because in Italy there are rules that regulate the activation times of the siren.

in fact, to avoid breaking the laws relating to alarms, an intrusion alarm must not sound more than 3 minutes in total, which is the maximum duration allowed.

I'd like to send notifications to more than one target.

I renamed a number of my sensors, but Alarmo still refers to their original names. I completely remove Alarmo and restarted HA, then re-installed Alarmo, and it still refers to the sensors by the old names, and does not find them by their new names.

For Alarmo to interface with and control an external alarm system there is a requirement to send outgoing MQTT messages to the external alarm. Since the external alarm is a security device it requires a passcode. Doing so allows HA to control the external alarm system such that HA and the external Alarm system remain synchronised.

Please provide support to allow sending of passcodes in the outgoing MQTT messages.

Please also allow for subcommands to be sent in the MQTT message.

ie:

JSON Payload template
   {
    "password":"1234",
    "Command":"arm",
    "Subcommand":"0"
   }

Having subcommands will also allow for controlling multiple 'Areas' in future.

I'm trying to add a motion sensor that is attached to a light switch (the Jasco Motion Sensor Switch) to use with my alarmo config... it doesn't show up as a sensor when configuring. Is this a bug or needs to be added as a feature?

I enabled push messages and now I can't disable them. I tried to refresh cache browser, etc but push messages are enabled each time I check them. Doesn't mind if I vary "target for push messages" option.

I have a number of Sensative Strip Guards that I use to monitor doors open / close state. Since these report a value 22/23 back for the open/close state, I have wrapped them in a binary sensor to allow them to be used in Alarmo.

The issue observed is that although Alarmo does pick up that a sensor changes state to open (= alarm is triggered), the correct sensor is not listed in open.sensors. In fact a completely unrelated sensor is sent along when this state change occurs (despite that sensor is actually in an off state - a verification has been made, and did confirm that this is the case when the event is triggered).
The effect is that notifications sent by Alarmo do not accurately depict what actually has occurred.

This is with the new version of alarmo.

Opening the UI locally works as expected. I have websockets support enabled in the Nginx Proxy Manager, and HA also does not have issues establishing websockets. However, if accessed externally, this is what i get in the dev console when i try to open the UI:

alarmo:1086 Uncaught (in promise) TypeError: Cannot convert undefined or null to object at Function.entries (<anonymous>) at HTMLElement.render (alarmo:1086) at HTMLElement.update (alarmo:186) at HTMLElement.performUpdate (alarmo:148) at HTMLElement._enqueueUpdate (alarmo:148) render @ alarmo:1086 update @ alarmo:186 performUpdate @ alarmo:148 _enqueueUpdate @ alarmo:148 async function (async) _enqueueUpdate @ alarmo:148 requestUpdateInternal @ alarmo:148 set @ alarmo:148 (anonymous) @ chunk.6291eb9f40d952ac49d9.js:1 l @ chunk.6291eb9f40d952ac49d9.js:1 _setProperties @ chunk.6291eb9f40d952ac49d9.js:1 value @ chunk.6291eb9f40d952ac49d9.js:1 performUpdate @ app.8efb5ced.js:10288 _enqueueUpdate @ app.8efb5ced.js:10288 async function (async) _enqueueUpdate @ app.8efb5ced.js:10288 requestUpdateInternal @ app.8efb5ced.js:10288 set @ app.8efb5ced.js:10288 value @ app.8efb5ced.js:43529 value @ app.8efb5ced.js:39299 performUpdate @ app.8efb5ced.js:10288 _enqueueUpdate @ app.8efb5ced.js:10288 async function (async) _enqueueUpdate @ app.8efb5ced.js:10288 requestUpdateInternal @ app.8efb5ced.js:10288 set @ app.8efb5ced.js:10288 commit @ app.8efb5ced.js:10288 commit @ app.8efb5ced.js:10288 update @ app.8efb5ced.js:10288 __commitTemplateResult @ app.8efb5ced.js:10288 commit @ app.8efb5ced.js:10288 a @ app.8efb5ced.js:10288 H.render @ app.8efb5ced.js:10288 update @ app.8efb5ced.js:10288 performUpdate @ app.8efb5ced.js:10288 _enqueueUpdate @ app.8efb5ced.js:10288 async function (async) _enqueueUpdate @ app.8efb5ced.js:10288 requestUpdateInternal @ app.8efb5ced.js:10288 set @ app.8efb5ced.js:10288 commit @ app.8efb5ced.js:10288 commit @ app.8efb5ced.js:10288 update @ app.8efb5ced.js:10288 __commitTemplateResult @ app.8efb5ced.js:10288 commit @ app.8efb5ced.js:10288 update @ app.8efb5ced.js:10288 __commitTemplateResult @ app.8efb5ced.js:10288 commit @ app.8efb5ced.js:10288 a @ app.8efb5ced.js:10288 H.render @ app.8efb5ced.js:10288 update @ app.8efb5ced.js:10288 performUpdate @ app.8efb5ced.js:10288 _enqueueUpdate @ app.8efb5ced.js:10288 async function (async) _enqueueUpdate @ app.8efb5ced.js:10288 requestUpdateInternal @ app.8efb5ced.js:10288 set @ app.8efb5ced.js:10288 value @ app.8efb5ced.js:41533 (anonymous) @ app.8efb5ced.js:41533 s @ core.bcfce4ca.js:1 (anonymous) @ core.bcfce4ca.js:1 (anonymous) @ core.bcfce4ca.js:1 _handleMessage @ core.bcfce4ca.js:1 (anonymous) @ core.bcfce4ca.js:1

After the change to the new model trying to add users is now very slow. Not sure if there's anything that can be done about it but I thought I would just note it. I ended up pressing save twice and saving the new user twice

Opening the alarm panel settings page on the android HA app you can't actually see all the settings when it's in portrait mode - page is too wide.

The notification is received but when I push the "Retry Arm" button on ios an error occurs in HA core. I've set up the actionable notification as follows and the error is below.

ios:
  push:
    categories:
      - name: Alarm Arm Failure
        identifier: alarmo_arm_failure
        actions:
          - identifier: ALARMO_RETRY_ARM
            title: Retry Arm # feel free to change this text
            destructive: true
          - identifier: ALARMO_FORCE_ARM
            title: Force Arm # feel free to change this text
            destructive: true

2020-12-08 11:43:53 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved Traceback (most recent call last): File "/config/custom_components/alarmo/alarm_control_panel.py", line 598, in async_handle_event elif event.data["action"]: KeyError: 'action'

Hi,
As the name suggests, I propose an extra state attribute with the friendly names of the current {{open_sensors}} attribute.
Use case: this way smart speakers can announce the reason for the alarm trigger (in case they don't like the notification component or to build bigger trigger scripts).
Thanks

Again, an incredible tool! Thank you very much!

A suggestion, and maybe this is already in process, but having each action have it's own duration could be good. I have my alarm set up to run the siren for 5 minutes, but leave the lights on for 20 minutes (if lights and siren go off at the same time, it might not be enough of a deterrent, at least that's my logic).

Thank you very much for these integrations! They are a huge upgrade to YAML-based config.

Brandon

No way to add/edit notification message.

I am trying to set up Mqtt at Alarmo.
I can get the state with several clients and disarm the alarm, but I can not arm_away or arm_home with them.
I have tried with MQTTLens, which is an addon for Chrome and some kind of Mqtt sniffer and lets you to send commands to the subscribed topics. I have also tried with the Android app MQTT Alarm Control Panel and I get the same behaiviour.
It works for disarming but not for the two disarming modes.

Hello
What Siren do you use?
I have gateway xiaomi, which could not be directly triggered, but just put alarm on or off, it can't command and play siren directly
Thanks
Michael

As discussed on the Home Assistant forum, there should be some different options around each sensor. My existing alarm system is really good for this. So you can set a sensor to be:

• Immediate
• Entry/Exit
• 2x Entry Delay
• 4x Entry Delay
• Fire

Immediate is as you currently have, whilst entry/exit allows the current delays. 2 and 4 times are useful for things like garages where the garage door opens but you don't necessarily get in to turn it off quickly enough.

Fire will always cause the alarm to go off whether the alarm is activated or not.

Hopefully you can implement something like this - would be great!

For some reason this alarm panel doesn't see all my binary sensors. E.g: binary_sensor.sm_g988b_is_charging. May be a good reason for this, but I can't see it because the text in the section for adding sensors is cut off. It gets as far as this "There are no available HA entities that can be configured for the alarm. Make sure to include ent":

Turn the alarm on from the overview page. Then try and add a user in the alarm panel page and click save and doesn't save. Turn the alarm off and it will save. The behaviour is probably correct it's just a bit confusing, so would be good if there was a message to say it wasn't able to be added.

I'm enjoying the integration thus far (thank you for your efforts!), and as I'm a recent convert from SmartThings one thing I did like was being able to trigger alarm states based on geofencing of my mobile devices. Is this something possible to add as a way to arm and disarm? Also any thoughts on when we'll be able to trigger a siren within this integration? I use Konnected for my devices and that one isn't working yet

I installed alarm and have set it up as I wanted. But sometimes the system armes itself and triggers without any one of us arming the system before.

Very annoying when all of a sudden the sirens go off at home.

Logger: homeassistant.components.alarm_control_panel
Source: core.py:1401
Integration: Alarm control panel (documentation, issues)
First occurred: 10:35:51 AM (2 occurrences)
Last logged: 10:35:51 AM

Error adding entities for domain alarm_control_panel with platform alarmo
Error while setting up alarmo platform for alarm_control_panel
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 316, in async_add_entities
await asyncio.gather(*tasks)
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 507, in _async_add_entity
await entity.add_to_platform_finish()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 530, in add_to_platform_finish
await self.async_added_to_hass()
File "/config/custom_components/alarmo/alarm_control_panel.py", line 356, in async_added_to_hass
await self.async_update_state(STATE_ALARM_DISARMED)
File "/config/custom_components/alarmo/alarm_control_panel.py", line 393, in async_update_state
await self.automations.async_handle_state_update(state=state, last_state=last_state)
File "/config/custom_components/alarmo/automations.py", line 71, in async_handle_state_update
await self.async_execute_automation(automation_id)
File "/config/custom_components/alarmo/automations.py", line 117, in async_execute_automation
await async_call_from_config(
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 97, in async_call_from_config
await hass.services.async_call(*parms, blocking, context)
File "/usr/src/homeassistant/homeassistant/core.py", line 1401, in async_call
raise ServiceNotFound(domain, service) from None
homeassistant.exceptions.ServiceNotFound: Unable to find service notify/alexa_media

Hi,
This is with ver. 1.1.0
I have only two sensors configured: one entry door sensor and a movement one.
When I try to arm, I get this in the log:

2020-11-16 18:02:42 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.139730749224128] 'NoneType' object has no attribute 'items' Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 135, in handle_call_service await hass.services.async_call( File "/usr/src/homeassistant/homeassistant/core.py", line 1448, in async_call task.result() File "/usr/src/homeassistant/homeassistant/core.py", line 1483, in _execute_service await handler.job.target(service_call) File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 204, in handle_service await self.hass.helpers.service.entity_service_call( File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 482, in entity_service_call future.result() # pop exception if have File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 664, in async_request_call await coro File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 519, in _handle_entity_call await result File "/config/custom_components/alarmo/alarm_control_panel.py", line 265, in async_alarm_arm_away await self.async_arm(STATE_ALARM_ARMED_AWAY) File "/config/custom_components/alarmo/alarm_control_panel.py", line 428, in async_arm await self.async_update_state(STATE_ALARM_ARMING) File "/config/custom_components/alarmo/alarm_control_panel.py", line 393, in async_update_state await self.automations.async_handle_state_update(state=state, last_state=last_state) File "/config/custom_components/alarmo/automations.py", line 71, in async_handle_state_update await self.async_execute_automation(automation_id) File "/config/custom_components/alarmo/automations.py", line 108, in async_execute_automation changed_by_string = self.async_format_sensor_info(changed_by) File "/config/custom_components/alarmo/automations.py", line 127, in async_format_sensor_info for (entity_id, status) in open_sensors.items(): AttributeError: 'NoneType' object has no attribute 'items' 2020-11-16 18:02:48 WARNING (MainThread) [custom_components.alarmo.alarm_control_panel] Cannot go to state armed_away from state arming. 2020-11-16 18:02:52 WARNING (MainThread) [custom_components.alarmo.alarm_control_panel] Cannot go to state armed_home from state arming.

If you need more data, please ask me.

Thanks for your interest.

Hi,

Can we please implement a feature allowing certain users or codes perform a master-override when arming?
Master-override means that any sensors that are either active or failed will not block arming the alarm nor trigger the alarm, instead they would be bypassed and set as disabled for the session. Active or failed sensors that block arming is troublesome for me as the alarm is to arm automatically when I leave and as I leave by car I can't stop in the middle of the highway because a sensor is failed or delibarately left active and the alarm won't arm. This means the alarm is left disarmed far longer than I want.

Scenario is f.ex.:

1. Window in the bathroom is left open to air out, window is usually not left open.
2. User leaves house, alarm tries to arm automatically.
3. Alarm notices window is left open over the allowed time, but since it's asked to arm anyways it does.
4. Alarm bypasses the sensor, logging this and then arms the alarm.
5. User can then be notified that alarm is armed, but that sensor is bypassed due to active/error.

Hi.
I my previous domotic system I was able to define multiple alarm partitions, individually configurable and usable: I was able to define wharehouse / house1 / house2 partitions, each with its sensors/users/settings.

This feature could be so useful in a large installation.

Logger: homeassistant.components.websocket_api.http.connection
Source: custom_components/alarmo/alarm_control_panel.py:289
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 12:19:19 PM (3 occurrences)
Last logged: 12:19:48 PM

[140178131266768] 'bool' object is not subscriptable
[140178161299408] 'bool' object is not subscriptable
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 135, in handle_call_service
await hass.services.async_call(
File "/usr/src/homeassistant/homeassistant/core.py", line 1451, in async_call
task.result()
File "/usr/src/homeassistant/homeassistant/core.py", line 1486, in _execute_service
await handler.job.target(service_call)
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 204, in handle_service
await self.hass.helpers.service.entity_service_call(
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 499, in entity_service_call
future.result() # pop exception if have
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 664, in async_request_call
await coro
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 536, in _handle_entity_call
await result
File "/config/custom_components/alarmo/alarm_control_panel.py", line 305, in async_alarm_arm_home
await self._async_handle_arm_request(STATE_ALARM_ARMED_HOME, code, skip_code)
File "/config/custom_components/alarmo/alarm_control_panel.py", line 289, in _async_handle_arm_request
elif res[ATTR_IS_OVERRIDE_CODE]:
TypeError: 'bool' object is not subscriptable

I'm testing with 1.1. Looks like I may have added my user with the wrong pin code, because I can't arm currently.

So tried to change the code (entered what I think was the old code, but most likely wrong code, and new code x2) and got the following error:
Something went wrong!

Response error: 500

Please report the bug.

Log details:
Logger: aiohttp.server
Source: custom_components/alarmo/init.py:155
First occurred: 9:21:32 AM (3 occurrences)
Last logged: 9:31:46 AM

Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/aiohttp/web_protocol.py", line 418, in start
resp = await task
File "/usr/local/lib/python3.8/site-packages/aiohttp/web_app.py", line 458, in _handle
resp = await handler(request)
File "/usr/local/lib/python3.8/site-packages/aiohttp/web_middlewares.py", line 119, in impl
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 18, in request_context_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 72, in ban_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 127, in auth_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 129, in handle
result = await result
File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 60, in wrapper
result = await method(view, request, *args, **kwargs)
File "/config/custom_components/alarmo/websockets.py", line 190, in post
coordinator.async_update_user_config(user_id, data)
File "/config/custom_components/alarmo/init.py", line 138, in async_update_user_config
elif not self.async_authenticate_user(data[ATTR_OLD_CODE], user_id):
File "/config/custom_components/alarmo/init.py", line 155, in async_authenticate_user
if not user[ATTR_CODE] and not code:
TypeError: 'UserEntry' object is not subscriptable

I know that this superb project is still in early beta stage :-)
But for everyday use by family it would be nice to have native language setup (OK thanks to lokalise we have a frontend native language for Alarm Panel at least)- as some of them are smart enough to add/delete something (with permissions but not enough English knowledge :-( )
That would make a great WAF effect :-)
Best, JR

The state topic should be posted with retain, so that Keypads or other interfaces, can pick it up upon a restart.

I have something strange going on (i did a hard refresh this time!) and with the new version the functionality for requiring a pin for arming/disarming is inverted for me.

E.g. if i turn on the require pin for arming, then it doesn't require pin for arming, but instead for disaming. Same thing happens if i turn the other one on, disarming becomes arming.

I hope all this makes sense.

I dont know if i should open a new issue, but also, if the leave time is set to None, the alarm will not Arm. (tested for arm home/arm night)

Love your creation, thank you for your efforts. I'm a user, not developer, so "operator error" is likely, but I am having trouble getting my messaging edits to "stick". Simply trying to add "type: tts" in YAML editor. It works (messages make it to ECHO device) but the addition seems to disappears in next edit. Am I missing something?

I think it'd be a good idea to hide the Alarmo configuration panel for users that are not home assistant administrators.

Currently a non-admin user can just go in and create a code and have full control of the alarm.

Hi.
As subject says, could be useful to let the user to choose a siren duration under the minute.
I use an interior siren and a 1min duration is too much (imagine during the night a false alarm that turn on the siren for a minute..) :D
The best this could be a base value available as entity that define the siren duration, so we can change the duration with an automation (armed night set duration to 15s or less, armed away to a minute).

HACS installation works but it copies lot of source files into your HA deployment which are not really needed.
Specifically, I see lot of files in the frontend subfolder compared to what you get with manual installation.
Nothing really broken by that, but this is just something which can get cleaned-up eventually.

Currently if I have sensor which is configured to "allow open" and it is active while trying to arm the alarm the arming will fail.
This is because of the following logic in validate_event function

           sensor_config = self._config[entity]
            if event == EVENT_LEAVE and not sensor_config[ATTR_IMMEDIATE]:
                continue
            elif event == EVENT_ARM and sensor_config[ATTR_ALLOW_OPEN]:      
                continue          #<--- We expected this continue statement to execute and skip the validation of this sensor but the state is EVENT_LEAVE and not EVENT_ARM so we skip this if statement.

I think the fix should be:

            sensor_config = self._config[entity]
            if event == EVENT_LEAVE and not sensor_config[ATTR_IMMEDIATE]:
                continue
            if event in [EVENT_LEAVE, EVENT_ARM] and sensor_config[ATTR_ALLOW_OPEN]:
                continue

I tested it on my setup and it seems to do what I would expect but maybe i'm missing something.

Version used: 1.2.0
Going to settings, enable MQTT, save:

Response error: 500

I'm using MQTT in several other devices, without any issue.

Error reported in the log:

Logger: aiohttp.server
Source: custom_components/alarmo/alarm_control_panel.py:228 
First occurred: 8:15:58 AM (4 occurrences) 
Last logged: 8:17:55 AM

Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/site-packages/aiohttp/web_protocol.py", line 422, in _handle_request
    resp = await self._request_handler(request)
  File "/usr/local/lib/python3.8/site-packages/aiohttp/web_app.py", line 499, in _handle
    resp = await handler(request)
  File "/usr/local/lib/python3.8/site-packages/aiohttp/web_middlewares.py", line 118, in impl
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 172, in forwarded_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 18, in request_context_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 127, in auth_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 129, in handle
    result = await result
  File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 60, in wrapper
    result = await method(view, request, *args, **kwargs)
  File "/config/custom_components/alarmo/websockets.py", line 98, in post
    await coordinator.async_update_config(data)
  File "/config/custom_components/alarmo/__init__.py", line 107, in async_update_config
    await self.config_callback()
  File "/config/custom_components/alarmo/alarm_control_panel.py", line 228, in async_reload_config
    await self._unsubscribe_topics()
TypeError: object NoneType can't be used in 'await' expression

Alarm get stuck in arming state. Investigating the log shows the following error:
2020-11-22 20:53:57 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/config/custom_components/alarmo/alarm_control_panel.py", line 459, in async_initialization_timer_finished
await self.async_arm(self.arm_mode)
File "/config/custom_components/alarmo/alarm_control_panel.py", line 408, in async_arm
res = self.sensors.validate_event(event=EVENT_ARM, bypass_open_sensors=bypass_open_sensors)
File "/config/custom_components/alarmo/sensors.py", line 128, in validate_event
open_sensors[entity] = state.state
AttributeError: 'NoneType' object has no attribute 'state'

Yesterday I localized et.json, submitted but no I can not find it anywhere- forgot to save/publish? :-(

Hi,
I have a feature request. I would like to have different events for pending to armed away and pending for armed night. Something like "pending_away" or "pending_night".
The reason is that I automate this changes with some different actions like tts.say, switch on different lights, that are not the same in both cases.
The same request for warning states make sense too, I think.

Beside armed away, night, etc. IMHO there should be a permanent armed state for all time alarm sensors like smoke, gas, water leak, etc that should trigger always, no matter if away, night, home, etc are armed or not.

Not sure if people do, but I use two categories for push messages. Both with Telegram groups. One "triggered alarm", very loud sound and another low sound notification to rest of notifications like armed, no armed, etc. Push messages "when something changes in the alarm" could be heart dangerous IMHO. I would like two targets for push messages at least and the possibility to choose among them. By now I have a workaround with automations.

hi could i suggest this card to set times https://github.com/htmltiger/numberbox-card

hello and great job

if you need, I can help if you start creating the language files in Italian.

Hi mate, I have tried all the install methods given but "AlarmO" does not show on the left panel once HA is restarted. I had a manual alarm setup in configuration.yaml which I commented prior to installing "AlarmO"

I am running the latest version of HA
Operating System
Ubuntu 20.04.1 LTS
Docker version
19.03.12

most likely I am doing something wrong, but any help will be great

Alarmo is working great here. I moved HA alarm related notifications to Alarmo notifications. I tried them and I think they're working nice. Armed, disarmed, leaving, opened sensor and so on. It seems there's only one kind of notifications I can´t get rid of: "Low battery sensor". I have fire sensors and door sensors that send a specific 433MHz code when low batt reached. I know I could assign them as "always" but they should trigger alarm as hard as it home were burning, which can be heart dangerous. I would suggest a feature request to another "always" sensor category to assign a low level notifications service as target . In my case it is a telegram group with only a bip sound.

I am trying to make an automation to disarm the alarm when a NFC tag is read.
In automations I have a call to this service:

  - service: alarm_control_panel.alarm_disarm
    data:
      entity_id: alarm_control_panel.alarmo

But the service is not executed.
Also, if I check with the service developer tools, no disarm is made.

May be I am doing something wrong?

Is ti possible to add soo you can go from Armed away to Armed home in one click?

Hey,

at first, thanks for this great integration.

I got an Alarm with Push Notifictions in which i use {{open_sensors}}.
But the variable {{open_sensors}} is always the first sensor that triggers the Alarm.

e.g.

• I open Window 1 and the Notification is correct. "Window 1 is on"
• I dissarm and arm again
• I open Window 2 and the Notification is wrong. "Window 1 is on"

-- Restarting Home Assistant --

• I open Window 2 and the Notification is correct. "Window 2 is on"
• I dissarm and arm again
• I open Window 1 and the Notification is wrong. "Window 2 is on"

Any ideas?

Thanks again!

Logger: homeassistant.components.websocket_api.http.connection.139909452651920
Source: custom_components/alarmo/alarm_control_panel.py:465
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 2:28:11 AM (2 occurrences)
Last logged: 2:28:17 AM

'leave'
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 135, in handle_call_service
await hass.services.async_call(
File "/usr/src/homeassistant/homeassistant/core.py", line 1448, in async_call
task.result()
File "/usr/src/homeassistant/homeassistant/core.py", line 1483, in _execute_service
await handler.job.target(service_call)
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 573, in handle_service
await service.entity_service_call(
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 482, in entity_service_call
future.result() # pop exception if have
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 664, in async_request_call
await coro
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 519, in _handle_entity_call
await result
File "/config/custom_components/alarmo/alarm_control_panel.py", line 465, in async_edit_config
self._config[ATTR_DELAYS][event][mode] = val
KeyError: 'leave'

I'm using the latest 1.1.2, just wondering if there was any change on notifications (on purpose or not) as I haven't been able to see the failed to arm notifications anymore, other notifications look ok ie: If I try to arm the alarm with a sensor open, it doesn't work and it also doesn't show me anything even though I have a notification set.