Story · Smart home
A Smart Home Born from Everyday Frustrations · 1 / 6

Our Smart Home Began with Inconvenience, Not New Products

From the front door to the lights and aquarium cooler, this is how I connected our home

How I connected an existing door lock to SmartThings and moved toward Zigbee after unreliable infrared remote control and a discontinued Wi-Fi plug service.

A family member called. They were standing outside the front door after their fingerprint had failed to register four times. A similar series of failures had once triggered a loud alarm, so they were worried it might happen again.

They usually unlocked the door with a fingerprint and could not immediately remember the PIN. When they called to ask me, I could not recall it on the spot either. Fortunately, I opened SmartThings on my phone and remotely unlocked the door.

That was exactly the kind of convenience I had hoped for when setting up a smart home years earlier. What lasted was not futuristic technology but a feature that solves the sort of awkward problem anyone can encounter in ordinary life.

I never intended to replace every device

Our home was not a newly built apartment where the wall-mounted video intercom and door lock worked together seamlessly. We could see visitors on the wallpad, but we could not unlock the front door from it. Someone had to walk to the entrance.

Replacing the entire door lock or rewiring the wallpad might have solved it. But I was more interested in keeping our existing hardware and adding only the missing function.

The lock supported an optional wireless communication module. I installed a compatible Zigbee module, SHP-DADT301/CN, and connected it to our existing SmartThings Station. Through the Samsung account and SmartThings app, I could then unlock the front door from elsewhere.

This also helped when friends or family reached home before I did. Instead of sharing the lock's PIN, I could open the door myself when needed.

Not every door lock supports this modification. Exact lock models, module specifications, hub compatibility, and software support all need to be checked individually. I am describing the combination I used, not guaranteeing universal compatibility.

Two failures shaped the decisions I make today

Most of my devices use Zigbee today, but that was not the starting point. The selection criteria emerged from earlier failures.

Infrared remotes: I sent a command but never knew the real state

I first used an integrated infrared (IR) remote controller to operate the television and air conditioner. From my phone outside the home, I could tell the controller to transmit the appropriate remote signal. One device controlling multiple appliances seemed wonderfully convenient.

There was one major weakness: I could see that I had pressed a button, but not whether the air conditioner received the command or whether it was actually on.

This was years ago, and I no longer remember the exact sequence. I believe I accidentally pressed the AC power button remotely. Unsure whether it had turned on, I pressed it again and assumed it must now be off. When I returned home, the air conditioner was still running.

I still do not know whether the first signal failed or the second command was not received. What matters is that I had pressed the button twice without checking the actual state even once.

That experience taught me the difference between being able to send a command and being able to confirm and control the device's current state.

Wi-Fi smart plugs: the hardware survived but the service disappeared

My first smart plug was a Wi-Fi device made by a small vendor. It depended on the manufacturer's app and cloud service.

It worked well for a while. Then the company ended its business and support for the platform stopped. The plug itself had not broken, but its remote-control function could no longer be used as before.

The service that made the hardware useful reached the end of its life first.

Since then, I have considered connection architecture and service longevity alongside price. I started looking for ways to reduce reliance on separate vendor clouds and controllers, even if that meant paying a little more.

One center instead of many separate apps

I chose SmartThings Station as a central hub. Compatible Zigbee switches, buttons, and smart plugs connected directly to SmartThings without separate manufacturer hubs. It was easier to manage lighting and other devices in one place.

This is a simplified view of the actual components and their roles:

Relationship between a phone, SmartThings Station, door lock module, switches, buttons, smart plugs and other home devices
A conceptual overview of the roles in my actual setup. It does not imply every operation runs locally.

An important qualification: Zigbee does not automatically make every product compatible or guarantee offline operation. SmartThings has cloud-dependent functionality, and appliances such as air conditioners and boilers may use their manufacturers' own integrations. My aim was to reduce the scattered control systems.

Zigbee and Z-Wave are distinct wireless protocols, not interchangeable names for the same technology. My SmartThings Station supports Zigbee but is not a direct Z-Wave hub. Check what the actual hub supports before buying a device.

What one small button by the front door changed

Once the lock was connected, I realized I could fix the wallpad inconvenience too. I placed a smart button next to the wallpad so I could unlock the front door from inside.

Now I could check who was visiting on the wallpad screen without walking to the entrance. The original wallpad stayed in place; the button supplied the missing action.

I installed another smart button near the entrance. One press switches off the home's lights, a double press turns on the living-room light, and a long press starts the robot vacuum. Grouping everyday actions into a physical button meant opening an app less often.

SituationActionResult
A visitor arrivesPress the button beside the wallpadUnlock front door
Leaving homeSingle press at entranceTurn off all lights
Entering a dark living roomDouble press at entranceTurn on living-room light
Starting cleaningLong pressStart robot vacuum

An opened front door did not always mean someone had arrived home

I originally hoped to eliminate even those button presses. If the front door opened late at night, the living-room lights would turn on. If it opened in the morning commute window, the robot vacuum would start.

It sounded plausible on paper, but our family did not follow a single schedule. A door opening did not necessarily mean somebody was arriving, and a door closing did not prove the house was empty.

I added an open/close sensor to the interior door and a motion sensor. One sequence—front door opens, followed by interior-door opening or motion—would count as an arrival and switch on the light. The reverse path—interior door opens, motion, then front door opens—would count as departure and switch off the lights.

It was logically appealing, but real movement did not reliably follow the scenario. Sensors sometimes reported events in a different order, and identical door events could mean very different things.

The most important failure was simpler: one family member leaving does not mean everyone has left. When the automation switched off every light while somebody was still in the living room, it was following its rules perfectly but inconveniencing a person.

Adding more conditions did not solve the fundamental problem. Sensors could report whether a door opened or somebody moved, but not who was moving, why, or what they intended.

I eventually removed much of that automatic arrival/departure inference. Turning on the living-room light returned to a deliberate double press. The single-press all-off and long-press vacuum functions stayed.

A smart home does not need to guess every human decision. One reliable button can be more useful than ten elaborate conditions.

Keep the light fixtures, replace the switches

Most of our lighting now uses Zigbee wall switches. I did not need to replace every fixture; I added control at the existing switch.

The best part is that family members can still operate the wall switch as usual. Automation sits quietly on top of that familiar interaction. Requiring everyone to open an app to turn on a light would create more friction, not less.

Of course, switch compatibility depends on neutral wiring, load type, and installation standards. Electrical work must prioritize safety.

Reusing the air conditioner's sensor for the aquarium cooler

In summer I worried about the aquarium warming up. I had a cooler above the tank, but switching it on and off manually was tedious.

Before buying another temperature sensor, I tried using the AC's indoor-air-temperature reading already available in SmartThings. If the room exceeded a chosen threshold, SmartThings switched on a Zigbee smart plug powering the aquarium cooler. Once the AC had cooled the room, the cooler was needed less often.

This was not accurate control of aquarium water temperature. An air-conditioner sensor measures room air, not water. Keeping aquatic animals healthy requires separate water-temperature checks and suitable safeguards. This was an example of supplementary control using an existing sensor.

I also replaced the boiler controller for remote operation, but that device uses Wi-Fi rather than Zigbee. Forcing every product onto one radio protocol would have been less practical than finding sensible ways to combine them.

Different spaces create different reasons for automation

At another living space in a darker area outside the city, I connected a CCTV person-detection event to line lighting along the floor. When the camera detected a person, the lights came on as a welcome light.

It is barely noticeable in daylight but much more valuable at night. Rather than copying all the automations from our main home, I needed to look for the moments when this particular space became inconvenient.

What remained after several years

Over time I connected quite a few devices. But device count is a poor measure of a good smart home.

When considering another product, I ask three questions: Can I verify its real state? Is it likely to remain useful if a vendor's service changes? Does it remove an inconvenience without disrupting familiar behavior?

Security must be part of the decision, especially for door locks. Protect remote-control accounts, limit access, place indoor buttons appropriately, and preserve safe manual access when automation fails. Convenience is not an excuse to compromise safety.

I started by wanting to unlock the front door remotely. That connection spread to lights and cleaning; the AC sensor began controlling an aquarium cooler; and a CCTV event became a small welcome light in another space.

A smart home was not about replacing everything with the latest device. It was about connecting what I already had and removing everyday frustrations, one at a time.

Next I want to explain how the door lock—the starting point for all these changes—was connected without replacing the wallpad.

---

Technical references

Smart homeTechnology in daily lifeSmartThingsZigbeesmart door lockssmart buttonshome automation
Connected projectsSmart Home HOMEBLOG
Practical KnowledgeVerified follow-up guides will be linked when published.
A Smart Home Born from Everyday Frustrations · 1 / 6 · View series ↗