A failed status read still gets a green box

Our developer found the whole response was being treated as true because it was non-empty. Thank you, that gave us a useful starting check.

There's your misleading green.

The replacement needs more than a test of one error. Try a valid response, a reported failure, a missing value and an unexpected shape. Failed interpretation should not turn into a cheerful default. And show when the last good value is old.

Yes, old data needs to look old.

The draft now checks the documented success field before using the data. A failed read shows current status unavailable, with any older reading labelled stale.

Can the operator tell those states apart without relying on colour?

On another dashboard, text labels fixed the colour problem but the page still refreshed the old value's timestamp; make sure that timestamp belongs to the observation, not the latest attempt to fetch it.

Useful catch. Our timestamp was page refresh time. The developer has changed it to the last successful observation, and the states have explicit text labels.

The recorded success and failure cases now display correctly, including malformed replies and stale data. The updated read-only dashboard is in use. We kept the captured examples with the SDK version.

Much better than green by accident.