Radio node
Bot
Live activity
Add a contact by public key
Add a node you have not heard yet, e.g. a repeater found on a map (kiekr.app shows its public key), then test whether your node reaches it. Until its next advert the path is unknown, so the test floods; set a region to keep the flood in that area. A reply (even “wrong password”) means it was reached, and its route is stored for the next request.
Edit contact
Stored on the node, so the MeshCore app shows it too. The node takes name and position from the contact's adverts again: its next advert overwrites what you set here.
Latest 30 samples and direct messages
| Time | Heard from | Route | SNR | RSSI |
|---|
Clean up the contact list
The node keeps a limited number of contacts; it needs every one it talks to. Pick the ones you no longer need; removed contacts stay in the bot's archive unless you untick it, and come back with one click. Favorites, rooms you use, contacts with a region setting and challenge targets are never offered.
Archive
removed from the node, kept by the bot| Favorite | Name | Type | Last advert | Route | Key |
|---|
Heard, not added
Nodes whose advert your node heard but did not add as a contact (see below). Add the ones you want; the list only covers what was heard since the bot started.
| Slot | Name | Type | Key | Bot answers |
|---|
Raw radio log
every packet your node hears, decoded where possibleWhen the mesh is busy
packets heard per hour, last 7 daysWhat is on the air
Signal quality
SNR of every packet heardWho carries your traffic
last repeater before your nodeBusiest channels
messagesHow far your messages get
channel messages heard back from a repeater, per dayNoise floor
your node, last 24 hoursWho talks most
received messages| Sender | Messages | Last |
|---|
Link to the outside world
Hour by hour
Above the line: packets from beyond the border your node heard. Below: your messages, filled when something proves they got out, outlined when nothing does. Hatched: no data.
Where the border runs
Your area shaded, distance rings around you; lines are the ways in and out, labelled with the distance and, where measured, the SNR.
How far: you hear vs you are heard
Share by route length in hops, from you.
Link margin across the border
SNR on each border link, both ways, against what your radio settings can still decode.
Way in
Longest gaps in
Way out
Farthest reached
Radio links across the border
Your messages and what proves they got out
The border
How it is measured
In: an hour is linked when your node heard a packet whose route has a hop outside the border, cut off when your node was up and heard only inner traffic, and left out when there is no data. The radio log keeps 7 days; before that, received messages are used.
Out: your node hears its own repeats only from the nearest repeaters, so it cannot see how far
a message gets. A message counts as out when something beyond the border proves it: a bot answering with
the route it heard (Pong … (14,C4,DA)), a reader whose reaction came from outside, or a DM
confirmed by a contact further away than the border. The community service's probe sends a ping now and
then so bots out there report it. Neighbour tables of repeaters (Telemetry) give the SNR across the
border: how well the outside hears your area (out) and your area the outside (in).
Routes to your readers
You in the centre, every node on the ring of its hop count from you. A line is the route one piece of evidence travelled: the path of a reader's reaction to you, the repeats of your messages, or a route a ping bot wrote into its answer (“7 hops 06ccfb>be8950>…”), with the hashes matched to your contacts. Point at a node to follow its routes, click it for the evidence.
Your community
Your latest messages
and who is known to have read them
How it knows
Channel messages have no read receipts, so reading has to show in what people do. Only proof makes someone a reader; evidence counts less as it gets older (half every 30 days). Shared words count only if they are rare in that channel; answers addressed to someone else and automatic responders (bots answering within seconds) do not count.
Room servers keep posts and relay them to everyone logged in. Log in (with the room's password, if it has one) to read and post; with auto-login the bot logs in again after every connect and every hour. Bot answers lets the bot reply to commands in that room.
| Room | Key | Route | Status | Auto-login | Bot answers |
|---|
New challenge
Repeaters on the map are found by key, with their position. For a person, give roughly where they are: the route then ends at repeaters near them.
A region (like #bremen) limits how far a flooded message travels: it is only forwarded
by repeaters configured for that region. The node's default region applies to everything it floods;
a channel region scopes what the bot sends in that channel; single messages and rules can set one too.
Direct (routed) messages are unaffected.
Node default region
Known regions
Channel regions
Everything the bot sends in the channel is scoped to this region.
Repeaters
Ask a repeater in range which regions it serves.
Traffic heard, last 24 hours
"scoped" = region-scoped flood of a region not in your list.
Packets heard per hour
Table
Hops per packet
0 hops: heard directly from the sender, no repeater in between.
Links
Repeaters by the paths packets took toward this node. Thicker line = more packets. Positions are layout only, not geography.
| Repeater | Hash | Status | In paths | Heard directly | SNR | RSSI | Last heard | Last advert |
|---|
Link to the node
Every connect and drop between the bot and its node (USB, Bluetooth or Wi-Fi). Uptime counts only the time the bot ran and you had not released the link.
Events
Noise floor (dBm)
Start the live monitor to measure.
Lower is better. Around −115 dBm or below is a quiet spot; −105 or higher means interference nearby (computer, USB cable, charger, another radio).
Receive errors per sample
Start the live monitor to measure.
Packets the radio started to receive but could not decode: too weak, or hit by interference or a collision.
Packets received per sample
Start the live monitor to measure.
Placement test
Compare positions: name the setup, start the test, leave the node still for the duration. Then change one thing (cable, distance, orientation) and test again. Each test measures the noise floor, receive errors and the signal of every packet heard; the best setup is highlighted. Rating: the worse of noise floor (good ≤ −114 dBm, fair ≤ −106) and receive error rate (good ≤ 5 %, fair ≤ 15 %, rated from 10 packets on). Hover a rating for the reasons.
| Rating | Setup | When | Noise floor | Packets heard | Receive errors | Error rate | SNR | RSSI |
|---|
Compare the same remote stations: signal values depend on who happens to transmit during a test. Longer tests in busy times give fairer comparisons. Results are kept in this browser.
Your contacts and everyone who wrote to the bot, one row per person. A role belongs to the
contact: in DMs the mesh proves who it is. In channels a sender is only a name that anyone with the channel key
can type, so there admin and trusted count as user; blocking covers both. Admins send commands by DM:
!say !advert !rule !set !role !block
!status.
| Name | Identity | Role | Messages | Last seen | Subscriptions |
|---|
| Name | Trigger | Actions | Fired | Last |
|---|
New rule
Reference
Triggers (trigger.type):
message (command / match / contains / exact, kind dm|channel|any, channels),
cron (cron), data (key glob, on change|set|delete),
advert (contact_type, new), node (state),
webhook (name → POST /api/hooks/<name>), event (name, from emit).
Actions: reply text · send channel, text · dm contact, text ·
set key, value, ttl, public · delete key ·
http url, method, headers, json, body, save_as, extract, public ·
advert flood · emit event, data · log text · delay seconds.
Templates (Jinja): {{ msg.sender }} {{ msg.text }} {{ msg.hops }}
{{ msg.path }} {{ msg.snr }} {{ args }} {{ match[1] }}
{{ event.* }} {{ result.json.* }} {{ data.key }} {{ node.name }}
{{ now.strftime('%H:%M') }}; filters ago, dt, truncate_bytes, json.
when: is a list of expressions that must all be true, e.g. msg.hops > 2.
Values the bot works with. Public keys answer !key on the mesh (formerly bulletins).
Rules, schedules and templates read them as {{ data.key }}; changes can trigger rules.
Feed them here, via PUT /api/data/{key}, ./bot data set, or an http rule.
| Key | Value | Public | Updated | Source | Expires |
|---|
| Name | Channel | Content | When | Next run | Last run |
|---|
Every service answers DMs. In channels it uses either the default list (Settings, or the "Bot answers" switches on the Channels tab), its own selection, or none.
Usage
About
Versions follow semantic versioning (major.minor.patch): patch releases fix things,
minor ones add features, major ones change something incompatibly. New release: ./bot release minor.
Access keys
One key per device (phone, laptop, wall display). Revoke a key and only that device is signed out. Read-only keys can look at everything but not change or send anything.
Browser notifications
Nothing is shown for a conversation you are looking at. Stored in this browser only.