Skip to content

task: Offband overlay preset file + schema in config-profiles #722

Closed

Description

@diffwireauto

Parent: #721.

Add the overlay file and document its schema in SCHEMA.md.

Entry shape follows Liam's (title, frequency, bandwidth, spreading_factor, coding_rate, optional network_settings.path_hash_size in bytes), plus id, region, optional tx_power.

Initial entries, i.e. what Liam's list lacks: OKI-Mesh 500kHz Test (909.75 / 500 / SF10 / CR5, TX 20, #661), USA Philly (902.25 / 500 / SF11 / CR5), the 26 Russia city presets, USA Arizona, and Off-Grid 433/869/918.

Owner pick needed: Arizona is SF10/CR5 in ours and SF9/CR8 in zjs81's latest.

Acceptance

  • File + schema committed in config-profiles.
  • Every entry validates.
  • No entry duplicates one in Liam's list unless it's a deliberate override, marked as such.

Filed by MagentaHawk (session 5a8922d6).

Activity

  1. diffwireauto commented on Oct 1, 2026

    @diffwireauto
    MemberAuthor

    Owner decisions, 2026-10-01:

    1. task: add the OKI-Mesh 500kHz Test preset entry #661 is folded into this task. The OKI-Mesh 500kHz Test entry lives in the overlay file, not hardcoded in the app. The stopgap code was never committed and is discarded.
    2. Values change, so the overlay must be editable without an app release.
      • Philly has changed its frequency since the 902.25 value in zjs81's code. The current Philly values must be confirmed from Philly Mesh at build time, not copied from zjs81 or older notes.
      • OKI hasn't settled on a frequency. 909.75 / 500 / SF10 / CR5 was a test.

    Added acceptance:

    • Changing an entry in the overlay file in config-profiles (a commit, nothing else) reaches users' apps on their next preset refresh, with no app code change and no version bump. This is proven end to end in A4 / B6.
    • The schema documents how to add, change and retire an entry, so an owner edit is a small JSON change.

    Agent: MagentaHawk (session 5a8922d6)

  2. diffwireauto commented on Oct 1, 2026

    @diffwireauto
    MemberAuthor

    Arizona preset: which values, by what source (research 2026-10-01)

    Agent: MagentaHawk (session 5a8922d6). Owner decided on 2026-10-01 that the overlay home is OffbandMesh/config-profiles.

    No authoritative Arizona source found. Both values in circulation are unsourced or secondhand:

    Value Where it comes from Strength
    908.205 / 62.5 / SF10 / CR5 (ours) zjs81 947fafbb (2026-02-17) added "USA Arizona" with no cited source. It was not in the zjs81#72 table. CR5 is the blanket "all CR 5" default from #72. Unsourced
    908.205 / 62.5 / SF9 / CR8 (zjs81 now) zjs81#507 (2026-07-27, user Samschurn): "Spread factor should be 9 and the coding rate should be 4/8 ... alignment with what Tucson and the greater Phoenix area have setup". The poster also says they are "fairly new to core". zjs81 applied it (736eb064, 2026-08-09) and closed the issue 2026-08-12 with "This is fixed". No link to an Arizona community. One local user's report, accepted by zjs81

    Checked and empty:

    • Liam's registry has no Arizona entry.
    • RegionMesh Tucson/Phoenix pages give no parameters.
    • The myGMRS Arizona thread is about Meshtastic, a different network.
    • The LetsMesh analyzer is a live packet feed with no per-region settings (a search-engine summary claiming it showed 908.205/SF9 was not borne out).

    Leaning, not settled: SF9/CR8 has the only Arizona-specific claim behind it and is newer. Confirming it needs an Arizona MeshCore operator or community post (Tucson / Phoenix). Because the overlay is editable without an app release (owner requirement, above), whichever value ships can be corrected by a one-line JSON commit.

  3. diffwireauto commented on Oct 1, 2026

    @diffwireauto
    MemberAuthor

    Owner decision, 2026-10-01: ship USA Arizona = 908.205 / 62.5 / SF9 / CR8 in the overlay (source: zjs81#507 local report, applied by zjs81 736eb064). It's unconfirmed by an Arizona authority; the owner will correct it later if needed, via a one-line overlay edit with no app release.

    Agent: MagentaHawk (session 5a8922d6)

  4. diffwireauto commented on Oct 1, 2026

    @diffwireauto
    MemberAuthor

    Starting. Agent: MagentaHawk (session 5a8922d6). Philly current values confirmed from phillymesh.net (2026-10-01): 919.500 / 500 / SF10 / CR5 / path hash 2 bytes (replaces their original 902.25 guidance).

  5. diffwireauto commented on Oct 1, 2026

    @diffwireauto
    MemberAuthor

    Landed on config-profiles \ eat/721-preset-sources\ as 8d8be74 (overlay with Arizona, Philly 919.500/500/SF10/CR5/2B, OKI test, 27 Russia, 3 Off-Grid; validator; SCHEMA.md). Validator rejects bad values, string numbers, unknown keys, and unmarked title clashes with upstream. Merges with Epic A's PR.

  6. added a commit that references this issue on Oct 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions