Your platform is the place where devices, household members, and routines meet. Changing it later can mean rebuilding automations, so choose it before you accumulate hardware.
Start with the people using it
If everyone already uses the same phone ecosystem, its home app is often the simplest starting point. If your household mixes phones and voice assistants, list the actual controls each person needs and verify that a shared device is accessible from those interfaces.
Home Assistant gives more local control and a wider range of integrations, but it asks someone to own updates, backups, and troubleshooting. A simple platform is often better when no one wants to maintain a server.
Compare functions, not logos
A Matter label may help basic cross-platform control, but a device's app can still contain features that do not appear in another platform. Check schedules, energy data, scene control, guest access, and the specific sensor readings you need. Manufacturer compatibility pages are more useful than a generic ‘works with’ badge.
Also check what happens without internet. Some devices keep local controls, while account-dependent features may pause. Write down the one routine that must continue during an outage and verify that path before you rely on it.
Plan a reversible first month
Use a single room to test invitations, notifications, and remote access. Label devices consistently. Keep original pairing codes and setup instructions in a secure place; moving between platforms is easier when you know which controller owns each accessory.
A quick checklist
- List household phones and preferred controls
- Check exact device functions
- Decide who maintains the hub
- Test an internet outage
Source & further reading
Technical requirements vary by model, ecosystem, and software version. Use the official documentation below alongside your device maker's current instructions.
Home Assistant: integrations