KevsRobots Learning Platform
84% Percent Complete
By Kevin McAleer, 4 Minutes
Your repeater is in the loft, on a pole, or in a weatherproof box on a roof. Fetching a ladder and a laptop every time you want to change a setting would get old fast. It is a good job you do not have to.
| Method | Where you need to be | Good for |
|---|---|---|
| USB serial console | Physically at the node | First setup, recovery, forgotten passwords |
| config.meshcore.io | Plugged in via USB, in Chrome or Edge | A friendlier form-based UI over the same commands |
| Over the mesh, from the app | Anywhere in radio range | Day to day admin, checking stats |
The third one is the interesting one, and it is what this lesson is about.
You are now talking to the repeaterβs command line over LoRa, encrypted, from wherever you happen to be standing.
About the wait timer
The MeshCore mobile app imposes a short wait before remote server management becomes available. An optional in-app purchase removes it. The functionality is all there in the free version - you just wait a moment.
Everything the serial console offers. In practice, the ones you will actually reach for:
Health checks
stats-core
stats-radio
stats-packets
neighbors
Tuning
set tx 20
set advert.interval 60
set flood.advert.interval 12
set flood.max 3
Housekeeping
set name Kev-Loft-01
set owner.info Kev - kevsrobots.com
advert
reboot
Why reboot matters: being able to reboot a wedged node without a ladder is worth the whole exercise on its own.
Your admin password is the only thing standing between your repeater and anyone within radio range with a MeshCore client.
Do:
password the moment you flash the node - which you did in lesson 7owner.info so people can contact you rather than reconfiguring youConsider:
set allow.read.only true
This lets people query your repeaterβs stats without being able to change anything - friendly and useful on a community node.
For tighter control:
get acl
set acl <...>
setperm <public-key> <permission>
The access control list lets you grant specific node keys specific permissions, which is worth exploring if your repeater is shared infrastructure.
stats-core gives you uptime, battery voltage and queue depth.
Queue depth is the interesting one. A consistently non-zero queue means the repeater is receiving faster than it can retransmit - the mesh around it is congested. That is the signal to reduce flood limits or advert intervals, or to talk to the local community about settings.
stats-radio gives you RSSI, SNR and the noise floor. Track the noise floor over time. A rising noise floor means new interference has appeared near your repeater, and it will quietly eat your range.
If you forget the password there is always a way back, it just needs physical access:
password <new-password>The serial console is always trusted - the password only ever gates access over the air. If that is not enough, erase wipes the filesystem and returns the node to defaults.
stats-core. What is its uptime?allow.read.only true, log out, and confirm you can still read stats but not change settings.Problem: Remote login times out.
Solution: Check you can message the repeater normally first, and that you are in range.
Why: Remote admin runs over the mesh. If messaging does not work, admin cannot either.
Problem: The app says the password is wrong but I am sure it is right.
Solution: Try the default password, in case a reflash reset it.
Why: Flashing new firmware can reset stored settings depending on the build and whether the filesystem was erased.
Problem: I changed a setting remotely and now the repeater is unreachable.
Solution: Fetch the ladder. Connect over USB and put it back.
Why: Changing frequency or radio parameters remotely instantly moves the node off the channel you were talking to it on. Never change radio settings on a remote node unless you can physically reach it.
You can use the arrows β β on your keyboard to navigate between lessons.
Comments