Integrating Flipper Zero with Home Assistant: Sub-GHz and NFC Triggers for Smart Home Automation

The Flipper Zero's Sub-GHz and NFC capabilities — reading and replaying RF signals, scanning tags, cloning remotes — are covered extensively elsewhere on this site as standalone skills. This guide covers a different question: how to make those captured signals actually trigger something in a smart home running Home Assistant, so a captured garage remote signal, a doorbell button press, or an NFC tag tap on your way out the door can flip a scene, arm an alarm, or toggle a light, not just replay on-demand from the Flipper's own screen.

Two Integration Paths

Flipper Zero has no native network connectivity of its own — no WiFi or Ethernet on the base unit — so getting its captures into Home Assistant always routes through an intermediary. There are two practical approaches, and they suit different use cases:

ApproachHow It WorksBest For CLI bridge via USB/serialA script on a Raspberry Pi or always-on computer talks to the Flipper over its CLI serial interface, watches for specific events, and publishes them to MQTT for Home Assistant to consumeTethered setups where the Flipper stays connected to a Pi or hub full-time, such as a fixed Sub-GHz monitoring station Custom FAP app + WiFi Dev BoardA Flipper app built with ufbt (covered in this site's custom app development content) uses the WiFi Devboard add-on to publish directly to MQTT without a tethered host computerPortable setups where the Flipper needs to trigger automations while not physically connected to anything

Building the MQTT Bridge (CLI Approach)

This path reuses the same CLI-over-USB foundation already covered in this site's Flipper CLI content, extended with a small Python bridge script:

Confirm serial CLI access to the Flipper works first — screen /dev/ttyACM0 115200 (or the equivalent on your OS) should drop you into the Flipper's command prompt.
Install an MQTT broker if Home Assistant doesn't already have one — Mosquitto as a Home Assistant add-on is the standard choice and is a few clicks from the Home Assistant add-on store.
Write a bridge script on the Pi or host computer that opens the Flipper's serial CLI, issues a subghz rx or nfc command in listening mode, parses the output for a signal match, and publishes an MQTT message when it sees one — for example, mosquitto_pub -t flipper/subghz/garage -m "detected" triggered from the parsing script whenever a known signal's hash appears in the CLI output.
Run the bridge as a systemd service so it restarts automatically after a reboot or a Flipper disconnect/reconnect event, the same reliability pattern used for any other always-on Pi service on this site.

Wiring MQTT Into Home Assistant

With the MQTT integration enabled in Home Assistant and pointed at your broker, create an MQTT binary sensor or trigger that listens on the topic your bridge script publishes to — flipper/subghz/garage in the example above.
Build an automation with that MQTT topic as the trigger and whatever action makes sense — toggling a scene, sending a notification, arming/disarming an alarm helper entity, or logging the event to a history log for review.
For NFC-based triggers (an NFC tag by the door that arms "away mode" when tapped), the same pattern applies: the bridge script watches for a specific tag UID in the CLI's NFC read output and publishes a distinct MQTT topic per known tag, so different tags can trigger different automations.

A Concrete Example: NFC "Leaving Home" Trigger

A common, genuinely useful pattern: place a passive NFC tag (a blank NTAG215 sticker, cheap and available in bulk) by the front door. Tapping the Flipper against it on your way out reads a known UID, the bridge script recognizes that UID and publishes to flipper/nfc/leaving, and a Home Assistant automation on that topic runs an "Away Mode" scene — locking smart locks, lowering the thermostat, arming Frigate's camera-based motion detection (already covered on this site for Pi-based security setups), and turning off lights. This is a nice complement to phone-presence-based automations since it works as a deliberate, explicit action rather than relying on geofencing, which can be slow or unreliable to trigger.

Sub-GHz Considerations: Read-Only vs. Replay Automations

It's worth being deliberate about which direction the automation runs. Using the Flipper to read a signal and trigger a Home Assistant automation (the pattern above) is straightforward and low-risk. Using Home Assistant to command the Flipper to transmit a stored Sub-GHz signal — for example, having a Home Assistant automation trigger the Flipper to replay a captured garage door signal — is a different and more sensitive capability, since it turns a home automation platform into something that can key an RF transmitter. If you build this direction, be especially careful about which signals get stored and whether they're rolling-code protected (most modern garage and gate systems are, which meaningfully limits replay usefulness anyway) — the legal and technical considerations already covered in this site's Sub-GHz replay and "Flipper Zero and the Law" content apply just as much when the trigger comes from an automation platform instead of your own hand on the Flipper.

Reliability Notes

USB serial connections drop occasionally, especially if the Flipper goes to sleep or its USB connection is disturbed — build reconnect logic into the bridge script rather than assuming the serial handle stays valid indefinitely.
The WiFi Devboard path avoids the tethering problem entirely but requires writing and maintaining a custom FAP app, a meaningfully bigger lift than a CLI bridge script — start with the CLI bridge approach to validate the automation logic works the way you want before investing in a standalone app.
Keep the bridge script's parsing narrow and specific. Matching on exact known signal hashes or NFC UIDs, rather than triggering on any detected signal, avoids false triggers from neighboring RF traffic or unrelated NFC taps in the environment.

This pattern — Flipper as a sensor input, MQTT as the transport, Home Assistant as the automation brain — reuses infrastructure many makers already have running for ESP32 sensor networks and other MQTT-based projects on this site, and it's a natural extension once the Flipper's Sub-GHz and NFC skills are solid on their own.

Related Guides

Loading_