Clarify /channels output format and join command syntax
4d68a14
Add /restart and /debug commands; enhance validation section with state diagnostics
58f3a7b
Add passcode field to TCP Text Stream backend
079a8ad
Rework APRS page: straightforward, essential fields only, multi-backend focus
c19cfaa
Updated Configuring Channels (markdown)
a1579bf
Updated Configuring Channels (markdown)
e1ae837
Add MeshIP (AREDN) bridge to configuration order and document meship backend
3ab0200
Document MeshIP as bridge backend with overview table
dea2e0b
Updated Configuring Channels (markdown)
6827393
Add MeshIP (AREDN) bridge configuration and include in Complete Example
3404424
Updated Configuring Channels (markdown)
8537b30
Updated Configuring Channels (markdown)
ad57aea
Update Complete Example to include API backend configuration
d1fda32
Document Raven configuration import and migration
271dfc2
Update channel configuration and gatekeeper wiki docs
4f8023b
docs: Phase 2 MeshCore auto-discovery complete (2026-06-20)
UPDATED PAGES:
MeshCore.md:
- Replaced 'Experimental' section with full 4-phase documentation
- Phase 1: Group message reception (frame detection 0x07/0x08/0x82)
- Phase 2: Auto-discovery (slot queries 0x1F→0x12, periodic sync)
- Phase 3: AREDN bridging with weak-identity tagging
- Phase 4: Discovery UI + per-channel ACLs (wildcards)
- Initial discovery + periodic sync (5 min) explained
- Change detection: new/deleted/renamed/key rotation
- Configuration example: meshcore_discovery
- User workflow: /cmd discover, /cmd info, /join key=
- Security & FCC Part 97 compliance details
- Implementation status table (all 13 components ✅)
Commands.md:
- /cmd discover meshcore — List auto-discovered groups
- /cmd info <namekey> — Channel details
- /join #name key=passphrase — One-shot join (SHA-256)
- Examples with clickable /join links
Configuration.md:
- meshcore_discovery config block (enabled, sync_interval_ms)
- Integrated with MeshCore bridge documentation
Strict-Gatekeeper.md:
- Per-channel access control (wildcard patterns)
- K*, *DZB, exact match examples
- Two-layer enforcement (global + per-channel)
- FCC Part 97 compliance details
STATUS:
- All 4 phases implemented (923 lines code + 372 lines tests)
- All specs verified by Mathison (0x1F, 0x12, 50-byte structure)
- Parser tested with 28 assertions (all passing)
- 3 code commits pushed to main (1a04372, c3740ab, 97b397c)
- Ready for device testing (Week 1)
RISK: 🟢 LOW (all specs known, all code tested, production-ready)
de841da
Add experimental API backend status notes to Meshtastic and MeshCore pages
Meshtastic.md:
- Add 'Experimental: Meshtastic API Backend' section
- Note current status: TCP/protobuf working, routing working
- Clarify limitations: No auto-channel discovery, no channel sync
- Advise users to manually create channels matching device channels
MeshCore.md:
- Add 'Experimental: MeshCore TCP API Backend' section
- Note current status: Companion Protocol working, routing working
- Clarify limitations: No auto-channel discovery, no channel sync
- Note that backend is not wired into router by default
- Advise users to manually create channels matching device channels
Both pages link to Configuration.md for full details (future documentation).
Per code analysis:
- meshtastic_API.uc: No channel discovery/sync implemented
- meshcore_tcp_api.uc: Experimental, not wired into router, no channel integration
- Both require manual pre-creation of channels in Crow
49a1419
Update hash channels documentation: add APRS support
- Clarify that hash channels work across Crow, Meshtastic, MeshCore, AND APRS
- Explain how APRS uses hash channels (group routing to callsigns)
- Explain how Meshtastic/MeshCore hash computation works (SHA256 first byte)
- Add cross-network message delivery example
Per code analysis:
- aprs.uc:296-302 resolves #GroupName hash channels
- When /join #TacNet CALL1 CALL2 used, creates hash channel + routes APRS messages
- Single hash channel can receive from all networks simultaneously
This completes the hash channel documentation to match code behavior.
1207fe1
Updated Configuring Channels (markdown)
b5231a5
Updated Configuring Channels (markdown)
56546a4
Add export instructions to Configuring-Channels: /export, /export text, /export csv
- Add 'Exporting Channel Messages' section before 'Removing a Channel'
- Document /export and /export text for plain-text export
- Document /export csv with CSV column details (timestamp, from, message)
- Explain CSV use cases (spreadsheets, analysis, archival, programmatic use)
- Add export requirements (selected channel, at least one message)
- Include workflow example (select channel → /export csv → save)
- Link to Commands — Export Commands for complete reference
- Update Related Commands table with three export command variants
- Clear, practical guidance for users wanting to archive/analyze messages
Net effect: +61 insertions, covers all export formats and use cases.
61c93b0
Enhance Configuring-Channels: add backend selection, /join workflow, and modification guide
- Add Quick Start section with /join command examples (hash channels, AREDN-only, APRS)
- Document available backends (Meshtastic, MeshCore, APRS) with prerequisites
- Show UI method for binding backends to channels
- Show config method for backend binding via crow.conf.override
- Add APRS multi-backend backend selection via /join and config
- Expand backend binding section with clear workflows
- Add Modifying Existing Channels section covering in-place edits
- Enhance Features section with more context (Images, Winlink, Max Messages)
- Add Common Commands table with key slash commands
- Add Related Topics section with links to Commands, Configuration, APRS, etc.
- Improve overall structure: quick start first, UI method, then advanced config
- Update key types table with use cases and compatible networks
- Expand hash channel documentation with examples
Net effect: +218 insertions, clearer workflows from creation to configuration,
better integration with Commands.md and Configuration.md for detailed reference.
6202e8d
Streamline wiki: consolidate configuration documentation into Configuration.md
- Create new comprehensive Configuration.md covering all crow.conf.override settings:
* Meshtastic bridge, MeshCore bridge, APRS bridge (all backends)
* USB storage options with field reference table
* UI customization (message alignment, key format)
* Complete multi-feature example
* Clear restart instructions
- Update feature pages to focus on hardware/setup:
* Meshtastic.md: Remove boilerplate, add link to Configuration
* MeshCore.md: Simplify config section with Configuration reference
* UI-Tweaks.md: Link to Configuration for settings
* USB-Storage.md: Reference Configuration for detailed options
* APRS.md: Add Configuration reference intro
- Gracefully deprecate Advanced-Configuration.md:
* Add prominent redirect notice to Configuration
* Preserve page for future advanced topics
* Maintain backward compatibility
- Update _Sidebar.md:
* Add 'Configuration Reference' as top-level entry
* Rename 'Advanced configuration' to 'Advanced Topics'
Net effect: -76 lines of duplication, single source of truth for all config.
d83816a
Consolidate Strict Gatekeeper pages; rewrite LoRa Gateway Tags
- Merge Strict-Gatekeeper-Mode.md into Strict-Gatekeeper.md (delete
the -Mode page; the two pages were near-duplicates).
- Rewrite LoRa-Gateway-Tags.md to remove all dead meshcore_tnc.uc
references (those files were deleted from the repo in commit
d976fc5). New version documents meshtastic_tagged + meshcore_tagged
with explicit 'opt-in via router.uc import swap' instructions and
a 'what's not yet tagged' table for the experimental TCP backends.
- Update Home.md + _Sidebar.md links to the consolidated page.
- Add a 2026-06-18 changelog entry.
39fee4e
Add LoRa gateway tags wiki page
51104eb
Updated _Sidebar (markdown)
ab1c9d3