meshcore-client

Commit Graph

Author	SHA1	Message	Date
Strycher	0f74050d46	feat(#93 ): render broker runtime-state + resolved-default placeholders Consume the additive OCFG_BROKERS dump fields from firmware #172/#173 (backward-compatible — absent fields read as today's enabled/disabled): - BrokerRuntimeState (`state`) + BrokerLastError (`last_error`) + a pure BrokerConfig.status mapping -> Connected / Connecting / Failed (reason) / Held (no clock\|low heap) / Enabled / Disabled; held shown neutral, not error. - Brokers list shows the real status line + colour instead of just "enabled". - Editor shows jwt_owner / iata_override resolved defaults (`jwt_owner_resolved`, `iata_resolved`) as greyed placeholders when the raw key is blank; only writes the raw key when the user enters a value (blank stays the source of truth). Sourced from the pool dump (getBrokers); getBroker's per-field GET list is unchanged pending the firmware GET-ability answer on #173. Unit-tested mapping, parsing, and backward-compat (9 tests). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	1 month ago
Strycher	8e5a83086c	feat(#89 ): verify broker enable/disable actually applied before confirming A firmware build can ACK a broker enable/disable as success without applying it (HV4; meshcore-firmware#179). The quick toggle and the editor save previously trusted the ACK and showed a success snackbar, so an ack-but-no-op looked like it worked. Both paths now SET, wait a short settle, re-read the slot, and report what the device ACTUALLY did: - applied -> confirm - notApplied -> warn "possible firmware issue"; the editor stays and re-seeds to the device's true state instead of popping a false success - unverified -> re-read failed (e.g. an enable that rebooted the device) Every device is treated identically: the UI reflects the re-read, never assuming a change took that the device didn't confirm. - BrokerConfig.classifyApply pure classifier + BrokerApplyOutcome (unit-tested) - ObserverConfigService.applySettleDelay - wired into mqtt_brokers_screen quick toggle + broker_editor_screen save - widget test for the ACK-but-not-applied path Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	1 month ago
Strycher	6cd707218d	fix(#80 ): only URL/port gate a broker enable; firmware owns the rest On-hardware feedback: JWT owner defaults to the device pubkey and IATA override is optional by definition, so gating a save on them is wrong -- they have under-the-hood firmware defaults. BrokerConfig.enableError now checks only the structural fields with no default: URL present, port in range. The JWT field checks are gone; the firmware enforces JWT completeness with its defaults, and a genuinely-bad enable surfaces the firmware's reason via the failure messaging added earlier. The editor's pre-save check and the list's quick Enable both follow. Tests updated to the new contract (a JWT broker with blank owner/audience now enables; a structurally-complete quick Enable confirms). Full suite green. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	1 month ago
Strycher	0d9dc79b91	fix(#80 ): broker enable/disable feedback + don't validate a disable On-hardware test feedback: - Long-press Enable/Disable was silent on success AND failure. It now confirms on success and, on failure, surfaces the device's reason (lastError) instead of nothing. - The client now refuses to quick-Enable a broker that can't work (incomplete required fields, e.g. JWT without audience/owner) and says why -- so it never reports "enabled" on a broker that won't run. (Firmware should reject too.) - The editor blocked a DISABLE on blank/invalid fields. Validation now gates ENABLING only -- disabling a slot with partial values is fine; it won't be active. Validation rules shared via BrokerConfig.enableError (editor pre-save + list quick-Enable). Full suite green. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	1 month ago
Strycher	1983ed94ab	feat(#64 ): observer config wire codec + models + service (logic layer) Client side of the Offband config command (CMD_OFFBAND_CONFIG 0xC0, firmware Epic F #160-#163), mirroring OffbandConfigProtocol.h + MyMesh::handleOffbandConfigCmd byte-for-byte: - models/observer_config.dart: ObserverConfig/BrokerConfig/WifiConfig/ MqttGlobalConfig/DisplayConfig, the tcp\|tls\|wss + none\|basic\|jwt enums, three-state SecretField, BrokerConfig.fromWireFields. - connector/observer_config_client.dart: pure codec -- frame builders (SET/GET/VIEW/BROKERS), parse() -> typed ConfigResponse, BrokerListDecoder (START->KV->END), supportsConfig (ver gate + 0x01 cap bit). - services/observer_config_service.dart: ChangeNotifier driving the codec over MeshCoreConnector -- send/await/parse round-trips, getBrokers stream, full-config refresh, capability gate, error/stale surfacing (SAFELANE 6). Known firmware gap flagged to RedCreek: broker enable/disable/clear have no wire path yet (configSet lacks `enabled`, VIEW allowlist blocks mutations); field SET + read work, activation/clear await a firmware F-task. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	1 month ago

5 Commits (a7fcb3e9a41c67974d4fba01cb66a53d8397c2a8)