Wireless sensors and Yggio, the open operational layer for cities, property owners and transport operators. Your data, your operations, your sovereignty.

LoRaWAN User and installation manual

Strips Guard for LoRaWAN

The ultra-thin door and window sensor for LoRaWAN. This manual takes you from the opened box to a sensor in service, and keeps the technical reference at the end.

Revision A · October 2026 · Sensative AB

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).

In the Strips LoRa Config Tool, this sensor is listed as Strips Multi-sensor +Guard.

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

Front and back of Strips: square end with LED, rounded end with antenna, label with region and DevEUI on the back
The square end (by the logo) has the LED, and the door magnet goes there. The rounded end holds the antenna, and it is where you give commands with a magnet. The label on the back shows the region and the DevEUI.

2Before you start

A LoRaWAN sensor needs a little more preparation than a sensor that pairs with a hub. Have this ready first:

Strips sends by radio to a gateway, the gateway to the network server, the network server to your application; settings go back as a downlink

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
Window with Strips in the frame and the magnet on the sash

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.

1

Unpack

Check that the sensor and its magnets are there, and find the keys. Leave the magnets on until step 3.

2

Register the sensor in the network server

  1. Add a new end device in your network server, with activation OTAA.
  2. 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.
  3. Enter the DevEUI, JoinEUI (AppEUI) and AppKey. Check them carefully: one wrong character and the join fails.
  4. Add the Strips payload decoder to the device or the application.
Done when: the device is listed in the network server, waiting for its first join.
3

Join the network

Take every magnet off the sensor. Strips leaves transport mode and sends a join request.

One or two magnets on Strips; take them all off and it 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.

Done when: a short green blink shows the join request was sent, and a few seconds later one long green blink confirms the join. The network server now shows the device as joined, with its first messages.
Five short red blinks means the join failed. See Troubleshooting: the usual causes are wrong keys, the wrong region or sub-band, or no gateway in range.

After the first join, Strips sends the current state of its default reports: the door status and the tamper status. That is expected.

4

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.

Good: the link must carry at least SF9. As a rule of thumb, look for an SNR above −5 dB and an RSSI above −115 dBm. That leaves a margin to the SF9 limit (about −12.5 dB SNR).
A weaker link forces the network server's adaptive data rate (ADR) onto SF10–SF12. Each message then takes much longer to send, which costs battery and capacity. If the sensor is still on SF10–SF12 a day after installation, improve the link.
If the message does not arrive, or arrives only now and then, move the gateway or the sensor, or add a gateway. Behind closed metal, consider beacon mode.
5

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 ToolWhat it does
Door ReportA report (unconfirmed) each time the door or window opens or closes. This matches the factory setting.
Door/Window AlarmAn alarm each time it opens or closes. Alarms are confirmed: Strips sends them again until the network server acknowledges them.
Door CounterHow many times the door was opened, reported once per interval (60 minutes by default).
Open Door Only ReportBeacon 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.
  1. Open the Strips LoRa Config Tool and choose Strips Multi-sensor +Guard.
  2. Choose a profile, check its reports and settings, and change a value if needed.
  3. Copy the payload the tool creates, and send it as a downlink on port 11 from your network server.
  4. 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.
Done when: Strips answers with status code 0300 (OK). Any other code means the setting was not accepted. See Status codes.
Without the magnet, Strips picks up the downlink at its next message, at the latest with the daily heartbeat. So a setting can take up to 24 hours to arrive, and on a busy network longer.
6

Install

  1. Clean both surfaces. They must be clean, dry and at least +10 °C.
  2. Try the position: hold Strips in place with a piece of ordinary tape, so you can still move it.
  3. 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.
  4. Check fully open and fully closed: the door or window must open and close freely, and every change must be reported.
  5. 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.
Closed: magnet under 10 mm from the square end or under 5 mm beside it. Open: at least 30 mm away
Closed: the magnet is less than 10 mm from the square end of Strips, or less than 5 mm beside it. Open: it must be at least 30 mm away.
Keep the magnet away from the rounded end. A magnet at both ends at once is read as tampering.
For rough or temporary surfaces, use the +Clip accessory (sold separately) instead of the adhesive.
7

Test

Open and close the door or window a few times and watch the messages in the network server or your application.

Done when: every open and every close arrives, with the right status. In beacon mode: a report arrives within 5 minutes of opening.
8

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.

Beacon mode needs firmware from February 2024 or later: R9 in the EU and R7 in the US. Contact Sensative technical support if you are unsure which firmware your sensors have.

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

ModeWhat it means
TransportMagnets on, deep sleep, almost no battery used. This is how Strips is delivered.
JoinedNormal operation: connected to the network and reporting.
ResendA confirmed message has not been acknowledged. Strips retries with longer and longer gaps.
StandbyNot 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

LEDMeaning
● Short greenA 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 greenJoined, reset or starting up
● Short orangeStrips is sending a report, or a join request when it is in standby
●● Orange, then redDuty-cycle limit: too many messages for the network. The message goes out a little later.
● 5 short redThe join failed. After a resend: the message still had no acknowledgement.
● 3 short redStrips sent a confirmed report, but got no acknowledgement (ACK) from the network server
● 2 short redA report was not sent, because Strips is in resend mode
● Long redThe 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.

Magnet moved to the rounded end of Strips and away, three times
CommandHowResult
Send an uplink / joinMagnet to the rounded end three times, for three green blinksA short extra green blink. If joined, Strips sends a message and picks up waiting downlinks. If not joined, it sends a join request.
ResetAs above, but on the third time hold the magnet at the rounded end for 10 secondsTwo long green blinks. Strips leaves the network and restarts. Its settings are kept.
Is it joined?Hold the magnet at the square endShort orange: joined and reporting the door. No blink: joined, but door reports are off. Long red: not joined.
Between each swipe, move the magnet about 20 cm away from Strips and wait 2 seconds before the next one. Too quick or too close, and Strips counts the swipes as one. Watch how it is done: wake-up and uplink (video) and reset (video).
The magnet reset does not clear the settings. To return the settings to factory defaults, send the downlink 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

Floss behind Strips, pulled along its length

Use dental floss or a thin string.

Moving to another network server

  1. Delete the device from the old network server.
  2. Reset Strips with the magnet.
  3. Register it in the new network server and join it again.

The settings stay in the sensor.

Once the sensor has joined, do not pack or store it with the magnets back on.

7Troubleshooting

ProblemWhat to do
Join Request in the network server, but no Join AcceptCheck 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 serverCheck 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 dataFrom the factory only the door status is reported, and only when it changes. Choose a profile for anything else.
A new setting has no effectStrips 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 irregularCheck 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 mountingIf 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 movesThe magnet comes near both ends of Strips at once. Move the magnet so it only passes the square end.
Short green, then short redDuty-cycle limit: the network server thinks the sensor sends too often. The message goes out later.
Battery shows 99 % on a new sensorThat is full, by design.
Keys missingThey 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 allThe 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 11Configuration downlinks from the Config Tool. 00 returns all settings to factory defaults.
Port 10Commands. 0100 also returns the settings to factory defaults.
Port 10, 08XXXXLeave 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 settingsDoor report and tamper report on, heartbeat once every 24 hours
Class and activationLoRaWAN 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:

CodeMeaning
0300OK
0301Bad settings
0302Bad payload length
0303Value not accepted
0304Unknown command

Reports

ReportContent
Door ReportDoor closed or opened (unconfirmed)
Door AlarmDoor closed or opened (confirmed)
Door Count ReportHow many times the door was opened. Also used in beacon mode.
Magnet Tampering Report / AlarmA magnet at both ends at once
Temperature Report / AlarmCurrent temperature, and alarms at the low and high levels
Average Temperature Report / AlarmAverage over a set period, and alarms on the average
Temperature Door ReportDoor status and temperature in one uplink
Battery ReportBattery level (%)

Settings

The settings that apply to Strips Guard, as in the Config Tool.

SettingWhat it doesRangeDefault
Magnet Poll IntervalHow often the magnet sensors are checked. All other intervals are multiples of it. Lower is faster but uses more battery.1–10 s1.5 s
Door Alarm Invert1 = a magnet present means open instead of closed0–10
Door Count IntervalInterval for door count reports10–10080 min60 min
Temperature Poll IntervalHow often the temperature is read. 0 = off.0.5–60 min2 min
Temperature Send Immediately ThresholdChange from the last reported value that triggers a report0.1–60 °C2 °C
Temperature Low / High Alarm LevelTemperature at or beyond which the alarm triggers−20 to +120 °Coff
Temperature Alarm HysteresisHow far back the temperature must go before a new alarm can trigger0.1–60 °C1 °C
Average Temperature TimeHow often the average temperature is sent10–10080 min1440 min
Average Temperature Send Immediately ThresholdSend an average only when it has changed this much0.1–60 °C0 (off)
Average Temperature Low / High Alarm LevelAlarm levels for the average temperature−20 to +60 °Coff
Average Temperature Alarm HysteresisHysteresis for the average alarms0.1–60 °C1 °C
LED Level0 = very limited, 1 = user actions and errors, 2 = all events0–22

9Specifications

SensorsMagnetic contact (open/close), temperature, tamper detection
Temperature accuracy±1 °C at 0–30 °C
RadioLoRaWAN 1.0.4, class A, OTAA
Frequency plansEU868 · US915 · AU915 · AS923 · IN865 · JP920
RangeUp to 10 km in line of sight
BatteryBuilt-in LiMnO2, 480 mAh, well over ten years
IP ratingIP67, indoor and sheltered outdoor
Operating temperature−20 to +60 °C
Dimensions195 × 15 × 3 mm
Weight11 g
MountingAdhesive backing; +Clip for rough or temporary surfaces

10Support

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.