fr10 wrapper reads a failed response as availability

SarahBarnes0589 · 4 Mar 2026, 12:15 UTC

Reply to discussion
SA
SarahBarnes0589
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.

12 replies

LU
LuisAli0260
Replying to SarahBarnes0589

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 points
SA
SarahBarnes0589
Replying to 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 points
IM
ImranAdams0131
Replying to SarahBarnes0589

Our old mock made every request successful. Include unsuccessful replies, missing readings and timeouts in this one, not only the two happy formats

14 points
DA
DavidBennett0780
Replying to SarahBarnes0589

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 points
SA
SarahBarnes0589
Replying to DavidBennett0780

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 points
OS
OscarAbbott0010
Replying to SarahBarnes0589

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 points
LU
LuisAli0260
Replying to OscarAbbott0010

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 points
SA
SarahBarnes0589
Replying to 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 points
DA
DavidBennett0780
Replying to SarahBarnes0589

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 points
SA
SarahBarnes0589
Replying to DavidBennett0780

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 points
IM
ImranAdams0131
Replying to SarahBarnes0589

Keep that export case in the regression checks. Easy to forget when the next change only looks cosmetic

21 points
SA
SarahBarnes0589
Replying to ImranAdams0131

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 points

Add to the discussion

Welcome to Application Robot

Everyone can read the forum. Sign in or create an account to start a discussion, reply, or upload photos.

Forgot your password?

By creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.