Skip to Content
Last modified by Mengting Qiu on 2025/07/03 15:02
Show last authors
1 [[image:image-20250228144849-1.jpeg||data-xwiki-image-style-alignment="center" height="490" width="490"]]
2
3
4
5
6 (% _mstvisible="1" %)
7 (% _msthash="315238" _msttexthash="18964465" _mstvisible="3" %)**Table of Contents：**
8
9 {{toc/}}
10
11
12
13
14
15
16
17
18 = 1.  Introduction =
19
20 == 1.1  What is the PB05-L LoRaWAN Push Button? ==
21
22
23 The **PB05-L LoRaWAN Button** is a wireless device with (% style="color:blue" %)**5 push buttons**(%%). When a button is pressed, the device sends a signal to the IoT server using the LoRaWAN protocol.
24
25 It runs on (% style="color:blue" %)**2 x AA batteries**(%%), lasting for approximately (% style="color:blue" %)**30k presses**(%%) across all five buttons. When the batteries run out, they can be easily replaced.
26
27 The PB05-L also has a **built-in speaker** that plays different sounds when a button is pressed or when a response is received from the server. If needed, the speaker can be turned off.
28
29 This device is **fully compatible with LoRaWAN v1.0.3** and works with any standard LoRaWAN gateway.
30
31 {{info}}
32 **Note:** Battery life depends on how often the device sends data. Check the [[battery analyzer>>||anchor="H4.2A0PowerConsumptionAnalyze"]] for details.
33 {{/info}}
34
35 == 1.2  Features ==
36
37
38 * Wall-mountable
39 * LoRaWAN v1.0.3 Class A protocol
40 * 5 push buttons
41 * Built-in speaker
42 * Frequency bands: CN470, EU433, KR920, US915, EU868, AS923, AU915
43 * AT commands for parameter configuration
44 * Remote parameter configuration via LoRaWAN downlink
45 * Firmware upgradeable via programming port
46 * Supports 2 × AA LR6 batteries
47 * IP52-rated for dust and water resistance
48
49 == 1.3  Power Consumption ==
50
51
52 * **Idle:** 5 µA
53 * **Transmit:** Max 110 mA
54
55 == 1.4  Storage & Operation Temperature ==
56
57
58 -10 ~~ 50 °C  or -40 ~~ 60 °C (depends on the battery type, see [[FAQ>>||anchor="H6.5Whyiseedifferentworkingtemperatureforthedevice3F"]])
59
60
61 == 1.5  Applications ==
62
63
64 * Smart Buildings & Home Automation
65 * Logistics and Supply Chain Management
66 * Smart Metering
67 * Smart Agriculture
68 * Smart Cities
69 * Smart Factory
70
71 See **Use Cases** (Section 7) for more information.
72
73
74 == 1.6 Device appearance ==
75
76
77 (% class="wikigeneratedid" %)
78 [[image:image-20250303102218-1.jpeg||height="340" width="572"]]
79
80 (% class="wikigeneratedid" %)
81 (% style="color:red" %)**Note: For customization purposes, the PVC sticker is not attached by default.**
82
83
84 == 1.7 Mechanical Drawings ==
85
86
87 [[image:image-20250312090840-1.png||height="509" width="671"]]
88
89
90 = 2.  Operation Mode =
91
92 == 2.1  How does it work? ==
93
94
95 Each PB05-L is shipped with a **unique set of LoRaWAN registration information**, including **DevEUI**, **AppEUI**, and **AppKey**. To use the PB05-L in a LoRaWAN network, the user must register these EUIs and keys **in advance** to enable OTAA activation of the device in the LoRaWAN network server.
96
97
98 [[image:image-20230426083617-1.png||height="294" width="633"]]
99
100
101 Once the device is powered on and within the network’s coverage, it will automatically join and start transmitting sensor data. By default, it sends an uplink every **20 minutes**.
102
103
104 == 2.2  How to Activate PB05-L? ==
105
106
107 (% style="color:red" %)** 1.  Open the enclosure from the bottom as shown in the image below.**
108
109 [[image:image-20250303105217-1.jpeg||height="298" width="493"]]
110
111
112 (% style="color:red" %)** 2.  Insert 2 x AA LR6 batteries. Make sure to insert them in the correct direction.**
113
114 [[image:image-20250303105439-2.jpeg||height="241" width="489"]]
115
116
117 (% style="color:red" %)** 3. Activate the device by pressing and holding (long press) the ACT button.**
118
119 [[image:image-20250303105945-3.jpeg||height="217" width="518"]]
120
121 You can check [[LED Status>>||anchor="H2.8LEDIndicator"]] to determine the working state of the PB05-L.
122
123
124 == 2.3 Joining with a LoRaWAN network server ==
125
126
127 This section shows an example of how to join The Things Stack LoRaWAN network server. Registering with other LoRaWAN network servers may also follow a similar procedure.
128
129 (% class="wikigeneratedid" _mstvisible="1" %)
130 The following network diagram shows that the PB05-L is connected to a LoRaWAN Network Server. The network server supports end-to-end data communication between the PB05-L and the application server. You can use any public LoRaWAN Network Server to register your device, or you can set up your own private LoRaWAN Network Server. The Things Stack (both free and paid) and ChirpStack are some of the popular LoRaWAN Network Servers available for use.
131
132
133 (% class="wikigeneratedid" _mstvisible="1" %)
134 The following network diagram illustrates how the PB05-L connects to a LoRaWAN network server and how end-to-end communication occurs between the PB05-L and the application server.
135
136 (% class="wikigeneratedid" _mstvisible="1" %)
137 The PB01-L sends LoRa-modulated uplink packet when a specific button (Button 1 to 5) is pressed by the user. The uplink packet is received by the LoRaWAN gateway and forwarded to the LoRaWAN Network Server via its internet connection. The Network Server then forwards the application payload of the uplink packet to the Application Server for further processing, enabling data analysis and valuable insights. Both the Application Server and the Network Server can send downlink messages to the PB05-L through the LoRaWAN gateway.
138
139
140 [[image:pb05-l-lorawan-nw.jpg||height="241" width="900"]]
141
142
143
144 === 2.3.1 Registering with The Things Stack ===
145
146 The following steps guide you through the process of registering the PB05-L with The Things Stack LoRaWAN network server.
147
148
149 ==== 2.3.1.1 Setting up ====
150
151 * Sign up for a free account with [[The Things Stack Sandbox>>url:https://eu1.cloud.thethings.network]] if you do not have one yet.
152 * Log in to your **The Things Stack** account.
153 * Create an **application** with The Things Stack if you do not have one yet.
154 ** On the left navigation, click **Applications**.
155 ** Then click **+ Add Application** button.
156
157 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LWL02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/lwl02-4.png?rev=1.1||alt="lwl02-4.png" height="768" width="1230"]]
158
159
160 * On the **Create Application **page, configure the following:
161 ** **Application ID**: Provide a unique identification for your application within The Things Stack.
162 ** **Application name**: (optional) Provide a descriptive name.
163 ** **Description**: (optional) Provide a description.
164 * Click on **Create application **button.
165
166 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LWL02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/lwl02-5.png?rev=1.1||alt="lwl02-5.png" height="802" width="1284"]]
167
168
169
170 * Go to your application's page and click on the **End devices** in the left menu.
171 * On the End devices page, click on **+ Register end device**.
172
173 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/lds02-step-5.png?width=1311&height=819&rev=1.1||alt="lds02-step-5.png" height="819" width="1311"]]
174
175
176
177 * Two registration options are available:
178 ** Using the LoRaWAN Device Repositoty
179 ** Manual registration
180
181 ==== 2.3.1.2 Manual registration ====
182
183 Currently, the PB05-L supports only manual registration.
184
185
186
187
188 * On the **Register end device** page:
189 ** Select the option **Enter end device specifies manually** under **Input method**.
190 ** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list.
191 ** Select the **LoRaWAN version** as **LoRaWAN Specification 1.0.3**
192 ** Select the **Regional Parameters version** as** RP001 Regional Parameters 1.0.3 revision A**
193 ** Enter **AppEUI** in the **JoinEUI** field. Then click **Confirm** button.
194
195 [[image:image-20250306095706-4.jpeg]]
196
197 * In the **DevEUI** field, enter the **DevEUI**.
198 * In the **AppKey** field, enter the **AppKey**.
199 * In the **End device ID** field, enter a unique name for your PB05 within this application.
200 * Under **After registration**, select the **View registered end device** option.
201 * Click the **Register end device** button.
202
203 [[image:image-20250306095754-5.jpeg]]
204
205
206 You will be navigated to the **Device overview** page.
207
208
209 ==== 2.3.1.3 Uplink Payload Formatter (Decoder) ====
210
211
212 To add the uplink formatter code, select **Applications > [your application] > End devices** > [**your end device]** > **Payload formatters** > **Uplink**. Then select **Use Device repository formatters** for the **Formatter type** dropdown. Click the **Save changes** button to apply the changes.
213
214 The uplink payload formatter for PB05-L can be downloaded from here: [[PB05-L decoder>>https://github.com/dragino/dragino-end-node-decoder/tree/main/PB05]].
215
216
217 [[image:image-20241030172839-3.png||height="508" width="918"]]
218
219
220 Press the ACT button to activate the PB05-L. It will then join The Things Stack. Once successfully joined, it will start uploading sensor data to The Things Stack, which you can view on the Live Data panel.
221
222
223 [[image:image-20241030173150-5.png||height="304" width="1292"]]
224
225
226 == 2.4  Uplink Payload ==
227
228
229 Uplink payloads include two types: **Valid Sensor Valu**e and **Other Status / Control Commands**.
230
231 * **Valid Sensor Value**: Use FPort=2
232 * **Other Status / Control Commands**: Use an FPort other than 2.
233
234 === 2.4.1  Uplink FPort~=5, Device Status ===
235
236
237 You can get the **Device Status** uplink through the downlink command:
238
239 (% style="color:#4472c4" %)**Downlink:  **(%%)**0x2601**
240
241 The device uplinks the status using FPort=5.
242
243 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:370px" %)
244 |=(% style="width: 60px;background-color:#4F81BD;color:white" %)**Size (bytes)(% style="display:none" %) (%%)**|=(% style="width: 60px;background-color:#4F81BD;color:white" %)**1**|=(% style="width: 80px;background-color:#4F81BD;color:white" %)**2**|=(% style="width: 80px;background-color:#4F81BD;color:white" %)**1**|=(% style="width: 60px;background-color:#4F81BD;color:white" %)**1**|=(% style="width: 30px;background-color:#4F81BD;color:white" %)**2**
245 |(% style="width:99px" %)Value|(% style="width:62px" %)Sensor Model|(% style="width:80px" %)Firmware Version|(% style="width:82px" %)Frequency Band|(% style="width:85px" %)Sub-band|(% style="width:46px" %)BAT
246
247 Example from The Things Stack:
248
249 [[image:image-20241030165804-1.png]]
250
251 Example payload (FPort=5):  [[image:image-20241030170029-2.png||height="24" width="136"]]
252
253 (% style="color:#4472c4" %)**Sensor Model**(%%): For PB05-L, this value is 0x3B.
254
255 (% style="color:#4472c4" %)**Firmware Version**(%%): 0x0100 means the version is v1.0.0.
256
257 (% style="color:#4472c4" %)**Frequency Band**:
258
259 * 0x01: EU868
260 * 0x02: US915
261 * 0x03: IN865
262 * 0x04: AU915
263 * 0x05: KZ865
264 * 0x06: RU864
265 * 0x07: AS923
266 * 0x08: AS923-1
267 * 0x09: AS923-2
268 * 0x0a: AS923-3
269
270 (% style="color:#4472c4" %)**Sub-Band**(%%): Value 0x00 to 0x08 (only for CN470, AU915, and US915. For other regions, use 0x00.)
271
272 (% style="color:#4472c4" %)**BAT**(%%): Shows the battery voltage of PB05-L.
273
274 (% style="color:#4472c4" %)**Example**(%%): 0x0C48 = 3144mV
275
276
277 === 2.4.2  Uplink FPort~=2, Real-time sensor value ===
278
279
280 The PB05-L will send this uplink after the Device Status uplink once it has successfully joined the LoRaWAN network. It will then continue to send this uplink periodically. The default interval is **20 minutes**, but it [[can be changed>>||anchor="H3.1A0DownlinkCommandSet"]].
281
282 This uplink uses FPort=2 and, by default, is sent once every 20 minutes.
283
284
285 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:470px" %)
286 |=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
287 **Size(bytes)**
288 )))|=(% style="width: 50px; background-color: rgb(79, 129, 189); color: white;" %)2|=(% style="width: 170px; background-color: rgb(79, 129, 189); color: white;" %)(((
289 **1**
290 )))|=(% style="width: 50px; background-color: rgb(79, 129, 189); color: white;" %)(((
291 **1**
292 )))|=(% style="width: 140px; background-color: rgb(79, 129, 189); color: white;" %)(((
293 **1**
294 )))
295 |(% style="width:97px" %)(((
296 Value
297 )))|(% style="width:63px" %)Battery|(% style="width:101px" %)(((
298 Sound_key & Sound_ACK
299 )))|(% style="width:62px" %)(((
300 (((
301 Alarm
302 )))
303 )))|(% style="width:140px" %)key1 & key2 & key3 & key4 & key5
304
305 (% style="color:blue" %)**key1 & key2 & key3 & key4 & key5:**
306
307 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:470px" %)
308 |=(% style="width: 81px; background-color: rgb(79, 129, 189); color: white;" %)**Size(bit)**|=(% style="width: 79px; background-color: rgb(79, 129, 189); color: white;" %)**bit[1:7]**|=(% style="width: 310px; background-color: rgb(79, 129, 189); color: white;" %)**bit0**
309 |(% style="width:81px" %)(((
310 Value
311 )))|(% style="width:79px" %)Reserve|(% style="width:294px" %)key1 & key2 & key3 & key4 & key5
312
313 Example from The Things Stack.
314
315 [[image:image-20241031101215-3.png]]
316
317
318 * (((
319 (% class="wikigeneratedid" id="HBattery:" %)
320 (% style="color:blue" %)**Battery:**
321 )))
322
323 To get the battery voltage.
324
325 Example 1: 0x0CEA = 3306mV
326
327 Example 2: 0x0D08 = 3336mV
328
329
330 * (% style="color:blue" %)**Sound_key & Sound_ACK:**
331
332 Key sound and ACK sound are enabled by default.
333
334 Example 1: 0x03
335
336 Sound_ACK: (03>>1) & 0x01=1, OPEN.
337
338 **~ ** Sound_key:  03 & 0x01=1, OPEN.
339
340 Example 2: 0x01
341
342 Sound_ACK: (01>>1) & 0x01=0, CLOSE.
343
344 **~ ** Sound_key:  01 & 0x01=1, OPEN.
345
346
347 * (% style="color:blue" %)**Alarm:**
348
349 Key alarm.
350
351 Example 1: 0x01 & 0x01=1, "TRUE", key alarm packet.
352
353 Example 2: 0x00 & 0x01=0, "FALSE", normal uplink data.
354
355
356 * (% style="color:blue" %)**key1**
357
358 (% class="wikigeneratedid" %)
359 Displays whether the uplink data was triggered by key 1.
360
361 01 (H): (0x01&0x01)=01(H) =0000 000**1**(B)  bit0=1, "Yes"
362
363 02 (H): (0x02&0x01)=0  bit0=0, "No"
364
365
366 * (% style="color:blue" %)**key2**
367
368 (% class="wikigeneratedid" %)
369 Displays whether the uplink data was triggered by key 2.
370
371 02 (H): (0x02>>1)&0x01 =01(H) =0000 000**1**(B)  bit0=1, "Yes"
372
373 04 (H): (0x04>>1)&0x01 =0  bit0=0, "No"
374
375
376 * (% style="color:blue" %)**key3**
377
378 (% class="wikigeneratedid" %)
379 Displays whether the uplink data was triggered by key 3.
380
381 04 (H): (0x04>>2)&0x01 =01(H) =0000 000**1**(B)  bit0=1, "Yes"
382
383 08 (H): (0x08>>2)&0x01 =0  bit0=0, "No"
384
385
386 * (% style="color:blue" %)**key4**
387
388 (% class="wikigeneratedid" %)
389 Displays whether the uplink data was triggered by key 4.
390
391 08 (H): (0x08>>3)&0x01 =01(H) =0000 000**1**(B)  bit0=1, "Yes"
392
393 10 (H): (0x10>>3)&0x01 =0  bit0=0, "No"
394
395
396 * (% style="color:blue" %)**key5**
397
398 (% class="wikigeneratedid" %)
399 Displays whether the uplink data was triggered by key 5.
400
401 10 (H): (0x10>>4)&0x01 =01(H) =0000 000**1**(B)  bit0=1, "Yes"
402
403 01 (H): (0x01>>4)&0x01 =0  bit0=0, "No"
404
405
406 === 2.4.3  Uplink FPort~=3, Datalog sensor value ===
407
408
409 PB05-L stores sensor values, and the user can retrieve this historical data via a downlink command. The datalogged sensor values are sent via FPort=3.
410
411 The historical payload includes one or multiple entries.
412
413 (% border="1" cellspacing="2" style="background-color:#f2f2f2; width:510px" %)
414 |=(% style="width: 60px; background-color: rgb(79, 129, 189); color: white;" %)(((
415 **Size(bytes)**
416 )))|=(% style="width: 50px; background-color: rgb(79, 129, 189); color: white;" %)4|=(% style="width: 170px; background-color: rgb(79, 129, 189); color: white;" %)(((
417 **1**
418 )))|=(% style="width: 50px; background-color: rgb(79, 129, 189); color: white;" %)(((
419 **1**
420 )))|=(% style="width: 110px; background-color: rgb(79, 129, 189); color: white;" %)(((
421 **1**
422 )))|=(% style="width: 70px; background-color: rgb(79, 129, 189); color: white;" %)4
423 |(% style="width:87px" %)(((
424 Value
425 )))|(% style="width:78px" %)Reserve|(% style="width:102px" %)(((
426 key5 & key4 & key3 & key2 & key1
427 )))|(% style="width:75px" %)Reserve|(% style="width:55px" %)Poll message flag & alarm|(% style="width:68px" %)Unix Time Stamp
428
429 (% style="color:blue" %)**key5 & key4 & key3 & key2 & key1:**
430
431 (% border="1" cellspacing="2" style="background-color:#f2f2f2; width:470px" %)
432 |=(% style="width: 81px; background-color: rgb(79, 129, 189); color: white;" %)**Size(bit)**|=(% style="width: 79px; background-color: rgb(79, 129, 189); color: white;" %)**bit[1:7]**|=(% style="width: 310px; background-color: rgb(79, 129, 189); color: white;" %)**bit0**
433 |(% style="width:81px" %)(((
434 Value
435 )))|(% style="width:79px" %)Reserve|(% style="width:294px" %)key5 & key4 & key3 & key2 & key1
436
437 (% style="color:blue" %)**Poll message flag & Alarm:**
438
439 (% border="1" cellspacing="2" style="background-color:#f2f2f2; width:510px" %)
440 |=(% style="width: 60px;background-color:#4F81BD;color:white" %)**Size(bit)**|=(% style="width: 80px; background-color: rgb(79, 129, 189); color: white;" %)**bit**7|=(% style="width: 80px; background-color: rgb(79, 129, 189); color: white;" %)(((
441 **bit6**
442 )))|=(% style="width: 80px; background-color: rgb(79, 129, 189); color: white;" %)bit5|=(% style="width: 80px; background-color: rgb(79, 129, 189); color: white;" %)bit4|=(% style="width: 60px; background-color: rgb(79, 129, 189); color: white;" %)**bit[3:1]**|=(% style="width: 70px; background-color: rgb(79, 129, 189); color: white;" %)**bit0**
443 |(% style="width:97px" %)Status&Ext|(% style="width:63px" %)No ACK Message|(% style="width:101px" %)Poll Message Flag|(% style="width:140px" %)Sync time OK|(% style="width:140px" %)Unix Time Request|(% style="width:140px" %)Reserve|(% style="width:140px" %)(((
444 Alarm:1
445 )))
446
447 (% style="color:blue" %)**No ACK Message:**(%%) 1: This indicates that the payload is from an uplink message that did not receive an ACK from the server (related to the [[PNACKMD=1>>url:https://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT65N%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20Manual/#H4.13AutoSendNone-ACKmessages]] feature)
448
449 (% style="color:blue" %)**Poll Message Flag: **(%%)1: This indicates that the message is a reply to a poll message.
450
451
452 * Each data entry is 11 bytes long to save airtime and battery. PB05-L will send the maximum number of bytes allowed based on the current data rate (DR) and frequency band.(% style="display:none" %)
453
454 For example, in the US915 band, the maximum payload size for different DRs is:
455
456 1. **DR0**: Maximum is 11 bytes - the device sends one data entry.
457 1. **DR1**: Maximum is 53 bytes - the device sends 4 data entries (44 bytes total).
458 1. **DR2**: Payload includes 11 data entries.
459 1. **DR3**: Payload includes 22 data entries.
460
461 If you send the downlink command:  [[image:image-20241031142131-3.png||height="31" width="216"]]
462
463 Where:
464 **Start time:** 6722DD98 = 2024/10/31 (Thursday) 01:30:00
465 **Stop time:** 672300C0 = 2024/10/31 (Thursday) 04:00:00
466
467
468 PB05-L will uplink the following payload:
469
470 [[image:image-20241031135901-2.png]]
471
472 **000000001000416722E531**
473
474 000000000800416722E538000000000400416722E540000000000200416722E54A000000000100416722E552000000000000406722E9BA000000000000406722EE6A000000000000406722F31A000000000000406722F7CA000000001000416722F9BA000000001000416722F9F6000000000800416722FB0E000000000000406722FC7A
475
476 Where the first 11 bytes are for the first entry:
477
478 [[image:image-20241031153803-1.png||height="35" width="240"]]
479
480 The first four bytes are reserved - (do not indicate anything)
481
482 key5 & key4 & key3 & key2 & key1: __10(H)__
483
484 * key5: ((0x10>>4)&0x01) = 1, "Yes".
485 * key4: ((0x10>>3)&0x01) = 0, "No".
486 * key3: ((0x10>>2)&0x01) = 0, "No".
487 * key2: ((0x10>>2)&0x01) = 0, "No".
488 * key1: (0x10 & 0x01) = 0, "No".
489
490 The sixth byte is reserved - (does not indicate anything)
491
492 Poll Message Flag & Alarm: 0x41 (Hex) indicates a reply message. For the alarm, 0x41 & 0x01 = 1, which means "True."
493
494 Unix time is 0x6722E531= 1730340145s= 24/10/31 02:02:25
495
496
497 If the PB05-L has no data at the polling time, it will transmit an uplink containing 11 bytes of zeros.
498
499 [[image:image-20241031113339-4.png||height="307" width="1112"]](% style="display:none" %)
500
501 See  [[Datalog feature>>||anchor="H2.6A0DatalogFeature"]] for more informaton.
502
503 (% style="display:none" %) (%%)
504
505 == 2.5 Show data on Datacake ==
506
507
508 (((
509 The Datacake IoT platform provides a user-friendly interface to display sensor data in charts. Once your sensor data is available in The Things Stack, you can connect Datacake to The Things Stack and view the data in Datacake. Follow the steps below:
510
511
512 === 2.5.1 Prerequisites ===
513
514 * The Things Stack account
515 )))
516
517 (((
518 * Ensure that your PB05 is programmed and properly connected to the LoRaWAN network.
519
520 === 2.5.2 Procedure ===
521
522
523 )))
524
525 (((
526 First, configure your application to forward data to Datacake by adding an integration:
527
528
529 ~1. Go to The **Things Stack Console ~-~-> Applications ~-~-> Integrations ~-~-> Add Integrations**.
530 )))
531
532 (((
533 2. On the **Choose webhook template** page, click on the **Datacake**.
534 )))
535
536 (((
537
538 )))
539
540 (((
541 Please refer to the figure below:
542 )))
543
544 [[image:image-20240510150924-2.png||height="500" width="970"]]
545
546
547 Log in to **Datacake **and copy the **API token** from your account. You can find it under **Account Settings -> API Token**.
548
549 [[image:image-20240510151944-3.png||height="482" width="989"]]
550
551
552 In the** Setup webhook for Datacake** page, enter the following:
553
554 * Enter the **Webhook  ID**
555 * Paste the **API token** you copied from The Things Stack in the **Token **text box.
556
557 Click on the **Create Datacake webhook** button.
558
559 [[image:image-20241031114021-5.png||height="526" width="896"]]
560
561
562 In the Datacake, click **Devices **and then click on the **+Add Device** button.
563
564 [[image:image-20240510152300-5.png||height="249" width="995"]]
565
566
567 In the** Add Device** dialogue box, choose **LoRaWAN**.
568
569 Then click on the **Next **button.
570
571
572 [[image:image-20240510152355-6.png||height="459" width="701"]]
573
574
575 In the **Add LoRaWAN Device** dialogue box, configure the following:
576
577 **STEP 1:**
578
579 * Choose **New Product**.
580 * Enter the** product name** in the **Product Name** text box. pb05-l, for example.
581
582 Click on the **Next** button.
583
584
585 [[image:image-20241031114330-6.png||height="462" width="626"]]
586
587
588 **STEP 2:**
589
590 * Choose **The Things Stack V3.**
591
592 Click on the **Next **button.
593
594
595 [[image:image-20240510152634-9.png||height="609" width="602"]]
596
597
598 STEP 3:
599
600 * Enter the **DevEUI** of the PB05 in the **DEVEUI **box.
601 * Type //**PB05**// in the **NAME **text box.
602
603 Click the **Next **button.
604
605 [[image:image-20241031114443-7.png||height="498" width="601"]]
606
607
608 Go to the PB05's configuration page.
609
610 [[image:image-20241031114600-8.png||height="295" width="826"]]
611
612
613 Copy and paste the [[TTN decoder>>https://github.com/dragino/dragino-end-node-decoder/tree/main/PB05]] in the Payload Decoder box and click the **Save **button.
614
615 [[image:image-20240510153624-13.png||height="286" width="731"]]
616
617
618 To learn about how to add visual widgets in the Datacake to visualise the data, please read the **Datacake **[[documentation>>https://docs.datacake.de/]].
619
620 (% style="display:none" %) (%%)
621
622 == 2.6  Datalog Feature ==
623
624
625 Datalog Feature is to ensure IoT Server can get all sampling data from Sensor even if the LoRaWAN network is down. For each sampling, PB05 will store the reading for future retrieving purposes.
626
627
628 === 2.5.1 How datalog works ===
629
630
631 PB05 will wait for ACK for every uplink, when there is no LoRaWAN network,PB05 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.
632
633 * (((
634 a) PB05 will do an ACK check for data records sending to make sure every data arrive server.
635 )))
636 * (((
637 b) PB05 will send data in **CONFIRMED Mode**, but PB05 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 PB05 gets a ACK, PB05 will consider there is a network connection and resend all NONE-ACK messages.
638
639
640 )))
641
642 === 2.5.2 Enable Datalog ===
643
644
645 User need to make sure below two settings are enable to use datalog;
646
647 * (% style="color:blue" %)**SYNCMOD=1(Default)**(%%) to enable sync time via LoRaWAN MAC command, click here ([[AT+SYNCMOD>>https://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/#H4.6Settimesynchronizationmethod28ThenetworkservermustsupportLoRaWANv1.0.329]]) for detailed instructions.
648 * (% style="color:blue" %)**PNACKMD=1**(%%)** **to enable datalog feature, click here ([[AT+PNACKMD>>https://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/#H7.26RequesttheservertosendanACK]]) for detailed instructions.
649
650
651
652 Once PB05 Joined LoRaWAN network, it will send the MAC command (DeviceTimeReq) and the server will reply with (DeviceTimeAns) to send the current time to PB05 . If PB05 fails to get the time from the server, PB05 will use the internal time and wait for next time request (AT+SYNCTDC to set the time request period, default is 10 days).
653
654 (% 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.**
655
656
657 === 2.6.1  Unix TimeStamp ===
658
659
660 The Unix timestamp shows the sampling time of the uplink payload. The following figure shows the **DeviceTimeAns** payload format.
661
662 [[image:image-20220523001219-11.png||_mstalt="450450" _mstvisible="3" height="97" width="627"]]
663
664
665 To get the current Unix epoch time, visit the website [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/||_mstvisible="3"]] :
666
667 For example, if the Unix epoch time is 1611889090, you can convert it to hex using a Decimal to Hex Converter available online, such as Code Beautify. For this example, the equivalent hex value is 0x60137afd.
668
669
670 [[image:1655782409139-256.png]]
671
672
673 === 2.6.2 Set Device Time ===
674
675
676 (((
677 (% style="color:blue" %)**There are two ways to set the device's time:**
678 )))
679
680 (((
681 **1.  Through LoRaWAN MAC Command (Default settings)**
682 )))
683
684 (((
685 You need to set **AT+SYNCMOD=1** to enable time synchronisation via the MAC command.
686
687 Once the PB05-L joins a LoRaWAN network, it sends a MAC command (DeviceTimeReq). The server responds with a DeviceTimeAns to provide the current time to the PB05-L. If the PB05-L fails to get the time from the server, it will use its internal clock and wait for the next time request.
688
689 You can use **AT+SYNCTDC** to set the time request period (default is 10 days).
690 )))
691
692 (((
693 {{info}}
694 **Note:** The LoRaWAN server needs to support **LoRaWAN v1.0.3 (MAC v1.0.3)** or higher to enable this MAC command feature.
695 **ChirpStack**, **TTS V3 (v3)**, and **Loriot** support it, but **TTS V3 (v2)** does not.
696 If the server does not support this command, it will **discard** the uplink packet containing the time request. As a result, the user will lose the time request packet when using **TTS V3 (v2)** with SYNCMOD=1.
697 {{/info}}
698
699
700 )))
701
702 (((
703 **2. Manually Set Time**
704 )))
705
706 (((
707 You need to set **AT+SYNCMOD=0** to enable manual time configuration. Otherwise, the time you set will be overwritten by the time provided by the server.
708 )))
709
710
711 === 2.6.3 Poll sensor value ===
712
713
714 You can poll sensor values based on timestamps from the server.
715
716
717 Below is the downlink command.
718
719 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:428px" %)
720 |(% style="background-color:#4f81bd; color:white; width:59px" %)**1byte**|(% style="background-color:#4f81bd; color:white; width:128px" %)**4bytes**|(% style="background-color:#4f81bd; color:white; width:124px" %)**4bytes**|(% style="background-color:#4f81bd; color:white; width:117px" %)**1byte**
721 |(% style="width:58px" %)31|(% style="width:128px" %)Timestamp start|(% style="width:123px" %)Timestamp end|(% style="width:116px" %)Uplink Interval
722
723 Timestamp start and Timestamp end use Unix Timestamp format as mentioned above. Devices will reply with all data logs during this time period, using the uplink interval.
724
725 For example, downlink command [[image:image-20241031142131-3.png||height="31" width="216"]]
726
727 Is to check 2024/10/31 01:30:00 to 2020/12/1 04:00:00's data
728
729 Uplink Internal =5s, means PB05-L will send one packet every 5s, range 5~~255s.
730
731
732 === 2.6.4  Datalog Uplink payload ===
733
734
735 See, [[Uplink FPort=3, Datalog sensor value>>||anchor="H2.4.3A0UplinkFPORT3D32CDatalogsensorvalue"]]
736
737 (% style="display:none" %) (%%) (% style="display:none" %)
738
739 == 2.7 Buttons ==
740
741
742 * **ACT button**
743
744 Long-press the ACT button to reset the device and allow it to join the network again.
745
746 [[image:image-20250303110613-4.jpeg||height="198" width="472"]]
747
748 * **Alarm buttons**
749
750 When you press the alarm button, the PB05-L immediately uplinks data. The alarm flag is set to 'TRUE,' and the corresponding button status is 'Yes'.
751
752 [[image:image-20250303111505-5.jpeg||height="252" width="374"]](% style="display:none" %)
753
754
755 == 2.8 LED Indicators ==
756
757
758 (((
759 The** PB05-L** has a **tri-color LED** for easily indicating different stages.
760
761 Hold the **ACT** button until the green light turns on to reset the device. The green LED will flash as the node restarts, the blue LED will flash once when requesting network access, and the green LED will remain on for 5 seconds after successful network access.
762 )))
763
764 (((
765 **In a normal working state:**
766
767 * When the node restarts, hold the ACT button until the GREEN LED lights up. The GREEN LED will flash as the node restarts.
768 * The BLUE LED will flash once upon requesting network access.
769 * The GREEN LED will remain on for 5 seconds after successful network access.
770
771 **During OTAA Join:**
772
773 * For each Join Request uplink, the GREEN LED will blink once.
774 * Once the Join is successful, the GREEN LED will remain on for 5 seconds.
775 * After joining, for each uplink, either the BLUE or GREEN LED will blink once.
776
777 **Alarm Button Press:**
778
779 * When an alarm button is pressed, the RED LED will flash until the node receives an ACK from the platform.
780 * Once the ACK is received, the BLUE LED will stay on for 5 seconds.
781
782
783 )))
784
785 == 2.9 Buzzer ==
786
787
788 The PB05 has a **button sound** and an **ACK sound**, both of which users can turn on or off using [[AT+SOUND>>||anchor="H3.3A0SetbuttonsoundandACKsound"]].
789
790 * (% style="color:#4f81bd" %)**Button sound**(%%) is the tone played by the node after an alarm button is pressed.
791 You can use [[AT+OPTION>>||anchor="H3.4A0Setbuzzermusictype2807E429"]] to set different button sounds.
792 * (% style="color:#4f81bd" %)**ACK sound**(%%) is the notification tone played when the node receives an ACK.
793
794 == 2.10 E2 Extension Cable ==
795
796
797 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT65N%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20Manual/WebHome/image-20220619092222-1.png?width=188&height=182&rev=1.1||alt="image-20220619092222-1.png"]][[image:image-20250303135532-3.jpeg||height="184" width="234"]]
798
799
800 **1m Long Breakout Cable for PB05-L**
801
802 **Features:**
803
804 * Used for AT commands; compatible with LHT52, LHT65N, and PB05-L.
805 * Supports firmware updates for PB05-L; also works with LHT52 and LHT65N.
806 * Exposes all pins from the PB05-L Type-C connector.
807
808 The following diagram shows the pin mapping between PB05 and the E2 Cable.
809
810 [[image:image-20250303134914-1.png||height="320" width="456"]]
811
812
813 = 3.  Configure PB05-L via AT command or LoRaWAN downlink =
814
815
816 You can configure PB05-L via AT Command or LoRaWAN Downlink command.
817
818 * **AT Command Connection: **
819
820 [[image:image-20250303141745-4.jpeg||height="489" width="505"]]
821
822
823 (((
824 On a PC, you need to set the serial tool (such as [[PuTTY>>https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]] or SecureCRT) to a baud rate of **9600** to access the serial console for the PB05-L.
825
826 AT commands are disabled by default and require entering a password (default: **123456**) to activate them. The AT command input timeout is 5 minutes; after this period, the user must enter the password again.
827
828 Enter the password and ATZ to activate the PB05-L, as shown below:
829
830
831 [[image:image-20250303114409-8.png]]
832
833
834 )))
835
836 * LoRaWAN Downlink instructions for different platforms can be found here: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
837
838 (((
839 There are two types of commands to configure the PB05-L:
840
841 **General Commands**
842
843 These commands configure:
844
845 * General system settings, such as the uplink interval.
846 * LoRaWAN protocol and radio-related settings.
847
848 These commands are the same for all Dragino devices that support the DLWS-005 LoRaWAN stack (**Note~*~***). They can be found on the wiki: [[End Device Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]].
849
850 **Commands Specifically Designed for PB05-L**
851
852 These commands are only valid for the PB05-L, as listed below:
853
854
855 )))
856
857 == 3.1  Downlink Command Set ==
858
859
860 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
861 |=(% style="width: 100px; background-color: rgb(79, 129, 189); color: white;" %)**Command Example**|=(% style="width: 161px; background-color: rgb(79, 129, 189); color: white;" %)**Function**|=(% style="width: 92px; background-color: rgb(79, 129, 189); color: white;" %)**Response**|=(% style="width: 157px; background-color: rgb(79, 129, 189); color: white;" %)**Downlink**
862 |(% style="width:130px" %)AT+TDC=?|(% style="width:151px" %)(((
863 View current TDC time
864 )))|(% style="width:92px" %)(((
865 1200000
866 OK
867 )))|(% style="width:206px" %)Default 1200000(ms)
868 |(% style="width:130px" %)AT+TDC=300000|(% style="width:151px" %)Set TDC time|(% style="width:92px" %)OK|(% style="width:206px" %)(((
869 (((
870 0X0100012C:
871 01: Fixed command
872 00012C: 0X00012C=
873
874 300(seconds)
875 )))
876
877 (((
878
879 )))
880 )))
881 |(% style="width:130px" %)ATZ|(% style="width:151px" %)Reset node|(% style="width:92px" %) |(% style="width:206px" %)0x04FF
882 |(% style="width:130px" %)AT+FDR|(% style="width:151px" %)Restore factory settings|(% style="width:92px" %) |(% style="width:206px" %)0X04FE
883 |(% style="width:130px" %)AT+CFM=?|(% style="width:151px" %)View the current confirmation mode status|(% style="width:92px" %)(((
884 0,7,0
885 OK
886 )))|(% style="width:206px" %)Default 0,7,0
887 |(% style="width:130px" %)AT+CFM=1,7,1|(% style="width:151px" %)(((
888 Confirmed uplink mode. The maximum number of retries is seven, and the uplink FCnt increases by 1 for each retry.
889 )))|(% style="width:92px" %)(((
890 OK
891 )))|(% style="width:206px" %)(((
892 05010701
893 05: Fixed command
894 01: Confirmed uplink
895 07: Retry 7 times
896 01: FCnt count plus 1
897 )))
898 |(% style="width:130px" %)AT+NJM=?|(% style="width:151px" %)(((
899 Check the current network connection method.
900 )))|(% style="width:92px" %)(((
901 1
902 OK
903 )))|(% style="width:206px" %)Default 1
904 |(% style="width:130px" %)AT+NJM=0|(% style="width:151px" %)Change the network connection method to ABP.|(% style="width:92px" %)(((
905 Attention: Take effect after ATZ
906 OK
907 )))|(% style="width:206px" %)(((
908 0X2000: ABP
909 0x2001: OTAA
910 20: Fixed command
911 )))
912 |(% style="width:130px" %)AT+RPL=?|(% style="width:151px" %)View current RPL settings|(% style="width:92px" %)(((
913 0
914 OK
915 )))|(% style="width:206px" %)Default 0
916 |(% style="width:130px" %)AT+RPL=1|(% style="width:151px" %)set RPL=1    |(% style="width:92px" %)OK|(% style="width:206px" %)(((
917 0x2101:
918 21: Fixed command
919 01: For details, check the wiki
920 )))
921 |(% style="width:130px" %)AT+ADR=?|(% style="width:151px" %)View current ADR status|(% style="width:92px" %)(((
922 1
923 OK
924 )))|(% style="width:206px" %)Default 0
925 |(% style="width:130px" %)AT+ADR=0|(% style="width:151px" %)Set the ADR state to off|(% style="width:92px" %)OK|(% style="width:206px" %)(((
926 0x2200: Close
927 0x2201: Open
928 22: Fixed command
929 )))
930 |(% style="width:130px" %)AT+DR=?|(% style="width:151px" %)View the current DR settings|(% style="width:92px" %)OK|(% style="width:206px" %)
931 |(% style="width:130px" %)AT+DR=1|(% style="width:151px" %)(((
932 Set DR to 1
933 It takes effect only when ADR=0
934 )))|(% style="width:92px" %)OK|(% style="width:206px" %)(((
935 0X22000101:
936 00: ADR=0
937 01: DR=1
938 01: TXP=1
939 22: Fixed command
940 )))
941 |(% style="width:130px" %)AT+TXP=?|(% style="width:151px" %)View the current TXP|(% style="width:92px" %)OK|(% style="width:206px" %)
942 |(% style="width:130px" %)AT+TXP=1|(% style="width:151px" %)(((
943 Set TXP to 1
944 It takes effect only when ADR=0
945 )))|(% style="width:92px" %)OK|(% style="width:206px" %)(((
946 0X22000101:
947 00: ADR=0
948 01: DR=1
949 01: TXP=1
950 22: Fixed command
951 )))
952 |(% style="width:130px" %)AT+RJTDC=10|(% style="width:151px" %)Set the RJTDC time interval|(% style="width:92px" %)OK|(% style="width:206px" %)(((
953 0X26000A:
954 26: Fixed command
955 000A: 0X000A=10(min)
956 For details, check the wiki
957 )))
958 |(% style="width:130px" %) |(% style="width:151px" %)(((
959 (((
960 ~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_
961
962 Retrieve stored data for a specified period of time
963 )))
964
965 (((
966
967 )))
968 )))|(% style="width:92px" %) |(% style="width:206px" %)(((
969 0X3161DE7C7061DE8A800A:
970 31: Fixed command
971 61DE7C70:0X61DE7C70=2022/1/12 15:00:00
972 61DE8A80:0X61DE8A80=2022/1/12 16:00:00
973 0A: 0X0A=10(second)
974 View details 2.6.2
975 )))
976 |(% style="width:130px" %)AT+DDETECT=?|(% style="width:151px" %)View the current DDETECT setting status and time|(% style="width:92px" %)(((
977 1,1440,2880
978 OK
979 )))|(% style="width:206px" %)Default 1,1440,2880(min)
980 |(% style="width:130px" %)AT+DDETECT=(((
981 1,1440,2880
982 )))|(% style="width:151px" %)(((
983 Set the DDETECT setting status and time
984 ((% style="color:red" %)When the node does not receive the downlink packet within the set time, it will re-enter the network(%%))
985 )))|(% style="width:92px" %)OK|(% style="width:206px" %)(((
986 0X320005A0: Close
987 0X320105A0: Open
988 32: Fixed command
989 05A0: 0X05A0=1440(min)
990 )))
991
992 == 3.2  Set Password ==
993
994
995 **Feature**: Set the device password—maximum 9 digits.
996
997 (% style="color:#4f81bd" %)**AT Command: AT+PWORD**
998
999 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:372px" %)
1000 |(% style="background-color:#4f81bd; color:white; width:155px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:128px" %)**Function**|(% style="background-color:#4f81bd; color:white; width:89px" %)**Response**
1001 |(% style="width:155px" %)AT+PWORD=?|(% style="width:124px" %)Show password|(% style="width:86px" %)(((
1002 123456
1003 OK
1004 )))
1005 |(% style="width:155px" %)AT+PWORD=999999|(% style="width:124px" %)Set password|(% style="width:86px" %)OK
1006
1007 (% style="color:#4f81bd" %)**Downlink Command:**
1008
1009 No downlink command is available for this feature.
1010
1011
1012 == 3.3  Set button sound and ACK sound ==
1013
1014
1015 **Feature**: Turn on/off the button sound and the ACK sound/alarm.
1016
1017 (% style="color:#4f81bd" %)**AT Command: AT+SOUND**
1018
1019 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:372px" %)
1020 |(% style="background-color:#4f81bd; color:white; width:155px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:128px" %)**Function**|(% style="background-color:#4f81bd; color:white; width:89px" %)**Response**
1021 |(% style="width:155px" %)(((
1022 AT+SOUND=?
1023 )))|(% style="width:124px" %)Get the current status of the button sound and the ACK sound|(% style="width:86px" %)(((
1024 1,1
1025 OK
1026 )))
1027 |(% style="width:155px" %)(((
1028 AT+SOUND=0,1
1029 )))|(% style="width:124px" %)Turn off the button sound and turn on the ACK sound|(% style="width:86px" %)OK
1030
1031 (% style="color:#4f81bd" %)**Downlink Command: 0xA1 **
1032
1033 **Format**: Command Code/prefix (0xA1) followed by 2 bytes mode value.
1034
1035 The first byte after 0XA1 sets the button sound, and the second byte after 0XA1 sets the ACK sound.** (0: OFF, 1: ON)**
1036
1037 * **Example: **Downlink Payload: **A10001  **~/~/ Set AT+SOUND=0,1  Turn off the button sound and turn on ACK sound.
1038
1039 == 3.4  Set buzzer music type(0~~4) ==
1040
1041
1042 **Feature**: Set different alarm key response sounds. There are five different types of button music.
1043
1044 (% style="color:#4f81bd" %)**AT Command: AT+OPTION**
1045
1046 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:372px" %)
1047 |(% style="background-color:#4f81bd; color:white; width:155px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:128px" %)**Function**|(% style="background-color:#4f81bd; color:white; width:89px" %)**Response**
1048 |(% style="width:155px" %)(((
1049 AT+OPTION=?
1050 )))|(% style="width:124px" %)(((
1051 Get the buzzer music type
1052 )))|(% style="width:86px" %)(((
1053 3
1054
1055 OK
1056 )))
1057 |(% style="width:155px" %)AT+OPTION=1|(% style="width:124px" %)Set the buzzer music to type 1|(% style="width:86px" %)OK
1058
1059 (% style="color:#4f81bd" %)**Downlink Command: 0xA3**
1060
1061 **Format**: Command Code/Prefix (0xA3) followed by 1 byte mode value.
1062
1063 * **Example: **Downlink Payload: **A300  **~/~/ Set AT+OPTION=0 to set the buzzer music to type 0.
1064
1065 == 3.5  Set Valid Push Time ==
1066
1067
1068 Feature: Set the holding time for pressing the alarm button to avoid miscontact. Values range from** 0 ~~1000ms**.
1069
1070 (% style="color:#4f81bd" %)**AT Command: AT+STIME**
1071
1072 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:372px" %)
1073 |(% style="background-color:#4f81bd; color:white; width:155px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:128px" %)**Function**|(% style="background-color:#4f81bd; color:white; width:89px" %)**Response**
1074 |(% style="width:155px" %)(((
1075 AT+STIME=?
1076 )))|(% style="width:124px" %)(((
1077 Get the button sound time
1078 )))|(% style="width:86px" %)(((
1079 0
1080 OK
1081 )))
1082 |(% style="width:155px" %)(((
1083 AT+STIME=1000
1084 )))|(% style="width:124px" %)Set the button sound time to 1000**ms**|(% style="width:86px" %)OK
1085
1086 (% style="color:#4f81bd" %)**Downlink Command: 0xA2**
1087
1088 Format: Command Code/Prefix (0xA2) followed by 2 bytes mode value.
1089
1090 * **Example: **Downlink Payload: **A203E8   **~/~/ Set AT+STIME=1000  
1091
1092 **~ Explain: **Hold the alarm button for 10 seconds before the node will send the alarm packet.
1093
1094
1095 = 4.  Battery & How to replace =
1096
1097 == 4.1  Battery Type and Replacement ==
1098
1099
1100 PB05-L uses 2 x AA LR6(1.5v) batteries. If the batteries are running low (Shows 2.1v in the platform). You can buy generic AA batteries and replace them.
1101
1102 (% style="color:red" %)**Note: **
1103
1104 1.  The PB05-L doesn't have any screws so you can use a nail to open it by the middle.
1105
1106 [[image:image-20250303112351-7.png||height="234" width="494"]]
1107
1108
1109 2.  Make sure the direction is correct when installing the AA batteries.
1110
1111 [[image:image-20250303105439-2.jpeg||height="241" width="489"]]
1112
1113
1114 == 4.2  Power Consumption Analysis ==
1115
1116
1117 All Dragino's battery-powered products run in low-power mode. We have an updated battery calculator which based on the measurement of the real device. You can use this calculator to check the battery life and calculate the battery life if you want to use a different transmit interval.
1118
1119 Instructions to use are as below:
1120
1121 (% style="color:blue" %)**Step 1**(%%): Download the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from the  below link:
1122
1123 [[battery calculator>>https://www.dropbox.com/sh/sxrgszkac4ips0q/AAA4XjBI3HAHNpdbU3ALN1j0a/Battery%20Document/Battery_Analyze?dl=0&subfolder_nav_tracking=1]]
1124
1125
1126 (% style="color:blue" %)**Step 2**(%%):  (% style="display:none" %) (%%)Open it and choose
1127
1128 * Product Model
1129 * Uplink Interval
1130 * Working Mode
1131
1132 And the Life expectancy in different cases will be shown on the right.
1133
1134 [[image:image-20220621143643-7.png||height="429" width="1326"]]
1135
1136
1137
1138 = 5. OTA Firmware update =
1139
1140 **You can update the firmware of PB05-L to:**
1141
1142 * Change the Frequency band/ region.
1143 * Update with new features.
1144 * Fix bugs.
1145
1146 **Firmware and changelog can be downloaded from:** **[[Firmware download link>>https://www.dropbox.com/scl/fo/ztlw35a9xbkomu71u31im/ACMiK0Y0E5C2ZEcSKxgvmeE/LoRaWAN%20End%20Node/PB05/Firmware?dl=0&rlkey=ojjcsw927eaow01dgooldq3nu&subfolder_nav_tracking=1]]**
1147
1148 **Methods to Update Firmware:**
1149
1150 * (Recommended 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/]]**
1151 * 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]]**.
1152
1153 = 6. Use Cases =
1154
1155 == 6.1 Public Transport Satisfaction ==
1156
1157 Public transport satisfaction terminals, placed inside buses, trams, or train stations, allow passengers to quickly rate aspects like cleanliness, punctuality, or overall experience after a ride, providing cities and transport operators with valuable real-time feedback, even from locations with poor cellular or WiFi coverage. This helps to improve service quality and passenger satisfaction.
1158
1159
1160 [[image:public-transport.jpg||height="186" width="800"]]
1161
1162
1163
1164 == 6.2 Event or Conference Feedback ==
1165
1166 Event or conference feedback terminals, strategically placed at session exits, information booths, or entrance gates, enable attendees to rate specific talks, exhibitors, or their overall event experience on the spot. This setup provides organisers with detailed, location-specific feedback in real time, without relying on constant internet connectivity, allowing them to assess and improve various aspects of the event efficiently.
1167
1168
1169 [[image:conference.jpg||height="186" width="800"]]
1170
1171
1172 == 6.3 Retail Stores or Service Desks ==
1173
1174 Placed at cashier counters or near store exits, these devices allow customers to quickly rate staff behaviour, checkout experience, and store cleanliness. The feedback is captured in real time, giving store managers valuable, honest insights to help improve service quality and enhance the overall shopping experience.
1175
1176
1177 [[image:retail-store.jpg||height="186" width="800"]]
1178
1179
1180 = 7. FAQ =
1181
1182
1183 == 7.1 How to design a customised sticker? ==
1184
1185
1186 PB05-L is shipped with a default PVC stick with satisfied icons. This sticker is not attached to the design for easy customisation purposes. You can design a customised PVC sticker and change the panel design.
1187
1188 Follow this [[link>>https://www.dropbox.com/scl/fo/4i7ezfiwdxqvnmo5d30pe/AO8KACW7i6tRiNC22ZLR_RU?rlkey=9z9bdlix0hal7dmy9lztgmrel&st=9su98u3a&dl=0]] for the design template.
1189
1190
1191 = 8. Order Info =
1192
1193
1194 Part Number: (% style="color:#4472c4" %)**PB05-L-XX**
1195
1196 (% style="color:#4472c4" %)**XX **(%%): The default frequency band
1197
1198 * (% style="color:red" %)**AS923**(%%)**: **LoRaWAN AS923 band
1199 * (% style="color:red" %)**AU915**(%%)**: **LoRaWAN AU915 band
1200 * (% style="color:red" %)**EU433**(%%)**: **LoRaWAN EU433 band
1201 * (% style="color:red" %)**EU868**(%%)**:** LoRaWAN EU868 band
1202 * (% style="color:red" %)**KR920**(%%)**: **LoRaWAN KR920 band
1203 * (% style="color:red" %)**US915**(%%)**: **LoRaWAN US915 band
1204 * (% style="color:red" %)**IN865**(%%)**:  **LoRaWAN IN865 band
1205 * (% style="color:red" %)**CN470**(%%)**: **LoRaWAN CN470 band
1206
1207 = 9. Packing Info =
1208
1209
1210 (% style="color:#4472c4" %)**Package Includes:**
1211
1212 * PB05-L LoRaWAN Push Buttons x 1
1213
1214 (% style="color:#4472c4" %)**Dimension and weight:**
1215
1216 * Device Size: cm
1217 * Device Weight: g
1218 * Package Size / pcs: cm
1219 * Weight / pcs: g
1220
1221 = 10. Support =
1222
1223
1224 * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different time zones, we cannot offer live support. However, your questions will be answered as soon as possible in the aforementioned schedule.
1225 * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it, etc.) and send an email to [[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]].