1Introduction
Strips Drip raises an alarm as soon as water reaches the absorbent pads on its blue plate. It also measures temperature and can warn before pipes freeze. It is only 6 mm thick, plate included, and copes with damp places, so it fits where leaks start: under sinks and appliances, along pipe runs, in cellars, plant rooms and roof spaces.
It works with any LoRaWAN network server (LoRaWAN 1.0.4, class A, OTAA) and reaches up to 10 km in line of sight. The battery is built in and lasts well over ten years. Leak alarms are sent confirmed, so they are repeated until the network server has received them.
What's in the box
- Strips Drip, with the adhesive already on the back
- The blue pad plate with two absorbent pads. It usually comes separate. Some customer variants have it fitted.
- One or two magnets on the sensor. They keep it in transport mode until you start.
- The LoRaWAN keys (DevEUI, JoinEUI and AppKey). They come on a label in the box and also by e-mail.
No tools or screws are needed. The +Clip mounting accessory is sold separately.
Parts of the sensor
2Before you start
A LoRaWAN sensor needs a little more preparation than a sensor that pairs with a hub. Have this ready first:
You need
- A LoRaWAN gateway within range, powered on and online
- An account on a LoRaWAN network server (for example The Things Network, ChirpStack, Loriot or Actility), with the gateway added to it
- The keys for the sensor: DevEUI, JoinEUI (also called AppEUI) and AppKey
- The region printed on the sensor's label (for example EU868 or US915). The network server and the gateway must use the same region. In US915 and AU915, they must also use the same sub-band.
- The Strips payload decoder in your network server or application, so the messages can be read (see Support)
Choosing the place
- Where water collects first: flat on the floor under sinks, dishwashers, washing machines, pipe joints and boilers. In a cellar, choose the lowest point.
- Indoors or sheltered outdoors: the sensor is IP67, but should not lie under water for long
- Range: up to 10 km in open line of sight, much less through walls and floors
- No metal: do not mount Strips directly on metal, magnetic surfaces or inside a metal structure. If it has to go on metal, put padding between them. A metal cabinet base counts.
3Step by step: from box to ready
Nine steps. Register the sensor in the network server before you take the magnets off. Then join it, choose what it should report, and mount it last.
Unpack
Check that the sensor and its magnets are there, and find the keys. Leave the magnets on until you join.
Register the sensor in the network server
- Add a new end device in your network server, with activation OTAA.
- Choose LoRaWAN 1.0.4 (MAC version), regional parameters revision RP002-1.0.1, and the frequency plan for the region on the label. In US915 and AU915, choose the same sub-band as the gateway.
- Enter the DevEUI, JoinEUI (AppEUI) and AppKey. Check them carefully: one wrong character and the join fails.
- Add the Strips payload decoder to the device or the application.
Join the network
Take every magnet off the sensor. Strips leaves transport mode and sends a join request.
If the magnets have already been off, or you are joining the sensor again, start the join with the magnet instead: move it to the rounded end three times, for three green blinks.
Fit the pad plate
Fit the plate straight after the join. It cannot go on earlier, because the tape that holds the transport magnets runs round the sensor. Two hours after the join, Strips Drip calibrates again, and it must then be on its plate, mounted in its final place, with the pads dry. If your sensor came with the plate already fitted, skip this step, but still mount it within two hours.
- Peel the film off the adhesive on the back of Strips.
- Press Strips onto the side of the plate marked STRIPS SIDE.
Check the signal where it will sit
Hold Strips at the place where it will be mounted and send an uplink: move the magnet to the rounded end three times. Then look at the message in the network server.
Configure
From the factory, Strips Drip sends only a daily heartbeat. Choose the leak profile to turn on the leak alarm.
| Profile in the Config Tool | What it does |
|---|---|
| Liquid Leak and Frost Alarm | An alarm (confirmed) when water is detected, and when the temperature falls to 4 °C. The pads are checked every 30 seconds. Also sends the flood value (0–100 %) once a day and during a leak. |
| Custom Profile (Advanced) | Choose reports and settings yourself, for example a different frost level or temperature reports. |
In a damp place, the alarm level may need to be raised: see Damp places under Using the sensor.
- Open the Strips LoRa Config Tool and choose Strips Multi-sensor +Drip.
- Choose a profile, check its reports and settings, and change a value if needed.
- Copy the payload the tool creates, and send it as a downlink on port 11 from your network server.
- Send an uplink with the magnet (three times at the rounded end). Strips is a class A device: it only receives a downlink right after it has sent something.
Install
Choose one of three ways:
- Loose: lay the sensor flat in place, pads down. This is good for a quick start, or where it may need to move.
- Adhesive: the surface must be clean, dry and at least +10 °C. Peel the film off the adhesive under the plate and press it firmly in place.
- Screws: the plate has a hole at each end. Use the plate to mark the holes, and use screws with flat heads.
Place it so that the pads have the best chance of meeting water first.
Test (optional)
You do not have to test: a correctly calibrated sensor works. If you want to see the alarm, wait until at least five hours have passed since the join, so that the second calibration is long done with the sensor mounted and dry. Do not wet the pads before that. Then put a little water on them.
Ready
- Registered in the network server with the right region and keys
- On its plate, mounted in its final place and dry within two hours of the join
- Joined, and the messages are decoded
- Leak profile chosen and confirmed with status code 0300
- Signal checked at the final spot
- Optional: leak alarm tested with water after five hours, and the pads dried
- An action set up in your application for a leak: a notification, or a valve that closes
4Using the sensor
What it reports
- Water leak: an alarm (confirmed) when the flood value passes the alarm level, and again when it clears
- Flood value: 0 (dry) to 100 (soaked), once a day and during a leak
- Temperature: frost and high alarms, reports or averages
- Battery level and heartbeat: once a day by default. A new sensor shows 99 %, which means full.
After a leak
- Leave the sensor where it is. Remove the water, and the pads dry by themselves. A cloth round the pads speeds this up.
- Drying takes at least 24 hours, and longer after a lot of water. The pads only detect water reliably again once they are dry.
- The sensor keeps working after a leak and can detect leaks again and again for its whole battery life.
- Do not leave it submerged for long periods.
Damp places: adjusting the alarm level
In a damp place, such as a cellar, a crawl space or a plant room, the pads never get completely dry. The flood value (0 = dry, 100 = soaked) then rests above 0, and with the default alarm level of 10 % the sensor can raise false alarms. Set the level to suit the place:
- Calibrate in place first. With the sensor mounted where it will stay, and as dry as it gets there, calibrate it (see Recalibrating). The resting value then becomes the base.
- Watch the flood value for a few days. The Liquid Leak and Frost Alarm profile reports it once a day. To see it more often, set the Flood Report Interval to, for example, 60 minutes. Note the highest value in normal conditions.
- Set the alarm level above it. Set the Flood Alarm Threshold Level clearly above the highest normal value: if it rests around 10 %, try 20–30 %. Keep the Flood Alarm Hysteresis a few per cent, so the alarm clears once the pads dry. Do not go higher than needed: a small leak must still pass the level.
- Send the settings. In the Config Tool, choose the profile, change the two settings, copy the payload and send it as a downlink on port 11. Then send an uplink with the magnet. Status code 0300 confirms.
- Turn the Flood Report Interval off again if you only turned it on for this. Frequent reports cost battery.
Confirmed messages and network outages
Alarms are sent confirmed: Strips waits for an acknowledgement from the network server. If none arrives, for example because the gateway is off, Strips goes into resend mode. It tries again after 1, 2, 4, 8 minutes and so on, up to once a day. After 7 days without an acknowledgement, Strips resets itself and goes into standby (see below).
Operating modes
| Mode | What it means |
|---|---|
| Transport | Magnets on, deep sleep, almost no battery used. This is how Strips is delivered. |
| Joined | Normal operation: connected to the network and reporting. |
| Resend | A confirmed message has not been acknowledged. Strips retries with longer and longer gaps. |
| Standby | Not joined, after a reset or after 7 days in resend mode. Strips sends a join request once a day until it gets in. |
Strips cannot be switched off. Once the magnets have been removed, it can go back into transport mode only if it has never joined. This applies if the join failed, or if the magnets were put back before it sent a join request.
LED signals
| LED | Meaning |
|---|---|
| ● Short green | A magnet at the rounded end. An extra short blink after a three-swipe pattern: the command was accepted. Also shown when an alarm is acknowledged. |
| ● Long green | Joined, reset or starting up |
| ● Short orange | Strips is sending a report, or a join request when it is in standby |
| ●● Orange, then red | Duty-cycle limit: too many messages for the network. The message goes out a little later. |
| ● 5 short red | The join failed. After a resend: the message still had no acknowledgement. |
| ● 3 short red | Strips sent a confirmed report, but got no acknowledgement (ACK) from the network server |
| ● 2 short red | A report was not sent, because Strips is in resend mode |
| ● Long red | The magnet was detected while Strips is in standby (not joined) |
You can turn the LED down with the LED Level setting: all events (default), user actions and errors only, or very limited.
5Magnet commands
You give commands by moving a magnet at the rounded end of Strips. Use the magnet that came with it, or any small magnet.
| Command | How | Result |
|---|---|---|
| Send an uplink / join | Magnet to the rounded end three times, for three green blinks | A short extra green blink. If joined, Strips sends a message and picks up waiting downlinks. If not joined, it sends a join request. |
| Reset | As above, but on the third time hold the magnet at the rounded end for 10 seconds | Two long green blinks. Strips leaves the network and restarts. Its settings are kept. |
00 on port 11 (or 0100 on port 10). The sensor stays joined.6Maintenance and removal
Battery
The battery is built in and lasts well over ten years. It cannot be replaced. Frequent reporting, a weak link and high spreading factors all shorten it. To get the most out of it:
- Mount Strips away from metal, within good reach of a gateway
- Report only what you need. The profiles in the Config Tool are tested for battery life.
- Keep the poll intervals at their defaults unless you need faster response
In the cold, the battery level can read lower than it really is. This is expected: the reading takes the temperature into account and does not show the real charge.
The battery is a lithium manganese dioxide (LiMnO₂) cell, one of the most stable lithium chemistries. Do not open the sensor, and do not puncture it or heat it above +80 °C. When the battery is empty, dispose of the whole sensor as a battery, for recycling. Near the end of its life the battery normally swells a little; this is expected.
Recalibrating the leak sensor
Calibrate again if the sensor was not on its plate, mounted and dry when it calibrated two hours after the join, or if you move it. Over time, dust and humidity can also make a dry sensor report some moisture, or even a false alarm. Make sure the pads are completely dry and the sensor is in its place. Then send the downlink 011900000000 on port 11, and send an uplink with the magnet. Check afterwards that the reported flood value is close to 0.
Removing Strips
Use dental floss or a thin string.
Moving to another network server
- Delete the device from the old network server.
- Reset Strips with the magnet.
- Register it in the new network server and join it again.
The settings stay in the sensor.
7Troubleshooting
| Problem | What to do |
|---|---|
| Joined, but no leak alarm | The leak alarm is off from the factory. Choose the Liquid Leak and Frost Alarm profile. |
| Leak alarm although it is dry | Recalibrate with the pads completely dry (downlink 011900000000 on port 11). If it happens again, raise the Flood Alarm Threshold Level: see Damp places. |
| No alarm although the pads are wet | Was the sensor wet, not on its plate or not yet mounted when it calibrated two hours after the join? Then the base level is wrong: dry the pads completely, mount it, and recalibrate with the downlink. |
| No alarm again after a leak | The pads are still drying. Allow at least 24 hours. |
| Can it detect oil? | No. Strips Drip Oil detects oil. |
| Join Request in the network server, but no Join Accept | Check the region, the LoRaWAN version (1.0.4), the regional parameters and the keys. In US915 and AU915, the network server must use the same sub-band as the gateway. |
| Nothing at all in the network server | Check that the gateway is on and online, and listed as connected. Check that Strips is in range and not on metal. Check that the region on the label matches the network server. Strips may still be joined to another network server: reset it with the magnet and try again. |
| "MIC mismatch" | The keys are wrong. Check that they belong to this sensor and are typed correctly. |
| "DevNonce too small" | Delete the device from the network server and add it again. Then reset Strips with the magnet and join again. |
| A new setting has no effect | Strips receives the downlink at its next message, up to 24 hours later. Send an uplink with the magnet to fetch it sooner, and look for status code 0300. On a busy network it can take several messages before the downlink gets through. |
| Messages missing or irregular | Check RSSI and SNR. The sensor may be too far from the gateway, or behind metal. Some channels can also be disturbed by interference on the same frequency band, for example from a nearby cellular transmitter or an RFID reader. In US915 and AU915, check that the sub-bands match. |
| Short green, then short red | Duty-cycle limit: the network server thinks the sensor sends too often. The message goes out later. |
| Battery shows 99 % on a new sensor | That is full, by design. |
| Keys missing | They are on a label in the box and were sent by e-mail. Contact Sensative if you need them in digital form. |
| The LED does not react to the magnet at all | The battery may be empty. Check the last battery level the network server received. The battery cannot be replaced, so an empty sensor has to be replaced. If the battery level was fine, contact Sensative support. |
8Technical reference
For integrators. The Strips LoRa Config Tool builds the downlinks, and the payload decoder reads the uplinks. Both are linked under Support.
Ports and factory settings
| Port 11 | Configuration downlinks from the Config Tool. 00 returns all settings to factory defaults. |
| Port 10 | Commands. 0100 also returns the settings to factory defaults. |
Port 10, 08XXXX | Leave the network and wait: 08XXXX, where XXXX is a number of minutes as two bytes in hex. Strips leaves the network and sends no new join request until that time has passed; for example 0805A0 waits 1 440 minutes (24 hours). Useful for joining sensors at the office to check them before they are shipped to a customer for mounting. |
| Factory settings | Heartbeat once every 24 hours. The leak alarm is off until you choose a profile. |
| Class and activation | LoRaWAN 1.0.4, regional parameters RP002-1.0.1, class A, OTAA |
Status codes
After a configuration downlink, Strips answers with one of these codes:
| Code | Meaning |
|---|---|
| 0300 | OK |
| 0301 | Bad settings |
| 0302 | Bad payload length |
| 0303 | Value not accepted |
| 0304 | Unknown command |
Reports
| Report | Content |
|---|---|
| Flood Alarm | Water detected: the flood value has passed the alarm level (confirmed) |
| Flood Report | The flood value, 0 = dry to 100 = soaked, at a set interval |
| Temperature Report / Alarm | Current temperature, and alarms at the low and high levels |
| Average Temperature Report / Alarm | Average over a set period, and alarms on the average |
| Battery Report | Battery level (%) |
Settings
The settings that apply to Strips Drip, as in the Config Tool.
| Setting | What it does | Range | Default |
|---|---|---|---|
| Flood Poll Interval | How often the leak (and oil) sensors are checked. 0 = off. | 0.5–60 min | 0.5 min |
| Flood Report Interval | How often the flood value is reported | 10–10080 min | 0 (off) |
| Flood Alarm Threshold Level | Flood value at which the leak alarm triggers | 0–100 % | 10 % |
| Flood Alarm Hysteresis | How far below the alarm level the flood value must fall before the alarm clears | 0–100 % | 4 % |
| Temperature Poll Interval | How often the temperature is read. 0 = off. | 0.5–60 min | 2 min |
| Temperature Send Immediately Threshold | Change from the last reported value that triggers a report | 0.1–60 °C | 2 °C |
| Temperature Low / High Alarm Level | Temperature at or beyond which the alarm triggers | −20 to +120 °C | off |
| Temperature Alarm Hysteresis | How far back the temperature must go before a new alarm can trigger | 0.1–60 °C | 1 °C |
| Average Temperature Time | How often the average temperature is sent | 10–10080 min | 1440 min |
| Average Temperature Low / High Alarm Level | Alarm levels for the average temperature | −20 to +60 °C | off |
| Magnet Poll Interval | How often the magnet sensors are checked. All other intervals are multiples of it. Lower is faster but uses more battery. | 1–10 s | 1.5 s |
| LED Level | 0 = very limited, 1 = user actions and errors, 2 = all events | 0–2 | 2 |
9Specifications
| Sensors | Water leak (absorbent pads), temperature |
| Alarms | Leak (configurable sensitivity), frost |
| Radio | LoRaWAN 1.0.4, class A, OTAA |
| Frequency plans | EU868 · US915 · AU915 · AS923 · KR920 · IN865 |
| Range | Up to 10 km in line of sight |
| Battery | Built-in LiMnO2, 480 mAh, well over ten years |
| IP rating | IP67, indoor and sheltered outdoor |
| Operating temperature | −20 to +60 °C |
| Dimensions | 195 × 15 × 6 mm: the 3 mm sensor plus the 3 mm pad plate |
| Mounting | Loose, adhesive, or screws through the plate; +Clip for rough or temporary surfaces |
10Support
- Strips LoRa Config Tool, which creates the configuration downlinks: strips-lora-config-app.service.sensative.net
- Payload decoder (open source): github.com/Sensative/strips-lora-translator-open-source
- Support, FAQ and downloads: sensative.com/support
- Product page and product sheet: sensative.com/sensors/strips-drip
- Technical support request: through the form on the support page
Sources: Sensative Docs, Strips for LoRaWAN pages, FAQ Strips LoRaWAN, Troubleshooting Guide Strips LoRaWAN and +Switch (read 24 October 2026); Strips LoRa Config Tool (profiles, reports and settings); Rev B datasheets; specifications from the sensative.com product data.