How We Verify
NestGrid's core claim is that every fix or compatibility verdict is personally reproduced, dated, and scoped to an exact hub and firmware/app version -- not aggregated from a forum thread. This page states what that discipline actually means and where its limits are.
The status taxonomy
The fix or compatibility claim was personally reproduced on the exact device, hub, and firmware/app version listed. A claim only earns this label after hands-on testing -- never from a report alone, no matter how many people confirm it elsewhere.
A workaround has been verified to work, but the underlying cause is not resolved. Expect to repeat the workaround after certain updates until a durable fix exists.
The issue has been reported and is being actively re-tested. No fix has been confirmed to hold yet. The pulsing indicator marks this as the one status still in motion -- check back rather than trusting an unconfirmed workaround as durable.
A “Confirmed” label is demoted back to “Investigating” the moment a later firmware, app, hub OS, or Matter/Thread update reintroduces the failure. Status is not a permanent badge -- it is a claim with visible rules.
Re-verification and sourcing boundaries
Fixes and compatibility claims are re-tested when a relevant firmware, app, hub OS, or Matter/Thread spec update ships, and a verification date is published on every record so you can judge whether a claim is current. A stale “Confirmed” label is treated as worse than no label at all.
Outage-tracking signals (broad spikes in user reports) are used only as corroborating context for how widespread an issue is -- never as a substitute for hands-on verification. On Update Watch entries, this is labeled explicitly as “impact scope,” kept visually distinct from the site's own status.
Where certification is involved, NestGrid states independently verified facts and links out to the standards bodies and platforms that actually issue certification, rather than implying it is itself a certifying authority:
Have a question about a specific record? Contact & Report feeds directly into the re-verification queue.