Device identity
Device model, manufacturer, model number, and region if the behavior differs by market.
Correction Intake Console Source leads, compatibility caveats, and future public correction flow
Intake preparing
Contact
Send source leads that can become better compatibility answers.
The best correction includes a product model, ecosystem, firmware or app version, region if relevant, and a source URL. Public correction intake is being prepared internally.
Best lead Source URL Official docs, support pages, release notes, or clear reports Device detail Model Brand, model, model number, and region when relevant Context Ecosystem Apple Home, Google Home, Alexa, SmartThings, Home Assistant Review state Pending Corrections need fact check before publication
Correction packet
What a useful compatibility correction includes.
A correction is easiest to verify when it includes identity, environment, source, and timing.
Ecosystem and feature
The smart-home platform and the specific control or behavior involved.
Evidence link
Official source, support page, release note, or a reproducible community thread.
Date observed
When the behavior was observed or when the source was last checked.
After intake
Source leads enter the same review route as research rows.
A submitted lead does not immediately become public guidance. It first has to be triaged, sourced, checked, caveated, and approved for publication.
- Triage source and device identity
- Cross-check source against current docs
- Map affected ecosystem and feature
- Write caveat with date checked
- Legal and editorial review
- Publish only if review passes