Home ▸ Integrations ▸

Matrix

This integrationIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] 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.

There is currently support for the following device types within Home Assistant:

Notifications

Configuration

To enable the Matrix integrationIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more], add it to your configuration.yamlThe configuration.yaml file is the main configuration file for Home Assistant. It lists the integrations to be loaded and their specific configurations. In some cases, the configuration needs to be edited manually directly in the configuration.yaml file. Most integrations can be configured in the UI. [Learn more] file. After changing the configuration.yamlThe configuration.yaml file is the main configuration file for Home Assistant. It lists the integrations to be loaded and their specific configurations. In some cases, the configuration needs to be edited manually directly in the configuration.yaml file. Most integrations can be configured in the UI. [Learn more] file, restart Home Assistant to apply the changes. The integration is now shown on the integrations page under Settings > Devices & services. Its entities are listed on the integration card itself and on the Entities tab.

# 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 Variables

Looking for your configuration file?

username string Required

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.

password string Required

The password for your Matrix account.

homeserver string Required

The full URL for your homeserver. If you use the default matrix.org homeserver, this is ‘https://matrix.org’.

verify_ssl string (Optional, default: true)

Verify the homeservers certificate.

rooms string (Optional, default: empty)

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’).

commands map (Optional, default: empty)

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:

word string (Optional)

Specifies a word that the bot should listen for. If you specify ‘my_command’ here, the bot will handle any message starting with ‘!my_command’.

expression string (Optional)

Specifies a regular expression (in Python regexp syntax) that the bot should listen to. The bot will handle any message that matches the regular expression.

reaction string (Optional)

Specifies an emoji reaction that the bot should listen to. The bot will handle any message that is reacted to with this emoji.

name string Required

The name of the command. This will be an attribute of the event that is fired when this command triggers.

rooms string (Optional, default: empty)

A list of rooms that the bot should listen for this command in. If this is not given, the rooms list from the main configuration is used. Please note that every room in this list must also be in the main room configuration.

Warning

In order to prevent infinite loops when reacting to commands, you have to use a separate account for the Matrix integration.

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.

Comprehensive Configuration Example

This example also uses the matrix notify platform.

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

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

automation:
  - alias: "Respond to !testword"
    triggers:
      - trigger: event
        event_type: matrix_command
        event_data:
          command: testword
    actions:
      - action: notify.matrix_notify
        data:
          message: "It looks like you wrote !testword"

  - alias: "Respond to an introduction"
    triggers:
      - trigger: event
        event_type: matrix_command
        event_data:
          command: introduction
    actions:
      - action: notify.matrix_notify
        data:
          message: "Hello {{trigger.event.data.args['name']}}"

  - alias: "Respond to a reaction in a thread"
    triggers:
      - trigger: event
        event_type: matrix_command
        event_data:
          command: thumbsup
    actions:
      - action: notify.matrix_notify
        data:
          message: "I saw that {{trigger.event.data.args['reaction']}} -- glad you appreciated this!"
          data:
            thread_id: "{{trigger.event.data.thread_parent}}"

  - alias: "React to a command"
    triggers:
      - trigger: event
        event_type: matrix_command
        event_data:
          command: testword
    actions:
      - action: matrix.react
        data:
          reaction: "✅"
          room: "{{trigger.event.data.room}}"
          message_id: "{{trigger.event.data.event_id}}"

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 and also place a ✅ reaction on the original message.
Listen in both rooms for any message matching “My name is ” and answer with “Hello ” into “#hasstest:matrix.org”.
Listen in both rooms for messages reacted to with 👍 and answer in a thread with “I saw that 👍 – glad you appreciated this!”

Notifications

The matrix platform allows you to deliver notifications from Home Assistant to a Matrix room. Rooms can be both direct as well as group chats.

To enable Matrix notifications in your installation, you first need to configure the Matrix integration. Then, add the following to your configuration.yamlThe configuration.yaml file is the main configuration file for Home Assistant. It lists the integrations to be loaded and their specific configurations. In some cases, the configuration needs to be edited manually directly in the configuration.yaml file. Most integrations can be configured in the UI. [Learn more] file:

# Example configuration.yaml entry
notify:
  - name: NOTIFIER_NAME
    platform: matrix
    default_room: ROOM_ID_OR_ALIAS

Configuration Variables

Looking for your configuration file?

name string (Optional, default: notify)

Setting the optional parameter name allows multiple notifiers to be created. The notifier will bind to the notify.NOTIFIER_NAME action.

default_room string Required

The room all messages will be sent to, when no other target is given.

The target room has to be precreated, the room id can be obtained from the rooms settings dialog. Rooms by default have a canonical id of the form "!<randomid>:homeserver.tld", but can also be allocated aliases like "#roomname:homeserver.tld". Make sure to use quotes around the room id or alias to escape special characters (!, and #) in YAML. The notifying account may need to be invited to the room, depending on the individual rooms policies.

To use notifications, please see the getting started with automation page.

Message formats

Matrix supports sending messages using a limited HTML subset. To specify the message format, add it in the notification data.

Supported formats are: text (default), and html.

# Example of notification as HTML
actions:
  - action: notify.matrix_notify
    data:
      message: >-
        <h1>Hello, world!</h1>
      data:
        format: "html"

Images in notification

It is possible to send images with notifications. To do so, add a list of paths in the notification data.

# Example of notification with images
actions:
  - action: notify.matrix_notify
    data:
      message: "Test with images"
      data:
        images:
          - /path/to/picture.jpg

Important

If you need to include a file from an external folder in your notifications, you will have to list the source folder as allowed.

configuration.yaml
...
homeassistant:
  allowlist_external_dirs:
    - /tmp

Replying in threads

The matrix_command event will contain an event_id field that represents the message identifier for the received message. It will also contain a thread_parent field that contains the message identifier for the parent message of the thread. If the message was inside of a thread, thread_parent will be the identifier of the root message of the thread. If it is not inside of a thread, thread_parent will be the same as event_id.

To reply inside of a thread, pass the correct message identifier of the root message into data.thread_id when sending a reply message. For example:

action: notify.matrix_notify
data:
  message: "Reply message goes here"
  data:
    thread_id: "{{ trigger.event.data.thread_parent }}"

Actions

The integration also provides the following actions:

Sending a message

As an alternative to using the notify integration as described above, you may use matrix.send_message to send a message to a Matrix room.

action: matrix.send_message
data:
  message: "My cool message"
  target: "#hasstest:matrix.org"
  data:
    images:
      - /path/to/picture.jpg
    format: html
    thread_id: "$-abcdeghij_klmnopqrstuvwxyz123"

Data attribute: message
- Description: The message body to send
- Optional: No
- Type: String
Data attribute: target
- Description: The room to send the message to
- Optional: No
- Type: String
Data attribute: data
- Description: Additional options
- Optional: Yes
- Type: Map
- Sub-attributes:
  - Data attribute: images
    - Description: One or more image paths to attach to the message
    - Optional: Yes
    - Type: List of strings
  - Data attribute: format
    - Description: The format of the message. Must be either text or html
    - Optional: Yes
    - Default: text
    - Type: String
  - Data attribute: thread_id
    - Description: The ID of the parent message to thread this reply under
    - Optional: Yes
    - Type: String

Reacting to messages

To react to a message with an emoji reaction, use the matrix.react action:

action: matrix.react
data:
  reaction: "✅"
  room: "{{ trigger.event.data.room }}"
  message_id: "{{ trigger.event.data.event_id }}"

Tip

Reactions do not have to be an emoji. They can be any valid string. However, emoji are the typical/traditional use case.

Data attribute: reaction
- Description: The reaction to send
- Optional: No
- Type: String
Data attribute: room
- Description: The room to send the reaction in
- Optional: No
- Type: String
Data attribute: message_id
- Description: The ID of the message to apply the reaction to
- Optional: No
- Type: String

Help us improve our documentation

Suggest an edit to this page, or provide/view feedback for this page.

Configuration

Configuration Variables

Event data

Comprehensive Configuration Example

Notifications

Configuration Variables

Message formats

Images in notification

Replying in threads

Actions

Sending a message

Reacting to messages

Related topics

Help us improve our documentation