HOME TECHCOMPATIBILITY

Contact

Send source leads that make an answer better

The most useful correction names the product model, the platform, the firmware or app version, the country if it matters, and a source link.

Illustration

What a useful correction includes

Four things make a tip quick to check.

  • Device identity

    Model, maker, model number, and the country if the device behaves differently there.

  • Platform and feature

    The smart-home platform and the specific control or behavior involved.

  • Evidence link

    An official page, support document, release note, or a forum thread others can repeat.

  • Date observed

    When you saw the behavior, or when the source page was last checked.

What happens after intake

A tip does not become public guidance on arrival. It is sorted, checked against current documentation, matched to the platform and feature it affects, given a dated note on the limits, reviewed for wording and policy, and published only if it passes.

Device: [brand + model]
Ecosystem: [Apple Home / Google Home / Amazon Alexa / SmartThings / Home Assistant]
Source URL: 
What I observed: 
Date observed:
Policy details

Correction packet

What a useful compatibility correction includes.

A correction is easiest to verify when it includes identity, environment, source, and timing.

01

Device identity

Device model, manufacturer, model number, and region if the behavior differs by market.

02

Ecosystem and feature

The smart-home platform and the specific control or behavior involved.

03

Evidence link

Official source, support page, release note, or a reproducible community thread.

04

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.

  1. Triage source and device identity
  2. Cross-check source against current docs
  3. Map affected ecosystem and feature
  4. Write caveat with date checked
  5. Editorial and policy check
  6. Publish only if review passes