Messages per hour
How this works
Everyone heard on the watched channels or on Public since the last restart (the latest 256), everyone known by an advert, everyone reminded before, and the companions you added. Where you place someone counts before the route does. One not heard for 90 days is dropped, unless you set it.
More actions
How this works
What their adverts tell, which IDs the routes of packets show relaying, and what you add or correct yourself. One not heard for 90 days is dropped, unless you set it.
More actions
How this works
Room servers and sensors heard by their advert, and what you add or correct yourself. Once you set one, its adverts only say it is still there, until you let them decide again. One not heard for 90 days is dropped.
More actions
Probably outside Slovenia: say where each one is.
How this works
Companions whose last message came in over a first repeater nothing is known of (no position from its advert, and you have not placed it). Your answer goes on your list of companions and counts before the route does. Until you decide, they are treated like everyone else. When that repeater becomes known, they leave this list by themselves.
Senders who come in through a repeater abroad
How this works
A sender who comes in through a repeater abroad is not reminded: you get a report instead. Repeaters with a position are judged by it; here you can mark others as foreign by their ID.
Traffic between other nodes, inside Slovenia, of the last seven days.
How this works
Traffic between other nodes that this node cannot read: private messages, requests and replies, and messages on channels it has no key for. Only what stays inside Slovenia is shown. It is counted per day and kept for seven days at most (168 hours), also across a restart. A packet shows one byte of each node's key, so a name here is every known node that byte fits, not a certain match.
More actions
Packets per hour
Airtime, % of the hour
Signal and noise, dBm
SNR of the packets heard, dB
Damaged packets, %
CPU, °C, and memory in use, %
Wi-Fi signal, dBm
Legend
Upload
How this works
The adverts of repeaters with a position inside Slovenia, as they came off the air, go to map.meshcore.io signed with this node's key, the way the map's own uploader does it. One round a minute after each clock sync from the internet (after the start, then twice a day); an advert that is not newer than the one sent before, or less than an hour newer, is left out. Two uploads in a row without a good answer pause it for 24 hours. A refused advert (the server answered 4xx) is not sent again.
Rounds
Repeaters
Polling
How this works
Twice a day, at the quietest hour of 00-05 and of 12-17 UTC (the least airtime over the last 7 days; 03:00 and 15:00 until that is known), the node logs in as guest (empty password) to each repeater you picked below (up to 20, from your repeater contacts heard directly or over one repeater) and asks for its status (a scheduled round leaves out one asked less than an hour before): battery, uptime, noise, airtime, traffic and the link both ways. Requests go along the known route; after the login the node gives the repeater its route back, so the replies come the same way. One hop away the route back also goes before each login: a repeater that does not know it answers with a flood the repeater between may drop. If both direct tries get no answer, a third login goes as a flood with this node's region, which the repeater answers with the same region. A picked repeater is asked only while the node hears it directly or over one repeater; otherwise its poll is logged as "no route" and nothing is sent. 30 s between repeaters. A repeater with a guest password set does not answer. The log keeps every poll for 7 days.
Repeaters
What counts as right
How this works
For companions: their messages on the watched channels, from now on; what was noted before keeps its marks. For repeaters, room servers and sensors: what their last flooded advert carried, judged by this rule as it is now (Nodes, Settings; on the map, Repeaters with wrong settings). A region counts as right when a watched channel allows it. info-bot itself sends with the size set here (with Any it keeps its own). The texts name the size where they say {hs}.
Airtime
How this works
What info-bot sends itself (reminders, welcomes, announcements, repeater polls) is counted over the last hour. When the budget is used up, reminders and welcomes wait as at the cap, polls wait a minute, and an announcement is left out with a note in Events. Messages the node only repeats do not count.
How this works
The first region is the channel's main one (the reminders name it). Leave regions empty when adding a meshcore.si regional channel to get its usual set. Hint regions are allowed, but the sender gets a one-off note that the channel is regional.
Announcement schedule
One schedule for every channel that has the announcement ticked. Times are by the node's own clock.
Timing and link
A reminder goes out about 5 seconds after a wrong message.
How this works
On each channel the same companion gets at most one reminder a day and five in all, then the companion is marked in the list. For everyone together info-bot sends at most 2 reminders in 4 hours.
Welcome on Public
How this works
Someone info-bot has never seen before, who writes on Public from inside Slovenia, gets one message there that sends them to your first watched channel. Inside means: their own position says so, or the message came over Slovenian repeaters only (or was heard directly). Nothing is checked or corrected on Public. It counts towards the 2 messages in 4 hours.
Texts
How this works
In place of {name} {ch} {reg} {hs} {link} {also} it puts the sender, the channel, its main region, the path hash size of the rule ("2 bajta"), the link and the other allowed regions. {add} is the link that adds the channel in the MeshCore app, about 100 characters long: it is meant for the welcome, where info-bot shortens the greeting rather than cut the link. Beside each text you see how it arrives.
More actions
Admin
How this works
One login field for both accounts: the password decides which one you are. The password never travels: the browser proves it knows it. Five wrong tries from one address lock that address for 5 minutes, then 15, then 60.
Viewer
How this works
The viewer sees the Monitor, Companions, Repeaters, Bot and Statistics, and changes nothing. Private traffic and System are not shown to it, and the node refuses its commands that would change something. Its password must differ from the admin's.
More actions
MeshCore app over Wi-Fi
The app's port only takes devices allowed here. This device is .
Through the public copy a device cannot be allowed: open the node's own page on its network for that.
Hotspot
How this works
When the node's Wi-Fi network is missing for 2 minutes, the node opens its own network, so the page and the app can be reached off-grid. Join it with the password below, then open https://192.168.77.1:10000 (or http://192.168.77.1:10001). It goes off again once its network is back and no device has been on the hotspot for a minute. Without a password there is no such hotspot. The button on the LoRa board held for 10 seconds opens another one at any time: MeshCore, without a password, at the same address. It closes 10 minutes after the last device left (or after it opened, when nobody joins), or when the button is held 10 seconds again. The page still asks for its password, and the app port still takes only the devices allowed here.
More actions
Access from outside
The certificate
The node made this certificate itself, so a browser warns the first time. It is this node when the browser shows the same fingerprint in the certificate's details.
Public copy
How this works
The node sends what this page shows to your own server (a Cloudflare Worker with its database, see cloud/README.md in the firmware's source): the figures every minute, each message, advert, event, hour and repeater poll at most 10 s after it happens, the node lists when they change. Anyone can open the copy there: it shows no settings, nothing private, and changes nothing on the node. It keeps 180 days; the node keeps 7. Every request is signed with the key below, and the server takes it only with the same key.
The key
Give the server the same key (its secret INGEST_KEY). Keep it secret: with it anyone could write to your copy.
Name
Wi-Fi network
How this works
The network the node joins. A change applies after a restart. If the node cannot join it, it opens its hotspot after 2 minutes (when a hotspot password is set, under Access), so it stays reachable. Power saving lets the radio sleep between beacons; off keeps it always awake. The password goes to the node as typed: change it over HTTPS.
LoRa radio
How this works
Frequency, bandwidth, spreading factor and coding rate must be the same as on the other nodes of the mesh, or this node hears nobody. A change applies after a restart. Transmit power applies at once.
Internet and clock
How this works
The node asks a time server at the start and then twice a day. An answer says it is online and sets its clock; the map upload follows a minute later. Off: the clock comes from the mesh or the app only.
Temperature guard
Memory
How this works
Internal RAM is the scarce part: each task (thread) has its own stack there, fixed at the start. Shown is the most each one has used since the start, of its size; one that comes near its size needs more, one that stays far below could give some back. The heap is the shared memory the node takes and gives back as it runs; its lowest free figure is the one that matters. The large tables and buffers are in the 8 MB PSRAM.
Restart
Settings and lists are kept. The page comes back by itself.
Storage
How this works
The history is the last 7 days, rolling: the oldest goes a block at a time as it passes 7 days, in quiet moments of the radio. Each record is written to the flash as it comes, so a restart or a power cut loses nothing. Node info (repeaters, room servers, sensors and companions known by their advert: ID, position, name) stays until 180 days after it was last heard, or until you forget it below. What you set by hand stays until you remove it. Settings and node info are in the file area.
Received data
Forget what the node heard on the air, keeping only the last:
How this works
Only what came off the air goes. Your settings, channels, texts, the rule, the accounts and the repeaters picked for polling stay, and so does what you set by hand unless you tick the last box. Whatever is heard again comes back. The way to each picked repeater stays, so the polls still reach it. The public copy on your server keeps its own data. With the clock not set, only Nothing can be chosen for the messages, private traffic, events, charts and map upload log.
The lists in one file
How this works
Repeaters, room servers, sensors, companions heard by their advert, and the companions you added: export them to keep or to move to another node. Importing merges: what is missing is added, what the file heard later is taken, your own settings stay, nothing is deleted.
Firmware update
Choose the file ending in -update.bin. The node restarts into it; a wrong file needs USB to fix.
Through the public copy: no firmware updates. Open the node's own page on its network for that.
Details
Where from
Every command works here; over USB and in the app only get bot, get web, set web.pwd and set bot live|dry|off.Reading only: the get commands (not the keys and passwords), ver, board and help.
Commands
Tap one to put it in the box. Parts in <angle brackets> are yours to fill in.