# SOME DESCRIPTIVE TITLE. # Copyright (C) 2018-2026, Slavi Pantaleev, Aine Etke, MDAD community members # This file is distributed under the same license as the matrix-docker-ansible-deploy package. # FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: matrix-docker-ansible-deploy \n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2026-05-07 11:16+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #: ../../../docs/configuring-playbook-bridge-meshtastic-relay.md:8 msgid "Setting up a Matrix <-> Meshtastic bridge (optional)" msgstr "" #: ../../../docs/configuring-playbook-bridge-meshtastic-relay.md:10 msgid "The playbook can install and configure [meshtastic-matrix-relay](https://github.com/jeremiah-k/meshtastic-matrix-relay) (sometimes referred to as `mmrelay`) for you — a bridge between [Matrix](https://matrix.org/) and [Meshtastic](https://meshtastic.org/) mesh networks." msgstr "" #: ../../../docs/configuring-playbook-bridge-meshtastic-relay.md:12 msgid "See the [project's documentation](https://github.com/jeremiah-k/meshtastic-matrix-relay) to learn what it does and why it might be useful to you." msgstr "" #: ../../../docs/configuring-playbook-bridge-meshtastic-relay.md:14 msgid "Prerequisites" msgstr "" #: ../../../docs/configuring-playbook-bridge-meshtastic-relay.md:16 msgid "You need a Matrix account for the bot. You can either [register the bot account manually](registering-users.md) or let the playbook create it when running `ansible-playbook … --tags=ensure-matrix-users-created`. Either way, you'll need the account's **password** to configure the bridge — unlike most other bridges in this playbook, `mmrelay` authenticates with a password and creates its own session (optionally with End-to-End Encryption material)." msgstr "" #: ../../../docs/configuring-playbook-bridge-meshtastic-relay.md:18 msgid "You also need access to a Meshtastic device, connected to the server via one of:" msgstr "" #: ../../../docs/configuring-playbook-bridge-meshtastic-relay.md:20 msgid "**TCP**: the device is reachable on the network (e.g. a Meshtastic node running the TCP API)," msgstr "" #: ../../../docs/configuring-playbook-bridge-meshtastic-relay.md:21 msgid "**Serial**: the device is plugged in via USB and available on the host (e.g. `/dev/ttyUSB0`)," msgstr "" #: ../../../docs/configuring-playbook-bridge-meshtastic-relay.md:22 msgid "**BLE**: the device is reachable via Bluetooth Low Energy from the host." msgstr "" #: ../../../docs/configuring-playbook-bridge-meshtastic-relay.md:24 msgid "Adjusting the playbook configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-meshtastic-relay.md:26 msgid "To enable the bridge, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:" msgstr "" #: ../../../docs/configuring-playbook-bridge-meshtastic-relay.md:56 msgid "By default, the bot's Matrix ID is `@meshtasticbot:{{ matrix_domain }}`. To change it, adjust `matrix_meshtastic_relay_matrix_bot_user_id`." msgstr "" #: ../../../docs/configuring-playbook-bridge-meshtastic-relay.md:58 msgid "Bluetooth (BLE) connections" msgstr "" #: ../../../docs/configuring-playbook-bridge-meshtastic-relay.md:60 msgid "When `matrix_meshtastic_relay_connection_type` is `ble`, the container runs with `--network=host` and bind-mounts the host's DBus socket — both are required for Bluetooth pairing/communication. Only use this connection type if you trust the playbook-managed host and are comfortable with these privileges." msgstr "" #: ../../../docs/configuring-playbook-bridge-meshtastic-relay.md:62 msgid "Serial connections" msgstr "" #: ../../../docs/configuring-playbook-bridge-meshtastic-relay.md:64 msgid "When `matrix_meshtastic_relay_connection_type` is `serial`, the host device referenced by `matrix_meshtastic_relay_serial_port` is passed through to the container. Make sure that `matrix_user_uid` / `matrix_user_gid` have read/write access to that device (e.g. by adding the matrix user to the `dialout` group, or adjusting udev rules)." msgstr "" #: ../../../docs/configuring-playbook-bridge-meshtastic-relay.md:66 msgid "Extending the configuration" msgstr "" #: ../../../docs/configuring-playbook-bridge-meshtastic-relay.md:68 msgid "There are some additional things you may wish to configure about the bridge." msgstr "" #: ../../../docs/configuring-playbook-bridge-meshtastic-relay.md:70 msgid "Take a look at:" msgstr "" #: ../../../docs/configuring-playbook-bridge-meshtastic-relay.md:72 msgid "`roles/custom/matrix-bridge-meshtastic-relay/defaults/main.yml` for some variables that you can customize via your `vars.yml` file. You can override individual `matrix_meshtastic_relay_*` variables, or make finer-grained adjustments via `matrix_meshtastic_relay_configuration_extension_yaml`." msgstr "" #: ../../../docs/configuring-playbook-bridge-meshtastic-relay.md:74 msgid "Installing" msgstr "" #: ../../../docs/configuring-playbook-bridge-meshtastic-relay.md:76 msgid "After configuring the playbook, run the playbook with [playbook tags](playbook-tags.md) as below:" msgstr "" #: ../../../docs/configuring-playbook-bridge-meshtastic-relay.md:83 msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`." msgstr "" #: ../../../docs/configuring-playbook-bridge-meshtastic-relay.md:85 msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too." msgstr "" #: ../../../docs/configuring-playbook-bridge-meshtastic-relay.md:87 msgid "Usage" msgstr "" #: ../../../docs/configuring-playbook-bridge-meshtastic-relay.md:89 msgid "Invite the bot to the Matrix rooms listed in `matrix_meshtastic_relay_matrix_rooms_list` and it will relay between Matrix and the corresponding Meshtastic channel. Messages sent on Meshtastic will appear in Matrix and vice versa." msgstr "" #: ../../../docs/configuring-playbook-bridge-meshtastic-relay.md:91 msgid "See the [project's wiki](https://github.com/jeremiah-k/meshtastic-matrix-relay/wiki) for details about commands, plugins and advanced usage." msgstr "" #: ../../../docs/configuring-playbook-bridge-meshtastic-relay.md:93 msgid "Troubleshooting" msgstr "" #: ../../../docs/configuring-playbook-bridge-meshtastic-relay.md:95 msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-meshtastic-relay`." msgstr ""