Connected devices now report flow, pressure, leak alarms, and filter status to an app on a phone. Many also receive software updates from the manufacturer, often without a technician at the door. For a homeowner, that changes the record. The device that was checked at installation may not be the device running a year later.
The question is not whether updates are good or bad. The question is whether anyone wrote down what the device was doing before the change, and who is responsible for what happens after it.
Why ownership changes matter
Ownership changes are a common source of this problem. On Nov. 3, Badger Meter announced that it had acquired 37South, which Water Finance and Management described as a "utility technology and remote monitoring company" based in Melbourne, Australia. The same outlet notes that the deal follows a recent run of acquisitions by Badger Meter. The summary does not describe how any product line, firmware schedule, or support arrangement will change for existing customers. That silence is the point. A buyer's public statement tells you a deal exists. It does not tell you the release cadence, the support window, or the terms that will govern the next update to a device already installed in a house.
What to record before the update
A short record covers most of the risk. Start with the model number, serial number, and installed firmware or software version, taken from the device or its settings screen and dated the day you take it. Save a screenshot or print a copy. If the device has a companion app, note the app version as well, since the app and the device can be updated on different schedules.
Next, record what the device was set to do: alarm thresholds, shutoff behavior if it has one, notification recipients, and any reporting schedule. Updates sometimes reset settings to defaults or change how alerts are routed. As one example, an alarm that sends notices to a former account holder, or to no one at all, looks like silence until someone checks the water bill.
Finally, write down who you call. Note the manufacturer's support contact, where the warranty document is kept, and whether the warranty says anything about software. Keep the installer invoice in the same folder. These papers are what you will need if an update changes behavior and you have to show what the device did before.
The tradeoff with updates
Updates carry real benefits. Security fixes close gaps that a connected device would otherwise keep open, and feature changes can improve alert accuracy. The cost is that a homeowner usually cannot test an update against their own plumbing before it lands. A sensor set up for one installation may behave differently after a change to its filtering or threshold logic, and release notes may not describe the effect on your specific system.
A practical approach is to check the app for an update notice before accepting it, when the option exists. If the device allows a delay, use that time to confirm the current settings are recorded. After the update, compare readings and alerts over the first few days against what you saw before. A short test, such as a planned draw or a controlled leak check where the manufacturer's instructions allow one, is more useful than a general sense that everything looks fine.
Where coverage fits
If a connected device fails to alert after an update and water damage follows, the questions become contractual. Review your coverage for home systems and appliances to see how the policy treats software, third-party reporting services, and devices that may be classed as separate purchases rather than part of the home. Do not assume that an update is covered or excluded. Check the language.
The record kept before the update is the evidence that supports any claim. It shows what the device was configured to do and what changed afterward. Without it, the question of whether the update caused the failure is much harder to answer.