MeshMonitor 4.18.0 is out. Its headline feature is support for Meshtastic's new is_automation flag: every packet MeshMonitor sends on its own now says so, and MeshMonitor reads the same flag from every other client. This post explains what the flag is, how 4.18.0 uses it, and what changes for you.
Read the upgrade notes before you update. Auto Acknowledge and Auto Responder now behave differently by default.
The problem: bots answering bots β
A mesh with two auto-responders can talk to itself. Bot A answers a message, bot B answers bot A, and so on until a rate limit or a person stops it. Each reply takes airtime from everyone on the channel. Until now, a node had no way to tell a typed message from a scripted one.
The flag β
Meshtastic reserved bit 2 (0x04) of Data.bitfield as is_automation in meshtastic/protobufs#1134. It means "a bot or script sent this, not a person". Matching firmware constants are proposed in firmware#12128, but current firmware already passes the bit through unchanged, so nothing on the radio needs to change.
- It costs no airtime.
bitfieldis already in every packet; MeshMonitor sets one more bit in it. - It reaches every node that can decrypt the packet, because
Datatravels inside the encrypted payload. - Firmware adds its own bits (
ok_to_mqtt,want_response) with|=, so the client's bit survives. On firmware 2.8, the XEdDSA signature covers it. - Older firmware and clients ignore it.
- The sender sets it, and nothing checks it. Treat it as advice, not proof.
What 4.18.0 does with it β
Sending β
Every Meshtastic packet MeshMonitor sends for an automation sets the bit. That covers Auto Acknowledge, Auto Responder, Auto Announce, Auto Traceroute, timers, scheduled telemetry and position requests, key-repair NodeInfo exchanges, and Automation Engine actions. Messages you type never set it, and neither do admin packets.
MeshMonitor already tagged each send internally as manual or automated (it uses that tag to keep automated packets off an MQTT bridge, #5414). 4.18.0 writes the same tag into the packet. A manual send leaves bitfield out entirely, so its bytes on air match 4.17.
When a Virtual Node client replays history, the bit goes along with each automated message, so the phone app sees it too.
Receiving β
MeshMonitor reads the bit from every received packet and stores it in a new isAutomation column on messages and the packet log (migration 239). A packet with no bitfield at all stores unknown, not person.
- Messages show a bot icon next to the hop count on flagged messages. Hover it for "Sent by an automation".
- Packet Monitor shows the flag in its own column.
Pre-release testing found that the icon took a few seconds to appear. The live update omitted the flag, so the icon waited for the next poll (#6455). 4.18.0 includes the fix, and the same change makes the XEdDSA shield and MQTT badge show up at once too.
Filtering β
Auto Acknowledge and Auto Responder skip flagged messages by default. Each has a new Respond to automated messages checkbox for the rare case where you want a bot to answer a bot. See Respond to Automated Messages.
Automation Engine message triggers have a new Sent by filter:
| Value | Fires on |
|---|---|
| People only (skip automated messages) | Messages without the flag. The default for new rules. |
| Anyone | Every message. Existing rules keep this, so nothing you built changes. |
| Automations only | Only flagged messages. |
The editor warns you to set a cooldown when you pick Anyone or Automations only. Converting Auto Acknowledge to an automation carries the checkbox over as the matching Sent by value. {{ trigger.isAutomation }} exposes the flag to conditions and message text. See Sent by.
MeshCore and Reticulum have no such flag, so their messages count as sent by people.
Also in 4.18.0 β
- Public-instance mode. Run a read-only public view that hides positions, names, keys and message text from anonymous visitors.
- Embedded MeshCore MQTT broker as a source, with upstream forwarding.
- Meshtastic over MQTT with no radio. Send messages through a broker alone.
- Notification defaults for the whole mesh, with per-source overrides and cross-source dedup.
- Direct RF Contacts history for Meshtastic and MeshCore.
- Verified remote config saves. Remote admin saves read the setting back to confirm.
- Security digest Preview. See the exact digest and its length before you send it.
- Analyzer Observer owner claims. Link your MeshCore observer to a LetsMesh or MeshMapper account.
The changelog lists every change and fix.
Upgrade notes β
- Auto Acknowledge and Auto Responder now ignore flagged messages. If one of your bots relied on answering another MeshMonitor bot, tick Respond to automated messages on that source. Other MeshMonitor 4.18 instances flag their automated messages; clients that don't set the bit look the same as before.
- New Automation Engine message rules start at People only. Existing rules are unchanged.
- Migrations 233 to 239 run on startup. Back up before you upgrade, as always.
- Other default changes (Companion heartbeat, notification subscriptions, Exchange Position, Room Sync re-join) are listed in the changelog's upgrade notes.
Thanks to the Meshtastic maintainers for reviewing and merging the protobuf change, and to everyone who tested the release candidates.
