Our replacement SDK returns a documented container rather than the old status value. The dashboard wrapper accepts the container as if it were a reading, so failed requests can look plausible. I need both supported formats handled without a failure turning into a normal status.
fr10 wrapper reads a failed response as availability
SarahBarnes0589 · 2026年3月4日 12:15 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
12 条回复
Decode against the identified supported version and its documented success and failure forms, then give the display one consistent internal result; guessing success from a nonempty container is the bit to remove first
14分回复 LuisAli0260
Developer has the documentation for both supported versions and representative retained replies. The new path checks the documented outcome before extracting a reading. Unknown shapes stay errors.
13分Our old mock made every request successful. Include unsuccessful replies, missing readings and timeouts in this one, not only the two happy formats
14分Show the operator a failed current read separately from the last valid reading, with its age. Otherwise the parser can be fixed while the screen still looks reassuringly current whenever communication fails.
-4分We added separate current-read status and last-valid age. The first test exposed an old default value appearing before any successful read. That now shows unavailable, not a pretend previous reading.
14分Does changing to another controller clear that last-valid value? A previous device's reading would be even more misleading than an old reading from the same one.
15分Tie the retained reading to its source identity and session, Sarah, so changing the source cannot borrow the old value just because the display window stayed open
20分回复 LuisAli0260
Source-change test now starts without a reading and retains the previous source only in history. Both supported formats pass success, failure, timeout and missing-reading checks offline.
15分Has anyone checked the exported report? The display labels and parser may be right while the file still writes the last value into a current-status column.
0分Export had exactly that ambiguity. We split current request outcome from last valid value and observation time, with source identity included. The same failed-read case now agrees on screen and in the report.
4分Keep that export case in the regression checks. Easy to forget when the next change only looks cosmetic
21分Installed read-only comparison completed in both supported environments. Expected controller identity, valid readings and failed-read display/report behaviour checked. Ordinary close and reopen also starts without an invented value. Wrapper change closed.
2分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .