Reference · built on requestOperator by FibricFacilities & comfort

Leak Response

Correlates leak sensors with meter flow and proposes a valve shutoff, a work order, and who to notify.

Request accessPricing ↗

About

A leak sensor under a sink reports wet. A water meter shows flow that has not stopped for hours. Alone, each is a nuisance alert; together they are a burst. Leak Response reads leak and water sensor uplinks from your LoRaWAN network server, flow and totalizer values from meters over Modbus TCP or MQTT, continuous-flow flags from a utility meter platform, and the state of any motorized shutoff valve.

When a wet sensor and abnormal flow agree, it proposes three things at once: close the valve that isolates that area, open a work order with the location and evidence, and notify the people on the list for that building. You approve the shutoff. Nothing closes until you do.

This is a reference listing. It documents what Fibric would read from Leak Response and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Leak and water uplinks from your LoRaWAN network server, with decoded payload, received time, gateway, and signal quality per message
  • Battery level and last-seen time per sensor, so a silent sensor is flagged rather than assumed dry
  • Flow rate and totalizer values from water meters, on Modbus TCP registers or MQTT topics you map
  • Continuous flow and leak columns from Badger Meter BEACON interval exports, such as Current Leak Rate Per Day and Current Leak Start Date
  • Open and closed state of motorized shutoff valves, on the register or topic each valve reports
  • Open work orders in your CMMS for the same location, so a leak already in hand is not reported twice

Proposed actions

  • Target capability: propose closing the shutoff valve that isolates the affected area, through the Modbus TCP or MQTT connector, for your approval
  • Target capability: propose a work order in your CMMS with the location, the sensor, the flow evidence, and the valve state
  • Target capability: propose a notice to the people on the building's list, by Microsoft Teams, Slack, or Twilio SMS
  • Target capability: propose reopening the valve once the work order is closed, for the technician to confirm on site
  • Target capability: propose a sensor check when a sensor reports wet but the meter shows no change, or its last-seen time is stale

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Isolate a burst before it reaches the floor below

    A LoRaWAN leak sensor in a riser closet reports wet and the floor meter over Modbus TCP shows flow that will not stop. Leak Response proposes the riser valve closed, a Fiix work order, and a Teams notice to the on-call engineer.

    With LoRaWAN Network, Modbus TCP, Fiix, Microsoft Teams

  • Text the person who can turn the key

    A Milesight sensor under a rooftop unit reports water. The MQTT meter topic agrees. The operator proposes a MaintainX work order and a Twilio SMS to the technician named for that building.

    With Milesight Development Platform, MQTT Broker, MaintainX, Twilio

  • Use the utility's own leak flag

    BEACON reports a leak rate per day on a site with no sensors. The operator proposes an UpKeep work order to walk the site and a Slack notice, with the start date BEACON gives.

    With Badger Meter BEACON, UpKeep, Slack

  • Trust the sensor less when the meter disagrees

    A Monnit sensor reports wet but the meter shows no flow. Rather than a shutoff, the operator proposes a Limble task to check the sensor and its placement.

    With Monnit iMonnit, Limble CMMS

Requirements

  • A LoRaWAN connector to the network server that receives your leak and water sensors
  • A Modbus TCP or MQTT connector that reads meter flow and, where installed, the shutoff valve's state and command
  • One CMMS connector: Fiix, UpKeep, MaintainX, or Limble CMMS
  • One messaging connector: Microsoft Teams, Slack, or Twilio, and a notification list per building
  • A map of which valve isolates which sensors and meters, kept by you
Authentication
Leak Response owns no credentials. It reads sensors and meters through your LoRaWAN, MQTT, Modbus TCP, and meter connectors, and proposes valve writes, work orders, and notices through those connectors and your CMMS and messaging connectors.

Limits

  • A shutoff is proposed only for valves you mark as proposable. Fire protection and other supplies you exclude are never proposed.
  • Sensors report when they send. Between uplinks the operator knows only the last reading and its age.
  • Utility meter exports arrive at the interval and delay the platform publishes. They confirm a leak; they do not catch one in the first minutes.
  • It is not a fire or life-safety system, and it does not replace a flow-based shutoff device that acts on its own.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Leak Response ↗

Questions and answers

What do you approve when a leak is found?
The shutoff, the work order, and the notice, each on its own. The proposal shows the sensor, the meter series, the valve it would close and what that valve isolates, and who would be told. You can approve all three or only some. Reopening the valve is a separate approval.
What record does a leak leave?
A receipt per proposal: the uplinks and flow readings, the valve state before and after, the work order written, the notices sent and to whom, who approved each step, and how to reopen. Sensor checks that found a false alarm are kept, so a noisy sensor becomes visible.
Will it close a valve on its own?
No. A valve moves only after a person approves the proposal, and only for valves on your proposable list, through the connector that controls it. Where seconds matter, install a device that acts locally; this operator gives people the evidence and the decision.
Ask about Leak Response

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy