Skip to content

fix: distinguish unsupported device providers (DEVDB-475) - #759

Merged
sybohy merged 1 commit into
prototype/devdb-mobile-comparisonfrom
fix/devdb-unsupported-providers
Oct 30, 2026
Merged

sybohy merged 1 commit into
prototype/devdb-mobile-comparisonfrom
fix/devdb-unsupported-providers

Conversation

@sybohy

@sybohy sybohy commented Oct 30, 2026

Copy link
Copy Markdown
Member

Salto Homelok was displayed between supported providers even though its Seam integrations are marked inquire or unavailable. In the DeviceDB design preview, providers without a stable or beta integration now appear last, with a neutral “Not supported” badge and a “Request Integration →” link to the marketing request form.

Use current provider integration metadata when available, falling back to fresh capability support levels. Missing, null, stale, or connectivity-only device data remains unconfirmed rather than being labeled unsupported. Supported provider tables and requirements retain their existing behavior.

Validation: TypeScript, ESLint, Prettier, and 46 unit tests pass. Actual browser checks cover all three variants, list/matrix views, desktop and phone, light/dark themes, widths down to 320px, and August/Nuki regressions. Clicked the request link and verified the real marketing form loads without submitting it. No browser errors; Ecosystem requests returned 200/304.

Targets the existing preview branch; the overall design draft #755 stays open.

Closes DEVDB-475

@sybohy
sybohy requested review from dawnho and razor-x as code owners October 30, 2026 16:15
@sybohy
sybohy merged commit d744aa4 into prototype/devdb-mobile-comparison Oct 30, 2026
13 checks passed
@sybohy
sybohy deleted the fix/devdb-unsupported-providers branch October 30, 2026 16:20

This branch was successfully deployed

1 active deployment
Preview — f4bd58fb Deployed Oct 30, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant