Family friendly

One thing I think gets overlooked when building a smart home is accessibility for the whole family.

It’s very easy to get carried away with automations, sensors, dashboards, voice commands and clever routines. But if the rest of the family can’t easily use the house, then has it really become smarter?

For me, a smart home shouldn’t be built only around features. It should be built around the people living in it.

My wife and children shouldn’t need to understand Home Assistant, Matter, Thread, Zigbee or know which automation is running just to turn on a light.

Physical controls still matter.

A normal-looking wall switch that always works can be more valuable than another clever automation. The same goes for simple buttons, clear controls and making sure there is always an obvious manual way to operate something.

Automations should make everyday life easier in the background, not make the family dependent on the person who configured them.

I try to think about three things when adding anything to our smart home:

• Can everyone in the house use it without me?
• If the automation fails, can the device still be controlled normally?
• Does this genuinely make life easier, or am I adding it just because I can?

Some of my favourite smart-home setups are actually the ones nobody notices. Lights come on when needed, devices turn off automatically, reminders happen at the right time — but the normal switches and controls still work exactly as everyone expects.

That, to me, is what a smart home should be.

Not a house full of technology.

A house where technology quietly makes things easier for everyone.

I’d be interested to know how other Aqara users approach this. Do you design your smart home around maximum automation, or do you deliberately keep physical controls and family accessibility at the centre of it?

6 Likes

This is something I keep coming back to with my automations. It’s easy to understand why something happened when you wrote the automation, but everyone else just sees a light that went off when they still needed it!

One example in my setup is a Cleaner Mode. It temporarily pauses selected routines and opens the blinds so the house behaves more appropriately while someone else is using it. Working out when the normal automations shouldn’t run is as useful as deciding when they should.

I also think automatic switch-off needs more care than switch-on. I’m currently looking at FP2 zones where someone walks into an adjoining room and disappears from the sensor’s view. “No longer detected” doesn’t necessarily mean “finished using the space”.

My aim is automation for convenience, with obvious physical controls whenever someone wants something different. If I have to explain the logic before they can use the room, there’s probably more work for me to do.

3 Likes

This is something I’ve focussed more and more on recently.

Years ago first getting into smart tech i think for most if was a bulb turned on and off via a assistant speaker we all know the one.

Today when I’m building automations i want stuff to just happen. So lights coming on when in a room, lights scheduled around sunset. Outside lights turning on when external cameras spot a person, air filters turning on when air quality drops, lights coming on when you open a wardrobe going off when closed etc. This is definitely the way it should be.

1 Like

Totally agree!

1 Like

As I build out our smart home I share this philosophy to make it easy to use for our family and frequent guests. My goals are to make our home more convenient, fun, and secure for the whole family.

1 Like