mirror of
https://github.com/ALLFATHER-BV/wadamesh.git
synced 2026-10-15 06:09:58 +00:00
MeshCore's airtime_factor is the Dispatcher's TX pacing multiplier: duty = 1/(1+af), so a 10% duty limit needs af = 9. The presets wrote af = pct/100 (0.10), which configured every preset user's radio to ~91% duty -- the Home meter's 'always 91%' was truthfully reporting the misconfiguration, on every region preset including UK/EU. - applyMeshRadioPresetFields converts duty% -> factor correctly (clamped to the core's 0..9). - findMatchingMeshRadioPreset accepts both the correct and the old buggy value so previously-configured devices still show their preset in the dropdown. - healPresetAirtimeFactor (run once at UI begin) rewrites the factor for devices whose params exactly match a preset and whose stored factor matches the OLD buggy write -- the exact-match requirement is the guard against touching deliberate user-set values. NOTE for the web client: Meshcomod-client/shared/radio_presets.ts documents the same pct/100 convention and needs the matching fix. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>