My Meshtastic Nodes

• Waveshare: https://www.waveshare.com/sx1262-868m-lora-hat.htm?sku=16807
• Amazon, $35, Nov 2025: https://www.amazon.com/dp/B07VS1S2P7?ref=ppx_yo2ov_dt_b_fed_asin_title
• CONCERN: Google AI advises: "Confirm your Waveshare board uses the SX1262 radio with an SPI connection, not UART, for Meshtastic compatibility on Linux devices like Raspberry Pi."
  • At this time I don't know how to do that. ...
    I posted a question to the amazon product page: "does it have spi". Reply somewhat nebulous:
    "Yes, the Waveshare SX1262/SX1268 LoRa HAT connects through the standard Raspberry Pi 40-pin GPIO header, which includes SPI pins.
    The HAT uses UART interface for communication with the LoRa chip, but as a standard Raspberry Pi HAT, it connects via the GPIO header that provides access to SPI, I2C, UART, and other interfaces."
  • The amazon product listing says: "Compatible with Raspberry Pi 5/4B/3B/Zero/Zero W/Zero 2W/Pico/Pico W/Pico WH, UART Interface,"
    So yes, it says it's compatible with rPi's, but it also says "UART", and it does NOT say "SPI" ...
    OTOH, Google AI continues with configuration instructions, saying: "ensure SPI is enabled on your Pi.",
    so perhaps all is well...
  • The MeshTastic hardware page (https://meshtastic.org/docs/hardware/devices/linux-native-hardware/) does not explicitly exclude the SX1262 LoRa hat, though does say that the SX1262 LoRaWAN version has problems that may require using CLIENT_MUTE to disable rebroadcast...

----------------------

• https://www.youtube.com/watch?v=vLGoEPNT0Mk
  uses rPi 3B+ and WaveShare hat: SX1262XXXMLorWan GNSS
  find/get/install meshTastic software:
  go to: https://github.com/meshtastic/firmware/releases
  find the debian package under assets...
  confused here, not sure which to use... Did not find a .deb package...

  copy the url, use $ wget to install...

• alt source procedure from meshtastic.org:
  from: https://meshtastic.org/docs/hardware/devices/linux-native-hardware/
  There are two alternative procedures listed, one for 32-bit Raspian OS, the other for 64-bit Debian implementations
  Still a little confused since both Debian 12 bookworm and Debian 13 trixie seem to be supported ...
• alt procedure: https://www.youtube.com/watch?v=_NQHlI-al2w
  Heavy on the show-and-tell, light on the actual instructions/steps needed to get it running.
  Uses the LoRaWAN version (SKU: 24654)
  He states, without explaining, that it uses the SPI...
• ... another video ...: https://www.youtube.com/watch?v=V3sPGQiUJHs
  Also heavy on show-and-tell, thin on procedure details,
  though he does mention that the Zero 2W he's using doesn't work with bluetooth,
  that you have to use wifi or ethernet,
  and further that you should set up a private network to avoid disrupting your "regular" network.
  He also says to enable SSH on the pi so you can connect to it from a PC terminal.
  He also installed meshtastic[cli] (at 19:35)
• Other videos to investigate:
  worthless - uses SX1262 LoRaWAN: https://www.youtube.com/watch?v=7IepCbktGT8
  pretty general, in Spanish with translation: https://www.youtube.com/watch?v=pykZ7xf5lQM
  https://www.youtube.com/watch?v=HzddKyepqxA
  The Comms Channel - meshtastic - Getting Started (11 videos); https://www.youtube.com/playlist?list=PLshzThxhw4O5JTOACGHzYSSd3soDhoXKK
  The Comms Channel - meshtastic - Advanced Series (8 videos); https://www.youtube.com/playlist?list=PLshzThxhw4O4--klTjqDzR6KeJyqXNNXI

---------------------------------------------------------

• Plug the hat into your rPi.
  Connect the antenna to the transmitter.
  Never power on the radio without the antenna connected.
  ---------------------

• Configure rPi:
  This involves telling the rPi to enable the SPI interface, and ignore the CS line:
  Do this by editing the config.txt file, which is usu located in /boot, or perhaps in /boot/firmware
  $ sudo nano [path]config.txt
  Add or uncomment (remove leading "#") these lines:
  dtparam=spi=on
  dtoverlay=spi0-0cs
  tells rPi: Don't claim any CS pins for SPI0.
  This requires a device with its CS permanently enabled.

  Not sure if you need i2c, but if so, add this line:

  dtparam=i2c_arm=on

  If your rPi has GPS, you need to enable it by also adding this line:

  enable_uart=1

  close and save nano edit with ctrl-x, Y, -enter-
  reboot, and confirm by finding: /dev/spidev0.0
      and /dev/ttys0 if the GPS was enabled.
  ---------------------

• Load the MeshTastic software (meshtasticd) into the rPi:
  • When using Meshtastic on a Raspberry Pi to create a native Linux Meshtastic node, you install meshtasticd.
    meshtasticd is the Meshtastic firmware compiled to run as a daemon (a background service) on Linux-native devices like the Raspberry Pi.
    This allows the Raspberry Pi to directly participate in a Meshtastic network using a compatible LoRa HAT (Hardware Attached on Top) for SPI radios.
    While you might use the meshtastic Python CLI (command-line interface) for configuration and interaction with a Meshtastic device connected via USB, meshtasticd is the core application that enables the Raspberry Pi itself to function as a Meshtastic node.
    -------------------
  • actual procedure I will use is still TBD...
    but here's the direction I'll take as a first pass:
    assume bookworm 64-bit:
    from: https://meshtastic.org/docs/hardware/devices/linux-native-hardware/
    [[ "$(. /etc/os-release && echo $NAME)" == Raspbian* ]] && echo "ERROR: Raspberry Pi OS (32-bit) detected, please use the Raspbian repos."
    echo 'deb http://download.opensuse.org/repositories/network:/Meshtastic:/beta/Debi... /' | sudo tee /etc/apt/sources.list.d/network:Meshtastic:beta.list
    curl -fsSL https://download.opensuse.org/repositories/network:Meshtastic:beta/Debia... | gpg --dearmor |sudo tee /etc/apt/trusted.gpg.d/network_Meshtastic_beta.gpg > /dev/null
    sudo apt update
    sudo apt install meshtasticd
  • First install attempt will be on jPi-08, a rPi 4B
    -------------------

  • Well, that didn't work, at least not the way it seemed to be saying it should...
    Specifically, I could not get the first command line to work. The "[[..." seemed to be a problem,
    perhaps typing it in verbatim as I interpreted the instructions was wrong,
    or perhaps there was some shorthand trick that someone with more knowledge than me would have understood intuitively,
    but regardless it didn't work.

  • I did manually type in $ . /etc/os-release && echo $NAME, and indeed it printed out "Debian GNU/Linux", which I think was the point of the command, so I proceeded...
    I did the echo deb, curl, update and install commands, and all worked without error, so I rebooted and believe the install worked,
    as confirmed by the presence of /etc/meshtasticd/config.yaml

  • $ pip show meshtastic ... fails - as you'd expect since it isn't installed, meshtasticd is installed instead
    $ meshtasticd --help ... in fact shows options
    $ meshtasticd --info ... however fails as unsupported option
    $ meshtasticd ... shows what appears to be a log file
    $ meshtasticd --version ... shows 2.7.15

  ---------------------

• Configure meshtasticd:
  from: https://meshtastic.org/docs/hardware/devices/linux-native-hardware/?os=d...
  The meshtasticd configuration is at /etc/meshtasticd/config.yaml by default.
  If a config.yaml is found in the current directory, that will take precedence.
  Follow instructions in the link. Also more stuff ...
  ls /etc/meshtasticd/available.d
  the file: lora-waveshare-sxxx.yaml was shown
  sudo cp /etc/meshtasticd/available.d/lora-waveshare-sxxx.yaml /etc/meshtasticd/config.d/
  successful

  
  Other stuff in the link:
  enable web server: not sure if I need this or how to use it ...
  note that bluetooth currently unsupported on native Linux devices ...

  
  Since the meshtasticd runs as a daemon, it must be started.
  procedure in the link to auto-start it on bootup

  
  view status of daemon:
  sudo systemctl status meshtasticd

  view meshtastic logs:
  journalctl -u meshtasticd -b
  ---------------------

• Load and configure meshtastic CLI:
  • With CLI, you can interact with meshtastic using tyhe command line:
    meshtastic --host localhost ...
  • This allows interacting with your node using the command line on your host PC,
    rather than eg. an Android App.
    -----------------
  • pip3 install --upgrade pytap2
    error for "externally managed environment"
    • following alt procedure I discovered when doing the ADC, I executed:
      sudo python -m venv my-venv
      sudo my-venv/bin/pip install --upgrade pytap2
      successful
  • pip3 install --upgrade "meshtastic[cli]" - errored again...
    sudo my-venv/bin/pip install --upgrade "meshtastic[cli]"
    successful
  • Using CLI:
    https://meshtastic.org/docs/software/python/cli/usage/

  ---------------------

• Using meshtasticd:
  • from GoogleAI: 'To send a Meshtastic message using meshtasticd, you can use the curl command to interact with the meshtasticd API. This allows you to send messages to your mesh network from a command line or through integrations with other systems like Home Assistant.
  • Here's how to send a message:
    Ensure meshtasticd is running: You need to have meshtasticd running and connected to a Meshtastic node. You can configure its runtime parameters through environment variables if using a containerized setup.
    Send the message via curl:
    Use a POST request to the /messages endpoint of the meshtasticd API, including your message as a query parameter.
    The default port for the API is typically 8097.
    curl -X 'POST' 'http://localhost:8097/messages?message=Your%20message%20here'
  • Explanation:
    curl -X 'POST': Specifies that you are sending a POST request.
    'http://localhost:8097/messages': This is the endpoint for sending messages.
    Replace localhost:8097 with the actual IP address and port if meshtasticd is running on a different machine or port.
    ?message=Your%20message%20here: This appends your message as a query parameter.
    Remember to URL-encode any special characters in your message (e.g., spaces become %20).
    Example:
    To send the message "Hello from meshtasticd!", you would execute:
    curl -X 'POST' 'http://localhost:8097/messages?message=Hello%20from%20meshtasticd!'

    " end GoogleAI info

  -----------------------

• Using meshtastic CLI with meshtasticd:

  from GoogleAI: 'Yes, it is possible to use the Meshtastic CLI to interact with a meshtasticd instance.
  meshtasticd is a daemon designed to run on Linux-native devices (like Raspberry Pis with radio hats or USB radios) and provides a way to manage Meshtastic devices. The Meshtastic CLI can then be used to communicate with this running daemon.
  To do this, you would typically use the --host option with the Meshtastic CLI, specifying the address of the machine running meshtasticd. For example, if meshtasticd is running on the same machine, you might use:
  Code

  meshtastic --host localhost --info

  This allows for remote administration of devices connected to the meshtasticd instance without a direct physical connection to the device itself.
  " end GoogleAI

  ---------------------

• Using mestastic CLI:
  • Ensure you have Python 3 and pip installed, along with the necessary serial drivers for your device's USB-to-UART bridge (e.g., CP210X or CH9102).
  • Connect: The CLI can connect to your Meshtastic device via serial (USB) or Bluetooth Low Energy (BLE).
    for Serial (USB): Specify the serial port using the --port or -p option. For example:
    meshtastic --port /dev/ttyACM0 --info
    (Replace /dev/ttyACM0 with your device's serial port.)

    for Bluetooth (BLE): Use the --ble option along with the device's name or address.

    meshtastic --ble "Meshtastic Device Name" --info
    The first time you connect via BLE, you may be prompted for a PIN.
  • Commands: The CLI offers various commands for managing your device:
    --info: Display device information.
    --nodes: List nodes on the mesh.
    --export-config > file.yaml: Export current device configuration to a YAML file.
    --configure file.yaml: Apply a configuration from a YAML file.
    message send -m "Your message": Send a message to the mesh.
    --ch-set psk [key | none | random | default]: Set the channel preshared key for encryption.
    reset: Reset the radio.
    location set --lat LATITUDE --long LONGITUDE --alt ALTITUDE: Set the radio's location.
    eg:
    meshtastic message send -m "Hello from the CLI!"
    Change the primary channel's preshared key to a random one:
    meshtastic --ch-set psk random

----------------------

-------------------------------

eof