Our dashboard for controller availability reporting 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 bench integration setup, with a fixture block as a reference.
I'm trying to fix how we interpret the answer
@AmyBrooks0815 Can you compare sanitized success and failure responses against that SDK's documentation? The useful detail is which field your wrapper treats as status.
@AmyBrooks0815 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.
@LuisBennett0782 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've got an answer to the design question: parse the documented status for the identified SDK and keep failures unavailable. I'll call the display fix complete only when our offline examples show that behaviour on screen