Our dashboard for controller status polling on Fairino FR5 expected a status value from the old SDK. The replacement environment returns a container with extra information, and our screen now shows a plausible status even when a request fails. This is in a workshop status-monitoring station, with an inspection coupon as a reference.
I'm trying to fix how we interpret the answer
Can you compare sanitized success and failure responses against that SDK's documentation? The useful detail is which field your wrapper treats as status.
Fair point. Those two are a regression case, not full coverage. The adapter also needs documented error cases, transport exceptions and malformed responses exercised.
@RosaCarter0988 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.
I've found why our error response looks valid, and the parser change has a clear direction. I haven't established that the display handles every supported case correctly