Our FR5 teaching dashboard was written around the old SDK response. The replacement environment returns a different container, and the wrapper treats a failed read as a usable status. I warned someone else about this recently and have now found it in my own example. The display needs explicit failure handling, not another convenient default.
The new FR5 response makes our error screen look healthy
ElliotChan1118 · 10 Jun 2025, 12:23 UTC
2 replies
Replying to ElliotChan1118
Does it keep the last successful reading after that failure? I'd want the age visible too, otherwise fixing the parser could still leave the operator staring at yesterday's good news.
6pointsReplying to JasperAbbott0029
It does. We have added a test with a successful read followed by failure, alongside tests for each documented response form. The revised display marks the retained value stale. Classroom review is still pending.
17pointsDiscussion closed
This discussion is closed to new replies after six months without activity. Last activity: .