Yes, you should be able to do it like this:
action:
- service: alarm_control_panel.alarm_arm_away
data:
entity_id: alarm_control_panel.alarm_panel
code: !secret alarm_pin
Thanks to @MartyTremblay for the original post:
Did you have any luck figuring this out? I just got my AD2USB in today and Iām having the same problem.
@PhracturedBlue, been 8 months since any posting. Either it has matured and just works or abandon.
How are things going?
The reason for the update, is I should be ready to buy mine in the coming month.
There hasnāt been a lot of development since this was incorporated into HomeAssistant, but to be honest, it doesnāt need much, as it seems to ājust workā. I will caveat that I have seen Home assistant lose connection to alarm decoder (or maybe alarm decoder loses connection with the panel, Iām not sure) on a very rare occasion. By rare I mean Iāve seen it happen 2 or 3 times in the past 8 months, and not at all in the past 2 months. I have a warning setup to email me if a signal is not received in reasonable time from HomeAssistant just in case. My point being (as I think I said above), I would not personally replace a monitored system with relying entirely on HomeAsisstant/AlarmDecoder, but as far as the system goes (and the increased fexibility of being able to drive automation and alerts via HomeAssistant) I would say reliability has been very good.
That is what I was expecting. Home assistant is not replacing monitoring, I just want access to sensor more than anything. I have a detached shop, and there are some things I would like to automate.
Any new words of wisdom on which AlarmDecoder to use. When I look at this before you sugested AD2USB and ser2socket as the interface, anything changed there?
Also, just thought to ask, I am using hass.io, any issues since it is hard to get down to the OS?
I have been using AD2PI for a year or so (since it was introduced in HASS) and so far so good, I have seen the disconnections mentioned in the other post, but the system has been reliably for me (I do not have a monitored system). In the Alarmedecoder implementation you have the option to alert on the zones being triggered and I am using that one too (as a backup measure). My Home Assistant installation is Hassbian based.
I spent the extra money and got the AD2PI Network Appliance. It has been rock solid and I am happy I did. I picked it so I didnāt have to worry about usb drivers/configuration, setup of ser2socket, etc. Just connect to the alarm, plugin it into the network, plug it into power and done.
It is nice having access to all the door sensors and alarm state changes for automations.
Iāve not used the ad2pi (my rpi already has connections that would prevent the use of the hat, and would mean I needed a different pi just for this purpose. I prefer to have a single system running all my peripherals)
I still use the ad2usb + ser2socket plugged directly into my rpi.
I donāt use hass.io so I donāt know the effort of using it that way
I posted a Feature Request for this a while back but maybe in the wrong place where you couldnāt see it. Would it be possible to add in the relay messages that come across the port 10000 stream? They are close to the RFX wireless messages and just be mapped as additional zones/binary sensors.
Docker running on a Synology box.
My concern was what configuration would be needed outside of HASS. HASS.io creates a docker environment and without hoops, you can not get to the OS shell. But in hindsight, if you use a device (ie: AD2USB or AD2PI) outside of the pi that is running HASS, then all the configurations should be in the HASS yaml files. There is not anything at the OS level to configure ser2sockets is there?
Should the docker running HASS.io be same as @hawk259? Maybe a different way to ask ā¦ @hawk259 did you have to do anything outside of the docker box running HASS?
Right, if you use a usb or serial device, you will need to import the device into the docker container. I have to do this for my usb z-wave stick. With AD2PI running on a separate device it is all in the configuration settings.
@penright
check out
So Iām going to be that guy that responds to his own post. First of all, Iām no Python coder by any means but I have various coding backgrounds I can usually dig in, take things apart and see how things are done and modify some work. So thatās what I did with this component. I was able to add the relay monitoring feature I wanted for the most part. I got the proof of concept down and monitor a relay I wanted.
Now, Iām streamlining things and making the configuration easier and straightforward but then I ran into an issue. I canāt seem to get the schema down on just listing various entities without numbering them like the zone numbering is done. Before I go into a whole code snippet dump with various errors, is this the right spot/thread to inquire about that? Would some of the HA gurus on the coding side be able to help?
Itās been a fun challenge and I canāt wait to get it all finished! Take all the knowledge learned and will learn to contribute to the HomeAssistant projectā¦exciting stuff.
Question for the gurus here, only been messing with Python off and on for a month or two along with HA. Iām hooked and all in, Smartthings is back in the box as of this week! Iām trying to update the alarmdecoder component to allow the triggering of the virtual relay messages (answer my own feature request). This feature is required for my alarm panel to send out the motion triggers while armed which is my big usage for lights of course.
I have it working for the most part after a good bit of trial and error but it works, Iād like to clean it up and do a proper config on it though as I mocked up each relay based on the examples of the zones. Is there a way to change my relays to not require a number like the zones are listed? I tried looking at several different components as examples but was unable to get my code to work. Basically looking to have a ārelay:ā section then list the name, address and channel of each relay in 3 variables. A system can have up to 4 relay boards with 4 or so relays per board, hence the address and channel. Any insight would be much appreciated. Thanks
Two components I updated:
https://github.com/digiblur/home-assistant/blob/dev/homeassistant/components/alarmdecoder.py https://github.com/digiblur/home-ssistant/blob/dev/homeassistant/components/binary_sensor/alarmdecoder.py
indent preformatted text by 4 spaces
Current config style is:
relays:
01:
relayname: āLRoomRelayā
relayid: ā12,01ā
Would like to change it to something like:
ā¦and so forth
Any examples of how to get this working in the config schema?
Can I suggest that you donāt need to call everything ārelayXā? Itās already under the relays tag. ānameā, āaddrā, āchannelā should be good enough then. I usually start with a basic yaml file and use a simple script that calls yaml.load() directly until you get it to work and see what the structure looks like. Then you can translate that into a schema. If you look at the existing zones schema, it should be pretty similar.
relays:
- name: "Relay 1"
address: 12
channel : 1
- name: "Relay 2"
address: 12
channel: 2
Ahhā¦ Nice idea. I think I tried name but it threw an error so I changed it back to relay name. Will start simple first like you said and build from there.
Any of the Alarmdecoder folks with Vista/Honeywell panels using the virtual relay on their panel? Or wish they could see the bypassed zone triggers? I have a pull request in the queue with the changes to add the relays (reworked from the last time I got advice on the design). I had one user chime in that they tested and have no issues. Itās been working great here for a few months as well.