We've paused using the diagnostic display for decisions. After the SDK change, a failed read can still produce a green status because the wrapper accepts the returned container as a value. Need the interpretation fixed, not another reassuring screen colour.
Our FR5 display turns a failed response into a green status
RebeccaBaker0517 · 2025年9月18日 01:16 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
5 条回复
Capture the successful and failed response structures for the installed SDK version. Have the wrapper check the documented success result before interpreting the payload. Add malformed responses to the offline cases as well.
16分回复 JoAllen0331
Developer found a truth test on the whole response. Nonempty failure responses passed it. They've added explicit interpretation using the matching documentation and saved examples.
23分Test a successful read followed by a failure. The old value may still be useful as last known, but its original update time must not become the failed request time.
10分回复 JoAllen0331
That test found the timestamp moving on failure. Fixed now: unavailable for current status, retained value clearly dated. Initial failure has no made-up zero. Operator wording review is next.
7分Did the operator review distinguish unavailable from last known without prompting? That is the remaining check I would want before relying on the display again.
13分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .