Overview
Once your hardware is assembled and programmed, you'll need to configure network settings to ensure your node can communicate with other HRMesh nodes and repeaters.
Key Configuration Parameters
Frequency Band
HRMesh operates in license-free frequency bands depending on region:
- US (902–928 MHz): Use US915 or US902 firmware variant
- EU (863–870 MHz): Use EU868 firmware variant
- Australia: Use AU915 variant
Set your region in the firmware configuration before uploading:
// In config.h or platformio.ini
#define LORABAND US915 // or EU868, AU915
Spreading Factor and Bandwidth
These settings affect range vs. data rate:
| SF | Sensitivity | Speed | Power | Best For |
|---|---|---|---|---|
| 7 | -124 dBm | Fast | Low | Short range, urban |
| 9 | -129 dBm | Medium | Medium | Balanced coverage |
| 11 | -137 dBm | Slow | High | Maximum range |
| 12 | -139 dBm | Very Slow | Very High | Long distance |
Recommended: Start with SF9 for balanced performance.
Node ID and Network Key
Configure unique identifiers:
- Node ID: A unique identifier for your device (0–255 or 0–65535 depending on protocol)
- Network Key: Shared encryption key for all HRMesh nodes (provided by your community coordinator)
Store these in EEPROM or flash memory:
const uint8_t nodeID = 42;
const uint8_t networkKey[16] = { /* 16 bytes from community */ };
Web Configuration Interface
Many Heltec boards support a web-based config portal:
- Power on the node with GPIO0 held low
- Connect to the
HRMesh-Config-XXXXWiFi network - Open
192.168.4.1in your browser - Fill in:
- Node name
- Network frequency
- Spreading factor
- Network key
- Click Save and Reboot
Testing Your Configuration
After configuration:
Check Serial Output:
[INFO] Node 42 initialized [INFO] Frequency: 915.0 MHz [INFO] Spreading Factor: 9 [INFO] Waiting for network...Verify Connectivity:
- Look for
[INFO] Network joinedmessage - Monitor signal strength indicators
- Send a test message to confirm two-way communication
- Look for
Monitor Performance:
- Check RSSI (Received Signal Strength Indicator)
- Review message delivery success rate
- Log range tests from known distances
Advanced: LoRaWAN vs. Point-to-Point
HRMesh can operate in two modes:
LoRaWAN Mode (Class A):
- Requires gateway connection
- Higher power consumption
- Centralized architecture
Point-to-Point Mode (Mesh):
- Peer-to-peer communication
- Lower power consumption
- Decentralized—recommended for HRMesh
Ensure your firmware is compiled for Mesh mode.
Troubleshooting
Node doesn't join network:
- Verify network key matches community settings
- Check frequency band matches your region
- Ensure at least one repeater is in range
Intermittent connectivity:
- Try increasing spreading factor (better range, slower speed)
- Check for RF interference (microwave, WiFi, etc.)
- Reposition antenna away from metal objects
Message delivery is slow:
- Reduce spreading factor for faster (but shorter range) messages
- Move closer to repeaters
- Review network congestion