MOVE'O sensor (Deprecated)

Presentation


The MOVE'O sensor is a LoRaWAN class A sensor that manages two different power supplies: one is external and may range from 3,6V to 24V, the other one is internal on 3 AA battery slots.Usually it is powered with 2 x 2600 mAh AA Lithium Batteries only, it could also be only one.

MOVE'O can sensor measure following environemental parameters: Temperature, Hygrometry, Occupancy (Passive infrared move detetction), Illuminance. It can also detect case openning effraction.

Family code

The family code of  MOVE'O sensor is: 50-70-220-xxx :  MOVE'O

LoRaWAN release

v1.0.2 Region Parameter rev B

Installation and operation


Installation

Manual and QuickStart guide are available in our download center.

The housing is intended to be installed inside a building and it must be protected from any water spray and must be used in environnement with less than 80% relative humidity. The product should not be installed in direct heat source (Heater, sunlight, ...) to avoid local heating effects that may alter a global estimation of environnemental parameters in the measured room. The product should be installed in a representative position in regard of the required environnemental parameters survey. IUsualy it should be installed beetween 1m50 and 2m50 from floor.

In the case of room occupancy survey the PIR Lense should face center of the surveyed area.

vaqao-installation

The product has "2 leds" and one "reed switch" as human to machine interface.These elements should placed down when installing the sensor.

To correctly install the sensor:

  • Open the product from the two clips at the botom using a small flat screw driver.
  • Use the base as a template and obtain horizontality using a level.
  • Once done you can clip back the front, containing electronic parts, on the base.

vaqao-fonddeboitier

vaqao-leds-ils

Once installed, the two leds are visible through the bottom left vertical windows and the reed switch can be actuated like a simple button using a magnet.

Replacing batteries

Batteries can be replaced with lithium-thionyl-chloride (Li-SOCI2) LR6/AA of 2600mAh each (exemple: SAFT LS14500). They can be replace on the fly, one afer each other, as each battery slot is protected against side overvoltage.

However  operator must carefully avoid any short circuit or electrostatic discharge during batery replacement.

Steps to replace batteries are :

  • Open the product from the two clips at the botom using a small flat screw driver.
  • Once front has been separated from base, use a spudger to remove the PCB from front of the sensor. Do it by  slightly making lever between casing and PCB on one of the long sides (Bottom or Up).
  • The PCB should now be separated from front. You can now extract a battery with the spludger and replace it with a new one.
    BEWARE that batteries must all be placed in the same direction. Notice the "+" sign on the PCB.
    Renew this operation for up to 3 batteries. (Usually 2 batteries are enough for more than 7 years life expectancy)
  • Gently clip back the PCB in the front of the casing, starting from lower or upper side.
  • Once done you can clip back the front containing electronic parts, on the base starting from upper  side.

Batteries replacement principle

batterryexchange

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.

Following estimations are given with default reporting configuration  and using three 3.6Ah capacity AA batteries installed, of which 85% is used.
With the default configuration the sensor will record all significative measurements (T and Hr) up to once each 10 minutes and at least once per hour. Then batch reports will be regularly send containning all these last measurements. It may contains several sample for any of the measured parameters (T, H, OCC, Lux...). Some specific reports/alarms may also be sent because of default configuration (case opening, moves, threshold crossing for T or Rh  ...). Due to all these possibly reported informations comsumption estimation is based on a périodic transmissions in range from 20 minutes to one hour with 2 x 2600 mAh batteries.

Transmission periodicitySpreading factorBatteries life
1 Frame / HourSF1213 Years
2 Frames / HourSF126 Years
6 Frames / HourSF123 Years
6 Frame / HourSF910 Years
6 Frames / HourSF715 Years

Human Machine Interface


Video Tutorials - WATTECO

There are 1 reed switch (label ILS) and two LEDs to interract with the product:

GREEN LED : LoRaNetwork status, mainly working when sensor try to join a network.
RED LED : miror of "Reed switch" actuation, and working during configuration mode.

  • When unused the sensor should be set in storage mode (Deep sleep mode) to avoid battery consumption. By the way, notice that when sent from factory the sensor should always be in Storage mode. The table below describes the actions to be performed on the reed switch (label ILS) to disable or enable the storage mode.
    Action
    Magnet
    Switch ON
    (disable storage mode)
    1 second
    Switch OFF
    (enable storage mode)
    5 seconds

    Notice: in case the sensor would not react to magnet actuation, please verify that internal ON/OFF switch is set to "ON" position. Switch is ON when pushed toward outside of the electronic board.

    CarteVaqaoInterrupteurOnOff
  • After Power on or Factory reset or Wakeup from storage mode the GREEN LED will blink until network could be joined.

association

  • During regular working mode, a configuration mode can be activated through one "user button" press (same as one pass of magnet on reed switch (ILS)), to enter the configuration mode.
    Consequently, "Void" frames are then sent every minute for 10 minutes allowing to probe uplink communication and send quickly downlink frames (configurations, requests, ...) to the class A sensor.

Standard reports are disabled during this configuration mode.

Configuration mode
Way to trigger itOne press on the USER button or specific ZCL command
Way to stop it Another press on the USER button or specific ZCL command
Effects on the sensorThe CONF led (red) blinks (3 sec. OFF, 3 sec. ON) and the sensor sends an uplink frame every minute. The blinking is illustrated below this table.
DurationThe configuration mode lasts 10 minutes when it is triggered by pressing the USER button

4

  • A reassociation procedure can be fired either manually (see table below) or automatically 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.

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 short presses on the USER button or ZCL command from LoRaWAN cluster.
Effects on the sensorThe ASSO LED (green) blinks as the “no commissioned sensor” LED is lit.
  • A factory reset, available on Watteco’s sensors, can be fired manually (see table below). It deletes all the applicative settings saved in the flash memory (i.e.: newly configured batches and reports will be replaced by the factory reporting configuration).

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 short presses and one long press for approximately 7 seconds on the USER button.
Effects on the sensorThe CONF LED (red) and ASSO LED (green) blink at the same time briefly. All the applicative settings (for batches and reports) are deleted. The blinking is illustrated below this table.

5

Applicative layer


Codecs are available to decode frames: Downloads

All downlink frames have to be sent on port 125

Please, try and see also Watteco Online codecs

The MOVE’O device implements many applicative clusters associated to different sensors entries. The associations beetween measurment functionnalities and EndPoints/Clusters are shown below:

ClusterCluster nameEndPoint: RôleProductManaged attributes
0x0402TemperatureEP1 (0x31): Accuracy +/-0,2°C [1/100 °C] AllAll
0x405HumidityEP1 (0x31): Accuracy +/-2% [1/100 %RH] AllAll
0x000FBinary inputEP0 (0x11): Open case status [Casing, 1: Opened, 0: Closed]AllAll
0x0406OccupancyEP0 (0x11): Current PIR sensor status [1: Occupied, 0: Not occupied]AllAll
0x0400IlluminanceEP0 (0x11): Illuminance measurement [Lux]AllAll
0x0000BasicEP0 (0x11): Sensor firmware and hardware informationsAllAll
0x0050ConfigurationEP0 (0x11): Sensor global configuration parameters and commandsAllAll
0x8004LoRaWANEP0 (0x11): Sensor LoRaWAN parameters managementAllAll

Default configuration

MOVE'O sensors have got a default, Batch and Standard, configuration, that manages all embeded measurements through a periodic reporting of up to 2 frames per hour. This default configuration can be summerized as follow :

The "Batch" configuration

It records environnemental parameters with a 10 minutes max time sampling and sends them once or twice per hour:

  • Temperature with a resolution of 0.1°C
  • Humidity with a resolution of 1%
  • Occupancy state
  • Illuminance with a resolution of 10 Lux

The "Standard" configuration

It monitors critical events on environnemental parameters

  • An report on case opening (violation)
  • An alarm/report on power supply lowring down to 2,9v and once each 5 days
  • An alarm/report on Temperature lower than 14°C or higher than 28°C
  • An alarm/report on Relative humidity lower than 20% or higher than 40%
  • A report each time Occupancy changes from Occupied to Unoccupied and vice versa

Any of these configurations can be removed or modified, and some different ones can be set.  However, 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%, corresponds to approximately 2 frames per hour with the most constrained Spreading Factor : SF12.

Detailed default configurations

MOVE'O (v3.5.2.5415.5855)

# . Set "unconfirmed mode"
08 11 05 8004 0000 08 00
#
# . PIR config
# Occ to Unocc delai: 30min (30 minutes WITHOUT move (notice that PIR activity won't be processed 1/10 x 30mn )
09 11 05 0406 0010 21 0708
# UnOcc to Occ delai: 0s (Immediatly)
09 11 05 0406 0011 21 0000
#
# . LUX Configuration
# Default : Y = 0*X^2 + 1*X + 0
14 11 05 0400 8000 41 0C 00000000 3f800000 00000000
# Set calibration coef to Y = 0*X^2 + 3*X + 0
# with current version and light tube : 1293.3000 from MENTOR => beetween 2.5 and 3.5 multiplier coef
# 14 11 05 0400 8000 41 0C 00000000 40400000 00000000
#
# . Effacement des configurations (Batch et Standard)
06 11 50 0050 02 03
#
# ------------------------ STANDARD REPORTS -------------------------
# . POWERDESC [mV]
# . Periodic MAX = 5 J => 7200mn => x9C20; MIN = 10mn => 0x800A
# . Length of remaining payload (for 0x41 type ): 0x08
# . ALARM on power treshold : 2,7v (hyst 100mV)
# RP : NewCfg/Reserved/ShortCause/SecuredIfAlarm/AllNotSecured/HeaderKept/NotBatch : b 1 0 01 1 0 0 0 ==> x98
# CSD : IsAlarm/OnExceed/OnFall/Threshold/Slot0 : b 1 1 1 10 000 ==> xF0
# Disposable battery field index : 0x04
# THRS: 2700 : 0x0A8C; HYST: 100 mV : 0x0064
# OCC : 2
14 11 06 0050 98 0006 41 800A 9C20 07 F0 04 0A8C 0064 02
#
# . OCCUPANCY (EKMB110411) [Occupancy state 0/1]
# . ROOM occupation changes
# Min 1mn => 0x8001, Max max, Delta=1
# Note: Min 1minute (But beware that UnOcc to OCC and Occ to UnOcc impact the reporting behaviour)
0D 11 06 0406 00 0000 18 8001 FFFF 01
#
# . VIOLATION (OpenCase button) ([Binary state 0/1]
# . Configure POLLING PERIOD based on REPORT CONFIGURATION (0xFFFF)
09 11 05 000F 0403 21 FFFF
# . Box openning and closing
# Min 10s => 0x000A, Max max, Delta=1
0D 11 06 000F 00 0055 10 000A FFFF 01
#
# . TEMPERATURE (sht3c) [1/100 °C]
# . Periodic MAX = Inf => xFFFF; MIN = 10mn => 0x800A
# . ALARM on treshold LOW: 14°; hyst 0.5°
# RP : NewCfg/Reserved/ShortCause/SecuredIfAlarm/AllNotSecured/HeaderKept/NotBatch : b 1 0 01 1 0 0 0 ==> x98
# CSD : IsAlarm/OnExceed/OnFall/Threshold/Slot0 : b 1 1 1 10 000 ==> xF0
# THRS: 1400 : 0x0578; HYST: 50 : 0x0032
# OCC : 2
# . ALARM on treshold HIGH: 28°; hyst 0.5°
# RP : NewCfg/Reserved/ShortCause/SecuredIfAlarm/AllNotSecured/HeaderKept/NotBatch : b 1 0 01 1 0 0 0 ==> x98
# CSD : IsAlarm/OnExceed/OnFall/Threshold/Slot1 : b 1 1 1 10 001 ==> xF1
# THRS: 2800 : 0x0AF0; HYST: 50 : 0x0032
# OCC : 2
18 31 06 0402 98 0000 29 800A FFFF F0 0578 0032 02 F1 0AF0 0032 02
#
# . HUMIDITY (sht3c) [1/100 %]
# . Periodic MAX = Inf => xFFFF; MIN = 10mn => 0x800A
# . ALARM on treshold LOW: 20%; hyst 5%
# RP : NewCfg/Reserved/ShortCause/SecuredIfAlarm/AllNotSecured/HeaderKept/NotBatch : b 1 0 01 1 0 0 0 ==> x98
# CSD : IsAlarm/OnExceed/OnFall/Threshold/Slot0 : b 1 1 1 10 000 ==> xF0
# THRS: 2000 : 0x7D0; HYST: 500 : 0x01F4
# OCC : 2
# . ALARM on treshold HIGH: 70%; hyst 5%
# RP : NewCfg/Reserved/ShortCause/SecuredIfAlarm/AllNotSecured/HeaderKept/NotBatch : b 1 0 01 1 0 0 0 ==> x98
# CSD : IsAlarm/OnExceed/OnFall/Threshold/Slot1 : b 1 1 1 10 001 ==> xF1
# THRS: 2300 : 0x08FC; HYST: 500 : 0x01F4
# OCC : 2
18 31 06 0405 98 0000 21 800A FFFF F0 07D0 01F4 02 F1 08FC 01F4 02
#
# . ILLUMINANCE [lux]
#
# ------------------------- BATCH REPORT ---------------------------------------
# . OCCUPANCY
# Min 30mn => 0x801E, Max 1h, Delta=1, resol=1, Tag Label 0, Tag Size 3, Type Bool 1
0F 11 06 0406 11 0000 00 801E 803C 01 01 03
# . TEMPERATURE (SHTC3)
# Min 10mn => 0x800A, Max 1h, Delta=0.1°, resol=0.1°, Tag Label 1, Tag Size 3, Type I16 7
11 31 06 0402 15 0000 00 800A 803C 000A 000A 0B
# . HYGROMETRY (SHTC3)
# Min 10mn => 0x800A, Max 1h, Delta=1%, resol=1%, Tag Label 2, Tag Size 3, Type U16 6
11 31 06 0405 15 0000 00 800A 803C 0064 0064 13
# . ILLUMINANCE
# Min 10mn => 0x800A, Max 1h, Delta=10, resol=10, Tag Label 5, Tag Size 3, Type U16 6
11 11 06 0400 15 0000 00 800A 803C 000A 000A 2B
#
# Watteco online Codec parameters:
# --------------------------------
# 3 0,1,4,OCC 1,10,7,T 2,100,6,H 5,10,6,LUX 6,10,6,P

Alternate 'No Batch' configuration

MOVE'O sensors has got an alternate default configuration that can be activated instead of default one. With this alternate configuration Batch is not used. Beware that this configuration is more verbose on radio, and will drain battery faster.

Following configuration commands can be used to swap beetween default configuration and alternate one:

  • Set 'No Batch' default configuration: 11500050F101
  • Set Back default configuration : 11500050F100

Detailed alternate 'No batch' configurations

MOVE'O Alternate 'No batch' configuration

# To Swap from Default to Alternate configuration: 11 50 0050 F1 01
#                                
and to get back: 11 50 0050 F1 00
# All report unconfirmed
08 11 05 8004 0000 08 00
#
# Remove current reports configuration (Standard and batchs)
06 11 50 0050 02 03
#
# T: 30mn or variation of 0.4°C, no more than once per minute
0F 31 06 0402 80 0000 29 8001 801E 48 0028
#
# RH: 30mn or variation of 4%, no more than onceper minute
0F 31 06 0405 80 0000 21 8001 801E 48 0190
#
# VBATT: 24 h ou or variation of 0.5V, no more than once per minute
12 11 06 0050 00 0006 41 800a 85a0 05 00 04 01f4 00
#
# OPEN/CLOSE: 24 h or changing, no more than once per minute
0D 11 06 000f 00 0055 10 8001 85a0 01
#
# PRESENCE:
# Unoccupied after30m without move
09 11 05 0406 0010 21 0708
# Report 12h or changing, no more than once per 10 minutes
0D 11 06 0406 00 0000 18 800a 82d0 01
#
# LUMINOSITY:12h or 50lux variation, no more than once per minute
0E 11 06 0400 00 0000 21 8001 82D0 0032

Received frame examples

Codecs are available to decode frames: Downloads

Please, try and see also Watteco Online codecs


Batch report

Typical MOVE'O batch report

Input uplink frame to decode:

<TODO>

Batch attributes :

3 0,1,4,OCC 1,10,7,T 2,100,6,H 5,10,6,LUX

Decoding results:

<TODO>

Standard report

Report on case opened (violation)

110a000f00551001

Decoded payload:

{"version": "WATTECO_Frame_Codec_v_1.0", "TimeStamp": "2020-03-02 17:01:45.232452"}
{
 "EndPoint": 0,
 "Report": "Standard",
 "CommandID": "ReportAttributes",
 "ClusterID": "BinaryInput",
 "AttributeID": "PresentValue",
 "AttributeType": "Boolean",
 "Data": true,
 "Cause": []
}

Alarm on Humidity level getting lower than specified threshold

318a0405000021053398b0

Decoded payload:

{"version": "WATTECO_Frame_Codec_v_1.0", "TimeStamp": "2020-03-02 16:58:38.024454"}
{
 "EndPoint": 1,
 "Report": "Standard",
 "CommandID": "ReportAttributesAlarm",
 "ClusterID": "RelativeHumidity",
 "AttributeID": "MeasuredValue",
 "AttributeType": "UInt16",
 "Data": 1331,
 "Cause": [
  {
   "ReportParameters": {
    "New": "Yes",
    "Reserved": 0,
    "CauseRequest": "Short",
    "SecuredIfAlarm": "Yes",
    "Secured": "No",
    "NoHeaderPort": "No",
    "Batch": "No"
   },
   "SlotDescriptors": [
    {
     "CriteriaSlotDescriptor": {
      "Alarm": "Yes",
      "OnExceed": "No",
      "OnFall": "Yes",
      "Mode": "Threshold",
      "CriterionIndex": 0
     }
    }
   ]
  }
 ]
}

Known Issues


  • 50-70-220-000: Low Lux measurement:
    • Due to a misplacement of Lux sensor, the measurement is very low. the measurement is impacted by the shades of casing ears. Therefore Lux is only an indication of presence of light. Notice that a comming soon new version of Move'O will solve this problem.

Print Friendly