Why does a failed UR5e read still show healthy?

Developer found it tests whether the whole response is non-empty. Even the error response passes.

That would explain it. Ask them to check documented success before reading the status payload, and keep the failed example for a regression test. An empty response needs a case too.

What happens to the last good value on the screen? Our stock display once kept an old number perfectly legible through a failed refresh, and everyone assumed it was current because nothing looked different.

Ours keeps it green. So that's two changes needed.

Draft now says current status unavailable. Last reading has its own age beside it. Developer is testing missing fields and unexpected shapes as well.

Can the display tell a valid negative status from a failed request? Those could both become false in a simple wrapper, but the operator needs different information for them.

Please try it from the other side of the bench. We had a screen whose stale-data warning was technically present, in tiny grey text under a huge green value. Lovely in the screenshot, useless where people stood.

Fair point. Warning is now beside the value, same readable size. Valid negative and failed request display differently.

Keep the words too; changing green to another colour isn't much of an explanation.

Have you captured the version and response examples with the wrapper change? I don't want the next laptop rebuild to put you through this again because the working assumption lived only in the developer's head.

Yes. Offline cases pass. Waiting for the agreed read-only checks on the bench before release.

Good, let us know how the screen reads in use. I'm particularly interested in that old value after a failed refresh.