archy

1,892 Commits 40 Branches 143 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
archipelagoandClaude Fable 5	999a100531	feat(mesh): RF-params settings UI + expose lora_radio_params in mesh.status Demo images / Build & push demo images (push) Has been cancelled Details Device panel gets MeshCore RF fields (frequency MHz, bandwidth kHz, SF, CR) wired to mesh.configure's validated lora_radio_params; shown only for MeshCore radios, all-empty leaves the radio's flashed settings untouched. Human units in the UI, firmware field units on the wire. Per operator direction the panel's static stat rows duplicating editable fields (name, region, channel) are dropped — the editable control is the display. Stale 'adjust via a MeshCore client' hints updated: the node programs the radio now. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-07-21 06:53:10 -04:00
archipelagoandClaude Fable 5	7b36b5cc34	feat(mesh): device-detected setup modal with board images + full radio settings Plugging in a LoRa radio now pops a global two-step setup modal on any page: step 1 shows the ACTUAL detected board (25 board SVGs vendored from the Meshtastic web-flasher, GPL-3.0; matched by USB product string on native-USB boards, vid:pid heuristics for bridge chips, animated fallback otherwise); step 2 configures with Archipelago presets — the LoRa region pre-selected from the node's location (new lat/lon→region mapping), channel 'archipelago', node name, and an advanced firmware pin. Options adapt per protocol: region+channel program Meshtastic; MeshCore shows its community frequency plan (firmware owns RF); RNode defers to the Reticulum daemon config. Backend: mesh.configure now accepts lora_region (validated against the driver's region table) and device_kind (probe pin); mesh.status returns the persisted values plus per-port USB identity (sysfs vid/pid/product) for board identification. The Mesh Device tab gains a full settings form (region with duty-cycle/legality hints, firmware pin, channel, name, identity broadcast) replacing the read-only panel; the old Mesh-page-only onboarding modal is superseded by the global flow. Mock backend: stateful mesh config so the dev UI demos the full detect→configure round-trip (disable mesh → modal fires with Heltec V3). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-07-14 08:40:18 -04:00
archipelagoandClaude Sonnet 5	494f272815	feat(mesh): Device settings tab (backlog #8 ) New MeshDevicePanel.vue, added as a 4th/5th tab entry to activeTab/toolsTab/ mobileTab following the exact existing pattern (chat/bitcoin/deadman/ assistant/map). Shows firmware version, node ID, advert name, LoRa region, channel, and device type -- firmware_version/self_node_id were already server-side but never rendered; region is new (composed into MeshStatus from MeshConfig.lora_region at read time, not part of the live session state). Reboot button wired to the already-working mesh.reboot-radio RPC. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-06-30 23:03:09 -04:00

Author

SHA1

Message

Date

archipelagoandClaude Fable 5

999a100531

feat(mesh): RF-params settings UI + expose lora_radio_params in mesh.status

Demo images / Build & push demo images (push) Has been cancelled

Details

Device panel gets MeshCore RF fields (frequency MHz, bandwidth kHz, SF, CR)
wired to mesh.configure's validated lora_radio_params; shown only for
MeshCore radios, all-empty leaves the radio's flashed settings untouched.
Human units in the UI, firmware field units on the wire. Per operator
direction the panel's static stat rows duplicating editable fields (name,
region, channel) are dropped — the editable control is the display. Stale
'adjust via a MeshCore client' hints updated: the node programs the radio now.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-07-21 06:53:10 -04:00

archipelagoandClaude Fable 5

7b36b5cc34

feat(mesh): device-detected setup modal with board images + full radio settings

Plugging in a LoRa radio now pops a global two-step setup modal on any
page: step 1 shows the ACTUAL detected board (25 board SVGs vendored
from the Meshtastic web-flasher, GPL-3.0; matched by USB product string
on native-USB boards, vid:pid heuristics for bridge chips, animated
fallback otherwise); step 2 configures with Archipelago presets — the
LoRa region pre-selected from the node's location (new lat/lon→region
mapping), channel 'archipelago', node name, and an advanced firmware
pin. Options adapt per protocol: region+channel program Meshtastic;
MeshCore shows its community frequency plan (firmware owns RF); RNode
defers to the Reticulum daemon config.

Backend: mesh.configure now accepts lora_region (validated against the
driver's region table) and device_kind (probe pin); mesh.status returns
the persisted values plus per-port USB identity (sysfs vid/pid/product)
for board identification. The Mesh Device tab gains a full settings
form (region with duty-cycle/legality hints, firmware pin, channel,
name, identity broadcast) replacing the read-only panel; the old
Mesh-page-only onboarding modal is superseded by the global flow.

Mock backend: stateful mesh config so the dev UI demos the full
detect→configure round-trip (disable mesh → modal fires with Heltec V3).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-07-14 08:40:18 -04:00

archipelagoandClaude Sonnet 5

494f272815

feat(mesh): Device settings tab (backlog #8 )

New MeshDevicePanel.vue, added as a 4th/5th tab entry to activeTab/toolsTab/
mobileTab following the exact existing pattern (chat/bitcoin/deadman/
assistant/map). Shows firmware version, node ID, advert name, LoRa region,
channel, and device type -- firmware_version/self_node_id were already
server-side but never rendered; region is new (composed into MeshStatus from
MeshConfig.lora_region at read time, not part of the live session state).
Reboot button wired to the already-working mesh.reboot-radio RPC.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

2026-06-30 23:03:09 -04:00