mirror of
https://github.com/meshtastic/web.git
synced 2026-08-01 07:26:34 -04:00
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.
76 lines
2.0 KiB
Protocol Buffer
76 lines
2.0 KiB
Protocol Buffer
syntax = "proto3";
|
|
|
|
package meshtastic;
|
|
|
|
option csharp_namespace = "Meshtastic.Protobufs";
|
|
option go_package = "github.com/meshtastic/go/generated";
|
|
option java_outer_classname = "RemoteHardware";
|
|
option java_package = "org.meshtastic.proto";
|
|
option swift_prefix = "";
|
|
|
|
/*
|
|
* An example app to show off the module system. This message is used for
|
|
* REMOTE_HARDWARE_APP PortNums.
|
|
* Also provides easy remote access to any GPIO.
|
|
* In the future other remote hardware operations can be added based on user interest
|
|
* (i.e. serial output, spi/i2c input/output).
|
|
* FIXME - currently this feature is turned on by default which is dangerous
|
|
* because no security yet (beyond the channel mechanism).
|
|
* It should be off by default and then protected based on some TBD mechanism
|
|
* (a special channel once multichannel support is included?)
|
|
*/
|
|
message HardwareMessage {
|
|
/*
|
|
* TODO: REPLACE
|
|
*/
|
|
enum Type {
|
|
/*
|
|
* Unset/unused
|
|
*/
|
|
UNSET = 0;
|
|
|
|
/*
|
|
* Set gpio gpios based on gpio_mask/gpio_value
|
|
*/
|
|
WRITE_GPIOS = 1;
|
|
|
|
/*
|
|
* We are now interested in watching the gpio_mask gpios.
|
|
* If the selected gpios change, please broadcast GPIOS_CHANGED.
|
|
* Will implicitly change the gpios requested to be INPUT gpios.
|
|
*/
|
|
WATCH_GPIOS = 2;
|
|
|
|
/*
|
|
* The gpios listed in gpio_mask have changed, the new values are listed in gpio_value
|
|
*/
|
|
GPIOS_CHANGED = 3;
|
|
|
|
/*
|
|
* Read the gpios specified in gpio_mask, send back a READ_GPIOS_REPLY reply with gpio_value populated
|
|
*/
|
|
READ_GPIOS = 4;
|
|
|
|
/*
|
|
* A reply to READ_GPIOS. gpio_mask and gpio_value will be populated
|
|
*/
|
|
READ_GPIOS_REPLY = 5;
|
|
}
|
|
|
|
/*
|
|
* What type of HardwareMessage is this?
|
|
*/
|
|
Type type = 1;
|
|
|
|
/*
|
|
* What gpios are we changing. Not used for all MessageTypes, see MessageType for details
|
|
*/
|
|
uint64 gpio_mask = 2;
|
|
|
|
/*
|
|
* For gpios that were listed in gpio_mask as valid, what are the signal levels for those gpios.
|
|
* Not used for all MessageTypes, see MessageType for details
|
|
*/
|
|
uint64 gpio_value = 3;
|
|
}
|