YET another take on an alarm system

[Dawi.Es (Dani)]

@argykaraz i have the same problem

YET another take on an alarm system

hello, because of the restart problem I leave you some details. As you will see in the images there are two, one before the restart and another after restarting the raspberry. the sensors go from active to inactive. provisionally we have been able to fix that with an automation for each mode. type like this: alias: reinicio ha modo AWAY trigger: event: start platform: homeassistant condition: condition: state entity_id: alarm_control_panel.house state: ‘armed_away’ action: service: al…

[stefve (Stef)]

Hi! Do you have any info about the update?

Thank you!

[gazoscalvertos]

Is anyone else experiencing this?

I’ll give it a test on my live rig tomorrow but the test rig with the new code doesn’t appear to have this issue however I have changed a lot of the backend code.

[gazoscalvertos]

I’ve uploaded a test branch to github however there are still bugs to correct before its stable to use in a real environment so do not use in your real environment! but for those who want to test fly feel free.

Once I’ve ironed out these little niggles it should be good to go.

Current issues off the top of my head:
IOS colour selector issue
General mobile alignment/resizing
User specific code editing
Check of all settings
Default to HA colours
A full end to end test!

[gazoscalvertos]

Can confirm this appears to be fixed in the test branch.

I’ll try and get it out as soon as possible

[Dawi.Es (Dani)]

Ok thanks!!!

[Anders_Karlstrom (Anders Liljekvist)]

Don’t mind this, another restart solved the problem…

Hi, I’m trying to run your dev branch but I got stuck immediately.

You are using “ruamel” as a requirement. But I’m guessing it needs to be in the HA requirements file to be downloaded automatically by HA, because it is missing for me when I’m trying your component. Any suggestion on how to fix this?
Since I’m not using your component for real yet (I’ve only installed it) I think I would be a good test candidate for this. I’m running HA in a docker environment and I don’t really want to modify the requirements file

2018-07-07 12:22:28 ERROR (MainThread) [homeassistant.components.alarm_control_panel] Error while setting up platform bwalarm
Traceback (most recent call last):
File “/usr/src/app/homeassistant/helpers/entity_platform.py”, line 129, in _async_setup_platform
SLOW_SETUP_MAX_WAIT, loop=hass.loop)
File “/usr/local/lib/python3.6/asyncio/tasks.py”, line 358, in wait_for
return fut.result()
File “/usr/local/lib/python3.6/asyncio/coroutines.py”, line 212, in coro
res = func(*args, **kw)
File “/config/custom_components/alarm_control_panel/bwalarm.py”, line 359, in async_setup_platform
alarm = BWAlarm(hass, config, mqtt)
File “/config/custom_components/alarm_control_panel/bwalarm.py”, line 379, in init
self.init_variables()
File “/config/custom_components/alarm_control_panel/bwalarm.py”, line 528, in init_variables
self._yaml_content = self.yaml_load()
File “/config/custom_components/alarm_control_panel/bwalarm.py”, line 607, in yaml_load
from ruamel.yaml import YAML
ModuleNotFoundError: No module named ‘ruamel’

[gazoscalvertos]

Restart ha. The component installs ruamel when you first start it but it doesn’t pick it up first time. I’m also in a docker env.

You should see ruamel get installed to your deps/lib folder

[gazoscalvertos]

Let me know how you get on. Like I say it’s not in any fit state for proper use yet but after sorting minor issues it should be.

[Anders_Karlstrom (Anders Liljekvist)]

I’ll add some feedback here. I haven’t found anything severe yet though

• If default value is true the toggle should indicate that
  
• In the sensor view, it would be great if the id of the sensor could be shown when hovering the name (title attribute)
  
• the weather icon is black, it should be white I think?
  
• I would love to be able to turn of the mirroring effect, I’m not really fond of it
  
• I don’t know if it is possible, but it would be great if you could save the passcodes and the admin password with the “!secret” configuration. This will be a problem for those who backup to github…
• make the transitions between screens a tad quicker, I think it’s a bit to slow right now

But really awesome work, it looks great. I will try it out some more now, I have just touched the admin gui so far. Let me know if you want som help or just someone to discuss ideas with. I am a professional developer (but sadly not in python) so I would be able to give you more constructive feedback or help if needed.

Thanks so much for this!

[stefve (Stef)]

Hi!

Thanks for the update, and the great alarm system)!
I will install it now and help you testing it!

[gazoscalvertos]

Thanks for the feedback!

I’ll take all the points into account.

I’m not a professional dev to be honest, I’m a bit of a Jack of all trades IT wise, any feedback is most helpful. Ill float a few ideas your way via pm once I’ve sorted the bulk of issues.

[riteshp83 (Ritesh)]

Hey guys, really hoping for some assistance as I just got this implemented this evening. When testing I can trigger the alarm just fine and turn on the siren, however upon disarming the siren stays on. Please see below at my code:

• id: alarm_disarmed
  alias: ‘[Alarm] Disarmed’
  trigger:
  • platform: state
    entity_id: alarm_control_panel.house
    to: ‘disarmed’
    action:
  • service: switch.turn_off
    entity_id: switch.Siren
  • service: notify.ios_tayshs_iphone_x
    data:
    message: ‘Alarm Disarmed’

Also, I am using HomeKit and can arm the system just fine, but it doesn’t want to disarm. Any suggestions on how to make this work? I was thinking of removing code to arm but it states that its required.

[Sunonline (Sun K)]

check the name entity_id: switch.Siren / might be switch.siren (not capital letter S)
the deactivate the alarm (disarmed) this need the passcode. Have to put in somewhere in your script to deactivate the alarm.

[tremebundo (Juan Manuel)]

@gazoscalvertos
Hi,
I am a happy user of this custom alarm and I am thinking about testing and switching to your new UI.
But I have read that HA is going to switch to the new Lovelace UI from the release 0.73.1 and I guess that change will likely break many things and I do not want to fight twice with configuration issues.
Have you tested your new Ui with Lovelace?

Thanks a lot for your work.

[sparkydave (🇦🇺 Dave)]

I upgraded to 0.73.1 this morning and this alarm is still working. I do however have a fairly old version of the alarm I think. I do however get errors in the log when I navigate to the alarm screen. Waiting on the next version before I upgrade it all

[tbrausch]

Having problems getting the new UI Alarm System to work. Not quite sure what is going on. I copied all of the appropriate files to my directory, including the base alarm.yaml file which only includes the two lines:

platform: bwalarm
name: House

I restarted the first time and got the expected errors. After the 2nd restart, i got the error:

2018-07-11 17:14:42 ERROR (MainThread) [frontend.js.latest.201806080b0] https://xxxxxxxxxx.duckdns.org:8123/api/panel_custom/alarm:377:72 Uncaught TypeError: Cannot read property ‘disarmed’ of undefined

When I go to the Alarm panel, it looks like the old user interface (of course with no sensors). Not sure where I should be seeing the Settings button to get things setup.

[Dawi.Es (Dani)]

Hello! do you use homebridge?

[gazoscalvertos]

Lovelace should work fine with new alarm

[gazoscalvertos]

If you’re seeing the old alarm interface then your browser is either caching the old html file or the alarm.html file hasn’t been updated.

Try clearing your browser cache