I wrote a step-by-step tutorial on how to bring up a Home Assistant alarm panel

Inspired by recurring questions from reddit, I wrote a step-by-step tutorial on how to set up an alarm panel in Home Assistant based on Konnected.io boards. You find here:   


In the tutorial, I cover the steps necessary to bring up a full-featured system that group sensors by type, distinguished between "armed away" and "armed home", arms and disarms with grace periods and audible feedback, and even auto-arms and auto-disarms depending on presence.

All feedback is welcome! (But I can only promise corrections and additions work load and family permitting.)

(441 KB)
  • So where do I go from here ?  I've got all of the automations setup, when I did my walkthrough I was able to see the interactions of doors or window groups actually working.


    1.  I cannot ARM/DIARM the system from the alarm panel.

    2.  I only get a message that I've disarmed the system - none of the other notifications work

    3.  Even though I'm getting a notification, the alarm system in the home is not being armed

    Found a document that outlines programmable outputs for Ademco/Vista panels - Is this the NEXT required step in the process ?

  • I'm following a thread that focus on setting up the switch OUT to Zone 1 on the Vista board. I have the following configuration:

    VISTA 15P Konnected Interface Board Next Step

    PIN 1 Zone 1 Configure new zone in H.A. Integration for Konnected as Switchable

    PIN 5 Zone 6 Configure new zone in H.A. Integration for Konnected as Switchable

    After creating the switches for the zones in Konnected integration do I need to created a Konnected.YAML file that represents the same switch configuration with the OUT Relays identified ?

    If anyone has an example please share.  I've added screen shots to demonstrate what I'm thinking my next step is.

  • Hi Archie, it looks like you are configuring the interface kit to arm/disarm the legacy system.

    I haven't bought the interface kit so I'm not a direct expert on creating tutorials that encompass that part.

    To answer your question, the yaml configuration is optional, and it's only imported the first time you run the UI configuration. If you add it after going through the configuration UI, it's ignored. At this point, use only the UI.

    The screenshots you posted seem accurate in their config for pin 1 and 5. 

    I recommend you create a HA entity card with a button to toggle them and you test that they work interactively with a multimeter.

    At that point you can add the automations necessary to do legacy arm/disarm.

  • When you say UI configuration, you are speaking of the Konnected integration config ?

  • Yes, definitely, that's what I mean, the multi-page setup in the integrations.

  • Daniele - you know sometimes this stuff can make you feel so stupid and dumb.  I mean, I've read over the konnected H.A. instructions probably 10 times and none of these things even caused a flutter in my brain.  Arrrgggh!!!

    Also, you said something and now I've read the same thing in the konnected H.A. instructions as follows:  

    If you prefer you can utilize a konnected section in the configuration.yaml file that specifies the Konnected devices on the network and the sensors or actuators attached to them.

    Is this saying I don't need the file as the UI configuration is all that is required ?

  • I'm happy to help you.

    Yes, the excerpt that you quote is precisely the one that I was referring to. Later in the same text, it also says: "Once the import creates a Configured integration the Konnected section of the configuration.yaml is no longer used - it is recommended to remove the konnected section of configuration.yaml and after the import occurs."

    Short story, writing a konnected section in your yaml is only a shortcut to pre-populate the UI, and once you are done, you should go back and delete it. If you don't think it saves you time or if you find it confusion, totally avoid it, and only use the UI without touching the YAML at all.

    I hope this helps. Good luck!

  • I tell you, that's "pure plain english" for a rock for a brain like me.  this is why I probably continue to get errors when I restart Hass.io

    Again, thank you!

  •  Thanks for your tutorial, it's been very helpful. I have a few questions though. I got as far as section 7 before I ran into trouble. I don't understand where alarm_control_panel.home_alarm comes from. If I look in the Developer Tools, I see an alarm_control_panel.intrusion_alarm, and it's state responds to the actions on the card, but I do not see a .home_alarm or it's defined states. I'd be happy to contribute to the tutorial after I figure this out. 

  •  I don't understand where alarm_control_panel.home_alarm comes from. If I look in the Developer Tools, I see an alarm_control_panel.intrusion_alarm, and it's state responds to the actions on the card, but I do not see a .home_alarm or it's defined states. 
    I have the same stumbling block..

    Konnected integration created a switch entity that arms and disarms my alarm, but how does this tie to the alarm_control_panel ?  The HA Alarm card certainly behaves as defined by the timers etc, but it doesn’t trigger the switch to actually arm / disarm the actual alarm system.

  • @ Groutley,

    It's in Step 3 of my tutorial https://github.com/scarpazza/home-assistant-konnected-tutorial, and it requires you to manually edit configuration.yaml.

    It won't appear in the developer tools till you change the configuration file and reload the configuration.

    Good luck and let me know. 

  • @Daniel,  I have followed your tutorial including step 3, which creates the alarm control panel,

    Perhaps you are referring to the bit that states “you’ll need to write those yourself”?

    I have followed step by step, I have modified my configuration.yaml with the code that creates the alarm_control_panel. I have that control panel card added to my Dashboard, I even played with adding a code, and removed it.  It works great, I can tell the card to arm_away or arm_home or disarm,  that card on my dashboard behaves as I would hope according to your tutorial step 3.

    But, to actually arm or disarm my konnected panel, the ‘ switch.alarm_arm’ must toggle. 

    I added a switch card to my dashboard and it arm/ disarms my konnected and interfaced dsc panel.

    But how do I get the ‘alarm_contral_panel’ arm_away selection to operate my ‘switch.alarm_arm’ ?

    There is no example that I can see on how to do this, maybe it is obvious, but not to me I am afraid,  sorry if this is a stupid question, but I need just a little bit more guidance on how the created dashboard panel actually controls the konnected ‘switch’.

    Appreciate your guidance.

  • @Groutley

    Did you have any joy with this, I too am struggling with the same issue as you.

    I too have successfully added the sensors etc, and the output arms/disarms the panel, I do not have the output from the alarm working as yet, to state armed, but I am getting there.

    But it seems to me that the Alarm control panel is a finite state machine, so is it that we have to write the code that needs to occur during the transitions, ie, the conditions required to be met for the transition and also the actions to be performed on a transistion?

Login or Signup to post a comment