The siren cannot help you. The footage can

Most people picture home security as an alarm going off loudly. In the moment, that alarm does very little. The real problem shows up afterwards: something is missing and you have no idea when it went missing; your child says somebody rang the doorbell and you do not know what time or who; the patio door was open in the night and you have no memory of it at all.

The value of security is whether you can reconstruct a stretch of time. If you can, the incident is closed. If you cannot, all you are left with is guessing and unease.

Three things have to be chained together

First, the recording. Footage is evidence, and it has to include the seconds before the trigger, because the decisive movement usually happens before any sensor reacts. Second, the timestamp burned into every frame. Without a time, a clip is just a clip and cannot be matched to anything. Third, the notification, delivered right then, with a still image attached, so you can judge it without opening a single app.

None of the three is hard on its own. Chaining them is the hard part. Recording lives in one place, alerts in another, the clocks do not agree, and you end up stitching the story together by hand. The chain below turns all three into one action.

What one real trigger looked like

The chart above is in seconds. Here is the same thing as one real night.

1. 02:14:06

   The patio door swings open

   The door contact flips from closed to open. Nobody in the house is awake and nobody is in the living room.

2. 02:14:07

   The camera starts saving

   The file reaches ten seconds further back, so the moment the curtain first moved is inside it too.

3. 02:14:07

   Living room lights to full

   The lights are not there to scare anyone. They are there so the footage is usable. Night vision is fine, but it never beats a lit room.

4. 02:14:08

   Your phone buzzes

   The message reads "living room patio door opened at 02:14" with a still image underneath. One glance from bed and you know what you are dealing with.

5. 02:14:20

   You can see it clearly

   The wind caught a door that had not latched properly and the whole curtain lifted. Nobody came in.

6. 02:15:36

   It stands down on its own

   Ninety seconds with no further movement, so the lights fade back to where they were and the recording runs thirty more seconds before closing. You never had to get up.

7. Next morning

   The clip is still there

   You open the file and the time is written right on it. The latch on that door is loose, and it has been swinging every night this week. You would never have found that out.

The point is not the notification at two seconds. It is the next morning. With footage and a time, a vague uneasy feeling turns into something you can actually go and fix.

False alarms are why people switch security off

Almost everyone who installs a security setup and then disables it gives the same reason: it was too noisy. Woken three times in a night, twice by the cat and once by the robot vacuum, and by day four the whole rule is off. And then the one night you need it, it is not running.

So false alarms are not a minor annoyance. They decide whether the system survives at all. The good news is that a home only has a handful of false-alarm sources, and each one has a fix.

What you need to have

Home Assistant treats every device in the house as an "entity", something the system can read or control. The brand and model are irrelevant. What matters is which class it falls into.

How the system works

There are only three roles here: a few things that detect, one thing that decides and directs, and a few things that leave a record. The deciding part is not something you write yourself.

Use the blueprint that already exists

The hub ships with a tested set of automation blueprints. Think of a blueprint as a fill-in-the-blanks form: the boxes are already drawn, you only supply the content. The lead role here is binary_sensor_trigger_things, which exists precisely to run a list of actions in order the moment a sensor reacts.

Fill those five boxes and recording and lighting are handled. The message itself goes to a second blueprint, entity_state_trigger_notify, which is better at wording alerts and can carry the time and the snapshot along with them.

Different homes, different settings

The above is the general shape. If any of these describe your home, adjust accordingly.

Four things it takes care of

Two more you can add

One rule is enough on its own. These two are optional. Add whichever you want.

You do not have to set this up yourself

The WOOWTECH hub ships with HA-MCP, so an assistant can connect straight into your system, do the work, then test it once and confirm it really runs before reporting back. You never touch a settings box.

Prompts you can copy straight out

Each block below can be copied whole with the button on the right. Pick the one closest to what you want. You do not need all five.

Set up security in my living room.
When the patio door opens, or motion is detected in the living room, start
recording on the camera, bring the living room lights up, and send me a
message with a snapshot. No siren for now.

Set up living room security for me using the existing blueprints. Do not
write custom code.
Trigger on the patio door contact and the living room motion sensor.
Only arm it when everybody is out. If somebody is home, leave us alone.
On trigger: start recording immediately and include ten seconds of footage
from before the trigger; bring the living room lights to full; within two
seconds push a message to my phone carrying a snapshot and the time.
Keep recording for thirty seconds past the end of the event, and do not
repeat the alert for the same event within ninety seconds.
Pause the whole rule while the robot vacuum is running.
Also add a nightly check at 23:00 for the camera and sensors going offline.
When it is built, test it once yourself, confirm it really works, then tell
me which devices you used.

I have a cat, and the living room motion sensor keeps picking her up.
Change it so both have to agree: the patio door contact has to open first,
and the living room has to detect somebody within ten seconds after that,
before it records, lights up or alerts me.
When the motion sensor reacts on its own, just record quietly. No lights,
no message.

That living room security rule is alerting me too much.
Change it to alert me at most once every three minutes for the same event.
Also stop turning the lights on outside 23:00 to 06:00 — just record
quietly during the day.
Leave everything else alone.

There was an alert from the living room on my phone this morning and the snapshot
is right there, but when I went looking for the full clip afterwards the file was gone.
The message side clearly worked, so detection and notification are both fine.
I only want you to follow the recording and storage side: whether the camera really
started recording once it was told to, where what it recorded ended up,
and how long it survives before something newer overwrites it.
Once you know, fill in the missing piece, then trigger it once
so I can open the clip straight from the message.

Common questions