Connected water equipment can report salt level, track consumption, flag continuous flow, schedule regeneration, or close a valve while nobody is home. Those are useful functions. They also create a practical commissioning job that homeowners and installers too often skip: identifying what depends on the internet, who controls the account, and what still works when the connection fails.
The reason to take that job seriously is not theoretical. ACHR News reports that a cyberattack targeting French supermarket refrigeration systems caused food losses and disruptions. The supplied report concerns commercial refrigeration, not residential water treatment. Still, its central lesson travels well. Equipment connected for monitoring or control can inherit risks that have nothing to do with its original mechanical purpose.
A homeowner does not need to become a network engineer. You do need to know which parts of the water system can be changed remotely and whether basic operation survives a lost account, dead router, or discontinued app.
Start with a control inventory
Stand in front of each connected device and write down its make, model, serial number, app name, account email, and connection method. Note whether it uses Wi-Fi directly, communicates through a hub, or reports through another control panel. Photograph the label and the wiring before closing the cabinet.
Then separate monitoring from control. A pressure sensor that only sends readings presents a different operational consequence than a valve that can stop water to the entire house. A softener app that displays remaining capacity is not the same as a controller that can alter regeneration settings.
For every controllable function, find the local equivalent. Can you start a manual regeneration at the valve head? Can you reopen an automatic shutoff without the app? Can you silence an alarm locally without disabling protection? Put those instructions near the equipment, not only in a cloud account.
Give the connected gear its own lane
Check the router client list and identify the water devices by name or hardware address. If your router supports a separate guest or internet of things network, use it for equipment that does not need access to laptops, storage devices, or shared household files. Do not expose a controller directly to the internet through manual port forwarding unless the manufacturer specifically requires it and explains how it is secured.
Replace default passwords, use a unique password for the equipment account, and enable multifactor authentication when offered. Also inspect the account for old installers, previous owners, unused phones, and shared logins. Removing stale access is ordinary maintenance, much like clearing an obsolete thermostat schedule.
Updates deserve a line on the service checklist. Record the controller firmware version and whether updates happen automatically. If the manufacturer no longer supports the model, that does not automatically mean the treatment hardware is worn out. It may mean the connected control deserves isolation, replacement, or conversion to local operation.
Run a deliberate offline test
Do not discover the fallback behavior during a storm or active leak. Pick a time when water use can be interrupted. Note the current valve position and programmed settings, then disconnect the equipment from Wi-Fi or temporarily disable its network access at the router.
Confirm that normal water service continues where it should. Test local buttons and displays. Verify whether schedules remain stored, alarms remain visible, and a shutoff valve can be operated by hand. Restore the connection and confirm that the device returns without losing settings or creating duplicate alerts.
If you are comparing equipment or arranging service, ask a water treatment shop like Jones Air & Water which functions are local, which require a subscription or cloud account, and what replacement path exists if the communications module fails. Those questions are more useful than asking whether a unit is simply “smart.”
Leave a handoff sheet
Finish with one page kept near the main shutoff. Include device names, account owner, local operating steps, network name, installer contact, and the date of the last offline test. Do not print the password itself. Note where credentials are stored securely.
The goal is not to disconnect every useful control. It is to make sure the house still has understandable, serviceable water equipment when the app, account, or network is unavailable. Connected features should add visibility. They should not become the only way anyone knows how to run the valve.