# Troubleshooting Guide

# My node cannot connect to others

Work through these checks in order.

1. **Verify antenna is connected.** Most common cause. Transmitting without an antenna can also permanently damage the PA.
2. **Verify modem preset matches.** Two nodes on different presets are invisible to each other. Check [Meshtastic app](https://wiki.meshamerica.com/books/hardware-guide/page/meshtastic-app) - Radio Config - LoRa - Modem Preset. Ask your local community which preset they use.
3. **Verify channel name and PSK match.** Wrong credentials mean your messages are encrypted to a key nobody else has. Verify against local network documentation.
4. **Verify frequency band.** US/Canada = 915 MHz hardware. EU = 868 MHz hardware. These cannot interoperate. Many AliExpress boards ship as 868 MHz by default.
5. **Check if other nodes are in range.** Visit meshmap.net to see nearby nodes. In rural areas you may genuinely be out of range.
6. **Verify the radio is transmitting.** Check for LoRa init errors in the serial console. A working node shows increasing packet counts in the app.
7. **Factory reset and reconfigure.** If all else fails, reset and start configuration fresh.

# My messages are not getting through

## First: identify the failure mode

- Node visible in list but messages do not arrive: routing or range issue
- Node does not appear in list at all: preset, channel, or range issue (see previous page)

## Hop count too low

If hop count is 1, you can only reach nodes in direct radio range. Increase it (Meshtastic: Radio Config - LoRa - Hop Limit, default 3 is fine for most networks).

## Network congestion

If channel utilization exceeds 25% (visible in [Meshtastic app](https://wiki.meshamerica.com/books/hardware-guide/page/meshtastic-app)), packets are colliding. Reduce your broadcast intervals for position and telemetry.

## ACK failures

Meshtastic uses ACKs to confirm delivery. No ACK means the destination node may be offline or out of range. Check its last-heard timestamp.

## Recently joined node

New nodes may not have propagated throughout the mesh yet. Wait 5-10 minutes after joining before expecting full connectivity.

## MeshCore specific

MeshCore requires successful route discovery before first contact. If intermediate repeaters are offline, the route cannot be established. Check that all repeaters in the expected path are online.

# My battery drains too fast

## Step 1: Measure actual power draw

Use a USB inline power meter to measure real current draw. This immediately shows whether you have a software config problem or a hardware issue.

## Expected draw by hardware

<table id="bkmrk-hardwaretypical-acti"><thead><tr><th>Hardware</th><th>Typical active draw</th></tr></thead><tbody><tr><td>ESP32 (T-Beam, Heltec), no display, no BT</td><td>40-55 mA</td></tr><tr><td>ESP32 with OLED display on</td><td>+20 mA</td></tr><tr><td>nRF52840 (RAK4631, T-Echo, T114)</td><td>8-15 mA</td></tr></tbody></table>

## Power drain checklist

- Screen on? Set timeout to 0.
- Bluetooth enabled? Disable if not needed.
- GPS polling? Disable or set a long interval.
- WiFi enabled (ESP32)? Disable.
- Position broadcast interval too short? Set to 30+ minutes on battery.

## Battery sizing

Battery (mAh) divided by draw (mA) = hours of runtime. 1000 mAh at 40 mA = 25 hours; at 10 mA = 100 hours. Switching from ESP32 to nRF52840 hardware typically gives 4x longer life on the same battery.

# My solar node keeps going offline

Systematic diagnosis in order of likelihood:

1. **Undersized battery or panel.** Goes offline at night or on cloudy days? Review the [Solar System Sizing Guide](https://wiki.meshamerica.com/books/solar-power-systems/page/solar-system-sizing-guide) and resize.
2. **Panel obstruction.** Bird droppings, snow, or vegetation growth. Verify the panel is clean with clear sky access.
3. **Charge controller LVD setting.** If the low-voltage disconnect threshold is too high, the controller cuts power while charge remains. For LiFePO4: LVD = 3.0V/cell (12.0V for 12V system).
4. **Water ingress.** Goes offline after rain = water ingress. Inspect all cable glands, connector weatherproofing, and enclosure seals.
5. **Thermal shutdown.** Sealed enclosures in direct sun reach 70-80 degrees C. Add venting, shading, or a radiation shield.
6. **Firmware hang.** Check for firmware updates. Enable hardware watchdog if supported.
7. **Remote monitoring.** Watch battery voltage trend via Meshtastic telemetry. Declining trend = insufficient harvest. Sudden drop to zero = hardware failure.