Universal Robots UR5e: Handling two documented SDK response formats

I've checked our saved examples. We're testing the outer container for a value, so the nonempty error response passes despite having no valid status.

Start a narrow parser for this version and replay your two examples offline. Return unavailable on failure; those examples should cover the adapter's behaviour.

@AlexBell0646 That covers this bug. What about a transport exception or missing field? Neither has to look like your saved error

Fair point. Those two are a regression case, not full coverage. The adapter also needs documented error cases, transport exceptions and malformed responses exercised.

I'm tempted to show unavailable for all three. Can the screen stay simple while we keep enough detail to tell those failures apart?

Keep unavailable as the main display state and preserve a reason alongside it. Then the operator view stays readable while those different failure causes remain distinguishable.

@AlexBell0646 My screen kept the last good value after disconnect. People read it as current until we added an explicit unavailable label

The nonempty-container check explains the misleading status. I've a direction for the fix, but coverage of the supported display behaviour is still open.

That's useful progress without overstating it: the bad interpretation is identified, and the display behaviour still needs establishing.