MeshCore Bot Offline

Radio node

Bot

Live activity

    FavoriteNameTypeLast advertRouteKey

    Adding contacts

    Stored on the node, so the MeshCore app shows the same setting.

    SlotNameTypeKeyBot answers

    Add channel

    –
    packets heard in the last hour

    Raw radio log

    every packet your node hears, decoded where possible

      When the mesh is busy

      packets heard per hour, last 7 days

      What is on the air

      Signal quality

      SNR of every packet heard

      Who carries your traffic

      last repeater before your node

      Busiest channels

      messages

      How far your messages get

      channel messages heard back from a repeater, per day

      Noise floor

      your node, last 24 hours

      Who talks most

      received messages
      SenderMessagesLast
      this node, last 14 days; repeated lines are counted
        –
        people read you

        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.

            Pick a repeater, room, sensor or companion on the left.

            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.

            RoomKeyRouteStatusAuto-loginBot answers

            Add room server

            Rooms appear here by themselves once the node hears their advert. To add one now, paste its share link (MeshCore app → contact → Share → copy, starts with meshcore://), or its public key with a name.

            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

            Current: –

            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.

            RepeaterHashStatusIn paths Heard directly SNRRSSILast heardLast advert
            stopped

            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.

            RatingSetupWhenNoise floorPackets heard Receive errorsError rate SNRRSSI

            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.

            NameIdentityRoleMessagesLast seenSubscriptions

            Rate limits per role

            Cooldown: seconds between replies to the same person (empty = the bot-wide cooldown). Per hour: replies per person per hour (0 = unlimited). Blocked users are ignored completely.

            NameTriggerActionsFiredLast

            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.

            Test with message

            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.

            Set value

            Announce now in:
            KeyValuePublicUpdatedSourceExpires

            New schedule

            Presets:
            NameChannelContentWhenNext runLast 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

            Bot

            A reply waits until repeaters have passed the question on; the random part keeps it from going out at the same moment as another bot's answer, and scheduled posts of several bots at the full hour apart. Then every channel message waits until the radio has heard nothing for the quiet time (at most 8 s more; 0 = off).

            Default channels the bot answers in:

            Firmware

            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

            Notify me about

            Nothing is shown for a conversation you are looking at. Stored in this browser only.

            Advert