mirror of
https://github.com/pyMC-dev/pyMC_Repeater.git
synced 2026-08-07 01:13:11 +02:00
101681fad4
set freq and set radio stored the CLI's MHz/kHz inputs directly into radio.frequency and radio.bandwidth, which the rest of the stack treats as Hz — a freq change tuned the radio to a few hundred hertz. Convert to Hz on write and validate set radio with the firmware gate (freq 150-2500, bw 7-500, sf 5-12, cr 5-8, same error string; set freq stays unvalidated like firmware). Radio changes are now saved without a live apply so the reply's restart-to-apply contract is real: a live retune would cut off the remote admin mid-session, and the all-or-nothing live radio path would also have dragged staged frequency changes along with a tx tweak.