Who this guide helps
People expanding an existing system
The short answer
Record exact model, firmware, transport and controller requirements. Brand compatibility lists can vary by product generation and software version.
Practical workflow
List current devices, controllers, hubs, bridges and network components from verified documentation. Separate Wi-Fi, Thread, Bluetooth and other connectivity from application-level compatibility. Ask which controller features are actually supported and whether a bridge is required. Mark unknown details for the vendor.
What a useful handoff looks like
Compare the proposed device against current official specifications and test the intended function where feasible. Keep the inventory dated and note updates that change behavior. The result should identify dependencies rather than announce that everything works together.
Mistakes to avoid
Do not equate a radio type with feature compatibility or infer support from a similar model. Product-specific documentation remains essential.
Working example: fields to record
| Field | Illustrative entry — replace with your own facts |
|---|---|
| Device identity | Model and firmware |
| Dependency | Required controller or bridge |
| Unknown feature | Vendor confirmation pending |
Add your own entries; the example is illustrative. Keep sensitive information private.
Sources & further checks
Official references are starting points for further checks, not approval of a specific case, product or project.
Editorial note
AI-assisted editorial guidance; not expert certification.
Original editorial guidance. Examples are illustrative, not client cases, measured outcomes or promised services.
Legal and health-related decisions require appropriately qualified local professionals. This site is an independent editorial resource, not a law firm or medical provider.