NFC Smart Home Triggers: Home Assistant and SmartThings

Tap a sticker by your door and your lights, locks, and thermostat fall into place. That's the whole pitch behind NFC smart home automation. Home Assistant and SmartThings both support it natively, but they wire the trigger up differently — here's how to set each one up, plus what to check when a tap doesn't fire.

Quick answer

Both platforms trigger automations from a plain NFC tag, and neither needs special hardware — a $1 NFC Forum Type 2 tag like an NTAG213, 215, or 216 works for either one. Home Assistant reads the tap through its mobile app, stores the tag's unique ID in its own tag registry, and fires a tag_scanned event any automation can listen for. SmartThings does it differently: on a Samsung Galaxy phone, Modes and Routines treats "NFC tagged" as a built-in trigger, so there's no separate registry and no third-party writer needed. Setup on both follows the same shape: prepare a tag, register it, place it where the action makes sense, then test.

Step-by-step: Setting up NFC triggers in Home Assistant

Register the tag. Open the Home Assistant app, go to its NFC Tags menu, and hold your phone near a blank tag. The app reads the tag's UID and stores it in the tag registry — nothing needs to be written to the tag first.

Build the automation. Add an automation using the tag trigger platform, referencing the ID you just captured. When that tag is scanned again, the tag_scanned event fires and hands off to your defined actions — a scene, a locked door, a thermostat nudge. The event also carries which device did the scanning, so one tag by the door can run a different "arrive home" routine per person.

Pick placements. Entryway: arm away, lights off, doors locked. Nightstand: bedtime scene, alarm set, media off. Kitchen: morning routine. Prefer a different automation engine on Android? Our Tasker starter guide covers the same idea outside Home Assistant.

Step-by-step: Setting up NFC triggers in SmartThings

Use Modes and Routines, not a tag-writing app. On a supported Galaxy phone, open Modes and Routines, tap Routines, then the plus icon. Choose "If," select "NFC tagged," and program a blank tag right there. Then choose "Then" and pick the result. This keeps the tag's behavior contained to your own phone — a tag written with a general-purpose tool can fire on anyone's phone that taps it, not just yours.

Know the trade-off. It's an easier setup than Home Assistant's, but a more locked-down one — SmartThings' native trigger pairs cleanly only with Galaxy hardware and SmartThings-compatible devices. Got a mixed-phone household? Worth reading how iOS and Android handle NFC differently first.

Common problems and fixes

• Nothing happens on tap. Re-scan the tag from the app's own tag menu — if it isn't recognized as already registered, the first UID capture didn't take.
• Tag reads fine elsewhere but not here. A thick or metal phone case can block the antenna. Also confirm NFC is on in quick settings.
• A different app grabs the scan first. A tag-writing utility running in the background can intercept the tap before Home Assistant's or SmartThings' app sees it.
• Choosing a tag. An NTAG213 has plenty of memory for a trigger-only tag. Step up to an NTAG215 or 216 if you also want a fallback URL for phones without the automation app installed. Mixing in iPhones? See our iOS Shortcuts NFC triggers guide for that side.

Doing this on NFCore specifically

NFCore doesn't talk to Home Assistant or SmartThings directly. What we're good for is preparing the tag itself: read the UID, write a clean NDEF record, lock it to read-only once set — no account or cloud sync required. That leaves a tag ready for either platform's app to register as a trigger. Setting up a house full of them? Get NFCore on the App Store or Google Play and write your first tag in under a minute.

Frequently Asked Questions

Do Home Assistant and SmartThings need the same NFC tags?

No special tag is required for either platform — both read the same NFC Forum Type 2 tags, with NTAG213, 215, or 216 being the common choices. Home Assistant stores the tag's UID in its own tag registry through the mobile app; SmartThings reads the tag directly inside Modes and Routines on a Galaxy phone. The same physical tag can be registered in both if you want it to do double duty.

Can one NFC tag trigger different automations for different people?

In Home Assistant, yes — the tag_scanned event includes which device scanned the tag, so an automation can branch by who tapped it. SmartThings' Modes and Routines trigger is tied to the phone running the routine, so the same effect means creating a separate routine per person's device.

Why didn't my NFC tag trigger the automation?

Usually it's a tag that wasn't fully registered (re-scan it to confirm the UID was captured), a phone case blocking the antenna, NFC turned off in quick settings, or a competing app intercepting the scan first. Removing the case and re-scanning resolves most of these.

Is it safe to leave written NFC tags around the house?

Yes, for tags that only store a URL or trigger ID — there's nothing sensitive on them, and losing one just means someone could tap it and fire the linked scene, not access your accounts. Lock the tag to read-only after writing it so a stray tap can't overwrite the trigger by accident.