Will a wireless leak sensor close a valve if the internet connection fails?
That depends on where the automation runs. A supported local sensor-to-controller rule may work without an internet connection; a cloud-dependent rule may not. Check the actual sensor, gateway, valve and firmware together, including power loss, link failure, manual operation and how the valve state is confirmed.
Plan local behaviour and remote data separately- Leak sensor
Detect water at the chosen position
- Local controller
Run the supported automation rule
- Valve + feedback
Operate and confirm the actual state
- Remote application
Alerts, users and multiple-site records
Describe the response before the wireless protocol
A leak sensor near a water connection may need to alert one person. Another project wants automatic isolation. A service provider may need to supervise many customer sites. Start with those jobs before choosing Zigbee, Wi-Fi or another link. Name the person who responds, the water section the valve controls and the conditions in which automatic operation is allowed. The site team must review the plumbing and valve arrangement.
Find out where the shutoff rule runs
Ask the supplier to show the automation path from detection to valve command. Is it stored in a local hub, the valve controller, a phone or a cloud service? Then disconnect the internet and test the supported behaviour. A gateway still having power is not enough if it waits for a cloud instruction. Keep the local response requirement separate from remote notification, and agree how a failed sensor-to-controller link is reported.
Match the valve, actuator and feedback
An actuator’s supply voltage alone does not establish that it fits a valve. Check mounting, stem connection, torque, open/close or positioning control, and the valve’s suitability for the medium and operating temperature. A changed seal or valve arrangement can change the actuator requirement. A screen saying “close” may show a command rather than a confirmed position. Check the feedback, manual operation and recovery after power loss with the local team.
Check what the phone app actually provides
A consumer app may be suitable for one owner and a small set of devices. Multi-customer operation adds user roles, site separation, device enrollment, alert ownership and service records. Ask whether the selected service supports those functions and whether the intended API is available in the agreed subscription. Branding and API integration are additional requirements, not automatic benefits of using an app-connected gateway.
- List the people and companies that need access.
- Keep customer sites separated in the account design.
- Agree who receives and acknowledges an alert.
Put outages into the pilot
Test a wet-sensor event according to the selected equipment’s instructions, then check valve operation, feedback and notification. Repeat under the planned internet-loss and power-loss conditions where the site procedure permits. Check low battery, an unavailable sensor and a restart. Use a clear record of what operated locally and what reached the remote application. A delivered alert on one phone does not establish the full multi-site workflow.
Prepare the system request as one package
Send the number and type of sites, leak-detection positions, valve details, available power, network and required local response. State whether the job needs one user’s app or a service-provider platform. We can review the compatible hardware and identify any additional integration. The quotation should distinguish equipment, local configuration, platform services and site installation so the team knows what it will receive and maintain.
| Job | Review with the selected configuration |
|---|---|
| Notify one site owner | App access, notification method and sensor health |
| Operate a local shutoff valve | Rule location, compatible valve, feedback and outage behaviour |
| Supervise multiple customer sites | Account roles, site separation, API and service workflow |
| Continue during internet loss | Local logic and a tested recovery arrangement |
Common questions
Does Zigbee compatibility guarantee the complete automation works?
Check the supported device functions and rules on the selected hub and firmware. A compatible radio link is one part of the system.
Can an app-connected kit become a branded multi-customer platform?
Review account separation, API access, device enrollment and branding with the service provider. They may require additional platform work and recurring charges.
