Tuya / Smart Life Smart Water Valves: Setup, Alerts and Automations Explained

If you have just bought a Tuya-based smart water valve, such as Hydrion's whole-house leak detector with auto shut-off, the hardware itself is usually the easy part. The learning curve is the Smart Life app: how pairing actually works, where each type of alert shows up, what an automation can and cannot promise, and how to let someone else in the household control the valve without handing them the entire account. This guide walks through all four, using the app as it behaves for a single Wi-Fi-connected valve rather than a hub-based smart-home network.

• Pairing almost always requires a 2.4GHz Wi-Fi network during setup, even if your phone and router are configured for 5GHz or a combined band.
• Alerts are not collected in one inbox: the Message Center splits them across an Alarm tab, a Home tab and a Bulletin tab, and push notifications also depend on your phone's own permission settings.
• An automation built around a standalone Wi-Fi valve runs through the cloud, so it depends on the home's internet connection rather than working as a local, offline-proof rule.
• Sharing access means assigning a role, and the role decides whether that person can edit automations and manage devices or only open and close the valve.

What the Smart Life App Actually Controls

Smart Life is a general-purpose companion app built by Tuya, not something written from scratch for this valve. That distinction matters in practice: the same app manages plugs, sensors and other Tuya-ecosystem devices from many different brands inside one account. Everything covered in this guide, pairing, alerts, automations and sharing, happens inside a single "Home" in that app, and the whole-house leak detector and shut-off valve is simply one device living inside that Home alongside whatever else has been paired to it.

Pairing the Valve: EZ Mode, AP Mode and the 2.4GHz Requirement

Before You Start

To add the valve, tap the + icon on the Home page, choose the matching device category, and enter the Wi-Fi password when prompted. Which pairing mode to choose next depends entirely on how the valve's indicator light is behaving. A fast-blinking indicator corresponds to EZ Mode, where the app broadcasts the network credentials directly to the device, while a slow-blinking indicator corresponds to AP Mode, where the phone temporarily joins a small hotspot that the valve itself creates so it can receive those same credentials (source: How do I add a device to the App and connect it to the Internet Wi-Fi? — Tuya Help Center). The app switches between the two modes through a button in its upper-right corner during setup, so if the light does not match the mode currently selected, that is the first thing to correct before trying again.

The detail that causes more failed setups than anything else is the network band. Most Wi-Fi devices added through the app, including this one, only support a 2.4GHz network during the pairing step itself, even when the device's ongoing Wi-Fi connection works fine on other bands (source: How do I add a device to the App and connect it to the Internet Wi-Fi? — Tuya Help Center). If a router broadcasts one combined network name for both bands, or if the phone has recently connected to 5GHz, pairing can fail even when every other step has been followed correctly. The product listing for this valve describes support for both 2.4G and 5G Wi-Fi, which refers to its general wireless capability rather than a guarantee that first-time pairing works over 5GHz, so it is worth having a 2.4GHz-only network name available, even temporarily, for setup.

If the Indicator Isn't Blinking

If the light is solid, off, or blinking in a pattern that does not match either mode, the valve usually needs a manual reset before the app will recognize it as ready to pair; the exact reset method is in the product manual rather than in the app itself. Once the device is pairing correctly but the app still cannot find it on the network, that points to a connectivity problem rather than a pairing-mode problem, and it is worth working through router-side checks, such as 2.4GHz visibility and band settings, rather than repeating the same pairing attempt. A separate guide covers those Wi-Fi fixes in detail for a device that keeps showing as offline after it has already been added once.

Where Each Alert Actually Shows Up

Saying an app "sends alerts" undersells how the notifications are actually organized. The Message Center is split into three separate tabs rather than one combined inbox: Alarm, Home and Bulletin (source: What information can I get from Message Center? — Tuya Help Center). The Alarm tab is where the leak detector's own alarms appear, together with automation-triggered notifications and alerts for scheduled actions that failed to run. The Home tab logs changes to the Home itself, such as members joining or devices being added or removed. The Bulletin tab is where phone call notifications, SMS notifications, new-device-login notices and official app announcements appear, kept separate from the device alarms shown in the Alarm tab.

Because the leak detector can notify through a push notification, an SMS message and a phone call, it is worth checking each channel rather than assuming one covers the others. Push notifications specifically depend on the phone's own operating-system notification permission for the app, not just an in-app toggle, so a restricted permission at the OS level can silence push alerts even when everything inside the app is switched on. For readers who specifically want the valve's alerts routed through a voice assistant as well, Alexa and Google Assistant integration is covered separately, since it works through a different setup path than the Message Center described here.

Building an Automation Without Assuming Too Much

A Simple Automation, as an Example

Automations live on the Smart page's Automation tab. Tapping + starts a new one: one or more trigger conditions are set, requiring either all of them or any one of them to be true, then the devices and actions to run are chosen, and the result is saved (source: How to set smart scenes? — Tuya Help Center). A simple example for this valve would trigger on an abnormal-flow alarm and pair it with a push notification and a phone call, so a slow leak the valve has already flagged also reaches a household member through a channel they are more likely to notice quickly.

What that automation can actually promise depends on a distinction the app does not surface up front. Scenes come in three technical forms: cloud-based scenes, which are judged and stored on Tuya's servers; local scenes, where every linked device shares one gateway and the rule itself is stored on that gateway; and LAN scenes, which span multiple gateways on the same local network (source: What types of automation scenes are there? — Tuya Help Center). A standalone Wi-Fi valve with no shared gateway does not qualify for a local or LAN scene, so any automation built around it is a cloud scene by default. That means the trigger has to reach Tuya's servers and the resulting command has to come back down before the action runs, and if the home's internet connection is down, that round trip cannot complete, so the automation may simply fail to fire (source: Will the Automation still be triggered normally if the home network is disconnected? — Tuya Help Center).

This is how the platform's cloud scenes behave for any single Wi-Fi device, not a shortcoming specific to this valve. The practical implication is to treat the app's automations and alerts as a convenience layer on top of the valve's own built-in sensing and shut-off behaviour, rather than a substitute for it: the flow sensor and motorized shut-off are part of the device itself, while the notification and remote-control layer depends on connectivity. A setup where automations need to survive an outage generally needs devices and a hub that support local or LAN scenes, which is covered separately in a guide on Home Assistant integration.

Sharing Control With the Household

Multiple people can use the same valve without sharing one login. To join an existing Home, a new member goes to Me, opens Home Management, selects Join a Home, and enters the invitation code that the Home's owner or an administrator generates for them (source: How to join a home via an invitation code? — Tuya Help Center).

The role assigned to that person decides what they can actually do, and the difference matters for a device that controls a home's water supply. There is exactly one Home Owner per Home, with full control, including the ability to appoint administrators and configure custom members. Administrators can manage devices, automations, rooms and common members. Common Members can use devices and run existing automations but cannot add or remove devices or edit automations themselves. Custom Members receive whatever permissions the owner explicitly sets for them, which can be limited to specific devices or specific conditions (source: What are the differences between the Custom Role, Common Member, Administrator and Home Owner? — Tuya Help Center). For a shut-off valve specifically, giving a partner or caregiver a Common Member role lets them open or close it directly when needed, without also giving them the ability to change how the automation behaves or remove the device from the Home.

None of this replaces reading the valve's own manual, but it should make the app itself less of a black box: pairing succeeds once the network band and mode match what the indicator light is showing, alerts are organized by tab rather than gathered into one feed, an automation's reliability depends on whether it is a cloud or a local scene, and sharing access is a matter of choosing the right role rather than handing over the whole account. Readers still deciding whether an automatic shut-off valve is worth adding to a home can treat this walkthrough as a reasonably accurate preview of what living with one day to day looks like once it is installed.