Start here: how to build a local-first smart home

A good local-first smart home is not defined by ideology. It is defined by what still works when the cloud is flaky, what integrates cleanly, and what you can live with for years without hating it.

This site leans hard toward:

• strong Home Assistant compatibility
• honest coverage of Apple Home, Google Home, Alexa, Matter, Thread, Zigbee, and Z-Wave
• devices that are reliable enough for normal households
• gear that avoids unnecessary cloud dependence

The simplest framework

When evaluating any device, ask:

1. Does it work locally?
2. Does it work well with Home Assistant?
3. Does it still behave reasonably with major ecosystems?
4. What breaks if the internet dies?
5. Is the setup stable or just technically possible?

The three mistakes most people make

1. Buying for badges instead of actual compatibility

“Works with” is often weaker than it sounds. A device can technically connect to a platform while missing the features that actually matter.

2. Underestimating cloud dependence

A lot of smart home products feel fine until an API changes, a company adds friction, or the internet is down.

3. Mixing too many protocols and apps too early

A local-first setup usually gets easier when you pick a clean center of gravity. For most readers here, that center is Home Assistant.

A sane beginner stack

For most homes, the safest starting point looks like:

• Home Assistant as the control layer
• Zigbee for many sensors and battery devices
• local cameras with RTSP / ONVIF when possible
• smart plugs, relays, and switches with strong local integrations
• Matter and Thread only when the product is genuinely mature

What this site is for

This site is for people who want a smart home that is:

• practical
• local-first where it matters
• privacy-aware without becoming annoying
• still compatible with the broader smart home world

If that sounds like you, start with the guides and buying pages rather than trying to solve everything at once.