Common Problems
Solutions to the most frequent problems in the mesh network.
Connectivity Problems
Tracker Won't Connect to Mesh
Symptoms:
- Doesn't appear in node list
- Can't send or receive messages
Solutions:
-
Verify powered on
- LED should be active
- Restart if necessary
-
Verify region
Settings → Radio → Region = US -
Verify channel
Settings → Channels → Channel 0
Name = Test
PSK = Ml/5IOJQyplnvlzWmnvMrg== -
Restart tracker
- Power off completely
- Wait 10 seconds
- Power on
Gateway Not Receiving Messages
Symptoms:
- Trackers send but gateway sees nothing
- No MQTT traffic
Solutions:
-
Verify Meshtastic service
sudo systemctl status meshtastic -
Verify LoRa module
lsusb
ls /dev/ttyUSB* /dev/ttyACM* -
Restart service
sudo systemctl restart meshtastic -
View logs
journalctl -u meshtastic -f
No Response from Claude
Symptoms:
- Message sent with @claude
- No response after 30+ seconds
Solutions:
-
Verify @claude in message
- Must include exactly
@claude - Not
@Claudeor@ claude
- Must include exactly
-
Verify internet connection
# On reComputer
ping 8.8.8.8
ping api.anthropic.com -
Verify Node-RED
- Open http://192.168.100.10:1880
- Verify MQTT is "connected"
-
View Node-RED logs
journalctl -u nodered -f -
Verify Claude API key
- May be expired or out of credits
Network Problems
No Internet (Starlink)
Symptoms:
- No responses from Claude
- Can't access internet
Solutions:
-
Verify Starlink
- Check Starlink router
- Verify cable not damaged
- Check antenna position
-
Verify route
ip route
ping 192.168.68.1 -
Restart network
sudo systemctl restart networking
Mesh messages continue working without internet. Only Claude requires connection.
Internal WiFi Not Working
Symptoms:
- Network
MPR114993468244600004-2.4Gnot appearing - Can't connect
Solutions:
-
Verify hostapd
sudo systemctl status hostapd -
Restart WiFi services
sudo systemctl restart hostapd dnsmasq -
View logs
journalctl -u hostapd -n 50 -
Verify WiFi interface
iw dev wlan0 info
MQTT Problems
Node-RED Not Receiving Messages
Symptoms:
- Messages reach gateway
- Node-RED doesn't process them
Solutions:
-
Verify MQTT connection
- In Node-RED, MQTT node should say "connected"
-
Verify topic
- Correct topic:
meshtastic/2/json/LongFast/!69d01ebc
- Correct topic:
-
Test manually
mosquitto_sub -h 192.168.68.127 -t "meshtastic/#" -v -
Restart Node-RED
sudo systemctl restart nodered
Hardware Problems
Battery Draining Fast
Symptoms:
- Tracker lasts less than 1 day
Solutions:
-
Change role to CLIENT_MUTE
- Significantly reduces consumption
-
Reduce GPS
- Increase interval or disable
-
Check battery
- May need replacement if old
LoRa Module Not Detected
Symptoms:
- Gateway doesn't see USB module
- Error "no device found"
Solutions:
-
Verify physical connection
- Reconnect USB cable
- Try another USB port
-
View USB devices
lsusb
dmesg | tail -20 -
Verify permissions
sudo chmod 666 /dev/ttyUSB0 -
Restart
sudo reboot
Configuration Problems
PSK Doesn't Match
Symptoms:
- Tracker powered on but not in mesh
- Other nodes don't see it
Solutions:
The PSK must be exactly:
Ml/5IOJQyplnvlzWmnvMrg==
- Verify no extra spaces
- Verify uppercase/lowercase
- Better: use QR code from already configured device
Incorrect Region
Symptoms:
- Tracker doesn't communicate with others
- Frequencies don't match
Solutions:
All devices must be on:
Region: US (915 MHz)
If you changed region:
- Device restarts
- Wait for restart to complete
- Verify it stayed on US