Advertisement
Quick Links
MOVE'O
support.watteco.com/moveo/
MOVE'O sensor
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
1/16
Advertisement
Related Manuals for WATTECO MOVE'O
Summary of Contents for WATTECO MOVE'O
- Page 1 MOVE'O sensor 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.
- Page 2 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.
- Page 3 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.
- Page 4 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.
- Page 5 6 Frames / Hour 15 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.
- Page 6 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.
- Page 7 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).
- Page 8 EP0 (0x11): Sensor LoRaWAN parameters management 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"...
- Page 9 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) 9/16...
- Page 10 # . 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 # .
- Page 11 # . 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 # .
- Page 12 # 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.
- Page 13 # 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>...
- Page 14 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...
- Page 15 {"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",...
- Page 16 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. 16/16...
Need help?
Do you have a question about the MOVE'O and is the answer not in the manual?
Questions and answers