Home Assistant handles NFC tags

How-To Geek published a guide on May 24 arguing that Home Assistant handles NFC tags better than rival smart-home platforms because tag scans are built directly into its automation system. The article compared Home Assistant with platforms such as SmartThings and said Home Assistant makes NFC tags work as flexible triggers for actions around the house. Home Assistant’s own documentation shows that tags are a native integration, with a dedicated Tags panel for naming, managing and automating scans. The official mobile apps can write NFC tags, and a scan fires a tag event back to the user’s Home Assistant instance for automation handling. ### Why did How-To Geek single out Home Assistant here? How-To Geek said the difference is that Home Assistant treats NFC tags as general-purpose automation inputs instead of a narrow add-on. (howtogeek.com) The article said SmartThings supports NFC-triggered routines only through Samsung Modes & Routines and only on Samsung Galaxy phones, which it presented as a platform limit. (home-assistant.io) Home Assistant’s tag feature, by contrast, is documented as part of the platform itself. The company’s 2020 launch post described tags as “a first-class citizen” in Home Assistant, with support across core software, frontend, mobile apps and hardware. ### What actually happens when you tap a tag? Home Assistant Companion documentation says a Home Assistant NFC tag or QR code contains a URL that triggers a `tag scanned` event in Home Assistant. (howtogeek.com) Those scans are collected in the Tags panel, where users can assign friendly names and connect tags to automations. The tag-writing flow is also built into the apps. Home Assistant says the easiest way to start is to use NFC stickers or cards with the official mobile apps, write the tag once, and then scan it with a phone to trigger the associated action. (home-assistant.io) ### What can a Home Assistant NFC tag trigger? Home Assistant’s documentation says a scan can be used as an automation trigger, which means it can start any action available to the platform’s automation engine. (companion.home-assistant.io) In practice, that includes device actions, scripts, scenes and app shortcuts, depending on how the automation is configured. Community examples linked around the feature show users sending scans to dashboards, launching media actions and tying tags to room-specific tasks. (home-assistant.io) Those examples are not official product claims, but they match the platform’s documented model of using a tag scan as an event that can be routed to other services. ### Does this depend on cloud services? (home-assistant.io) Home Assistant’s setup is centered on the user’s own Home Assistant instance, and the tag mechanism is documented as a URL handled by the companion app and passed into Home Assistant. How-To Geek framed that as an advantage for physical automations because the workflows can stay inside a locally run smart-home system rather than depending on a vendor cloud routine engine. (community.home-assistant.io) The documentation does include device limits. Home Assistant says background NFC tag reading on iPhone requires iPhone XS, XR, iPhone 11 or later, while Android behavior depends on app link handling and device settings. ### Where do the setup steps and code examples live? How-To Geek’s May 24 article included setup guidance and configuration examples for readers who want to build tag-based automations. (howtogeek.com) The primary reference pages for that process are Home Assistant’s Tags integration page and the Companion documentation section covering Universal Links, NFC and QR tags. (home-assistant.io) Home Assistant’s tag documentation and companion app pages remain the main places to find the next steps, including writing a first tag, naming it in the Tags panel, and attaching the scan to an automation in the user’s instance. (home-assistant.io) (howtogeek.com)