Files

T

davidandClaude Sonnet 5 a1ba1a9603 Add ansible-managed wifi profiles for meshcore nodes

Each node now gets three NetworkManager wifi connections via a new
wifi role: dotnetwork (home), dotmobile (phone hotspot, for field
troubleshooting), and a host-specific deployed-location network.
Credentials live in a new per-repo ansible-vault (group and host
scoped), matching the pattern already used in dotnetwork.

Also updates the README's Pi imaging instructions from Bookworm to
Trixie, matching what the nodes actually run.

Co-Authored-By: Claude Sonnet 5 <[email protected]>

2026-07-06 20:07:26 +01:00

2.2 KiB

Raw Blame History

dotmesh-monitor

Ansible playbooks for deploying MeshCore monitoring nodes (Raspberry Pi Zero W / Zero 2 W).

Hosts

Host	Hardware	Group
dm-baldock	Pi Zero W (armv6)	zero_w
dm-ashwell	Pi Zero 2 W (armv7)	zero2_w
dm-edworth	Pi Zero 2 W (armv7)	zero2_w

Prerequisites

Local machine:

pip install ansible
# or: sudo apt install ansible

New Pi node checklist:

Flash Raspberry Pi OS Lite (Trixie), connect to WiFi
Install Tailscale and join the network
Ensure david user exists with sudo access
Connect the MeshCore device via USB, then find its serial ID:
```
ls /dev/serial/by-id/
```
Set serial_port in ansible/host_vars/<hostname>.yml

SSH key auth is required. From this machine:

ssh-copy-id david@<hostname>.tail740bb.ts.net

Usage

Deploy to a single host (recommended for first run / testing):

cd ansible
ansible-playbook -i inventory.yml site.yml --limit dm-edworth

Deploy to all nodes:

ansible-playbook -i inventory.yml site.yml

Dry run:

ansible-playbook -i inventory.yml site.yml --limit dm-edworth --check

If sudo requires a password, add --ask-become-pass.

You'll be prompted for a Tailscale auth key — leave blank if the node is already authenticated.

What it does

base — apt upgrade, installs screen/pipx/vnstat/git, sets MOTD, installs and authenticates Tailscale
meshcore_cli — installs meshcore-cli via pipx
meshcore_capture — runs the agessaman/meshcore-packet-capture install script, writes .env.local config, enables meshcore-capture.service, deploys update/log helper scripts
scripts — deploys voltage.sh and bandwidth.sh

Config

Shared MQTT config lives in group_vars/meshcore.yml. Per-host serial port is in host_vars/<hostname>.yml.

Running the playbook again re-applies .env.local and restarts the service if it changed — safe to run on already-deployed nodes.

Credentials note

group_vars/meshcore.yml contains MQTT credentials in plaintext. Consider encrypting with Ansible Vault if this repo is shared:

ansible-vault encrypt_string 'yourpassword' --name mqtt_ukmesh_password

2.2 KiB Raw Blame History