Repository navigation
task: integration test every node type end to end #738
Description
Parent: #737.
On real hardware: Companion, Observer, Repeater, Room Server, Sensor. Catalog offline and refreshed, overlay precedence, OKI 500 kHz entry applied and on-air, Temporary revert on a repeater.
Acceptance
- Results with evidence recorded.
Filed by MagentaHawk (session 5a8922d6).
Activity
diffwireauto commentedon Oct 1, 2026
D1 hardware checklist (owner)
Agent: MagentaHawk (session 5a8922d6). Build: the combined test binaries from
throwaway/647-combined, which contains Epics B + C (#744, #746) plus OrangeDog's #668/#702 and SageDog's #717 line, so you can test everything in flight at once.Companion / Observer (Settings > Radio):
Repeater (and Room Server, same screen):
6. Manage Repeater > Settings > Radio: the same picker. Pick a preset: freq/BW/SF/CR fill in, TX power doesn't change.
7. Check Apply temporarily (default 1440). Save. The reply snackbar is success, and the repeater replies
OK - temp params for N mins(CLI log). Use a short duration, e.g. 2, to watch it revert.8. Pick a preset with a path hash (Philly, or SoCal 3-byte) and check Apply temporarily: the note says the path hash stays pending. Save: no path hash command is sent. Uncheck and Save:
set path.hash.modegoes out.9. Unchecked Save still sends
set radio(reply: reboot to apply), as before.Sensor (if you have one):
10. Sensor contact > options > Manage Sensor: login, then the hub, then Settings shows the same radio card.
Refresh without a release: after config-profiles#3 merges, edit a value in
radio-presets/offband.jsonon main. About five minutes later, tap refresh in the app and the new value shows.Results go on this issue. Anything wrong gets fixed on the Epic branches before the end-of-chain merges.
diffwireauto commentedon Oct 2, 2026
D1 result: owner approved testing (2026-10-01)
Build: local combined
throwaway/647-combined@e1d30482(contains #74404025cb0and #7469c17f8a5). Installed on S25 FE (R3GYC01BKGZ) and Windows (C:\Apps\Offband_MeshCore).Owner, verbatim in substance: the test looks good and matches what he expected. He sees Philly, USA and the MeshCore entries. It's clean, it reads well, and the source labels are understandable. Grouping by region is an improvement. "Testing approved."
Automated evidence on the same build: analyze clean, 1087 tests pass, and the live preset test (#748) passes against config-profiles
main.MagentaHawk (session 5a8922d6)
diffwireauto commentedon Oct 2, 2026
D1 addendum: remote nodes (owner, 2026-10-01)
The owner opened the repeater Settings screen on the test build and reviewed the preset picker there. It looks good, the same as on the directly connected radio.
Not tested: applying a preset to a real repeater, room server or sensor over the mesh. That covers a normal save (
set radio), a temporary save (tempradioand its revert), andset path.hash.mode. The owner noted this gap himself. The remote command format, send order and duration limit are covered by unit tests only (test/helpers/remote_radio_commands_test.dart).MagentaHawk (session 5a8922d6)