4a3a21bb8e
* Add RelayAddr/Chan to Alarmdecoder * Pulled zone 3 example out, corrected motion-based Zone 3 example not needed * Removed RFID double space * Removed double space on relayaddr line
3.9 KiB
layout, title, description, date, sidebar, comments, sharing, footer, logo, ha_category, ha_release, ha_iot_class
| layout | title | description | date | sidebar | comments | sharing | footer | logo | ha_category | ha_release | ha_iot_class |
|---|---|---|---|---|---|---|---|---|---|---|---|
| page | AlarmDecoder Alarm | Instructions on how to integrate a DSC/Honeywell alarm panel with Home Assistant using an AlarmDecoder device. | 2017-04-02 13:28 | true | false | true | true | alarmdecoder.png | Hub | 0.43 | Local Push |
The alarmdecoder component will allow Home Assistant users who own either a DSC or Honeywell alarm panel to leverage their alarm system and its sensors to provide Home Assistant with rich information about their homes. Connectivity between Home Assistant and the alarm panel is accomplished through a device produced by Nu Tech Software Solutions, known as the AlarmDecoder. The AlarmDecoder devices provide a serial, TCP/IP socket or USB interface to the alarm panel, where it emulates an alarm keypad.
Please visit the AlarmDecoder website for further information about the AlarmDecoder devices.
There is currently support for the following device types within Home Assistant:
- Binary Sensor: Reports on zone status
- Sensor: Emulates a keypad display
- Alarm Control Panel: Reports on alarm status, and can be used to arm/disarm the system
This is a fully event-based component. Any event sent by the AlarmDecoder device will be immediately reflected within Home Assistant.
An alarmdecoder section must be present in the configuration.yaml file and contain the following options as required:
# Example configuration.yaml entry
alarmdecoder:
device:
type: socket
host: 192.168.1.20
port: 10000
panel_display: On
zones:
01:
name: 'Smoke Detector'
type: 'smoke'
rfid: '0123456'
02:
name: 'Front Door'
type: 'opening'
Configuration variables:
- type (Required): The type of AlarmDecoder device: socket, serial or USB
- host (Optional): The IP address of the AlarmDecoder device on your home network, if using socket type. Default:
localhost - port (Optional): The port of the AlarmDecoder device on your home network, if using socket type. Default:
10000 - path (Optional): The path of the AlarmDecoder device, if using socket type. Default:
/dev/ttyUSB0 - baudrate (Optional): The baud rate of the AlarmDecoder device, if using serial type. Default:
115200 - panel_display (Optional): Create a sensor called sensor.alarm_display to match the Alarm Keypad display. Default:
off - zones (Optional): AlarmDecoder has no way to tell us which zones are actually in use, so each zone must be configured in Home Assistant. For each zone, at least a name must be given. For more information on the available zone types, take a look at the Binary Sensor docs. Note: If no zones are specified, Home Assistant will not load any binary_sensor components.
- rfid (Optional): The RF serial-number associated with RF zones. Providing this field allows Home Assistant to associate raw sensor data to a given zone, allowing direct monitoring of the state, battery, and supervision status.
- relayaddr (Optional): Address of the relay expander board to associate with the zone. (ex: 12, 13, 14, or 15). Typically used in cases where a panel will not send bypassed zones such as motion during an armed home state, the Vista 20P is an example of this. Alarmdecoder can emulate a zone expander board and the panel can be programmed to push zone events to this virtual expander. This allows the bypassed zone binary sensors to be utilized. One example is using bypassed motion sensors at night for motion-based automated lights while the system is armed with the motion sensor bypassed.
- relaychan (Optional): Channel of the relay expander board to associate with the zone. (ex: 1, 2, 3, or 4)