I'm fixing our controller availability reporting dashboard for Universal Robots UR5e in a training cell with a read-only dashboard. Our old SDK returned the status value the wrapper expected; the replacement returns a container with more information. Failed requests can now look like plausible status readings.
We use a sample housing as a reference, but the problem is interpreting the response.
Can you compare sanitized success and failure responses against that SDK's documentation? The useful detail is which field your wrapper treats as status.
@AnikaBrooks0856 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.
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 can't yet trust our displayed status across the supported responses. Finding the container check explains a bug, but doesn't give me a verified replacement parser.