Connecting UART equipment, GPIO inputs and alarm sensors without treating a hobby mesh as an industrial control system.
Meshtastic can interface with external equipment through UART serial modes, sensor modules, digital detection inputs and—on specialized builds—remote GPIO access. These capabilities support weather stations, power systems, simple alarms and experimental controllers. They do not make a shared LoRa mesh deterministic, real-time or safe for critical industrial control.
Serial module modes
The current Serial module documentation includes several distinct modes. Choosing the wrong one is not a small formatting error; each mode defines a different protocol.
| Mode | Purpose |
|---|---|
| SIMPLE | Raw binary pass-through on a channel named serial |
| PROTO | Meshtastic Protobuf Client API for software clients |
| TEXTMSG | Serial strings become text messages; received texts are printed |
| NMEA / CALTOPO | Outputs position and waypoint sentences |
| WS85 | Parses supported Ecowitt wind sensor data |
| VE_DIRECT | Receives Victron Energy VE.Direct data |
| LOG / LOGTEXT | Outputs packet or text logs |
Confirm voltage levels, cross TX to RX, set the correct baud rate and prevent the debug console from colliding with application data. Serial packets are constrained by Meshtastic payload size and shared airtime; SIMPLE mode is a small packet tunnel, not a transparent replacement for a continuous cable.
Detection Sensor for alarms
The Detection Sensor module watches a configured GPIO input and can send a text notification when its state changes. It suits door contacts, float switches, PIR outputs and other slow digital events when electrically conditioned correctly. Configure an appropriate pull-up or pull-down, active state, minimum broadcast interval and message.
Debounce noisy contacts in hardware or software. Use isolation for long outdoor wires, lightning-exposed inputs or equipment with different ground potentials. Never connect an unknown alarm-panel output directly to a microcontroller pin.
Remote Hardware is advanced and restricted
The Remote Hardware module can read, write and watch GPIO on another node through an authenticated gpio channel. In firmware later than 2.5.3 it is excluded from normal builds and requires custom firmware; actual GPIO operations are currently performed through the Python CLI. Invalid GPIO operations can damage hardware.
Remote GPIO state change monitoring is not suitable for fast button events; the Detection Sensor module is the better fit. More importantly, packet delay, loss, duplication and node reboot make remote actuation unsafe without local interlocks. A pump, heater, door lock, siren or machinery controller must have independent electrical safety, timeout behavior and manual override.
Alarm design pattern
- Let a local controller own the sensor, filtering and safe output state.
- Use Meshtastic to report a summarized event, not raw high-frequency samples.
- Include node identity, alarm type and state in a short unambiguous message.
- Rate-limit repeats and define restoration/clear messages.
- Require acknowledgement through a separate process when consequences matter.
- Log locally so RF loss does not erase the incident record.
Testing
Bench-test power loss, reboot, disconnected sensor, stuck input, noisy contact, full channel and lost acknowledgement. Verify that a boot does not create a false alarm or unsafe output. Test both direct and relayed paths, but do not make safety depend on either. Document pin numbers because the same GPIO can serve displays, radios, GPS or boot functions on different boards.
Public-network policy
Keep experimental binary traffic and private alarms off the shared public channel. Use dedicated keys, restricted administrators and conservative intervals. Do not reveal whether a private building is occupied, unlocked or in alarm. Public environmental data may be suitable for open channels; site security states generally are not.
Meshtastic is excellent for “tell me the water level became high” or “report the solar controller summary.” It is a poor choice for millisecond control loops, guaranteed emergency dispatch or unprotected remote switching. Design the local system to remain safe and useful when the mesh is completely unavailable.