ClaraAdams0089 · 20 Apr 2026, 13:56 UTC
What does your parser use as the status now? Compare the installed SDK's documented reply with a successful read and a failure, rather than guessing from one green example.
18 pointsIt tests whether the returned container is nonempty. That's embarrassingly literal.
11 pointsNonempty failure, then, so your dashboard is successfully detecting that it received some stuff
23 pointsHave the maintainer separate request success from the returned status value. Confirm the field meanings against that installed version before changing the display mapping.
0 pointsMaintainer has the matching documentation now. Failure bypasses the status mapping in the revised parser.
22 pointsWhat does the screen show instead, because a parser fix can still leave yesterday's reassuring colour sitting there?
6 pointsI'd remove the current-status claim on failure. Keep the last successful reading separately if somebody genuinely needs it, with its age visible.
6 pointsLiam, I'd keep it for diagnosis, otherwise every broken read erases the clue you were looking at just before it broke
11 pointsSeparately was the important bit. I don't want the old value wearing the current green label.
9 pointsHassan, the saved diagnostic history can retain it even if the live tile is unavailable. Those are different display choices; neither needs to discard the previous successful reply.
5 pointsWe're using an unavailable live tile and a separate last-success line with time. History remains intact.
10 pointsTry the screen with updates stopping entirely too, not only a tidy failure reply reaching the parser.
6 pointsThat exposed a second bug: the age display only refreshed when replies arrived.
4 pointsAh. The clock that stops with the news.
22 pointsDid the maintainer add an independent freshness check? Also try a failure before any successful read, so there isn't always an old value to display.
14 pointsYes. Freshness now advances independently, and startup failure says no successful reading rather than showing a default status.
13 pointsInclude an unexpected reply shape in the parser tests. It should not fall through to a plausible status while you wait for someone to explain the changed contract.
15 pointsTests passed for success then failure, startup failure, stopped updates and unexpected shape. We also tested recovery: a new successful reply restores the live value and updates its time. The failed or stale tile stays unavailable until then. Thanks, Lin; stopping updates found the bit our parser tests missed.
6 pointsGood, and the next person looking at the training screen won't have to guess whether its cheerful answer is still alive.
19 pointsBy creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.