Standard User Modes
Press me
Sends a message when the button is pressed. Can recognize various types of button presses - quite simple with many use cases ranging from security to eldercare.
Hex value: 0x01
Use cases: Security, order button, panic button, eldercare and more
Devices that support this mode: SimplePack and SimplePack Plus
Required sensors: Button
Mode-specific deltas:
Deltas are mode-specific register values different from register default values.
Register (hex) | Default (hex) | Delta (hex) | Delta information |
0x07 | 0x98 | 0x00 | Heartbeat 1 turned off |
Mode-specific events (uplink messages):
For more information on what uplink messages (mode-independent events) and additional data from various sensors in the device (appended payload) can be sent regardless of mode and how to fine-tune message behavior (alerts), see Mode-independent information and events.
Hex | Event name | Alert | Event information |
0x30 | Short press | 1 | Press lasting no more than 2 seconds |
0x31 | Double click | 3 | Two short presses with short (<1s) release in between |
0x32 | Long press | 2 | Press lasting more than 2 seconds and less than 6 seconds |
Registers relevant for this mode:
Hex | Register name | Default value (hex) |
0x59 | Button press timing threshold | 2 and 4 seconds (0x81) |
0x0E | Presets (Device control) | LED on - 10101001 (0xA9) |
Similar modes:
Hex | Mode name | Description |
0x14 | Press me WiFi | Basic WiFi-enabled version of Press me |
0x23 | Press me Wifi Atlas | WiFi Atlas version of Press me |
0x50 | Press me Wifi SuperLocal | WiFi SuperLocal version of Press me |
Switching to mode, arming and disarming information:
Follow the Basic Operations With SimpleHw Devices guide, where you can also find information about LED behavior, relevant Sigfox messages and more.
Here’s what’s important for Press me messages:
To set this mode, the downlink needs to include this mode register setting: 0101
The uplink messages need to begin with the mode hex as the first byte: 01
Press me does not require arming or disarming. This means the device will not send the following events: 0x10 (Start of arming), 0x11 (End of arming), 0x14 (Disarmed by long press).
Guard me
Guard me sends messages once the object moves, vibrates or changes position. After the alert is sent, the device is inert for the duration of the sleep time to prevent draining the battery.
Because of the way the accelerometer works, the device will not detect movement perpendicular to the ground nor the pull of the Earth’s gravity (this means that e.g. the smooth opening of office doors would not be reported - use the Door mode for this use case).
Hex value: 0x02
Use cases: Monitoring objects; security for both personal and commercial belongings
Devices that support this mode: SimplePack and SimplePack Plus
Required sensors: Accelerometer
Mode-specific deltas: None
Mode-specific events (uplink messages):
For more information on what uplink messages (mode-independent events) and additional data from various sensors in the device (appended payload) can be sent regardless of mode and how to fine-tune message behavior (alerts), see Mode-independent information and events.
Hex | Event name | Alert | Event information |
0x20 | Start of movement | 3 | Accelerometer-based movement detection |
Registers relevant for this mode:
If you change the general sensitivity of the accelerometer and the magnetometer (0x11 and 0x19), respective axis registers reset to 0 as the general settings replace them and vice versa.
Hex | Register name | Default value (hex) |
0x04 | Sleep time | 1 minute (0x41) |
0x11 | Accelerometer sensitivity | 7 (0x07) |
0x12 | Accelerometer X axis sensitivity | 7 (0x07) |
0x13 | Accelerometer Y axis sensitivity | 7 (0x07) |
0x14 | Accelerometer Z axis sensitivity | 7 (0x07) |
0x3C | Accelerometer measurement period | 1 second (0x01) |
0x49 | Accelerometer detection delay | 0 seconds (0x00) |
Similar modes:
Hex | Mode | Description |
0x03 | Track me | Sends messages when movement starts and stops |
0x04 | Trace me | Sends messages continuously while moving |
0x05 | Monitor me | Records precise movement and sends the data periodically, great for monitoring vibration occurrence and duration |
0x09 | Door mode | Combines accelerometer and magnetometer in order to detect smooth opening of any door that’s not vibrating while moving |
0x15 | Guard me WiFi | Basic WiFi-enabled version of Guard me |
0x27 | Guard me Wifi Atlas | WiFi Atlas version of Guard me |
0x51 | Guard me WiFi SuperLocal | WiFi SuperLocal version of Guard me |
Switching to mode, arming and disarming information:
Follow the Basic Operations With SimpleHw Devices guide, where you can also find information about LED behavior, relevant Sigfox messages and more.
Here’s what’s important for Guard me messages:
To set this mode, the downlink needs to include this mode register setting: 0102
The uplink messages need to begin with the mode hex as the first byte: 02
When arming the device, you should see this message: 0210
When the device is armed, it should send you these two bytes: 0211
If you disarm the device via long press, you should receive this message: 0214
Track me
Track me sends a message when the monitored object starts moving and also sends one when the movement stops and the device does not move for an adjustable time period.
Hex value: 0x03
Use cases: Tracking luggage, parcels, containers etc.
Devices that support this mode: SimplePack and SimplePack Plus
Required sensors: Accelerometer
Mode-specific deltas:
Deltas are mode-specific register values different from register default values.
Register (hex) | Default (hex) | Delta (hex) | Delta information |
Sleep time (0x04) | 1 minute (0x41) | 0 (0x00) | Sleep time turned off |
Uplink messages (events) used in this mode:
For more information on what uplink messages (mode-independent events) and additional data from various sensors in the device (appended payload) can be sent regardless of mode and how to fine-tune message behavior (alerts), see Mode-independent information and events.
Hex | Event name | Alert | Event information |
0x20 | Start of movement | 1 | Accelerometer-based movement detection |
0x21 | End of movement | 2 | Arrival delay countdown expired |
Registers relevant for this mode:
If you change the general sensitivity of the accelerometer and the magnetometer (0x11 and 0x19), respective axis registers reset to 0 as the general settings replace them and vice versa.
Hex | Register name | Default value (hex) |
0x02 | Departure delay | 15 seconds (0x0F) |
0x03 | Arrival delay | 10 minutes (0x4A) |
0x11 | Accelerometer sensitivity | 7 (0x07) |
0x12 | Accelerometer X axis sensitivity | 7 (0x07) |
0x13 | Accelerometer Y axis sensitivity | 7 (0x07) |
0x14 | Accelerometer Z axis sensitivity | 7 (0x07) |
0x3C | Accelerometer measurement period | 1 second (0x01) |
0x49 | Accelerometer detection delay | 0 seconds (0x00) |
Similar modes:
Hex | Mode name | Description |
0x02 | Guard me | Sends accelerometer-triggered movement alerts |
0x04 | Trace me | Sends messages continuously while moving |
0x05 | Monitor me | Records precise movement and sends the data periodically, great for monitoring vibration occurrence and duration |
0x16 | Track me WiFi | Basic WiFi-enabled version of Track me |
0x2B | Track me WiFi Atlas | WiFi Atlas version of Track me |
0x52 | Track me WiFi SuperLocal | WiFi SuperLocal version of Track me |
Switching to mode, arming and disarming information:
Follow the Basic Operations With SimpleHw Devices guide, where you can also find information about LED behavior, relevant Sigfox messages and more.
Here’s what’s important for Track me messages:
To set this mode, the downlink needs to include this mode register setting: 0103
The uplink messages need to begin with the mode hex as the first byte: 03
When arming the device, you should see this message: 0310
When the device is armed, it should send you these two bytes: 0311
If you disarm the device via long press, you should receive this message: 0314
Trace me
Trace me sends messages while the object is moving and stops sending them when it’s still. While moving, it periodically sends a message (the period length is defined in the Tracing delay register) so you can trace the monitored object. No more messages are sent after stop of movement is detected and reported.
Hex symbol: 0x04
Use cases: Package tracing for postal services, tracing international trucks, river transport boats and more
Devices that support this mode: SimplePack and SimplePack Plus
Required sensors: Accelerometer
Mode-specific deltas:
Deltas are mode-specific register values different from default register values.
Register (hex) | Default (hex) | Delta (hex) | Delta information |
Sleep time (0x04) | 1 minute (0x41) | 10 minutes (0x4A) | Sleep time prolonged |
Mode-specific events (uplink messages):
For more information on what uplink messages (mode-independent events) and additional data from various sensors in the device (appended payload) can be sent regardless of mode and how to fine-tune message behavior (alerts), see Mode-independent information and events.
Hex | Event name | Alert | Event information |
0x20 | Start of movement | 1 | Accelerometer-based movement detection |
0x21 | End of movement | 2 | Arrival delay countdown expired, no movement detected anymore |
0x22 | Tracing tag | 3 | Periodical event sent only while moving |
Registers relevant for this mode:
If you change the general sensitivity of the accelerometer and the magnetometer (0x11 and 0x19), respective axis registers reset to 0 as the general settings replace them and vice versa.
Hex | Register name | Default value (hex) |
0x02 | Departure delay | 15 seconds (0x0F) |
0x03 | Arrival delay | 10 minutes (0x4A) |
0x04 | Sleep time | 1 minute (0x41) |
0x05 | Tracing interval | 10 minutes (0x4A) |
0x11 | Accelerometer sensitivity | 7 (0x07) |
0x12 | Accelerometer X axis sensitivity | 7 (0x07) |
0x13 | Accelerometer Y axis sensitivity | 7 (0x07) |
0x14 | Accelerometer Z axis sensitivity | 7 (0x07) |
0x3C | Accelerometer measurement period | 1 second (0x01) |
0x49 | Accelerometer detection delay | 0 seconds (0x00) |
Similar modes:
Hex | Mode name | Description |
0x02 | Guard me | Sends accelerometer-triggered movement alerts |
0x03 | Track me | Sends messages when movement starts and stops |
0x05 | Monitor me | Records precise movement and sends the data periodically, great for monitoring vibration occurrence and duration |
0x17 | Trace me WiFi | Basic WiFi-enabled version of Trace me |
0x2F | Trace me WiFi Atlas | WiFi Atlas version of Trace me |
0x53 | Trace me WiFi SuperLocal | WiFi SuperLocal version of Trace me |
Switching to mode, arming and disarming information:
Follow the Basic Operations With SimpleHw Devices guide, where you can also find information about LED behavior, relevant Sigfox messages and more.
Here’s what’s important for Trace me messages:
To set this mode, the downlink needs to include this mode register setting: 0104
The uplink messages need to begin with the mode hex as the first byte: 04
When arming the device, you should see this message: 0410
When the device is armed, it should send you these two bytes: 0411
If you disarm the device via long press, you should receive this message: 0414
Monitor me
Using the accelerometer, this mode monitors occurrence of vibration and periodically reports when the monitored object was vibrating and when it was not in a predefined time window.
Hex value: 0x05
Use cases: Monitoring usage of engines, heavy machinery, factory robots and more
Devices that support this mode: SimplePack and SimplePack Plus
Required sensors: Accelerometer
Mode-specific deltas: None
Mode-specific events (uplink messages):
For more information on what uplink messages (mode-independent events) and additional data from various sensors in the device (appended payload) can be sent regardless of mode and how to fine-tune message behavior (alerts), see Mode-independent information and events.
Hex | Event name | Alert | Event information |
0x80 | Monitor me | 1 | Sends vibration data in 10 bytes of the payload* |
*Each of the 10 bytes in the payload that come after mode and event (after 0580) represents a time window. One bit represents one second, one byte represents up to 255 seconds. The number you receive is the number of seconds in this time window (max 0xFF - 255) when vibration was detected by the device. This means you can determine the intensity of vibration in % in the given time interval.
The Monitor me uplink event is received after the payload is full. This means that in default settings, the first message will come after 42:30 minutes (10 bytes, 255 seconds each, total of 2550 seconds). This interval can be prolonged with register 0x3C (Accelerometer measurement interval) - the default setting is 1 second. E.g. two seconds would make this interval 42:30 x 2 = 85 minutes.
Registers relevant for this mode:
If you change the general sensitivity of the accelerometer and the magnetometer (0x11 and 0x19), respective axis registers reset to 0 as the general settings replace them and vice versa.
Hex | Register name | Default value (hex) |
0x11 | Accelerometer sensitivity | 7 (0x07) |
0x12 | Accelerometer X axis sensitivity | 7 (0x07) |
0x13 | Accelerometer Y axis sensitivity | 7 (0x07) |
0x14 | Accelerometer Z axis sensitivity | 7 (0x07) |
0x3C | Accelerometer measurement interval | 1 second (0x01) |
0x49 | Accelerometer detection delay | 0 seconds (0x00) |
0x4F | Monitor me measurement window | 20 milliseconds (0x14) |
Similar modes:
Hex | Mode name | Description |
0x02 | Guard me | Sends accelerometer-triggered movement alerts |
0x09 | Door mode | Combines accelerometer and magnetometer in order to detect smooth opening of any door that’s not vibrating while moving |
Switching to mode, arming and disarming information:
Follow the Basic Operations With SimpleHw Devices guide, where you can also find information about LED behavior, relevant Sigfox messages and more.
Here’s what’s important for Monitor me messages:
To set this mode, the downlink needs to include this mode register setting: 0105
The uplink mess
ages need to begin with the mode hex as the first byte: 05
When arming the device, you should see this message: 0510
When the device is armed, it should send you these two bytes: 0511
If you disarm the device via long press, you should receive this message: 0514
Put me back
Reports movement of an object and once the movement stops, reports precise position through accelerometer data. You can use the data to determine whether the object was displaced or not.
Hex value: 0x06
Use cases: Manholes, containers, lab doors, safe boxes, fire extinguisher cabinets, poles and more
Devices that support this mode: SimplePack and SimplePack Plus
Required sensors: Accelerometer
Mode-specific deltas:
Deltas are mode-specific register values different from register default values.
Register (hex) | Default (hex) | Delta (hex) | Delta information |
Arrival delay (0x03) | 10 minutes (0x4A) | 1 minute (0x41) | Arrival delay decreased |
Mode-specific events (uplink messages):
For more information on what uplink messages (mode-independent events) and additional data from various sensors in the device (appended payload) can be sent regardless of mode and how to fine-tune message behavior (alerts), see Mode-independent information and events.
Hex | Event name | Alert | Event information |
0x20 | Start of movement | 1 | When the device moves, this message is sent |
0x21 | End of movement | 2 | When movement stops and arrival delay expires, this message is sent with appended accelerometer data in 9 bytes |
Registers relevant for this mode:
If you change the general sensitivity of the accelerometer and the magnetometer (0x11 and 0x19), respective axis registers reset to 0 as the general settings replace them and vice versa.
Hex | Register name | Default value (hex) |
0x04 | Sleep time | 1 minute (0x41) |
0x11 | Accelerometer sensitivity | 7 (0x07) |
0x12 | Accelerometer X axis sensitivity | 7 (0x07) |
0x13 | Accelerometer Y axis sensitivity | 7 (0x07) |
0x14 | Accelerometer Z axis sensitivity | 7 (0x07) |
0x3C | Accelerometer measurement period | 1 seconds (0x01) |
0x49 | Accelerometer detection delay | 0 seconds (0x00) |
Similar modes:
Hex | Mode name | Description |
0x02 | Guard me | Sends accelerometer-triggered movement alerts |
0x09 | Door mode | Combines accelerometer and magnetometer in order to detect smooth opening of any door that’s not vibrating while moving |
Switching to mode, arming and disarming information:
Follow the Basic Operations With SimpleHw Devices guide, where you can also find information about LED behavior, relevant Sigfox messages and more.
Here’s what’s important for Put me back messages:
To set this mode, the downlink needs to include this mode register setting: 0106
The uplink messages need to begin with the mode hex as the first byte: 06
When arming the device, you should see this message: 0610
When the device is armed, it should send you these two bytes: 0611
If you disarm the device via long press, you should receive this message: 0614
Don’t drop me
Don’t drop me behaves similarly to Guard me except for its event (uplink message) is triggered by faster acceleration of the accelerometer in one of its axis and not just movement detection. Drop alert detection threshold can be defined.
Please note this mode should not be used on boards with an opto pin (SimpleIndustry with 2 external sensors) because of accelerometer consumption. Please contact us at ask.simplehw.eu for more information.
Hex value: 0x07
Use cases: Monitoring packages inside trucks, shipping containers and more
Devices that support this mode: SimplePack and SimplePack Plus
Required sensors: Accelerometer
Mode-specific deltas: None
Mode-specific events (uplink messages):
For more information on what uplink messages (mode-independent events) and additional data from various sensors in the device (appended payload) can be sent regardless of mode and how to fine-tune message behavior (alerts), see Mode-independent information and events.
Hex | Event name | Alert | Event information |
0x20 | Start of movement | no | Accelerometer-based movement detection |
0x21 | End of movement | no | Arrival delay countdown expired |
0x22 | Tracing tag | no | Sends a periodical message when moving |
0x23 | Drop alert | 3 | Sends a message when dropped - high acceleration |
Registers relevant for this mode:
If you change the general sensitivity of the accelerometer and the magnetometer (0x11 and 0x19), respective axis registers reset to 0 as the general settings replace them and vice versa.
Hex | Register name | Default value (hex) |
0x02 | Departure delay | 15 seconds (0x0F) |
0x03 | Arrival delay | 10 minutes (0x4A) |
0x04 | Sleep time | 1 minute (0x41) |
0x05 | Tracing interval | 10 minutes (0x4A) |
0x11 | Accelerometer sensitivity | 7 (0x07) |
0x12 | Accelerometer X axis sensitivity | 7 (0x07) |
0x13 | Accelerometer Y axis sensitivity | 7 (0x07) |
0x14 | Accelerometer Z axis sensitivity | 7 (0x07) |
0x15 | Don’t drop me threshold | 1920 mG (0x60) |
0x16 | Don’t drop me duration | 200 ms (0x02) |
0x17 | Don’t drop me axis configuration | 7 (0x07)* |
0x3C | Accelerometer measurement period | 1 second (0x01) |
0x49 | Accelerometer detection delay | 0 seconds (0x00) |
*4 upper bits of register 0x17 determine which Don’t drop me submode the device will be in. The other 4 (lower) bits determine the accelerometer sensitivity (similar to register 0x11).
Don’t drop me submodes:
SHOCK
0x17 value: 0x07
Behavior: Don’t drop event is sent when acceleration is detected above the Don’t drop me threshold (register 0x15) for longer than Don’t drop me the duration (0x16)
Accelerometer configuration: ODR 100Hz
0x15 units: 1 LSb = 32 mg, range is ±4G
0x16 units: 1/ODR
FREE FALL
0x17 value: 0x47
Behavior: Don’t drop event is sent when acceleration is detected below the Don’t drop me threshold (register 0x15) for longer than the Don’t drop me duration (0x16)
Accelerometer configuration: ODR 25Hz
0x15 units: 1 LSb = 16 mg, range is ±2G
0x16 units: 1/ODR
CLICK
0x17 value: 0x87
Behavior: Don’t drop event is sent when acceleration is detected above the Don’t drop me threshold (register 0x15) for no longer than the Don’t drop me duration (0x16)
Accelerometer configuration: ODR 100Hz
0x15 units: 1 LSb = 32 mg, range is ±4G
0x16 units: 1/ODR
Similar modes:
Hex | Mode | Description |
0x02 | Guard me | Sends accelerometer-triggered movement alerts |
Switching to mode, arming and disarming information:
Follow the Basic Operations With SimpleHw Devices guide, where you can also find information about LED behavior, relevant Sigfox messages and more.
Here’s what’s important for Don’t drop me messages:
To set this mode, the downlink needs to include this mode register setting: 0107
The uplink messages need to begin with the mode hex as the first byte: 07
When arming the device, you should see this message: 0710
When the device is armed, it should send you these two bytes: 0711
If you disarm the device via long press, you should receive this message: 0714
Reed switch on/off with redundancy
Sends a timeline of when and how long the reed contact was opened and when and how long it was closed, 8 time periods are sent in total. Useful for creating a history of e.g. door usage and more.
Hex value: 0x08
Use cases: History of door usage mostly (or anything where you can use the binary reed switch on/off functionality)
Devices that support this mode: SimplePack and SimplePack Plus
Required sensors: Reed switch
Mode-specific deltas:
Deltas are mode-specific register values different from register default values.
Register (hex) | Default (hex) | Delta (hex) | Delta information |
0x4B | 0x00 | 0x05 | Detection delay 5s |
0x04 | 0x4A | 0x00 | Sleep time 0s |
Uplink messages (events) used in this mode:
For more information on what uplink messages (mode-independent events) and additional data from various sensors in the device (appended payload) can be sent regardless of mode and how to fine-tune message behavior (alerts), see Mode-independent information and events.
Hex | Event name | Alert | Event information |
0x83 | Reed switch on/off with redundancy | 1 | Reed switch on/off with redundancy |
Registers relevant for this mode:
Hex | Register name | Default value (hex) |
0x37 | Reed switch measurement period | 1 second (0x01) |
0x4B | Reed switch detection delay | 0 seconds (0x00) |
Similar modes:
Hex | Mode | Description |
0x0C | Reed switch on/off | Sends a message when the reed opens and also when closes |
0x13 | Reed switch counter | Counts reed switches, various settings |
Switching to mode, arming and disarming information:
Follow the Basic Operations With SimpleHw Devices guide, where you can also find information about LED behavior, relevant Sigfox messages and more.
Here’s what’s important for Reed switch on/off with redundancy messages:
To set this mode, the downlink needs to include this mode register setting: 0108
The uplink messages need to begin with the mode hex as the first byte: 08
When arming the device, you should see this message: 0810
When the device is armed, it should send you these two bytes: 0811
If you disarm the device via long press, you should receive this message: 0814
Door mode (based on compass and not reed switch)
Detects doors opening and closing using the accelerometer and the magnetometer.
Hex value: 0x09
Use cases: Monitoring various doors; offices, cabinets, entrances and more
Devices that support this mode: SimplePack
Required sensors: Accelerometer, magnetometer
Mode-specific deltas: None
Mode-specific events (uplink messages):
For more information on what uplink messages (mode-independent events) and additional data from various sensors in the device (appended payload) can be sent regardless of mode and how to fine-tune message behavior (alerts), see Mode-independent information and events.
Hex | Event name | Alert | Event information |
0x20 | Start of movement | 3 | Accelerometer-based movement detection |
0x24 | Start of movement 2 | 2 | Magnetometer-based movement detection |
Registers relevant for this mode:
Hex | Register name | Default value (hex) |
0x11 | Accelerometer sensitivity | 7 (0x07) |
0x19 | Magnetometer sensitivity | 4 (0x04) |
0x3C | Accelerometer measurement interval period | 1 second (0x01) |
0x3D | Magnetometer measurement interval period | 1 second (0x01) |
0x49 | Accelerometer detection delay | 0 seconds (0x00) |
0x4A | Magnetometer detection delay | 0 seconds (0x00) |
Similar modes:
Hex | Mode | Description |
0x02 | Guard me | Sends accelerometer-triggered movement alerts |
0x05 | Monitor me | Records precise movement and sends the data periodically, great for monitoring vibration occurrence and duration |
Switching to mode, arming and disarming information:
Follow the Basic Operations With SimpleHw Devices guide, where you can also find information about LED behavior, relevant Sigfox messages and more.
Here’s what’s important for Door mode messages:
To set this mode, the downlink needs to include this mode register setting: 0109
The uplink messages need to begin with the mode hex as the first byte: 09
When arming the device, you should see this message: 0910
When the device is armed, it should send you these two bytes: 0911
If you disarm the device via long press, you should receive this message: 0914
Leak detector
This mode lets you know when a water leak has occurred and also when water is no longer detected. Position is monitored and any tilt over a predefined threshold (up to 180 degrees) is reported. If the device returns to the original position, the device will send a message too.
Leak detector is only for the SimpleLeak! No other device works properly in this mode.
Hex value: 0x0A
Use cases: Bathrooms, kitchens, industrial spaces, transport, laboratories and more
Devices that support this mode: SimpleLeak
Required sensors: Water leak detector and accelerometer
Mode-specific deltas:
Deltas are mode-specific register values different from register default values.
Register (hex) | Default (hex) | Delta (hex) | Delta information |
0x0E | 0xA9 | 0xE9 | Beeper enabled |
0x0F | 0x06 | 0x07 | Start of arming alert requests downlink |
0x11 | 0x07 | 0x40 | Accelerometer sensitivity decreased to 40 |
0x23 | 0x04 | 0x02 | Alert 1 indicated by beeping |
0x24 | 0x00 | 0x4A | Alert 1 repeated every 10 minutes |
0x25 | 0x00 | 0x05 | Alert 1 repeated 5 times |
0x26 | 0x04 | 0x02 | Alert 2 indicated by beeping |
0x2C | 0x00 | 0x1E | Alert 1 delay set to 30 seconds |
0x2D | 0x00 | 0x0A | Alert 2 delay set to 10 seconds |
0x34 | 0x00 | 0x43 | Temperature measured every 3 minutes |
0x48 | 0x00 | 0x1E | Leakage detection delay set to 30 seconds |
0x49 | 0x00 | 0x0A | Accelerometer detection delay set to 10 seconds |
Uplink messages (events) used in this mode:
For more information on what uplink messages (mode-independent events) and additional data from various sensors in the device (appended payload) can be sent regardless of mode and how to fine-tune message behavior (alerts), see Mode-independent information and events.
Hex | Event name | Alert | Event information |
0x40 | Leakage | 1 | Sent when water is detected |
0x41 | End of leakage | No | Send when water is no longer detected |
0x42 | Wrong orientation | 2 | Sent when the tilt threshold is exceeded |
0x43 | End of wrong orientation | No | Sent when the position is fixed |
Registers relevant for this mode:
Hex | Register name | Default value (hex) |
0x0E | Device control presets | 0xA9 |
0x0F | Activation/Confirmation | 0x06 |
0x11 | Accelerometer sensitivity | 0x07 |
0x23 | Alert 1 configuration | 0x04 |
0x24 | Alert 1 repetition interval | 0x00 |
0x25 | Alert 1 number of repetitions | 0x00 |
0x26 | Alert 2 configuration | 0x04 |
0x2C | Alert 1 delay | 0x00 |
0x2D | Alert 2 delay | 0x00 |
0x34 | Temperature measurement interval period | 0x00 |
0x35 | Leakage measurement interval period | 0x03 |
0x3C | Accelerometer measurement interval period | 0x01 |
0x3E | Tilt detection | 0x00 |
0x45 | Leak detector filter | 0x55 |
0x48 | Leak detector detection delay | 0x00 |
0x49 | Accelerometer detection delay | 0x00 |
Similar modes: None
Switching to mode, arming and disarming information:
Follow the Basic Operations With SimpleHw Devices guide, where you can also find information about LED behavior, relevant Sigfox messages and more.
Here’s what’s important for Leak detector messages:
To set this mode, the downlink needs to include this mode register setting: 010A
The uplink messages need to begin with the mode hex as the first byte: 0A
When arming the device, you should see this message: 0A10
When the device is armed, it should send you these two bytes: 0A11
If you disarm the device via long press, you should receive this message: 0A14
Demo mode
A mode created to literally show off. Will send some mode-specific events from Press me (0x01) and all mode-specific events from Don’t drop me (0x07), Reed on/off (0x0C) and Light on/off (0x0D) together with appended payload with voltage, temperature and accelerometer data. WiFi is used in one event.
Hex value: 0x0B
Use cases: Demos and shows - but will cover anything that requires the data this mode can send you
Devices that support this mode: SimplePack Plus
Required sensors: Button, WiFi module, reed switch, light sensor, accelerometer, either temp sensor
Mode-specific deltas:
Deltas are mode-specific register values different from register default values.
Register (hex) | Default (hex) | Delta (hex) | Delta information |
0x0E | 0xA9 | 0xE9 | Beeper ON, button active all the time |
0x3D | 0x01 | 0x00 | Magnetometer turned off |
0x36 | 0x00 | 0x05 | Light sensor turned on |
0x04 | 0x41 | 0x00 | Sleep time turned off |
0x0D | 0x00 | 0xE0 | Voltage, temperature, accelerometer data sent as appended payload |
Uplink messages (events) used in this mode:
For more information on what uplink messages (mode-independent events) and additional data from various sensors in the device (appended payload) can be sent regardless of mode and how to fine-tune message behavior (alerts), see Mode-independent information and events.
Hex | Event name | Alert | Event information |
0x23 | Drop alert | 1 | Sends a message when dropped - high acceleration |
0x30 | Short press | 1 | Press lasting no more than 2 seconds |
0x60 | Light detected | 1 | Light % exceeded light detection threshold |
0x61 | Darkness detected | 1 | Light % fell below light detection threshold |
0x62 | Reed switch on | 1 | Reed switch on - magnet present |
0x63 | Reed switch off | 1 | Reed switch off - no magnet |
0x9E | Double click WiFi 1/2 | 1 | Two short presses within 1 second, sent with 3 MAC addresses |
0x9F | Double click WiFi 2/2 | 1 |
Registers relevant for this mode (tbd):
Hex | Register name | Default value (hex) |
0x11 | Accelerometer sensitivity | 7 (0x07) |
0x12 | Accelerometer X axis sensitivity | 7 (0x07) |
0x13 | Accelerometer Y axis sensitivity | 7 (0x07) |
0x14 | Accelerometer Z axis sensitivity | 7 (0x07) |
0x15 | Drop me threshold | 936 mG (0x60) |
0x16 | Drop me duration | 200 ms (0x02) |
0x17 | Drop me axis configuration | 7 (0x07) |
0x36 | Light sensor measurement period | 0 seconds (0x00), delta: 5 seconds (0x05) |
0x3C | Accelerometer measurement period | 1 second (0x01) |
0x43 | Light sensitivity hysteresis | 5% of light (0x05) |
0x44 | Light sensitivity threshold | 30% of light (0x1A) |
0x49 | Accelerometer detection delay | 0 seconds (0x00) |
0x4B | Reed contact detection delay | 0x00 |
0x4C | Light sensor detection delay | 0 seconds (0x00) |
0x59 | Button press timing threshold | 2 and 4 seconds (0x81) |
Similar modes:
Hex | Mode name | Description |
0x01 | Press me | Recognizes various button presses |
0x07 | Don’t drop me | Sends a message triggered by faster acceleration of the accelerometer in one of its axis |
0x0C | Reed switch on/off | Sends messages when a magnet is present or absent |
0x0D | Light on/off | Sends messages based on light % thresholds |
0x14 | Press me WiFi | Basic WiFi-enabled version of Press me |
Switching to mode, arming and disarming information:
Follow the Basic Operations With SimpleHw Devices guide, where you can also find information about LED behavior, relevant Sigfox messages and more.
Here’s what’s important for Demo mode messages:
To set this mode, the downlink needs to include this mode register setting: 010B
The uplink messages need to begin with the mode hex as the first byte: 0B
When arming the device, you should see this message: 0B10
When the device is armed, it should send you these two bytes: 0B11
If you disarm the device via long press, you should receive this message: 0B14
Reed switch on/off
Sends a message when the reed contact is switched on by a magnet and also sends one when the sensor is switched off because the nearby magnetic field is no longer detected.
Hex value: 0x0C
Use cases: Garage doors, warehouse doors, fridges, anything where reporting contact is important
Devices that support this mode: SimplePack and SimplePack Plus
Please note that in the SimplePack 4.0 Plus Magnetic Switch, the device is shipped in this mode (armed) without the possibility to disarm the device by long press. Triggering downlinks with an extra long press is still enabled (you can disarm the device with downlink).
Required sensors: Reed switch
Mode-specific deltas:
Deltas are mode-specific register values different from register default values.
Register (hex) | Default (hex) | Delta (hex) | Delta information |
0x04 | 0x41 | 0x06 | Sleep time decreased to 6 seconds |
Uplink messages (events) used in this mode:
For more information on what uplink messages (mode-independent events) and additional data from various sensors in the device (appended payload) can be sent regardless of mode and how to fine-tune message behavior (alerts), see Mode-independent information and events.
Hex | Event name | Alert | Event information |
0x62 | Reed switch on | 1 | Reed switch on because of magnet presence |
0x63 | Reed switch off | 2 | Reed switch off because of magnet absence |
Registers relevant for this mode:
Hex | Register name | Default value (hex) |
0x37 | Reed switch measurement period | 1 second (0x01) |
0x4B | Reed switch detection delay | 0 seconds (0x00) |
Similar modes:
Hex | Mode name | Description |
0x08 | Reed switch on/off with redundancy | Sends a history of reed switches in one event |
0x13 | Reed switch counter | Counts reed switches, various settings |
0x19 | Reed switch on/off WiFi | Basic WiFi-enabled version of Reed switch on/off |
0x37 | Reed switch on/off WiFi Atlas | WiFi Atlas version of Reed switch on/off |
0x55 | Reed switch on/off WiFi SuperLocal | WiFi SuperLocal version of Reed switch on/off |
Switching to mode, arming and disarming information:
Follow the Basic Operations With SimpleHw Devices guide, where you can also find information about LED behavior, relevant Sigfox messages and more.
Here’s what’s important for Reed switch on/off messages:
To set this mode, the downlink needs to include this mode register setting: 010C
The uplink messages need to begin with the mode hex as the first byte: 0C
When arming the device, you should see this message: 0C10
When the device is armed, it should send you these two bytes: 0C11
If you disarm the device via long press, you should receive this message: 0C14
Light on/off
Detects light - a message is sent every time a predefined threshold (% of light detected) is crossed either way. Can be set up to detect a very low light percentage threshold - darkness and extreme darkness (useful for monitoring package opening in the night).
Hex value: 0x0D
Use cases: Monitoring electricity usage, buildings and rooms, detecting opening of packages, freezers, safeboxes etc. and more
Devices that support this mode: SimplePack and SimplePack Plus
Required sensors: Light sensor
Mode-specific deltas:
Deltas are mode-specific register values different from register default values.
Register (hex) | Default (hex) | Delta (hex) | Delta information |
0x04 | 0x41 | 0x06 | Sleep time decreased |
0x36 | 0x00 | 0x05 | Light detection on |
Mode-specific events (uplink messages):
For more information on what uplink messages (mode-independent events) and additional data from various sensors in the device (appended payload) can be sent regardless of mode and how to fine-tune message behavior (alerts), see Mode-independent information and events.
Hex | Event name | Alert | Event information |
0x60 | Light detected | 1 | Light % over predefined threshold |
0x61 | Darkness detected | 2 | Light % under predefined threshold |
Registers relevant for this mode:
Hex | Register name | Default value (hex) |
0x36 | Light sensor measurement period | 0 seconds (0x00), delta: 5 seconds (0x05) |
0x43 | Light sensitivity hysteresis | 5% of light (0x05) |
0x44 | Light sensitivity threshold | 30% of light (0x1E) |
0x4C | Light sensor detection delay | 0 seconds (0x00) |
Similar modes:
Hex | Mode name | Description |
0x1A | Light on/off WiFi | Basic WiFi-enabled version of Light on/off |
0x3B | Light on/off WiFi Atlas | WiFi Atlas version of Light on/off |
0x56 | Light on/off WiFi Precise | WiFi Precise version of Light on/off |
Switching to mode, arming and disarming information:
Follow the Basic Operations With SimpleHw Devices guide, where you can also find information about LED behavior, relevant Sigfox messages and more.
Here’s what’s important for Light on/off messages:
To set this mode, the downlink needs to include this mode register setting: 010D
The uplink messages need to begin with the mode hex as the first byte: 0D
When arming the device, you should see this message: 0D10
When the device is armed, it should send you these two bytes: 0D11
If you disarm the device via long press, you should receive this message: 0D14
Temperature threshold with redundancy
Intended for long-term monitoring of temperature exception occurrences - in this mode, temperature exception is defined as temperature above or below the three predefined temperature thresholds A, B and C. Will send an event with 5 exceptions and the duration of each exception. Every exception with its duration will take up two bytes of the payload for a total of 12 bytes. The thresholds are encoded in SimpleTemp.
Hex value: 0x0E
Use cases: Long-term monitoring of temperature in any environment; labs, freezers, pools and more
Devices that support this mode: SimplePack and SimplePack Plus
Required sensors: Either temperature sensor (ambi or precise, precise is preferable)
Mode-specific deltas:
Deltas are mode-specific register values different from register default values.
Register (hex) | Default (hex) | Delta (hex) | Delta information |
0x34 | 0x00 | 0x43 | Temperature measuring turned on |
Mode-specific events (uplink messages):
For more information on what uplink messages (mode-independent events) and additional data from various sensors in the device (appended payload) can be sent regardless of mode and how to fine-tune message behavior (alerts), see Mode-independent information and events.
Hex | Event name | Alert | Event information |
0x84 | Temperature threshold pipeline | 1 | Timeline of 5 temperature exceptions and their duration, temp. above or below predefined thresholds A, B or C |
Registers relevant for this mode:
Hex | Register name | Default value (hex) |
0x1D | Temperature threshold A | 1,5°C (0x53) |
0x1E | Temperature hysteresis A | 1°C (0x04) |
0x1F | Temperature threshold B | 40°C (0xA0) |
0x20 | Temperature hysteresis B | 2°C (0x08) |
0x21 | Temperature threshold C | 60°C (0xC8) |
0x22 | Temperature hysteresis C | 2°C (0x08) |
0x34 | Temperature measurement period | 0 seconds (0x00), delta: 3 minutes (0x43) |
0x4D | Temperature detection delay | 0 seconds (0x00) |
Similar modes:
Hex | Mode name | Description |
0x0F | Temperature delta pipeline | Similar to this mode but defines temperature exception as temperature above predefined delta |
0x10 | Temperature threshold alert | Sends an alert every time temperature is above or below any of the three predefined thresholds |
0x11 | Temperature delta alert | Sends an alert every time measured temperature is above the predefined delta |
0x1B | Temperature threshold alert WiFi | Basic WiFi-enabled version of Temperature threshold alert |
0x3F | Temperature threshold alert WiFi Atlas | WiFi Atlas version of Temperature threshold alert |
0x57 | Temperature threshold alert WiFi Precise | WiFi Precise version of Temperature threshold alert |
Switching to mode, arming and disarming information:
Follow the Basic Operations With SimpleHw Devices guide, where you can also find information about LED behavior, relevant Sigfox messages and more.
Here’s what’s important for Temperature threshold pipeline messages:
To set this mode, the downlink needs to include this mode register setting: 010E
The uplink messages need to begin with the mode hex as the first byte: 0E
When arming the device, you should see this message: 0E10
When the device is armed, it should send you these two bytes: 0E11
If you disarm the device via long press, you should receive this message: 0E14
Temperature change with redundancy
Intended for long-term monitoring of temperature exception occurrences - in this mode, temperature exception is defined as temperature above the predefined temperature delta. Will send an event with 5 exceptions and the duration of each exception. Every exception with its duration will take up two bytes of the payload for a total of 12 bytes (mode and event bytes included). The delta is encoded in SimpleTemp.
Hex value: 0x0F
Use cases: Long-term monitoring of temperature in any environment; labs, freezers, pools and more
Devices that support this mode: SimplePack and SimplePack Plus
Required sensors: Either temperature sensor (ambi or precise, precise is preferable)
Mode-specific deltas:
Deltas are mode-specific register values different from register default values.
Register (hex) | Default (hex) | Delta (hex) | Delta information |
0x34 | 0x00 | 0x43 | Thermometer turned on |
Uplink messages (events) used in this mode:
For more information on what uplink messages (mode-independent events) and additional data from various sensors in the device (appended payload) can be sent regardless of mode and how to fine-tune message behavior (alerts), see Mode-independent information and events.
Hex | Event name | Alert | Event information |
0x85 | Temperature delta pipeline | 1 | Pipeline of 5 temperature exceptions and their duration, when temperature is above the predefined delta |
Registers relevant for this mode:
Hex | Register name | Default value (hex) |
0x2F | Temperature delta | 2°C (0x08) |
0x34 | Temperature measurement period | 0 seconds (0x00), delta: 3 minutes (0x43) |
0x4D | Temperature detection delay | 0 seconds (0x00) |
Similar modes:
Hex | Mode name | Description |
0x0E | Temperature threshold pipeline | Similar to this mode but defines temperature exception as temperature above or below thresholds A, B and C |
0x10 | Temperature threshold alert | Sends an alert every time temperature is above or below any of threshold A, B or C |
0x11 | Temperature delta alert | Sends an alert every time the measured temperature is above the predefined delta |
0x1C | Temperature delta alert WiFi | Basic WiFi version of Temperature delta alert |
0x43 | Temperature delta alert WiFi Atlas | WiFi Atlas version of Temperature delta alert |
0x58 | Temperature delta alert WiFi Precise | WiFi Precise version of Temperature delta alert |
Switching to mode, arming and disarming information:
Follow the Basic Operations With SimpleHw Devices guide, where you can also find information about LED behavior, relevant Sigfox messages and more.
Here’s what’s important for Temperature delta pipeline messages:
To set this mode, the downlink needs to include this mode register setting: 010F
The uplink messages need to begin with the mode hex as the first byte: 0F
When arming the device, you should see this message: 0F10
When the device is armed, it should send you these two bytes: 0F11
If you disarm the device via long press, you should receive this message: 0F14
Temperature threshold alert
This mode sends an alert every time the measured temperature is above or below any of three predefined temperature thresholds A, B or C. The thresholds are encoded in SimpleTemp.
Hex value: 0x10
Use cases: Monitoring any environment that requires constant temperature in a certain range; labs, factories, warehouses, swimming pools and more
Devices that support this mode: SimplePack and SimplePack Plus
Required sensors: Either temperature sensor (ambi or precise, precise is preferable)
Mode-specific deltas:
Deltas are mode-specific register values different from register default values.
Register (hex) | Default (hex) | Delta (hex) | Delta information |
0x0D | 0x00 | 0x40 | Temperature sent with appended payload |
0x34 | 0x00 | 0x43 | Temperature measuring turned on |
Uplink messages (events) used in this mode:
For more information on what uplink messages (mode-independent events) and additional data from various sensors in the device (appended payload) can be sent regardless of mode and how to fine-tune message behavior (alerts), see Mode-independent information and events.
Hex | Event name | Alert | Event information |
0x50 | Temperature below threshold A | 1 | Temperature crossed 1 of the 3 thresholds |
0x51 | Temperature above threshold A | 1 | Temperature crossed 1 of the 3 thresholds |
0x52 | Temperature below threshold B | 1 | Temperature crossed 1 of the 3 thresholds |
0x53 | Temperature above threshold B | 1 | Temperature crossed 1 of the 3 thresholds |
0x54 | Temperature below threshold C | 1 | Temperature crossed 1 of the 3 thresholds |
0x55 | Temperature above threshold C | 1 | Temperature crossed 1 of the 3 thresholds |
Registers relevant for this mode:
Hex | Register name | Default value (hex) |
0x1D | Temperature threshold A | 1,5°C (0x53) |
0x1E | Temperature hysteresis A | 1°C (0x04) |
0x1F | Temperature threshold B | 40°C (0xA0) |
0x20 | Temperature hysteresis B | 2°C (0x08) |
0x21 | Temperature threshold C | 60°C (0xC8) |
0x22 | Temperature hysteresis C | 2°C (0x08) |
0x34 | Temperature measurement period | 0 seconds (0x00), delta: 3 minutes (0x43) |
0x4D | Temperature detection delay | 0 seconds (0x00) |
Similar modes:
Hex | Mode name | Description |
0x0E | Temperature threshold pipeline | Sends a pipeline of 5 temperature exceptions based on the three predefined thresholds |
0x0F | Temperature delta pipeline | Sends a pipeline of 5 temperature exceptions based on the predefined delta |
0x11 | Temperature delta alert | Similar to this mode but sends an alert every time temperature is above the predefined delta |
0x1B | Temperature threshold alert WiFi | Basic WiFi version of Temperature threshold alert |
0x3F | Temperature threshold alert WiFi Atlas | WiFi Atlas version of Temperature threshold alert |
0x57 | Temperature threshold alert WiFi Precise | WiFi Precise version of Temperature threshold alert |
Switching to mode, arming and disarming information:
Follow the Basic Operations With SimpleHw Devices guide, where you can also find information about LED behavior, relevant Sigfox messages and more.
Here’s what’s important for Temperature threshold alert messages:
To set this mode, the downlink needs to include this mode register setting: 0110
The uplink messages need to begin with the mode hex as the first byte: 10
When arming the device, you should see this message: 1010
When the device is armed, it should send you these two bytes: 1011
If you disarm the device via long press, you should receive this message: 1014
Temperature change alert
This mode sends an alert every time the measured temperature is above the predefined temperature delta. The delta is encoded in SimpleTemp.
Hex value: 0x11
Use cases: Monitoring any environment that requires constant temperature in a certain range; labs, factories, warehouses, swimming pools and more
Devices that support this mode: SimplePack and SimplePack Plus
Required sensors: Either temperature sensor (ambi or precise, precise is preferable)
Mode-specific deltas:
Deltas are mode-specific register values different from register default values.
Register (hex) | Default (hex) | Delta (hex) | Delta information |
0x0D | 0x00 | 0x40 | Temperature sent with appended payload |
0x34 | 0x00 | 0x43 | Temperature measuring turned on |
Uplink messages (events) used in this mode:
For more information on what uplink messages (mode-independent events) and additional data from various sensors in the device (appended payload) can be sent regardless of mode and how to fine-tune message behavior (alerts), see Mode-independent information and events.
Hex | Event name | Alert | Event information |
0x56 | Temperature delta alert | 1 | Temperature above predefined delta |
Registers relevant for this mode:
Hex | Register name | Default value (hex) |
0x2F | Temperature delta | 2°C (0x08) |
0x34 | Temperature measurement period | 0 seconds (0x00), delta: 3 minutes (0x43) |
0x4D | Temperature detection delay | 0 seconds (0x00) |
Similar modes:
Hex | Mode name | Description |
0x0E | Temperature threshold pipeline | Sends a pipeline of 5 temperature exceptions based on the three predefined thresholds |
0x0F | Temperature delta pipeline | Sends a pipeline of 5 temperature exceptions based on the predefined delta |
0x10 | Temperature threshold alert | Similar to this mode but sends an alert when temperature is above/below threshold A, B or C |
0x1C | Temperature delta alert WiFi | Basic WiFi version of Temperature delta alert |
0x43 | Temperature delta alert WiFi Atlas | WiFi Atlas version of Temperature delta alert |
0x58 | Temperature delta alert WiFi Precise | WiFi Precise version of Temperature delta alert |
Switching to mode, arming and disarming information:
Follow the Basic Operations With SimpleHw Devices guide, where you can also find information about LED behavior, relevant Sigfox messages and more.
Here’s what’s important for Temperature delta alert messages:
To set this mode, the downlink needs to include this mode register setting: 0111
The uplink messages need to begin with the mode hex as the first byte: 11
When arming the device, you should see this message: 1110
When the device is armed, it should send you these two bytes: 1111
If you disarm the device via long press, you should receive this message: 1114
Reed switch counter
Counts the number of reed contact switches and can report them in various ways. Very useful when you need to count e.g. rotation, door openings and closings etc.
Hex value: 0x13
Use cases: Vending machines, door openings, machine usage monitoring, cogs and more
Devices that support this mode: SimplePack and SimplePack Plus
Required sensors: Reed contact
Mode-specific deltas: None
Uplink messages (events) used in this mode:
For more information on what uplink messages (mode-independent events) and additional data from various sensors in the device (appended payload) can be sent regardless of mode and how to fine-tune message behavior (alerts), see Mode-independent information and events.
Hex | Event name | Alert | Event information |
0x87 | Reed count | 1 | Two ways to trigger this alert: 1. when reed count reaches a predefined number 2. after predefined time to trigger this event passes |
Registers relevant for this mode:
Hex | Register name | Default value (hex) |
0x37 | Reed contact measurement period | 1 second (0x01) |
0x4B | Reed contact detection delay | 0 seconds (0x00) |
0x50 | Reed count to trigger alert | Count to 50 (0x32) |
0x51 | Reed counter timer | 24 hours (0x98) |
Similar modes:
Hex | Mode name | Description |
0x08 | Reed contact pipeline | Sends a history of reed switches in one event |
0x0C | Reed contact on/off | Sends alerts when the reed is switched on and off |
Switching to mode, arming and disarming information:
Follow the Basic Operations With SimpleHw Devices guide, where you can also find information about LED behavior, relevant Sigfox messages and more.
Here’s what’s important for Reed counter messages:
To set this mode, the downlink needs to include this mode register setting: 0113
The uplink messages need to begin with the mode hex as the first byte: 13
When arming the device, you should see this message: 1310
When the device is armed, it should send you these two bytes: 1311
If you disarm the device via long press, you should receive this message: 1314
Legionella mode
Please note that the Legionella mode is only available in the SimpleIndustry Legionella device as it is not included in the standard API 6 build due to its size.
This mode was created to monitor water pipes and prevent growth of Legionella pneumophila bacteria that cause the legionnaire’s disease. A device with two external NTC sensors measures temperature of the pipe(s) in two modes and reports the temperature periodically.
Hex value: 0x1D
Mode description: The device will send regular uplink messages with information from both external NTC sensors. The mode can define each NTC sensor as Hot or Cold (and you can also have Hot or Cold twice at the same time and without the other).
The mode is built around what we call a Flow. A Flow starts when the measured temperature increases or decreases by X °C (default is 2°C). During the Flow, temperature is monitored in a faster interval than when the temperature is in the original range. When the Flow ends, the device will return back to the original measuring interval. The device will record the lowest and the highest temperature during Flows from both NTCs (Flow1 and Flow2), the number of Flows for each sensor and the lowest and the highest temperature measured during the whole interval regardless of number of Flows.
In default settings, the regular message is sent every 24 hours.
Please note that the Legionella mode is only available in the SimpleIndustry Legionella device as it is not included in the standard API 6 build due to its size.
Use cases: Monitoring water systems to prevent bacterial growth
Devices that support this mode: SimpleIndustry Legionella
Required sensors: One or two external NTC probes
Mode-specific deltas: None
Uplink messages (events) used in this mode:
For more information on what uplink messages (mode-independent events) and additional data from various sensors in the device (appended payload) can be sent regardless of mode and how to finetune message behavior (alerts), see Mode-independent information and events.
Hex | Event name | Alert | Event information |
0xB8 | Legionella event | None | Payload from both NTC sensors as described above |
Registers relevant for this mode:
Hex | Register name | Default value (hex) |
0x80 | Temperature drop delta for Flow1 | 2°C (0x54) |
0x81 | Temperature increase delta for Flow2 | 2°C (0x54) |
0x82 | Configuration of Flow1 and Flow2 | Flow1 cold, Flow2 hot (0x02) |
0x83 | Number of samples in Flow1 and Flow2 | 19 and 19 (0x88) |
0x84 | Legionella mode reporting period | 24 hours (0x98) |
Similar modes: None
Switching to mode, arming and disarming information:
Follow the general step-by-step guide for switching modes, arming and disarming for for all devices, where you can also find information about LED behavior and relevant Sigfox messages.
Here’s what’s important for Legionella messages:
To set this mode, the downlink needs to include this mode register setting: 011D
The uplink messages need to begin with the mode hex as the first byte: 1D
When arming the device, you should see this message: 1D10
When the device is armed, it should send you these two bytes: 1D11
If you disarm the device via long press, you should receive this message: 1D14
Blinker
The LED diode will start blinking when the button is pressed and will continue doing so until the button is pressed again. Used for simple LED indication.
Hex value: 0x60
Use cases: Simple LED indication
Devices that support this mode: SimplePack and SimplePack Plus
Required sensors: Button, LED diode
Mode-specific deltas:
Deltas are mode-specific register values different from register default values.
Register (hex) | Default (hex) | Delta (hex) | Delta information |
Tracing interval (0x05) | 0x0A | 0x05 | This register is used |
Uplink messages (events) used in this mode:
For more information on what uplink messages (mode-independent events) and additional data from various sensors in the device (appended payload) can be sent regardless of mode and how to fine-tune message behavior (alerts), see Mode-independent information and events.
Hex | Event name | Alert | Event information |
0x33 | Short press on | 1 | Button pressed while the LED is inactive |
0x34 | Short press off | 2 | Button pressed while the LED is active |
Registers relevant for this mode:
If you change the general sensitivity of the accelerometer and the magnetometer (0x11 and 0x19), respective axis registers reset to 0 as the general settings replace them and vice versa.
Hex | Register name | Default value (hex) |
0x05 | Tracing interval | 1 minutes (0x41), delta 5 seconds (0x05) |
0x58 | LED short blink length | 14 milliseconds (0x14) |
Similar modes:
Hex | Mode name | Description |
0x01 | Press me | Sends three types of messages based on button press length |
Switching to mode, arming and disarming information:
Follow the Basic Operations With SimpleHw Devices guide, where you can also find information about LED behavior, relevant Sigfox messages and more.
Here’s what’s important for Blinker messages:
To set this mode, the downlink needs to include this mode register setting: 0160
The uplink messages need to begin with the mode hex as the first byte: 60
Blinker does not require arming or disarming. This means the device will not send the following events: 0x10 (Start of arming), 0x11 (End of arming), 0x14 (Disarmed by long press).
Gas monitoring
Please note that the Gas monitoring mode is only available in the SimpleIndustry CH4 as it is not included in the standard API 6 build due to its size.
Monitors the concentration of gas regularly - reports 1) predefined gas threshold breaches (two thresholds available) and 2) periodic gas values (redundant data is configurable). Currently used for monitoring CH4.
Hex value: 0x65
Mode description: The mode has two ways to report messages with different triggers.
The first trigger is time, device will send a periodic message with 6 gas value records in ppm - each of the records is spaced by the gas monitoring period (0xA1) and the frequency of messages is defined by the aggregation (0xA0). Similar to the Periodic temperature independent event (only gas is monitored).
The second trigger is threshold breach. There are two configurable thresholds A (0xA2) and B (0xA3). Whenever a threshold is breached either way (up or down), the device sends a different event. Similar to the Temperature threshold alert mode (only gas is monitored). Requires gas monitoring period (0xA1) to be defined.
Use cases: Monitoring the presence of CH4 gas
Devices that support this mode: SimpleIndustry CH4
Required sensors: CH4 sensor
Mode-specific deltas: None
Uplink messages (events) used in this mode:
For more information on what uplink messages (mode-independent events) and additional data from various sensors in the device (appended payload) can be sent regardless of mode and how to finetune message behavior (alerts), see Mode-independent information and events.
Hex | Event name | Event information |
0xD3 | Gas below threshold A | Gas crossed one of the 2 thresholds |
0xD4 | Gas over threshold A | Gas crossed one of the 2 thresholds |
0xD5 | Gas below threshold B | Gas crossed one of the 2 thresholds |
0xD6 | Gas above threshold B | Gas crossed one of the 2 thresholds |
0xD7 | Periodic gas event | Periodic record of 6 measured gas values |
Registers relevant for this mode:
Hex | Register name | Default value (hex) |
0xA0 | Periodic gas monitoring aggregation | 0 (0x00)* |
0xA1 | Gas monitoring measurement interval | 1 hour (0x81) |
0xA2 | Gas threshold A | off (0x00)** |
0xA3 | Gas threshold B | off (0x00)** |
0xA4 | Gas monitoring hysteresis | 300 ppm (0x03)** |
0xA5 | Sensor warm-up time | 1 minute (0x41) |
*values 0x01, 0x02, 0x03, 0x06, if the MSB is 1 (e.g. 0x81 or 0x86), the device will calibrate the sensor. This must be done in fresh air and the value of register 0xA0 will then turn the MSB back to value 0 after calibration is done (e.g. from 0x86 to 0x06). Calibration only works when the device is armed.
**value x 100 = value in ppm
Similar modes: None
Switching to mode, arming and disarming information:
Follow the general step-by-step guide for switching modes, arming and disarming for for all devices, where you can also find information about LED behavior and relevant Sigfox messages.
Here’s what’s important for Gas monitoring messages:
To set this mode, the downlink needs to include this mode register setting: 0165
The uplink messages need to begin with the mode hex as the first byte: 65
When arming the device, you should see this message: 0165
When the device is armed, it should send you these two bytes: 0165
If you disarm the device via long press, you should receive this message: 0165
Battery consumption: Based on the number of messages sent.
The SimplePack Plus would last at least years (30 000+ messages).
Stupid mode 1 (only 2 MAC addresses)
Sends 2 MAC addresses regularly in a predefined period. Precise localisation with an emphasis on using as little battery life as possible as the MACs are sent in one message.
Hex value: 0x12
Use cases: Simple WiFi tracking, tracing, keep-alive heartbeats, localisation in general
Devices that support this mode: SimplePack Plus
Required sensors: WiFi module
Mode-specific deltas:
Deltas are mode-specific register values different from register default values.
Register (hex) | Default (hex) | Delta (hex) | Delta information |
0x64 | 0x00 | 0x98 | Heartbeat 3 sent every 24 hours |
Uplink messages (events) used in this mode:
This mode does not send the mode, event and mask bytes as usual. In default settings, the only payload you’ll receive are two 6-byte MAC addresses in one message (max uplink payload) - similar to Atlas WiFi user modes without the mode+event uplink message.
Uplink message example | Parsing |
0c9d924d4a500c9d924d4a51 | 12:157:146:77:74:50 (1st MAC),12:157:146:77:74:81 (2nd MAC) |
For more information on what uplink messages (mode-independent events) and additional data from various sensors in the device (appended payload) can be sent regardless of mode and how to fine-tune message behavior (alerts), see Mode-independent information and events.
Registers relevant for this mode:
Hex | Register name | Default value (hex) |
0x64 | Heartbeat 3 period | 0 seconds (0x00), delta: 24 hours (0x98) |
Similar modes:
Hex | Mode name | Description |
0x61 | Stupid mode 2 | Sends only Sigfox metadata, no payload is sent |
Switching to mode, arming and disarming information:
Follow the Basic Operations With SimpleHw Devices guide, where you can also find information about LED behavior, relevant Sigfox messages and more.
Here’s what’s important for Stupid mode 1 messages:
To set this mode, the downlink needs to include this mode register setting: 0112
When arming the device, you should see this message: 1210
When the device is armed, it should send you these two bytes: 1211
If you disarm the device via long press, you should receive this message: 1214
Stupid mode 2 (only empty payload)
This mode doesn’t send any payload, only Sigfox metadata. The messages are sent periodically and the time period can be adjusted. Used for Sigfox localisation with the lowest battery consumption possible.
Hex value: 0x61
Use cases: Simple Sigfox tracking, tracing, keep-alive heartbeats, localisation in general
Devices that support this mode: SimplePack and SimplePack Plus
Required sensors: None
Mode-specific deltas:
Deltas are mode-specific register values different from register default values.
Register (hex) | Default (hex) | Delta (hex) | Delta information |
0x64 | 0x00 | 0x98 | Heartbeat 3 sent every 24 hours |
Uplink messages (events) used in this mode: None
This mode does not send any uplink payload. You will receive an empty Sigfox message with the metadata, which you can use for localisation through Sigfox.
Registers relevant for this mode:
Hex | Register name | Default value (hex) |
0x64 | Heartbeat 3 period | 0 seconds (0x00), delta: 24 hours (0x98) |
Similar modes:
Hex | Mode name | Description |
0x12 | Stupid mode 1 | Only sends 2 MAC addresses in a single uplink message |
Switching to mode, arming and disarming information:
Follow the Basic Operations With SimpleHw Devices guide, where you can also find information about LED behavior, relevant Sigfox messages and more.
Here’s what’s important for Stupid mode 2 messages:
To set this mode, the downlink needs to include this mode register setting: 0161
The uplink messages need to begin with the mode hex as the first byte: 61
When arming the device, you should see this message: 6110
When the device is armed, it should send you these two bytes: 6111
If you disarm the device via long press, you should receive this message: 6114
Last updated
