An open API service indexing awesome lists of open source software.

https://github.com/dadecoza/pidgin-meshtastic

a Meshtastic plugin for Pidgin
https://github.com/dadecoza/pidgin-meshtastic

meshtastic nanopb pidgin pidgin-plugin

Last synced: 10 months ago
JSON representation

a Meshtastic plugin for Pidgin

Awesome Lists containing this project

README

          

![Pidgin logo](https://raw.githubusercontent.com/dadecoza/pidgin-meshtastic/refs/heads/main/nsis/pidgin-meshtastic.ico)

# a Meshtastic plugin for Pidgin

Make sure you already have [Pidgin](https://pidgin.im/install/) installed.

The Windows installer for the plugin is available [here](https://github.com/dadecoza/pidgin-meshtastic/releases/latest/download/pidgin-meshtastic-setup.exe).

Precompiled libraries for Windows and Linux can be found under [releases](https://github.com/dadecoza/pidgin-meshtastic/releases).

## Installation

### Debian
```shell
sudo apt-get update
sudo apt-get install pidgin-dev git
git clone https://github.com/dadecoza/pidgin-meshtastic.git --recursive
cd pidgin-meshtastic
make
sudo make install
sudo adduser $USER dialout
```

### Arch
[AUR Package](https://aur.archlinux.org/packages/pidgin-meshtastic-git) (Thanks [timttmy](https://github.com/timttmy))

### Windows
[Windows Installer](https://github.com/dadecoza/pidgin-meshtastic/releases/latest/download/pidgin-meshtastic-setup.exe)

# Adding the account
![Account screenshot](https://dade.co.za/images/account.png)
* *Protocol*: Meshtastic
* *Username*: this can be anything, your radio will update the username once connected
* *COM port or IP address*: Typically "COMx" on Windows, or "/dev/ttyUSBx" on Linux. It can also be a valid IPv4 address for socket connections.
* *Local Alias*: Can be left empty, it will populate on first connect.

# Usage
![Menus screenshot](https://dade.co.za/images/menus.png)
* Right-click on a node and navigate to the "Meshtastic" menu item for Meshtastic-specific actions.
* These actions will be applied to your local node (indicated by the blue flag) or any remote node where you have admin access.
* A note on admin access: The legacy admin channel will take precedence over admin keys. This means that if you want to administer newer nodes with admin keys configured, you must ensure the admin channel is disabled or you will get the "no channel" error message.