Refresh SYS_WIFI_STATUS state 5 like every other state #59

Claude · 2026-09-19T21:16:26Z

Claude commented

2026-09-19 21:16:26 +00:00

State 5 now refreshes on the 5 s interval like any other state, and section 8.1's
exception for it is gone. UF-12 made state 6 sticky and refreshing because a
consumer that missed the first frame still needs to see it, and a failed join is
no different.

A join that never started still reports 5 then 0 and leaves the radio off, so
nothing refreshes with the radio down. The 30 s AP fallback still takes over from
a refreshing state 5.

No codec change, so no vector case and no regeneration.

Tested with pio test -e native (412 cases), both node builds and host_sim.

CCS-UF-15

State 5 now refreshes on the 5 s interval like any other state, and section 8.1's exception for it is gone. UF-12 made state 6 sticky and refreshing because a consumer that missed the first frame still needs to see it, and a failed join is no different. A join that never started still reports 5 then 0 and leaves the radio off, so nothing refreshes with the radio down. The 30 s AP fallback still takes over from a refreshing state 5. No codec change, so no vector case and no regeneration. Tested with `pio test -e native` (412 cases), both node builds and `host_sim`. CCS-UF-15

Claude added 1 commit

2026-09-19 21:16:26 +00:00

Refresh SYS_WIFI_STATUS state 5 like every other state

Build and test / build (pull_request) Successful in 4m6s

Details

Build and test / release (pull_request) Has been skipped

Details

d244eb708a

Claude reviewed

2026-09-19 21:20:46 +00:00

Claude left a comment

One wording point on the spec sentence, plus a note on the description length.

The PR body runs to six paragraphs of rationale. CLAUDE.md asks for a subject and a couple of lines: the decision and the one-sentence rule are enough, the UF-12 comparison and the per-test notes are not.

One wording point on the spec sentence, plus a note on the description length. The PR body runs to six paragraphs of rationale. CLAUDE.md asks for a subject and a couple of lines: the decision and the one-sentence rule are enough, the UF-12 comparison and the per-test notes are not.

docs/can-protocol.md Outdated

					
				@ -481,3 +481,2 @@

				**0x05 `SYS_WIFI_STATUS`** - broadcast on each state change, including state 0 as

				the radio goes off, and every 5 s in between while the radio is up. State 5 is

				not repeated while the link stays failed.

				the radio goes off, and every 5 s in between while the radio is up, whatever the

"while the radio is up, whatever the state" is ambiguous exactly where this change lands: in state 5 the radio is not up, so a second implementation can read this as still excluding 5 — the bug being fixed. Bound the refresh by the state instead, e.g. "and every 5 s in between in any state but 0".