PIR Motion Sensor User Manual

Last modified by Xiaoling on 2025/06/10 09:17

From 3.1 to 2.1 From 47.1 to 46.4

From version 46.4

edited by Xiaoling
on 2023/08/16 10:40

Change comment: There is no comment for this version

To version 3.1

edited by Edwin Chen
on 2023/04/09 00:13

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (3 modified, 0 added, 0 removed)
Attachments (0 modified, 0 added, 17 removed)

Details

Page properties

Title

@@ -1,1 +1,1 @@
--LHT65N-PIR Temperature/Humidity/PIR Motion Sensor User Manual
++LHT65-PIR Temperature/Humidity/PIR Sensor User Manual

Author

@@ -1,1 +1,1 @@
--XWiki.Xiaoling
++XWiki.Edwin

Content

@@ -1,9 +1,14 @@
  (% style="text-align:center" %)
--[[image:LHT65N-PIR1.jpg||alt="image-20221206143242-2.png" height="484" width="485"]]
++[[image:image-20221206143242-2.png||height="602" width="551"]]
++
++
++
++
++
  **Table of Contents：**
  {{toc/}}
@@ -13,11 +13,13 @@
++
++
++
  = 1. Introduction =
  == 1.1 What is LHT65N-PIR Temperature,Humidity & PIR Sensor ==
--
  The Dragino (% style="color:blue" %)**LHT65N-PIR Temperature, Humidity & PIR sensor**(%%) is a Long Range LoRaWAN Sensor.It includes a (% style="color:blue" %)**built-in Temperature & Humidity sensor**(%%) and has an (% style="color:blue" %)**external PIR Probe**(%%)**.** LHT65N-PIR can detect environment Temperature & Humdity, it also detects (% style="color:blue" %)**People Activity**(%%) via PIR probe and them send these info to LoRaWAN IoT Server.
  The LHT65N-PIR allows users to send data and reach extremely long ranges. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional wireless sensor network applications such as irrigation systems, smart metering, smart cities, building automation, and so on.
@@ -28,12 +28,12 @@
  LHT65N-PIR is fully compatible with (% style="color:blue" %)**LoRaWAN v1.0.3 Class A protocol**(%%), it can work with a standard LoRaWAN gateway.
++
  **~*~***The actual battery life depends on how often to send data, please see battery analyzer chapter.
  == 1.2 Features ==
--
  * LoRaWAN v1.0.3 Class A protocol
  * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915
  * AT Commands to change parameters
@@ -43,12 +43,9 @@
  * Built-in 2400mAh battery for up to 5 years of use.
  * Built-in Temperature & Humidity sensor
  * External PIR Sensor
--* Tri-color LED to indicate working status
++* Tri-color LED to indicate working status(% style="display:none" %)
--
--(% style="display:none" %)
--
  == 1.3 Specification ==
@@ -66,19 +66,19 @@
  * Long Term Drift: < 0.02 °C/yr
  * Operating Range: 0 ~~ 96 %RH
--(% style="color:#037691" %)**External PIR Sensor:**
++(% class="mark" style="color:#037691" %)**External PIR Sensor:**
--* Base on RDB223 Sensor
--* Cable Length : 1 meter
--* Stable detect distance : 0~~3 meter
++* (% class="mark" %)Base on BH1750 Illumination Sensor
++* (% class="mark" %)Cable Length : 50cm
++* (% class="mark" %)Resolution: 1 lx
++* (% class="mark" %)Range: 0-65535 lx
++* (% class="mark" %)Operating Range: -40 °C ~~ 85 °C
--
  = 2. Connect LHT65N-PIR to IoT Server =
  == 2.1 How does LHT65N-PIR work? ==
--
  LHT65N-PIR is configured as LoRaWAN OTAA Class A sensor by default. Each LHT65N-PIR is shipped with a worldwide unique set of OTAA keys. To use LHT65N-PIR in a LoRaWAN network, first, we need to put the OTAA keys in LoRaWAN Network Server and then activate LHT65N-PIR.
  If LHT65N-PIR is within the coverage of this LoRaWAN network. LHT65N-PIR can join the LoRaWAN network automatically. After successfully joining, LHT65N-PIR will start to measure environment temperature, humidity & people activity, and start to transmit sensor data to the LoRaWAN server. The default period for each uplink is 20 minutes.
@@ -86,32 +86,22 @@
  == 2.2 How to Activate LHT65N-PIR? ==
++The LHT65N-E5 has two working modes:
--The LHT65N-PIR has two working modes:
++*
++(% style="color:blue" %)**Deep Sleep Mode**(%%): LHT65N-E5 doesn't have any LoRaWAN activation. This mode is used for storage and shipping to save battery life.
--* (% style="color:blue" %)**Deep Sleep Mode**(%%): LHT65N-PIR doesn't have any LoRaWAN activation. This mode is used for storage and shipping to save battery life.
++*
++(% style="color:blue" %)**Working Mode**(%%):     In this mode, LHT65N-E5 works as LoRaWAN Sensor mode to Join LoRaWAN network and send out the sensor data to the server. Between each sampling/tx/rx periodically, LHT65N-E5 will be in STOP mode (IDLE mode), in STOP mode, LHT65N-E5 has the same power consumption as Deep Sleep mode.
--* (% style="color:blue" %)**Working Mode**(%%):     In this mode, LHT65N-PIR works as LoRaWAN Sensor mode to Join LoRaWAN network and send out the sensor data to the server. Between each sampling/tx/rx periodically, LHT65N-PIR will be in STOP mode (IDLE mode), in STOP mode, the PIR sensor is still working to detect people activity in low power consumption.
++The LHT65N-E5 is set in deep sleep mode by default; The ACT button on the front is to switch to different modes:
--The LHT65N-PIR is set in deep sleep mode by default; The ACT button on the front is to switch to different modes:
++[[image:image-20220515123819-1.png||_mstalt="430742" height="379" width="317"]]
--[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT65N-E5%20LoRaWAN%20Temperature_Humidity%20%26%20Illuminance%20Sensor%20User%20Manual/WebHome/image-20220515123819-1.png?width=317&height=379&rev=1.1||alt="image-20220515123819-1.png" height="379" width="317"]]
++[[image:image-20220525110604-2.png||_mstalt="427531"]]
--(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
--|=(% style="width: 167px;background-color:#D9E2F3;color:#0070C0" %)**Behavior on ACT**|=(% style="width: 117px;background-color:#D9E2F3;color:#0070C0" %)**Function**|=(% style="width: 225px;background-color:#D9E2F3;color:#0070C0" %)**Action**
--|(% style="background-color:#f2f2f2; width:167px" %)Pressing ACT between 1s < time < 3s|(% style="background-color:#f2f2f2; width:117px" %)Test uplink status|(% style="background-color:#f2f2f2; width:225px" %)(((
--If LHT65N-PIR is already Joined to rhe LoRaWAN network, LHT65N-PIR will send an uplink packet, if LHT65N-PIR has external sensor connected,(% style="color:blue" %)**Blue led** (%%)will blink once. If LHT65N-PIR has not external sensor, (% style="color:red" %)**Red led**(%%) will blink once.
--)))
--|(% style="background-color:#f2f2f2; width:167px" %)Pressing ACT for more than 3s|(% style="background-color:#f2f2f2; width:117px" %)Active Device|(% style="background-color:#f2f2f2; width:225px" %)(((
--(% style="background-color:#f2f2f2; color:green" %)**Green led**(%%) will fast blink 5 times, LHT65N-PIR will enter working mode and start to JOIN LoRaWAN network.
--(% style="background-color:#f2f2f2; color:green" %)**Green led**(%%) will solidly turn on for 5 seconds after join in network.
--)))
--|(% style="background-color:#f2f2f2; width:167px" %)Fast press ACT 5 times.|(% style="background-color:#f2f2f2; width:117px" %)Deactivate Device|(% style="background-color:#f2f2f2; width:225px" %)(% style="color:red" %)**Red led**(%%) will solid on for 5 seconds. Means LHT65N-PIR is in Deep Sleep Mode.
--
--
--
  == 2.3 Example to join LoRaWAN network ==
@@ -120,413 +120,621 @@
  (% class="wikigeneratedid" %)
--[[image:image-20230409080812-1.png||height="487" width="785"]]
++[[image:image-20221224101636-1.png||height="435" width="715"]]
--Assume the LPS8v2 is already set to connect to [[TTN V3 network>>url:https://eu1.cloud.thethings.network||_mstvisible="2"]], So it provides network coverage for LHT65N-PIR. Next we need to add the LHT65N-PIR device in TTN V3:
++(((
++Assume the LPS8v2 is already set to connect to [[TTN V3 network>>url:https://eu1.cloud.thethings.network||_mstvisible="2"]], So it provides network coverage for LHT65N-E5. Next we need to add the LHT65N-E5 device in TTN V3:
++)))
  === 2.3.1 Step 1: Create Device n TTN ===
--Create a device in TTN V3 with the OTAA keys from LHT65N-PIR.
++(((
++Create a device in TTN V3 with the OTAA keys from LHT65N-E5.
++)))
--Each LHT65N-PIR is shipped with a sticker with its device EUI, APP Key and APP EUI as below:
++(((
++Each LHT65N-E5 is shipped with a sticker with its device EUI, APP Key and APP EUI as below:
++)))
--[[image:image-20230426083533-1.png||height="286" width="616"]]
++[[image:image-20220617150003-1.jpeg||_mstalt="5426434"]]
--
  User can enter these keys in the LoRaWAN Server portal. Below is TTN V3 screenshot:
  Add APP EUI in the application.
--[[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220522232916-3.png||_mstalt="430495"]]
++[[image:image-20220522232916-3.png||_mstalt="430495"]]
--[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT65N-E5%20LoRaWAN%20Temperature_Humidity%20%26%20Illuminance%20Sensor%20User%20Manual/WebHome/image-20220522232932-4.png?rev=1.1||alt="image-20220522232932-4.png"]]
++[[image:image-20220522232932-4.png||_mstalt="430157"]]
--[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT65N-E5%20LoRaWAN%20Temperature_Humidity%20%26%20Illuminance%20Sensor%20User%20Manual/WebHome/image-20220522232954-5.png?rev=1.1||alt="image-20220522232954-5.png"]]
++[[image:image-20220522232954-5.png||_mstalt="431847"]]
--(% style="color:red" %)**Note: LHT65N-PIR use same payload decoder as LHT65.**
++(% style="color:red" %)**Note: LHT65N-E5 use same payload decoder as LHT65.**
--[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT65N-E5%20LoRaWAN%20Temperature_Humidity%20%26%20Illuminance%20Sensor%20User%20Manual/WebHome/image-20220522233026-6.png?rev=1.1||alt="image-20220522233026-6.png"]]
++[[image:image-20220522233026-6.png||_mstalt="429403"]]
--**Input APP EUI,  APP KEY and DEV EUI:**
--[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT65N-E5%20LoRaWAN%20Temperature_Humidity%20%26%20Illuminance%20Sensor%20User%20Manual/WebHome/image-20220522233118-7.png?rev=1.1||alt="image-20220522233118-7.png"]]
++Input APP EUI,  APP KEY and DEV EUI:
--=== 2.3.2 Step 2: Activate LHT65N-PIR by pressing the ACT button for more than 5 seconds. ===
++[[image:image-20220522233118-7.png||_mstalt="430430"]]
--Use ACT button to activate LHT65N-PIR and it will auto-join to the TTN V3 network. After join success, it will start to upload sensor data to TTN V3 and user can see in the panel.
++=== 2.3.2 Step 2: Activate LHT65N-E5 by pressing the ACT button for more than 5 seconds. ===
--[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT65N-E5%20LoRaWAN%20Temperature_Humidity%20%26%20Illuminance%20Sensor%20User%20Manual/WebHome/image-20220522233300-8.png?rev=1.1||alt="image-20220522233300-8.png"]]
++(((
++Use ACT button to activate LHT65N-E5 and it will auto-join to the TTN V3 network. After join success, it will start to upload sensor data to TTN V3 and user can see in the panel.
++)))
++[[image:image-20220522233300-8.png||_mstalt="428389" height="219" width="722"]]
--== 2.4 Uplink Payload~-~-Device Status, (Fport~=5) ==
++== 2.4 Uplink Payload   ( Fport~=2) ==
--Users can use the downlink command(**0x26 01**) to ask LHT65N-PIR to send device configure detail, include device configure status. LHT65N-PIR will uplink a payload via FPort=5 to server.
--The Payload format is as below.
++(((
++The uplink payload includes totally 11 bytes. Uplink packets use FPORT=2 and (% style="color:#4f81bd" %)**every 20 minutes**(%%) send one uplink by default.
++)))
--(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
--|(% colspan="6" style="background-color:#d9e2f3; color:#0070c0" %)**Device Status (FPORT=5)**
--|(% style="background-color:#f2f2f2; width:103px" %)**Size (bytes)**|(% style="background-color:#f2f2f2; width:72px" %)**1**|(% style="background-color:#f2f2f2" %)**2**|(% style="background-color:#f2f2f2; width:91px" %)**1**|(% style="background-color:#f2f2f2; width:86px" %)**1**|(% style="background-color:#f2f2f2; width:44px" %)**2**
--|(% style="background-color:#f2f2f2; width:103px" %)**Value**|(% style="background-color:#f2f2f2; width:72px" %)Sensor Model|(% style="background-color:#f2f2f2" %)Firmware Version|(% style="background-color:#f2f2f2; width:91px" %)Frequency Band|(% style="background-color:#f2f2f2; width:86px" %)Sub-band|(% style="background-color:#f2f2f2; width:44px" %)BAT
++(((
++After each uplink, the (% style="color:blue" %)**BLUE LED**(%%) will blink once.
++)))
--Example parse in TTNv3
++(% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:390px" %)
++|=(% style="width: 60px;" %)(((
++**Size(bytes)**
++)))|=(% style="width: 30px;" %)(((
++**2**
++)))|=(% style="width: 100px;" %)(((
++**2**
++)))|=(% style="width: 100px;" %)(((
++**2**
++)))|=(% style="width: 50px;" %)(((
++**1**
++)))|=(% style="width: 50px;" %)(((
++**4**
++)))
++|(% style="width:97px" %)(((
++**Value**
++)))|(% style="width:39px" %)(((
++[[BAT>>||anchor="H2.4.2BAT-BatteryInfo"]]
++)))|(% style="width:100px" %)(((
++(((
++[[Built-In Temperature>>||anchor="H2.4.3Built-inTemperature"]]
++)))
++)))|(% style="width:77px" %)(((
++(((
++[[Built-in Humidity>>||anchor="H2.4.4Built-inHumidity"]]
++)))
++)))|(% style="width:47px" %)(((
++[[Ext>>||anchor="H2.4.5Ext23"]] #
++)))|(% style="width:51px" %)(((
++[[Ext value>>||anchor="H2.4.6Extvalue"]]
++)))
--[[image:image-20230508151932-1.png]]
++* The First 6 bytes: has fix meanings for every LHT65N-E5.
++* The 7th byte (EXT #): defines the external sensor model. It can be 0x05 or 0x09 for LHT65N-E5
++* The 8^^th^^ ~~ 9^^th^^ byte: Illuminance. Range: 0-65535 lx.
++* The 10th ~~ 11th byte: Reserve, always 0xFFFF
++=== 2.4.1 Decoder in TTN V3 ===
--(% style="color:blue" %)**Sensor Model**(%%): For LHT65N-PIR, this value is 0x1A
--(% style="color:blue" %)**Firmware Version**(%%): 0x0100, Means: v1.0.0 version
++When the uplink payload arrives TTNv3, it shows HEX format and not friendly to read. We can add LHT65N-E5 decoder in TTNv3 for friendly reading.
--(% style="color:blue" %)**Frequency Band**:
++Below is the position to put the decoder and LHT65N-E5 decoder can be download from here: [[https:~~/~~/github.com/dragino/dragino-end-node-decoder>>https://github.com/dragino/dragino-end-node-decoder]]
--0x01: EU868
--0x02: US915
++[[image:image-20220522234118-10.png||_mstalt="451464" height="353" width="729"]]
--0x03: IN865
--0x04: AU915
++=== 2.4.2 BAT-Battery Info ===
--0x05: KZ865
--0x06: RU864
++These two bytes of BAT include the battery state and the actually voltage
--0x07: AS923
++[[image:image-20220523152839-18.png||_mstalt="457613"]]
--0x08: AS923-1
--0x09: AS923-2
++[[image:image-20220522235639-1.png||_mstalt="431392" height="139" width="727"]]
--0x0a: AS923-3
--0x0b: CN470
++Check the battery voltage for LHT65N-E5.
--0x0c: EU433
++* BAT status=(0Xcba4>>14)&0xFF=11(B)，very good
++* Battery Voltage =0xCBF6&0x3FFF=0x0BA4=2980mV
--0x0d: KR920
++=== 2.4.3 Built-in Temperature ===
--0x0e: MA869
++[[image:image-20220522235639-2.png||_mstalt="431756" height="138" width="722"]]
--(% style="color:blue" %)**Sub-Band**:
++* Temperature:  0x0ABB/100=27.47℃
--AU915 and US915: value 0x00 ~~ 0x08
++[[image:image-20220522235639-3.png||_mstalt="432120"]]
--CN470: value 0x0B ~~ 0x0C
++* Temperature:  (0xF5C6-65536)/100=-26.18℃
--Other Bands: Always 0x00
++=== 2.4.4 Built-in Humidity ===
--(% style="color:blue" %)**Battery Info**:
++[[image:image-20220522235639-4.png||_mstalt="432484" height="138" width="722"]]
--Check the battery voltage.
++* Humidity:    0x025C/10=60.4%
--Ex1: 0x0B45 = 2885mV
++=== 2.4.5 Ext value ===
--Ex2: 0x0B49 = 2889mV
++==== 2.4.5.1 Ext~=0x05, Illuminance Sensor ====
--== 2.5 Uplink Payload, Sensor Data  ( Fport~=2) ==
++[[image:image-20221224161634-2.png||height="138" width="851"]]
--The uplink payload includes totally 11 bytes. Uplink packets use FPORT=2 and (% style="color:#4f81bd" %)**every 20 minutes**(%%) send one uplink by default.
++* Illumination=0x005E=94 lux
--After each uplink, the (% style="color:blue" %)**BLUE LED**(%%) will blink once.
++The last 2 bytes of data are meaningless
--(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:390px" %)
--|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)(((
++[[image:image-20221224161725-3.png]]
++
++* When the sensor is not connected or not connected properly, will show "NULL"
++
++          The last 2 bytes of data are meaningless
++
++
++
++==== 2.4.5.2 Ext~=0x85, E5 sensor with Unix Timestamp ====
++
++
++(((
++Timestamp mode is designed for LHT65N-E5 with E3 probe, it will send the uplink payload with Unix timestamp. With the limitation of 11 bytes (max distance of AU915/US915/AS923 band), the time stamp mode will be lack of BAT voltage field, instead, it shows the battery status. The payload is as below:
++)))
++
++(((
++
++)))
++
++(% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:535px" %)
++|=(% style="width: 88px;" %)(((
  **Size(bytes)**
--)))|=(% style="width: 30px;background-color:#D9E2F3;color:#0070C0" %)(((
++)))|=(% style="width: 93px;" %)(((
  **2**
--)))|=(% style="width: 100px;background-color:#D9E2F3;color:#0070C0" %)(((
++)))|=(% style="width: 94px;" %)(((
  **2**
--)))|=(% style="width: 100px;background-color:#D9E2F3;color:#0070C0" %)(((
++)))|=(% style="width: 117px;" %)(((
  **2**
--)))|=(% style="width: 50px;background-color:#D9E2F3;color:#0070C0" %)(((
++)))|=(% style="width: 54px;" %)(((
  **1**
--)))|=(% style="width: 50px;background-color:#D9E2F3;color:#0070C0" %)(((
++)))|=(% style="width: 79px;" %)(((
  **4**
  )))
--|(% style="width:97px" %)(((
--Value
--)))|(% style="width:39px" %)(((
--[[BAT>>||anchor="H2.5.2BAT-BatteryInfo"]]
--)))|(% style="width:100px" %)(((
++|(% style="width:88px" %)(((
++**Value**
++)))|(% style="width:93px" %)(((
++[[External temperature>>||anchor="H4.2SetExternalSensorMode"]]
++)))|(% style="width:94px" %)(((
++[[Built-In Temperature>>||anchor="H2.4.3Built-inTemperature"]]
++)))|(% style="width:117px" %)(((
++BAT Status &
++Illumination
++)))|(% style="width:54px" %)(((
++Status & Ext
++)))|(% style="width:79px" %)(((
++[[Unix Time Stamp>>||anchor="H2.6.2UnixTimeStamp"]]
++)))
++
++* **Battery status & Built-in Humidity**
++
++(% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:461px" %)
++|=(% style="width: 67px;" %)Bit(bit)|=(% style="width: 256px;" %)[15:14]|=(% style="width: 132px;" %)[11:0]
++|(% style="width:67px" %)Value|(% style="width:256px" %)(((
++BAT Status
++00(b): Ultra Low ( BAT <= 2.50v)
++01(b): Low  (2.50v <=BAT <= 2.55v)
++10(b): OK   (2.55v <= BAT <=2.65v)
++11(b): Good   (BAT >= 2.65v)
++)))|(% style="width:132px" %)(((
++Illumination
++)))
++
++* **Status & Ext Byte**
++
++(% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:500px" %)
++|=(% scope="row" style="width: 60px;" %)**Bits**|(% style="width:90px" %)**7**|(% style="width:100px" %)**6**|(% style="width:90px" %)**5**|(% style="width:100px" %)**4**|(% style="width:60px" %)**[3:0]**
++|=(% style="width: 96px;" %)**Status&Ext**|(% style="width:124px" %)None-ACK Flag|(% style="width:146px" %)Poll Message FLAG|(% style="width:109px" %)Sync time OK|(% style="width:143px" %)Unix Time Request|(% style="width:106px" %)Ext: 0b(1001)
++
++* (% style="color:blue" %)**Poll Message Flag**:(%%)    1: This message is a poll message reply, 0: means this is a normal uplink.
++* (% style="color:blue" %)**Sync time OK**: (%%)          1: Set time ok，0: N/A. After time SYNC request is sent, LHT65N-E5 will set this bit to 0 until got the time stamp from the application server.
++* (% style="color:blue" %)**Unix Time Request**:(%%)  1: Request server downlink Unix time, 0 : N/A. In this mode, LHT65N-E5 will set this bit to 1 every 10 days to request a time SYNC. (AT+SYNCMOD to set this)
++
++== 2.5 Show data on Datacake ==
++
++
  (((
--[[Built-In Temperature>>||anchor="H2.5.3Built-inTemperature"]]
++Datacake IoT platform provides a human-friendly interface to show the sensor data, once we have sensor data in TTN V3, we can use Datacake to connect to TTN V3 and see the data in Datacake. Below are the steps:
  )))
--)))|(% style="width:77px" %)(((
++
  (((
--[[Built-in Humidity>>||anchor="H2.5.4Built-inHumidity"]]
++
  )))
--)))|(% style="width:47px" %)(((
--Ext #
--)))|(% style="width:51px" %)(((
--[[Ext value>>||anchor="H2.5.5Extvalue"]]
++
++(((
++(% style="color:blue" %)**Step 1**(%%): Be sure that your device is programmed and properly connected to the LoRaWAN network.
  )))
--* The First 6 bytes: has fix meanings for every LHT65N-PIR.
--* The 7th byte (EXT #): defines the external sensor model. It can be 0x0A for LHT65N-PIR
--* The 8^^th^^ byte: Alarm Bit (if this uplink is from periodically or movement)
--* The 9^^th^^ ~~ 11^^st^^  byte: Movement Detect Count.
++(((
++(% style="color:blue" %)**Step 2**(%%): Configure your Application to forward data to Datacake you will need to add integration. Go to TTN V3 Console ~-~-> Applications ~-~-> Integrations ~-~-> Add Integrations.
++)))
--=== 2.5.1 Decoder in TTN V3 ===
++(((
++Add Datacake:
++)))
--When the uplink payload arrives TTNv3, it shows HEX format and not friendly to read. We can add LHT65N-PIR decoder in TTNv3 for friendly reading.
++[[image:image-20220523000825-7.png||_mstalt="429884" height="262" width="583"]]
--Below is the position to put the decoder and LHT65N-PIR decoder can be download from here: [[https:~~/~~/github.com/dragino/dragino-end-node-decoder>>https://github.com/dragino/dragino-end-node-decoder]]
--[[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220522234118-10.png||_mstalt="451464" height="353" width="729"]]
++Select default key as Access Key:
--=== 2.5.2 BAT-Battery Info ===
++[[image:image-20220523000825-8.png||_mstalt="430248" height="453" width="406"]]
--These two bytes of BAT include the battery state and the actually voltage
++In Datacake console ([[https:~~/~~/datacake.co/>>url:https://datacake.co/]]) , add LHT65 device.
--(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:477px" %)
--|=(% style="width: 69px; background-color:#D9E2F3;color:#0070C0" %)(((
--**Bit(bit)**
--)))|=(% style="width: 253px;background-color:#D9E2F3;color:#0070C0" %)[15:14]|=(% style="width: 155px;background-color:#D9E2F3;color:#0070C0" %)[13:0]
--|(% style="width:66px" %)(((
--Value
--)))|(% style="width:250px" %)(((
--BAT Status
--00(b): Ultra Low ( BAT <= 2.50v)
--01(b): Low (2.50v <=BAT <= 2.55v)
--10(b): OK (2.55v <= BAT <=2.65v)
--11(b): Good (BAT >= 2.65v)
--)))|(% style="width:152px" %)Actually BAT voltage
--[[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220522235639-1.png||_mstalt="431392" height="139" width="727"]]
++[[image:image-20221224161935-5.png||height="523" width="409"]]
--Check the battery voltage for LHT65N-PIR.
++[[image:image-20221224161957-6.png||height="306" width="852"]]
--* BAT status=(0xcba4>>14)&0xFF=11(B)，very good
--* Battery Voltage =0xCBF6&0x3FFF=0x0BA4=2980mV
++== 2.6 Datalog Feature ==
--=== 2.5.3 Built-in Temperature ===
++(((
++Datalog Feature is to ensure IoT Server can get all sampling data from Sensor even if the LoRaWAN network is down. For each sampling, LHT65N-E5 will store the reading for future retrieving purposes. There are two ways for IoT servers to get datalog from LHT65N-E5.
++)))
--[[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220522235639-2.png||_mstalt="431756" height="138" width="722"]]
++=== 2.6.1 Ways to get datalog via LoRaWAN ===
--* Temperature:  0x0ABB/100=27.47℃
--[[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220522235639-3.png||_mstalt="432120"]]
++There are two methods:
--* Temperature:  (0xF5C6-65536)/100=-26.18℃
++(% style="color:blue" %)**Method 1:** (%%)IoT Server sends a downlink LoRaWAN command to [[poll the value>>||anchor="H2.6.4Pollsensorvalue"]] for specified time range.
++(% style="color:blue" %)**Method 2: **(%%)Set [[PNACKMD=1>>||anchor="H4.13AutoSendNone-ACKmessages"]], LHT65N-E5 will wait for ACK for every uplink, when there is no LoRaWAN network, LHT65N-E5 will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery.
--=== 2.5.4 Built-in Humidity ===
++(% style="color:red" %)**Note for method 2:**
--[[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220522235639-4.png||_mstalt="432484" height="138" width="722"]]
++* a) LHT65N-E5 will do an ACK check for data records sending to make sure every data arrive server.
++* b) LHT65N-E5 will send data in **CONFIRMED Mode** when PNACKMD=1, but LHT65N-E5 won't re-transmit the packet if it doesn't get ACK, it will just mark it as a NONE-ACK message. In a future uplink if LHT65N-E5 gets a ACK, LHT65N-E5 will consider there is a network connection and resend all NONE-ACK Message.
--* Humidity:    0x025C/10=60.4%
++Below is the typical case for the auto-update datalog feature (Set PNACKMD=1)
++[[image:image-20220703111700-2.png||_mstalt="426244" height="381" width="1119"]]
--=== 2.5.5 Ext value ===
--==== 2.5.5.1 Ext~=0x0E, PIR Sensor ====
++=== 2.6.2 Unix TimeStamp ===
--[[image:ext=14.png||alt="image-20221224161634-2.png"]]
++LHT65N-E5 uses Unix TimeStamp format based on
--==== 2.5.5.2 Ext Value ====
++[[image:image-20220523001219-11.png||_mstalt="450450" height="97" width="627"]]
--There are 4 bytes in Ext Value field.
--Bit0 of byte 8th shows if this uplink is generate by PIR activity.
++User can get this time from link:  [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/]] :
--(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:393px" %)
--|=(% style="width: 107px; background-color:#D9E2F3;color:#0070C0" %)(((
--**The 8^^th^^ byte**
--)))|=(% style="width: 73px; background-color:#D9E2F3;color:#0070C0" %)(((
--**Bit 1~~7**
--)))|=(% style="width: 213px; background-color:#D9E2F3;color:#0070C0" %)(((
--**Bit 0**
++Below is the converter example
++
++[[image:image-20220523001219-12.png||_mstalt="450827" height="298" width="720"]]
++
++
++So, we can use AT+TIMESTAMP=1611889405 or downlink 3060137afd00 to set the current time 2021 – Jan ~-~- 29 Friday 03:03:25
++
++
++=== 2.6.3 Set Device Time ===
++
++
++(((
++(% style="color:blue" %)**There are two ways to set device's time:**
  )))
--|(% style="width:106px" %)(((
--**Value**
--)))|(% style="width:71px" %)(((
--Reserve
--)))|(% style="width:211px" %)(((
++
  (((
--0: Normal Uplink
--1: Uplink by activity detected
++**1.  Through LoRaWAN MAC Command (Default settings)**
  )))
++
++(((
++User need to set SYNCMOD=1 to enable sync time via MAC command.
  )))
--(% style="color:red" %)**Note**:** Uplink by activity is disable by default.**
++(((
++Once LHT65N-E5 Joined LoRaWAN network, it will send the MAC command (DeviceTimeReq) and the server will reply with (DeviceTimeAns) to send the current time to LHT65N-E5. If LHT65N-E5 fails to get the time from the server, LHT65N-E5 will use the internal time and wait for next time request (AT+SYNCTDC to set the time request period, default is 10 days).
++)))
--The 9^^th^^ ~~ 11^^st^^  byte: Movement Detect Count.
++(((
++(% style="color:red" %)**Note: LoRaWAN Server need to support LoRaWAN v1.0.3(MAC v1.0.3) or higher to support this MAC command feature, Chirpstack,TTN V3 v3 and loriot support but TTN V3 v2 doesn't support. If server doesn't support this command, it will through away uplink packet with this command, so user will lose the packet with time request for TTN V3 v2 if SYNCMOD=1.**
++)))
--0x00 E5 09 : Total detect 58633 activity since end node start.
++(((
++**2. Manually Set Time**
++)))
--== 2.6 Show data on Datacake ==
++(((
++User needs to set SYNCMOD=0 to manual time, otherwise, the user set time will be overwritten by the time set by the server.
++)))
--Datacake IoT platform provides a human-friendly interface to show the sensor data, once we have sensor data in TTN V3, we can use Datacake to connect to TTN V3 and see the data in Datacake. Below are the steps:
++=== 2.6.4 Poll sensor value ===
--(% style="color:blue" %)**Step 1**(%%): Be sure that your device is programmed and properly connected to the LoRaWAN network.
--(% style="color:blue" %)**Step 2**(%%): Configure your Application to forward data to Datacake you will need to add integration. Go to TTN V3 Console ~-~-> Applications ~-~-> Integrations ~-~-> Add Integrations.
++User can poll sensor value based on timestamps from the server. Below is the downlink command.
--Add Datacake:
++[[image:image-20220523152302-15.png||_mstalt="451581"]]
--[[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220523000825-7.png||_mstalt="429884" height="262" width="583"]]
++Timestamp start and Timestamp end use Unix TimeStamp format as mentioned above. Devices will reply with all data log during this time period, use the uplink interval.
++For example, downlink command (% _mstmutation="1" %)**31 5FC5F350 5FC6 0160 05**(%%)
--Select default key as Access Key:
++Is to check 2020/12/1 07:40:00 to 2020/12/1 08:40:00’s data
++Uplink Internal =5s，means LHT65N-E5 will send one packet every 5s. range 5~~255s.
--[[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220523000825-8.png||_mstalt="430248" height="453" width="406"]]
++=== 2.6.5 Datalog Uplink payload ===
--In Datacake console ([[https:~~/~~/datacake.co/>>url:https://datacake.co/]]) , add LHT65 device.
++The Datalog poll reply uplink will use below payload format.
--[[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20221224161935-5.png||height="523" width="409"]]
++**Retrieval data payload:**
++(% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:480px" %)
++|=(% style="width: 60px;" %)(((
++**Size(bytes)**
++)))|=(% style="width: 90px;" %)**2**|=(% style="width: 90px;" %)**2**|=(% style="width: 70px;" %)**2**|=(% style="width: 100px;" %)**1**|=(% style="width: 70px;" %)**4**
++|(% style="width:97px" %)**Value**|(% style="width:123px" %)[[External sensor data>>||anchor="H2.4.6Extvalue"]]|(% style="width:108px" %)[[Built In Temperature>>||anchor="H2.4.3Built-inTemperature"]]|(% style="width:133px" %)[[Built-in Humidity>>||anchor="H2.4.4Built-inHumidity"]]|(% style="width:159px" %)Poll message flag & Ext|(% style="width:80px" %)[[Unix Time Stamp>>||anchor="H2.6.2UnixTimeStamp"]]
--[[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20221224161957-6.png||height="306" width="852"]]
++**Poll message flag & Ext:**
++[[image:image-20221006192726-1.png||_mstalt="430508" height="112" width="754"]]
--== 2.7 LED Indicator ==
++(% style="color:blue" %)**No ACK Message**(%%):  1: This message means this payload is fromn Uplink Message which doesn't get ACK from the server before ( for [[PNACKMD=1>>||anchor="H4.13AutoSendNone-ACKmessages"]] feature)
++(% style="color:blue" %)**Poll Message Flag**(%%): 1: This message is a poll message reply.
--The LHT65N-PIR has a triple color LED which for easy showing different stage .
++* Poll Message Flag is set to 1.
--While user press ACT button, the LED will work as per LED status with ACT button.
++* Each data entry is 11 bytes, to save airtime and battery, devices will send max bytes according to the current DR and Frequency bands.
--In a normal working state:
++For example, in US915 band, the max payload for different DR is:
--* For each uplink, the (% style="color:blue" %)**BLUE LED**(%%) or (% style="color:red" %)**RED LED**(%%) will blink once.
--(% style="color:blue" %)**BLUE LED**(%%) when external sensor is connected.
--* (% style="color:red" %)**RED LED**(%%) when external sensor is not connected
--* For each success downlink, the (% style="color:purple" %)**PURPLE LED**(%%) will blink once
++(% style="color:blue" %)**a) DR0:** (%%)max is 11 bytes so one entry of data
++(% style="color:blue" %)**b) DR1:**(%%) max is 53 bytes so devices will upload 4 entries of data (total 44 bytes)
++(% style="color:blue" %)**c) DR2:**(%%) total payload includes 11 entries of data
--== 2.8 installation ==
++(% style="color:blue" %)**d) DR3: **(%%)total payload includes 22 entries of data.
++If devise doesn't have any data in the polling time. Device will uplink 11 bytes of 0
--~1. Don't install LHT65N-PIR outdoor or place where will get wet.
--2. Towards the PIR probe to the place where need to monitor activity. Below is the detect beam.
++**Example:**
--Stable distance is 0~~3m. Some motion might not detected between 3~~5 m.
++If LHT65N-E5 has below data inside Flash:
--[[image:image-20230411135341-1.png||height="450" width="456"]]
++[[image:image-20220523144455-1.png||_mstalt="430040" height="335" width="735"]]
--(% style="color:red" %)**Notice: PIR can only detect motion activity, not to use to detect static people case.**
++If user sends below downlink command:  (% style="background-color:yellow" %)3160065F9760066DA705
--* 1. PIR Motion Detector should not be installed near the Air conditioner places where with cold wind or hot wind flow, because PIR motion detector is sensitive with the temperature changes of the environment. Environment changes quickly will cause a false alarm.
++Where : Start time: 60065F97 = time 21/1/19 04:27:03
--* 2. PIR should not be installed facing the glass window, facing glass window will be interfered by the outside sunlight and moving objects (people or vehicle). The infrared energy can penetrate the glass window.
++             Stop time: 60066DA7= time 21/1/19 05:27:03
--* 3. PIR should not be installed facing the moving objects or background changing objects, movement object will cause airflow change, it may cause false alarm.
--* 4. Between the detection range of PIR Motion detector, there is should be less objects.  Many objects may reduce the sensitive of detection range.
++**LHT65N-E5 will uplink this payload.**
--* 5. Do not install more than one (2 or above) Wireless PIR in the same detection space (like at the same room).
++[[image:image-20220523001219-13.png||_mstalt="451204" height="421" style="text-align:left" width="727"]]
++__**7FFF089801464160065F97**__ **__7FFF__ __088E__ __014B__ __41__ __60066009__** 7FFF0885014E41600660667FFF0875015141600662BE7FFF086B015541600665167FFF08660155416006676E7FFF085F015A41600669C67FFF0857015D4160066C1E
++Where the first 11 bytes is for the first entry:
++
++7FFF089801464160065F97
++
++Ext sensor data=0x7FFF/100=327.67
++
++Temp=0x088E/100=22.00
++
++Hum=0x014B/10=32.6
++
++poll message flag & Ext=0x41,means reply data,Ext=1
++
++Unix time is 0x60066009=1611030423s=21/1/19 04:27:03
++
++
++== 2.7 Alarm Mode ==
++
++(((
++
++
++when the device is in alarm mode, it checks the built-in sensor temperature for a short time. if the temperature exceeds the preconfigured range, it sends an uplink immediately.
++)))
++
++(((
++(% style="color:red" %)**Note: alarm mode adds a little power consumption, and we recommend extending the normal read time when this feature is enabled.**
++
++
++)))
++
++=== 2.7.1 ALARM MODE ===
++
++
++(% class="box infomessage" %)
++(((
++(((
++**AT+WMOD=1**:              Enable/disable alarm mode. (0: Disabled, 1: Enabled Temperature Alarm for onboard temperature sensor)
++)))
++
++(((
++**AT+CITEMP=1**:             The interval between checking the alarm temperature. (In minutes)
++)))
++
++(((
++**AT+ARTEMP**:                 Gets or sets the alarm range of the internal temperature sensor
++)))
++
++(((
++(% _mstmutation="1" %)**AT+ARTEMP=？ **(%%):          Gets the alarm range of the internal temperature sensor(% style="display:none" %)
++)))
++
++(((
++**AT+ARTEMP=45,105**:   Set the internal temperature sensor alarm range from 45 to 105.
++)))
++)))
++
++(% style="color:#4f81bd" %)**Downlink Command: AAXXXXXXXXXXXXXX**
++
++Total bytes: 8 bytes
++
++**Example:**AA0100010001003C
++
++WMOD=01
++
++CITEMP=0001
++
++TEMPlow=0001
++
++TEMPhigh=003C
++
++
++== 2.8 LED Indicator ==
++
++
++The LHT65 has a triple color LED which for easy showing different stage .
++
++While user press ACT button, the LED will work as per LED status with ACT button.
++
++In a normal working state:
++
++* For each uplink, the BLUE LED or RED LED will blink once.
++BLUE LED when external sensor is connected.
++* RED LED when external sensor is not connected
++* For each success downlink, the PURPLE LED will blink once
++
++== 2.9 installation ==
++
++
++[[image:image-20220516231650-1.png||_mstalt="428597" height="436" width="428"]]
++
++
  = 3. Sensors and Accessories =
  == 3.1 E2 Extension Cable ==
--[[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220619092222-1.png||_mstalt="429533" height="182" width="188"]][[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220619092313-2.png||_mstalt="430222" height="182" width="173"]]
++[[image:image-20220619092222-1.png||_mstalt="429533" height="182" width="188"]][[image:image-20220619092313-2.png||_mstalt="430222" height="182" width="173"]]
--**1m long breakout cable for LHT65N-PIR. Features:**
++**1m long breakout cable for LHT65N-E5. Features:**
  * (((
  Use for AT Command
  )))
  * (((
--Update firmware for LHT65N-PIR
++Update firmware for LHT65N-E5
  )))
++* (((
++Exposed All pins from the LHT65N Type-C connector.
--[[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220619092421-3.png||_mstalt="430547" height="371" width="529"]]
++
++)))
--= 4. Configure LHT65N-PIR =
++[[image:image-20220619092421-3.png||_mstalt="430547" height="371" width="529"]]
--== 4.1 Configure Methods: ==
++= 4. Configure LHT65N-E5 via AT command or LoRaWAN downlink =
--LHT65N-PIR supports below configure method:
--* AT Command via UART Connection : See [[FAQ>>||anchor="H7.FAQ"]].
++(((
++Use can configure LHT65N-E5 via AT Command or LoRaWAN Downlink.
++)))
--* LoRaWAN Downlink.  Instruction for different platforms: See [[IoT LoRaWAN Server>>url:http://wiki.dragino.com/xwiki/bin/view/Main/]] section.
++* (((
++AT Command Connection: See [[FAQ>>||anchor="H6.FAQ"]].
++)))
++* (((
++LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
++)))
++(((
++There are two kinds of commands to configure LHT65N-E5, they are:
++)))
--== 4.2 General Commands ==
++* (((
++(% style="color:#4f81bd" %)**General Commands**.
++)))
--
++(((
  These commands are to configure:
++)))
--* General system settings like: uplink interval.
--* LoRaWAN protocol & radio related command.
++1. (((
++General system settings like: uplink interval.
++)))
++1. (((
++LoRaWAN protocol & radio-related commands.
++)))
--They are same for all Dragino Devices which support DLWS-005 LoRaWAN Stack. These commands can be found on the wiki:
++(((
++They are the same for all Dragino Devices which supports DLWS-005 LoRaWAN Stack(Note~*~*). These commands can be found on the wiki: [[End Device Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
++)))
--[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/>>url:http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/]]
++* (((
++(% style="color:#4f81bd" %)**Commands special design for LHT65N-E5**
++)))
++(((
++These commands are only valid for LHT65N-E5, as below:
++)))
--== 4.3 Commands special design for LHT65N-PIR ==
++== 4.1 Set Transmit Interval Time ==
--These commands only valid for LHT65N-PIR, as below:
++Feature: Change LoRaWAN End Node Transmit Interval.
--=== 4.3.1 Set Transmit Interval Time ===
++(% style="color:#4f81bd" %)**AT Command: AT+TDC**
--Feature: Change LoRaWAN End Node Transmit Interval.
++[[image:image-20220523150701-2.png||_mstalt="427453"]]
--(% style="color:#4f81bd" %)**AT Command: **
--(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:501px" %)
--|(% style="background-color:#d9e2f3; color:#0070c0; width:155px" %)**Command Example**|(% style="background-color:#d9e2f3; color:#0070c0; width:166px" %)**Function**|(% style="background-color:#d9e2f3; color:#0070c0; width:180px" %)**Response**
--|(% style="width:155px" %)AT+TDC=?|(% style="width:162px" %)Show current transmit Interval|(% style="width:177px" %)30000 OK the interval is 30000ms = 30s
--|(% style="width:155px" %)AT+TDC=60000|(% style="width:162px" %)Set Transmit Interval|(% style="width:177px" %)OK Set transmit interval to 60000ms = 60 seconds
++(% style="color:#4f81bd" %)**Downlink Command: 0x01**
--(% style="color:#4f81bd" %)**Downlink Payload: 0x01**
--
  Format: Command Code (0x01) followed by 3 bytes time value.
  If the downlink payload=0100003C, it means set the END Node's Transmit Interval to 0x00003C=60(S), while type code is 01.
@@ -535,140 +535,370 @@
  * **Example 2**: Downlink Payload: 0100003C         ~/~/ Set Transmit Interval (TDC) = 60 seconds
++== 4.2 Currently only supports E5 ==
--=== 4.3.2 Get Device Status ===
++Feature: Set device password, max 9 digits
--Send a LoRaWAN downlink to ask device send Alarm settings.
++(% style="color:#4f81bd" %)**AT Command: AT+EXT**
--* (% style="color:#4f81bd" %)**Downlink Payload**(%%)**:  **0x26 01
++(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
++|Command Example|Function|Response
++|AT+EXT=?|Get or Set external sensor model|(((
++5
--Sensor will upload Device Status via FPORT=5. See payload section for detail.
++OK
++)))
++|AT+EXT=5|(% colspan="2" %)Set external sensor mode to 5
++(% style="color:#4f81bd" %)**Downlink Command:0xA2**
--=== 4.3.3 Set Password ===
++Total bytes: 2 bytes
--Feature: Set device password, max 9 digits
++**Example:**
--(% style="color:#4f81bd" %)**AT Command: **
++* 0xA205: Set external sensor type to E5
--(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:372px" %)
--|(% style="background-color:#d9e2f3; color:#0070c0; width:155px" %)**Command Example**|(% style="background-color:#d9e2f3; color:#0070c0; width:128px" %)**Function**|(% style="background-color:#d9e2f3; color:#0070c0; width:89px" %)**Response**
--|(% style="width:155px" %)AT+PWORD=?|(% style="width:124px" %)Show password|(% style="width:86px" %)(((
--123456
++== 4.3 Set to sleep mode ==
--OK
--)))
--|(% style="width:155px" %)AT+PWORD=999999|(% style="width:124px" %)Set password|(% style="width:86px" %)OK
++Feature: Set device to sleep mode
++
++* **AT+Sleep=0**  : Normal working mode, device will sleep and use lower power when there is no LoRa message
++* **AT+Sleep=1** :  Device is in deep sleep mode, no LoRa activation happen, used for storage or shipping.
++
++(% style="color:#4f81bd" %)**AT Command: AT+SLEEP**
++
++[[image:image-20220523151218-7.png||_mstalt="430703"]]
++
++
  (% style="color:#4f81bd" %)**Downlink Command:**
--No downlink command for this feature.
++* There is no downlink command to set to Sleep mode.
++== 4.4 Set system time ==
--=== 4.3.4 Set to sleep mode ===
++Feature: Set system time, unix format. [[See here for format detail.>>||anchor="H2.6.2UnixTimeStamp"]]
--Feature: Set device to sleep mode
--* (% style="color:#037691" %)**AT+Sleep=0**(%%)  : Normal working mode, device will sleep and use lower power when there is no LoRa message
++(% style="color:#4f81bd" %)**AT Command:**
--* (% style="color:#037691" %)**AT+Sleep=1**(%%) :  Device is in deep sleep mode, no LoRa activation happen, used for storage or shipping.
++[[image:image-20220523151253-8.png||_mstalt="430677"]]
--(% style="color:#4f81bd" %)**AT Command: **
--(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:513px" %)
--|(% style="background-color:#d9e2f3; color:#0070c0; width:155px" %)**Command Example**|(% style="background-color:#d9e2f3; color:#0070c0; width:140px" %)**Function**|(% style="background-color:#d9e2f3; color:#0070c0; width:218px" %)**Response**
--|(% style="width:155px" %)AT+SLEEP|(% style="width:139px" %)Set to sleep mode|(% style="width:213px" %)(((
--Clear all stored sensor data…
++(% style="color:#4f81bd" %)**Downlink Command:**
--OK
++0x306007806000        ~/~/  Set timestamp to 0x(6007806000),Same as AT+TIMESTAMP=1611104352
++
++
++== 4.5 Set Time Sync Mode ==
++
++
++(((
++Feature: Enable/Disable Sync system time via LoRaWAN MAC Command (DeviceTimeReq), LoRaWAN server must support v1.0.3 protocol to reply this command.
  )))
++(((
++SYNCMOD is set to 1 by default. If user want to set a different time from LoRaWAN server, user need to set this to 0.
++
++
++)))
++
++(% style="color:#4f81bd" %)**AT Command:**
++
++[[image:image-20220523151336-9.png||_mstalt="431717"]]
++
++
  (% style="color:#4f81bd" %)**Downlink Command:**
--* There is no downlink command to set to Sleep mode.
++0x28 01             ~/~/  Same As AT+SYNCMOD=1
++0x28 00             ~/~/  Same As AT+SYNCMOD=0
++== 4.6 Set Time Sync Interval ==
--=== 4.3.5 Set UOA (Uplink on Activity) ===
++Feature: Define System time sync interval. SYNCTDC default value: 10 days.
--Feature: Enable / Disable Uplink on Activity
--(% style="color:#4f81bd" %)**AT Command: **
++(% style="color:#4f81bd" %)**AT Command:**
--* (% style="color:#037691" %)**AT+UOA=0**(%%)  : Disable UoA
++[[image:image-20220523151411-10.png||_mstalt="449696"]]
--* (% style="color:#037691" %)**AT+UOA=1,2**(%%) :  Enable UoA , Calm Down Time: 2 minutes. If device already send a uplink on activity, it will not send another uplink on activiy in 2 minutes, even detect activity.
--(% style="color:red" %)**Notice: Calm Down time range is 1 ~~ 65535 minutes. If user set Calm Down time to low value, such as 1 minute, the sensor might send uplink very frequenctly and battery drain fast.**
++(% style="color:#4f81bd" %)**Downlink Command:**
++**0x29 0A**       ~/~/ Same as AT+SYNCTDC=0x0A
++
++== 4.7 Print data entries base on page. ==
++
++
++Feature: Print the sector data from start page to stop page (max is 416 pages).
++
++
++(% style="color:#4f81bd" %)**AT Command: AT+PDTA**
++
++[[image:image-20220523151450-11.png||_mstalt="451035"]]
++
++
  (% style="color:#4f81bd" %)**Downlink Command:**
--Format: Command Code (0xA1) followed by 1 byte or 3 bytes.
++No downlink commands for feature
--When followed by 3 bytes, the first byte is 01, and the second and third bytes are Calm Down Time.
--* (% style="color:#037691" %)**A1 00    **(%%)**         ==>    AT+UOA=0     **
--* (% style="color:#037691" %)**A1 01 00 02  **(%%)** ==>    AT+UOA=1,2**
++== 4.8 Print last few data entries. ==
++Feature: Print the last few data entries
--= 5. Battery & Power Consumption =
++(% style="color:#4f81bd" %)**AT Command: AT+PLDTA**
--LHT65N-PIR use **CR17450** battery pack. See below link for detail information about the battery info and how to replace.
++[[image:image-20220523151524-12.png||_mstalt="452101"]]
--[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
++(% style="color:#4f81bd" %)**Downlink Command:**
--= 6. OTA firmware update =
++No downlink commands for feature
--User can change firmware LHT65N-PIR to:
++== 4.9 Clear Flash Record ==
--* Change Frequency band/ region.
--* Update with new features.
--* Fix bugs.
--Firmware and changelog can be downloaded from : **[[Firmware download link>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20OTA%20Update%20for%20Sensors/]]**
++Feature: Clear flash storage for data log feature.
--Methods to Update Firmware:
--* (Recommanded way) OTA firmware update via wireless: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20OTA%20Update%20for%20Sensors/>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20OTA%20Update%20for%20Sensors/]]
--* Update through UART TTL interface. **[[Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H1.LoRaSTv4baseHardware]]**.
++(% style="color:#4f81bd" %)**AT Command: AT+CLRDTA**
++[[image:image-20220523151556-13.png||_mstalt="454129"]]
--= 7. FAQ =
++(% style="color:#4f81bd" %)**Downlink Command: 0xA3**
--== 7.1 How to use AT Command? ==
++* Example: 0xA301        ~/~/  Same as AT+CLRDTA
++== 4.10 Auto Send None-ACK messages ==
--LHT65N-PIR supports AT Command set.User can use a USB to TTL adapter plus the Program Cable to connect to LHT65 for using AT command, as below.
++Feature: LHT65N-E5 will wait for ACK for each uplink, If LHT65N-E5 doesn't get ACK from the IoT server, it will consider the message doesn't arrive server and store it. LHT65N-E5 keeps sending messages in normal periodically. Once LHT65N-E5 gets ACK from a server, it will consider the network is ok and start to send the not-arrive message.
--[[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220615153355-1.png||_mstalt="430222"]]
++(% style="color:#4f81bd" %)**AT Command: AT+PNACKMD**
--[[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@1655802313617-381.png||_mstalt="293917"]]
++The default factory setting is 0
++(% border="1" cellspacing="4" style="background-color:#ffffcc; color:green; width:367px" %)
++|=(% style="width: 158px;" %)**Command Example**|=(% style="width: 118px;" %)**Function**|=(% style="width: 87px;" %)**Response**
++|(% style="width:158px" %)AT+PNACKMD=1|(% style="width:118px" %)Poll None-ACK message|(% style="width:87px" %)OK
--In PC, User needs to set serial tool(such as [[**putty**>>https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to (% style="color:green" %)**9600** (%%)to access to access serial console for LHT65N-PIR. The AT commands are disable by default and need to enter password (default:(% style="color:green" %)**123456**(% style="color:red" %))(%%) to active it. Timeout to input AT Command is 5 min, after 5-minute, user need to input password again. User can use AT+DISAT command to disable AT command before timeout.
++(% style="color:#4f81bd" %)**Downlink Command: 0x34**
--[[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220615154519-3.png||_mstalt="431925" height="672" width="807"]]
++* Example: 0x3401       ~/~/  Same as AT+PNACKMD=1
++= 5. Battery & How to replace =
--== 7.2 Where to use AT commands and Downlink commands ==
++== 5.1 Battery Type ==
++(((
++LHT65N-E5 is equipped with a 2400mAH Li-MnO2 (CR17505) battery . The battery is an un-rechargeable battery with low discharge rate targeting for up to 8~~10 years use. This type of battery is commonly used in IoT devices for long-term running, such as water meters.
++)))
++
++(((
++The discharge curve is not linear so can't simply use percentage to show the battery level. Below is the battery performance.
++
++
++[[image:image-20220515075034-1.png||_mstalt="428961" height="208" width="644"]]
++)))
++
++The minimum Working Voltage for the LHT65N-E5 is ~~ 2.5v. When battery is lower than 2.6v, it is time to change the battery.
++
++
++== 5.2 Replace Battery ==
++
++
++LHT65N-E5 has two screws on the back, Unscrew them, and changing the battery inside is ok. The battery is a general CR17450 battery (3.0v). Any brand should be ok.
++
++[[image:image-20220515075440-2.png||_mstalt="429546" height="338" width="272"]][[image:image-20220515075625-3.png||_mstalt="431574" height="193" width="257"]]
++
++
++== 5.3 Battery Life Analyze ==
++
++
++(((
++Dragino battery-powered products are all run in Low Power mode. User can check the guideline from this link to calculate the estimated battery life:
++[[https:~~/~~/www.dragino.com/downloads/downloads/LoRa_End_Node/Battery_Analyze/DRAGINO_Battery_Life_Guide.pdf>>https://www.dragino.com/downloads/downloads/LoRa_End_Node/Battery_Analyze/DRAGINO_Battery_Life_Guide.pdf]]
++)))
++
++
++(((
++A full detail test report for LHT65N-E5 on different frequency can be found at : [[https:~~/~~/www.dropbox.com/sh/r2i3zlhsyrpavla/AAB1sZw3mdT0K7XjpHCITt13a?dl=0>>https://www.dropbox.com/sh/r2i3zlhsyrpavla/AAB1sZw3mdT0K7XjpHCITt13a?dl=0]]
++)))
++
++
++= 6. FAQ =
++
++== 6.1 How to use AT Command? ==
++
++
++LHT65N-E5 supports AT Command set.User can use a USB to TTL adapter plus the Program Cable to connect to LHT65 for using AT command, as below.
++
++
++[[image:image-20220615153355-1.png||_mstalt="430222"]]
++
++
++
++[[image:1655802313617-381.png||_mstalt="293917"]]
++
++
++
++(((
++In PC, User needs to set serial tool(such as [[**putty**>>https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to (% style="color:green" %)**9600** (%%)to access to access serial console for LHT65N-E5. The AT commands are disable by default and need to enter password (default:(% style="color:green" %)**123456**(% style="color:red" %))(%%) to active it. Timeout to input AT Command is 5 min, after 5-minute, user need to input password again. User can use AT+DISAT command to disable AT command before timeout.
++)))
++
++[[image:image-20220615154519-3.png||_mstalt="431925" height="672" width="807"]]
++
++AT Command List is as below:
++
++AT+<CMD>? :                  Help on <CMD>
++
++AT+<CMD> :                   Run <CMD>
++
++AT+<CMD>=<value> :   Set the value
++
++AT+<CMD>=? :               Get the value
++
++AT+DEBUG:    Set more info output
++
++ATZ:                Trig a reset of the MCU
++
++AT+FDR:         Reset Parameters to Factory Default, Keys Reserve
++
++AT+DEUI:       Get or Set the Device EUI
++
++AT+DADDR:   Get or Set the Device Address
++
++AT+APPKEY:   Get or Set the Application Key
++
++AT+NWKSKEY:   Get or Set the Network Session Key
++
++AT+APPSKEY:     Get or Set the Application Session Key
++
++AT+APPEUI:        Get or Set the Application EUI
++
++AT+ADR:       Get or Set the Adaptive Data Rate setting. (0: off, 1: on)
++
++AT+TXP:        Get or Set the Transmit Power (0-5, MAX:0, MIN:5, according to LoRaWAN Spec)
++
++AT+DR:         Get or Set the Data Rate. (0-7 corresponding to DR_X)
++
++AT+DCS:       Get or Set the ETSI Duty Cycle setting - 0=disable, 1=enable - Only for testing
++
++AT+PNM:      Get or Set the public network mode. (0: off, 1: on)
++
++AT+RX2FQ:    Get or Set the Rx2 window frequency
++
++AT+RX2DR:    Get or Set the Rx2 window data rate (0-7 corresponding to DR_X)
++
++AT+RX1DL:    Get or Set the delay between the end of the Tx and the Rx Window 1 in ms
++
++AT+RX2DL:    Get or Set the delay between the end of the Tx and the Rx Window 2 in ms
++
++AT+JN1DL:     Get or Set the Join Accept Delay between the end of the Tx and the Join Rx Window 1 in ms
++
++AT+JN2DL:     Get or Set the Join Accept Delay between the end of the Tx and the Join Rx Window 2 in ms
++
++AT+NJM:        Get or Set the Network Join Mode. (0: ABP, 1: OTAA)
++
++AT+NWKID:    Get or Set the Network ID
++
++AT+FCU:        Get or Set the Frame Counter Uplink
++
++AT+FCD:        Get or Set the Frame Counter Downlink
++
++AT+CLASS:    Get or Set the Device Class
++
++AT+JOIN:       Join network
++
++AT+NJS:        Get the join status
++
++AT+SENDB:   Send hexadecimal data along with the application port
++
++AT+SEND:     Send text data along with the application port
++
++AT+RECVB:    Print last received data in binary format (with hexadecimal values)
++
++AT+RECV:      Print last received data in raw format
++
++AT+VER:        Get current image version and Frequency Band
++
++AT+CFM:       Get or Set the confirmation mode (0-1)
++
++AT+CFS:        Get confirmation status of the last AT+SEND (0-1)
++
++AT+SNR:       Get the SNR of the last received packet
++
++AT+RSSI:       Get the RSSI of the last received packet
++
++AT+TDC:       Get or set the application data transmission interval in ms
++
++AT+PORT:     Get or set the application port
++
++AT+DISAT:    Disable AT commands
++
++AT+PWORD: Set password, max 9 digits
++
++AT+CHS:       Get or Set Frequency (Unit: Hz) for Single Channel Mode
++
++AT+CHE:       Get or Set eight channels mode,Only for US915,AU915,CN470
++
++AT+PDTA:      Print the sector data from start page to stop page
++
++AT+PLDTA:    Print the last few sets of data
++
++AT+CLRDTA:  Clear the storage, record position back to 1st
++
++AT+SLEEP:     Set sleep mode
++
++AT+EXT:        Get or Set external sensor model
++
++AT+BAT:        Get the current battery voltage in mV
++
++AT+CFG:        Print all configurations
++
++AT+WMOD:   Get or Set Work Mode
++
++AT+ARTEMP:  Get or set the internal Temperature sensor alarm range
++
++AT+CITEMP:   Get or set the internal Temperature sensor collection interval in min
++
++AT+SETCNT:   Set the count at present
++
++AT+RJTDC:     Get or set the ReJoin data transmission interval in min
++
++AT+RPL:         Get or set response level
++
++AT+TIMESTAMP:   Get or Set UNIX timestamp in second
++
++AT+LEAPSEC:        Get or Set Leap Second
++
++AT+SYNCMOD:    Get or Set time synchronization method
++
++AT+SYNCTDC:      Get or set time synchronization interval in day
++
++AT+PID:                Get or set the PID
++
++
++== 6.2 Where to use AT commands and Downlink commands ==
++
++
  **AT commands：**
--[[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220620153708-1.png||_mstalt="429806" height="603" width="723"]]
++[[image:image-20220620153708-1.png||_mstalt="429806" height="603" width="723"]]
  **Downlink commands:**
@@ -677,13 +677,13 @@
  (% style="color:blue" %)**TTN:**
--[[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220615092124-2.png||_mstalt="429221" height="649" width="688"]]
++[[image:image-20220615092124-2.png||_mstalt="429221" height="649" width="688"]]
  (% style="color:blue" %)**Helium：**
--[[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220615092551-3.png||_mstalt="430794" height="423" width="835"]]
++[[image:image-20220615092551-3.png||_mstalt="430794" height="423" width="835"]]
@@ -690,52 +690,56 @@
  (% style="color:blue" %)**Chirpstack: The downlink window will not be displayed until the network is accessed**
--[[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220615094850-6.png||_mstalt="433082"]]
++[[image:image-20220615094850-6.png||_mstalt="433082"]]
--[[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220615094904-7.png||_mstalt="433485" height="281" width="911"]]
++[[image:image-20220615094904-7.png||_mstalt="433485" height="281" width="911"]]
  (% style="color:blue" %)**Aws:**
--[[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220615092939-4.png||_mstalt="434460" height="448" width="894"]]
++[[image:image-20220615092939-4.png||_mstalt="434460" height="448" width="894"]]
--== 7.3 How to change the uplink interval？ ==
++== 6.3 How to change the uplink interval？ ==
  Please see this link: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/How%20to%20set%20the%20transmit%20time%20interval/>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20set%20the%20transmit%20time%20interval/||_mstmutation="1" style="background-color: rgb(255, 255, 255);"]]
--[[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220615154519-3.png||_mstalt="431925" height="672" width="807"]]
--== 7.4 How to use TTL-USB to connect PC to upgrade firmware? ==
++[[image:image-20220615154519-3.png||_mstalt="431925" height="672" width="807"]]
--[[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220615153355-1.png||_mstalt="430222"]]
++== 6.4 How to use TTL-USB to connect PC to upgrade firmware? ==
++[[image:image-20220615153355-1.png||_mstalt="430222"]]
++
++
  (% style="color:blue" %)**Step1**(%%): Install TremoProgrammer  first.
--[[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220615170542-5.png||_mstalt="430638"]]
++[[image:image-20220615170542-5.png||_mstalt="430638"]]
++
  (% _mstmutation="1" style="color:blue" %)**Step2**(%%)：wiring method.(% style="display:none" %)
  First connect the four lines；(% style="display:none" %)
--[[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220621170938-1.png||_mstalt="431340" height="413" width="419"]]，(% style="display:none" %)
++[[image:image-20220621170938-1.png||_mstalt="431340" height="413" width="419"]]，(% style="display:none" %)
  Then use DuPont cable to short circuit port3 and port1, and then release them, so that the device enters bootlaod mode.
--[[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220621170938-2.png||_mstalt="431704"]]
++[[image:image-20220621170938-2.png||_mstalt="431704"]]
++
  (% style="color:blue" %)**Step3：**(%%)Select the device port to be connected, baud rate and bin file to be downloaded.
--[[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220615171334-6.png||_mstalt="431028"]]
++[[image:image-20220615171334-6.png||_mstalt="431028"]]
  Click the (% style="color:blue" %)**start**(%%) button to start the firmware upgrade.
@@ -743,17 +743,19 @@
  When this interface appears, it indicates that the download has been completed.
--[[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220620160723-8.png||_mstalt="430703"]]
++[[image:image-20220620160723-8.png||_mstalt="430703"]]
  Finally, unplug the DuPont cable on port4, and then use the DuPont cable to short circuit port3 and port1 to reset the device.
--[[image:Main.User Manual for LoRaWAN End Nodes.LHT65N-E5 LoRaWAN Temperature_Humidity & Illuminance Sensor User Manual.WebHome@image-20220615154519-3.png||_mstalt="431925" height="672" width="807"]]
--= 8. Order Info =
++[[image:image-20220615154519-3.png||_mstalt="431925" height="672" width="807"]]
++= 7. Order Info =
++
++
  Part Number: (% style="color:#4f81bd" %)** LHT65N-PIR-XX**
  (% style="color:#4f81bd" %)**XX **(%%): The default frequency band
@@ -767,27 +767,26 @@
  * (% style="color:#4f81bd" %)** **(% _mstmutation="1" style="color:red" %)**IN865**(%%): LoRaWAN IN865 band
  * (% style="color:#4f81bd" %)** **(% _mstmutation="1" style="color:red" %)**CN470**(%%): LoRaWAN CN470 band
++= 8. Packing Info =
--= 9. Packing Info =
--
--
  **Package Includes**:
  * LHT65N-PIR Temperature/Humidity/PIR Sensor x 1
++**Dimension and weight**:
++* Device Size:  10 x 10 x 3.5 mm
++* Device Weight: 120.5g
--= 10. Reference material =
++= 9. Reference material =
  * [[Datasheet, photos, decoder, firmware>>https://www.dropbox.com/sh/una19zsni308dme/AACOKp6J2RF5TMlKWT5zU3RTa?dl=0]]
++= 10. FCC Warning =
--= 11. FCC Warning =
--
--
  This device complies with part 15 of the FCC Rules.Operation is subject to the following two conditions:
  (1) This device may not cause harmful interference；

1FPORT=5.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Ellie

Size

...	...	@@ -1,1 +1,0 @@
1		-34.8 KB

Content

ACT.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Ellie

Size

...	...	@@ -1,1 +1,0 @@
1		-49.3 KB

Content

AT+SLEEP.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Ellie

Size

...	...	@@ -1,1 +1,0 @@
1		-5.8 KB

Content

AT+TDC.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Ellie

Size

...	...	@@ -1,1 +1,0 @@
1		-12.3 KB

Content

FPORT=5.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Ellie

Size

...	...	@@ -1,1 +1,0 @@
1		-29.4 KB

Content

LHT65N-E5.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Ellie

Size

...	...	@@ -1,1 +1,0 @@
1		-215.2 KB

Content

LHT65N-PIR1.jpg

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Ellie

Size

...	...	@@ -1,1 +1,0 @@
1		-47.3 KB

Content

add application1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Ellie

Size

...	...	@@ -1,1 +1,0 @@
1		-44.5 KB

Content

add application2.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Ellie

Size

...	...	@@ -1,1 +1,0 @@
1		-53.7 KB

Content

ext=14.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Ellie

Size

...	...	@@ -1,1 +1,0 @@
1		-30.5 KB

Content

image-20230409080812-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Edwin

Size

...	...	@@ -1,1 +1,0 @@
1		-249.6 KB

Content

image-20230411114550-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Edwin

Size

...	...	@@ -1,1 +1,0 @@
1		-268.1 KB

Content

image-20230411135341-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Edwin

Size

...	...	@@ -1,1 +1,0 @@
1		-113.6 KB

Content

image-20230426083533-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-190.0 KB

Content

image-20230508151932-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.kai

Size

...	...	@@ -1,1 +1,0 @@
1		-36.0 KB

Content

input APP EUI.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Ellie

Size

...	...	@@ -1,1 +1,0 @@
1		-57.6 KB

Content

shipped.jpeg

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Ellie

Size

...	...	@@ -1,1 +1,0 @@
1		-16.5 KB

Content