The app half is on dev and in the next dev build. These are the checks to run on a real radio with debug logging on, reading the [RADMIN] and [CONN] lines, before it goes any further. The server's /repeater leg has to be live in the region you test in.
- Connect, open the Trace row picker, pick a repeater you administer, tap Manage. Expect the sheet, status "Not logged in", the Administrators line from the list.
- Log in with the guest password. Expect "Guest", the guest sentence, no Claim card, the Route card visible.
- Log in with the admin password, Remember on. Expect "Admin" and
Logged in as admin (fw_level=N).
- Tap "I administer this repeater". Expect
Admin proven: ACL answered with N entries, then POST /repeater claim -> HTTP 200 ok, "Claimed. Listed as ", the button now Unclaim.
- Reset route, then watch for PATH_UPDATED on the next request; the route card should fill in with names.
- Fetch neighbours (one page line in the log, "Load more (10 of N)" when the table is bigger), Load more once, then Upload. Expect the resolved/unknown toast and the upload's total to be the repeater's count, not the held count.
- Close the sheet; expect
Session released, ping controls unlocked and the ping buttons enabled again. Start Active mode and confirm Manage is disabled with "Stop the running mode first".
- Reopen the sheet, then power the radio off mid-login. Expect "The radio disconnected." and, in the log,
Aborted in-flight repeater admin command plus the session release line. Let it auto-reconnect and confirm the ping buttons come back.
- Wrong password: expect "No reply from the repeater. Check the password and try again." after the timeout (est_timeout plus 5 s), with Retry.
- If a repeater on firmware older than v1.9.0 is reachable: log in with its admin password and expect the "older than v1.9.0" sentence with no binary request in the log.
- Kill and relaunch the app: My Repeaters still lists the claim; the detail sheet says "You administer this repeater"; after connect,
Claims reconciled (connect): N.
- Offline Mode: the sheet opens and login works, but Claim, Unclaim and Upload refuse with the online-session sentence and make no request.
The app half is on dev and in the next dev build. These are the checks to run on a real radio with debug logging on, reading the
[RADMIN]and[CONN]lines, before it goes any further. The server's/repeaterleg has to be live in the region you test in.Logged in as admin (fw_level=N).Admin proven: ACL answered with N entries, thenPOST /repeater claim -> HTTP 200 ok, "Claimed. Listed as ", the button now Unclaim.Session released, ping controls unlockedand the ping buttons enabled again. Start Active mode and confirm Manage is disabled with "Stop the running mode first".Aborted in-flight repeater admin commandplus the session release line. Let it auto-reconnect and confirm the ping buttons come back.Claims reconciled (connect): N.