How to Set Up Flood Warning Alerts on Your Smart Home Hub
A dated, status-labeled setup guide for flood and leak warning alerts across Apple Home, Google Home, Alexa, Home Assistant, and app-based sensors — with each ecosystem's alert-path quirks and the sensor-buying calls to make before you commit.
This guide is about in-home water leak and flood alerts from smart sensors, hubs, apps, and routines: the message you need when a probe under the sink gets wet. If you meant outdoor weather flood warnings, river gauges, or NWS-style alerting, start with the separate smart home flood alarm setup guide instead. For leak sensors, the buying order is simple: choose the notification path first, then choose the sensor.
| Ecosystem, Q3 2026 status | Viable sensor paths | What the alert can actually do | Automation limits to notice before buying | Required hub or bridge | Buy this only if… |
|---|---|---|---|---|---|
| Apple Home / HomeKit — Confirmed, with hub requirement | Aqara Water Leak Sensor via Aqara hub; Eve Water Guard; Matter-capable options such as Shelly Flood Gen4 where your Apple Home setup supports the device path [1][2] | Apple Home can be the visible alert and automation layer when the sensor is properly bridged into HomeKit and the home has the needed hub for remote behavior. | Eve Water Guard is HomeKit-only, and remote alerts or automations need an Apple TV or HomePod acting as the Apple home hub [2]. Aqara’s leak sensor requires an Aqara hub for Apple Home support [1]. | Apple TV or HomePod for remote alerts and automations; Aqara hub if using Aqara. | You already have, or are willing to add, the Apple home hub and any required manufacturer bridge before placing sensors. |
| Google Home — Confirmed for status on some devices; limited for automations | D-Link SW-A11KT supports Google Home and IFTTT; Kidde can expose leak status in Google Home [1]. | Google Home may show wet/dry leak status for supported devices, but that is not the same as a usable automation or phone-warning path. | Wirecutter’s testing found Kidde’s Google Home support exposes leak status but cannot drive Google Automations [1]. | Usually the sensor maker’s app, bridge, or account link; check the specific model. | You are comfortable using the manufacturer app as the primary alert layer, or you only need Google Home visibility. |
| Alexa — Confirmed for the documented SwitchBot routine path | SwitchBot Water Leak Detector through Alexa; some other sensors through Skills or compatible bridges. | For SwitchBot, Alexa treats the detector like a contact sensor. The routine trigger is the detector becoming “Open,” then an Echo can speak a custom warning [3]. | The important condition is not called “water detected”; it is the contact-sensor “Open” state in the Alexa routine [3]. Skill-based support may not mean the same thing as routine-ready support. | SwitchBot account/device setup as required, plus an Echo if you want spoken alerts. | You will build and test the routine rather than trusting the Alexa badge. |
| Home Assistant — Workaround / Investigating for blueprint-heavy setups | Zigbee, Z-Wave, Wi-Fi, Matter, or bridge-fed leak sensors exposed as Home Assistant entities. | Home Assistant can send mobile push, play TTS, and route alerts by presence if your entities and automations are sound. | A community multi-sensor blueprint exists for push + TTS + presence checks, but commenters reported template errors in May 2026, so that path should be treated cautiously rather than as a clean confirmed recipe [4]. | A maintained Home Assistant instance, working mobile app notifications, and the radio/bridge your sensors require. | You are willing to test entity states, notifications, and templates after every meaningful change. |
| Standalone app-first sensors — Confirmed as the safer primary-alert choice when hub behavior is weak | Govee, Moen, SwitchBot, Kidde, D-Link, and other vendor-app sensors, depending on model. | The vendor app may be the actual phone-alert layer even when Apple, Google, or Alexa can see the device. | App notifications depend on phone notification permissions, background delivery, account login, and the vendor’s cloud or local behavior. A hub tile changing state is not proof that your phone will interrupt you. | Whatever the manufacturer requires: Wi-Fi, Bluetooth gateway, hub, or account link. | Your main goal is a phone alert, and you are willing to keep the vendor app installed and tested. |

Apple Home: confirm the home hub before you place the sensor
Apple Home is a good leak-alert path when the whole chain is present. The part people miss is the home hub. Eve Water Guard is HomeKit-only and needs an Apple TV or HomePod as the Apple home hub for remote alerts and automations [2]. Aqara’s water leak sensor can work with Apple Home, but not by itself; it needs an Aqara hub to bridge it into HomeKit [1].
Set it up in this order: install the manufacturer app and bridge if the device needs one, add the sensor or bridge to Apple Home, assign it to the room where the leak would matter, then turn on Home notifications for that sensor. If you are using Apple Home automations, build the action after the sensor shows a reliable wet/dry state in Home.
- Check that your Apple TV or HomePod is present in the home and functioning as the home hub before relying on remote leak warnings.
- Pair the leak sensor in the required app first if it uses a bridge, then expose it to Apple Home.
- In the Home app, open the sensor’s settings and enable notifications for leak or status changes where the app offers them.
- If you want more than a phone alert, create an automation that reacts to the sensor detecting water: turn on lights, trigger a plug-in siren, or change another visible device.
- Test with the iPhone locked and away from the house network if remote alerts are the point.
Make the final Apple check from the device that matters: the phone that would be upstairs, outside, or away should receive the Home notification or see the automation result.
Google Home: treat leak status as visibility, not automatically as an alert path
Google Home is the place where compatibility language needs the most suspicion. A leak detector can be visible in Google Home without being useful as a Google Automation trigger. Wirecutter found that Kidde’s Google Home support exposes leak status but cannot drive Google Automations [1]. That is a meaningful limitation if your plan was “when water is detected, Google turns on lights and sends me a warning.”
If you already own a Google-visible leak sensor, open Google Home and confirm what it actually gives you. If it only shows wet/dry status, configure the real phone alert in the manufacturer app. Do not stop at the Google tile unless your use case is simply checking status manually.
- Pair the leak detector in the manufacturer app and enable that app’s leak notifications.
- Link the manufacturer account or device service to Google Home if the model supports it.
- Look at the device in Google Home and confirm whether it is only reporting status or can actually start an automation.
- Wet-test the sensor and wait for the manufacturer app notification, not just the Google Home state change.
D-Link’s SW-A11KT is another reminder to check the exact path: Wirecutter lists it as supporting only Google Home and IFTTT [1]. That may be fine for a narrow setup, but it is not a broad cross-platform promise. If your existing hub is Google Home and you want a hub-driven routine, verify that exact routine trigger before buying. The broader sensor-to-hub pairing pass belongs in the smart flood sensors by hub guide; here, the only thing that matters is whether the warning reaches you.
Alexa: the SwitchBot path works, but the trigger is called “Open”
The documented SwitchBot-to-Alexa setup is workable because it tells you the odd part plainly: Alexa exposes the SwitchBot Water Leak Detector as a contact sensor, and the routine must use the “Open” condition. SwitchBot documents the routine path for app version 8.1 and newer, with an Echo speaking a custom message when the detector reports that condition [3].
- Set up the SwitchBot Water Leak Detector in the SwitchBot app and make sure the detector reports normally there.
- In the Alexa app, confirm the detector appears under devices after the SwitchBot integration is linked.
- Create a new Alexa routine.
- For the routine trigger, choose the water leak detector as the smart-home device and select the “Open” condition.
- Add the action you actually need: an Echo announcement, a custom spoken message, lights turning on, or another visible device response.
- Wet-test the detector and listen for the Echo message in the room where someone will hear it.
For a phone-first alert, keep the vendor app notification enabled too. The documented Alexa example is valuable for an in-home spoken warning, especially at night, but a speaker announcement is not the same as a push notification when nobody is home.
Home Assistant: use the flexibility, but do not inherit a broken template blindly
Home Assistant can make the richest alert path: multiple leak sensors, mobile push, speaker TTS, presence checks, helper toggles, repeat behavior, and escalation. It also gives you enough rope to build something that looks clever and fails at the exact moment the sensor changes state.
A Home Assistant community blueprint for water leak alerts combines multi-sensor mobile push, TTS, and presence checking, but May 2026 comments in the thread reported template errors [4]. That does not make the idea bad. It does mean the blueprint path belongs in Workaround / Investigating status until you have personally validated it on your instance.
For a first Home Assistant flood alert, start boring. Find the leak sensor entity, confirm whether it turns to “on,” “wet,” or another state when the contacts get damp, then send one mobile notification. Add TTS and presence logic after the basic alert has passed a real wet test.
alias: Water leak - notify phones
mode: single
trigger:
- platform: state
entity_id:
- binary_sensor.kitchen_sink_water_leak
- binary_sensor.laundry_water_leak
to: "on"
action:
- service: notify.mobile_app_your_phone
data:
title: "Water leak detected"
message: "{{ trigger.to_state.name }} is wet. Check this sensor now."That example uses placeholder entity names. Replace them with the actual entities from your Home Assistant instance and verify the wet state in Developer Tools before trusting the automation. If your sensor reports a different wet value, change the trigger instead of forcing the sensor to match the example.
App-first sensors: sometimes the vendor app is the main alert, not the fallback
For Govee, Moen, SwitchBot, Kidde, D-Link, and similar app-based leak detectors, the manufacturer app may be the most dependable warning layer available to you. That is not a failure if you acknowledge it before buying. It becomes a problem only when the hub badge makes you assume Apple, Google, or Alexa will do things the sensor maker’s app is actually doing.
- Install the vendor app on every phone that needs the leak alert.
- Enable push notifications for that app at the phone operating-system level.
- Turn on the app’s leak, water, or alarm notifications inside the app itself.
- If the app uses a hub or gateway, place that bridge where it keeps a stable connection to the sensor.
- Only after that, add Apple Home, Google Home, Alexa, or another hub as a secondary layer.
Whole-home flow monitors sit next to this category but are not the same thing as spot leak sensors. Flo by Moen, for example, requires a 7-to-10-day learning period before it can flag abnormal flow [2]. That kind of system can be useful, but it does not replace a probe under a water heater, dishwasher, sink, or laundry machine when the question is, “Did water touch this exact spot?”
The pre-purchase calls that prevent most bad setups
If you have not bought the sensor yet, do this part before reading another product page. A good per-ecosystem detector list can help with shortlisting—see the best smart water leak detectors guide for picks—but the buying decision here is narrower: which device can produce the alert path your home will actually use?
| Device or category | Q3 2026 buying call | Why it matters for alerts |
|---|---|---|
| Aqara Water Leak Sensor | Good Apple Home candidate only if you also accept the Aqara hub requirement [1]. | The sensor’s Apple Home support depends on the bridge path, so the hub is part of the alert setup, not an accessory. |
| Eve Water Guard | Apple-only choice; plan on an Apple TV or HomePod home hub for remote alerts and automations [2]. | Do not buy it for a Google- or Alexa-first home and assume the badge problem will be solved later. |
| Shelly Flood Gen4 | Current low-cost Matter path at about $40, with Matter plus Alexa, Google, HomeKit, and SmartThings support over Bluetooth, Wi-Fi, or Zigbee [2]. | Matter reduces lock-in, but it does not remove the need to test the actual phone alert in your chosen platform. |
| D-Link SW-A11KT | Narrow ecosystem fit: Google Home and IFTTT support only in Wirecutter’s compatibility notes [1]. | Fine if that is your exact path; frustrating if you expected broader hub behavior. |
| Kidde smart leak detector path | Google Home can expose leak status but not drive Google Automations; Alexa support is through a Skill [1]. | This is the classic visibility-versus-actionability split. Confirm where the push alert comes from. |
| SwitchBot Water Leak Detector | Useful Alexa workaround if you build the routine with the contact-sensor “Open” condition [3]. | The routine trigger wording is the setup detail that prevents a miss. |
| Flo by Moen and similar whole-home flow monitors | Adjacent category, not a spot sensor; Flo by Moen has a 7-to-10-day learning period before abnormal-flow detection [2]. | Use it for flow monitoring decisions, not as a substitute for a probe where puddles start. |
Run the wet test like you will not get a second chance

Use a damp folded paper towel or a small amount of water on the sensor contacts, then watch the full chain. The sensor should change state, the app or hub should recognize the leak, and the intended person should receive the warning in the form you planned: phone push, Echo announcement, Apple Home notification, Home Assistant mobile alert, or vendor-app alarm.
- Test with the phone locked.
- Test with the phone off the home Wi-Fi if remote alerts matter.
- Test the exact routine condition, especially Alexa’s “Open” trigger for SwitchBot.
- Test the manufacturer app even if the sensor also appears in a hub.
- Dry the contacts and confirm the sensor returns to normal so the next alert is not masked by a stuck state.
If the test only changes a tile from dry to wet, keep configuring. A smart home flood-warning setup is not finished when the sensor pairs. It is finished when the alert reaches the person who can act on it.
References
- The Best Smart Water Leak Detectors, Wirecutter
- The Best Smart Water Leak Detectors, PCMag
- How to set up Automation when Water Leak Detector detects leakage?, SwitchBot Help Center
- Water Leak Alert - Multi Sensor Mobile Push + TTS with Presence Check, Home Assistant Community
