Clos'O sensor

 

Declaration of conformity


Download the declaration of conformity

Presentation


The Clos’O sensor is a LoRaWAN class A sensor that uses a disposable 3.6V A-type battery as power supply and includes an internal antenna.

Clos’O is designed to detect closure or opening of a door or a gate. Time to take account is configurable.

Clos’O records all events (opening, closure).

Closo
Main case is fixed on the door frame. A magnet case fixed on the door leaf.

Battery level supervision by alarm sending.

Clos’O is able to detect tamper removal. Alarm is immediately sent.

Accessories to fix main case and magnetic case are supplied.

Integrated sensor in main case with external magnet case.

Family code:

The family code of Clos’O devices is: 50-70-108-xxx

Casing

Flammability rating: UL94V0
Ingress protection: IP65

Installation and operation


Installation

In construction...

Radio propagation

In order for the sensor to operate correctly, the number of obstacles should be limited in order to avoid excessive radio wave attenuation.

 

Autonomy


The information in the table below represents how long the battery can last. It is based on the default configuration at ambient temperature (+25°C) within the optimal operating range of the sensor via a LoRaWAN network (one uplink frame), when the spreading factor used is SF12.

The disposable battery has a 3.6Ah capacity, of which 85% is used.

 

Transmission periodicityBattery life
10 frames each day (default configuration with 2 alarms)7 years

Human Machine Interface


The Clos’O sensor has a buzzer that allows it to “communicate” with the user.

A reed switch is available under the sticker. It is possible to use a magnet to activate it and makes specific actions on the sensor (Switch off, switch on, Re-associtation…). When the reed switch is activated, the buzzer rings quickly.

 

 

To Start-up the device, it is necessary to put a magnet on the  side of the sensor during one second (at the left side of the cable gland). The buzzer rings quickly during this step. After this second, the buzzer stops and rings slowly until the association is done.

To switch off the device, use the same way by putting the magnet during 5 seconds. After this amount of time, the device rings 5 times slowly.

 

The table below describes the actions to be performed on the reed switch to disable or enable the storage mode.

Action
Magnet
Buzzer
Switch ON
(disable storage mode)
1 second
Switch OFF
(enable storage mode)
5 seconds

 

When the sensor is trying to associate with a network, it emits the following sound:

Once the association is completed, the buzzer makes the following sound:

A reed switch (or magnetic switch) is available. A magnet can be used to activate it and perform specific actions on the sensor (switch off, switch on, reassociation…).

  • Configuration: "void" frames are sent every minute for 10 minutes.

Standard reports are disabled in this mode.

Configuration mode
Way to trigger itOne passage of the magnet near the reed switch or specific ZCL command
Way to stop it Another passage of the magnet or specific ZCL command
Effects on the sensor
DurationThe configuration mode lasts 10 minutes
  • A reassociation procedure can be requested if no downlink frame is received by the sensor during a given periodicity (4 days by default) or if a given number (100 by default) is reached or in case of failure (no acknowledgement received) by sending an applicative frame to the sensor or via the sensor’s IHM.

The sensor keeps the AppEUi and DevAddr configured, Confirmed/Unconfirmed configuration and all applicative configurations. However, LoRaWAN configurations (channel, data rate…) are lost

 

ReAssociation Mode
Way to trigger itThree passages of the magnet near the reed switch or ZCL command from LoRaWAN cluster.
Effects on the sensor
  • A factory reset is available on nke Watteco’s sensors. It deletes all the applicative settings saved in the flash memory (i.e. configured batches and reports will be deleted).

The sensor keeps the AppEUi and DevAddr configured. However, LoRaWAN configurations (channel, data rate…) and applicative configurations are lost.

 

Factory reset
Way to trigger itTwo quick passages and a very long passage (until the sensor rings for the reset) of the magnet near the reed switch
Effects on the sensor

Applicative layer


Codecs are available to decode frames: Downloads

The Clos'O device implements “Binary Input” cluster associated to its Inputs.

Clos'O  integrates the following clusters:

ClusterEnd PointCluster name Managed attributes
0x0000 EP0BasicAll
0x0050EP0ConfigurationAll
0x8004EP0LoRaWANAll
0x000FEP0: tear off featureBinary InputAll
0x000FEP1: open/close featureBinary InputAll

 

Default configuration

The detection of an opening or closing is subject to maintaining the state for a period of filtering. 

An alarm of opening or closing is sent after maintening 2 seconds in the state, this state is sent too all 4 hours in a standard frame.

The recording in the batch is done when the opening or closing is maintained during 5 seconds.

The case tear off alarm is sent immediately.

The device send each day its voltage battery in a standard frame.

The batch is configured with the following parameters:

Label (size = 2) resolution
Binary Input (opening/closing) 0 1

 

 

Every change made to the default configuration must comply with the legal duty cycle (for example, the most restrictive in the EU is 0.1%, which corresponds to approximately 1 frame per hour with SF12)

Frame examples


All frames have to be sent on port 125

Standard report

Report

 

Report of case tear off

→ 11 0a 00 0f 00 55 10 00 : case is teared off

→ 11 0a 00 0f 00 55 10 01 : case is ok

 

Report of closing/opening

→ 31 0a 00 0f 00 55 10 00 : gate is open

→ 31 0a 00 0f 00 55 10 01 : gate is closed

 

Batch of closing/opening

→ 10 03 00 41 dd 76 c0 c0 80 03 14 b4 70 08 1d c0 27 19 07 04 30 a5 bc 6b cc 01

with https://support.nke-watteco.com/codec-online/  and batch attrributes : 2 0,1,1,OpenClose

{
"batch_counter": 3,
"batch_relative_timestamp": 346876,
"batch_absolute_timestamp": "2021-03-15T10:37:45.079",
"dataset": [
{
"data_relative_timestamp": 292315,
"data": {
"value": 1,
"label": 0,
"label_name": "OpenClose"
},
"data_absolute_timestamp": "2021-03-14T19:28:24.079Z"
},
{
"data_relative_timestamp": 339228,
"data": {
"value": 0.0,
"label": 0,
"label_name": "OpenClose"
},
"data_absolute_timestamp": "2021-03-15T08:30:17.079Z"
},
{
"data_relative_timestamp": 339233,
"data": {
"value": 1.0,
"label": 0,
"label_name": "OpenClose"
},
"data_absolute_timestamp": "2021-03-15T08:30:22.079Z"
},
{
"data_relative_timestamp": 340079,
"data": {
"value": 0.0,
"label": 0,
"label_name": "OpenClose"
},
"data_absolute_timestamp": "2021-03-15T08:44:28.079Z"
},
{
"data_relative_timestamp": 340087,
"data": {
"value": 1.0,
"label": 0,
"label_name": "OpenClose"
},
"data_absolute_timestamp": "2021-03-15T08:44:36.079Z"
},
{
"data_relative_timestamp": 344334,
"data": {
"value": 0.0,
"label": 0,
"label_name": "OpenClose"
},
"data_absolute_timestamp": "2021-03-15T09:55:23.079Z"
},
{
"data_relative_timestamp": 344343,
"data": {
"value": 1.0,
"label": 0,
"label_name": "OpenClose"
},
"data_absolute_timestamp": "2021-03-15T09:55:32.079Z"
}
] }

 

Configuration

 

Modify the batch

→ 31 06 00 0F 97 00 55 00 00 85 A0 01 70 01 00 05 01 02

0xMMMM : 85 A0 = 80 00 || 05 A0 avec 05 A0 = 1440 minutes = 24h
0xtt: 05 pour 5 x 1000ms → filtering between 4 and 6 secondes

 

Modify open/close alarm

→ 31 06 00 0F 80 00 55 10 00 00 80 F0 70 01 00 80 00 02 00 02

00 00 : min report.
80 F0 = 80 00 || 00 F0 avec 00 F0 = 240 minutes = 4h
0xcccc : 00 02 for 2 occurrences x 1000ms = 2 secondes → Close event
0xoooo : 00 02 pour 2 occurrences x 1000ms = 2 secondes → Open event

 

Print Friendly