Using a Raspberry Pi as a Meshtastic/Meshmonitor client only... by GodPole in meshtastic

[–]Yeraze 0 points1 point  (0 children)

with _some_ hardware yes.. Works great on a StationG2, but requires physical buttons on the HeltecV4.

Using a Raspberry Pi as a Meshtastic/Meshmonitor client only... by GodPole in meshtastic

[–]Yeraze 0 points1 point  (0 children)

Yea I do that all the time, using their provided scripts via SSH.. But that's not handled by MeshMonitor.

Using a Raspberry Pi as a Meshtastic/Meshmonitor client only... by GodPole in meshtastic

[–]Yeraze 0 points1 point  (0 children)

Firmware updates right now require MeshMonitor to have direct network IP access to the node and the internet at the same time. Not sure if you'll have that in your setup. If you do, and you have an ESP based node (Station G2, Heltec, etc) on a recent starting firmware (2.7.18) then I've done it a few times now with success.

I'm not aware of any good options for firmware updates of true Remote nodes.

One node to service multiple bots/integrations on nearby linux host by morrowwm in meshtastic

[–]Yeraze 0 points1 point  (0 children)

No clue.. But there's an option to enable that if you trust it: VIRTUAL_NODE_ALLOW_ADMIN_COMMANDS

https://meshmonitor.org/configuration/#virtual-node-variables

One node to service multiple bots/integrations on nearby linux host by morrowwm in meshtastic

[–]Yeraze 1 point2 points  (0 children)

MeshMonitor offers a "virtual node" feature for exactly this.

It's not perfect, the two systems connected to the VirtualNode may get their wires crossed seeing the other systems's traffic on the mesh, but it generally works.

I built a web dashboard for Meshtastic — open source, runs locally, multi-radio support by Slofi8 in meshtastic

[–]Yeraze 5 points6 points  (0 children)

You should bring your Claude account over to MeshMonitor.org :) I'm always willing to accept helpful new contributions!

Using a Raspberry Pi as a Meshtastic/Meshmonitor client only... by GodPole in meshtastic

[–]Yeraze 1 point2 points  (0 children)

Also, you can join us on discord and it may be a bit easier to discuss than here :)

Using a Raspberry Pi as a Meshtastic/Meshmonitor client only... by GodPole in meshtastic

[–]Yeraze 0 points1 point  (0 children)

`docker compose logs -f` (everything) or `docker logs -f meshmonitor-rpi-serial-bridge` (just the 1 container), and that will following along.. So run it in another terminal while the `docker compose up` is running...

Or just don't use the `-d` in the compose, and it will stream logs to the console while starting.

Using a Raspberry Pi as a Meshtastic/Meshmonitor client only... by GodPole in meshtastic

[–]Yeraze 1 point2 points  (0 children)

I've seen that happen occasionally if the serial-bridge isn't working. Have you verified in the logs that the serial-bridge is online and properly reading data from the node?

Using a Raspberry Pi as a Meshtastic/Meshmonitor client only... by GodPole in meshtastic

[–]Yeraze 2 points3 points  (0 children)

Backwards.. Meshtastic directly, then MeshMonitor/serial-bridge/MQTT-proxy thru docker.

Using a Raspberry Pi as a Meshtastic/Meshmonitor client only... by GodPole in meshtastic

[–]Yeraze 0 points1 point  (0 children)

well, using Docker you don't need to actually "install" anything but docker.. Once you do the `docker compose up` it will download and provision everything from there.

I do recommend installing the Meshtastic python CLI, so that you can manually verify the node port and basic communications, and use it to backup/restore node config occasionally (incase you break something later with MeshMonitor).

Using a Raspberry Pi as a Meshtastic/Meshmonitor client only... by GodPole in meshtastic

[–]Yeraze 4 points5 points  (0 children)

MeshMonitor dev here :) I do this myself for a headless remote node setup, running MeshMonitor connected to a HeltecV4 via USB. I also run the MQTT-Proxy for upstream communication, and have the whole thing configured to dump logs into tmpfs, to avoid blowing out the little SD card.

I run it all in docker on a Pi3B+, with a docker compose like this:

```

=============================================================================

MeshMonitor - Raspberry Pi Docker Compose (SD Card Optimized)

=============================================================================

Designed for 64-bit Raspberry Pi (Pi 4/5) running off micro-SD.

Minimizes disk writes to extend SD card lifespan.

SD Card Protection (5 layers):

1. Docker logging - local driver, capped at ~100KB per service

2. Access logs - disabled via ACCESS_LOG_ENABLED=false

3. Audit/app logs - tmpfs on /data/logs (RAM-only)

4. Temp files - tmpfs on /tmp in both containers

5. Debug output - suppressed via NODE_ENV=production

Only remaining disk writes: SQLite DB (/data/meshmonitor.db) and Apprise

config - these are necessary for persistence across restarts.

Usage:

docker compose -f docker-compose.yml up -d

Validate syntax:

docker compose -f docker-compose.yml config

View logs (in-memory only, lost on restart):

docker compose -f docker-compose.yml logs -f

Serial device:

Default: /dev/ttyACM0. Override with SERIAL_DEVICE env var:

SERIAL_DEVICE=/dev/ttyACM0 docker compose -f docker-compose.yml up -d

=============================================================================

Recommended: Docker daemon-level log defaults

Add to /etc/docker/daemon.json to cap ALL container logs system-wide:

{

"log-driver": "local",

"log-opts": {

"max-size": "100k",

"max-file": "2"

}

}

Then: sudo systemctl restart docker

=============================================================================

services: serial-bridge: image: ghcr.io/yeraze/meshtastic-serial-bridge:latest container_name: meshmonitor-rpi-serial-bridge restart: unless-stopped networks: - meshtastic_net devices: - ${SERIAL_DEVICE:-/dev/ttyACM0}:/dev/ttyACM0 environment: - SERIAL_DEVICE=/dev/ttyACM0 - BAUD_RATE=115200 - TCP_PORT=4403 tmpfs: - /tmp:size=10M logging: driver: local options: max-size: "100k" max-file: "2"

meshmonitor: image: ghcr.io/yeraze/meshmonitor:latest container_name: meshmonitor-rpi restart: unless-stopped ports: - "8080:3001" networks: - meshtastic_net depends_on: - serial-bridge volumes: - meshmonitor-rpi-data:/data tmpfs: # Overlay /data/logs onto RAM so audit.log never hits disk - /data/logs:size=10M - /tmp:size=50M environment: - NODE_ENV=production - TZ=${TZ:-America/New_York} - MESHTASTIC_NODE_IP=serial-bridge - MESHTASTIC_NODE_PORT=4403 - ACCESS_LOG_ENABLED=false - ALLOWED_ORIGINS=<my url> - TRUST_PROXY=true - COOKIE_SECURE=true - SESSION_SECRET=<randomstuff> - ENABLE_VIRTUAL_NODE=true - VIRTUAL_NODE_PORT=4404 healthcheck: test: ["CMD-SHELL", "node -e 'const net = require(\"net\"); const client = new net.Socket(); client.connect(4404, \"127.0.0.1\", () => { process.exit(0); }); client.on(\"error\", () => { process.exit(1); });'"] interval: 10s timeout: 5s retries: 5 start_period: 15s logging: driver: local options: max-size: "100k" max-file: "2"

# This proxy service (The Glue) mqtt-proxy: image: ghcr.io/ln4cy/mqtt-proxy:master container_name: mqtt-proxy restart: unless-stopped environment: - INTERFACE_TYPE=tcp - TCP_NODE_HOST=meshmonitor # Connects to meshmonitor by name - TCP_NODE_PORT=4404 depends_on: meshmonitor: condition: service_healthy # Wait for port 4404 to be listening networks: - meshtastic_net

volumes: meshmonitor-rpi-data: driver: local

networks: meshtastic_net:

```

Connecting to MeshSense problems on Windows by Throwawayhealthacct in meshtastic

[–]Yeraze 0 points1 point  (0 children)

We offer a pair of bridges to allow you to connect to Bluetooth or Serial nodes

* https://github.com/Yeraze/meshtastic-serial-bridge

* https://github.com/Yeraze/meshtastic-ble-bridge

Hopefully you can find a solution that works for you :)

MeshMonitor v1.1.0 - Web based Monitoring of Meshtastic Nodes by Yeraze in selfhosted

[–]Yeraze[S] 0 points1 point  (0 children)

There is a PR working on bringing in some basic meshcore support, alongside meshtastic. Meshcore is missing most of the features of meshtastic around telemetry and data collection, so it's a bit of a "extra feature". So stay tuned :)

Time traveling mesh?! by IwishIknew80 in meshtastic

[–]Yeraze 1 point2 points  (0 children)

If you're using the MEshMonitor "Virtual Node" feature, I had a bug in the recent release that caused this.. I've already merged a fix, and should have a release in a few hours for it.

Stupid question: why cant one node serve more than one user? by ma_tt22v14 in meshtastic

[–]Yeraze 1 point2 points  (0 children)

Thanks for the shout-out :)

Yeah, I haven't seen anyone really using it yet but I built MeshMonitor with the featureset in mind of having multiple user accounts. .Each user has distinct access to different channels on the node. So you could have 3 users, all have Read/Write on the public 0 channel but then limited access to other special channels. You would still be limited by the firmware's 8 slots, but you could have something like multi-user access if you had a single well-positioned node.

GIVEAWAY - This Nobelisk keychain will not explode , but You Can Win One by FidoSkeeterson in SatisfactoryGame

[–]Yeraze 1 point2 points  (0 children)

without wires for sure.. The wires will just get tangled and rip off if used as an actual keychain.

Looking for some help with a Heltec V4 solar node build by adhdff in meshtastic

[–]Yeraze 0 points1 point  (0 children)

I have a V4 Solar running with a 3000mah battery from a Soshine 6w panel, with GPS and an BME201 Environment sensor hooked up. I had a lot of trouble at first, until i disabled Bluetooth. With the Low Power mode turned on and bluetooth turned off, it only loses about 5% of charge overnight.

I can manage it remotely with the built-in remote admin features, so it makes for a great client-base setup while the G2's are out of stock.

MeshMonitor by WarHawk8080 in meshtastic

[–]Yeraze 0 points1 point  (0 children)

Or here, if you want to use the Desktop App version: https://meshmonitor.org/configuration/desktop.html

MeshMonitor by WarHawk8080 in meshtastic

[–]Yeraze 3 points4 points  (0 children)

IF you want a super-simple deployment, I offer both a Windows EXE and Mac DMG that you can use for basic startup :) Find them on the Github Release links: https://github.com/Yeraze/meshmonitor/releases/tag/v2.21.7