home-assistant.io/source/_components/matrix.markdown

layout	title	description	date	sidebar	comments	sharing	footer	logo	ha_category	ha_release
page	Matrix	Matrix chatbot support	2018-03-25 18:50	true	false	true	true	matrix.png	Hub	0.69

This component allows you to send messages to matrix rooms, as well as to react to messages in matrix rooms. Reacting to commands is accomplished by firing an event when one of the configured commands is triggered.

# Example configuration.yaml entry
matrix:
  homeserver: https://matrix.org
  username: "@my_matrix_user:matrix.org"
  password: supersecurepassword
  rooms:
    - "#hasstest:matrix.org"
  commands:
    - word: my_command
      name: my_command

{% configuration %} username: description: "The matrix username that Home Assistant should use to log in. Note: You must specify a full matrix ID here, including the homeserver domain, e.g., '@my_matrix_bot:matrix.org'. Please note also that the '@' character has a special meaning in YAML, so this must always be given in quotes." required: true type: string password: description: The password for your Matrix account. required: true type: string homeserver: description: "The full URL for your homeserver. If you use the default matrix.org homeserver, this is 'https://matrix.org'." required: true type: string verify_ssl: description: Verify the homeservers certificate. required: false type: string default: true rooms: description: "The list of rooms that the bot should join and listen for commands (see below) in. While you can limit the list of rooms that a certain command applies to on a per-command basis (see below), you must still list all rooms here that commands should be received in. Rooms can be given either by their internal ID (e.g., '!cURbafjkfsMDVwdRDQ:matrix.org') or any of their aliases (e.g., '#matrix:matrix.org')." required: false type: [string] default: empty commands: description: "A list of commands that the bot should listen for. If a command is triggered (via its word or expression, see below), an event is fired that you can handle using automations. Every command consists of these possible configuration options:" required: false type: map default: empty keys: word: description: "Specifies a word that the bot should listen for. If you specify 'my_command' here, the bot will react to any message starting with '!my_command'." required: false type: string expression: description: "Specifies a regular expression (in python regexp syntax) that the bot should listen to. The bot will react to any message that matches the regular expression." required: false type: string name: description: "The name of the command. This will be an attribute of the event that is fired when this command triggers." required: true type: string rooms: description: "A list of rooms that the bot should listen for this command in. If this is not given, the rooms list from the main config is used. Please note that every room in this list must also be in the main room config." required: false type: [string] default: empty {% endconfiguration %}

{% linkable_title Event Data %}

If a command is triggered, a matrix_command event is fired. The event contains the name of the command in the name field.

If the command is a word command, the data field contains a list of the command's arguments, i.e., everything that stood behind the word, split at spaces. If the command is an expression command, the data field contains the group dictionary of the regular expression that matched the message.

{% linkable_title Comprehensive Configuration Example %}

This example also uses the matrix notify platform.

# The Matrix component
matrix:
  homeserver: https://matrix.org
  username: "@my_matrix_user:matrix.org"
  password: supersecurepassword
  rooms:
    - "#hasstest:matrix.org"
    - "#someothertest:matrix.org"
  commands:
    - word: testword
      rooms:
        - "#someothertest:matrix.org"
    - expression: "My name is (?P<name>.*)"
      name: introduction

notify:
  - name: matrix_notify
    platform: matrix
    default_room: "#hasstest:matrix.org"

automation:
  - alias: 'React to !testword'
    trigger:
      platform: event
      event_type: matrix_command
      event_data:
        command: testword
    action:
      service: notify.matrix_notify
      data:
        message: 'It looks like you wrote !testword'
  - alias: 'React to an introduction'
    trigger:
      platform: event
      event_type: matrix_command
      event_data:
        command: introduction
    action:
      service: notify.matrix_notify
      data_template:
        message: "Hello {{trigger.event.data.name}}"

This configuration will:

• Listen for "!testword" in the room "#someothertest:matrix.org" (and only) there. If such a message is encountered, it will answer with "It looks like you wrote !testword" into the "#hasstest:matrix.org" channel.
• Listen in both rooms for any message matching "My name is " and answer with "Hello " into "#hasstest:matrix.org".