Ben MeadorsandGitHub
bbe9a0d5cd
* feat(protobufs): sync to firmware-current and consume workspace package Sync the vendored .proto sources to firmware-current (v2.7.25+48), regenerate the v2 TS bindings, and consume the workspace @meshtastic/protobufs (workspace:*) in place of the stale JSR 2.7.20 — finishing the monorepo migration (core was already workspace:*). Includes the one required breaking-change fix: admin nodedb_reset changed int32 to bool, so resetNodes() now sends value: true. * build(protobufs): vendor generated bindings for workspace consumers The package is consumed via workspace:* — its exports point at the TS source, which imports ./dist/meshtastic/*_pb.ts — so the generated output must exist at build time. CI builds web/core with no codegen step and the runners have no buf CLI, so the bindings are vendored here (kept gitignored; lint/format skip them). Regenerate with: pnpm --filter @meshtastic/protobufs gen * fix(protobufs): clean script removes the actual generated output dir buf writes bindings to packages/ts/dist, but clean was removing a non-existent root dist — so it never cleaned stale output. Addresses Copilot review feedback. * refactor: move web app packages/web -> apps/web Aligns the web app with the apps/web layout (matching the Vercel web-test Root Directory and the SDK-migration direction). Pure directory move plus root config: pnpm-workspace (adds apps/*), vitest projects, root tsconfig reference, and the pr/release-web/nightly workflows. vercel.json moved with the app. Build + 36 validation tests green. * feat: config fields, module pages, key verification, telemetry capture Incorporates the firmware-current feature work onto the protobuf foundation: new config fields (Display message bubbles; LoRa fem_lna_mode + serial_hal_only; Telemetry air_quality_screen_enabled); 4 new ModuleConfig pages (TrafficManagement, StatusMessage, TAK, RemoteHardware); the manual Key Verification flow (sendKeyVerification + ClientNotificationDialog stages + Verify Key button); live telemetry capture (nodeDB addDeviceMetrics) and admin hardening (toggleMutedNode, graceful PortNum default); plus the sdk-preview ConfigEditor demo and store/config tests. Build + lint + format + 131 tests green. * chore: drop #1062 (unsaved-change-detection) to match upstream revert #1062 was merged to main by accident (per @danditomaso) and is being reverted. Reverse-applied its diff here via 3-way so #1097 stays consistent with where main is headed, while keeping the feature changes layered on the same files (deviceStore/changeRegistry). Build + 131 tests + lint + format green. * fix(nodes): clean up SNR display in node table and map popup SNR is a ratio measured in dB, not dBm (which is absolute power); the node table and map popup both mislabeled it and crammed three values together: '0dBm/50%/50raw'. The trailing '%/raw' pair was the same heuristic ((snr+10)*5) shown twice — once clamped, once not. Render SNR in dB rounded to one decimal, color-coded by a 0-100% signal-quality heuristic (green/yellow/red), with the quality percentage as a muted secondary. Drop the redundant raw value. Adds unit.db; this matches the existing SNRTooltip, which already renders dB.
72 lines
3.2 KiB
JSON
72 lines
3.2 KiB
JSON
{
|
|
"page": {
|
|
"sectionLabel": "Каналы",
|
|
"channelName": "Канал: {{channelName}}",
|
|
"broadcastLabel": "Первичный",
|
|
"channelIndex": "Канал {{index}}",
|
|
"import": "Импорт",
|
|
"export": "Экспорт"
|
|
},
|
|
"validation": {
|
|
"pskInvalid": "Введите корректный PSK длиной {{bits}} бит."
|
|
},
|
|
"settings": {
|
|
"label": "Настройки канала",
|
|
"description": "Шифрование, MQTT и прочие настройки"
|
|
},
|
|
"role": {
|
|
"label": "Роль",
|
|
"description": "Телеметрия устройства отправляется по ПЕРВИЧНОМУ каналу. Допускается только один ПЕРВИЧНЫЙ канал",
|
|
"options": {
|
|
"primary": "ПЕРВИЧНЫЙ",
|
|
"disabled": "ОТКЛЮЧЕН",
|
|
"secondary": "ВТОРИЧНЫЙ"
|
|
}
|
|
},
|
|
"psk": {
|
|
"label": "Pre-Shared Key (PSK)",
|
|
"description": "Поддерживаемая длина PSK: 256 бит, 128 бит, 8 бит, пустой (0 бит)",
|
|
"generate": "Сгенерировать"
|
|
},
|
|
"name": {
|
|
"label": "Имя",
|
|
"description": "Уникальное имя канала (до 12 байт); оставьте пустым для значения по умолчанию"
|
|
},
|
|
"uplinkEnabled": {
|
|
"label": "Аплинк включён",
|
|
"description": "Отправлять сообщения из локальной mesh-сети в MQTT"
|
|
},
|
|
"downlinkEnabled": {
|
|
"label": "Даунлинк включён",
|
|
"description": "Отправлять сообщения из MQTT в локальную mesh-сеть"
|
|
},
|
|
"positionPrecision": {
|
|
"label": "Местоположение",
|
|
"description": "Точность местоположения для обмена в канале. Можно отключить.",
|
|
"options": {
|
|
"none": "Не делиться местоположением",
|
|
"precise": "Точное местоположение",
|
|
"metric_km23": "В пределах 23 километров",
|
|
"metric_km12": "В пределах 12 километров",
|
|
"metric_km5_8": "В пределах 5,8 километра",
|
|
"metric_km2_9": "В пределах 2,9 километра",
|
|
"metric_km1_5": "В пределах 1,5 километра",
|
|
"metric_m700": "В пределах 700 метров",
|
|
"metric_m350": "В пределах 350 метров",
|
|
"metric_m200": "В пределах 200 метров",
|
|
"metric_m90": "В пределах 90 метров",
|
|
"metric_m50": "В пределах 50 метров",
|
|
"imperial_mi15": "В пределах 15 миль",
|
|
"imperial_mi7_3": "В пределах 7,3 мили",
|
|
"imperial_mi3_6": "В пределах 3,6 мили",
|
|
"imperial_mi1_8": "В пределах 1,8 мили",
|
|
"imperial_mi0_9": "В пределах 0,9 мили",
|
|
"imperial_mi0_5": "В пределах 0,5 мили",
|
|
"imperial_mi0_2": "В пределах 0,2 мили",
|
|
"imperial_ft600": "В пределах 600 футов",
|
|
"imperial_ft300": "В пределах 300 футов",
|
|
"imperial_ft150": "В пределах 150 футов"
|
|
}
|
|
}
|
|
}
|