All Ezurio LoRa products should be referred as LoRaWAN as they all supports its protocol. LoRaWAN protocol make use of LoRa Chirp Spectrum Modulation within a license-free sub-gigahertz frequency band that allow to transmit regularly small packets up to 15km. 

It’s important to consider that 15km can only be achieved within absolute best conditions, some of which would be an outdoor “line of sight” transmission, interference free environment, ideal humidity/temperature, highest Spreading Factor, ect… Such range magnitude cannot represent any “real world” distance transmission and shouldn’t be expected by default.

The Sentrius RS1xx LoRaWAN sensor has been designed to use as minimum power as possible to be able to run on batteries for years in the field. Class A has been naturally chosen to fulfil this aim as its the most power efficient class. The only downside of this will be on the downlink latency where messages from the network server will only be possible after an uplink from the sensor.

There is no way to enable Class B or C behaviour on the RS1xx sensor.

The Sentrius RS1xx backlog feature allows to store up until 4096 measurement in its flash memory that users can retrieve with either FIFO or LIFO mode. To enable this feature, you'll have to make sure of the following :

- Depending on how you want the backlog feature to operate (On Fail or Continious), choose either Laird or Laird2 packets format.

- Provide the RS1xx with the network time

The backlog feature only functions if the sensor has received a timestamp from the server. Every time a sensor will join the Network Server, it will ask to be provided with the network time. Please make sure the network provide its timestamp every time the sensor will request it as per Application Note - RS1xx LoRa Protocol, section 4.3 Server-to-Sensor Message : Set UTC Notification. 

More information on the RS1xx logging feature can be found into User Guide - Sentrius RS1xx Sensor Configuration section 8.9.

The JOIN EUI, formerly referred to as the "APP EUI" has been renamed by the LoRaWAN Alliance, as it identifies the Join Server. This EUI can be configured the same across multiple devices, to identify which specific join server the device is to be linked to. It consists of an EUI64, 64 bit (8 byte) identifier.

Because the JOIN EUI is configurable (can be modified) by the end user, it is not included on the packaging of the sensor. A default JOIN EUI is configured at the time of manufacturing. For standard RS1xx products, any sensor/sensor kit assembled after date code: 0223451 will be configured with the current Manufacturing JOIN (APP) EUI of ECC07A0000000006. Any sensor/sensor kit assembled prior to this will be configured with the previous Manufacturing JOIN (APP) EUI of F9C60ECEA3ADC6BD. 

The default JOIN EUI (APP EUI), can also be found in the RS1xx User Guide, section 4.1.1, or via the RS1xx Sentrius Sensor App available from the Google Play Store or Apple Store.

Additional information for this product can be found on the Sentrius RS1xx Product Page.

*Note: Custom RS1xx products have their own unique JOIN EUI and do not use the default JOIN EUI found in the User Guide.

The state change is based on ‘latency’;

1. The RS1xx uses two internal dwell times to detect a door open and close. These can be set to a minimum of 5 seconds (which is also the default setting). So anything faster than 5 seconds will be suppressed and a change or the door won't be transmitted faster than 5 seconds.
2. Independent of the dwell time the RS186 faces a minimum LoRa uplink interval due to duty cycle limitation. At the maximum data rate (SF7BW125) the airtime is roughly 60msec, which then adds a dead time of 99x60msec=5.94sec. So from this we get a minimum cycle time of roughly 6 seconds, hence smaller dwell times than 5 seconds wouldn't make much sense. At the minimum data rate (SF12BW125) the airtime is roughly 1480msec plus a dead time of 99x1480msec=2.4min giving a minimum cycle time of roughly 2.5min.

So the latency of a door open/closed state detection plus transmission would be 6 seconds in a best case scenario (maximum LoRa data rate SF7BW125).

This applies to the RS186 EU version due to duty cycle limitations.

The RS191 will end up at approximately 5 seconds latency, purely due to dwell time.