1Introduction
Strips Guard is a magnetic open/close sensor for LoRaWAN. It reports when a door, window, gate, cabinet or drawer opens or closes, and it also measures temperature. At under 3 mm thick it fits inside the frame, where nobody sees it. The electronics are conformally coated, so it can be used indoors and in sheltered places outdoors, including damp ones.
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. Where metal doors or frames block the radio while closed, it can work as a beacon: it then reports only while the door is open (see Beacon mode).
What's in the box
- Strips Guard, with the adhesive already on the back
- One or two magnets on the sensor. They keep it in transport mode until you start. Afterwards, one goes on the door or window.
- 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
- 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. If a closed metal door blocks the radio, use beacon mode.
- Frame or door: Strips can go on the frame (recommended) with the magnet on the door or window, or the other way round
- Hidden mounting: to hide Strips inside a door or window frame you need a gap of at least 3.5 mm
- Hinges and locks: make sure neither Strips nor the magnet is in the way when the door or window opens fully
3Step by step: from box to ready
Eight 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 step 3.
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.
After the first join, Strips sends the current state of its default reports: the door status and the tamper status. That is expected.
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 (optional)
Strips Guard is delivered ready to use: it reports the door status (unconfirmed), magnet tampering and a daily heartbeat, so many customers never change anything. Choose a profile only if you want something else:
| Profile in the Config Tool | What it does |
|---|---|
| Door Report | A report (unconfirmed) each time the door or window opens or closes. This matches the factory setting. |
| Door/Window Alarm | An alarm each time it opens or closes. Alarms are confirmed: Strips sends them again until the network server acknowledges them. |
| Door Counter | How many times the door was opened, reported once per interval (60 minutes by default). |
| Open Door Only Report | Beacon mode, for places where the radio cannot get through while the door is shut. See Beacon mode. |
| Custom Profile (Advanced) | Choose reports and settings yourself, for example temperature reports or temperature alarms. |
- Open the Strips LoRa Config Tool and choose Strips Multi-sensor +Guard.
- 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
- Clean both surfaces. They must be clean, dry and at least +10 °C.
- Try the position: hold Strips in place with a piece of ordinary tape, so you can still move it.
- Place the magnet opposite the square end of Strips (see the distances below). Close and open the door or window and check that the reports arrive. Adjust if needed.
- Check fully open and fully closed: the door or window must open and close freely, and every change must be reported.
- Mark the position of Strips and remove the tape. Peel the film off the adhesive on the back and press Strips firmly in place, exactly on the mark. Fix the magnet the same way.
Test
Open and close the door or window a few times and watch the messages in the network server or your application.
Ready
- Registered in the network server with the right region and keys
- Joined, and the messages are decoded
- Factory setting kept, or a profile confirmed with status code 0300
- Signal checked at the final spot
- Open and close both seen
- Mounted with the final adhesive, clear of hinges and locks, with no magnet near the rounded end
4Using the sensor
What it reports
- Open / closed: as a report or as an alarm, depending on the profile
- Tamper: when a magnet is held at both ends at once
- Temperature: reports, averages or alarms, if you turn them on
- Door count: with the Door Counter profile
- Battery level and heartbeat: once a day by default. A new sensor shows 99 %, which means full.
Beacon mode
Some doors and frames are metal, and a closed metal door can block the radio completely, for example in hotel rooms. In beacon mode (the Open Door Only Report profile), Strips stays quiet while the door is shut. While it is open, it sends a report every 5 minutes for the first 20 hours, and then once an hour. Your application can see from the reports that the door is open and for how long, for example to pause the air conditioning.
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. |
| Is it joined? | Hold the magnet at the square end | Short orange: joined and reporting the door. No blink: joined, but door reports are off. Long red: not joined. |
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 Magnet Poll Interval at its default 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.
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 |
|---|---|
| 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. |
| Joined, but no data | From the factory only the door status is reported, and only when it changes. Choose a profile for anything else. |
| 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 such as a heavy door. 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. Consider beacon mode for metal doors. |
| Door reports stop after mounting | If it worked before mounting: Strips may be on metal, or a nearby magnetised metal part may be disturbing the magnet's field. Check the magnet distances. |
| Tamper reports when the door moves | The magnet comes near both ends of Strips at once. Move the magnet so it only passes the square end. |
| 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 | Door report and tamper report on, heartbeat once every 24 hours |
| 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 |
|---|---|
| Door Report | Door closed or opened (unconfirmed) |
| Door Alarm | Door closed or opened (confirmed) |
| Door Count Report | How many times the door was opened. Also used in beacon mode. |
| Magnet Tampering Report / Alarm | A magnet at both ends at once |
| 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 |
| Temperature Door Report | Door status and temperature in one uplink |
| Battery Report | Battery level (%) |
Settings
The settings that apply to Strips Guard, as in the Config Tool.
| Setting | What it does | Range | Default |
|---|---|---|---|
| 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 |
| Door Alarm Invert | 1 = a magnet present means open instead of closed | 0–1 | 0 |
| Door Count Interval | Interval for door count reports | 10–10080 min | 60 min |
| 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 Send Immediately Threshold | Send an average only when it has changed this much | 0.1–60 °C | 0 (off) |
| Average Temperature Low / High Alarm Level | Alarm levels for the average temperature | −20 to +60 °C | off |
| Average Temperature Alarm Hysteresis | Hysteresis for the average alarms | 0.1–60 °C | 1 °C |
| LED Level | 0 = very limited, 1 = user actions and errors, 2 = all events | 0–2 | 2 |
9Specifications
| Sensors | Magnetic contact (open/close), temperature, tamper detection |
| Temperature accuracy | ±1 °C at 0–30 °C |
| Radio | LoRaWAN 1.0.4, class A, OTAA |
| Frequency plans | EU868 · US915 · AU915 · AS923 · IN865 · JP920 |
| 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 × 3 mm |
| Weight | 11 g |
| Mounting | Adhesive backing; +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-guard
- Technical support request: through the form on the support page
Sources: Sensative Docs, Strips Multi-sensor for LoRaWAN, FAQ Strips LoRaWAN and Troubleshooting Guide Strips LoRaWAN (read 24 October 2026); Strips LoRa Config Tool (profiles, reports and settings); datasheet Strips Guard LoRaWAN Rev B; specifications from the sensative.com product data.