Use this if you're happy to flash a debug build and keep a small always-on computer (like a Raspberry Pi) attached to a node to relay its output.
Flash a debug-enabled build (prebuilt images are available), connect the node to a computer, and run MeshCoreToMQTT to forward what it sees to your MQTT broker(s).
Use this if you have a companion radio you'd rather not reflash, and want a computer to read it over USB, TCP, or serial.
Point the packet-capture tool at a companion radio from any computer. It reads the mesh traffic the companion hears and uplinks it. No dedicated observer firmware is required.
Use this if you're running the MeshCore Bot (or want its other features) and want it to observe the mesh at the same time.
The bot's built-in PacketCapture service module reads mesh traffic and can uplink it, so a single MeshCore Bot deployment doubles as an observer.
Use this if you're comfortable running Python and want one process to act as repeater and observer while also hosting a room server and virtual companions.
OpenHop is a Python implementation of MeshCore. A single instance repeats and observes mesh traffic while also hosting a room server and virtual companions, putting several roles on one always-on machine.
Use this if you want a point-and-click web UI to operate a companion node, with mesh observing included as a bonus.
A browser-based terminal for driving a companion node over the web. It also works as an observer, so you get remote control and mesh monitoring from the same interface.
Use this if you run Home Assistant and want your mesh data (nodes, messages, and telemetry) available as entities on your dashboard.
The meshcore-ha integration connects a MeshCore node to Home Assistant, so you can observe mesh activity and automate on it alongside the rest of your smart home.
